M503 crashes Printrun 2.0.0rc8
the-robo opened this issue · comments
Running an M503 command crashes pronterface.
printrun.log contents and console contents do not match.
Files attached.
Steps to reproduce:
- launch pronterface
- connect to printer
- issue M503 command
- press disconnect
Result from compiled version, interface crashes. COM port remains open and printer must be manually reset.
Result from source version, errors (see attached) result. Interface is disconnected and will no longer connect. Manual printer reset is required.
M500 and M504 run successfully
Windows 10 Pro (fully updated)
Marlin 1.2.1 (update: fails with Marlin 2.x as well)
Ender 3 Pro (update, fails with new mainboard 4.2.7 as well)
Baud: 115200
printrun.log
pronterface-gui-console.txt
gui log shows macro recursion - a macro you defined which directly or indirectly calls itself.
About the serial timeout - does the printer hang? Can you operate the printer with the lcd after the error?
If the printer hangs on legitimate commands - the problem is in the printer.
The problem is the same whether I manually enter the M503 or via a macro.
The printer is unaffected by the crash, commands via the LCD work fine. The crash does not release the serial port on the Windows side. Windows can no longer use the port (via PuTTY, etc.). Sending M503 via PuTTY (before the crash) works as expected.
@ROBERTmartin
did you solve your problem?
It seems, like @volconst already point to, you have a problem with a macro as shown in your console text file. Maybe it is worth to attach your macro.
Regarding M503 it looks like that your printer loose connection to Pronterface or vise versa. This usually isn't a problem with Pronterface so fare I know from own experiences or had seen in reported issues here. A known cause is using programs in parallel that blocks the com port while running Pronterface with an established connection. Well known from my side is Cura as this program scans all available COM ports with printer commands and lock the port connected of a printer. I disabled the communication plugin in Cura to be save in this regards. Running Putty and Pronterface in parallel on the same port will ask as well for problems if you don't know which program is using the port at a given time. An other cause can be to high communication rates combined with longer USB cables.
In addition I just recognize in the first post your baud rate setting: "Baud: 114200". This isn't the usual baud rate setting. 115200 should be the correct standard value. Maybe worth to check too.
I tested again today after upgrading the mainboard on an Ender 3 (to a 4.2.7 version).
The problem remains.
Thank you for your suggestions and insight. Here is some additional information regarding you post.
Cura, PrusaSlicer, Matter Controll, and others never loose connection.
Pronterface is the only application running.
I have tried several different USB cables.
The baud rate was a type-o. I use 115200.
M503 crashes Pronterface both from a macro and manually entering.
M503 from a Putty console works with out issue.
I upgraded to Marlin 2.0.6 and the problem still occurs.
Hi, I know this is an old issue. @the-robo, did you manage to solve this? I am unable to reproduce this with either Printrun 2.0.0rc8 or the latest 2.0.1 on Debian. Could you try the latest Windows build and see if the problem persists? As was pointed out above the issue might be related to a faulty macro. Maybe try running with a clean configuration file too.
@rockstorm101 and @volconst,
should we close this issue? I don't see any way to help further.
Agreed. Last request for information was almost a year ago. Please feel free to re-open if the issue is still there on the latest version.