I just installed the new BlackBox X32 on my rig, and I can get everything to move except for the Y2 motor. The motor and wiring are fine. I tested it by swapping the Y2 and the Z ports. When the Y2 motor is connected to the Z port, I can make it move by jogging the Z axis. When I try to jog the Y, however, the motor connected to it (in this case Z) it does not move when the Y axis is jogged. Is this a software issue or a hardware issue? I saw an earlier posting about a slave setting in the software, but the link was broken. Any suggestions?
Just for a bit of clarification, because all that swap Y with Z thing gets a but confusing... I made it easier. When the Y motor is in the Y port and the Y2 motor is in the Y2 port, only the left side of the gantry moves. If I swap them and put the Y motor in the Y2 port and then put the Y2 motor in the Y port, only the right side of the gantry moves. So, the question remains. Is there a software setting to make it move the Y2 in sync with the Y? Or a jumper? Or a way to test the Y2 hardware to see if it is okay?
ScottM, Did you do the new software update of the OB control software and/or the Firmware for the Blackbox X32?
I accidentally forgot to enable Y2 in that firmware (fixed the probe, but disabled Y2). Power outtage here at the moment, will post an updated firmware once power is up
May I beg a minute of your time to beta test this before I run a release - just as another sanity check 1) Unzip the attached ZIP file 2) CONTROL > Wizards and tools > Firmware Flashing Tool > BlackBox X32 tab > Machine Style > Custom Firmware > Click red Use Custom Firmware Image button > Select unzipped file 3) Flash Let me know if probe and Y2 works please
I'm new to this, so this reply may not have anything to do with your code update... Using the probe to set Y0 appears to work, but, when I say go to Y, it goes WAY further than zero. I set up the probe, did a probe to set Y zero, and it worked. I saw the zero come up on the display, and it retracted. Then I told it to go to Y zero and it pushed the probe down the spoil board (I did not secure it to avoid damage from something like this) -- And, I made a video that I can upload if necessary.
1) What does the DRO say - how far from Zero are you before you click Zero. Does the actual distance and the DRO number look right? 2) Check your grbl settings > Steps per mm > is it correct (+-200 for our leadscrews?)
No thousand apologies for forgetting to turn on the ganged axis when I compiled, and your patience with me! And the help with testing Probing working for you? Not running away like Scott above?
I'm at 80 steps per mm. That was the recommendation for the BoB's CNC that I am currently trying to upgrade to the BlackBox. So far, it is causing frustration! So I assume that my test for the probe calibration as reported above is invalid. Having the V2 motor working again is extremely helpful!
We use 1/8th microstepping driver - so that number is probably off. Use the Calibration Wizards in CONTROL:
That was very helpful! My original values were double the calculated values. I was able to use the probe to set X, Y, and Z individually and the work zero is correct. If I try the XYZ probe in one operation, it fails, because X does not move far enough to get past the probe. Maybe that is due to my perceived weakness in the X axis.
Peter, NO, PROBE NOT RUNNING AWAY. I didn't run a new project yet but when I did the update patch you gave me. It worked! I will be doing a small test tonight or tomorrow morning. The most important thing here is that YOU fixed issue as fast as you could. You're a human like me. Things go wrong all the time. This is why I'm a OPENBUILDS customer and will be for a long time. You stepped up to the plate fast and fixed it fast. That is GREAT BUSINESS! Out of 8 OB CNC machines I own. This is the first major issue I have ever had. PETER YOU FIXED IT FAST! I'm a very happy OB CNC user. THANKS SO MUCH FOR YOUR TIME! One more thing I would like to say is OB shipping and packaging Department needs to be told they also do a GREAT JOB too. Please past that on to them. Again Thanks, Roger
Passing on for sure. These kinds of messages are read out to the team in the morning meetings and really means a lot to the team members. Have a great weekend!
V1.0.341 released Release v1.0.341 · OpenBuilds/OpenBuilds-CONTROL with the as tested binary for everyone else that needs the probe fix update
Hey Peter, I'm having this issue also. New install of OB control 1.0364 on new X32 box. The wiring for Y2 motor is correct by way of the documentation and the motor engages at startup but there is no movement. Control shows A axis jog buttons but even they wont turn the motor. Is there a $ in grbl to set the A motor to Y2 that I am missing?
Not a $$ settings no, but you can flash the 4th axes firmware from CONTROL > Wizards and Tools > Firmware flashing tool > BlackBox X32 > Machine Style: 4 Axes > Flash Once the 4th axes firmware is installed it just works Can set steps per deg, acceleration, rates etc in Grbl Settings Other checks for motor not working: 1) Motor wiring 2) PSU on and working 3) $4=0(Disabled) in Grbl Settings But (2) and (3) would affect all motors at the same time 4) Y2 in FAULT: See 2nd half of docs:blackbox-x32:currentadjustment [OpenBuilds Documentation]
Thanks Peter. Re-flashing the 3axis XYZ firmware did the trick. Cool to know that there is a ready made one for rotary too.
