Re: [mach1mach2cnc] GCode execution sequence with DSPMC plugin
thanks for identifying the error. I was updating the externalStill variable, but only during jogging.
I will email the plugin progress report sometime next week. hopefully will complete the remaining items by then.
----- Original Message ----
From: art2 <fenerty@...>
Sent: Wednesday, April 30, 2008 5:52:39 AM
Subject: Re: [mach1mach2cnc] GCode execution sequence with DSPMC plugin
The vaiable MainPlanner- >ExternaStill should be set to false when your doing motion, and when your buffers are empty and motion has stopped, then you set ExternalStill to true. This is what throttles the follwing commands not to execute until you have
completed your motions.
----- Original Message -----
To: Mach Yahoo Group
Sent: Wednesday, April 30, 2008 2:47 AM
Subject: [mach1mach2cnc] GCode execution sequence with DSPMC plugin
hi Brian and Art,
we are seeing a situation that mach does not wait for the buffered movement to complete. once the movement data has been completey off loaded from mach MainPlanner- >Movements, mach then executes the next gcode instruction, eg, M05. the end result is that the movement is still in progress on the mill but the i/o is turned off prematurely by Mach. M05 should be executed when the buffered motion in the device is completely exhausted.
how can we fix this issue? how do we tell mach that we are still moving
the axis using the movement data downloaded from
the DROs does show the current axis positions accurately.
I am not updating the Engine->StatLast, will that cause any problem?
In the plugin, ExTime is set to 0.001, ExBufferHi is 600, and externalType is VMS.
thanks for your help.
[Non-text portions of this message have been removed]