I followed the advice in this forum about the aladdin software. I found that I had to install static IP's because some some computers show the actual name and IP, while others display "pool" followed by the IP so it was hard to find the culprit since IP's were reassigned at random. Because of frustration with this people were shutting down he hasp and slowing program production. Just saying thanks for leading me to a solution. Now to tackle locked programs using Cimco.

Like Josh, we have "no sim found" especially on our Lathe seats. We are running Mcam 6 Mu3 and while Mu2 cut down our net hasp problems they are still there. Our programmer/ operators were instructed to use the Aladin monitor to shut down and restart the nethasp, but that stops 5 seats and costs us production. Because of this I have been looking into softwares such as Process Explorer that trace hooks and allow kills that might eliminate total hasp shutdowns. Windows seems full of these problems because there are many software partial solutions available. (I looked into the Safenet driver number and we are using 6.22) Any how, if anyone has looked into this and found some answers, I would like to hear them. Thanks Charlie Hajek Aurora Metals Tech. Spec.

If you're cutting off a model, maybe manipulating the geometry of the flat and reprogramming would help.

We have Cimco full, but it doesn't show the errors we get. It doesn't recognize (x,c) moves that take the place of y. Most of our problems are on 1 of a kind Mold parts and time is a big factor so our operators lean towards old proven methods. Also Cimco full is a per seat license and when a copy of Mcam is defaulted to Cimco it usually grabs a seat of full. I know there are work arounds, just was looking for an alternative that read the output I mentioned and showed the error. Maybe I'll look at varicut. Tight times , so maybe I'm day dreaming.

I would like to see back plotting in mastercam editor so I could see the actual output of certain mill/turn toolpaths. Verify tests the veracity of your input, but a good backplot shows what your g-code is telling the machine to do. We have found by trial and error toolpaths we can trust, but no operator wants software generated scrap on his file when reviews come around. The toolpaths we avoid are the Hi speed milling paths when making contour roughing and finishing cuts in lathes with live tooling.

We are in the process of upgrading our PC's to 64 bit OS as we replace them. I am looking for info from experienced users of MCAM 6x as far as any problems I might have with this upgrade, such as post processors, program sharing, and possibly network (nethasp) compatibility. Thanks ahead of time

Try running DeBug. this will help find the origin of the post output. Small changes in the post followed by sample output is best. Also try to watch for unwanted output in other areas.

Verified rapid moves in 3+2. Moves through walls when rapiding to and from cutter paths are not pleasant surprises. They can be caught, but picking through a complex cutter path is not always easy and very unproductive.

We have 2 mill seats, 2 lathe seats, and 1 wire seat. Our problem is running a design seat takes up a machine seat. Is this normal? Thanks for any help.