First I have to say I am EXTREMELY frustrated with this thing. It has been a terrible purchase for me, but I cannot give up. I see glimpses of this thing being a gem, but I did not expect this much trouble. I have only been able to get two parts off this thing since April 2019. There. Enough griping.
I had to work on getting a new router due to the Z-axis play. That’s all done and I went to cut a pattern to test and here’s what happens:
Generated the new file as I have the others that work.
Once loaded, GC displays the part perfectly.
I set home and hit “play”.
The Z-axis button goes dark and nothing happens.
No manual controls will work
Restart GC, restart computer, everything works as it should… motor test, Z manual, XY manual.
Go through this (3 - 6) about 4 times.
Load old cut file after GC restart… works great.
Compare the two files thinking it’s a G-Code issue… maybe I am initiating the program incorrectly, but don’t understand that as I use the same generator for all my files, then save as “.NC”… no differences in the initiation blocks:
Then I notice that GC does not recognize “G17” and skips the command. I take that out of the file, no change.
Think maybe its because I am trying to move X, Y and Z together and rewrite to a G19 / G68 block… nope.No change.
I did notice in the code display (lower right corner of GC) it stopped at G10 (Modifies the value of work coordinate and tool offsets) which is weird… cause there is no G10 in my code… anywhere. it read:
G10 Z0
The first Z command is to go to Z0.125 for travel.
So… I think I covered everything. Has anyone had this experience or a close facsimile?
can you post the full g-code and also try to get the groundcontrol.log file
(it’s probably big so clear it before you try another run)
It sounds as if whatever you are using to create the g-code is including codes
that the maslow doesn’t support, you don’t give us any clue about what those
things are.
Here is the full code… and I am asking here: the coordinates shouldn’t present the issue as they are all coordinates… right? I am thinking it has something to do with the initialization of the commands… Again, my old files work… same initialization blocks.
(SINGLE 1.4" STAR 20JUL19)
G20 G90 G40
T0 M6
Nope… no editing of the code. That is the original file I tried. My version is GC v1.24. And it looks correct by your screen shots. Thank you for trying it!
Oh… and it populates in GC. It just doesn’t do anything once you hit go. All manual controls stop, you have to restart the GC, then everything works great. Even old files written the same way with the same startup blocks/
I don’t see anything obviously wrong with the gcode. Since you get no movement at all when running the code it must be something in the first few lines.
I would try removing the comment and the tool command from the beginning of the file. I wouldn’t expect those to cause issues, but it’s possible the tool command is causing a pause to wait for a tool change. I would try running:
I’m able to run the original posted g-code in GC v1.26 with ‘fake-server’ mode. No issues.
Something else going on. Perhaps upload the g-code file. Sometimes ‘illegal characters’ or line-breaks sneak in.
It’s historical with the recent at the bottom. It grows large over time. Best to delete it with GC closed (will be created new with start of GC). Start GC and just try to run the file. Close GC right after and upload the fresh log.txt.
I think that Bar probably hit on it with the tool change, if it doesn’t think
it’s already using that tool, it will pause until you change the tool (although
it should prompt you to continue after the tool change)
