Yep, my dealer told me the same thing. The software is eventually what everyone will be going to.... whether it's handed out by a network server, or on each individual PC.

Yeah... just to be clear... I'm not necessarily denigrating the Nethap's... it just wasn't working for us. We have a decent network too... so that's curious... and it was recently upgraded by a professional company that certifies networking for DoD and aerospace security... so it's not a mom-and-pop hack-job network server. Day two with the Codemeter software licensing... no problems yet. Fingers crossed.

Sorry to hear that. Shout out to my dealer in Wixom, Michigan... Axsys Incorporated. They are AWESOME!!!!!!!!!! Five out of Five stars!!!! I have been dealing with them for a long time... decades... and because I work at a local college tech department, I come in contact with dozens of people that have dealt with them too... and quite honestly... I have never heard one bad report... never... not once. They respond quickly to every request. Both sales and tech support are outstanding. Some every knowledgeable people work there. IMHO, they are a world class company... and a benchmark for the industry. I wish everyone had a great distributer like I do.

O u t o f L i k e s

Okay... I just want to update this thread for posterity. We could not find a way to stabilize what we had while using the Nethasp... tried adjusting the communication time and made a few other adjustments our distributer suggested... but nothing worked. We were still rebooting the server almost every say... sometimes more than once. Finally, our dealer suggested going away from the Nethasp to software handling of the licensing... he said eventually, this is where everything is going to go anyway, so might as well get it installed now and maybe it would help. Set that up last night. Today was the first full day with it... so far so good. I will update this in a week or so and note our results. I hope this works.

Awesome!

What kind of video card are you running? Ron is on to something there... seems like a video card issue. Also, maybe run the install/repair... couldn't hurt.

I know this doesn't answer your question... but I like the last line of your paragraph. I like the idea of starting with a fresh platform with Mastercam exactly the way it is intended to be for that release. I always wonder what my old settings through migration might be covering up. No migration for me.

Lol... that name tho

I program bore-in-bore-out ( G85 ) and tell the operator to change it to G76 ( shift ).

We looked at the dedicated DNC unit... I think that's the way to go... but we found an old PC with a serial port so we're good to go for now. Thanks everyone.

Hi, Our old computer stopped working... it has the old school db8 serial port... that we used to DNC large programs to older machines without enough memory to hold the programs. Because new computers only have USB ports and no serial ports, I picked up a USB to serial cord... installed the software drivers... and it works for send and receive... but NOT DNC. I've read a few forums that say this USB to serial cord can not DNC, I do not know why or what the difference is..., seems like if send and receive work, DNC would also... but it doesn't. Question... What is the best set up to DNC these days?

I agree... and this is pretty much what I was trying to say in the original post. Once I have a license... it should not kick me off until I release it. That would solve my problem. The downside of what you are saying is still a downside of this Nethasp system too... because if al the licenses are being used... you can't get on until someone shuts down their session of Mastercam... which is fine... but that isn't currently happening for us right now. People are randomly getting booted out of their session... then that license is still locked out until there is a system reboot of the main computer that the physical Nethasp is on. What a pain. Hopefully we can get this ironed out.

So... I came in over the weekend... skeleton crew... only one other programmer and the WEDM guy... and again, there are 4 mill seats and the WEDM seat... so I should be good no matter what... right? So, I log in and start Mastercam... no problem. Working along for 10 minutes... MESSAGE... you have lost connection, you have one chance to save your work... DAMMIT!!! So I run out to see who else is on the Nethasp... and the WEDM guy had just logged on 20 seconds prior... we set his config file to log him directly into WEDM... so it should not have affected my mill seat. There is no other explanation than when he logged on... I got kicked off. ******************************************************** I don't buy the bad network thing... something else is at play here. Hopefully, our distributor will have some answers.

Thanks

Sounds right... just frustrated. We'll get this resolved. I'd rather go back to the physical hasps though. What's "codemeter?" @JParis

So, we gave up the physical hasps and we switched over to the Nethasp system where I work... and it's been nothing but trouble. We must have rebooted the main computer with the Nethasp on it... a hundred times or more. We have 4 mill seats and one WEDM seat , and frequently... I mean a whole he|| of a lot of times... there someone that can't get on... so the only answer is to reboot and try again. The thing that bothers me most is... once I have a seat and I'm working along... I don't think I should EVER GET KICKED OFF once I have acquired a seat... that should be mine to work with even if the network goes down... seriously... I mean... put a 24 hour time limit on it if you have to... but I should not lose access randomly for any reason... but it happens... all... the... time. You've lost connection, you have one chance to save... is a message I see in my dreams... or should I say... nightmares. I am in contact with my distributor... but I just thought I'd vent and ask... does anyone else have trouble like this with the evil Nethasp? #physicalhaspsrule!!!

Okay, thanks everyone. I'll let him know a fix is coming in 2021.

Has anyone else encountered this? I don't use Turn-Slice, but I work with someone who does... and he said it always used to create arcs and lines... but in MC2020 it is just creating one big spline. Is there a setting or option here? Thanks in advance!

Update: Problem solved I updated the graphics card driver and everything works. Thanks Jeff, thanks Newbeeee!!!!

I tried compatibility settings. Still tweaking... very strange behavior. If I go into config and change the screen background color... nothing happens... but if I minimize and bring it back up... the new color setting populates. Good advice... I'll try to download a different graphics card driver.

Windows 10 Yeah... I'll try compatibility mode. Edit... Nope... that didn't work.

I have an old copy of X6 Lite that I want to use on a computer for estimating purposes.. basically, just to look at the part and draw bounding boxes and such. When I load a file, it shows the entities in the level manager... but nothing populates on the screen. If I minimize Mastercam... and bring it back up... it shows the wireframe, but I can not rotate it or do any thing with it. If I hit F9... nothing happens... but when I minimize it and bring it back up... the crosshairs appear. Basically, it isn't functioning properly. I have uninstalled it, cleaned the registry lines and re-installed... still no good. Any suggestions? Thanks!

Try this one... Reko Pencil Finish

I recently had this issue as well, with a raster toolpath... which was getting this error... so my solution was to change to old-school parallel, which solved it. I thought of it as a toolpath problem... possible collision checking problem that the simulator couldn't solve. So now... I went back to the raster that had this problem... and turned off those three check-boxes... and it worked... no more error. ******************************************************************************** My question is... does this affect any collision checking? Why are those three check-boxes there in the first place? I just want to understand the ramifications of turning off something I have never messed with before. Thanks!