Over on FB, the most frequent problem I see is that people don’t understand that the BitSetter has to be Disabled for their very first initialization, then enabled once they have access to Jogging.
Carbide Motion should default to BitSetter DISABLED for all machines, even those that include it. It should require user selection to enable, so that they both can complete initial initialization, and also can slect the correct location.
Then there seems to be some edge cases where it needs to be re-disabled.
For example, if someone changes the machine type and sends that configuration, then the bit-setter should be disabled. This is an indication that the user has a new machine.