Same UI. Fixed bugs like touchdown that wasnt included, no more runaway Continuous jogs, etc And this is a bad strategy. If you find something broken, report it, so it gets fixed. Leave the past (old versions) in the past where they belong
Exactly reported after 226 you say: And what does the changelog say for 227: It's almost like we listened to you So yeah, stop using outdated v224 (; Have a read through OpenBuilds/OpenBuilds-CONTROL and see all the improvements since then
Lol! Too funny! No man, you have entered the the list of awesome people who help test and report bugs though, without which CONTROL wouldn't be great. So I assume you tested latest version and all is well again?
Yes - all good! I installed the latest OBC version on my touch screen tablet and I was able to jog with no issues. Now I wish my UI looked like this
We hear you again but sadly on that one, we have some other plans And yes the plans will help with that too
Hello, i just finished setting up my 1515 and in going when running the hello world test from Gcode generator i immediately get this error when i run the job, seems to me like it thinks my table is smaller than it actually is. i have homed all any ideas? tia update:research research research, searching forums found the grbl settings page, just not sure what those are there for if i am pulling down a config for my machine and the one for the 1515 says my work area is something like 1170x1250x90. not sure but not having a good experience with this system so far...
Are you homing your machine first? You need to or it has no idea where its at and wont calculate your machine size correctly. Also, check out gnea/grbl. It has all the information you need on the settings and what they are there for. It will save you a ton of grief.
Select profile, click Save. Unless you save the profile to your controller, the firmware would not know the settings.
So i assume this affects mostly touchscreen users right? (keyboard jogging has become so stable I almost considered removing the UI buttons, but for touch, alternative accessibility inputs, etc, it's best to keep it.) I'd prefer to keep the XY widget looking like it does now (subtle hint reminding you that the cursors on a keyboard looks the same, thus introducing keyboard jogging) I have some extra vertical space (slight change to DRO introduced some space) - would adding more margin between the buttons help enough with the accidental finger accidents? We added margins on the Mobile Jog widget for same reason and haven't heard any complaints since anymore. And we can add some extra space between those and Z for you. Also with the Z+/- spaced further apart vertically.
I'm willing to try out any suggestions..... I personally do not have any issues with the Y or X - just that the X+ is too close to the Z and if I am moving at 100/10 and fat finger the Z I have had the z crash before. I am guilty of not trying to use the mobile access. I know I am giving you a hard time, all in good spirit. I think any extra padding would help. I will check out the mobile here this weekend
With the new padding, the tabs-holder overlaps jog speed settings. I can obviously resize the window to fix, but thought you should know.
AWESOME ! I will download it today and give it a try. Peter, side question.... my windows tablet has one 3.0 usb port which is connected to the BlackBox. I am toying with buying a 10 Key Numerical Keypad to try it for jogging if that can be done but I'd need a USB hub to run both. If you can comment, is this a viable option, meaning I should not run into an issue using a USB hub. Out of curiosity -- what device / screen resolution are you using?
That screenshot was from my 34" desktop monitor which is 3440x1440. On my machine I run a 12.3" touchscreen @ 1200 x 1600 at full screen in portrait mode so I get more simulation area
About to give this controller software and black box a go. My 2 other systems run WinCnc. Anyone know if this controller software can simply run the .tap g-code file I already have?
If your GCODE is Grbl Compatible, yes: See gnea/grbl and docs:software:overview [OpenBuilds Documentation]
One thing to check with *.tap g-code is the header code - in particular some post processors that output *.tap do not include a G20 (inch) or G21 (mm). The blackbox starts up in mm, so if your code is in inches it will come out rather small if there isn't a G20 at the start of the file. You can open your g-code file in a text editor to see. Alex.
Thank you! Exactly the info I’m looking for to write a new format g-code header file specific to this new machine. And after a little reading, looks like g28, g91, g92, g90 commands are the same... Just need to figure out how and where to add federate...
