I'm using Openbuilds Control V1.0.309 with my router. My CAD is done in Fusion 360, and I'm using the latest openbuilds360 post software available. Since earlier this week, Openbuilds control has been throwing some errors regarding the Gcode its been provided. It has occurred with several different projects with different designs. Most of them are carving out the same pattern at multiple depths. It usually gets a few steps down before it errors. Below is an example of the error, and attached is the associated gcode. Any thoughts as to how I can fix this? ... [12:57:14] [ G2 X11.024 Y330.55 Z4.154 I4.76 J-0.156 ] ok [12:57:14] [ G1 X246.451 Y333.082 Z2.286 ] ok [12:57:14] [ X477.211 Y335.562 F2540 ] ok [12:57:14] [ ] error: 25 - A G-code word was repeated in the block. [ G2 X482.025 Y330.794 I0.051 J-4.762 ] [12:57:14] [ ERROR ] error: 25 - A G-code word was repeated in the block. [ G2 X482.025 Y330.794 I0.051 J-4.762 ] [12:57:14] [ G2 X482.025 Y330.794 I0.051 J-4.762 ] error:25 [12:57:14] [ ] error: 25 - A G-code word was repeated in the block. [ G1 X481.559 Y12.747 ] [12:57:14] [ ERROR ] error: 25 - A G-code word was repeated in the block. [ G1 X481.559 Y12.747 ] [12:57:14] [ G1 X481.559 Y12.747 ] error:25 [12:57:14] [ X481.602 Y9.591 ] ok [12:57:14] [ G2 X476.84 Y4.762 I-4.762 J-0.066 ] ok [12:57:32] [ ALARM ] ALARM: 3 - Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended. [ undefined ] [12:57:32] [ ] ALARM: 3 - Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended. [ undefined ] [12:57:32] [ ] ALARM:3 [12:57:33] [ JOB COMPLETE ] Job completed in 00h02m
Also, when these errors occur, I have tried rerunning the job and they error out at the same line each time.
Can you confirm that you are getting this with 1.0.309. The bug was introduced in 1.0.308, but there was an attempted fix in 1.0.309. OpenBuilds CONTROL Software
Agreed with @sharmstr I ran your file through 1.0.309 (bug was in 1.0.308 only and it was only out for 19 hours before the bug was caught, fixed and 1.0.309 released) and it completed without any error. Make sure you are on 1.0.309, not 1.0.308
My mistake. I saw the update in the console, and on the changelog page and assumed I was on 309: I was in fact still running 308. The job is completing properly now. Thank you both for the quick replies!
The changelog shows all the entries so you can see even prior to an update, what's new in the incoming update
