Mastercam X editor Version 11.2.8 doesn't seem to allow the naming of a created macro, or the saving of a macro or its associated keyboard shortcut. When the application is shut down and reopened, poof!, my macro is gone. Am I missing something? Thanks,

I’m running a Hitachi Machine, Control file, and post on X MR2 SP1. I find that in this Control File no matter what values the coolant setting are set to (On or Off) in the mill toolpath parameters, the NCI 1001 Gcode coolant output value is always O, resulting in a coolant off condition in the posted file. Is there a setting or instruction in the Control file or elsewhere that overrides coolant settings in the Mill tool path parameters? Thanks,

Colin; Thanks for the response. The lathe is a bit of a mystery, with even Maintenance scratching their heads over the controller. The sensible solution would be to upgrade or replace the lathe, but then I wouldn't have the excuse to fiddle with the post. Thank goodness for tightly managed budgets!

We have an older (circa '94) Bridgeport EZ-Path lathe for which our tool shop wishes to begin programming offline using Mastercam. I've asked my reseller if he has a post, but I can’t tell him enough about the controller to pin one down. The only manual available is the Programming and Operations Manual (Feb. 1994, Code number 11865457) which describes the local programming sequences but says nothing about the controller software or what the controller expects to see coming out of a post. My reseller said if it is a ‘Boss 9’ controller, he may be able to scare up the post. There are no markings on the controller other than ‘EZ-Path’. I’ve emailed Hardinge but haven’t received and answer yet. Is there another source of information about ‘Boss 9’ or other valuable facts? I’d much rather buy a post than to reverse engineer one myself. Thanks

Paul; Your solution worked. I was unaware of the import function. Thanks, Guyaco

I've find that after customizing the text section of a .CONTROL file (drill panel parameters), save it, and then save it again under a new name, all the edits in the controller text area (controls drilling panels, etc.) are lost and all the text area fields revert to a default. How can I customize a .CONTROL file's text, save it under a different a different name, and retain the text section edits?

When working though Tutorial 13 in the MastercamX Mill Training Tutorials book, I find that the pocket toolpath that I project (Surface Rough Project) onto the surface (step 12) not only cuts the pocket correctly on the surface but also cuts the same pocket in Z 4.0 where it was originally programmed (Step 11). How do I suppress the Z 4.0 cutting? I can toggle the posting on that operation, but since that step is not included in the tutorial I think I missed something. Comments? Thanks

We have encountered a shading problem in X2 MR1 and MR2. The Settings/Configuration/Shading panel Spotlights section only illuminate the right hemisphere of the ball figure no matter which lights are powered. The effect of this is to prevent full part illumination especially in Verify, leaving one side of the part dark regardless of which orientation it’s in. The problem occurs regularly enough to be an issue. Any suggestions? Thanks

I find that changes Mastercam Editor windows settings (font, color, etc.) are not saved from session to session. I've tried all the functions I could find to save the settings, but am still saddled with changing settings from a rainbow of colors and fonts to something I like everytime I open the editor. What is the secret to saving window settings so they surive for the next session? Thanks!

Thanks! I thought I was doing that, but I guess all icons are created equal.

I'm running MX2 and find that my changes made in a .CONTROL file, such as in text/Mill Drill Cycles, Mill custom drill parameters, etc., have been randomly deleted when I reopen a part with the .MDD using that .CONTROL file or when a new part is created using that MDD. This happens regardless of the manner in which the .CONTROL file is saved (green check, or Save As). Is there a trick to dependably saving .CONTROL file changes? Thanks

I would like to make a post edit to change the string selection for sequence numbers at toolchanges. The post is for a Tree mill and we need the sequence number to change from N#### to :####, only on the tool change line. Here is an example of some code- :1 G17 G70 G90 G0 T1 M6 <--- Instead of "N1" we need ":1" N2 G0 X4.67 Z1.0 M3 S1000 N3 G1 Z-.47 F4. N4 Y2.25 N5 X3.62 N6 G0 Z3. :7 G17 G70 G90 G0 T2 M6 <--- Instead of "N" we need ":" code: We've tried formatting a new variable (Tseqnum) and setting it to be equal to (n$), but that doesn't seem to work. I've also tried using the (nwadrs) function to select a new prefix string for n$, but that isn't working either. I was trying to use: code: scolon ":" real_result = nwadrs(scolon, n$) But this wasn't working either... Please help, I'm stuck...

Where can I get a description of the Force Tool Change Option in the Tool Path Parameters pane? I can't find much in the Help file or Reference Guide? Thanks!

We are transitioning from several PC-CAM applications to Mastercam (X MR2) and routinely convert Esprit created models to parasolids which are readable by Mastercam. Occasionally we will need to go the other way, converting a Mastercam model to something Esprit can read. Reversing the Esprit-to-Mastercam process using parasolids does not work. Is the a proven Mastercam model-to-Esprit readable model conversion process? Thanks

I hate to admit I'm a post greenhorn, but I'm tweaking the generic Fanuc 5 axis post and need to know the difference between the "primary" and "secondary axis". Comments or references?

I’m sorry for being late to thank you for your advice on the MR1/MR2 post problem. I’ve found that it occurs sporadically when both MR1 and MR2 are both installed on the PC. Removing both versions completely and doing a clean install cleans it up. So far so good. My fingers will still be crossed for a week or two, though. Guayaco

We are have recurring posting problems with parts programmed on MR1 and modified on MR2. All selected files are not immediately posted. Those not immediately posted are posted in a second posting operation, replacing the first.NC file. Previously this problem could be remedied by checking all the files in the Toolpath Group and then renaming the program # by right click on Toolpath Group/edit selected operations/Change Program #. All the files would then post proper in the proper sequencc, This fix no is no longer dependable and the problem occurs on both MR1 and MR2. We are programming for an older 3-axis Mazak 56 using the generic Mazak .pst. Could this be the result of a MR1/MR2 hybrid part, or am I missing something? Thanks!

Thanks John! Your solution worked perfectly and jobs are now posting with no problem. Fly Boeing Guayaco

I’m testing X MR02 and have found a post processing anomaly for which I need some advice. After adding tool paths to a previously saved file and checking all tool paths in the Tool Path Manager for posting, the system first selects only the original tool paths for posting. After that group has been either saved (posted) or cancelled, the system then returns to the file and picks up some of the cutter paths it ignored in the first pass, and then goes onto posting. This may happen several times before all tool paths that been posted, resulting in several .nc files rather than one as it should. This occurs despite all the tool paths having been checked for posting. Other than happening on parts with more than 5-10 tool paths, there doesn’t seem to be a pattern to this behavior. Position on the tool path list, cutter type, etc. don’t seem to matter. I’ve found the same thing happens in MR01 (we must have been running simple parts, because the shop hasn’t noticed the problem until now). I’ve suspected that this may be controlled by a setting, but I haven’t been able to find it on the system or in the documentation. I’m using the slightly tweaked Mfan post, but the problem occurs on any other 3-axis post I’ve used. I’d appreciate any advice on this opportunity. Thanks, Guyaco at Boeing