Jump to content

Calypso 2020 w/ Contura G2 - any success?


---
 Share

Recommended Posts

Installed 2020, and have not been able to do more than measure one part, and that was after 90 minutes of team viewer assistance from zeiss.
So far:
Unable to connect to the CMM at all. The wrong IP address was being used.
Only a portion of the contents on the sdodata*.mdf files got copied from the backup, so most of our stylii were missing. There is an incompatibility issue with the sql server used in 2020 and the one used in 2019. Fortunately, zeiss were able to get the entire file contents to copy over using some magic app they have access to. He was ultimately able to get it functioning again.
I measured a part.
I installed a network printer, but that borked the connection to the CMM. Apparently Windows 10 overwrites the hosts file when adding a printer. ("Apparently" because I'm not sure what all win10 does with network printers, I'm just repeating what zeiss told me.)
Zeiss re-wrote the hosts file and were able to get the connection to the cmm back.
Trying to measure the second part, I get "machine not initialized." in the main window.
I rebooted the CMM and the computer, and now I get a status window that is forever stuck at "system startup" with no other text. However, now the main widow opens up immediately after the status window opens, but any attempt to open any inspection file results in "machine not initialized."
I removed the printer again, and replaced the hosts file with a copy I had made after zeiss fixed it.
The status window now won't say anything other than "System Startup."
I had to leave a call back number a few hours ago; still waiting.
I've put a computer with 2019 back on the cmm just to get it running; we've been down the entire day messing with this.
Has anyone had any success with this update on this specific model cmm?
Link to comment
Share on other sites

I tought it was common knowlage to not install a new calypso version "online" until the first service pack is released. You test it thoroughly off-line first. Just confirm that it is broken upon delivery 🙂

Well, guess you learned the hard way.. 😉
Link to comment
Share on other sites

Please sign in to view this quote.

Never, and I mean never, uninstall the original version that you have installed before updating to a newer version.

I haven't got to test 2020 yet, but bugs are expected with the initial release.
Link to comment
Share on other sites

Please sign in to view this quote.

Not so common I guess. I just assumed that if they are releasing it, that they have bug checked it. To be fair though, every time we've updated we end up having to take our cmm offline for days of troubleshooting, including service packs. I put the old version back on and was able to get our machine back in to production, so at least we can still use it.
Link to comment
Share on other sites

Please sign in to view this quote.

You can have multiple versions of Calypso installed at once, so it's best to keep your previous version installed in-case issues arise with the newest version.
Link to comment
Share on other sites

Please sign in to view this quote.

Uninstalling the old version is literally one of the first steps in the documentation. We've been bit real bad in the past by updating rather than freshly installing calypso; multiple file paths to multiple versions borked our system a few years ago, and we were reminded that we should always uninstall the previous version for just that reason. And while I realize that new versions will require some level of tweaking, it seems that 'not being able to stay connected to the cmm' is a pretty glaring bug that should have been hashed out before releasing the new version. Sorry for the rant, I'm just getting calypso fatigue from going through this every time we need to update our software.
Link to comment
Share on other sites

They do test it, with very capable tools such as SUnit etc. But everyone who have experience in software development knows that there is always bugs, and no level of bughunting is ever going to catch em all. How ever, some have more bad luck then others, every time..... 😃
Link to comment
Share on other sites

Please sign in to view this quote.

You are correct, and I do realize that. It was unfair of me to make a generalized statement like that.This is the 3rd update we've installed this year, and the 5th update I've been involved with in the past 3 years. Every time we install an update, this is the same behavior... The CMM is down for multiple days because of software issues with the upgrade. I got involved with updating it because the previous engineer responsible for it was also having the same multiple-day downtime results when he would update it, and they were hoping I would have better luck. I know they test it, and I know in my heart that they likely wouldn't roll out a new update if it won't connect to a cmm. It just seems that for the 6 years we've had this cmm, it is always a giant production-halting mess any time we update the software. We actually stopped paying our annual fee for a couple of years because it wasn't worth the hassle and downtime. This time though, a customer has provided us with their (recent) cmm programs from their contura G2, so we had to update ours just to load their programs.
Link to comment
Share on other sites

Please sign in to view this quote.

Oh, I apologize. I haven't read the install instructions in some time, so I didn't realize that they state to uninstall the previous version first.

I used to have some older G2s, and I've never seen the issues that you are talking about. It could be something IT related. I'm not a fan of letting IT touch PCs that are connected to CMMs, but I understand that they have their own requirements.
Link to comment
Share on other sites

 Share

×
×
  • Create New...