Post question

[GREG]

Hello all

What should I be looking for in our post to make tool call modal or non modal.

Only want tool call at start of program,its posting a tool call for each operation altough its using the same tool.

Thanks in advance

 

Cheers

[Steve Biehl - Cimquest Inc]

greg,

see if the ptlchg0 section of the post is calling the ptlchg section. Looking something like this:

code:

---

ptlchg0 #Null tool change

ptlchg

 

ptlchg #Full tool change

...

...

---

The ptlchg0 section handles the tool between operations or depth of cuts or separate pocket chains. It should just handle work offfset changes or Speed or spindle direction changes. I've seen some posts that this section just calls the ptlchg section, which is the full tool change.

 

What Version and post are you using?

[GREG]

Thanks Steven

v9.1 sp2

Its a new post from our dealer , not sure what its based on.

[Steve Biehl - Cimquest Inc]

What machine is it for?

[GREG]

DMU 50e TNC430 control

Its our new 5axis post

[Steve Biehl - Cimquest Inc]

is it a PST and PSB and TXT file based post or a PST/PRM/TXT post?

[GREG]

PSB/PST/TXT

[Steve Biehl - Cimquest Inc]

that makes it based on the generic 5x Heidenhain that ships with Mastercam. You could put the Mcam CD back into your PC and install posts and select the generic 5x post. Then do a file compare between the shipping post and your dealers post. Look for changes in the ptlchg0 section.

[Steve Biehl - Cimquest Inc]

CIMCO Integration,

http://www.cimco-software.com/products/sho....php3?prod_id=9

also makes a great DMU TNC430 post. I've used it many times at customers here in North America.

[Christian Raebild]

I have a suspicion what might be the problem. In Heidenhain code, the TOOL CALL command is also necessary to change the spindle speed, so the ptlchg0 postblock may be checking for a changed spindle speed, but comparing the non-formatted value from the new operation with the formatted value which was output for the last operation. The 'bad' code would look somthing like this:

 

if speed <> prv_speed, n, "TOOL CALL", ...

 

that should be changed to:

 

if fmtrnd(speed) <> prv_speed, n, "TOOL CALL", ...

 

It's just a guess, but that would explain the problem (and why it did not show up when your dealer tested the post).