It is always a good idea to examine the associated logic around the command, in case something is still moving or busy at the time that this command appears to fail.
Any chance of seeing your logic?
Just wondering if anyone else has had problems with the virtindex command having a fatal error every once in a while? Very annoying.
It is always a good idea to examine the associated logic around the command, in case something is still moving or busy at the time that this command appears to fail.
Any chance of seeing your logic?
First you get good, then you get fast. Then grouchiness sets in.
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
I had a different problem with VIRTINDEX. I found that even with a spindle fault (spindle stopped), the lathe would try to complete the thread cycle. And, of course, its impossible to restart a thread, you'll never get the same index mark.
Camsoft sells an inxpensive transistor to amplify the index mark on the spindle encoder. Hook this up to a high speed opto input. I did one better by using a slot sensor and disk on the spindle. Then you can use WAITAUXIO to get a very accurate start for your thread.
Karl