Hi Everyone, I am trying to get my BlackBox set up on my cnc and am using the latest version of Control also. I am having issues with the homing cycle. I have X & Y homing direction inverted (they travel in the negative direction), it was easier because of my wiring layout. The Z homes correctly, but when the X & Y home it fails. It appears the X backs off the switch (I did change the distance to 3mm from the default 1mm to see if that was the problem). The Y just depresses the switch and I get an error that tells me to check my wiring and my retreat distance (changed to 3mm). Maybe related, I do have 2 steppers to drive the Y, and one of them isn't holding position. Maybe this is causing an error? Did I miss a dip switch setting while assembling the BlackBox, that would cause the stepper to not hold position, or is it a grbl setting? Is there another reason why my homing cycle would be failing? I am using the Xtension Limit Switch kit, and I've checked the wiring a number of times. Let me know if there is some other info that would help with trouble shooting. It is a custom build, but is just a belt X & Y with a lead screw Z. Nothing crazy.
P.S. The machine has been operational for the last couple of years. I am just changing it over to the BlackBox to get some more juice in the stepper drivers and for easier set up. I had not previously had limit switches installed. It was previously an Arduino with a gShield.
We recommend 10mm Also, check that all switches function correctly in the troubleshooting tab first (press and release by hand) - pay attention that you didnt for example wire X to Y as an example and its looking at the wrong switch when it errors - Check wiring on second motor, maybe its intermittent because of a loose connection. - Check current adjustment - Check mechanical issue: Loose shaft coupler / belt pulley, etc slipping on the motor shaft, or belt tension too low so it skips teeth
Thanks Peter. I will change the homing pull back distance to 10mm and go through your suggested troubleshooting. Regarding the stepper itself: I have done a lot of continuity checks on the stepper and have found no issues there. The current it also good. Since I am a mechanical engineer, I assumed I screwed up the electrical or software side of things and didn't even think to check the mechanical stuff. With my controller swap I didn't do anything to the stepper, but stranger things have happened. The belt is tight, but I didn't check the belt pulley was still tight. I'll check that also. Thanks for the suggestions. -JD
That did it! The pulley was loose on the primary Y stepper and adjusting the pull back to 10mm fixed the homing error. Since the Control software defaults the pullback to 1mm, it might be helpful to have the pop-up notes suggest it be set to 10mm. I Saw in the trouble shooting that it could be a problem, but thought that tripling it would be sufficient. Since I didn't think to measure the switch throw first, I didn't consider it would default to being an order of magnitude off. I am sure there is a reason for doing it that way, and the fact that I don't have a standard configuration for my machine compounds that. Seems like it could be an easy use-ability improvement to an already nicely thought out system. Thanks for the quick help! I've been bitten a few times by the lack of a home position, so I'm excited to fold this into my process.
False see our profile definitions on OpenBuilds/OpenBuilds-CONTROL all are set to 5mm by default (which should always be enough, when someone complains we say try 10mm) 1mm might be the Grbl default
Sure, I suppose I am talking about the custom config side, so maybe it's pulling from the grbl defaults and etc etc. It doesn't change my point, which is that it defaulted to 1mm and a note in the hover pop-up would have made for a more user friendly experience. It's a minor suggestion, and I don't mean to take anything away from OpenBuilds, as I've been very happy with my purchase and support. So if I am an edge case, or my application is not the primary focus, disregard the comment. My feelings wont be hurt.
We have a "CUSTOM" profile in the dropdown, which sets the important parameters: See OpenBuilds/OpenBuilds-CONTROL
Hi, I planned to run my first file but can't because of a homing issue. When I launch home all, I receive a message stating alarm 8: Homing fail (See Pic.). By clicking on "home all", the spindle head slides a couple of inches sideways (Couple of inches on X and Y at the same time) and stops (Then the message pops up). I can continue clicking on "home all" and same action happens (Short slide sideways and alarm 8). All motors run without issue (Individually) and when touching by hand the limits, the Hardlimit alarms 1 pops up so I believe everything works fine... By now, I increased the pullback to 10mm and played a bit with the current adjustment but unfortunately the message remains. Any ideas? (*Other issue: My XYZ probe plus calibration doesn't work properly but that's linked to the homing issue). Thanks, Klaas.
Hi Peter, Thanks for the reply. Please see the attached pictures. I kept all the original switches from the Genmitsu PROVerXL 4030. Everything is clearly labelled from factory, after re-checking, I confirm no switches were inverted. Klaas.
Those doesn't have filtering like our Xtensions Limits. See the FAQ section of the BlackBox Documentation for some EMI tips. Spacing wiring away may help, if nothing on that FAQ page helps, upgrade the switches
Hi Peter, Could you please tell me what the settings should be for the X32 controller in $4 and $22? Current settings $4=0 and $22=1 Thanks, Klaas.
$4=0 is correct $22=1 should be correct for standard Homing (but can be customized: Additional or extended settings) - no need to for standard machines/use cases though
Hi Peter, Many thanks for your input and help. By now I try to figure out whether my setup and settings are correct for the X32 controller before trying some major physical changes (I've already ordered the Openbuilds limit switches). I'm proceeding that way because someone with a similar setup does not have interference issues but is running the X4 controller. The major difference between both is the amount of settings available. Therefore could you please have a quick look at the below settings list and tell me whether a value needs to be changed? Maybe there is a critical value that needs to be set to enable proper homing... I'm not really sure about $18, $40 - $46 (Original custom setup). $0=10.0 ; Step pulse time, microseconds $1=255 ; Step idle delay, milliseconds $2=0 ; Step pulse invert, mask $3=7 ; Step direction invert, mask $4=0 ; Invert step enable pin, boolean $5=0 ; Invert limit pins, boolean/mask $6=0 ; Invert probe pin, boolean $7=1 ; Disable spindle with 0 speed, boolean $8=0 ; Ganged axes direction invert as bitfield $10=1 ; Status report options, mask $11=0.020 ; Junction deviation, millimeters $12=0.002 ; Arc tolerance, millimeters $13=0 ; Report in inches, boolean $14=0 ; Limit pins invert, mask $15=0 ; Coolant pins invert, mask $16=0 ; Spindle pins invert, mask $17=0 ; Control pins pullup disable, mask $18=0 ; Limit pins pullup disable, mask $19=0 ; Probe pin pullup disable, boolean $20=0 ; Soft limits enable, boolean $21=1 ; Hard limits enable, boolean $22=1 ; Homing cycle enable, boolean (Grbl) / mask (GrblHAL) $23=0 ; Homing direction invert, mask $24=100.0 ; Homing locate feed rate, mm/min $25=1000.0 ; Homing search seek rate, mm/min $26=250 ; Homing switch debounce delay, milliseconds $27=10.000 ; Homing switch pull-off distance, millimeters $28=0.100 ; G73 retract distance, in mm $29=0.0 ; Step pulse delay (ms) $30=24000.000 ; Maximum spindle speed, RPM $31=0.000 ; Minimum spindle speed, RPM $32=0 ; Laser-mode enable, boolean $33=5000.0 ; Spindle PWM frequency $34=0.0 ; Spindle off Value $35=0.0 ; Spindle min value $36=100.0 ; Spindle max value $37=0 ; Stepper deenergize mask $39=1 ; Enable printable realtime command characters, boolean $40=0 ; Apply soft limits for jog commands, boolean $43=1 ; Homing passes $44=3 ; Homing cycle 1 $45=0 ; Homing cycle 2 $46=0 ; Homing cycle 3 $62=0 ; Sleep Enable $63=2 ; Feed Hold Actions $64=0 ; Force Init Alarm $65=0 ; Require homing sequence to be executed at startup $70=7 ; Network Services $73=1 ; Wifi Mode $74= ; Wifi network SSID $75= ; Wifi network PSK $100=160.000 ; X-axis steps per millimeter $101=160.000 ; Y-axis steps per millimeter $102=160.000 ; Z-axis steps per millimeter $110=2500.000 ; X-axis maximum rate, mm/min $111=2500.000 ; Y-axis maximum rate, mm/min $112=2500.000 ; Z-axis maximum rate, mm/min $120=150.000 ; X-axis acceleration, mm/sec^2 $121=150.000 ; Y-axis acceleration, mm/sec^2 $122=150.000 ; Z-axis acceleration, mm/sec^2 $130=440.000 ; X-axis maximum travel, millimeters $131=342.000 ; Y-axis maximum travel, millimeters $132=118.000 ; Z-axis maximum travel, millimeters $300=Grbl ; Hostname $302=192.168.5.1 ; IP Address $303=192.168.5.1 ; Gateway $304=255.255.255.0 ; Netmask $305=23 ; Telnet Port $306=80 ; HTTP Port $307=81 ; Websocket Port $341=0 ; Tool Change Mode $342=30.0 ; Tool Change probing distance $343=25.0 ; Tool Change Locate Feed rate $344=200.0 ; Tool Change Search Seek rate $345=100.0 ; Tool Change Probe Pull Off rate $370=0 ; Invert I/O Port Inputs (mask) $384=0 ; Disable G92 Persistence $I=custom Many thanks, Klaas.
Standard settings should be fine. 4X and X32 has no difference in Endstop filtering etc. But 2-wire limits are always a little more prone to EMI. Our switches will probably solve it But do go over docs:blackbox-x32:faq-emi [OpenBuilds Documentation] once more. Make sure spindle is earthed, wires seperated, using a decent PSU like a Meanwell, etc - EMI is always a little hard to properly solve, but work through the likely culprits
