Print stopping and random movement with Octopi
 
Avisos
Vaciar todo

Print stopping and random movement with Octopi  

  RSS
slayer1551
(@slayer1551)
Trusted Member
Print stopping and random movement with Octopi

Running the latest 3.1.1-RC4 b143 and twice now my print has randomly stopped and started extruding in one spot. Second time was after layer 6 in random spots. It also randomly travels to the front of the print bed and then moves back starts printing again.

Luckily I was watching and stopped it in time

Respondido : 30/12/2017 10:33 pm
ccfoo242
(@ccfoo242)
Trusted Member
Re: Print stopping and random movement with Octopi

I think everyone is having this problem. There's another octopi thread with lots of stories. Something about the serial communication getting garbled.

Respondido : 30/12/2017 10:36 pm
slayer1551
(@slayer1551)
Trusted Member
Topic starter answered:
Re: Print stopping and random movement with Octopi


I think everyone is having this problem. There's another octopi thread with lots of stories. Something about the serial communication getting garbled.

Just looked at my log and these are the last few lines before I rebooted the printed. I was using Octopi on RC3 fine and printed an 8 hour file. Will revert back and see if I can print the same gcode

| Send: N14926 G1 X110.795 Y73.412 E0.82358*86
| Recv: Error:No Checksum with line number, Last Line: 14925
| Recv: Resend: 14926
2017-12-30 21:26:36,807 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 14929, current line = 14930
| Last lines in terminal:
| Recv: ok
| Send: N14923 G1 X112.123 Y97.368 E0.02819*92
| Recv: ok
| Send: N14924 G1 X111.314 Y97.567 E0.02818*86
| Recv: ok
| Send: N14925 G1 X110.795 Y97.744 E0.01856*81
| Recv: ok
| Send: N14926 G1 X110.795 Y73.412 E0.82358*86
| Recv: Error:No Checksum with line number, Last Line: 14925
| Recv: Resend: 14926
| Recv: ok
| Send: N14926 G1 X110.795 Y73.412 E0.82358*86
| Recv: ok
| Send: N14927 G1 X110.981 Y73.367 E0.00649*86
| Recv: ok
| Send: N14928 G1 X111.074 Y73.546 E0.00683*88
| Recv: ok
| Send: N14929 G1 X111.363 Y73.981 E0.01768*94
| Recv: Error:checksum mismatch, Last Line: 14928
| Recv: Resend: 14929
2017-12-30 21:26:39,586 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 15037, current line = 15038
| Last lines in terminal:
| Recv: ok
| Send: N15029 G1 X123.278 Y103.467 E0.10883*101
| Recv: ok
| Send: N15030 G1 X127.603 Y99.142 E0.20703*85
| Recv: ok
| Send: N15031 G1 X127.829 Y99.045 E0.00832*91
| Recv: ok
| Send: N15032 G1 X128.526 Y98.649 E0.02714*87
| Recv: ok
| Send: N15033 G1 X129.002 Y98.306 E0.01983*89
| Recv: ok
| Send: N15034 G1 X129.597 Y97.771 E0.02711*90
| Recv: ok
| Send: N15035 G1 X129.979 Y97.347 E0.01931*89
| Recv: ok
| Send: N15036 G1 X130.312 Y96.904 E0.01878*85
| Recv: ok
| Send: N15037 G1 X130.442 Y96.696 E0.00829*87
| Recv: Error:Line Number is not Last Line Number+1, Last Line: 15036
| Recv: Resend: 15037

Respondido : 30/12/2017 10:49 pm
Martin Stoufer
(@martin-stoufer)
Estimable Member
Re: Print stopping and random movement with Octopi

Interesting to see things so out of order in the log. Looks like line 15037 got corrupted when received and there was a retransmit request that didn't make it. Can you capture this random movement again and see if its the same line and if it gets multiple retransmit requests? Perhaps there is a hole in the logic somewhere that silently gives up on the printing when the resend of a message does not occur.

Respondido : 31/12/2017 1:03 am
slayer1551
(@slayer1551)
Trusted Member
Topic starter answered:
Re: Print stopping and random movement with Octopi

It seems to be random. I just printed the same gcode from the SD card fine however another member has had it stall from SD so be careful guys! I wouldn't leave the printer unattended on RC4.

Originally I thought slic3r messed up but after spending ages looking through the gcode I decided to try again. The first time I saw random movement on layer 2 then it printed fine for 5 minutes then stalled at the front right and started oozing a big blob. The second time I saw random movement on layer 3 and then it stalled a few layers later in the middle of the print which is the photo in the post above. That's when I decided to trace back the log to see what was going on.

Respondido : 31/12/2017 1:21 am
Compartir: