Messages

1

General Mach Discussion / Re: Hangs After Last Motion Command, Does Not Execute M05 Spindle Off

« on: November 22, 2019, 04:55:50 PM »

Added the leading and trailing % lines. Each is %CRLF specifically. Ran the operation sequence 3 times and it failed on the 3rd run. Same symptom, all moves executed but the spindle-off command not executed and hung. So yeah it is one of those nasty intermittent things. Unfortunately did not respond to the % lines.

I think I'll chop down the sequence, investigate if there is any dependence on length of the move sequence. If I can pare it down to a manageable size that executes quickly (and still fails) I can iterate on experiments without waiting hours of machine time. Maybe experiment with adding delays before the spindle-off command.

2

General Mach Discussion / Re: Hangs After Last Motion Command, Does Not Execute M05 Spindle Off

« on: November 20, 2019, 07:05:36 PM »

Viewed in notepad++ all lines including last end with CR,LF.  But I'll try adding a lone % line anyway.

3

General Mach Discussion / Re: Hangs After Last Motion Command, Does Not Execute M05 Spindle Off

« on: November 20, 2019, 04:50:45 PM »

Tag % onto the end of the last line, or as a new line following last line?  Thanks.

4

General Mach Discussion / Hangs After Last Motion Command, Does Not Execute M05 Spindle Off

« on: November 20, 2019, 12:12:51 PM »

Configuration: USB RnRMotionController and stepper motors, running purchased and licensed Mach3 on a WinXP Thinkpad.

Laptop has all the power management and screen saver turned off, runs continuously.  Wireless networking is disabled and Ethernet is unplugged.  Not running any other application.

Intermittently the whole NC motion file will run successfully, but stop before executing the last 2 lines M05, M30.  So the spindle is still running.  Mach3 is hung at this point.  Need to close Mach3 to recover.  Sometimes Mach3 application can be closed.  Other times it is showing an unrecoverable error dialog box, has to be force-closed.

I have turned off the NC path display.  This seems to have fixed a hang in updates to the NC program display, but it did not cure the basic hanging issue.

Why is Mach3 successfully running a huge file of motions, then wedging at the spindle off command?  Possible issue with RnRMotionController?  Thanks for your help!