quote: ... is all this effort I've spent learning how to create and modify posts going to be obsolete in X? Obsolete? = No!

quote: ...can I cut/paste from MILL.SET to Post? To a certain extent - Yes. Like I said, it looks like you are going in the right direction. Take a close look at the Mill.SET (or Mill2.SET)

Format Statement 17 has not been defined. This is the the FS2 statement that defines what 'fmt 17' means. [ 03-24-2005, 12:53 PM: Message edited by: Roger Martin from CNC Software ]

You're going in the right direction, but with what you have posted you are missing some critical items. Like in PWRTT you need to call PWRITBUF5 and more... But I'm just guessing, because of what you snipped from your PST and posted... I assume that you've looked at the Mill.SET (or MILL2.SET) files from v9.

Dan, I was just yankin' your chain! Note the [Wink]! That Paul guy is a whole other story, but I'm not going there...

Heh! If you want assistance in the future, it does not help to let everyone know that it was my fault to begin with!

Dan, First, Backup your PST file! There couple ways this can be corrected. This easiest (without accidentally altering anything else) would be to do this... Search in your PST for "G92" (with the quotes) You'll land on something like this -> n, "G92", max_speed, e Now add an asterisk in front of the max_speed to force out the value -> n, "G92", *max_speed, e Note that you may need to make this change in more that one location in the PST.

quote: But what i did was copy and then overwrit all my pst files from MCAM8 into MCAM9 and then ran the UPDATEPST9 c-hook.Yes, copying all the PST (and their related TXT) files that you used with v8 and Updating them was the correct thing to do. These PST/TXT files would not be the cause of the -> "warning - unsupported function call. Recompile with new m_*.h files, link with new m_*.obj files" My original guess was the the PST you were using did NOT call MP.DLL (as the MP.DLL that was installed with v9 should be built to run with v9!) and that your PST was using a 3rd party DLL such as CP5.DLL But, if line 91. in your PST file is referencing 'MP', loading in a new CP5.DLL is not going to help. But, you already know that Try this... First, backup the current MP.DLL in the CHOOOKS folder and then download and install the latest version of MP.DLL -> MP.DLL (v9.18)

"warning - unsupported function call. Recompile with new m_*.h files, link with new m_*.obj files" Usually means you are trying to run an older DLL (C-Hook) that has not been complled to run with the version of Mastercam you are using. What is the name after this line in your PST? -> 91. Name of executable post processor? MP I'm (just) guessing that it is not MP. You need to get the updated version of that DLL file.

If you have 'text' as a Drafting Note -> Choose Main Menu, Modify, Break, Draft/line. I've got to learn to type faster!

I could not help noticing the toolbar. There is a certain icon that looked familiar... Cadist, are you licensing that image now? AK762 - j/k While it is possible that kwolf may be able to network to his machine in his situation, it always good to point out what can be done. Users are sometimes not aware of the useful! things they can do with their controllers .

" but as soon as I updated it on the V9" Did you run Update Post on your PST files after the upgrade? Main menu -> NC Utils -> Post Proc - Update PST I'm not saying this will solve this issue, but all v8 posts should be run thru Update PST for use with MC v9

Jerome, MP has a couple pre-defined variables that contain that info (which is from the NCI 1013 data) -> TLDIA = Tool DIameter and TCR = Tool Corner Radius. If you look at the MPMASTER.PST you can see where these varaiables are used in the 'ptoolcomment' postblock.

Not exactly sure what you're looking for... if gcode = 1005, "Process this this 1005 data", e if gcode = 1006, "Process this this 1006 data", e

Look on the splash screen Mastercam displays on startup --> Or look at the upper left corner of the Mastercam screen -->

I would give this one a try -> MPW-FA10.PST Yes, it is labeled for the FA, FX types - but still worth a go. Be sure to check the "# User Preference Settings" section that allows for easy customization of many functions and several code output format options pertaining to the 'H' registers.

Could it be refering to? -> MCUGetOps.dll This is a DLL from MCU (MetaCut Utilities) I would not expect to find it in the CHOOKS folder. On my system it is located here -> C:Program FilesMCUPartnersMastercamMCUGetOps.dll

Sharks are quite rare in the waters where we’ll be diving around the Caymans. But, last year in the Turks& Caicos there were a few. Not real big, but definitely curious! Always interesting when you about to jump in for a night dive and the dive master has told you to look before you leap so you don’t jump on the shark that’s under the boat And he is not kidding.

Eat, Sleep & Dive (Not necessarily in that order ) That's all that is on the agenda for next week! Cayman Aggressor

Just because you want this position output “as the first line of your program" does not mean you must output it in PHEADER. That is defiantly doing it the hard way! The first X,Y position in the program is easily available in PSOF. If there you have information being output in PHEADER than needs to be output after this initial G92 G70 X(start point)Y(start point) block, just relocate the code in PHEADER into PSOF. Add these diagnostics lines into PSOF and you'll see the (start) X,Y coordinates. code: psof #Start of file for non-zero tool number "*{psof}-> x = ", *x, e #<diagnostics> "*{psof}-> y = ", *y, e #< diagnostics >

Andy, I created a drawing in Mill (in Top plane). Then load it into Lathe. The “Current Configuration files” in Screen Config shows -> LATHE9.CFG Yes, the PST Filename was to a Mill PST (The one that was active in Mill when the MC9 was saved). NC output path, etc are pointing to the MILL folders. I click on the file folder icon just to the right of the “Current Configuration file” on the Files page in Config. I selected my LATHE.CFG file and the file paths change to pointing the LATHE folder paths as defined in that LATHE.CFG) and the PST changes to what is in that CFG. Off you go... Start makin' those Lathe toolpaths

#1026 - ? There is no NCI '1026' code. Probably why the "?" mark is there This a '1025' which is Canned Text

Mike, Where are you seeing a reference to this '1026' ?

quote: I am putting in a "shift" in a bunch of programs that are all similar and we have to slide the part because of the length.Knowing if there is a better way really depends on exactly what code you are inserting into the program and where in the program it needs to be inserted. quote: I want to use manual entry because I want it to be in the /MC9 file as well as the .nc file. I guess I can just put it in via Cimco using the old cut-and-paste method. No doubt about it, putting it into the .MC9 (however it’s done) is the way to go! “the old cut-and-paste method” sooner or later end up being a “oops-and-crunch” out on the machine. ;(

Yup! You confused me. Since you are inputting the (), on the first line take 'em out of the PST like Travis said -> quote: ok just take the parenth?? out of roger's else statement. but this way your man entry comments will always be text line 1 and g&m codes on the following lines.BTW, Why are you using Manual Entry to input code like? -> G00G40G80G90 G54X0Y0 Seems like there would be a better way. But without seeing your complete method of programming - that is just a guess!