Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

STRANGE POSTING ISSUE


Hubz
 Share

Recommended Posts

HELLO EVERYONE

LONG TIME READER, 1ST TIME POSTER :)

 

MORI SEIKI MV-50 MILL, USING X6

 

I'M HAVING AN ODD ISSUE TODAY. A PROGRAM THAT WE HAVE RUN 20+ TIMES THIS MONTH, WILL NO LONGER POST. THE POST PROCESSOR ATTEMPTS TO RUN, SAYS THAT IT HAS A POSTING ERROR AND THEN GIVES ME THE FOLLOWING .ERR MESSAGE;

 

 

30 May 2013 10:50:27 AM - <0> - Report created.

 

30 May 2013 10:50:27 AM - <2> - Initialize posting log file

 

30 May 2013 10:50:27 AM - <2> - Using MP run version 15.00 and post components version 15.00

 

30 May 2013 10:50:27 AM - <2> - Initiate opening the post processor file(s).

 

30 May 2013 10:50:27 AM - <2> - C:\USERS\PUBLIC\DOCUMENTS\SHARED MCAMX6\MILL\POSTS\MORI SEIKI MV-50.PST

 

30 May 2013 10:50:27 AM - <2> - The post processor file has been successfully opened.

 

30 May 2013 10:50:27 AM - <2> - Post version information (input):

 

30 May 2013 10:50:27 AM - <2> - UPDATEPOST Version 15. was used to modify this file.

 

30 May 2013 10:50:27 AM - <2> - The file was modified by this product on 11 Jul 12 10:09:30

 

30 May 2013 10:50:27 AM - <2> - The post was written to run with Mastercam Version 15.

 

30 May 2013 10:50:27 AM - <2> - The post product type is Mill.

 

30 May 2013 10:50:27 AM - <2> - Initialization of pre-defined post variables, strings, postblocks was successful.

 

30 May 2013 10:50:27 AM - <2> - Search for defined post variables, strings, postblocks was successful.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'dec_seq_right$' was re-initialized from 3. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'sub_seq_typ$' was re-initialized from 0. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'tplanemode$' was re-initialized from 2. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'bldnxtool$' was re-initialized from 0. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arctype$' was re-initialized from 2. to 6.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutput$' was re-initialized from 1. to 2.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arctypexz$' was re-initialized from 2. to 6.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputxz$' was re-initialized from 1. to 2.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arctypeyz$' was re-initialized from 2. to 6.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputyz$' was re-initialized from 1. to 2.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctype$' was re-initialized from 2. to 6.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutput$' was re-initialized from 1. to 2.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctypexz$' was re-initialized from 2. to 6.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctypexz$' was re-initialized from 1. to 2.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larctypeyz$' was re-initialized from 2. to 6.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutputyz$' was re-initialized from 1. to 2.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcs$' was re-initialized from 2. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcsxz$' was re-initialized from 2. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcsyz$' was re-initialized from 2. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcs$' was re-initialized from 2. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcsxz$' was re-initialized from 2. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcsyz$' was re-initialized from 2. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'helix_arc$' was re-initialized from 2. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lhelix_arc$' was re-initialized from 2. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'arccheck$' was re-initialized from 1. to 10111.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'larccheck$' was re-initialized from 1. to 10111.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed4$' was re-initialized from 2. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed5$' was re-initialized from 3. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed4$' was re-initialized from 2. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed5$' was re-initialized from 0. to 1.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'sub_level$' was re-initialized from 1. to 0.

 

30 May 2013 10:50:27 AM - <2> - CONTROL DEFINITION - Post variable 'peckacel$' was re-initialized from 0. to 1.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - RUN TIME - File error reading NCI file.

 

30 May 2013 10:50:27 AM - <2> - Successful completion of posting process!

 

 

 

I HAVE CHECKED OUR POST WITH OTHER PROGRAMS AND THEY HAVE NO ISSUES AND WORK JUST FINE. I'M THINKING THAT MY PROGRAM IS CORRUPTED.....ANY THOUGHTS?

 

THANK YOU!

-BC

Link to comment
Share on other sites

Well.....I've reloaded the Mach def's...didn't help.

 

try posting with a generic post that installs with Mastercam.

If you can post with a stock post the file is not corrupt.

I've seen this caused by a bad misc integer setting on highly customized posts.

 

Tried this too......didn't help. Still get the errors in posting message.

/sigh

Oh well, guess I'll remake the program. Thankfully I get paid by the hour....hello incoming OT!

 

Thanks for your help gcode,

BC

Link to comment
Share on other sites

Have you tried Regenerating the Operations? It looks like the NCI file isn't being written, before the Post file is open. This causes the post to not have any data to convert into NC code...

 

I have regenerated the toolpaths, with no success. I also verified that the files were routed to the correct folders and posts.

Thanks for the reply Colin, any chance that I have to save this program I will jump at!

BC

Link to comment
Share on other sites
  • 4 weeks later...

UPDATE:

I have successfully recreated this file and have come up with a reason why this happened. It seems that I had MCAM open twice. I didn't realize that I had an extra copy running in the background with the offending file open. DOH!

Won't be doing that again! Thanks guys for all your assistance :)

 

-BC

Link to comment
Share on other sites
  • 3 months later...

I am seeing the same issue. I am able to write a program and post it out, but if I save the file and open it again later I get errors and it will not post. Even though nothing has changed since the last time I posted the program successfully. This has happened to me on the last 8 program I have written this week. It does this to me on X6 and X7. I have tried posting the operations one at a time, replacing the machine definition, and I tried using one of the generic machine defs and posts. I still get an error log and the code fails to post. This is really frustrating because if everything isn't perfect the first time the program is written, it has to be completely rewritten because it will never post again. Any ideas on what's causing this issue? I'm opening IGES files from Pro E. I also tried using other file formats with the same result. These parts do have to be machined on both sides causing us to rotate the parts. Because of this there is a copy of the geometry on one level, and the another copy of the gemoetry flipped over on a different level.

 

Any ideas?

Thanks!

Link to comment
Share on other sites

I have the same issue here with 1 locked 5 axis and 1 regular 4 axis post. Next time I'll take a screen shot of it, but sounds like similar problem. Re-staring MC doesn't do anything, but restarting the pc gets it working again...happened about a dozen times in the last month. Scary, there is few weeks worth of work in each file...

Link to comment
Share on other sites

UPDATE:

I have had a few conversations with MCAM NW and found out the true issue. It was NOT because I had MCAM X6 open twice. It was because I had used the "Group Comment" field in the "Machine Group Properties" tab for program notes, and had entered an unrecognized integer into that field( hit tab most likely). This caused the error code and wouldn't let the post processor progress part that point. I have stopped using that field for notes, and have noticed no other issues :)

 

Happy Programming!

-BC

Link to comment
Share on other sites

Group Comment

 

 

I use that field to input all of my comments which get output on my active reports setup sheet, I post everything with those comments there but not output in my gcode

 

It should be causing a post issue

 

Might have that fixed :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...