Mach3 Incremental IJ Post Processor

[ftech]

I made a couple of small modifications to the Mach3 post and thought I should report some hiccups I found. The attached file is my modified PPR which simply eliminates line numbers (I find they just get in the way) and uses incremental IJ for arcs (which I think should be the default) rather than absolute .

First, for some weird reason I had to start the name of my PPR file with "M_". Otherwise it won't show up on the list in DCAM (there was a bit of blue air until I guessed at that one).
Second, the first couple of times it ran, it left out some important commands in the gcode file such as the first XY move or the initial feed rate. Without changing anything, perhaps after using a different post and then running mine again, it seems to work fine.

Just wondering if anyone else has experienced this. Is this perhaps a little glitch in the program or is it something on my system only?

Rick

[ftech]

More info ...
It seems that it the glitch still shows up sometimes. The first time you run it there may be a block missing at the beginning. Just running it through the same PPR fixes it.
Maybe someone a Dolphin can shed some light on this one?

Thanks, Rick

[ftech]

And still more info...
It is not just my PPR that exhibits this behaviour, the M_Mach3 does the same thing.
It only seems to happen if you post process without having simulated the run first. In other words, if you load a saved file that has operations and immediately post process, it misses the first XY move.

I would still like to have some feedback though.

Thanks,

Rick

[harley4ever]

Email them. You probably have an outdated post.

[ftech]

I certainly hope it is not an outdated one because it is from their current download; I have only had the program for less than 2 weeks.
Besides, the posts all seem to work fine as long as DCAM gets to simulate the run at least once before generating gcode. I would like someone else to confirm that this is the case by opening a file that you previously created and immediately post process to see if the file is different (ie does not have the first XY move entered properly). Simply running the post a second time generates the proper output.

This is not an issue for normal use of the program because it simulates as you create the operations. The problem only occurs when trying to create gcode with an existing file (for example to change the PPR used) without letting it simulate first.

As long as you know the work around there is not a problem.

Rick