I was getting started with OpenBuilds Control software. What is the "Size Check" feature do? I clicked on it and my router gantry started moving - I E-stopped it before it quit moving.
Draws the bounding box of where the job is in XY space Helps you to check if the job fits your stock. Or for laser, helps to see if you are right where you want to burn Position it above the workpiece, do the setzeroes. Then run checksize after loading gcode
I'm having an issue with this feature recently. When I press check size the gantry will take off on the x-axis and not stop until I hit the emergency stop. If I just run the program without checking the size it will run fine and cut what needs to be cut. @Peter Van Der Walt any idea?
Sweet, so next quick test. Recently we introduced mm/inch, could be that Send a G21 from the Serial Console before Checksize and see if that fixes it? If it does i know what to fix when I get to work later (;
I checked and its not inch/mm Can you post the gcode file? Maybe something in it adding to the 3D view's boundary box, beyond where the job is.
Forgot to mention. I created the file in Aspire using the Grbl (inch) PP. Note: I created GCODE in OpenBuilds CAM and it is acting correctly. Is it the wrong PostProcessor? Note 2: Went back into Aspire and changed the PP to Grbl (mm) and it works correctly. Not sure I like it that my 3D shows to be in mm in OpenBuilds Control software.. I am an inches type guy.
mm gcode does render a little better in the 3D viewer, but thanks for submitting a test case file, will add it to the list of edge cases and see if we can improve viewer for inch gcode in future versions
As an update from my testing. If I set my start point as the center of the board and use the Grbl (mm) PP, it works fine. It outlines my carving space. If I use the Grbl (in) PP, the gantry takes off to the front left corner until I abort it. Sending G21 seems to have no affect. Definitely seems to be the difference between inch and mm.
No updated code available yet, keep an eye on the Changelog in the troubleshooting tab, you'll see a note there when improvements has been made to inch mode/check size
Updated the codebase with a fix for the Checksize when in Inch mode: It'll be live in v1.0.207 and that is expected to be released maybe today, or tomorrow at the latest. Thanks for reporting the issue and even more thanks for your patience in waiting for the fix! @Alex Chambers FYI too - the Vectric Inch mode post will now play nice with the updated Checksize fix, so we can recommend it without fear now (referring to Aspire to OB Control)
Hi, after update of Openbuilds CONTROL to v1.0.2015, the check Size don't work anymore. Also, in Wizards & Tools, Surfacing, after input all, software don't let see the work in consol. When run the Job he do it fine but you can't follow the process.
Hmm, wasn't any direct changes in that last couple versions, so 1) press F12 or Ctrl+shift+I to open devtools 2) Check Console tab for clues while using these functions I am on leave today but will check deeper tomorrow
Either 1) accidentally disabled 3D viewer from Troubleshooting tab > diagnostics menu Or 2) incompatible GPU Checksize depends on the 3D view to calculate extents of the job, and of course the preview of the surfacing job as well.
Thanks Peter, it is not a accidentally disabled 3D viewer because I check it. Why it work with version v1.0.214? Can I download the old version?
Newer versions of Electron/Chromium updates the blacklist of bad GPUs (Google Groups) as they build up lots of reports from users with a certain GPU that misbehaves / doesn't properly support WebGL, etc: What GPU do you have in there by the way? It could be a case of just updating your GPU drivers, when was the last time you did that? I assume the day the PC was built or last reformatted and never again since? The blacklist takes several factors into account, driver version being one of them
My viewer works after I upgraded. The only issue was the upgrade failed so I installed from scratch. Had to reset some GRBL and re-calibrate. I didn't use the Check size. I will try today.
Grbl settings is not stored in control. Its stored in the EEPROM on the Atmega32p on the controller running Grbl (; So no need to change those if you are just working with the host applications
OK Thanks. I knew that but assumed that when I re-installed it that it sent default settings. What happened was, when I opened CONTROL, it said there was an upgrade available and it upgraded. But when I went to open CONTROL, none of my shortcuts worked from the Desktop or from Programs. I just downloaded it and installed it. I am running PC with Win10 in case you wanted to know.
Hello, Greetings from Johannesburg, South Africa. I've recently built a controller for a NEJE 7W laser, 'cos it comes with a proprietary board which is pretty useless unless you want raster or very limited gcode usage. Anyway, it has got new life with the OpenBuilds control S/W and an Arduino/CNC Shield, which runs beautifully. Two issues to mention: 1. The 'Size check' does not turn on the laser - so it's a little difficult to see the physical boundaries, or line up edges. Perhaps a drop-down to allow the choice of tool activation? And possibly keep it running the perimeter until stopped to allow adjusting of the workpiece. 2. The 'Tool On' does provide this drop down - but seems to be out of scale as even at 15%, the beam burns material and I need to adjust with the power slider to prevent marking the work. Of course - then I forget to put it back to 100% I have created two macros to turn on the laser at 1%, and then to turn it off again - this is my intermediate fix. Great work, Rgds, Brian
Agree, but then if there is a way to set the modulation, the non-linearity could be manually adjusted. On my macro I set it to 1/255 (M3 S1) and then it does not burn - although the dot is clear and easy to focus.
PWM Freq? See gnea/grbl We just use Grbl as-is, where the PWM is a linear response and works perfectly with well designed drivers (JTech, Optlaser, etc) We provide settings down to 5% - for most diode lasers thats perfect Thats what macros are for. Customize away You can always use the Javascript macros functionality to a) turn laser on, b) checksize OpenBuilds/OpenBuilds-CONTROL and c) turn it off again You can do a looped run too: see Help getting started with Javascript Macros in Control... for a similar example
Ah, thanks - that'll work. Ill delve into that code and write a macro to do it in one action. I tried the modulation with other GRBL controllers and they all appear to be quite linear - my feedback was simply an observation - no criticism intended. Thanks again for an excellent utility.
Hello, I've been struggling with the latter part of turning off the laser and am asking for help please. Initially I had a socket.emit('runCommand', "M5\n"); after the 'runJob' but that created an error 09 - Alarm or Jog so then I tried to wait for the job to finish but just cannot get it right. Here is the macro with various options commented out: var bbox2 = new THREE.Box3().setFromObject(object); console.log('bbox for Draw Bounding Box: ' + object + ' Min X: ', (bbox2.min.x), ' Max X:', (bbox2.max.x), 'Min Y: ', (bbox2.min.y), ' Max Y:', (bbox2.max.y)); var feedrate = $('#jograte').val(); if (laststatus.machine.firmware.type === 'grbl') { var moves = ` $J=G90G21X` + (bbox2.min.x) + ` Y` + (bbox2.min.y) + ` F` + feedrate + `\n $J=G90G21X` + (bbox2.max.x) + ` Y` + (bbox2.min.y) + ` F` + feedrate + `\n $J=G90G21X` + (bbox2.max.x) + ` Y` + (bbox2.max.y) + ` F` + feedrate + `\n $J=G90G21X` + (bbox2.min.x) + ` Y` + (bbox2.max.y) + ` F` + feedrate + `\n $J=G90G21X` + (bbox2.min.x) + ` Y` + (bbox2.min.y) + ` F` + feedrate + `\n `; } else { var moves = ` G90\n G0 X` + (bbox2.min.x) + ` Y` + (bbox2.min.y) + ` F` + feedrate + `\n G0 X` + (bbox2.max.x) + ` Y` + (bbox2.min.y) + ` F` + feedrate + `\n G0 X` + (bbox2.max.x) + ` Y` + (bbox2.max.y) + ` F` + feedrate + `\n G0 X` + (bbox2.min.x) + ` Y` + (bbox2.max.y) + ` F` + feedrate + `\n G0 X` + (bbox2.min.x) + ` Y` + (bbox2.min.y) + ` F` + feedrate + `\n G90\n`; } socket.emit('runCommand', "M3S1\n"); // Laser on minimum power socket.emit('runJob', { data: moves, isJob: false, fileName: "" }); // socket.emit('runCommand', "M5\n"); This was the first attempt to turn off laser - it works as standalone macro // console.log('Running mode: ' + ((status.comms.runStatus)); // Complains bitterly about 'Uncaught TypeError: Cannot read property 'runStatus' of undefined' // while (status.comms.runStatus = 'Running' ) {}; // socket.emit('runCommand', "G4 P0.5\n") // This also creates an error 09 var lzrOff = 'M5\n' socket.emit('runJob', { data: lzrOff, isJob: false, fileName: "" }); TIA, Brian