I have been receiving a similar error since installing MR2. I tried Roger Martin's fix and did not have positive results. Is it possible that a new 5axmsurf.dll and associated files needs to be installed?

Thanks, will do. I was hoping to be able to fix it myself because my dealer is usually backlogged.

With that change I am still running in to the same problem. When posting I get an error message "Warning-Output name is being changed to the program number" This is similar to the previous. If the program # = the program name/nc filename, the code posts correctly. Otherwise I get this warning and the file is named to the program # or to 1 if the program # is 0.

code: pheader$ #Call before start of file if met_tool$ = one, #Metric constants and variable adjustments [ ltol$ = ltol_m vtol$ = vtol_m maxfeedpm = maxfeedpm_m ] I'm not sure if that is what you need so I'll add the psof code: psof$ #Start of file for non-zero tool number pcuttype toolchng = one if ntools$ = one, [ #skip single tool outputs, stagetool must be on stagetool = m_one !next_tool$ ] if progno$ = zero, progno$ = one sav_progno = progno$ pbld, " ", e$ *progno$, e$ pbld, n$, "(", sprogname$," ", month$ , "/", day$ , "/", year$ ,")", e$ pbld, n$, "(POSTED FOR MAZAK)", e$ *tseqno, e$ pbld, n$, *smetric, e$ pbld, n$, "G0", sgplane, "G40", pg49, "G80", "G90", *sgfeed, e$ sav_absinc = absinc$ absinc$ = one prefreturn absinc$ = sav_absinc if mi1$ <= one, pfbld, n$, "G92", *xh$, *yh$, *zh$, e$ pcom_moveb c_mmlt$ #Multiple tool subprogram call pbld, n$, pwcs, "G90", e$ pbld, n$, "M98P20", e$ ptoolcomment comment$ pcan if stagetool = zero, pbld, n$, *t$, e$ if stagetool = one, [ if r2100bitde, pbld, n$, *t$, e$ else, pbld, n$, *t$, *next_tool$, e$ ] pindex if mi1$ > one, absinc$ = zero pbld, n$, "G43", *sgabsinc, ptlngno, pfzout, scoolant, e$ pcan1, pbld, n$, *sgcode, pwcs, pfcout, *speed, *spindle, pgear, strcantext, e$ pbld, n$, pfxout, pfyout, e$ #pbld, n, "M08", e if stagetool = one & r2100bitde, pbld, n$, *next_tool$, e$ absinc$ = sav_absinc pcom_movea toolchng = zero c_msng$ #Single tool subprogram call

Thanks Roger. Yep, that's the ticket! It works great now.

Is there anything else that may cause the ppost$ line not to work? It should be a simple copy/paste, enter new line and insert indentation operation. [ 06-12-2007, 10:32 AM: Message edited by: Scott W ]

I've tried adding the ppost$ command, with indentations on two different posts (mpcin850 and mpselca) and it has not worked for me. Is there a certain amount of spaces for the indentation or a switch that needs to be turned on for this to work? Mastercam vX2

Shawn D wrote: "when I make a program my first operation asks me my program name, and it is the same as your filename, and it takes the program" Exactly what I want to avoid. Currently posting will default to the program # if both names are not identical. The x+ utility renames the NC filename quickly, but does not rename the program # correctly. I just want to ignore the program # completely and use the NC filename in it's place. Matching both names is tedious and time consuming. Mazatrol M+ control [ 06-12-2007, 07:41 AM: Message edited by: Scott W ]

I am trying to get my Mazak post to output the sprogname$ (NC filename) in place of the progno$ (program #) at the start of the posted code. Ideally, I want to enter only the NC filename and eliminate having to enter the program # on toolpath operations. I currently use the X+ numbering utility to name my files. It does not duplicate the program # from the NC filename. Currently, the two #s need to be the same in order to post correct code with the proper program name required by the Mazak control. If the incorrect number is used for the program #, the code defaults to the program# (or 1 if program# = 0) not the entered NC filename, which I would prefer. Entering the same name twice is redundant and time consuming. If anyone knows how to do this, any help would be greatly appreciated. Thank you, Scott Wright Cameron Tool Corp. Mastercam X2 mill level 3 [post_VERSION] #DO NOT MOVE OR ALTER THIS LINE# V10.00 E1 P0 T1146494476 M10.00 I0

I have a similar problem with upper case extensions on nc files. We have some old controls that only recognize lower case file names, while X2 only outputs upper case. I've changed my control def. and posts to lower case extensions, but still get upper case output. I found a great shareware program that will change the case on file extensions in directories and sub-directories: http://www.altarsoft.com/all_file_renamer....action=download But I would prefer to get proper output from Mastercam.

I had a similar problem. Machines on our UNIX file server would not recognize files in upper case. I Googled "change to lower case" and found a free shareware program that works well and allows many other renaming options http://www.altarsoft.com/all_file_renamer....action=download (note: set your shortcut Start in: directory to your posted code directory so you don't have to click though the whole directory structure to rename.) or you can create a batch file in notepad or any other text editor that has the line: rename *.NC *.nc Copy the batch file to the nc code directory and run it to change the extension case.