I’m not sure we’re ready to add a lot of configuration options right now.
The MDI screen is due for some improvements and once that’s done we’ll share the probing codes so you can have your own preset probing routines with custom values ready to go there.
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.)
You should try 511. The “Ignore Status Updates” option should be a win for you.
We appreciate that and welcome to the forum. Hopefully, CM will get a lot better in the near future.