So I’m working on creating some tables from OpenDesk for our makerspace, and after spending the time to CAM it properly I’ve noticed that GroundControl doesn’t want to display the gcode properly. Apart from the fact that the CAM’d Gcode is roughly 8mb, there’s something else I can’t put my finger on that’s wrong with it.
While I might be ok, it’s one of those things where’d I’d prefer not to potentially cause damage to a full sheet of plywood (or our maslow) if I can help it.
Anyone have any ideas? I’m including the workspace from LaserWeb as well as a screenshot of GC. Thanks!
I’ve used NC viewer several times for different projects and it’s been good enough for my needs. Even after running the g-code from Laserweb it looks just fine, but there’s something about importing it into GroundControl that has it mess up.
My only going theory is that because Laserweb has a lot of segments in how it draws a path, GroundControl can only read so many of them (there’s a popup when you launch the program which confirms this), and thus is a bit messed up.
As far as hardware, I’m actually using a Surface 3 (non-pro) which has a Quad-Core Atom processor in it.
There’s a 60,000nline limit to what GroundControl is able to display, though it will cut a bigger file. Is that the pop up you’ve seen?
Consider dividing the work into several pieces with a separate file for each to stay under that limit. If you use the same 0,0 home position for all the files, you can load and cut them sequentially and not lose registration.
I thought it sounded like that.
You’re exploring one of the frontiers of the Maslow, where the limits of cutting speed intersects with the intricate detail that some CAM programs produce. It can take a router a long time to make 60,000+ cuts. It will get there, though.
Yep G21 is definitely there, right on line 1 as a matter of fact. So if Ncviewer is reading it fine, and the gcode looks decently ok, what else could there be that would cause GroundControl to not behave properly?
That definitely looks better. I guess I just assumed since there are no endstops on Maslow that the position would be relative. There appear to be some parts of the cut missing, but that’s more likely the line limitation of GroundControl.
Is there anything special that needs to be done in order to get the rest of the cut to go through? I don’t necessarily need the preview so long as I can see the code flow.
From previous huge files, I heard that Maslow will cut through. Only the display is limited. However, a file as big as your has not been tried as far I can tell. You are exploring untested ground.
I’ll let it run overnight in the GC-simulater and check first in the morning an again when I come back from work