Hey all, Having issues with my z axis not retracting after making contact with touch probe. Also getting an Alarm 3 prompt. Any I ideas what is going on here? [17:49:43] [ [external from hardware] ] OpenBuilds CONTROL received a FEEDHOLD notification from Grbl: This could be due to someone pressing the HOLD button (if connected) [17:49:43] [ [external from hardware] ] OpenBuilds CONTROL received a RESET/ABORT notification from Grbl: This could be due to someone pressing the RESET/ABORT button (if connected) [17:49:43] [ [external from hardware] ] OpenBuilds CONTROL received a CYCLESTART/RESUME notification from Grbl: This could be due to someone pressing the CYCLESTART/RESUME button (if connected) [17:49:43] [ ALARM ] ALARM: 3 - Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended. [ undefined ] [17:49:43] [ ] ALARM: 3 - Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended. [ undefined ] [17:49:43] [ ] ALARM:3 [17:49:43] [ ] Grbl 1.1f ['$' for help] [17:49:44] [ ] Grbl for ARM32 [17:49:44] [ ] Version:ARM32 V3.4 [17:49:44] [ ] $0=10 (step pulse,usec) ;Step pulse time, microseconds [17:49:44] [ ] $1=25 (step idle delay,msec) ;Step idle delay, milliseconds [17:49:44] [ ] $2=0 (stepport invert mask) ;Step pulse invert, mask [17:49:44] [ ] $3=4 (dirport invert mask) ;Step direction invert, mask [17:49:44] [ ] $4=0 (stepenable invert,bool) ;Invert step enable pin, boolean [17:49:44] [ ] $5=1 (lims pin invert,bool) ;Invert limit pins, boolean/mask [17:49:44] [ ] $6=1 (probe pin invert,bool) ;Invert probe pin, boolean [17:49:44] [ ] $10=3 (status report mask) ;Status report options, mask [17:49:44] [ ] $11=0.010 (junction deviation) ;Junction deviation, millimeters [17:49:44] [ ] $12=0.002 (arc tolerance,mm) ;Arc tolerance, millimeters [17:49:44] [ ] $13=0 (report inches,bool) ;Report in inches, boolean (CONTROL needs $13=0) [17:49:44] [ ] $20=0 (soft limits,bool) ;Soft limits enable, boolean [17:49:44] [ ] $21=1 (hard limits,bool) ;Hard limits enable, boolean [17:49:44] [ ] $22=1 (home cycle,bool) ;Homing cycle enable, boolean (Grbl) / mask (GrblHAL) [17:49:44] [ ] $23=3 (homing dir invert mask) ;Homing direction invert, mask [17:49:44] [ ] $24=100.000 (homing feed,mm/min) ;Homing locate feed rate, mm/min [17:49:44] [ ] $25=500.000 (homing seek,mm/min) ;Homing search seek rate, mm/min [17:49:44] [ ] $26=250 (homing debounce,msec) ;Homing switch debounce delay, milliseconds [17:49:44] [ ] $27=1.000 (homing pull-off,mm) ;Homing switch pull-off distance, millimeters [17:49:44] [ ] $30=10000 (maximum spindle speed,rpm) ;Maximum spindle speed, RPM [17:49:44] [ ] $31=0 (minimum spindle speed,rpm) ;Minimum spindle speed, RPM [17:49:44] [ ] $32=0 (laser mode enable,bool) ;Laser-mode enable, boolean [17:49:44] [ ] $100=800.000 (X axis pulse:step/mm) ;X-axis steps per millimeter [17:49:44] [ ] $101=800.000 (Y axis pulse:step/mm) ;Y-axis steps per millimeter [17:49:44] [ ] $102=800.000 (Z axis pulse:step/mm) ;Z-axis steps per millimeter [17:49:44] [ ] $103=177.777 (A axis pulse:step/mm) ;A-axis steps per degree [17:49:44] [ ] $110=2000.000 (X axis max rata:mm/min) ;X-axis maximum rate, mm/min [17:49:44] [ ] $111=2000.000 (Y axis max rata:mm/min) ;Y-axis maximum rate, mm/min [17:49:44] [ ] $112=2000.000 (Z axis max rata:mm/min) ;Z-axis maximum rate, mm/min [17:49:44] [ ] $113=1000.000 (A axis max rata:mm/min) ;A-axis maximum rate, deg/min [17:49:44] [ ] $120=20.000 (X axis acceleration:mm/s^2) ;X-axis acceleration, mm/sec^2 [17:49:44] [ ] $121=20.000 (Y axis acceleration:mm/s^2) ;Y-axis acceleration, mm/sec^2 [17:49:44] [ ] $122=20.000 (Z axis acceleration:mm/s^2) ;Z-axis acceleration, mm/sec^2 [17:49:44] [ ] $123=20.000 (A axis acceleration:mm/s^2) ;A-axis acceleration, deg/sec^2 [17:49:44] [ ] $130=400.000 (X aixs max travel:mm) ;X-axis maximum travel, millimeters [17:49:44] [ ] $131=400.000 (Y aixs max travel:mm) ;Y-axis maximum travel, millimeters [17:49:44] [ ] $132=80.000 (Z aixs max travel:mm) ;Z-axis maximum travel, millimeters [17:49:44] [ ] $133=9999.000 (A aixs max travel:mm) ;A-axis maximum travel, degrees [17:49:45] [ [clear alarm] ] Operator clicked Clear Alarm: Cleared Lockout and Emptied Queue [17:49:45] [ ] Grbl 1.1f ['$' for help] [17:49:45] [ ] Grbl for ARM32 [17:49:45] [ ] Version:ARM32 V3.4
If it isn't you pressing those buttons (or if they aren't connected), it sounds like a classic case of EMI. docs:blackbox-4x:faq-emi [OpenBuilds Documentation]
I have the exact same problems with OpenBuilds Control and my new Genmitsu 4040 Pro Max. Candle & UGS work perfectly fine when z probing but not OB. Did you find a solution?
I just ended up switching to UGS for this machine. I would like to find the issue but no time to run it down further.
Alarms generated by firmware, hosts just display them for you, read https://github.com/gnea/grbl/wiki/Grbl-v1.1-Interface to obtain a thorough understanding
if you actually read the messages..... it appears to think a bunch of buttons have been pressed, and since you have not mentioned that you have those buttons and you pressed them we have to assume this is caused by 'something wrong'. so, touching the probe is triggering what appears to be a hardware reset, so I think you should carefully check the probe setup for where it is shorting the +5 to ground, because that would cause the symptoms.
maybe. in OB CONTROL on the Troubleshooting tab when the probe is NOT active, the magnetic tag is NOT touching the body of the probe, you see this probe is GREEN/OFF then, when you touch the magnet to the body (same as if the magnet is on the tool and the tool touches the body) you see this RED box labelled TRIGGERED probe is triggered. So, you need to set the probe input invert to whatever gets you this situation. and, if that test works ok with no other messages in the serial console, then the wiring is probably ok, but there are 2 tests to do, one with just the probe body and the magnet end touch/notouch, and another test with the magnet on the tool and you being the body to touch the tool. If those both work ok then the wiring is probably fine. Now, back to what I said about checking the wires. The probe has 3 wires, GND, V+,SIG You have to make sure they are the right way round on both ends of the cable BECAUSE the symptom you describe indicates that SIG and V+ are swapped on one end or the other. The V+ powers the lights and it is not strictly needed since connecting SIG to GND is what makes the probe TRIGGERED, but connecting 5+ to GND is what will cause a controller reset. Maybe photos of all your connections to the Blackbox will help us diagnose further.
Looks like a 3rd party controller. "Grbl for ARM" not GrblHAL, and BlackBox has never been ARM based either
aye, but he is trying to use OBCONTROL, therefore he must set it up correctly from CONTROLS perspective
Yes just clarifying the connections won't be BlackBox Also ARM for Grbl or whatever its called (unable to find a git repo, couple online posts mentioning it in relation to genmitsu), may be rebooting because its buggy (not wiring) - since all three Button input IOs fire off before the reset, likely just buggy firmware (porting of AVR to ARM, maybe they didnt port the interrupts right) wiring would probably not fire off all the pins and a reset (shorting power rail will just reset due to brownout). Perhaps some bug that when the setzero after the touchoff is done (eeprom writes messing with interrupts popular ARM thing to get write). But even so Wiring is worth a check, just won't be a BlackBox. Probably Genmitsu or something (no github repo, no issues to cross check if other reports exist) One thing you all also didn't really focus on, each host is probably using different macros. To test hosts against each other - should probably be using the same Macro for all of them. perhaps theres just something in the built in macro CONTROL uses from the wizard, that spazzes out the ARM firmware - that the others more simple macros doesn't do. Regardless, using a supported firmware (Official GNEA/Grbl or Terjeio's GrblHAL) will do And while I do stay out of these 3rd party controllers with unsupported firmware forks running our software threads, just wanted you to be aware as it seems you missed it when you mentioned BlackBox.
Thanks a million guys. I will test your troubleshooting methods next weekend. Many thanks for your input.
