Strange posting question

[bmilford]

I have created an advanced multisurface 5 axis toolpath with X2 MR2 SP1, and when I posted it, the post acted like it finished properly. Whenever I was inspecting the code I found the ending sequence was missing from the post.

Normally the ending sequence is;

 

G00 Z2. (Move Z TC Height)

G46 (Tool Length Comp. Off)

(********************)

(* END PROGRAM CODE *)

(********************)

M83 (RETURN TO CONTROL LOOP)

 

M02 (SAFETY EOF)

 

 

For this toolpath I am getting this line at the end of the code;

 

G02 X40.2332 Y50.9667 I-19.4332 J-7.004 C196.8139 F933.

 

It looks like the post is "forgetting" to write the ending sequence for this toolpath.

 

Does anyone have any idea what could be causing this?

 

Thank you for your time,

Brian

[Guest]

Select all operations

 

right click >> edit selected operations > change nc file name.

 

for what ever reason they are not all of the same name

[bmilford]

Sorry John no good, it appears to only effect the Advanced Multiaxis, 5 Axis Multisurface toolpaths, there is only one toolpath in this file right now.

 

Brian

[bmilford]

Ok, I just noticed something else with this code;

 

( Tools And Operations List )

 

(Op: Undefined Oper. T002 Undefined Tool Name DIA:0.5)

 

Could the operation being undefined cause my problems?

 

I have also looked at the setup sheet from Mastercam and this is what is shown for the operation;

 

OPERATION TYPE = NULL

OPERATION COMMENT = FINISHING TOOLPATH DRAIN END

TOOL NAME = 1/2 Inch ball end mill

TOOL NUM. = 2

 

Any suggestions?

 

Brian

[Alex Cole]

It sounds like your post may have some stuff setup to read data based on the operation type. You are using a newer type tool path that the post may not have the logic in to support. You may want to email in your post to your dealer to have it looked at.

 

It sounds like to me there is some logic failing and the post is exiting with errors.

 

Alex

[Steve Biehl - Cimquest Inc]

Brian,

check to see if MC wrote an .err file with the same name as your nc file. That file might give you a clue as to what is going on.

[bmilford]

The post is completing successfully, there is no .err file for this toolpath.

My reseller thinks that mastercam may be outputing something the post processor can't understand.

What I don't understand is why after 160,000 lines of code does it do this, why not right away?

 

Brian

[Steve Biehl - Cimquest Inc]

do a search in the post for subout$ = 1 or any number other then 0. This would cause the post to buffer the gcode out for use as a sub program. Depending where this happens in the post, your code may be going out into buffer never-never land.

[bmilford]

Thanks everyone, my reseller got me an updated version of our post that seems to have fixed the problem.

 

Brian