I’ve encountered two issues since updating to CM 640, didn’t find either when searching, so I’m not sure if these have been mentioned before:
When disabling bitsetter to do a surfacing job, I will reset my Z zero manually and save. This first zeroing does not take. When running the job, the z resets to something far above the max z travel, raises the spindle and misses steps, ignoring the limit switch, then starts running passes. Only after stopping, re-zeroing and restarting does the job run successfully. Happens every time.
Game controller not recognized the first time entering the Jog screen after initialization. I have to trigger some other prompt or action first, like a quick move, but change, loading of a file, etc., then go into the jog screen for gamepad recognition.
I think it somehow remembers the tool length offset. Try hitting Reset All Offsets before setting your zeroes. ??? Otherwise, restart CM after enabling/disabling the bitsetter.
I think you might need to just click anywhere on the jog screen to give it focus. I have to do this with Gsender too. If I enter a MDI command to turn on the spindle, the remote doesn’t do anything until I click in the Jog window.
On the SO5 you can enable and disable the BitSetter without having to reinitialize (So the forum says). However on SO3/4 you have to reinitialize after enabling/disabling the BitSetter. Somehow when the Bitsetter is enabled/disabled it messes with the internal coordinates. So on the SO3/4 reinitialize to get everything syncronized after enabling/disabling the BitSetter.
It’s almost like it treats the new z coordinate as a negative, since it moves upward beyond where the limits are before it starts the job. I suppose for now, reinitialization is part of the workflow for me.