Post including offsets

[gary adams]

Is it possible to have tool offsets for tools stored within the library,then bundled together in the appropriate format for your control,appended to the nc file, then sent into your control when loading your part program.We do this manually as part of our procedure, it works well, with modular tool systems with known offsets.

Gary

[pip]

You could adapt a post processor, if I understand you correctly.

Run one post for the main prog, and another for the tool offsets. Maybe use vbscript to run the two posts, then paste them together.

G10 G90 code I think.

[gary adams]

Pip (thanks for reply)

Currently when we run a part for the first time, we output the proven program via cimco edit 5,to the open window on our PC, then we output to a new window the offsets for the same job, we then copy and paste the offsets into the part NC file and save it to our customer folder.Then when next we do the same job, we select and send the part file, then select and send the offsets (all contained in the one file).I want mastercam to create a file like this when we first program the part, simply the posted Nc file also has the offset data accessed from some area where the the unique offsets for the selected tools are stored.I hope I have explained this well enough for someone to explain if its possible.I am very green in regards to post modification.

Gary

[Dave Ball]

You may want to look into scoppyfile in the post guide, this may be able to acompolish what you need. From the V9 Post Guide....scopyfile, as the target of a user prompt function, receives the name of any

file that the user wants to merge with the NC output. The command

variable mergeext is used to merge the specified file into the NC output at

the location of the command variables in the post customization file.

[gary adams]

ShefferCNC

Pip got us thinking by alerting us to the G10 code.On experiment it allowed a line in our progam to input into our offsets.

G10P10001X50.Z100. (input the values to T1 offset when read by the program).

We modified our post to read the manufacturers tool code and use it to contain our offset data for each tool in our library (our modular km tools).So now we create our program as normal,and the program when executed inputs the offset data.

Thankyou our problem is solved, we think.

Gary