Work in inches in mastercam 2017, force metric output in gcode post processor

[Bob Dole]

Greetings everyone,

I've been working at configuring Mastercam 2017 to match my machine and toolset, and got stuck at a particular issue.

The controller I'm using is "dumb," it doesn't understand any but the most basic gcodes, which is fine.

The primary issue I'm having is that the controller doesn't process the G20 gcode properly; the output needs to be in metric. I don't want to switch the entire program to work in metric, just the post processor.

Would anyone know how to configure this in the post processor, or failing that, point me to resources/documentation on post processor configuration?

Thank you guys so much!

[crazy^millman]

Need to add a multiplier to the post to take all output and use that scale as part of the output. I would use metric and call it day myself.

[jlw™]

So, didn't make it to president so trying your hand at programming?  LOL j/k

[Bob Dole]

1 hour ago, 5th Axis CGI said:

Need to add a multiplier to the post to take all output and use that scale as part of the output. I would use metric and call it day myself.

I've been trying to figure out where to apply the calculation in the PST file, which is a monster at 1900+ lines (I used the generic post processor that most closely matched my machine). Would you have any hints as to where I should apply the calculation? I scanned through the file, looking for instances of 'inch', 'english', 'metric', etc and couldn't find an obvious location.

The file I'm using is Generic Fanuc 3X Router.pst

I've identified the absolute X, Y, Z, I, J coords as xabs, yabs, zabs, iout, jout. I'm just not sure where (or how) I should be applying it (I'm guessing it's just xabs = xabs * 25.4), and I can't find any documentation that describes the format and structure of PST files.

Thank you

59 minutes ago, jlw™ said:

So, didn't make it to president so trying your hand at programming?  LOL j/k

 

Yes, it's hard to type with one hand though.

[Tim Johnson]

'