Ignore due to resend errors, checksum mismatch, etc. after last server/host update
This may be completely unrelated but I print quite often and this has never occurred until the last server update to 1.1.2.
These are some of the errors I get and it does pause when this occurs)
- I'm running in win10 64bit
- I'm using Host V2.2.2
- I'm using Server V1.1.2
- Have not modified printer FW in years, have not touched USB cable in years
- Prints pause, but do continue and complete
- Never had this issue until this last update.
- Occurs on any print now (Even a basic test print w/ 200 lines)
- Two different machines generate the same results
- Reseated USB
- Rebooted Pi
These are some of the errors I get and it does pause when this occurs)
11:56:02.641 : Ignore due to resend: Error:Line Number is not Last Line Number+1, Last Line: 25
Error:checksum mismatch, Last Line: 2463 (lot of these w/ a different Last Line number)
Any help/input would be appreciated.
Dave
Any help/input would be appreciated.
Dave
Comments
Thanks for all the support throughout the years.
Dave
If you have ping pong disabled it helps if marlin has sending line numbers with "ok" enabled. Then we can normally detect a missed "ok" on the fly and correct it without pause. Also activating the "wait" message reduces maximum pause to 1s instead of timeout seconds. Simple checksum errors should be fixed fast enough to have no or only tine move breaks without modification. Good configured firmware will not loose steps from this since path planner stops gracefully except when it hits a fat blob maybe.
I do not really think it is version related. Still printing without much com errors my self. But that also depends on the printer, usb cable, cable shielding, where usb cable is positioned. Sometimes even a different usb port or baud rate can reduce error rate. There are many ways that can have an influence.
ThanksD
Dave
You can manually install 1.0.4 for backtesting. It will possibly remove new settings added and upgrading will then add them again with defaults, but it should work without breaking operation. Please enable logging and safe the logs for comparison. Only thing I know is that we are a bit more chatty then in the past, but I think that was already in 1.0.4 the case.
This is what I see in the test area:
https://cfbinc-my.sharepoint.com/:i:/p/dave/EQpbjrnFw41Ahzd9bQb3XNgBD7d01uhcZhoj9GptB9-wCQ?e=NnpZWl
Thanks
Dave
Ping-Pong means send one command and wait for firmware answer "ok" and send next. The others with buffer send multiple command sin parallel to speed up communication. But when firmware looses parts of it due to not being able to buffer it you get com errors just from not enough space. So when disabling ping pong it is crucial to know the buffer size so it does not overflow.
Also if you can send 2 commands in parallel one missed "ok" will not cause a pause. Only when a command comes that does not fit into remaining buffer - then you get a timeout and server assumes this case and continues to fix it.
But best is always of course to not get any errors if possible.
So if it gives consistent errors on 127 use 63 or ping pong mode.
I have sent you a donation for your time.
Dave