Is this the correct place to find the definitions for the extended setting for grblHAL? Additional or extended settings · terjeio/grblHAL Wiki Just the controller looks great, entering my settings now...
OpenBuilds CONTROL dispalys them quite nicely but does not provide all the definitions, so you will need the wiki as you linked it. There are some things you will not be able to set since they were compiled out.
and, oops, you linked to the old wiki which may not have all the current settings. The whole project moved and got reorganized a bit, so here is the current wiki Additional or extended settings · grblHAL/core Wiki
Fyi, if you do find definitions we don't know about (shown in red) point it out so we can add them If we couldn't find documented confirmation, we leave it blank
$8 shows up in red, not is wiki $65 shows up in red, but found it in the wiki $65=<boolean> : default 0 (off). Require homing sequence to be executed at startup(?). Replaces #define HOMING_INIT_LOCK. I think most people want $65=1 right?
here is one $65=<boolean> : default 0 (off). Require homing sequence to be executed at startup(?). Replaces #define HOMING_INIT_LOCK.
no, I don't think we want it to home the moment it resets or powers up. what I want is to power up in an alarm state, can only home before continuing, but when I have made certain the junk that collects on the router table is out of the way (-:
I agree, starting in alarm is what I want. I thought that this is what require homing meant, I have tried $65=1 and $65=0 and I don't start in alarm the way I used to...
Terjeio, thanks for the message but I do not understand what you are trying to say and I am not using io sender. what $ setting do I use to require homering at start up? I have $22=1 set and OpenBuilds control is not going into alarm when I connect. by the way thank you for your work on grblHAL.
$22 contains bits for enabling homing functionality: $$=22 outputs the following info: $$=22 0 - Enable (1) 1 - Enable single axis commands (2) 2 - Homing on startup required (4) 3 - Set machine origin to 0 (8) 4 - Two switches shares one input pin (16) 5 - Allow manual (32) 6 - Override locks (64) 7 - Keep homed status on reset (128) first number is the bit number, last is the bit value. So to enable homing with "on startup required" use $22=5 (1 + 4 = 5) Use $help settings for a listing of all available settings, preferably from a terminal such as puTTY to avoid sender issues. ioSender reads settings data from the controller in order to create the UI so it will always be up to date, and there is a settings only version available. Note that it is Windows only.
Peter if you are still listening to this one you might check out $22. when I set this to $22=5 OpenBuilds Control went in to an unknown alarm.
Thanks @terjeio! That's awesome will get CONTROL to use that too! Wow nice! If you wouldn't mind, things can get lost on the forum, please help by making bugs and tasks into Github issues that way it has a ticket to close so it doesn't get forgotten
I just purchased the blackbox x32, I updated control (re-download/installed it from the website) but it will not allow me to flash the firmware it fails every time. I am using a Mac if that is important.
The port "wlan-debug" is not a USB port. Make sure to select the correct port from the list (in the Flashing tool as well) Mainly though, as the error states onscreen, you don't have Python installed: Python not found when updating firmware