6071
VB and the development of wizards / Re: Read out G-Code list in the top right corner of mach3
« on: January 08, 2011, 04:20:58 PM »
I have looked and look and thunk and thunk but don't see a way to do what you want as there eis now way I see to KNOW if the G31 is running.
One thing I do see is to moniter the ProbeLed and IF it goes active AND wait a few MSec and IF the axis Ismoving () then Estop.
But looking back through a few years of notes on probing. The problem was NOT when the probed actually tripped the input and it turned on the led. IT was when the probe tripped but MACH did not see the trip because it was busy with VB stuff and then the axis drove the probe into the part thinking it had NOT tripped. (IMO)
I can say that the G31 when used in the Gcode programs is stone cold dependable. I have routines that probe for 998000 trips and it never misses a point.
BUT when you use it INSIDE the VB enviroment it requires you to constantly guard it with wait states to insure it does and sees what it is suppose to without crashing the probe.This usually makes it a very clunky stop/go process that is FAR from a smooth operation.
IF we had an indicator like you need MAYBE it could be made more fail safe.
Again (IMO), (;-)
One thing I do see is to moniter the ProbeLed and IF it goes active AND wait a few MSec and IF the axis Ismoving () then Estop.
But looking back through a few years of notes on probing. The problem was NOT when the probed actually tripped the input and it turned on the led. IT was when the probe tripped but MACH did not see the trip because it was busy with VB stuff and then the axis drove the probe into the part thinking it had NOT tripped. (IMO)
I can say that the G31 when used in the Gcode programs is stone cold dependable. I have routines that probe for 998000 trips and it never misses a point.
BUT when you use it INSIDE the VB enviroment it requires you to constantly guard it with wait states to insure it does and sees what it is suppose to without crashing the probe.This usually makes it a very clunky stop/go process that is FAR from a smooth operation.
IF we had an indicator like you need MAYBE it could be made more fail safe.
Again (IMO), (;-)