Bitsetter probing during initialization

[Julien]

FYI, this topic came up before (several times), and then:

@robgrz

With BitSetter, or the Nomad for that matter, we depend on having a valid tool offset all the time so if the machine has been off we assume that it’s changed and the tool needs to be checked again. This is both a safety issue and a potential for a lot of support problems so this behavior is not going to change for the foreseeable future.

I know there are a lot of workflows that people can come up with as a compromise. We understand them and we’re not going to implement them. This comes off much more harshly than I intend but I want to be very clear about this behavior in particular so that nobody is under the impression that we’re flexible on the topic. (My wife accuses me of hedging everything so at least she’d be happy about me being definitive on this one.)

It’s been part of the user feedbacks from day one, BUT it’s also quite understandable that C3D now has a very large user base to manage, and, how do I put this gently, some of the users want to use their machine like it’s an iDevice, so the workflow needs to be foolproof.

Considering Rob’s answer above (again, perfectly understandable), if this is a problem for you, you may want to consider using another G-code sender to use a specific workflow that will best suit your habits.