Unfortunately I had to change a bunch of things at the same time, my control board started playing up so I got a replacement board and then uploaded the latest GRBLHAL firmware onto it. When I launched Control it then updated to the latest version as well. So new Control, new (same) board, and newer firmware on the board. I ran Control and restored my backup file and got a few errors when it applied it. A few of the values were set to NaN. Wifi and a couple of others. Checked the backup file and it was correct so manually rewrote those values in Control. When I went to test my CNC plasma everything worked except I couldn't fire my torch. I got an error that M3 was an invalid value and it showed the NaN value again. I can't see the M3 setting in my backup file anywhere and I can't figure out how to change it. Hope someone can help. Cheers Matt
The Tool On menu looks at $30=1000 (usually for a plasma) to scale the M3S value for the menu. If your $30 is not set to a number then NaN is "not a number": Check $30=1000 If your test wasn't the Tool On menu but a Job, then the M3 comes from your CAM with problems
As always thanks so much Peter. I wonder why the config import didn't work - I can see the value in my original config backup file but it hasn't imported for some reason. Fixed now. Cheers Matt
Hi again. I editted the config file and imported the settings and saved to firmware, should $30 be visible in the GRBL settings tab? I am still getting the NAN error......
Thanks Peter. When attempting to turn on the tool from the menu, not from a job. I have just updated the GRBLHAL firmware prior to this so I am wondering if there is something funny going on with the new firmware. $30 isn't visible for me in the settings tab.
Yes, Tool On looks at the Grbl Settings Do a EEPROM reset Then try again Import the backup from the Restore Backup button Then click Save Any errors while saving, grab screenshots. And post screenshots with the backup for review
Hi Peter. I checked GRBLHAL and there was a newer firmware so I flashed that and then did the reset settings and EEPROM. I then closed Openbuilds so that the console would be clean and started up and then restored my backup. There were a couple of errors that popped up but they get overwritten, they were related to soft limits being enabled when homing wasn't enabled but $74 and $75 errors popped up. These can be seen in the console log. Interestingly I didn't get the error around the $30 command from before. I then edited the GRBL settings to set 74 and 75 and saved it without an error but the console output is a bit screwy and shows the value of $75 instead of $I when listing all the settings. I backed up the settings. I powered off the controller and powered it back on and reconnected and it connects to wifi fine and console output looks perfect. I then reset the settings and EEPROM again and restored from the new backup file which was working fine and get the $74 and 75 error again. I have attached the two console outputs and the original config file I am trying to restore from. Wonder if this is a GRBLHAL error. Cheers Matt
