Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint
 
Notifications
Clear all

Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint  

  RSS
devilhunter
(@devilhunter)
Reputable Member
Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

I've upgraded to firmware 3.1.0 with the linear advance feature yesterday. Did no other changes, and now 5 out of 6 prints stop at random layers with the hotend lodged at the top of the print and all temps and fans are still running.

I've got this log from octoprint:

Send: N20093 G1 X92.877 Y115.757 E0.05964*87
Recv: ok
Send: N20094 G1 X92.613 Y115.125 E0.01931*91
Recv: ok
Send: N20095 G1 X92.346 Y114.657 E0.01521*81
Recv: ok
Send: N20096 G1 X91.291 Y113.125 E0.05245*94
Recv: ok
Send: N20097 G1 X90.910 Y112.483 E0.02107*86
Recv: ok
Send: N20098 G1 X90.775 Y112.179 E0.00938*82
Recv: Error:checksum mismatch, Last Line: 20096
Recv: Resend: 20097
Recv: Error:Line Number is not Last Line Number+1, Last Line: 20096
Recv: Resend: 20097
Communication timeout during an active resend, resending same line again to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N20096 G1 X91.291 Y113.125 E0.05245*94
Recv: Error:Line Number is not Last Line Number+1, Last Line: 20096
Recv: Resend: 20097
Recv: start
Printer sent 'start' while already operational. External reset? Resetting line numbers to be on the safe side
Recv: echo:echo: Last Updated: Nov 12 2017 11:07:38 | Author: (none, default config)
Recv: Compiled: Nov 12 2017
Recv: echo: Free Memory: 2158 PlannerBufferBytes: 1360
Recv: echo:Stored settings retrieved
Recv: echo:SD init fail
Recv: echo:SD init fail
Communication timeout during an active resend, resending same line again to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N20096 G1 X91.291 Y113.125 E0.05245*94
Recv: Error:Line Number is not Last Line Number+1, Last Line: 0
Recv: Resend: 1
Printer requested line 1 but no sufficient history is available, can't resend
Changing monitoring state from 'Printing' to 'Error: Printer requested line 1 but no sufficient history is available, can't resend'

Anybody else got problems since upgrading to 3.1.0 or can help me out with this log?
Others on github seem to be having this issue as well
https://github.com/prusa3d/Prusa-Firmware/issues/234

I can't print via SD card because of the design of my printer case, or else i would try that.

I can try changing the USB cable or disabling Linear Advance

Publié : 25/11/2017 6:40 pm
devilhunter
(@devilhunter)
Reputable Member
Topic starter answered:
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

nope, changing the USB cable didn't work.

Publié : 25/11/2017 7:54 pm
devilhunter
(@devilhunter)
Reputable Member
Topic starter answered:
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

From the notes on linear advance, it states that:

This feature adds extra load to the CPU (and possibly more wear on the extruder). Using a communication speed of 115200 baud or lower to prevent communication errors and “weird” movements is recommended.

i've tried other baud rates from octoprint, but all except 115200 will fail to make a connection with the printer

Publié : 25/11/2017 7:56 pm
devilhunter
(@devilhunter)
Reputable Member
Topic starter answered:
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

"disabling" Linear Advance via M900 K0 did nothing, LA is still enabled but corrections are not used; still resulting in higher CPU overhead.

I've reflashed my Prusa back to 3.0.12 and everything is fine again

Linear Advance's higher CPU and bandwidth usage too much for the Raspberry Pi3?

Publié : 25/11/2017 10:35 pm
Starlynk
(@starlynk)
Trusted Member
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

From what you posted, it appears to be a communication issue, most likely with M110.

There is another post regarding Repetier Server, so I would checking that post and try the firmware listed there. It is the new firmware, but with the M110 fixed. When Prusa releases an update to this 3.1.0 firmware, then you should hopefully be able to switch back to the Prusa one.

Publié : 26/11/2017 8:15 pm
GertL
(@gertl)
Reputable Member
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

I had this issue also.

This solved my issue with Octoprint :
https://shop.prusa3d.com/forum/software-f13/checksum-mismatch-t6214.html#p43543

---
Gert

Publié : 27/11/2017 8:23 am
NTX9
 NTX9
(@ntx9)
Eminent Member
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

I started running Octoprint a few months ago. Worked great for a while but then became really erratic. Stopped mid print, disconnected from the network etc.

I had the Raspberry PI mounted on the back of my MK2 just above the CPU. At some point it occurred to me that the Micro USB power connector could be the issue. I think the vibrations from the printer had an effect on the jack soldiered to the board.

I finally replaced the Raspberry PI and have been running the new one with the PI case just sitting on the counter next to the printer. In two weeks I have printed close to 30 prints with no Octoprint failures. Attaching the Raspberry to the printer frame might be OK if you are careful with your wire management. But I am not a fan of micro USB connectors so I have no intention of trying that again.

Publié : 28/11/2017 7:41 am
devilhunter
(@devilhunter)
Reputable Member
Topic starter answered:
Re: Upgraded to FW 3.1.0 with Linear Advance - now prints stop at random layers with OctoPrint

Just an update for this Problem, checking the "Simulate an additional OK for resend requests " box in OctoPrint works. No more failed prints with Octoprint and 3.1.0.

Without this box checked, prints may fail as soon as the first layer.

Publié : 30/11/2017 12:24 pm
Partager :