macros to automate Mastercam

[Bob_Looney]

I'm wanting to automate Mastercam with a macro that will post my G10's to a separate file then continue on and post my std .nc file. I haven't seen any documentation that mentions a macro language for mastercam that would allow me to create this macro. Is there such a thing?

[Jeremy Herron@DBS Solutions™]

I have my post set to call g10 x(var#) y(var#) z(var#) a(var#) c(var#) and I have macros that populate everything else resident in the controls on the machine. Is that what you mean?

[Bob_Looney]

no. The makino cell requires a separate G10 offset file. My post currently "formats" a complete offset file in the header of my code file. I then cut/paste that section into a notepad doc and save that as my offset file. I want a macro that I can execute once that will code and save the offsets as one file, then code and save my program file. Different post will be needed and perhaps a different control might be needed as the file extension of the offset file is different than the .nc program file.

[Colin Gilchrist]

Bob,

 

All that can be handled inside the Post using a buffer and the file manipulation functions in the MP language. You'll just need someone to make the edits. I'd recommend contacting your Reseller or whoever created it originally.

[GoetzInd]

Out of curiosity, why do you want a separate file with the offsets instead of in the header? Does the cell require this? I wonder for what purpose.

 

Mike

[Bob_Looney]

Colin, I created the post. I will dig up some post documentation for those file manipulation variables.

Goetz, Makino is set up to have a separate file. You only have one part program that can be run on a plurality of pallets/fixtures. Makes life easy. Like their H1 D2 std, it actually does work quite well.

I believe the separate offset file came from the automotive industry where they have a large presence.

[Bryan Johnson]

output to separate file is straight forward and does not require the use of Buffers.

See the "Subout" features in the post documentation.

[Colin Gilchrist]

output to separate file is straight forward and does not require the use of Buffers.

See the "Subout" features in the post documentation.

 

Yes, the file functions are easy enough, but capturing the XYZ and angle for the G10 lines typically needs a buffer to save and sort the data.

[Guest CNC Apps Guy 1]

Yes, the file functions are easy enough, but capturing the XYZ and angle for the G10 lines typically needs a buffer to save and sort the data.

Unless you already know those values, then you could use Misc. Reals.

[Colin Gilchrist]

Unless you already know those values, then you could use Misc. Reals.

 

If you already know the values, I'd just create a Manual Entry toolpath at the start of file. Then you only have one location where you might need to edit values.