MPMASTER bug3$ error when updating to MC2017

[?Mark]

There is only one error while updating all my mpmaster based posts from x9 to mc2017:

 

# --------------------------------------------------------------------------

# Debugging and Factory Set Program Switches  

# --------------------------------------------------------------------------

bug1$          : 2     #0=No display, 1=Generic list box, 2=Editor

bug2$          : 60    #Append postline labels, non-zero is column position? 

#CNC<<FAIL>>bug3$          : 0     #Append whatline no. to each NC line?<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<here

#CNC<<MSG-ERROR(248)>> The variable, postblock, or other keyword is no longer supported

bug4$          : 0     #Append NCI line no. to each NC line?

whatno$        : yes$  #Do not perform whatline branches? (leave as yes)

linktolvar$    : 0     #Associate X tolerance variables to V9- variable?

linkplnvar$    : 0     #Associate X plane specific variables to V9- variable?

 

# --------------------------------------------------------------------------

# Additional General Output Settings

 

 

Is anyone else seeing it?

Any idea what's going on?

 

TIA

[gcode]

_{I got that upgrading all my mpmaster posts}

_{I had no affect on output} 

[Colin Gilchrist]

The "BUG" Command Variables are hold-overs from the "Pre-X" Era of Mastercam.

 

These "Bug" variables were special commands to tell the post processor engine (MP.DLL), if you wanted to do any special things during processing. Bug 3 used to give you the ability to "print" the NCI Line Number that generated the current NC Code Line, in the NC output file.

 

Looks like "Bug 3" has been deprecated, probably because the Post Debugger is now handling all those "debugging" duties. I don't believe "Bug 3" has really even worked for a couple versions now. So it's just a relic of the past that is not important.

 

Now, "bug4$", to me, is still very important. Bug 4, controls the output of Variable Values during Debugging.

 

Wait, what?

 

Didn't I just say that the Post Debugger handles all those duties?

 

Well yes, but there are other important debugging techniques, such as just adding an output line to the NC file, and using the Tilde (~) character. This Tilde, caused the variable value to be written to the NC Code File in "Debugging" mode, which means you can output it, without changing the "current" or "previous" values. This is very handy.

 

Plus, when "bug4$" is set to 0, or 1, then the values are output using the Format Assignment and Format Statement for that variable (variable is rounded).

 

When 'bug4$' is set to "-1", then the Debugging values are output as RAW values (unrounded).

 

Being able to just print out the "raw" values can help you catch errors in your logic, like doing a "equality" test on a current and previous variable value, where one of them has been rounded by being output, and the other has not...

[?Mark]

Thanks Tom and Colin. It's good to confirm that it doesn't affect the code.

Makes me think though of how often those posts are being updated/refreshed by in-house solutions