Constant number format error when trying to run gcode

I’m trying to help my Dad with his new Longmill mk2. We downloaded Carbide Create and made a simple file, generated the gcode, and imported it into gSender.

I tried all the post processing options, and the ones that worked gave constant “bad number format” errors, a dozen or more in the first 8" of travel. (I had set 0,0,0 above the part, was trying a dry run to make sure it behaved as expected.) I checked through the code, and don’t see anything out of the ordinary. The lines it’s complaining about appear identical in format to the lines above and below.

I tried checking the firmware to update GRBL, found a couple of versions older than what it currently has, decided to leave it alone.

I’m at a bit of a loss. We’re running a Mac laptop.

I’m fine with trying a different post processor or CAM software, just having trouble finding one that works.

For background- I used to use Sheetcam and Mach3 to run a plasma table and CNC table at my old job. So I have at least some vague idea what I’m doing, but it’s been years.

Any advice?

@Zair What post processor did you finally settle on? I have never used Carbide Create but if it has a grbl inch or grbl mm post, use it.

I started off using the “Basic G-code” postprocessor. It gave me errors about missing tool commands, I assume it wanted some M commands.

So I tried again with postprocessor “GRBL” and kept getting bad number format errors. Like eight of them in a 4" arc. A bit of googling led me to believe that the firmware might need to be updated, but the only files I found are older than what the mill currently claims to have.

I’m open to different CAM software, but I’d really like something with a free demo mode so I can make a part start to finish before dropping money on software. (That’s why we ended up with Carbide Create, free demo.)

I tried again with MeshCAM today. Made a new file in Rhino, eventually figured out MeshCAM and made some G-code. I used the GRBL-Inch postprocessor.

I got a bunch of errors. “Invalid gcode ID:25 Repeated g-code word found in block.”

Here’s an example chunk where it threw an error.

X3.882Y22.062
X3.485Y21.538
X3.117Y20.996
X2.778Y20.438
X2.470Y19.869
X2.193Y19.289
X1.948Y18.703
X1.732Y18.109
X1.549Y17.515
X1.396Y16.918
X1.273Y16.323
X1.175Y15.699
X1.107Y15.077
X1.071Y14.465
X1.062Y14.000
X1.078Y13.370
X1.124Y12.740
X1.197Y12.137
X1.301Y11.528

Nothing’s repeated?

I skipped through a few errors, then at one point it just randomly took off in a straight line on the X-axis and I hit stop job.

I’m wondering if maybe we have some kind of hardware issue?

Did you get this figured out, I’m looking at CAM software right now and meshcam was one of my considerations.

1 Like

If someone wants to try exporting in grbl mm that might reduce some of the errors related to imperial units / arc movements and decimal places. Unfortunately I do not have any experience with Meshcam.