X4 Post .err file from update

[Tony35]

i update my posts to X4 now i get a .err file and it has a bunch of control def post variable changed

 

08 Jun 2009 01:59:05 PM - <0> - Report created.

08 Jun 2009 01:59:05 PM - <2> - Initialize posting log file

08 Jun 2009 01:59:05 PM - <2> - Using MP run version 13.00 and post components version 10.00

08 Jun 2009 01:59:05 PM - <2> - Initiate opening the post processor file(s).

08 Jun 2009 01:59:05 PM - <2> - Post processor file name: K:NCMASTERCAM POST & TOOLSPOSTSKITAMURA HX500I.PST

08 Jun 2009 01:59:05 PM - <2> - The post processor file has been successfully opened.

08 Jun 2009 01:59:05 PM - <2> - Post version information (input):

08 Jun 2009 01:59:05 PM - <2> - UPDATEPOST Version 13. was used to modify this file.

08 Jun 2009 01:59:05 PM - <2> - The file was modified by this product on 08 Jun 09 10:19:04

08 Jun 2009 01:59:05 PM - <2> - The post was written to run with Mastercam Version 13.

08 Jun 2009 01:59:05 PM - <2> - The post product type is Mill.

08 Jun 2009 01:59:06 PM - <2> - Initialization of pre-defined post variables, strings, postblocks was successful.

08 Jun 2009 01:59:06 PM - <2> - Search for defined post variables, strings, postblocks was successful.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'chord_tol$' was re-initialized from 0.0005 to 0.00005

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'ltol$' was re-initialized from 0.0005 to 0.002

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'maxrad$' was re-initialized from 999.9999 to 999.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'met_maxrad$' was re-initialized from 9999.999 to 9999.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'helix_tol$' was re-initialized from 0.0005 to 0.0001

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'met_helix_tol$' was re-initialized from 0.005 to 0.001

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'atol$' was re-initialized from 0.5 to 0.01

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'dec_seq_right$' was re-initialized from 3. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'dec_seq_left$' was re-initialized from 3. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'spaces$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'sub_seq_typ$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'tplanemode$' was re-initialized from 2. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'bldnxtool$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'nobrk$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'nobrkxz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'nobrkyz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lnobrk$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lnobrkxz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lnobrkyz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'arcoutput$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'arcoutputxz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'arcoutputyz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'larcoutput$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'larctypexz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'larcoutputyz$' was re-initialized from 1. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'breakarcs$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'breakarcsxz$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'breakarcsyz$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lbreakarcs$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lbreakarcsxz$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lbreakarcsyz$' was re-initialized from 0. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'rotfeed4$' was re-initialized from 2. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'rotfeed5$' was re-initialized from 3. to 0.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'lrotfeed4$' was re-initialized from 2. to 1.

08 Jun 2009 01:59:07 PM - <2> - CONTROL DEFINITION - - Post variable 'sub_level$' was re-initialized from 0. to 0.

 

is my post or control def wrong?

any help would be great

 

thanks

[peon]

I get the same thing!

[gcode]

Check out the log file from your post update.

Those resets have always been going on, but did not

generate alarms in the past.

The problem is that Mastercam has cranked up the

definition of a "fatal" alarm which generates an error

code.

The reinitializations should not trigger an err file.

Something else is causing it.

[Tony35]

downside is i updated before jp got his sticky up

 

thank god i backed up my X3 post so i could try a re-update of one of those and see what gets spit out

[crazy^millman]

by request of Crazy^Millman

 

[ 06-09-2009, 04:01 PM: Message edited by: JParis@CNC Programming Solutions ]

[peon]

tony, i still get the same errors after following the instructions in John's sticky. I set a system restore point before loading X4. I may have to revert back to my restore point.

[Guest]

Guys, those are only variable reinitialization's

 

In my experience so far they have affected nothing.

[Tony35]

i just wonder if i can use my posts or not. it dont look like its too major. code looks ok

 

if not... well back to X3 then

 

[edit]

so how can i turn it off then?

[edit]

[peon]

The code looks ok, but I get errors every single time I post a toolpath. How do I get rid of the errors? It appears I may have to modify some variables in the post.

[Guest]

You should be able to go into your control def >> files >> Keep error on fatal >> All error messages to file

[peon]

John, that has already been set to your suggestion.

[Guest]

We may need some clarification from someone at CNC then.

 

A variable reinitializing should not be causing a fatal error. In the past that was all it took.

[Tony35]

peon/JP

i have the .err file set the same way in the CD

[peon]

Ok, I'm a little less concerned then. Hopefully CNC will chime in with a suggestion or fix. I checked the control def and machine def files in windows explorer after the update and noticed that the date was changed on the machine def files but NOT the control def files. Is this normal?

[gcode]

When I was working with the Mastercam post

guys on an error I was getting when updating

mpmaster posts, I was told that the definition

of a "fatal" error has been changed and is now more strict.

The reinitialization errors should not be triggering the error file output. Something else is casung that.

In my case it was an incorrectly declared C axis variable in mpmaster. They changed to X4 update routine to fix that problem.

Getting an err file does not mean you are getting bad gcode, but it is exteremly irritating.

I would review the log file generated by the update chook.

There was something going on there that X4 doesn't like.

[Tony35]

peon

were you trying it on a file that was created in X3?

[peon]

both X3 and X4. In X4, i simply created a line, used a 2d contour and posted. Got the same errors as in your above sample. Got the error for all six machines

[gcode]

Tony and peon.. are these mpmaster posts?

[Tony35]

yes

one is : MP v11.1.0.0

 

one is MP v11.0

[peon]

They were originally CNC's Generic Fanuc Mill posts. v10.00 and v11.00

[Tony35]

peon

it must just be us cheese heads that are having this problem

[Rob @ Target Machine]

Tony - Try using the post with a new MD/CD from X4.

 

I had this same problem upgrading my Mpmaster to X2.

 

The update post dll creates bad MD's and CD's for some reason.

 

Once you replace them with one of the generic ones the problem goes away.

[Guest]

quote:

---

The update post dll creates bad MD's and CD's for some reason.

---

Guru, in this case the updatepost.dll is not being used to create machine defs, it is only updating the post

[gcode]

This is the fix I got for my mpmaster post

 

[*]Replace this...

 

sav_rev : 0 #Saved revolution counter

indx_out : c9k #Rotation direction calculation

prv_indx_out : c9k #Rotation direction calculation

fmt 16 indx_mc #Rotation direction calculation

 

With this...

 

sav_rev : 0 #Saved revolution counter

cabs : 0 #C axis position

cinc : 0 #C axis position

cout_i : 0 #C axis position

indx_out : c9k #Rotation direction calculation

prv_indx_out : c9k #Rotation direction calculation

fmt 16 indx_mc #Rotation direction calculation

The X4 update chook is suppossed to fix this problem though

[Tony35]

this is what i have

 

#Rotary/Index variables

csav : 0 #C saved value

prvcabs : 0 #Saved cabs from pe_inc_calc,

#Used for rotary feed and direction calculations

cdelta : 0 #Calculation for angle change

rev : 0 #Calculation for deg/min

sav_rev : 0 #Saved revolution counter

#--- Do not change the order of these variable initializations

cabs : 0

cinc : 0

cout_i : 0

indx_out : c9k #Rotation direction calculation

#---

prv_indx_out : c9k #Rotation direction calculation

fmt 16 indx_mc #Rotation direction calculation