We just installed the 2023.2 release on our two cmms. The issue is when we open the 2023.2 version we have the icon box machine not responding on one cmm and then with the other cmm we have an error in connect=0. A side note this was done on the night shift, I am just trying to help out and see if I could reach out here before having to get tech support if its not needed. We are currently running 2022.1 version.
Open a web browser and enter 100.0.0.1 in the address bar, this should take you to the FDC web interface screen. If this is the case then your hardware is fine and you probably simply need to set the IP address in PC-Dmis.
Open PC-Dmis with no program open go to Edit > Machine Interface Setup and on one of the tabs in there, it should require an Ip Address.
Enter 100.0.0.2. Port 1234
Start the software again and it should open properly.
I don't quite understand your description on the first one, can you clarify?
Here is a little more information for the first description, the cmm is a DEA machine with a PH10M head and PH10-2 controller. Just in case that information is needed and may be some of the issue. So when PC-DMIS is opened to start or create a new program I receive this notification that is screenshot below. Our jog box is showing that the machine is responding due to the green light being on after a normal machine start has occurred.
Does your SMA ok ?
Did you check the wiring ?
What version did you use before ?
Does it works now ?
If yes, you could back-up the config, and then recall it on the new install.
2022.1 was the version using, our SMA is good. No loose wiring, runs fine with 2022.1 version. I believe the config were backed-up but will verify and go through and recall on the new install.
Start settings editor for 2022.1 version.
Connect to your 2022.1 version in the settings editor.
Backup settings.
Close settings editor.
Start settings editor for 2023.2 version.
Import the setting you backed up from the previous version.
Close settings editor.
Start PC-DMIS 2023.2.
Seems to me that the automagical settings migration for newer version isn't really mature.
neil.challinor Shouldn't this happen automagically upon installing the new version/running the new version as admin the first time? Maybe this wasn't done (running as admin)?
Heather W Did your night shift run PC-DMIS as admin directly after the install (this is a must for the migration/file/folder permissions to work)?
That had not been done, once I ran as admin both cmms started right up! Since we have admin rights we didn't think to specifically run as admin. Thanks everyone for the help!
hahha a "Bad Guys" reference sorry.
