I currently have the relay in the Blackbox set to enable with the M3/M5 commands. I noticed that it will only close the relay if SXXX is set greater than 75% of the max speed set in $30. I feel like the relay should be thrown on any time M3 is sent, regardless of speed setpoint. Running verison 276
The popular discussion on here was the need to rather have the small jog distance than a large jog distance. Also, play with Continuous Jog, its much more convenient. Button down, go. Lift off the button it stops.
M3/5 = the PWM signal If you want to use the relay as an enable instead see the "Use spindle dir as enable" section on docs:blackbox:jumper-relay [OpenBuilds Documentation]
Thanks, I read through that last night, I wasn't aware M3 was a proportional signal. I was thinking the SXXX command was the proportional part of it. I'll get this jumper swapped!
Hi All, We have a Blackbox motion control system, and we are able to control it using the Openbuilds software. I would like to know if there's a way to interface directly with the Blackbox through a program written in C#. Our company is building a custom software for a new measurement tool and we would like to be able to control the Blackbox from within our custom software. Thanks
The short answer is yes, it's possible. You're basically just streaming gcode commands over a serial link.
Thanks for your reply! I'm quite new to gcode, I've always written programs in C# using Microsoft Visual Studio. Are there any online resources you could recommend to get me started?
See github.com/gnea/grbl, read EVERY page to understand Grbl first. The Interfacing page is of most importance, but a broad overview of everything will be needed to build a custom host application.
Can you not take a look at OpenBuilds Control that Peter Van Der Walt wrote and see if you can adapt/modify it to your liking and than post it as a fork on github (since it's open software)? It will save you A LOT of time!
Hi, is there a way to resume a job that oh i don't know got accidently aborted due to someone tapping the limit switch an hour in?.... edit: just found the macro section, now to see if there is one.
Only by hand editing the gcode (It needs a human to read, interpret and understand what to edit/add) - You need to bring in any modals that was set earlier in the job (coordinate systems, in/mm, plane, relative/absolute, spindle, feedrate, etc) - You need to write position moves to correctly position machine before entry into the first line of gcode - You need to make sure it won't crash
Yikes!, so it's pretty difficult but not impossible for the software to read the gcode line it was on and save line on abort, and then after alarm is cleared ask for a confirmation for abort or resume?
Not quite, because when the abort happens, you've lost position, the modals are reset, etc. Yes, software can do it, but we'd rather not take the responsibility just in case - with a supervising human taking responsibility... its not our fault
Ok thats odd, when it aborted the router shut off but stayed in the same spot, why couldn't the pause function be somewhat incorporated to the abort to save settings, oh well. Thanks
Grbl has several moves in a buffer, after the abort we clear that queue and aren't entirely sure how much of it did complete - because we keep the Planner full. Almost none of the Grbl hosts attempt to offer this feature, its just too risky
the 'easy' way is to use the editor built into bCNC. first install bCNC (with Python2.7) (does not have to be on your control PC, since you are not going to controll the machine with it) open the gcode select the Editor tab untick the block that have already been cut. save the file. transfer to controller cut..... here I have selected all the greyed out blocks up to and including the first hexagon cut that is highlighted in teal. you can click on a block and it will be highlighted so you know what is getting cut in each block.
Sry if this has been covered, I was unable to find an answer to my issue. OB Control Software works great on my LinuxMint 20.1 machine. But the issue is, if I check anyinfo on my settings then change something like bed limits $130 131 132, or any other. If i save settings then it would lock up the software and I will have to force stop software and then reconnect. Not really an issue but, was checking settings for my bother on his machine, while I was cutting. Did not save or anything. But it still locked up. Lucky me I will just let it run this cut over and catch up. How to keep the software from freezing up? Hope this gives you a better understanding. Running latest version of OB Control as of 2/13/21. Running on linuxmint 20.1 as mentioned above.
I been away from my router for some time and just started a new project. I allowed the upgrade to 1.0.284. It seems to run great at boot but becomes progressively sluggish to input or machine position status. After a 40 min job completed the 3d view was 3 minutes behind. And jogging commands sometimes execute but with massive delays. I seem to need to kill the program and reconnect, but I then need to home the machine effectively loosing my work peice reference. Please advise
1) try after a fresh reboot 2) you can selectively disable/enable features under Application Diagnostics on the Troubleshooting tab to see what causes it for you
Thanks, yes the first time it happened today I power cycle both the pc and router. This time I just did the pc. Everything seems to be working well. Machine has be running (10-30min) jobs since I posted with no obvious issues
No issue here on latest version on two 96 min jobs, I did see sluggishness and timeouts on my old pc but upgraded to a gaming laptop with SSD and zero issues since
Just to be clear, and maybe you understand this already, but you can power everything down and you wont lose your work coordinates. They are saved in the controller, not the PC.
I noticed something the other day running version 1.0.282. After leaving the program open on my computer for a day but inactive, it became sluggish. After checking, CONTROL was consuming 3+ Gb of RAM on my computer. I closed it and re-opened and loaded the same file and it was back down to 250 Mb and stayed there.
CTRL+Shift+I does not do anything. Locked up tight... After force quit, I can get into console session. But Im thinking it does not save passed errors, once it is forced quit.
CTRL+Shift+I when you first start up. Then go into your settings and try to reproduce the lockup condition. Hopefully you'll be able to catch any errors in the console then.
