My original fix of the instance_config file only fixed the specific error I had encountered.
Now, in the event that during startup FabMo is unable to read a current location from the instance_config.json file, it will load g2 with a "0" location for each axis. The config file itself will be regenerated after any move.
I believe this is the error that Brian recently reported that kept the tool from starting.
Someday might want to put a user warning on this, but it seems a pretty unusual thing and we will want to make sure that we've dealt with any other potential variations.
My original fix of the instance_config file only fixed the specific error I had encountered.
Now, in the event that during startup FabMo is unable to read a current location from the instance_config.json file, it will load g2 with a "0" location for each axis. The config file itself will be regenerated after any move.
I believe this is the error that Brian recently reported that kept the tool from starting.
Someday might want to put a user warning on this, but it seems a pretty unusual thing and we will want to make sure that we've dealt with any other potential variations.