4611
Mach4 General Discussion / Re: Spindle at Speed
« on: May 09, 2018, 03:30:54 AM »
Hi Steve,
your post is most informative.
I a while back was trying o help a bloke who wanted the Gcode file to pause until an AT_SPEED output on his VFD came good.
I used the mc.SignalWait() API. I had some bother with it until I discovered that the range of input signals for which it works is limited
from 0-63, ergo ISIG_SPINDLE_AT_SPEED being outside that range didn't work. I commented at the time that had even the shortest of
comments about the restriction in the API.chm document would have been most handy.
Once we had that matter in hand coding the rest was pretty straight forward.
Is there any formal process where users might post a specific addition or correction to the current documentation? There has been two posts in recent
months where this particular problem has cropped up for users. I was able to assist in both cases but it would have been easier still if the document had
a single line addition.
Craig
your post is most informative.
I a while back was trying o help a bloke who wanted the Gcode file to pause until an AT_SPEED output on his VFD came good.
I used the mc.SignalWait() API. I had some bother with it until I discovered that the range of input signals for which it works is limited
from 0-63, ergo ISIG_SPINDLE_AT_SPEED being outside that range didn't work. I commented at the time that had even the shortest of
comments about the restriction in the API.chm document would have been most handy.
Once we had that matter in hand coding the rest was pretty straight forward.
Is there any formal process where users might post a specific addition or correction to the current documentation? There has been two posts in recent
months where this particular problem has cropped up for users. I was able to assist in both cases but it would have been easier still if the document had
a single line addition.
Craig