2D not an option at this time. Best to use a machine that can handle the workload Might run better on Windows with the same hardware (Better GPU drivers, depending on what GPU it has, still today linux GPU drivers can sometimes be a source of frustration)
How do you add a e-stop button to the Grbl settings if you are using a Arduino uno board with openbuild firmware. Where do you terminate the button to
If it is truly for an emergency, place the E-stop on the main power to your machine so if a true emergency happens, all power is cut. I have used this on both my CNC Lathe and my CNC Router. Amazon.com This is even easer and requires no cutting of power cords for wiring into plugs like the first one. https://www.rockler.com/safety-power-tool-switch. But to answer your question, A0 and Ground, but the two switches I show above are far easier and safer. If a body part is being mangled by the machine, Feed Hold/Abort won't stop it unless you get the router off.
I use both emergency switches. The one that only stops the program from running, the A0 to ground, and the one that cuts off the power to the whole system, the one that Craig linked to Amazon.
Is the config that yall are using is the Openbuild JDs garage and is that IO point a standard for all configs
Hi Peter, Looking for some help - No matter what we try, cannot get the laser to turn off between letters in Control or Lightburn. Almost seems like the PWM isn't turning off to 0 completely. Green traverse lines are always being etched, resulting in messy etching. Combo is Acro 510 and Opt PLH3D-XT with the CNC adapter. Any ideas?
Did you remember to enable Laser Mode ($32) in Grbl Settings? Grbl v1.1 Laser Mode and $30/31 correctly set (Defaults of $30=1000 and $31=0 will do)? Laser wired to PWM (not to Tool Enable by mistake?) docs:blackbox-x32:start [OpenBuilds Documentation] > Section 3.3.2 and 3.3.3
To whom it may concern: I am trying to set the soft-limits for a desktop CNC machine running the X32 BlackBox controller. I do not have any hard-limit switches enabled. When I “incrementally jog” the X-axis (no other axes are connected as yet) but it does not go into feed-hold or stop. I have attached a back-up of the settings from the controller. What am I doing wrong or is it not possible to do what I want to do? Thank you for the support.
1) Did you home the machine prior to testing (Soft Limits applies in Machine coordinates, needs to be homed) 2) Soft Limits Enabled in Grbl Settings? 3) $40 set to 1? 4) Max Travel distances correct? CONTROL will check if you have Soft Limits enabled, then see what the value of max travel is, and just never send jog moves that will exceed the remaining travel. It wont "go into feedhold" (thats for pausing a job) it will just push it as far as allowed in jogging. Pretty silently stopping you from exceeding the Max Travel distance away from Home.
Thank you for the reply, Peter, For your first question, are you referring to the setting of the pre-defined position or the bottom screenshot referring to “G53” gotozero options? Can the options in the “gotozero” drop-down be changed? I am asking as my machine cannot travel those distances. It is made for a specific-function for material testing. I would not want to travel more than +/- 2 mm for each axis. Or do I run my own G53 sequence? The machine axes are in the correct position at this point. Thank you for the help.
Thank you, Peter, Tried it and had messages stating it could not find the hard limit switches, which I do not have.
Did it move towards the switches (if not, $23 Homing dir in Grbl Settings - tell it where the switches are)
Apologies, I stated at the beginning of our thread but did not mention it again above. I do not have hard-limit switches. What is the best procedure to follow then? Just keep using G28 and G30?
Oh wait theres the problem! Get some! You can't use soft limits without homing. You need to Home (soft limits, machine coordinates, and a lot of other offsets depend on it)
Thank you for the understanding. I cannot use soft limits without hard limits switches, is that correct? This then would allow homing of the system and the soft and hard limits can work. Is that a correct definition?
You are right... My bad! I assumed! Thank you again for your assistance. I will make sure to book note the above from GitHub. Thank you again for the support and great software.
Is there a log file stored somewhere where I can see more info? I have an error all of a sudden (error 2, no response from the controller, closing port) and I want to see what can have caused it since the machine ran fine last time and I have not made any changes at all since then. I tired to update control, from 1.0.30 to 1.0.37, and my Teensy 4.1, running GRBLhal, and I still have the same error. I can connect and run the machine on IOSender. It shows no errors.
Machine sat for a few months with no activity and when CONTROL updated to 1.0.377, I seem to have lost any display updating of the machine's work coords. If I manually jog to a location and set zeros, jog away, and then gotozero, the machine does as expected and returns perfectly. However, the GUI does not show the current coords as the machine is moving around. Is there a new setting that it defaulted to something else that I need to return to an actually useful setting?
Not related to CONTROL update (if in doubt, review OpenBuilds-CONTROL/CHANGELOG.txt at master · OpenBuilds/OpenBuilds-CONTROL ) But to show coordinates, make sure a) you didn't disable it Troubleshooting > Application diagnostics and b) you have not changed default grbl settings ($10=511 for example if it's a Blackbox X32) to something else