I am seeing the same issue. I am able to write a program and post it out, but if I save the file and open it again later I get errors and it will not post. Even though nothing has changed since the last time I posted the program successfully. This has happened to me on the last 8 program I have written this week. It does this to me on X6 and X7. I have tried posting the operations one at a time, replacing the machine definition, and I tried using one of the generic machine defs and posts. I still get an error log and the code fails to post. This is really frustrating because if everything isn't perfect the first time the program is written, it has to be completely rewritten because it will never post again. Any ideas on what's causing this issue? I'm opening IGES files from Pro E. I also tried using other file formats with the same result. These parts do have to be machined on both sides causing us to rotate the parts. Because of this there is a copy of the geometry on one level, and the another copy of the gemoetry flipped over on a different level. Any ideas? Thanks!

So I figured out that when doing the finishing pass for a pocket even when the cutter compensation is set to "Wear" it outputs it as "Computer". This is why its not showing up in my tool table. However, in the code it is still outputting a G41 and a call to the D offset in the controller. Anyone know why it is outputting the cutter comp as "Computer" instead of "Wear" when I have it set to Wear in the parameters, and I am only doing a finishing pass, there is not roughing pass?

In my situation I don't need to post the compensation type as a comment, but I do want my tool table at the start of the program to post the D offset and that it is in wear compensation. A pocket toolpath seems to be the only toolpath that will not post the D offset or the comp type in my tool table? How can I fix that?

Any response to this issue? I noticed that in the code the wear comp and diameter offset are not being posted in the tool table. This only seems to be an issue when creating a pocket toolpath, when I have a contour toolpath the wear compensation and diameter offset is being posted correctly in the tool table. Any Ideas?

Hey guys, I had a quick question about user defined fields for the Active Reports setup sheets. I followed through the tutorial and did the exercises and I understand how to create user defined fields. The problem I am having is that when I create a setup sheet in X6 I am not prompted with the dialog box for the user defined fields. It seems to be related to my subreports. If I have subreports in my setup sheet and run the setup sheet the dialog box does not pop up for the user defined fields and the setup sheet is created anyways. If I remove the subreports from my setup sheet and create a setup sheet in MC, the dialog box will pop up prompting me for the user defined fields and they will be placed on the setup sheet. The user defined fields are on my "main" setup sheet, they are not in any of the subreports, but for some reason MC doesn't seem to ask for inputs for user defined fields with my "main" setup sheet has subreports in it. Is there something special I have to define to make user defined fields work with subreports? What am I missing? Thanks!

Hey guys, I have created a custom setup sheet for mill using the Active Reports Designer and I'm now working on one for lathe. I have a simple tool list and one of the things it outputs is the feed and speed of each tool. For the lathe tools I know there are XML tags for "FAST-FEED" and "SLOW-FEED" to get the feed rate for each tool. Where I run into an issue is with any live tooling. For live tooling my setup sheet will give the speed, but not the feed rate. I noticed that the live tooling (C-axis) tools appear to be defined in the mill tool manager instead of the lathe tool manager. Is there a way to output the feed rate for the live tooling, such as c axis drilling, in my setup sheet using the Active Reports Designer? Thanks!

Thanks for the reply. So you basically just enter insert drills exactly like a regular drill bit, but enter 0 degrees for the point angle?

Hey everyone. My company just bought mastercam and I'm working on building our own tool library for both our mills and our lathes. We use indexable drills on both our mills and lathes when feasable. I was wondering how everyone was entering these in their tool libraries? Are you entering them as regular drills or as custom tools? Thanks in advance for your advice and opinions. Brandon

We have gotten the lathe hooked up to the network. We seem to only be able to point to a root folder on a network drive. We can't seem to get it to point directly to a subfolder, we have to browse to the subfolder on the controller. We have tried forward slashes, spaces, etc. with no luck. Talked to Haas and they said this is a limitation, the controller can only point to a root folder on the network. We just have to browse to the subfolder on the controller. Seem like an oversight or short coming to not be able to point directly to a subfolder this day in age, especially since the controller can browse through subfolders on the network.

Thanks for the input guys. I have been working with our IT guy and we haven't figured it out yet. Machineguy, do you happen to know what the Remote Server Name and the Remote Share Path is for your machine? Obviously ours would be different, but did you enter in a path with backslashes such as \HAASPGM\Lathe, our did you just point to the lowest subdirectory for the share path or is it all IP addresses? I was just curious. I was in contact with the Haas and they gave us a few suggestions which didn't work and I haven't been able to get them to call me back yet. Our machine is a year old or less so I would think it should be able to point to any directory not just the root. We are going to be using Mastercam to generate our code so we are ok with the operators not being able to change the program. In fact we don't want them to have the ability to change it without communicating the changes and why they are doing so.

We are doing the same thing. Hooking our new Lathe up to our network using the ethernet. We have been able to get it to open a shared folder on the connected computer on the Net Share tab, but are still trying to get it to connect to our network. We obviously have some setting wrong. I do have one question that I was wondering if anyone could answer. When pointing to a folder on the network drive does it have to be at the root level. So for example when we connected it to the computer in the "Remote Share Path" we pointed to a folder HAASPGM which was located directly on the C: drive (C:\HAASPGM). What we wanted to do is point to a subfolder underneath this. So we actually want to point to C:\HAASPGM\LATHE. We could never get the settings on the controller to point to a subfolder, only the root folder on the hard drive. Is it possible to point to subfolders? If so does anyone have any tips?