[GLCarlson]

In the interest of documenting things that trip me up...

I was planning to do some engraving with my spring loaded drag engraver. Generated the code using Cut2Ddesk (it's very fast with engraving g code). Because it was the drag engraver, I just set the cutter speed to zero. Hadn't used the drag with PP before. Load program. No alerts, no status messages. Runs fine, up to completing the pre position (G0) line. Program stops with the cycle start button blinking. Will not continue past that line despite clicking on cycle start. Relevant code fragment:

.....
N290T7M06
N300 (Tool: Engraving Diamond Drag)
N310G00G43Z0.8000H7
N320(Mist coolant ON)
N330M08
N340S0M03
N350(Toolpath:- Profile 1)
N360()
N370G94
N380X0.0000Y0.0000F5.0
N390G00X1.0000Y1.0000Z0.2000

(stops executing at this point with cycle start light blinking. Won't continue.)

N400G1X1.0000Y1.0000Z-0.0170F5.0
.....

Eventually the light dawns... Pathpilot is waiting for some ready signal. In this case, perhaps waiting for the speed to hit the target RPM? Sure enough, delete the speed and spindle on commands, and now it runs fine.

Didn't track it further than that, I just deleted the line and got on with it.

This seems like rational behavior from PathPilot. It got a couple perfectly OK commands, and it's waiting for the condition to be met. So, no bug report to Tormach.

But...if your g-code post always generates a speed word and spindle command, you might see some puzzling behavior when you set speed to zero and then start the spindle, without any grumbling on the status display from PP.

[MFchief]

Are you using v1.9.7? There was something in the release notes for that saying they fixed a bug about zero rpm when engraving serial numbers. Might be related?

Terry

[GLCarlson]

Yes, 1.9.7. Should have said that. Related? Beats me. Odd enough I thought I should report it.

This was one of those things that just left me bewildered. Took a day or so for the penny to drop.

[kstrauss]

I noticed this before with 1.9.5 or so and modified my Cut2D post. Use the attached post at your own risk but it works for me! You'll have to rename the file to whatever.pp to use it.

[GLCarlson]

I noticed this before with 1.9.5 or so and modified my Cut2D post. Use the attached post at your own risk but it works for me! You'll have to rename the file to whatever.pp to use it.

Thanks very much!

[MFchief]

I was hoping you were using an older version, and it would be fixed in v1.9.7. Oh well..........
Terry

[kstrauss]

I apologize but it appears that I uploaded the wrong version of my Cut3D post. Hopefully my fingers typed it right this time!