@MyersWoodshop I have my personal reasoning for having 2nd thought making a pull request which I don’t wanna go into details about it. 
But at the same time, I want to share it with the community. But before I create a pull request to 1F, I need one more genuine pig to test it. 
If anyone interested I can share the firmware, preferably the user having this DISCONNECTED issue cause I believe not everyone can reproduce it. I also posted previously the 2 g-code files I’m using for testing.
Francis - I’m not sure which code baseline you are using. To the best of my knowledge, OF has not published their latest code (1.0.8). They use a private repo for day to day operations.
Regardless, if you have something working, then certainly make a pull request (or push them the diff).
-Tom
It’s public. They are required to make it public since its fork from Buildbotics and according to Buildbotics in needs to follow GNU General Public License Version 2.
Here:
And here is the screenshot of the change history shows 1.0.8 is there.
Looks like this issue was already reported last May without any updates.
If anyone wants to try my fix, I uploaded a firmware here.
francischie/onefinity-release: onefinity firmware release (github.com)
Here’s the demo of the fix:
This is getting old. Wish Onefinity would get an official fix for this
Just had the EXACT same issue, and the EXACT same fix… Did you get an answer back from Onefinity in regard to the origin of the problem?
Francis - yes, they do post releases after the fact. I should have been more specific - that repo is not being used for maintenance or enhancements. So they are ‘complying’ with the license terms but it is not truly ‘open source’ from a development perspective were others can contribute to the active main line.
-Tom
I disagree. This repo is maintained and in fact the same code base where your current firmware is running. I was able to compile and created my own 1.0.8 firmware. Also, I already made a PR request for the fix, and was already accepted. It might make it on the next release. The only thing I don’t see the source is the camotics source.
@BKP @wsj-productions if you can’t wait for the official 1F firmware, you can download and try this firmware that I uploaded that fixes this issue:
GitHub - francischie/onefinity-release: onefinity firmware release
Francis - I didn’t say the repo wasn’t maintained. I said they don’t appear to use it for daily code fixes. During the evolution from 1.0.4 - 1.0.8 they dropped releases, but the repo didn’t change until weeks after the SW release. As such, they do not appear to be using for active development. I’m not saying the repo is not useful, just saying it is not necessarily timely. Hope this helps clarify my statements.
BTW - thanks for digging into the code and tracking down the error! Much appreciated. 
-Tom
Man. for god’s sake is an official fix coming or not? @OnefinityCNC Just today I was running a job and figured, “eh, I might need to adjust the axys by a few millimeters” in the middle of the job. But no, as soon as I stop, low and behold - disconnected and all my coordinates are lost. Is this really what we get for $3000? At least give us an update or estimate - the gentleman above had already fixed it as it seems.
I agree with you this is getting old very quick. It just happened to me as well and I am running v1.0.8. In the half dozen times that this has happened to me it has been after a job completed and the router returned to the work zero.
One thing that I found is that I can recover without losing position by pressing the Play button and at the Continue prompt pressing Cancel.
Mike
So is @OnefinityCNC gonna be doing the whole silent treatment here? No ETA, not even a comment on the status?
Which will be released when? 
woulda left just 1 but it’s a 20 character minimum.
Bumping this. Just got a disconnect after pausing the job and trying to resume a couple of hours later. It would be a nice feature if this worked reliably.
Another month passes, the trees turn of amber hue
and 
(so many leaves to clean up…)
