teranick374
Posts: 2
Joined: Sun Feb 03, 2019 7:54 pm

4.1.1 Com Overrun

Sun Feb 03, 2019 8:27 pm

Running Marlin over USB Win10. See attached log file. Printer FW has been stable for ever. Previous versions of S3D were fine along with Repetier and Cura. Suddenly with 4.1.1, when I go to start a print, sometimes it does a home Z and S3D appears to go into an error state and dumps the entire g-code file.

What is the cause of the "READ: Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)" did some timeout change?

Also noticed in 4.1.1 that after an emergenc y stop, the Extruder and Heated Bed radio lights remain Red, but the printer has re-initialized and bed/extruder power is off. Expecting radio lights to go to dark red.

Interesting part of the log file:

READ: T:224.9 E:0 W:4
READ: T:224.7 E:0 W:3
READ: T:224.8 E:0 W:2
READ: T:224.9 E:0 W:1
READ: T:225.0 E:0 W:0
READ: ok
SENT: M105
SENT: G91
SENT: G1 Z5 F5000
SENT: G90
SENT: M82
SENT: G28 X Y
SENT: G92 E0
SENT: G28 Z
SENT: G1 Z5
READ: ok T:225.0 /225.0 B:60.0 /60.0 T0:225.0 /225.0 T1:33.9 /0.0 T0R0:1072/225.0 @:39 B@:22
SENT: T0
READ: Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)
READ: ok
READ: ok
SENT: G1 Z0.090 F1002
READ: ok
READ: ok
READ: Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)
...rest of the gcode with errors
Attachments
errorlog.txt
(22.91 KiB) Downloaded 3 times

S3D-Jake
Posts: 412
Joined: Wed Jun 20, 2018 11:45 am

Re: 4.1.1 Com Overrun

Tue Feb 05, 2019 12:33 pm

What printer do you have?

The error message given doesn't allow for much interpretation. The temperature commands look to have been executed fully. The number of commands being buffered could cause an issue, depending on the board installed in your printer.

Have you opened Tools > Firmware Configuration > Communication tab and lowered the buffer size?

If the issue is with the G-Code itself, you should see the same issues when printing form SD card.

Have you tried using an SD card or flash drive to print this g-Code file?
"A bird does not sing because it has an answer. It sings because it has a song."

teranick374
Posts: 2
Joined: Sun Feb 03, 2019 7:54 pm

Re: 4.1.1 Com Overrun

Sat Feb 09, 2019 3:20 pm

Reverted to 4.0.0 and it continues to be stable. Haven't tried lowering the buffer size(yet). Settings in the Comm tab values are the same between 4.0.0 and 4.1.1.

Did the S3D Comm code change between the versions? Running them side by side, I still see the issue where the heater radio lights don't turn dark red after and emergency stop on 4.1.1, so something is different.

The printer started life as a first round Robo3D kickstarter. About the only thing that remains from the original is power cord and logo. Thank goodness they don't build them like they used to (hopefully).

Running a Marlin build circa 2017 on a Ardunio Mega. Standard stuff. Looking at the source code, MSG_ERR_STOPPED is pretty generic. I'll have to add some debug code and rebuild.

But you're right "The error message given doesn't allow for much interpretation. " doesn't give you anything to go on, and it sounds like you are confirming that others are not seeing the issue. Thanks. I'll report back if I find anything interesting.

Return to “Troubleshooting and Bug Reports”