Keyboard shortcuts to change jog isnt a solution for you? Some people dont know they exists so really just making sure you do.
Thats what Grbl uses: see the "Feed Overrides" section under gnea/grbl Click on Tools and Wizards, customize Keyboard Shortcuts. No one clicks the screen (; once you adapt to keyboard usage
I may not had made it clear that I mean the g-code command 'F' and not the jogging speed. While cutting, I may want to increase/decrease the cutting speed but I also would like to know the real number I'm changing to. Keyboard shortcuts are not an option right now since I'm using an old laptop, and a heavy one at that, and I can't lug it around.
I ran into a minor issue last night using version 274. Not sure when the pop-up got added to indicate run time, however, that popped up with about 10 lines of code to execute. When this happens, the pause and stop buttons are no longer active as it thinks the job is complete. I was using the surfacing wizard and the last 10 lines are the framing pass and if i were to need to stop the machine, i had no software buttons to do so. I am not sure what triggers the pop-up to come up, and i no longer have the g-code as i don't think the surfacing wizard saves anything. I am sure it is reproduceable.
Job is "complete" when all of its been sent to Grbl Grbl has a buffer of about 10-15 moves ahead (to keep planner working) Only on those loooong moves of a surfacing job that you'd notice, 15 short moves will be over in no time. In that state the big hand shaped abort button can still stop it if things go wrong.
Thanks Peter, I figured it was something along these lines. You are correct, on other jobs it is a non-issue, just found it interesting for that application.
I've experienced an issue since upgrading to the latest (1.0.274) build of CONTROL. Connected to a Blackbox. When I first connect, jogging controls work as expected. I then perform a probe using the OpenBuilds XYZ probe. After the probe, jogging from control has issues. No matter what increment I choose (.1mm, 1mm, 10mm, etc) it jogs roughly 10mm. On all 3 axis. I say "roughly", because it's not exactly 10mm. One time it might b 9.73mm. Next it might be 10.15mm. (Prior to the probe, jogging 10mm moves exactly 10mm.) I notice the issue a day or two ago, but the first time it happened, I called it a fluke. But it happened again today, so I started experimenting to try to reproduce. Happens every time after I probe. Not saying I had didn't have the issue before, but I just noticed this a day or so ago, right after updating to 1.0.274.
Sounds like you may have "continuous" jogging selected. Switch it back to incremental. Edit: Hmmm, maybe not since you can select the increments. I know I had opened up a issue where it would stay in continuous if you opened the probe window but cancelled it by clicking outside the window. I think that was fixed a few weeks ago. I've only probed Z since then and havent had any issues. Peter?
You may be on to something... I took a video of the behavior in case someone wanted to see it. Just took a look, and it looks like the slider did move over to continuous, but below that, it acts like its still in incremental. And as a note, I didn't cancel out of the Probe wizard, but completed it. So it looks like switching over to continuous after probing.
Here's a shot to show what I'm talking about... notice it's switched to continuous, but the increment selections are still there. (It was in incremental prior to probing.)
It switches to continuous when you launch the probe wizard because that's what it uses for the jog buttons that allows you to position your bit. Its supposed to go back to incremental after probing ONLY if you were incremental before you launched the wizard. Like I said, I've only used the Z probe and know that it doesnt have any issue. I haven't tested any of the other ones. Perhaps you can test it and report back? Edit: We posted at the same time. I see now. Peter will sort it out.
Like I said, I might had been having this issue before, I just never noticed. I only noticed this time because I had run a small job, and after it finished, I wanted to run it again on another section of my stock. So I was just trying to jog over to another spot and re-zero the X and Y.
any idea why prior to the update to 1.0.273 i could see the 3d Viewer and now i get this error on the same computer running an Nvidia GeForce GTX 850M. "No WebGL Support found on this computer! Disabled 3D Viewer - Sorry!" Standby as i update to the latest driver...
Probably not related to the Update (Refer changelog: OpenBuilds/OpenBuilds-CONTROL ) Double check that 3D viewer is not accidentally been disabled on the Troubleshooting tab under Application Diagnostics
THanks Peter, that's the first place i checked and bounced it on and off a few times to no avail, my driver is from 9/20 and the latest if from last week so hopefully it will change something.
Thanks! just installed 270 and it is there now! but i love updates...lol ok here is something even funnier, 2.70 detected the update to 2.75 and now 3d Viewer is back, not sure what is up with 2.73 but it was not detecting 2.74 yesterday
I have a suggestion for next version of OB Control: When I click on "Go to XYZ Work or Machine Zero", the CNC machine lowers the bit (Z-Axis) until it is about 1/8" off the material and then moves the bit to home corner (X and Y at 0,0), and lowers the bit to Z zero. That should be changed so that the machine moves the bit to X and Y home corner and then lowers the bit to Z zero. I ruined a plastic hold-down clamp. If the clamp is made of metal, I may break the bit.
Hi Mark, I have a problem with software setup. I created my drawing in inches, i run toolpath in inches, the program seems to be fine, but when i run it on the machine, it runs as if it is in metric. any idea what it is that i am missing? i'll attach the files. diameter should be 3.49"
Set your machines steps per mm. - $100-102 in Grbl settings tab - fine tune with Calibration Wizards under Wizards and Tools
I did it all, it is tuned just fine. However I figured the problem, I used Aspire to generate the code and I hade to change the machine I outputted the code for. Thank you for fast response.
If you want to use these post processors in Vectric Photo Carve you have to manually add them as this download is designed to automatically add load them into VCarve Pro and Desktop, Cut 2D, Cut3D and Aspire. Photo Carve is a 32 Bit Program whilst the others are 64 Bit programs. When you add them to Photo Carve in the Post P Folder you will more than likely get an error message from Photo Carve, but mine loaded okay and created the files with No Problems.
add G20 to the top of the file this tells the controller to consider the numbers in the file as inches Even better is to make the postprocessor insert a G20 or G21 in every file it produces for you. This is a basic safety requirement for Gcode files, each file must set all the modes it requires, so you can see in your file the G90 at the top. That is telling the controller to use absolute co-ordinates. Other normal header codes would be G17 ; use the XY plane for arcs G49 ; turn off tool length compensation and then G21 for metric or G20 for inch of course. I also see a T1 in the code. since GRBL based controllers do not support automated toolchange this is not a code we want to see in our Gcode. I am now wandering if you have selected the correct postprocessor for GRBL?
T1 is in the Aspire post processor for GRBL +--------------------------------------------------- + Commands output at the start of the file +--------------------------------------------------- begin HEADER "T1" "G17" "G21" "G90" "G0[ZH]" "G0[XH][YH]"
yeah, just as with fusion360, the Aspire people have never actually read the GRBL Wiki to find out what it can and cannot do.
Here are 2 feature requests- 1. Have a window with a library of my Gcode files so I can just click on them and run, instead of having to click-navigate-open 2. A method to alert when a job is complete. While SMS would be great, it's probably easier for you to just use a webhook or API call that we can integrate with our own systems. 3. One more level of jog- .0001 I used this often in my previous control software. I have been using Control for a couple of months and I really like it so far.
I just upgraded from .274 I think to .282 and noticed the 10" jog has been replaced by .0001. is there a way to get the 10" back?
