Geting pretty frustrated with random gcode errors that I don't know how to catch

Same project but a different problem now. Have arcs turned off because they were giving me trouble. Added some slots that I needed, redid the CNC program in Estlcam, and ran it.

New problem(s): in the middle of the program, the gantry did not lift, skipped the next slots, and started doing the lettering. The real kicker is that it MIRRORED the lettering (see green box). How am I supposed to catch this on an air cut? Originally I thought maybe I was skipping steps but in this case the gcode was just plain wrong. Almost like it started running another program in the middle of this one. Starting to get pretty discouraged :frowning:

The red box is to show where those cuts are in relation to the program


LS_WelcomeCenter_42inch.gcode (999.6 KB)

Did it look right in the estlcam preview when you ran it there?

Yep, went over it in detail. No issues.

Does anyone know of a bad SD card could cause the issues I’m seeing?

1 Like

Not sure but that doesn’t seem like an unreasonable guess. This is really odd behavior.

I’d be curious to try this myself but I’ve got too much stuff on my table to run something this large right now. I’m just curious if it’s repeatable.

The only other thing that comes to mind is there’s been some rare cases of odd behavior resolved with reflashing FluidNC, even the same version. It’s like it was a bad flash. I’m not sure that’s the problem here either since I was able to reproduce one of your earlier issues.

What makes me think now that it could be the SD card is:

  • it’s a cheap 128mb that came with a different board
  • it my latest gcode, I did “flip” the letters so they are now being cut face down and it’s almost like the card started reading bits from the old program
  • it would explain some of the randomness

I think you were able to repeat my other issue because it was related to poor path tracing and large I and J values. I’ll try getting a new card and running the same exact gcode and see if the problem happens again.

Is there a recommended size/speed rating?

32GB Class 4. Class 6 probably works. Otherwise, you might run into issues.

Shipping might be expensive from the V1 store. I bought the same card off Amazon recently and its been working fine in my FluidNC eggbot.

Awesome, I’ll start there and see if that fixes these random gremlins. I feel like I understand the machine pretty well and want to do more projects with it but it has been hard to trust it with anything more than the most basic of jobs. Hoping this fixes it.

1 Like

Did you upload a file with the same filename over an existing file? If so, it might be worth deleting and re-uploading. That shouldn’t be an issue but I saw something the other day that made me question it.

Not the exact same, but similar. I did delete the old file but it’s making me thinking that somehow the data wasn’t fully deleted. Who knows. I think the SD card is a good place to start and will report back. Want to try running the exact same gcode on the new card and see what happens.

1 Like

Ran the same exact file again on a known good micro SD card, went without a hitch. 99% sure that my old card was the source of all my weirdness (that and my Inkscape paths). Tossing it in the trash. Thanks all for the help!

4 Likes