Issue
Added new standalone CyberStation and bCX. Existing Phoenix controller on Siemens system generated a conflict error when the workstation is started.
Environment
CyberStation
bCX
Cause
New CyberStation was assigned ACCNetID =191; Device Node ID = 191. Phoenix controller was using 191 as its address, too and so there was a conflict between the Phoenix address and the CyberStation Device Node ID.
Resolution
The CyberStation Device Node ID is grayed out in the device editor and therefore cannot be changed. If you run the Database Initialization (DBInit) program the Device node ID is editable. However, if you change it and try to save it you will get a duplicate IP address error.
Perform the following: Shutdown CyberStation, change the workstation IP address in Windows. Run the DBInit program and create a new WS with different name, folder, ACCNetID, DeviceNode ID. Log back into CyberStation. Delete the old workstation (with the conflicting Device Node ID). Shutdown CyberStation. Change the IP address in Windows back to the one you had already assigned it.. Restart CyberStation. Edit the workstation object. Verify the Primary Access Server and Auto Download settings are correct. Perform a Teach. Make sure there are no conflicts and all the controllers are online. Reload the network controllers.
Reloading the network controllers may not be required but is good practice after making changes such as this. You're better off knowing now if there is a problem than after you leave the site.