Keeps stopping "error in line ###"

No Judgement
1

made a shelf cad gCode from free cad

and I keep getting errors

Serial Messages
Index.html Version: v1.24.0
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v1.24.0]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 5]
[MSG:INFO: Axis A (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis D (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.11]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:NO_PIN Disable:NO_PIN R:0.11]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Connecting to STA SSID:CreativeCity]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting…]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.1.6]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://maslow.local/\]
[MSG:INFO: WebSocket send protection active (canSend() checks enabled)]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:ERR: Not handling localfs subdirectories]
[MSG:INFO: Telnet started on port 23]
Grbl 1.24 [FluidNC v1.24.0 (wifi) ‘$’ for help]
Grbl 1.24 [FluidNC v1.24.0 (wifi) ‘$’ for help]
[MSG:INFO: ‘$H’|‘$X’ to unlock]
[MSG:INFO: Encoder connected on Top Left]
[MSG:INFO: Motor detected on Top Left]
[MSG:INFO: Encoder connected on Top Right]
[MSG:INFO: Motor detected on Top Right]
[MSG:INFO: Encoder connected on Bottom Left]
[MSG:INFO: Motor detected on Bottom Left]
[MSG:INFO: Encoder connected on Bottom Right]
[MSG:INFO: Motor detected on Bottom Right]
[MSG:INFO: Current z-axis position loaded as: 37.830]
[MSG:INFO: Starting Maslow Version v1.24.0-dirty]
[MSG:INFO: Maslow_Retract_Current_Threshold: 1200]
[MSG:INFO: Maslow update loop registered with hardware watchdog]
[MSG:INFO: Zm=37.830mm, Z home=41.000mm, Z position=-3.170mm]
[MSG:INFO: Channel auto report interval set to 50 ms]
JogTo: $J=G91G21F300Z9 (mm)
JogTo: $J=G91G21F300Z9 (mm)
[MSG:ERR: 33 (Gcode invalid target) in /sd/5round 2 rotated.nc at line 97]
JogTo: $J=G91G21F300Z9 (mm)

and the maslow stops

here is some of the gCode from line 97

(96) G1 X-353.892 Y-1192.983 Z-3.170 F60000.000
(97) G2 X-378.028 Y-1168.846 Z-3.170 I-0.020 J24.117 K0.000 F60000.000
(98) G1 X-378.028 Y-1142.219 Z-3.170 F60000.000

1 Like
2

One thing to check. It is possible that the gcode is trying to send the machine outside the allowed cutting area.

What is your cutting area? It is shown as a green rectangle on the main screen picture. You can change it using the " options" dialogue button just to the right of the arrow pad.

Before you start the cut, did you try the " trace boundary" button (under the arrow pad) this would move the machine with the blade up around the outside of the area described by the gcode. It would show you if the cutting area is outside the software fence.

Can you send us a screenshot of the Maslow window?

1 Like
3

I had never seen that before so I did a bit of research and what I’m seeing is:

Arc Center Offset Mismatch (Most Common) When FluidNC executes an arc (G2 clockwise or G3 counter-clockwise), the distance from the arc center (defined by I, J, or K offsets) to the start position must equal the distance from the center to the end position. If these two radii differ by more than the firmware’s internal tolerance (typically $> 0.005\text{ mm}$ or $0.5\text{ mm}$ depending on units/settings), FluidNC flags Error 33.

Basically it seems like that line is telling the machine to cut an arc, but that arc is mathematically nonsensical so the machine is choosing to stop instead.

Does the FreeCAD post processor have an option to turn off arcs? Basically arcs will be generated as a series of very small straight lines, but I’ve found that is often a more robust option.

1 Like
4

I cant find any “turn off arcs” option in free cad

however I was able to cut the exact same arc in different parts of my sheet..?

also has anyone come up against the red flashing light? it won’t connect (also there is no “maslow” wifi)

5

never mind, I didn’t have all the motors plugged in.

1 Like