Hi. Ive had an OX CNC for a few months now, it has been working fine but not the last 2 days. I am unable to zero the machine, I can set the zero at the correct height etc. But if I move the machine away from this by jogging it and click "return to zero" in UGS the visualiser shows the tool moving but it doesn't move. It freezes. It's like it loses its connection or something. Any help greatly appreciated. I have recorded a small video which hopefully I can upload.
What puzzles me in the video is that when you pressed "reset zero", the DRO did not go to zero as I would expect. Maybe an UGS problem rather than the machine?
Hmm, I have installed the latest version of UGS and the issue follows. If I try to run the file I just get the $$ settings and some g codes put back to me. Frustrating. Have scoured the web looking for similar issues but no luck.
Very interesting, I will try this. Do you know why I might suddenly have these issues? You think it's with the UGS not the machine. I have not a clue what serial queue bugs are but this gives me hope. Many thanks. I will report back.
So I've downloaded openbuilds control, I have the same issue. The machine will not zero and will not run a job. I get this message when I click run job "gcode parser gcode file (from gcode editor) sent to backend. And that's it...
What controller? Have you taken a backup (CONTROL > Grbl Settings tab > backup settings button) -And then post a backup of your Grbl Settings for review
I'm not able to get the backup settings right now, but still have the $$ settings on the screen if this is of use? Or else I will get out later and download them. Thanks again for the help. [16:31:36] [ $$ ] $0=10 ;Step pulse time, microseconds [16:31:36] [ $$ ] $1=255 ;Step idle delay, milliseconds [16:31:36] [ $$ ] $2=0 ;Step pulse invert, mask [16:31:36] [ $$ ] $3=6 ;Step direction invert, mask [16:31:36] [ $$ ] $4=1 ;Invert step enable pin, boolean [16:31:36] [ $$ ] $5=0 ;Invert limit pins, boolean/mask [16:31:36] [ $$ ] $6=0 ;Invert probe pin, boolean [16:31:36] [ $$ ] $10=1 ;Status report options, mask [16:31:36] [ $$ ] $11=0.020 ;Junction deviation, millimeters [16:31:36] [ $$ ] $12=0.002 ;Arc tolerance, millimeters [16:31:36] [ $$ ] $13=0 ;Report in inches, boolean [16:31:36] [ $$ ] $20=0 ;Soft limits enable, boolean [16:31:36] [ $$ ] $21=0 ;Hard limits enable, boolean [16:31:36] [ $$ ] $22=0 ;Homing cycle enable, boolean (Grbl) / mask (GrblHAL) [16:31:36] [ $$ ] $23=1 ;Homing direction invert, mask [16:31:36] [ $$ ] $24=25.000 ;Homing locate feed rate, mm/min [16:31:36] [ $$ ] $25=500.000 ;Homing search seek rate, mm/min [16:31:36] [ $$ ] $26=250 ;Homing switch debounce delay, milliseconds [16:31:36] [ $$ ] $27=1.000 ;Homing switch pull-off distance, millimeters [16:31:36] [ $$ ] $30=1000 ;Maximum spindle speed, RPM [16:31:36] [ $$ ] $31=0 ;Minimum spindle speed, RPM [16:31:36] [ $$ ] $32=0 ;Laser-mode enable, boolean [16:31:36] [ $$ ] $100=26.667 ;X-axis steps per millimeter [16:31:36] [ $$ ] $101=26.667 ;Y-axis steps per millimeter [16:31:36] [ $$ ] $102=200.000 ;Z-axis steps per millimeter [16:31:36] [ $$ ] $110=10000.000 ;X-axis maximum rate, mm/min [16:31:36] [ $$ ] $111=10000.000 ;Y-axis maximum rate, mm/min [16:31:36] [ $$ ] $112=2500.000 ;Z-axis maximum rate, mm/min [16:31:36] [ $$ ] $120=50.000 ;X-axis acceleration, mm/sec^2 [16:31:36] [ $$ ] $121=50.000 ;Y-axis acceleration, mm/sec^2 [16:31:36] [ $$ ] $122=50.000 ;Z-axis acceleration, mm/sec^2 [16:31:36] [ $$ ] $130=780.000 ;X-axis maximum travel, millimeters [16:31:36] [ $$ ] $131=1280.000 ;Y-axis maximum travel, millimeters [16:31:36] [ $$ ] $132=68.000 ;Z-axis maximum travel, millimeters
Sure its a V1? If so then 5. Troubleshooting states And you have So, if you are sure its a V1, that should be $4=0. ___ Changed from the Grbl default of Grbl v1.1 Configuration which says it shold be $11=0.010 - adjusting advanced settings like those are never worth it, the defaults are tweaked already Rest looks OK
So I just changed $4 to 0 and $11 to 0.010, restarted GRBL and went to jog the machine. It juddered and now all is limp, like the steppers aren't holding now. I'm pretty confused
If I try to jog the machine this is what I get back: [21:29:28] [ $J=G91 G21 Y-1000 F10000 ] ok [21:29:28] [ $G ] [GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0] [21:29:28] [ $G ] ok
Power supply still good? xPro still good? It sounds like old / secondhand goods. V2 is a lot of years ago 10000mm/min might be a bit fast: Try lower, like 3500 for XY
You are correct. It is second hand. I have changed the settings but no luck. I will try to re-flash the controller and if that doesn't work I think it needs a new one. Can you reccoment which one would be the best/ easiest direct replacement at all. Thanks. James.
BlackBox - massive upgrade over an xPro: Learn more at docs:blackbox-x32:start [OpenBuilds Documentation] - 32 bit - Way stronger stepper drivers - Much easier to wire - 24V PSU (so if you ran the xPro off 12v, grab the 24v PSU too) for faster acceleration docs:powercase-v1.9:start [OpenBuilds Documentation] - Wifi - Full compatibility with CONTROL software and other more modern software toolchains docs:software:overview [OpenBuilds Documentation] - Optcoupled and filtered inputs to make it EMI proof - 4th axes support - Compatible with OpenBuilds Interface (So you don't even need a computer! docs:interface:start [OpenBuilds Documentation]) - Compatible with our Probe: docs:xyzprobe:start [OpenBuilds Documentation] - Compatible with Xtensions Limits (A must have if you have plain switches now - Xtensions has onboard filtering and troubleshooting LEDs): docs:xtensions:limits [OpenBuilds Documentation]
Thank you, I think I'm convinced, I must say I far prefer the openbuilds software to the UGS, so if it ties in nicely then it should be a worthy upgrade.
Blackbox X32 ordered I just say, it's not the cheapest, but given my absolute lack of knowledge in Arduino, nor willingness to invest time to learn it I think it's the best choice. Can't wait to get it installed and get going again using the openbuilds controller. It's much more user friendly than UGS from what I've seen.
Just got the new blackbox installed... Wow! I had read that the machine sounded smooth as butter but in my head failed to see how it could with the same parts... I see now! Such an improvement! Loving it
Quick one, and thanks for all the help so far. When I open my gcode file, the viewer shows it as being out of the machine limits (see image). I'm not sure if this matters as I haven't come to cut anything yet. But I would like to be able to set the origin of my file to the origin of the machine, is this possible?
1) home to set Machine Coordinates 2) Jog to the origin (center of stock it seems from the screenshot) and Set Zero Machine Coordinates and Work Coordinates are seperate "layers" G53 = Machine Coordinates G54-G59.1 = multiple Work Coordinate systems, all stored as Offsets from Machine Coordinates G28/G30 = defined positions as offsets from Machine Coordinates Rehoming automatically re-establishes all saved Coordinate/Coordinate Systems too
