Having similar issues. It will home and unlock, but everything else is dead. Won’t jog, phone or pc makes no difference.
All of my buttons are dead except “home”. The 10mm jog setting can’t be changed, and the machine won’t jog at all. Guess this is the boot to switch over to UGS
Sorry about that, pushed a fix for a different issue and it had a tiny little typo. Already fixed, don't jump ship yet, we fix these little things in no time at all. V1.0.141 will be up for download in the next 10 mins
Thanks for the reports guys. For future reference, if you ever find that an update breaks something, you can ALWAYS find the older versions over on OpenBuilds/SW-Machine-Drivers to keep you going. So you can downgrade for the time the app is broken, report the issue here, and we'll have it fixed within a few hours with a newer release! - we can very rapidly push out updates so its never a trainsmash. I've pulled v1.0.140 from public view so no one else needs to suffer again V1.0.141 fixes: (See Commit for details: v1.0.141 · OpenBuilds/SW-Machine-Drivers@5ab161a) - typo that preventing jog.js code from running (which handles all the jog related functions) - Activate homing if $22=1 (Doesnt worry about $21 Hard Limits anymore) - Smoothieware: Enable the HOME button (The code disables HOME button if $22=0 (homing disabled) on grbl, but didnt take Smoothie into account - which doesn't have any $$ settings to check - so if you run Smoothie the HOME button will not be grayed out/disabled) Grab v1.0.141 from OpenBuilds/SW-Machine-Drivers or via the built-in updates. Once again, sorry for the interruption! Was cool to see so many previously inactive users jumping up to say something's wrong though! Appreciate the response! Just goes to show the power of an active community, look how fast a bug was found and fixed!
At the moment we have no plans to include a pre-built wizard to do the XY probing. However, you can very easily spin up the functionality yourself, from the MACROs tab: 1) Create button to set X Offset = X thickness of plate: G10 P1 L20 X[X thickness of plate] (for example G10 P1 L20 X6 for a corner finder with a 6mm offset) (Add probe diameter/2 to the thickness too) 2) Create button to set Y Offset = Y thickness of plate: G10 P1 L20 Y[Y thickness of plate] (Add probe diameter/2 to the thickness too) 3) Create PROBE buttons: G38.2 [axes][distance] F[feedrate] for example G38.2 Z-20 F500 will probe down to Z-20 at 500mm/min, or for example G38.2 X50 F500 will probe right to X50 at 500mm/min (repeat for X and Y as needed) To use run the probe: If it stopped perfectly, hit your button to set the offset.
Thank you very much Peter! I tried v141 but on opening it, it doesnt see the machine and does not connect. I rolled back to v138 (thank you so much for posting the repository link!!!) and it works just fine.
Shout when you're in process - depending on the moves you want to make / etc I'll be happy to help with advice when you get to the actual sit-down-and-figure-it-out stage
Peter bCNC has internal variables that are available for use within manual/macro code. This allows you to do stuff like G0 X[maxx] which will move to the max X value found in the current gcode. I think the probe values are also available, which might allow for some interesting probing, particularly if math is also allowed: probe left of thing and set 0 probe right of thing and set value/2 thus finding the center in X, nice for finding the center of a hole.
I've been toying with that idea too... MACROs still has a lot of growth ahead (multiline macros, scripting, variables etc) - will add a git issue so we dont forget
Hey quick question with a minor annoyance I’m having. I’m creating my g code with aspire and then using openbuilds control as the sender. When I use the center as zero, it carves perfect and placement is spot on. When I try to use the lower left corner, the carves end up high and to the right, even shows up that way on the 3d preview. It’s not super off, maybe 3/4”, but it’s noticeable enough that I can’t use it. I’m not using an offset or anything, just never seems to like that lower left as zero. Am I missing something? Zero centered is just fine for most things, I’d just like to be able to use the lower left on some jobs.
Sorry, just saw this notification - The feed hold and abort options will trigger and hold until the offending event is completed/cleared. In this case it sounds like the driver is over-heating and throwing and error (look for a red LED next to your motor inputs). While the error is detected, the board will continue to exert a feedhold to keep the gantry from being moved until the driver has cooled off enough to work. @email.james.home - would consider turning down the current on the one with heat issues or adding a board cooling fan
Hmm... interesting - I don't want to hijack this thread completely, would you send me an email here: mike @spark-concepts.com or submit a contact form and we will get things sorted?
I'm not sure if this is the right spot for "this" or not... My "shop-vac" has intermittently been triggering a "hard stop"...I'll turn the shop-vac on, suck up some dust...turn it off...turn it back on...suck up dust...turn it off...turn it back on...bam, hard stop. I should have taken a screen shot but there are several messages in the control software. Sort of a two-part question: 1. Why would that be happening? Is the sudden voltage / current draw on the circuit causing the board (xPro v4) to think I've hit a switch? 2. Is it possible to resume a job / start a job in the "middle"? Each time this has happened...3 or 4 times now today...I was trying to 'surface' a piece of wood and unfortunately it was towards the end of the job and I've started over completely from the beginning and done a lot of "air cutting" to get back to where it crashed. Thanks in advance and sorry if this is not the right spot for the questions / not a control software issue. PS - I should add that it has happened a couple times when I've shut the router OFF (DWP 611 router) at the end of the job...same "hard-stop" warning messages.
Have you earthed your vacuum pipe? You get quite a build-up of static and it is recommended to earth it.
Anyone else having arc problems? I have my controller setup for MM and im getting it just trying to cut a small circle.
I’ll keep an eye out for your dust boot... And might try bonding myself to the machine. Thanks for the insight
@Wip - definitely looks like you are having a noise/static issue. Definitely earth the vacuum pipe and if you are still having issues, check your limit switches. Recommended switch wiring for noise reduction can be found here
Hi We are going to need more information on this. Do you mean GRBL reports an arc error 33 or do you mean the arcs are not cutting or do you mean the arcs are not round or do you mean something else entirely?
Name: openbuildscontrol.exe From: Unknown Version: Copyright: Detected Resource or Process ID: c:\users\xxxxxx\appdata\local\programs\openbuildscontrol\openbuildscontrol.exe Response: Terminated Changed Files: f9c6e79e-24be-42b2-a7c2-7a7a4de3a57a.tmp.html fc88f1b5-5b79-4a28-93f2-bee4ff74b3b9.tmp.png e032231f-8980-4d55-aae4-a7142601fc29.tmp f9c6e79e-24be-42b2-a7c2-7a7a4de3a57a.tmp fc88f1b5-5b79-4a28-93f2-bee4ff74b3b9.tmp Looks like the software is trying to change some files. So the anti-ransomware in Trend is kicking in.
A shame the log doesnt print the paths to those files, as it could very well be our own installer extracting updated html/png/asar files over the older version... I'm going to bet Trend is just overparanoid never been a fan of it for many reasons.
