X6 MU2

[gcode]

I've installed MU2. Posting from MU1 worked fine, but posting from MU2, I get a bunch of errors.

 

I wouldn't have expected MU2 to upset the posting

 

It shouldn't, what errors are you getting?

[Mick]

It shouldn't, what erros are you getting?

 

Here is some typical errors from an Okuma 4 Axis Vertical post:

 

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1191) - The post block output type processing has failed!, , Label has not been defined[9]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1427) - The post block output type processing has failed!, , Label has not been defined[13]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1427) - The post block output type processing has failed!, , Label was expected but was not found[20], Illegal character(s) encountered

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1428) - The post block output type processing has failed!, , Label has not been defined[13]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1428) - The post block output type processing has failed!, , Label was expected but was not found[20], Illegal character(s) encountered

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1429) - The post block output type processing has failed!, , Label has not been defined[32]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1429) - The post block output type processing has failed!, , Label was expected but was not found[39], Illegal character(s) encountered

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1430) - The formula/boolean failed (general message), , Label has not been defined[29]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1430) - The formula/boolean does not terminate properly

 

I'd list the Multus errors, but they run off the page .

 

Here is a snippet:

 

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

 

I have to stress, nothing has changed other than installing MU2. Both the above parts posted fine, with no errors, in MU1.

[MrFish]

I've installed MU2. Posting from MU1 worked fine, but posting from MU2, I get a bunch of errors.

 

I wouldn't have expected MU2 to upset the posting

 

 

I also got an error when posting, thankfully only one and Mick (our local tech guy) managed to fix it for me overnight. Thanks Mike

[Jeremy Herron@DBS Solutions™]

In mu2 they improved the error reporting when posting. I had the same thing happen during beta, and the errors had always been there I just did not know it. Once I tracked them down and fixed them the problem went away. Post a program you had previously posted in mu1 and do a file compare. If they are identical, then you are probably having the same issue.

[gcode]

what do post lines

1191, 1427, 1428 and 1429 look like

 

 

[Mick]

I also got an error when posting, thankfully only one and Mick (our local tech guy) managed to fix it for me overnight. Thanks Mike

 

My pleasure I like to help

[Mick]

1191: !next_tool

1427: serror = sblank

1428: serror = "ERROR - " + strquot + strh + no2str(workofs$) + strquot + sfix_error + no2str(t$)

 

1429: if omitseq$ = no$, serror = serror + strspace + sopen_prn + strn + no2str(n$) + sclose_prn

 

Jeremy Herron: That probably is the case here. Maybe these errors have always existed. Thanks for the heads up.

[Jeremy Herron@DBS Solutions™]

No problem. I like to help too. ;-)

[Mick]

Interesting..

 

Using MU2, the following line in the post doesn't work. But in MU1 it does.

 

If I rem out the lines marked, it works in MU2.

 

if output_z = yes$, <-- rem out ok

[ <-- rem out ok

preadbuf5

if (opcode$ > 0 & opcode$ < 16) | opcode$ = 19,

[

n$, pspc, "(", "MAX : ", *max_depth, ")", e$

n$, pspc, "(", "MIN : ", *min_depth, ")", e$

]

] <-- rem out ok

 

It appears that the output_z switch doesn't work. But it should in MU2...

[Thee Rickster ™]

Tool re-numbering has worked flawless for me 1/2 dozen times!

even renumbered my identical(duplicate) different length tools

[pip]

[ There is a readme file in the documents telling what they have fixed in X6 MU2. It also says that X7 will only work in Win7 and Win8. ]

If this realy is the case, then we will have to give up our maintenence. We will not be investing in hundreds of new computers, just for mastercam to work. That would be a great shame.

[Todd Tracey from Fastech]

To pip, if you use Solidworks or other major CAD packages, you won't be using them on XP with their next release either. It's not just Mastercam that is walking away from an old OS that has seen its time. JM2C

[Guest]

agreed, SW2013 is dropping XP, Siemens is dropping XP and several others as well.

 

XP IS a dead O/S

 

this includes Vista as well

 

Win 8 will be x64 support only which leads me to believe at this moment that Microsoft is finally going x64 only.

 

To anyone saying, "fine we'll use something else", I would say, "go ahead you'll get a year, year plus and then EVERYTHING is going to push you off of XP"

[Mark V.]

You would think they would publicize this a little more, so people are ready for it.

[Guest]

You would think they would publicize this a little more, so people are ready for it.

 

There is a pop up upon launching MU2 that will tell you.

[Mark V.]

There is a pop up upon launching MU2 that will tell you

 

Thanks i just think they should put something on their website about it for everyone to see thats all.

[Guest]

I have been looking at other sites for other software makers, I must say at the moment at least, they are inline with what everyone else isn't doing either

 

This is the reason that as Tech Support, everyone I talk to on the phone, via email or in person, I mention it.

[cobra95kev]

Can someone who has installed MU2 please post a list of the bug fixes read me file?

 

Thanks,

Kevin C.

[gcode]

[ There is a readme file in the documents telling what they have fixed in X6 MU2. It also says that X7 will only work in Win7 and Win8. ]

If this realy is the case, then we will have to give up our maintenence. We will not be investing in hundreds of new computers, just for mastercam to work. That would be a great shame.

 

 

If you are have X6 and are not running on Win7x64, you are leaving money on the table every day.

X6x64 is much faster and more robust than previous versions running XP.

Its worth every penny of the cost to upgrade your computer

[Josh Kinney -Elite Engineering]

Can someone who has installed MU2 please post a list of the bug fixes read me file?

 

