Not sure about what the problem is but he's got the point. 2020 R2 onward compared to let's say 2016 CAD are junk. We have 2016 CAD & 2020 R2. 2016 version is rock solid. We use it every day & had no crash in 3 years. 2020 R2 is pathetic. Constant crashes, bugs & odd alarm messages requiring restarting the whole machine. We tried 2021 R1 & it's even worse. How did Hexagon messed it so bad? Our boss ain't happy.
MattR What are some of the bugs and alarm messages that you're seeing? Have you submitted anything to support? I've used 2016 for a long time and it was very stable unless I asked it to do strange things. I've had little to no complaints from 2020 R2 and onward.
We spent hours with hexagon tech support & they did help but some responses were like it's bug we can't do much wait for new version. We originally had 2021 R1 but it was so buggy hexagon support had us switch to 2020 R2. There was some improvement but it's still buggier than 2016. Argument messages, bus issues, programs that ran fine 1 month ago stop dead stuff like that. One super annoying thing is when taking sampling hits pc dmis moves the probe to the center of the hole; if you have a boss in the way you can't use sampling hits. And tech support said there is no way to get around it. 2016 doesn't do that. I'm not at the machine right now to list all problems. We've copied & copy all programs to the shared drive just in case something goes haywire. No we don't use automation besides using readpoints from time to time.
MattR That's interesting, which industry do you work in? I'm wondering what kind of programs you have that are causing PC-DMIS to act that way. Do you use non-tactile methods? Scanning? New or old hardware? New or old programs?
No. It's only tactile. We use scanning but most is points. Hardware is new (2021 later 2020 came along because boss decided to buy new cmm). Mot programs are new except some copied from 2016 but these old work very well. We had tech support check troublesome programs & they said there look fine.
MattR Very interesting, my situation is similar. For what it's worth, I'd be happy to check out a few of your troublesome programs and see if I experience the same issues or can detect a pattern in the issues you're seeing.
Could you use sampling hits with an external feature in the way prior to 2020 R2?
And has the same limitations it's had since it was added - only supports dimensioning a single feature (does not support patterns), no ability to perform simultaneous evaluation, does not support complex GDT / composite feature control frames, relies on the user to to have a high degree of GD&T knowledge to interpret the callout and have the programming skills to be able to create appropriate features / measurement strategies / alignments etc.
what an informative post
