New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error:Line Number is not Last Line Number+1, Last Line: ... #2342
Comments
Probably related: MarlinFirmware/Marlin#3680 - seems to be a firmware issue, not OctoPrint |
Can confirm same issue on Original Prusa I3 Mk2 Firmware 3.1.0 octopi 0.13.0 |
I am having the exact same issue and the same config as described in the bug.
How is this a firmware issue if the firmware is requesting resend of 20235 and Octoprint is sending 20234? If I use the exact same gcode file and send it via another means. Slic3r, Simplify3D, etc it does not fail. Only Octoprint is exhibiting this behavior. This is with OP 1.3.6 |
Duplicate of #2285 and in fact caused by a bug in the Prusa fork of Marlin as reported by me in prusa3d/Prusa-Firmware#331 And judging by the flood of comments on #2285, that appears to not be the only problem that the current versions of Prusa's firmware seems to have sadly. As mentioned in my firmware ticket, this:
should work, but it's tricky to test. |
I will dig into the Prusa code and try to find this. Super annoying and I can't trust Octoprint to finish the job. As I said, this only happens with Octoprint (so far) which is why I strongly suspected Octoprint code.
… On Jan 10, 2018, at 11:16 PM, Gina Häußge ***@***.***> wrote:
Duplicate of #2285 <#2285> and in fact caused by a bug in the Prusa fork of Marlin as reported by me in prusa3d/Prusa-Firmware#331 <prusa3d/Prusa-Firmware#331>
And judging by the flood of comments on #2285 <#2285>, that appears to not be the only problem that the current versions of Prusa's firmware seems to have sadly.
As mentioned in my firmware ticket, this:
Note: There does exist a workaround in OctoPrint for this (since it's happened in the past with other firmware variants), users can tell OctoPrint to "simulate" an ok after resends by enabling Settings > Serial communication > Advanced options > Simulate an additional ok for resend requests, but that has to be done manually.
should work, but it's tricky to test.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#2342 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEIjP1RnGWZEfbx5deV2yPgyeYpN93Iks5tJdFwgaJpZM4RVS6e>.
|
Contrary to other hosts, OctoPrint strictly adheres to the ping-pong protocol in place. Read: Any command it sends must be acknowledged by an The underlying issue here is a missing
|
Probably a bit late but i have the same issue with prints just randomly stopping mid print. I have only now seen the errors popping up with using the Slic3r interface directly connected to various PC's with different USB cables. I'm in the process of getting my new printer setup and have been fighting mid print pauses and occasional step skipping from both Octoprint and AstroPrint. Also 2 failures on Repetier Host. Step Skips were not mechanical it skipped on Z at 10mm that send me on a wild goose chase on fade hight. I notice a lot of these guys on Slic3r (Probably just a protocol issue with Slic3r but glad i found this post) My setup
If there is any testing that needs to be done please let me know. I will try my best to assist. |
Hmm. I've been using Cura and Slic3r to send jobs over serial (USB), and up until today (maybe a few dozen prints), no errors. In Slic3r, noticed the "Line Number is not Last Line Number+1" message in the serial text, but it would only display it once, and seemed to work fine after that. Never failed mid-print yet. So researching this error, it seemed like a big potential problem, so decided to build and upload the latest 1.1.9 Marlin bugfix fw. Now getting an endless supply of "Line Number is not Last Line Number+1" and it refuses to print in Slic3r. Printed fine in Cura though. |
What were you doing?
OctoPrint installed via OctoPi image on a raspi zero w
What did you expect to happen?
print successful
What happened instead?
print had to be aborted; pause/unpause did not help, neither did resending the requested line
Did the same happen when running OctoPrint in safe mode?
as it is only happening randomly, it's not easy to reproduce. I can try safe mod if absolutely required
Version of OctoPrint
Operating System running OctoPrint
OctoPi 0.14.0
Printer model & used firmware incl. version
Original Prusa MK2 MM Fw: 3.1.0
Browser and Version of Browser, Operating System running Browser
Windows, Chrome Version 63.0.3239.84 (Offizieller Build) (64-Bit)
Link to octoprint.log
https://gist.github.com/brandstaetter/06ef4053cc3db891c14bd3d5bd034004
Link to contents of terminal tab or serial.log
n/a
Link to contents of Javascript console in the browser
n/a
Screenshot(s)/video(s) showing the problem:
n/a
I have read the FAQ.
The text was updated successfully, but these errors were encountered: