Hello Guest it is April 27, 2024, 08:42:10 AM

Author Topic: G code stops after M03 command  (Read 860 times)

0 Members and 1 Guest are viewing this topic.

G code stops after M03 command
« on: August 25, 2023, 06:29:10 AM »
I have been updating a Boxford vmc260 which has been running mach3 with USS and PMDX125 in windows 7 for 12 years.
The machine is now configured keeping the PMDX125 but changing to ESS and Mach4 in windows11. Having worked through getting tool change and probing working it was time to try running a simple program to drill a couple of holes centre drilling first to test the tool change.
After setting work coordinates and running the Gcode the machine carried out the tool change, started spindle (which is an ac servo set up as motor 5 step and direction) and immediately froze.
If you turn spindle off from the screen and back on again until the gcode reaches M05 and it pauses again.

I have stripped the gcode back to 2 lines:
S2000 m03
G90 G00 x25 y25
Run from MDI spindle starts but moves are not executed.
If I remove the S2000 m03 the move does work so it has to be due to the spindle command.
I have disabled ‘wait on spindle to stabilise in Control Spindle tab.
Mach4 V4.2.0.4809 licensed

Has anyone come across this or have any idea where I am going wrong?

Regards

Art
« Last Edit: August 25, 2023, 06:46:48 AM by Flying Scot »
Re: G code stops after M03 command
« Reply #1 on: August 25, 2023, 06:54:04 AM »
2023-08-25 11:31:26.207 [I    ] - API: mcCntlMdiExecute(inst = 0, commands = 's2000 m3
g90 g00  x25 y-10
') (unknown caller)
2023-08-25 11:31:26.309 [I    ] - Attempt transition from "Idle" on event "MDI Start" controller.cpp:2473
2023-08-25 11:31:26.309 [I    ] - S_IDLE_on_exit
2023-08-25 11:31:26.309 [I    ] - Signal id 1172, (Machine Idle), changed from HIGH to LOW.
2023-08-25 11:31:26.309 [I    ] - ACTION_start_mdi
2023-08-25 11:31:26.309 [I    ] - SoftSync()! Clearing planner.
2023-08-25 11:31:26.331 [I    ] - S_MDI_RUNNING_on_entry
2023-08-25 11:31:26.331 [I    ] - SoftSync()! Clearing planner. stateinterface.cpp:1351
2023-08-25 11:31:26.331 [I    ] - S_MDI_RUNNING2_on_entry
2023-08-25 11:31:26.331 [I    ] - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2023-08-25 11:31:26.331 [I    ] - 
2023-08-25 11:31:26.331 [I    ] - -----===== Mach4 build 4.2.0.4809, ESS build 285 =====-----
2023-08-25 11:31:26.331 [I    ] - 
2023-08-25 11:31:26.334 [MR   ] - 
2023-08-25 11:31:26.334 [MR   ] -    >>> ESS: SS Motor Mode - Spindle stopped, 'Spindle Motor Dir' not changed.
2023-08-25 11:31:26.334 [MR   ] - >>> ESS: Told to shut off the spindle by Mach4.
2023-08-25 11:31:26.335 [MR   ] - Signal id 1142, (Spindle Fwd), changed from LOW to HIGH.
2023-08-25 11:31:26.335 [MR   ] - 
2023-08-25 11:31:26.335 [MR   ] -    >>> ESS: SS Motor Mode - 'Spindle Motor Dir' set to Forward.
2023-08-25 11:31:26.335 [MR   ] - >>> ESS: Setting SS Motor 5 spindle to 2000.0 RPM on Range 0
2023-08-25 11:31:26.335 [MR   ] - >>> ESS: Spindle PID is not enabled.
2023-08-25 11:31:26.335 [MR   ] - Signal id 1141, (Spindle On), changed from LOW to HIGH.
2023-08-25 11:31:26.336 [MR   ] - Waiting 200.000000 seconds for spindle at speed... spindle.cpp:306
2023-08-25 11:32:39.655 [MR   ] - API: mcCntlCycleStop(inst = 0) (unknown caller)
2023-08-25 11:32:39.656 [MR   ] - ~~~~~~ESS: Laser and M62 outputs shut off by MSG_CYCLE_STOP
2023-08-25 11:32:39.656 [MR   ] - >>>>>>>> LASER - ESS: Laser PWM DISABLED due to a STOP event.
2023-08-25 11:32:40.554 [MR   ] - -----ESS: Reset Homing and Probing settings.
2023-08-25 11:32:40.554 [MR   ] - 
2023-08-25 11:32:40.554 [MR   ] -    $$$ ESS: Mach4 had a Cycle Stop - Force Output Stop Sates Now
2023-08-25 11:32:40.554 [MR   ] - Attempt transition from "MDI Running" on event "Stop" command.cpp:3456
2023-08-25 11:32:40.554 [MR   ] - ~~~~~~ESS: Laser and M62 outputs shut off by StopStates
2023-08-25 11:32:40.554 [MR   ] - S_MDI_RUNNING2_on_exit
2023-08-25 11:32:40.554 [MR   ] - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2023-08-25 11:32:40.554 [MR   ] - -----ESS: Reset Homing and Probing settings.
2023-08-25 11:32:40.554 [MR   ] -    $$$ ESS: Finished processing the Stop Event
2023-08-25 11:32:40.554 [MR   ] - 
2023-08-25 11:32:40.555 [MR   ] - S_MDI_RUNNING_on_exit
2023-08-25 11:32:40.555 [MR   ] - ACTION_stop
2023-08-25 11:32:40.555 [MR   ] - Done. spindle.cpp:311
2023-08-25 11:32:40.559 [MR   ] - >>>>>>>> ESS: DISABLING Laser PWM.
2023-08-25 11:32:40.578 [MR   ] - S_IDLE_on_entry
2023-08-25 11:32:40.580 [MR   ] - Signal id 1172, (Machine Idle), changed from LOW to HIGH.
2023-08-25 11:32:40.581 [I    ] - API: mcSpindleSetDirection(inst = 0, dir = 0) (unknown caller)
2023-08-25 11:32:40.581 [I    ] - Signal id 1142, (Spindle Fwd), changed from HIGH to LOW.
2023-08-25 11:32:40.581 [I    ] - 
2023-08-25 11:32:40.581 [I    ] -    >>> ESS: SS Motor Mode - Spindle stopped, 'Spindle Motor Dir' not changed.
2023-08-25 11:32:40.581 [I    ] - >>> ESS: Told to shut off the spindle by Mach4.
2023-08-25 11:32:40.582 [I    ] - Signal id 1141, (Spindle On), changed from HIGH to LOW.

This is the diagnostic log that shows waiting for 200 seconds (not sure where this comes from and also mentions laser
Re: G code stops after M03 command
« Reply #2 on: August 25, 2023, 07:14:28 AM »
Problem found ignore all of above I cant figure out how to delete it.
a delay of 200 seconds in acceleration and deceleration was the problem
art