723
« on: October 18, 2015, 02:10:41 PM »
Just a side note BUT the Ismoving() is NOT just for motion related functions it is for ANY TIME mach3 may be busy doing something such as read Dro or Led or Write to file that may take a longer time to do.
And you will notice that there IS a bug in Mach3 and Ismoving() that can cause a race condition where it CAN skip over several sections of code.
One of the problems is dealing with an Air motor that drives teh Turret. They are know for Speed variations due to temp/air pressure cycles and moisture content of the air. I had also looked at advance notice of the next tool to get a head start but that did not work out well either as the speed variations can effect it as well. AND if you use a closest direction to the next tool routine that throws it out the door as well.
I do have the script working "HERE" I have been running test on it for several weeks now. I DID find a new bug I never knew about so had to create a workaround for it .
AND this is a BAD application for Mach3 to have to try and pull off with CB and a macro. It is NOT great on data aquisition type stuff where timing is critical.
Just a thought, (;-) TP