saving g-code files from ez path lathe

[Saint_Sophia]

Working with a '97 Bridgeport EZ Path lathe and trying to move some programs over to another machine. The snag is I can only save to the A drive as PGM files. I don't see a way to dump straight G-code out... at least not from the menus I've found. Anyone know if there's a setting or workaround to export as plain G-code instead of conversational PGM? Or do I need to run it through some kind of post-processor to make it usable on another machine? I'd rather not have to re-write every part if there's a clean path.

 

[feed&steve]

Working with a '97 Bridgeport EZ Path lathe and trying to move some programs over to another machine. The snag is I can only save to the A drive as PGM files. I don't see a way to dump straight G-code out... at least not from the menus I've found. Anyone know if there's a setting or workaround to export as plain G-code instead of conversational PGM? Or do I need to run it through some kind of post-processor to make it usable on another machine? I'd rather not have to re-write every part if there's a clean path.

On the older EZ Path systems, once you load a PGM file into the run mode, the control converts it into G-code and stores it as a TXT file, usually named something like G99.txt or Ezpath.txt. You can copy that to the A drive and rename it later if needed. It's a bit of a manual loop but it saves you from rewriting everything. Have you tried pulling one of those TXT files after running a part to see if it holds usable G-code for your other machine?

 

[hauntedvertigo]

@feed&steve is spot on with the G99.txt or Ezpath.txt workaround. That's the classic method for these older controls.

To add another possibility, it's worth checking your specific software revision. Some later versions of the EZ Path control did allow for direct G-code export if you switched to a different mode before saving, though it was an uncommon feature.

@Saint_Sophia just following up on this. Did you have any luck with the method feed&steve suggested or did you run into any other snags?

 

[9rape_soda]

@Saint_Sophia just wanna say that the PGM file is the conversational code. You must look for that automatically generated G code/TXT file that the control creates when it processes the PGM to run the part. That's your only direct export option without a true post processor