This is probably a stupid question, but When starting the spindle from the tool start button the software issues the command m3 s1000. How can this be changed so that the command can be m3 sxxxx where xxxx is an arbitrary speed. Thanks,
I think he means a speed that is not the maximum speed. 2 options 1) give a manual command for the speed you want in the Serial Console M3 S500 would be half speed (unless you changed the GRBL parameters) 2) create a macro for the speed you want, one macro for each speed
Thanks for the replies. I am new to CNC software and hardware. I know I can change the speed by inserting the command m3 sxxxx via the serial console. I was hoping there was a way to change the command that the tool start button initially inserts. I have not tried creating a macro. I am simply trying to avoid having to insert extra commands when starting a job. It is not essential, just a convenience. I appreciate your thoughts.
Your cam software should set the spindle speed - what software are you using to create your g-code? Alex.
Thanks for the reply. I am using Vcarve desktop to create the g code. I am not sure if the m3 s1000 command is inserted there or not. I will check it out. So far I have just added another m3 s16000 command when I start the job. I do notice that the rpm goes to 0 when the job is finished, so I assume that comes from Vcarve toolpath code. I am still trying to get a handle on everything. Thanks for your comments. Richard
Try setting your grbl settings to 6000 RPMs The vfd I set the minimum speed frequency to 100 Hertz vcarve takes over after that and once the g code is running you can use the slider to increase or decrease your speed I I also had to set my vfd accelerate and decelerate time 4 seconds Everything on my machine works really well though I did have to start the spindle using the coolant relay 2 Note my vfd is a y l 620 a, hope this helps!
I think what the OP is looking for is a way to adjust the default command from the dropdown in the Control software to be something other than 1000RPM. For most spindles, with the min and max speeds changed accordingly, this start button in the software becomes useless as 1000RPM is less than the minimum speed. A way to have that configurable could come in handy for tests/checks. I agree, most spindle speeds should be set within the file itself.
What are you using the relay to control? I am just sending the 0-10V signal to control speed for my spindle and it appears to be working fine. I have the same VFD you mention.
Just a heads up Our default / recommended machine config is an IoT relay + Router , default grbl setting of $30=1000, and CONTROL, being aimed squarely as at the very beginner, has a very strong "No config required" mandate. VFD spindles are a minority around here still. As its more advanced it in use, its also expected users who opt for them, are a little more clued up on what it takes to use them / setup post processors correctly, etc. That said, - we're always happy to make a plan that fits above mandate - and accordingly I added Tool On menu: Automate relative to $30 settings in Grbl · Issue #142 · OpenBuilds/OpenBuilds-CONTROL to the Todo list (No config needed, read $30, scale accordingly) - its in the todo, so will try get it into next release (Expected later this week)
Here you go: Release v1.0.243 · OpenBuilds/OpenBuilds-CONTROL or later Automatically scales according to gnea/grbl (for example if $30 = 24000, then the 50% menu sends S12000, etc) 11
My version of black box is 1 year old I am running 3 horse water cooled spindle, I have my relay connected to forward and ground, tool head wired Tu VI 1 and round, I turn on my vfd which also engages my water cooling, spindle not running and then going to the software and turn on M8 which engages the spindle I tried other jumpers but this one worked, so as Mark would say if it doesn't itch don't scratch it, I believe that the relay tells the vfd to look for the tool head input I might be off on this but it works I also have my grbl settings set to minimum 6000 RPMS 1000 did nothing 6000 a good round number maximum 24000 RPMS ,, vfd is set to minimum 100 Hertz which is 6000 RPMs maximum 400 Hertz which is 24000 RPMs. When the G-Code is initiated the RPMs are controlled by the software you can then use the slider to speed up or slow down the spindle, I have also written to macros one at 16,000 and the other at 18000. I don't know if any of this makes any sense took me awhile to get things straightened out On another note if you're having trouble with the new version of vcarve you need to go back to an older version copy the grbl G-Code that you're using and paste it in the g code folder of the new software when asked you if you want to replace yes. good luck Stephen
This all makes sense to me, i have a jumper wire from ground to fwd rather than running it through the relay. The PWM output from blackbox then goes to the VFD to control speed. When M5 is sent, it must put that to 0 V. Since i have my minimum grbl speed set below my minimum spindle speed in the VFD, the spindle stops as the PWM is scaled between your min and max speeds. I like the idea of running the enable through a relay in case something gets messed up with the settings or signals in the PWM. Again, mines working so I'm not sure i want to touch it, I was just curious of how you were using the relay for the spindle.
I burn up one vfd that was a better then this one trying to use Mach 3 what a wiring mess, in that case I jumped from forward to ground and was determined not to do that again with this vfd, I was determined to use the relay and as I have said before I am using the coolant relay M8 and M9 I couldn't get M3 and M5 to work, so now when I use M8 my spindle turns on and goes to my minimum setting which is 6000 RPMs from there the G-Code takes over and you should be able to increase or decrease the speed and Seed rates and at the end of the code spindle stops so I can change tools, the slider in the software is counterintuitive being that 100% is your minimum speed oh well I would like to thank Mark and Company for developing and staying on top of the black box it's been fun using it and what a difference between it Mark 3
nope, that is wrong <-: the PWM signal is a positive going pulse that is short for low speed and long for high speed. so there must be a VFD setting that is telling it 'invert that', and that setting needs to be undone (-:
Hi, First, thanks for making this CAM software for the Blackbox, I've managed to convert a Ventura61 CNC to the blackbox to keep it going a while longer (windows control box went to ****!), but have a small suggestion (maybe I'm configuring wrong..?): I see on startup that the spindle speed starts up to that in the Starting Gcode, which is OK once you realise, but then the first lowering starts before the full cutting gcode spindle speed is read - before I realised to put a reasonable speed (for wood cut) in the Starting gcode, I bent a bit as my very first cut the spindle was running at 1000rpm when it was lowered 3mm into the wood.. at that speed the spindle just stopped as it jammed, and even thou it then got a S8000 before moving in XY, it could not start the spindle from the blockage in the wood, and started to drag it sideways, bending it... If the CAM software had put the first spindle cutting speed command BEFORE lowering the Z axis, then this would not have happened.. it is after this that I learned about putting Start gcode speed, and I have put S8000, so, for wood (and first tests), all is good for now, however, when considering that my spindle can go to 25000, and that depending on the material I will require different start speeds, I will HAVE to remember to change that Start gcode in the settings to at least the same as I need for the job I wish to do - it would be a lot safer that the CAM software puts the very first cutting spindle speed BEFORE the first touching of the material in the gcode, as S8000 is ok for wood, but will probably also jam on aluminium (or some other material) at that speed and also possibly then not be able to ramp up to the full cutting speed before moving in XY, so will bend again... :-( To resume, from what I see in gcode made by CAM software, Start code first ramps spindle speed, but FULL cutting speed is not applied until AFTER the first Z lowering into the material takes place, and if my Start gcode is too low (default S1000) then the bit will jam and stop, and will not be able to start again before first XY movement drags and bends - suggestion: that CAM software places full cutting speed in gcode before first Z move. Thanks! PD I am learning to use Fusion360 to make gcodes, but as yet have not managed to try this out, so I do not yet know if this issue would also be present with Fusion360 - I doubt it will, or it will be more complex the way it is implemented (is a much more complex program to create toolpaths!!), but I will revise the gcode produced before using, and will get back with my observation ;-) PPD also, as far as I can tell, at the moment the full cutting speed written to gcode by CAM is that which is in the settings as Power/Speed Scale max, so also have to change that to 8000 when I wish to have spindle at 8000 - I imagine it is already a ToDo for you to add this in the workspace vector config toolpath window (not from settings) the chosen speed for the present job (next to XY feedrate, for example), so can leave the max settings at 25000 (in my case) - this for a newbie like me with a VFD controlled spindle would complete the simple experience with all the necessary controls on hand for each individual job ;-)
As our standard config (recommended) is a Dewalt+IoT Relay setup, CAM doesn't really cater to the variable spindles as much - it's a free, beginner CAM for the very beginners, ideally with mostly standard setups. VFD/Speed adjustable spindles etc complicates things for the regular 99% userbase (compared to setting the dial to 3 and go) Do add an enhancement request at OpenBuilds/OpenBuilds-CAM though and we'll see what we can do
you should also put a G4 Pn command after the M3 S8000 G4 is a delay, Pn where n is in seconds so G4 P3 will delay for 3 seconds. useful to let the spindle get up to stable speed.
I encountered a problem today with my machine. I switched from my HP to my Mac for starters. Once hooked up and everything updated and installed, I tested the machine manually and everything turned on and off, moved, and accepted files as it should. Then I go to run a test job and the machine runs the correct path as it should, the spindle just doesn't turn on during the job. I can stop the job and turn it on manually, but as soon as I start it back up it turns the spindle off. It, also, will not let me turn it on manually during the run time. Please help.
Plugged it into the wrong socket on the IoT relay? you want (and had before) the Normally Off, so it can get turned on by the signal
Regardless, check the labeling on the IoT relay and make sure its plugged into the correct one (there is a mix of normally on, Normally off, and always on sockets. What you describe sounds exactly like having the router in Normally On instead of the intended Normally off socket.)
The IoT relay that controls power to your router? See docs:blackbox:connect-dewalt-iotrelay [OpenBuilds Documentation]
Is there a setting or something that I may have accidently changed or does the program behave differently because it's a Mac. I hate to be a bother, but I am lost when it comes to this stuff. I finally with your help figured everything else out and this is the last step to be fully operational.
Which program? So you aren't running any of standard setups? Then please do mention that, and tell us what you are using then
Does exactly the same on win, mac and linux Sure you have exactly the same toolhead setup on the mac? Compare g-code output between win and mac
