Last night I was playing with a new lens and trying to find the best focal length. I was using the Z axis up/down control in LB with the increment set to .02 inch
I would click the Z up button and then pulse the laser to see the dot size, After doing this twice and not be 100% certain the Z axis was actually moving I clicked the Z up button a third time and the Z began moving up over an inch and was about to crash into the nozzle before I hit the eStop.
I thought I may have done something wrong, so I lowered the Z and tried again, this time I think it was the 4th or 5th button press of the Z up and the Z began moving upward toward a crash again.
Is this an issue with LB or with the Laser?
PS - can the Admins change the 15 character minimum for Topic Names? Sometimes I really do not need 15 characters.
I had a previous discussion about LB Z axis movement with respect to multiple passes. I was told that LB did not actually know where the Z axis was at and was just trying to do an absolute position command based on where it thought the Z was at and where you wanted it to be.
Could that have anything to do with LB moving the Z in an unexpected manner?
Ruida doesn’t support relative Z move commands in cut files, but they do have relative Z commands for “immediate mode”, which is what the arrows use, unless you have the “Move from origin” button checked in the Move window.
I have never turned on the “Move from Absolute Machine Zero” because I was not 100% sure what it would do and the movements seemed to work fine with that control turned off.
Now might be a good time to learn what that control button actually does.
Funny, I had a similar problem on my Bodor with a Ruida controller, but all of my movements were either manual or using the auto-focus. I’ve had several minor head crashes because of that. No movement commands were being made from software, either LB or RD. This may be a controller issue.