Ahh OK, i see yes, with soft limits enabled, we need the Grbl settings present to know the values of Max Travel settings - will bring that into Jog too Remember that the Jog Widget is a thing on its own, missed that part, thought you were talking about control itself, only with the screenshot did I realize, and then go back and saw the above means Jog widget If you wouldn't mind, it helps if I know exactly where you have an issue
Sorry if I was not clear about that part. Defiantly have quarantine brain. That is exactly what I mean, in the mobile wizard.
Give this one a go: AppVeyor (Mobile jog's code is now aware of the Grbl settings, previously it did not)
@David the swarfer Worked on some progress toward that goal (; v1.0.229 or later (not released yet) We will document the available variables, functions, and some samples with Math soon Beta of 1.0.230 if anyone wants to play with the JS macros yet AppVeyor Press ctrl+shift+i to open devtools, added the most important entry points to a note there for you. Explore from there, and shout if you need anything
I am on the latest version of OB-Control but I can't get the keyboard shortcuts to work. Nothing happens when I press the keys. Ctrl+Shift+b should move the spindle away so I can load a new board but it only works if I click the macro button. Anything I am missing? Thanks. Josh
Lol! Though in this case, its simple enough that its not out of reach for most (with a little documentation and examples) , all the internal logic is already in js, so easy to call on, and its way better than inventing our own scripting language for Macros
@Peter Van Der Walt installed v0.228 on my control laptop, Xubuntu 16.04 would not run until I also did a "sudo apt update && apt upgrade" - my bad, have not done that for a while. and then set up my preferred shortcut keys. could not select the 'goto xyz zero' field for edit, so it stays at 'del' which I really don't want set up my xbox type joystick for jogging (map the keys to the shortcuts in qjoypad) joy! continuous jogging just wonderful and can switch between incremental and continuous BUT once switched to incremental the keys (actual keyboard nor joystick) do not move the machine though the onscreen buttons do change colours. clicking the screen buttons with the mouse does move the machine. so, maybe some onclick /onkey etc events have not been linked where needed?
Jog controls via the arrows on the keyboard is broken for me. I'm on Windows 10. Worked up till the .228 version, tried the .230 beta as well. You can see on the screen like it's being selected but nothing works. Have to actually put the mouse cursor and click the mouse button instead of being able to use the arrow keys for X and Y.
I just updated to v 1.0.231 and I noticed that you Incorporated a few of my requests into this release. I really appreciate your support. ( Macro keyboard short cut and File name in the tool bar) One issue that I am having since updating is the keyboard arrow keys are no longer jogging the motors. If I use the arrow icons with my mouse it works just fine. I noticed now when I use the arrow keys from the keyboard the icons on the screen light up as if I hit the icon with the mouse but motors don't move. One additional observation is that the keyboard arrow keys do not work in incremental mode but they do work in continuous mode. I hope that helps to sort out the issue. Best regards -Mike
Hello Peter, Yes I tried .230 and still the same result. In continuous job it works, though I seem to have a few instances where it was continuing to job even after I released the key. I rolled back to .224 and it's back to working.
Alright, v1.0.232 OpenBuilds/OpenBuilds-CONTROL "should" fix the incremental, keyboard jog, not working bug. Please test (at least over here it all works Fixed another bug (which was the reason I missed it yesterday) - if you changed to/from inc/jog using keyboard it wasn't saving the state for a next run, only with mouse. That's been fixed too so now if I set it to Incremental via Keyboard, and refresh, it stays on Keyboard
I confirm this resolves my incremental jogging issue. Thank you! This in on a desktop Windows 10 machine with wireless keyboard.
Sweet, I did a little code cleanup of all the little quick-fixes over the last couple days - good thing to cleanup after a large coding stint like this to make future development easier, releasing as 1.0.233 Gained a couple fantastic new features added over the last couple days: XYZ Probing with OB's XYZ Probe Plus and Custom Probes Made several improvements to Keyboard shortcuts (macros, go to console, added extra assignable shortcuts for gotozero, switching between incremental and continuous, cleaned up the code and fixed several little bugs) Updated Macros with new Icon selector, Keyboard shortcuts, Javascripting capability and prettier buttons Show loaded filename in Window title bar Improved touchscreen support according to best-practise (proper touch-event bindings Updated Mobile Jog page to support Continous Jog and other little improvements
v1.0.234 is in the pipeline: -1: Fixed the Right click menu in the Gcode editor to start the Simulator correctly -2: Smoothed out G2/G3 Arc simulation (and added the Line indicator to assist in knowing which line is being simulated) - 3: Added a check for USB Selective Suspend settings to Troubleshooting tab to aid troubleshooting without having to resort to Windows Commandline
im still having problems installing the last couple of versions,, Just brings up an transparent window. Back to 207 i guess :/
Or... help us find why your PC likes the old version, and not the new versions (between 1.0.207 and 1.0.234 a LOT has happened, so not so easy to guess, though we did in that time update the Core electron dependecies Electron | Build cross-platform desktop apps with JavaScript, HTML, and CSS. - ie later versions of Chromium etc). If its something we can fix we will. If the issue isn't your PC... - Have you tried it on a different PC? - Are all your drivers up to date? Chromium (part of electron) for example maintains a Blacklist of old/outdated/buggy GPU+Driver combinations where it got too many reports of that combination causing hardware crash events. - If after updating drivers, you still have issue, Check the debug log - Quit OpenBuilds CONTROL from it's System Tray icon, right click, Quit - Edit the shortcut you use to start control, and copy the target - Open a Command Prompt and run "set DEBUGCONTROL=true" to enable the flag to print the Debug Logs - and paste the path to CONTROL, run it: This will show you a log of what the backend is doing, might contain some clues why Chromium isnt initialising on your PC Is the PC is particularly old? Specs?
Hello, so I've been looking around a bit but haven't found any info on my issue. I just finished putting my Lead CNC with the high Z mod together, I assembled the Black Box and power supply as per instructions. Now I'm at the software and connecting part and Openbuilds CONTROL v1.0.234 is not seeing the machine at all. When I plug in the usb the status goes from 'waiting for usb' to 'FTDI USB to Serial COM3' which it says in the video is not the right one but it's the only choice. Needless to say when I try it, it doesn't work. I tried installing the drivers but nothing. I also tried it on two different machines. Please help!
Disconnect everything from the Blackbox except USB and try again If it connects, something is wired incorrectly, shorting V+ to Gnd preventing board from booting. Likely limits, compare your wiring to docs openbuilds.com
Yeah, just tried that. I tried it on four different computers and then finally took the Black Box off to check my wiring and jumpers just to make sure nothing looked weird or off and I figured it should still do something even if nothing is connected but still nothing.
Borrow a jumper from for example Relay, and put it over USB MODE (if you have a v2.7 board) temporarily for a quick test? (bypassing mux chip) Try reflashing Grbl from Wizards and Tools > Grbl flashing tool. Both, still with only USB connected. Nothing else
