Maybe I'm just missing it on the screen but is there any way to get the current speed the machine is trucking along at? And I wouldn't mind a keyboard lockout. Turns out my wrist can take a nema 23 trying to peel it off my body. I should go wireless just so I can shut it off like the the little keyboard thing I use for jogging.
Not at this time in the UI (though the Parser is actually parsing it out and it is in the API) Not shown for sake of simplicity, remember Control is aimed at lessening the learning curve for beginners
I think sorting out the speeds you're actually running at helps the beginner set better values in their post processor. If I poke the slider up to 150% and that works great I can just jot that down and use that in the future.
Hi, My Blackbox Control Unit was working great, done a few cuts over a few weeks, Turned it off and not had it on for about a month, I turned it on to start a job and it updated itself, I did a restart, now the X and Z wont jog! any suggestions? Thanks
Very unlikely to be update related Check wiring, check for red exclamation mark LEDs on front. Define 'wont jog' for example - motor lock up when Grbl boots but doesnt respond at all? - motor wiggles in one place - motor does not lock when Grbl boots Check Serial Console for clues
Peter guess what, I uninstalled the update and everything works! Jog , the ability to move X Y Z fowards and backwards from the control panel. so it must be a problem with the update!
Thanks for the report. Will monitor Allow me to explain why I say it is unlikely to be update related: No one else had issue so far - refer to Github Release Stats (well over 2750 updates rolled out into the wild already, over last 4 days, if it was related, more people would be complaining by now. 1 report out of >2750 installs does not look like an update related statistic... ) If you really want to confirm, review the changes OpenBuilds/OpenBuilds-CONTROL - last two versions only added new machine profile. Nothing changed related to jogging. Version before that only changed Probe sequence to speed it up a little, before that some changes to support Pi4. No changes to Jogging in months Still curious what the actual answers to the original questions was - for when it does it again: sometimes one can extrapolate incorrectly. For example: what if X and Z was cutting out on overtemperature, you were maybe testing in the heat of the day with the current set too high. Come nighttime, you downgrade, and now it works. Easy to think its the reason, but could also be that is now cooler and thus the drivers didnt go into fault. Painting a possible scenario here, but see how those questions relate. Or you had a quick once off wiring short from loose strand near a terminal that put the drivers in fault mode. At the time you did the downgrade, you also cycled power (which clears the fault on the drivers) - again, coincidence. It might short again though So: what was it doing exactly when it wouldn't jog It would be good to make sure, if there is a wiring/hardware/setup problem that is not addressed it could come back, or worse, cause damage
Dear Gurus, I'm using a Bluetooth Keypad as a poorman's cnc pendant and would love to attribute keys for the .1 1 10 and 100 jogging functions in OpenBuilds Control. I haven't found a way via the shortcut keys assignments and I googled around, but I'm too newbie to understand how to do that with gcode... If anyone could point me in the right direction - I would be eternally grateful. Cheers ! PS I apologize if this questions has already been raised or if I'm at the wrong place to do so.
Wizards and Tools > Customise Keyboard Shortcut Key assignments but note that it takes two buttons: Decrease and Increase step size - that takes you up and down through the increments
Thanks for the quick feedback Peter. Not as sexy as .1 1 10 100 .... but if there isn't a gcode option, then I'll go for that.
Hi there. Is there any documentation on the API and what endpoints are exposed? Reason I ask is because I want to use a 4th axis for indexing (and potentially continuos motion) and am considering getting the UNO controlling 4th axis to command Gcode for machining to the BlackBox. The other alternative is to embed in the Gcode commands to send to the Uno, if that is even possible! Anyone else solved the Rotary 4th axis conundrum?
Simple and reliable with Wrapping Rotary Machining and Wrapping - VCarve Pro V9.0 User Manual Wrap around X or Y and plug indexer into the X or Y axis port
Can you do a macro? If so if you want point one just feed in four decrease steps, one mm would be four decrease and one increase, etc.
Not an option as is. But the workflow was planned around the numpad: / and * moves you between increments. You do your 100s, then 10s, last bit with 1s and finally dial in the 0.1s for example, you wouldn't be jumping around with it. Most people use Continuos jog for the big moves, probe to set the final zero
I have finally got my custom acro machine finished. Tested it today with the jogging function and all seems to be working like a treat. However when I click to run the homing cycle/'Home all', nothing happens and I can't do anything with it after - even the jogging doesn't work Look forward to some help Cheers
Visible behind the error I spot your mistake in your Grbl settings... $132 Z Max Travel should not be set to 0 thats the reason for the immediate error. You are telling Grbl its only allowed to move Z by 0mm. It homes Z first. Now onward. As this is an Acro, it does not have a Z axis: To disable z homing (which i assume was your intention?) see gnea/grbl or flash the 2 Axes build from Wizards and Tools - Grbl Flashing tool in control (easier than compiling yourself, we already did that for you) Loading our Acro profiles in Grbl Settings will also guide you through flashing the correct 2 Axes Grbl build (assuming if you did do a custom machine based on the Acro, loading the Acro profile first, then customising it, would have helped with this)
Thanks for that Would the best way to fix this be to re set up the firmware on control and customise it to my machine using the acro preset If I did the above, would I leave the z axis travel to the set/default amount. Also, how hot is too hot for nema 17 motors
I would do it that way (unless your build differs drastically) Yes, but make sure to flash the 2Axes version from the Flashing tool (or when you select Acro in the Grbl Settings window, it offer to flash it for you) - thats how Grbl handles it (refer the wiki link) - not by changing the distance Turn current about all the way down docs:blackbox:currentadjustment [OpenBuilds Documentation] for our NEMA17s - too hot is when it burns your hand. Warm is expected, Hot is not.
I have a issue with openbuilds not seeing the X axis limit switch , when I press each switch in turn they trigger except the X in diagnostics . if I try and home it doesnt naturally see the X limit. BUT I have come from UGS and it sees the switch fine and homes fine ? . I just went back to UGS to recheck and it is working fine . Is there a bug in V1.0.250 , the machine has no internet connection so not easy to upgrade
Its strange as all limit switches work and test ok in UGS and Commaders software , homing also works in both those. So it is not a wiring or switch issue. But if I use openbuild control it doesnt show it as finding X , finds Z and Y and Probe when testing. When I home it doesnt find the X limit as its not showing in openbuilds. As I said it homes perfect in UGS or Commander ??? got me confused
Homing is all internal to Grbl. The host does not check the pin, grbl does. CONTROL sends the “$H” command and grbl does the rest refer to the Grbl wiki for more info
