› ›

Prusa Slic3r Not Working With Repetier Firmware Controlled Kossel Clear

lboucherlboucher
in Bug Reports
Hi All

Wanted to post that I had several prints mess up before i realized the GCODE must be the culprit.
I was using Prusas new Slic3r edition 1.31.6 and basicly the print head would just stop mid print, some errors would be reported on the console, then it would run a little bit, then stop again, on and on, ruining the print.

The errors on the console are below.
Suspect Gcode is here:

Was running the latest 0.92.9 firmware.
Repetier server was 0.75.1 Free, will be upgrading to the latest after my next print.

Haven't had time to research the issue any farther myself.


20:03:00.-614: X:0.00 Y:0.00 Z:305.500 E:128.0000
20:03:02.-484: Printed filament:13378.86m Printing time:52 days 16 hours 35 min
20:16:14.-882: Error:No move in delta segment with > 1 segment. This should never happen and may cause a problem!
20:16:14.-882: Warning:executeGCode / queueDeltaMove returns error
20:16:21.-473: Error:No move in delta segment with > 1 segment. This should never happen and may cause a problem!
20:16:21.-472: Warning:executeGCode / queueDeltaMove returns error
20:16:52.-463: Warning: Communication timeout - resetting communication buffer.
20:16:52.-463: Connection status: Buffered:111, Manual Commands: 2, Job Commands: 5000
20:16:52.-463: Buffer used:111 Enforced free byte:19 lines stored:9
20:17:23.-402: Warning: Communication timeout - resetting communication buffer.
20:17:23.-402: Connection status: Buffered:113, Manual Commands: 2, Job Commands: 5000
20:17:23.-401: Buffer used:113 Enforced free byte:19 lines stored:7
20:17:35.-274: Error:Wrong checksum
20:17:35.-256: Resend:7319
20:19:32.-104: Warning: Communication timeout - resetting communication buffer.
20:19:32.-104: Connection status: Buffered:119, Manual Commands: 2, Job Commands: 5000
20:19:32.-104: Buffer used:119 Enforced free byte:19 lines stored:9

Error occured at 12.665 height

Comments

  • RepetierRepetier
    Yes, that looks like firmware did something unexpected. But do not expect me to analyse 6.5MB gcode - i would not see the line even after a week of reading:-)

    You need to find the exact commands causing this. For this enable logging in server. After the error happened you can see the commands send making it quite easy to spot the line where this error occurs. It must be one of the 10+move buffer size commands before the error. That should make it more likely to detect what combo makes the problems.
  • lboucherlboucher
    Looking at the Gcode it seems odd G1 F14400 is being called so much.

    G1 X9.276 Y-38.037 E18.87569
    G1 X8.086 Y-42.476 E19.03851
    G1 F14400
    G1 X9.276 Y-38.037 E18.12907
    G1 F14400
    G1 X8.318 Y-37.643 E17.92401
    G1 F14400
    G1 X7.788 Y-37.467 E17.81356
    G1 F14400
    G1 X7.250 Y-37.316 E17.70289
    G1 F14400
    G1 X6.704 Y-37.191 E17.59222
    G1 F14400
    G1 X6.154 Y-37.093 E17.48155
    G1 F14400
    G1 X5.599 Y-37.021 E17.37088
    G1 F14400
    G1 X5.044 Y-36.976 E17.26058
    G1 F14400
    G1 X3.721 Y-36.938 E16.99868
    G1 F14400
    G1 X3.721 Y-43.645 E15.67128
    G1 F14400
    G1 X8.086 Y-42.476 E14.77686
  • RepetierRepetier
    Yes, that is just waste of communication capacity. You could even add it to the real moves and omit them if it does not change. That reduces communication speed to 50-75% I guess. Hope it is not everywhere.
Sign In or Register to comment.