I'm going to tag in @Jason Moore - as he just posted a build the other day using the Door input as a Plasma THC Lead1500 Plasma Table - and he may be able to point you in the direction of how he modified the default Grbl behaviour.
You should use the G04 Dwell command in your gcode. you can specify a time to wait if you are doing a spot weld, or just a delay if you want to move the axes while arcing after an initial puddle is made. G04 G-Code: Pause / Dwell for Precise CNC Timing
Hi, uhm no. Im having a bit of problem to make the door sensor input pause and resume the ongoing job. As of now it does the feed and hold thing and I have to manually press "Resume job" after the weld is done. Did you have a solution to this? Thank you for the support!
That is a solution that could work if I dont manage to get the door sensor input to work as I hoped. Thank you for your answer!
Which firmware version are you running? There a few you can reflash. In firmware I switched door open pin with resume pin. Then connected my torch height controller resume output to the black box door open terminal. I also optoisolated my THC from BB because it runs at 24v and BB is 5v.
Ah ok, so I have to rebuild the software to a .hex file and reflash the firmware through Control? Is the door input then acting like a pause/resume pin? So for example, if door input/resume pin is 5V job pause and 0V means resume job?
Refer to the comments in Grbl's config.h to learn more: grbl/config.h at bfb67f0c7963fe3ce4aaf8a97f9009ea5a8db36e · gnea/grbl and grbl/config.h at bfb67f0c7963fe3ce4aaf8a97f9009ea5a8db36e · gnea/grbl and also grbl/config.h at bfb67f0c7963fe3ce4aaf8a97f9009ea5a8db36e · gnea/grbl
Thanks for tagging in Jason - and if i re-read your Build, you aren't using the input as DOOR at all, you were redefined the pinmap grbl/cpu_map.h at bfb67f0c7963fe3ce4aaf8a97f9009ea5a8db36e · gnea/grbl swopping feedhold (default pin used for DOOR too) and Cycle start. You do a feedhold command after triggering the plasma? Grbl v1.1 Commands · gnea/grbl Wiki then rely on the THC to send the cycle-start signal (thus not using the pin for both as the OP wants to, you mix software based feedhold with hardware based resume?
Correct. In my fusion 360 post I insert an M code forfeed hold after fire command is issued and then my THC sends back a resume signal to BB modified door pin terminal (modified in firmware to resume). Then BB resumes cut movement as normal.
Hello everyone. I have a wish for a function that I wish existed in the Openbuilds controller software. I would like a function when you right-click on the coordinate in the Gcode editor that you would be able to mark the coordinate in the gcode and right-click with the mouse and you would then be able to select "Go to the coordinate" so that the software automatically takes the coordinate and adds it to the gcode terminal just like the function that is already there called simulate from number, only that it does it live. Yes, I am well aware that it can be dangerous, but I use my cnc milling machine on a daily basis as a form of automation machine where I mill the surface of a plastic object and therefore I cannot simply transfer a file from e.g. fusion360 the plastic item may differ in size and the way the item has settled after it has cooled. I have tried to make a picture of what I think, it is added below. A very good day to all.
I think a better way is probing so you can set the WCS correctly from what you have and then run the Gcode relative to that WCS (or even more than one). something like this (yea, I know we cannot do the math in the gcode like that in GRBL, which is a pity)
I apologize for not explaining myself more clearly, what I mean is that I want a function so that you can go from step to step back and forth in gcode live so that the machine can be moved from step to step. At the moment, you can just mark the line in gcode and select copy and insert it into the serial console and then the machine runs to that coordinate. But it could be easier if you could just right-click on the line number and then select go to this line and so the machine moves there without having to post the line in the serial console manually. In the company we have Yaskawa MH50 robot arms there can jog to step by step.
Most sources I have seen agree that using full circles is generally bad and will cause some problems on some controllers. I have also seen R format arcs do very weird things with > 1/4 circle arcs. Which is why we avoid R format. That is why most posts do not output full circles, our Fusion360 post will linearize full circles and SketchUcam outputs no more than 1/4 circle arcs (it can do full circles, there is a hidden non-user option, but don't, just don't)
Yep. But its for a macro that i'm writing for tracing parts. The code will eventually be converted to a dxf.
Using Openbuild control software to run my 3018, amazing software and G-code editor. One thing I miss is to show completed path in different color rather than show all in red. anyone know how to turn this on openbuild controller?
Quick question about steps/mm in OpenBuilds Control- when a default profile is loaded (GRBL Settings -> Load Default Settings), does the default profile apply defaults for steps/mm? I have a LEAD machine and just reloaded the default settings- after doing so, I noticed that the steps/mm values for X and Y axes are identical to eachother, but the steps/mm value for the Z axis is different from X and Y. Are these default values that have been loaded? And if so, why might the Z axis default be different than X and Y?
Yes, as the profile should be used for initial setup - it sets all values to sane defaults. After initial setup, you can tweak away at it (all values are conservative) - and then use the Backup Settings button to keep a safe copy if you need to reload it later on. Our profile sets X, Y and Z steps per mm as 199.1 : OpenBuilds-CONTROL/grbl-settings-defaults.js at master · OpenBuilds/OpenBuilds-CONTROL If its different, it was changed after loading the profile (or if you forgot to click Save, ran calibration wizard, edited the field accidentally etc)
No reason to be rude. For issue 1: When the 3D viewer system is disabled, there is no 3d viewer tab. Please reinstall and verify. 3D viewer disabled 3d viewer tab not displayed and message in serial console. With 3d viewer enabled Peter, I can confirm issue 2. File open doesnt remember the last folder you opened a file from. I believe its defaulting to the last folder I opened from before I upgraded. I'll do a test by reverting to previous version, open a file from a different folder than it is now, then update. I'll let you know how that goes. Cant confirm issue with switching themes and ad going into full screen. Works fine for me. Takes 3 seconds to switch. Here's a screen recording
Can confirm that file open in .336 will default to last folder used before upgrading. Opened a new issue on github: File open doesnt remember last folder used. · Issue #270 · OpenBuilds/OpenBuilds-CONTROL
Thanks, we did upgrade version of Electron in backend - possibly they changed some behaviour. Thanks for the report
Is OB Control Software supposed to download new version automatically and ask me if I wasn't to upgrade?