Thanks,

Kevin C.

 

 

YGPM

[Jim Evans from CNC Software]

1191: !next_tool

1427: serror = sblank

1428: serror = "ERROR - " + strquot + strh + no2str(workofs$) + strquot + sfix_error + no2str(t$)

 

1429: if omitseq$ = no$, serror = serror + strspace + sopen_prn + strn + no2str(n$) + sclose_prn

 

Jeremy Herron: That probably is the case here. Maybe these errors have always existed. Thanks for the heads up.

 

Mick,

 

Most likely the issues that are being reported are syntax type errors and all would have existed prior to MU2. The error reporting was broke in previous version, but the error files was still created and could be viewed. Post in X6 MU1 and look for the .err file in the NC folder and see for your self. Posting just the lines sometimes isn't enough and we need to see the lines around the line reporting the error as there could be something simple as a missing brace or comma that triggers the problem on the offending line.

 

I put together a long explanation of how MP handles errors it encounters and will see if I can dig it up on the forum somewhere, but basically MP does it's best to solve the error and continue processing. So you could have errors that have NO effect on your NC code because the sections of code with the errors could potentially never be called. You wouldn't see an issue in the NC.

 

I always suggest fixing these errors and they are normally very easy to address for a post guy. You can have your reseller fix it for you and you should get them fixed. I sent you a PM.

 

Jim

[Jim Evans from CNC Software]

Interesting..

 

Using MU2, the following line in the post doesn't work. But in MU1 it does.

 

If I rem out the lines marked, it works in MU2.

 

if output_z = yes$, <-- rem out ok

[ <-- rem out ok

preadbuf5

if (opcode$ > 0 & opcode$ < 16) | opcode$ = 19,

[

n$, pspc, "(", "MAX : ", *max_depth, ")", e$

n$, pspc, "(", "MIN : ", *min_depth, ")", e$

]

] <-- rem out ok

 

It appears that the output_z switch doesn't work. But it should in MU2...

 

Mick,

 

The problem is probably related to the the output_z variable being used in the if statement. Search the entire post for output_Z and see if it is defined or declared in a NON postline there should be some line similar to this.

 

output_z : 0

 

Because there is no $ on the variable MP recongizes this as a user_defined variable and all user_defined variables need to be defined. Find the output_z lines in your post and post them to the thread. It's always easier to have the post itself to see the entire set.

 

Jim

[Jim Evans from CNC Software]

Here is some typical errors from an Okuma 4 Axis Vertical post:

 

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1191) - The post block output type processing has failed!, , Label has not been defined[9]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1427) - The post block output type processing has failed!, , Label has not been defined[13]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1427) - The post block output type processing has failed!, , Label was expected but was not found[20], Illegal character(s) encountered

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1428) - The post block output type processing has failed!, , Label has not been defined[13]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1428) - The post block output type processing has failed!, , Label was expected but was not found[20], Illegal character(s) encountered

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1429) - The post block output type processing has failed!, , Label has not been defined[32]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1429) - The post block output type processing has failed!, , Label was expected but was not found[39], Illegal character(s) encountered

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1430) - The formula/boolean failed (general message), , Label has not been defined[29]

11 Jul 2012 09:39:17 AM - <2> - PST LINE (1430) - The formula/boolean does not terminate properly

 

I'd list the Multus errors, but they run off the page .

 

Here is a snippet:

 

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- The math calculation/formula has an error

11 Jul 2012 09:40:35 AM - <2> - RUN TIME - PSB(-1,3034)- A serious syntax error has been detected in the vicinity of this postline-Contact your Mastercam dealer.

 

I have to stress, nothing has changed other than installing MU2. Both the above parts posted fine, with no errors, in MU1.

 

Label Not defined:

• 
   
  
• Variable has not been defined or defined incorrectly
  
• String literal missing quotes$ missing from predefined variable
  
• $ missing from pre-defined variable
  
• Variable declaration missing or commented out.
  

[Mick]

Mick,

 

Most likely the issues that are being reported are syntax type errors and all would have existed prior to MU2. The error reporting was broke in previous version, but the error files was still created and could be viewed. Post in X6 MU1 and look for the .err file in the NC folder and see for your self. Posting just the lines sometimes isn't enough and we need to see the lines around the line reporting the error as there could be something simple as a missing brace or comma that triggers the problem on the offending line.

 

I put together a long explanation of how MP handles errors it encounters and will see if I can dig it up on the forum somewhere, but basically MP does it's best to solve the error and continue processing. So you could have errors that have NO effect on your NC code because the sections of code with the errors could potentially never be called. You wouldn't see an issue in the NC.

 

I always suggest fixing these errors and they are normally very easy to address for a post guy. You can have your reseller fix it for you and you should get them fixed. I sent you a PM.

 

Jim

 

Thanks for the reply Jim. I've fixed the errors (the Multus error needed to be corrected in the PSB, which has been done). I agree that the errors should be fixed. That long explanation of how MP handles errors would be very good. I (and I am sure a lot of others) would appreciate seeing that.

 

"You can have your reseller fix it for you " <-- If you knew the irony in this statement, you'd be laughing..

 

I'll reply to your message shortly

[gcode]

I get emails from Microsoft Technet

One I recieved today contained a link regarding the uncoming demise of Win XP

People who are upset about Mastercam dropping support for XP in X7 might want to check it out ..... or not

 

 

see the attached pdf if you're interested

Mitigating Risk - Why Sticking with Windows XP is a Bad Idea - IDC - May 2012.pdf