I had a similar problem on Win7 with X9 that I used the wizard on. IIRC, I removed the cfg file or something to that effect and it took care of the problem. Not sure if this is the issue or will help.

Did you ever solve this issue?

If you want a degree, do it NOW. It doesn't get any easier to get it later. I am currently taking night classes at my local college for my ME degree.. This is not an easy task at all..While I managed to keep a minimum of a 3.75 GPA, it has been alot of work, late nights and even some very early mornings. I think most of this stuff would have been much easier had I managed to do it when I had the opportunity. i.e. closer to your age, and not my age (41 this Thursday). Good luck in your pursuits!

I understand..I couldn't take the chance there there wasn't something that would give me bogus numbers in the post had I chosen that route. My part was a relatively simple surfacing path and it was no big deal to re-create it. When it happened to me, the graphics seemed to be hosed up as well..this was shortly after a verification.

Yep...Had this happen yesterday..I ended up nuking the toolpath and recreating it.

Sweet! I did not even think of using Magics for this purpose at all. Use it plenty for the SLA..Thanks guys!

What size is the assembly file? (bytes, kilobytes, etc)

Arrrgh...I think my frustration level is getting higher...I think it's reverting to Mcam design....bah...I quit

John- If there are no mill 3 licenses available, then the nethasp reverts to a mill 1 license. Going between them is not the issue, that works but I do have an issue using the same machine, control defs as it will check the license server again for a mill level 3. That is the reason I asked about creating copies of machine, control, and post. I think they are tied by the post, but I could very well be wrong. If I am confusing anyone, sorry about that,.. I am beyond mad about this.. (nothing to do with mastercam per se- just management).

If anyone could help with this, I would appreciate it. I need the ability to switch between mill level 3 and mill level 1 . Not so bad, right? Well, the issue is, it is a nethasp license schema. If there are no available mill 3 licenses available, I would like to switch to mill 1. Mcam does this automagically I guess, but...I need new machine defs, control defs and posts set up to use mill level 1. Is there an easy way to copy the files and associate them with mill level 1 with little effort, or am I dreaming? Oh..I am running X3 Thanks! Bill

Thank you Thad!

James, That worked! I think that I have everything that I need for now to get these up and running until I can get some time to re visit simple modifications! Thank you James and Ron!

I guess I should add that I just installed X3 and am working through the setup from machine definitions/post stuff...I get to do this across about 5 computers...I hope I don't have to configure each one separately. I did use the updatepost.dll It seems that there were some items that were re-added to the post. Like "A" axis which we don't have/use. bah- Don't get me started on the reason why not... I will check out the debugger! Hopefully, this will help me until I can get a post cd coming! Thanks!

I would use the free post for the HAAS, but I need/want to strip out garbage we simply don't use. Changing the coolant position in the program, turning off comments that are not needed. There are a whole host of reasons why I want to edit the free post that I already have. The reason why I am editing the post is my department has no $ for this kind of stuff...Sounds unusual considering where I work, but then again, not my decision. So, to that end I need to learn this anyway, if not for my own benefit AFTER I leave this company. The one benefit is, they pay for my time to learn it. James, I did the search and found this only on one line. Under this heading #Misc. string definitions sg43 "G43" #Tool length compensation That is the only spot in the Generic Fadal Format_2 4x Mill.pst that I found that statement. Also I can appreciate why it is not acceptable to talk about price in the forums. I have read that before and respect it...I am looking for more of a "general guidance" where I can find it, then I will take it from there....You pointed this out to me so I thank you sir! I appreciate all the help Millman/Apps Guy! Bill

Moving from V9 to X3 and the transition seems to be cumbersome. Configuration, etc etc. Anyway, long story short, I need to learn how to configure/modify posts. The person that used to do that has left the company. Is there a resource that I can easily obtain? Perhaps one that I could purchase? (out of MY pocket grrrr ) In the meantime, is there a way/switch to output "G43" in the posted file? I am missing this somewhere and it doesn't appear to be obvious. I am using two posts. Generica Fadal 4 axis and an updated HAAS post from V9. Thanks for your help

I don't think I would rule out that not everyone has IE7- Especially prior to installing SP3. The point being, some have gone to firefox and other web browsers. Microsofts integration of their web browser into their OS is fairly extensive. Of course, this is opinion and speculation, but we all also know how much testing is done by vendors of software- By and large, improvments and break/fix situations are left to service packs and other release candidate upgrades. Don't you just love the complexity of all software in general. The more complex, the easier to break-. Anyhow, I'm out for the weeked. Take care! Bill

Not sure if this is the issue. I had someone tell me that it was recommended to remove IE before you install SP3 otherwise, you would not be able to uninstall it. I am not sure that there was a good reason to not do this other than there were some bugs that would be created in IE after the SP3 install. I have managed to hold off on XP SP3 for quite some time due to these kinds of "fixes". Just my .02

I used to cut flame cut 304ss and we used high speed roughers and didn't climb..Conventional cut seemed to help with tool life. Don't know if this will help with inserted tooling but made a huge difference on hss. Bill

James, I am curious about the co-create statement. I have used that since '99 and have yet to have anything that mcam couldn't machine. Most of it depended on the translator that was used. Until recently, it was the SAT that gave me the best results. Now they have a solidworks parasolid translator that seems to be rock solid. The times I have had problems with co-create (Onespace Designer which is now owned by PTC) the solid body had a problem due to design (problem exists between the monitor and keyboard). Garbage in, garbage out, as with most software. I often run into this problem with the files I receive and end up fixing the CAD in OSD. For what its worth, I have also used these files in Cimatron with very few problems. Btw, I typically use Solidworks, Onespace designer and once in a blue moon, ProE.

Somehow, I wish I could justify this to my manager for Mcam Art....Won't happen anytime soon though..

Has anyone actually tried dubbing the drill? By dubbing I mean putting a small flat on the cutting edges. I did this years ago, when I ran a fair amount of 304ss and it seemed to work pretty good. The drills seemed to last longer. I don't think I would do this at 6in deep though.

Another thought...Could you use a wet blast? Perhaps it would take some of the stress from heat out of the equation? JM2C Bill

Damnit...I just bought a house or I might seriously consider it. Was in that neck of the woods about 2mo ago.

We have a few here that we run....Drip feed was a pain to get going, but we managed with some messing around with it...Let me know if I can help. Bill

I will look into this as much as time allows. I used to have some CAD software that did this a few years ago, but they seemed to have fixed the problems in CAD. ( SolidDesigner, Onespace Designer ) Something about high resolution dump. One question. Do you have the 1020 plugged into a UPS or power strip? If you do, unplug it and plug it directly into a wall socket. Bill