Hey guys New to openbuilds….. Just finished installing blackbox32 Works kinda okey….. Getting a lot of red ! On the box…. Sometimes after 1 min when on Sometimes nothing… might be wiring… but thats not what i need help with…. Its the probe…. For some reason it only worked once yes once…. Now all it does is goes down towards the plate ( cheap plate ) and when touches it stops like it should The light goes on on the box… and thats it…. No movements after at all…. cant move any axis…. Unless i press stop unlock …. And if i do stop it then it shows an error…. After reading some post i took many pics lol Just so you can see…. Ill try putting pics as i was trying to run it…. its a brand new laptop Like i bought it today lol My old one was lagging when ran the program… limit switches not enabled… All motors running my personal direction But not that i think… just came up wit a question on top of the other question is it possible that the controller is not sending an equal signal to both Y motors? Cuz it seems like they dont move exactly same time… maybe like millisecond difference … I can see the x gantry move sides separately linda can see it…. Or its just me??? going back to probe…. Also i have another touch probe as u can see in the spindle…. That doesnt seem to work at al…. Any ideas? please let me know… as im bored and hate reading lol
Needs a firmware update: See section 7.1 and 7.2 of the X32 documentation: docs:blackbox-x32:firmware [OpenBuilds Documentation] And docs:blackbox-x32:firmware_changelog [OpenBuilds Documentation] Probably just loose setscrews on the shaft coupler See docs:blackbox-x32:currentadjustment [OpenBuilds Documentation] Any 3rd party motors, or just ours?
If they aren't ours, do check their electrical specs (inductance, resistance, etc) to be sure they are a good match (as close to the specs of our motors - the better)
Not from your description of the symptoms. Run the flashing tool as advised, from your CONTROL 1.0.342 If you haven't done it yet - it can't do it by itself, and the BlackBox left the factory a couple months prior before the update even existed (came out 3 weeks ago). Based on the fact that you report the hang and you haven't updated it yet - then to us it seems logical that it is still running the factory image, which had a bug in grblHAL itself.
okey... restarted everything did restore of the settings for motors and work z works all probes for z work
somehow everything works so far.... and love the old touch probe that does everything.... question i have is there code/button i can make so the probe checks the center of a circle? as that probe can do so... i remember i had it set up in mach ....but how do i do this in ob?
See earlier And related to that See custom macro in Getting started with Javascript Macros in CONTROL / Library of Macros created by the community
That's not the tool head pins. But the 0-10v output. Seperate plugs. Be specific about which you are working with
Refer to docs.openbuilds.com and do things right. Random "lets try the nonstandard thing" may lead to a damaged blackbox. The other outputs are all documented for their respective uses. 1) 24v PSU on? 2) measure and adjust 0-10v output exactly as described in the docs 3) if multimeter says you get 10v with M3Sxxx where xxx = value of $30 then BlackBox is set up 4) only then do you approach the VFD - otherwise it becomes a blame game. Seeing the multimeter result in (3) as OK, then if you have issues you know its more likely VFD parameters
I do get 10v but not in tool pins… only getting 3.1 -3.2v nothing changes when m3sxxxx xxx I have done vfd setup as per instructions on ob… maybe ive missed a setting in ob?
ONLY the 0-10 output should show (as labelled) up to 10V The other pins (Enable, PWM, etc) are 3.3v logic pins. They have OTHER uses (like Diode laser on PWM, IOT relays on Enable, etc). Not to be used for a VFD! (imagine how quick you'll fry the MCU by hooking a VFD terminal with a 24v pull up to a 3.3v logic pin! Please stop doing that, warranty won't be applicable) If you measure 10v at the 0-10v pin with M3S<max rpm> then no, you did not, and we are working fine. We cannot get too involved in VFD itself as we don't supply that, but refer your manual, and cross reference the Write ups linked to in the docs. Setup input terminals, tell them to expect 0-10v, remember your DCM/FOR jumper wire (labels differ between brands) to "arm" the VFD, configure Min Freq properly so lower than minimum RPM speeds doesn't turn it on etc.
I didnt hook up the vfd yet… like ur manual says …. Till i was sure it puts out 10v…. Ur manual states that vfd goes to tool pins…. How is that 10v? ive done everything what ur manual said…. And stil not sure if i should even attempt to hook up vfd cuz u are scaring me… ♂️♂️♂️
The picture in the docs shows exactly what to do: Make sure to look at the Blackbox X32 docs. Not the Old 4X's docs. The 4X had a single 4 pin Toolhead plug. The community contributed writeups were probably all BlackBox 4X but of course adapt to the new plug (same signal, just seperate plug now). We don't document VFDs as there are too many and we don't sell them at this time
So confirm, you are getting 10v out of THAT connector (yes or no?) the plug in the picture labelled 0-10v - when setting spindle speed to 100% (use the Tool On menu in CONTROL if in doubt on commands) Repeat test with 50% (5v+- etc) for example too to see how it works. Multimeter only
