The manual entry toolpath has an option for "as comment" or "as code". I guessing that you have this set to "as code". The next issue may be logic in the post to support the switch. pcomment2 #Comment from manual entry scomm = ucase (scomm) if gcode = 1007, "(", scomm, ")" else, [ if gcode = 1006, "M00", "(", scomm, ")", e else, "(", scomm$, ")", e$ ] You may need to modify the logic to include if gcode = 1026, n, scomm$, e #as code in current versions not sure about V8 Like so pcomment2 #Comment from manual entry scomm = ucase (scomm) if gcode = 1007, "(", scomm, ")" else, [ if gcode = 1006, "M00", "(", scomm, ")", e if gcode = 1026, n, scomm$, e ]

"It has a few whack moves I cannot get rid of.. :thumbdown:" Those moves are typical of the HS surface paths since the default in X8 is to keep the tool down (no retracts) when the move is less than 2098.666667% of the tool diameter. That default has been changed in X9 to 100% of tool diameter.

So you will need to run a while loop. N5 N10 WHILE [#3012 LT 05:00] GOTO N5 N20 S500 M3 Keep in mind that running the program all night will increase the accumulated machine cycle time when parts are not actually run.

Normally spindle warm up programs run when you start it, in your example idea you would run the program before you left for the day it would run all night till 5:00AM and then start running the spindle, is that what you are looking for? Typical spindle warm up O1234 (SPINDLE WARM UP) M3 S500 G4 P3000 S1000 G4P3000 S5000 G4P3000 S7500 G4P3000 S10000 G4P3000 M30

Are you sure its calling up macro program numbers or is it variables? M98 P9321 Or is it X#432Y#444 There is a pdf here that may be of help. https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CB4QFjAAahUKEwipkPXPlojHAhWQfpIKHSLoChE&url=http%3A%2F%2Fwww.mitsubishielectric.fr%2Fservlet%2Fcom.univ.collaboratif.utils.LectureFichiergw%3FID_FICHIER%3D1309451736544&ei=sOK8Van4DJD9yQSi0KuIAQ&usg=AFQjCNELgmk0MdLWtB9GpDKkVdhJsZmnMA&bvm=bv.99261572,d.aWw&cad=rja Just read the section in the manual chapter 5.4 will tell you the program numbers that you are missing. Allan

FYI you can force Mastercam to use a specific startup config file by adding to the command line prompts: "C:\Program Files\mcamX9\Mastercam.exe" mcamxm.config This will load the mcamxm.config regardless of what is set in the startup config setting of your default configuration file.

post up your .mcx-5 file and some one can take a look.

If you are referring to a finishing toolpath, it has always worked this way. Helpful when chaining up to a shoulder; no need to shorten the contour by the radius of the tool.

A2 is very stable in Heat treat. Threaded holes and reamed holes always done before heat treat in A2. Typically the reamed holes are transfer punched into the die shoe on assembly. JM2C Allan

Assuming control is a Fanuc 0iMD Set channel number to 5 in handy settings. Make a main program in the control like so: % O0001 (M198 SUB CALL) M198 P1234 M30 % Then on your flash memory card have a file called O1234 no extension(important) % O1234(FILE NAME ON CARD IS O1234) Code follows here ect.. %

Call these guys http://www.okuma.com/247365

Look in your nethasp.ini file. At the bottom of the file are these 2 lines ; General Keywords. ; ;;NH_SESSION = <Num> ; See Adapting the Timeout Length ;;NH_SEND_RCV = <Num> ; in the HASP Programmer's Guide. You can change the initial value of <Num> , the first search period in the NetHASP algorithm loop, from its default value of 2 seconds. To change the initial value of n: • In the [NH_COMMON] section, set NH_SESSION = <seconds> where <seconds> is the desired initial search period. Setting the NH_SESSION keyword in the NH_COMMON section, applies to all protocols. To set the session value for each protocol independently, set the value of NH_SESSION in each protocol section separately. Don't forget to un comment the lines by removing the ; characters like so: NH_SESSION = 15 ; See Adapting the Timeout Length NH_SEND_RCV = 15 ; in the HASP Programmer's Guide.

Yes I see that all the time. The issue is that the executable name is mastercam.exe in X8 as well as X9, windows will not play nice when the 2 versions have the same executable name. The mklink command may be of use, or perhaps renaming one of the version of mastercam's executable. HTH Allan

I'll second what Leigh said, except. You will want to change the tip compensation to center and chain the edge of the radius (chaining the center line will give no option for cutter comp). See attached file Allancutter_comp.mcx-8

You will need a 5 axis post to output the A axis angles from toolplanes.

There is a Catia translator to read in the native Catia models. I believe the .3dxml is intended for viewing, and appears to be a one way conversion. Is this 3DLive a Dassault product?

This part screams laser cut. Gear cutting on .120" (3mm) stock is impractical, So if .004" tolerance is good enough. (I'm sure it is because it will most likely bend/bow > .02" (0.5mm)) Laser cut it.

Net surface or coons patch

Selecting different control/machine configurations for backplot in Cimco Edit: http://screencast.com/t/Qe3BzyrDrXv

Compare your tolerance settings. Looks like arcs are getting linearized for some reason.

Un-check the Clearance or use the use "use clearance only at the start and end of an operation" then it will output the G98 (return to R plane).

Most likely you want to look at the break arc settings, I believe the default is set to break arc at quadrants for mpmaster machine definition. That would give you 3 extra lines of code for every full circle.

Like Tim says How about using a G65 call and using the local variables #1 thru #33 set your values A,B,C,D ect... then in your macro sub program #510 EQ #1 (Value of A in the G65 Call) #511 EQ #2 (Value of B in the G65 Call) Then you get all your variables on one line and error checking like in the TerryT example.

There is a parameter that controls if G49 makes movement or not. If set to not make movement their would be no issue as the height would be canceled (no movement) then apply high speed code. When the Z is set to move the G43 call would be applied.

I would say that you have mico switches or proximity switches that are gummed up or contaminated by swarf and the logic of the toolchange macro is failing. Or someone has played with the macro and the logic is messed up, however then the toolchange would likely never work. Many machines have a Large/Heavy tool toolchange sequence that runs physically slower than a regular toolchange to combat inertia.