Nomad auto measures tool after zeroing - how do I stop this?

CNC Machines Nomad
1

Basically the title. Whenever I zero the z or zero all, the Nomad instantly rips the tool away from the job to go measure it again (despite measuring during initialising and meauring when going into jog mode).

As far as I can see, there is no setting to stop this, but I would really like to. It’s only started this since I moved to my new macbook.

Thanks!

2

The only way I know of is to revert to a prior version of Carbide Motion that doesn’t have that “feature” :roll_eyes:

1 Like
3

In older versions of CM the machine initialized and then measured the tool. In the last version of CM the machine initializes and then comes to rest near the BitSetter (Shapeoko). Then if you zero the bit travels over to the BitSetter to reestablish the offset between the initialization and the Z. The X Y and Z are remembered from the previous setting of the zeros. So C3D says a lot of people never change their X Y and Z zeros. That is not true for me because I dont run the same jobs over and over.

There is no way around the current behavior. The only exception is what @Tod1d suggested is to revert to an earlier version of CM. Even then the BitSetter is used so it is half a dozen of one and 6 of another. To keep the current version you just have to live with the behavior. You could give a request for enhancement but individual user cases compared to the majority it is not likely to change. The news is they changed it recently so they could change it again in the future.

On a Shapeoko you can disable the BitSetter not sure about a Nomad. If you can disable the BitSetter on a Nomad you can set everything manually with the paper method.

1 Like
4

The bitsetter behaviour has always seemed a bit odd to me.

On a brand new setup with a new tool and workpiece it doesn’t matter how much the tool sticks out as long as the Z zero has been set. Only if there is a tool change in the job does consistency need to be maintained so it could just use the bitsetter directly before and after the toolchange.

It would be usefule for CM to use bitsetter at beginning and end of job to detect tool slippage or damage.