caplan
October 8, 2025, 10:10pm
1
When I load any newly-generated gcode (generated from fusion), nothing happens - no machining plan, no errors.
Is there a way to view more verbose logs or something in cutcontrol?
I can load old gcode files with no problem.
I’m using the same postprocessor as I always have, but I have not used my MR1 in a few months and have gone through a few fusion upgrades.
Examining the gcode file doesn’t indicate anything unusual as far as i can tell.
I don’t have an MR1 but something similar appeared with a Crossfire user.
They just downloaded their post processor, imported it to their local post processor library, and files were posted correctly.
Maybe it was on the Fusion side and needed a bit of a “refresh”?
caplan
October 9, 2025, 3:33pm
3
Well, I ended up using a different 3/8 bit tool definition and now it works fine, so there’s something about the old tool definition that’s causing cutcontrol to freak out.
1 Like
caplan
October 9, 2025, 5:47pm
4
Turns out this was caused by my tool having a weirdly high “number” - it was 9191, if I lower it to something < 20 then everything works fine.
I guess cutcontrol should display an error message or something if it runs into a tool number it deems to be too high.