Just a small issue in inch mode and I've checked my machine settings in grbl $13 =1 so I believe that to be correct. The drop down menu on my X and Y appear to still be in metric the Z however is correct I'm probably doing something wrong can somebody give me an idea here maybe others have had this problem I was thinking.
This issue is being discussed via social media in this case Facebook so I will provide the link below for that in case anyone in the future has questions or wants to read this as an archive.
Ps: I hope this is okay with the folks of CNC 3D I think this is a good idea if you do not please let me know take this down if you wish.
Hi Jean-Thierry,Thanks for reaching out.We have not had any other reports regarding this. Have you tried rolling the version forward to 303 after rolling it back to 302?You may be missing some DLL's.It may be easier to reach out to us on our website chat or via Facebook here: https://www.facebook.com/cnc3dau
How can I roll back to Build 300? I'm using FluidNC. I realize that you are official supporting it but Build 301 just broke it. At a minimum, I'd like to stay on Build 300 if Build 301 and future version are incompatible.
Looking at the serial raw log, it looks like Commander is sending "$#" and then "[ESP400]". The "[ESP400]" is dumping my TinyBee's EEPROM and it looks like Commander never fully recovers from that (or my controller doesn't). It takes multiple tens of seconds for the EEPROM dumping to end.
I can press the disconnect button and still command FluidNC via FluidTerm directly, so I believe my controller is at least not locked up. Commander never gets an update to the machine or the work position. If I manually send from Commander a "?", it will refresh the positions but doesn't do so automatically.
Thank you for access to the older builds. That did help. With this data, I've come to the conclusion that Build 301 update was not the issue. I don't have root cause yet, but access to Build 300 let me confirm that this is not a Commander issue (although Commander could allow for a longer timeout to receive all the $ESP400 data that FluidNC is sending). Thanks again for the older builds.
This issue is being discussed via social media in this case Facebook so I will provide the link below for that in case anyone in the future has questions or wants to read this as an archive.
Ps: I hope this is okay with the folks of CNC 3D I think this is a good idea if you do not please let me know take this down if you wish.
https://www.facebook.com/share/p/15HDgCxrMZ/