How to convert a bCX9640 to a CX9680 (NC2)

[Product_Support]

Warning

Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.

Issue

Procedure for converting a bCX9640 to a CX9680 (NC2)

Product Line

Andover Continuum

Environment

• CyberStation
• bCX9640
• CX9680 (NC2)

Cause

Documentation

Resolution

This article provides some guidelines for converting a bCX9640 to a CX9680 in the field.
As of version 1.94 CyberStation does not automatically convert a bCX9640 to a CX9680, such conversion while complex and error prone can be done manually.

DISCLAIMER:
Be aware that due to the differences between the two models not everything can be converted; certain items may have to be re-created from scratch in the new CX9680 controller.

DIFFERENCES BETWEEN BCX9640 AND CX9680

	Feature	bCX9640	CX9680
1	System Variables	47	65
2	Comm Ports	2	4
3	IO	Expansion Modules	IOU Modules
4	Infinet	1	2
5	Access Control	No	Yes
6	UPS Support	No	Yes
7	Display Module Support	Yes	No

Procedure:

1. Make sure you have a recent backup of the SQL ContinuumDB as a precaution.
2. From CyberStation send the bCX including children to a text file, the dump file can be later used for reference.
3. Take note of the bCX9640’s name, AccNetID and network settings.
4. Put the CyberStation in offline edit mode and delete the bCX9640 then create the CX9680 using the exact Name, ACCNetId and network settings as the deleted bCX.
5. After creating the new controller object it will come online, at this point you are still communicating with the bCX9640 hardware.
6. In the ‘Send to Database’ options make sure to select ‘Save attached objects and controllers’ then select the new controller in the Continuum explorer and perform a ‘Sent to database’, depending on how many Infinet devices you have this make take a while.
7. When the send to database operation has completed you are ready to remove the bCX9680 hardware and connect the CX9680 hardware. After disconnecting the bCX from the network commission the CX9680 hardware with the same AccNetID and network settings as the bCX it is replacing.
8. When the new hardware comes online reload it from Continuum making sure you don’t reload the Infinet devices (Reload attached objects but not attached controllers)

At this point you have converted the bCX9640 to a CX9680, the next steps in the process is fixing the items that do not convert properly due to the differences between the two controllers.

1. LCD Display Configuration
   If the bCX has an display module attached all configuration related to the display module must be removed as the CX9680 does not support it.
2. Fixing IO
   If the bCX had IO then appropriate IOU modules must be configured in the CX9680. In some cases points may have to be moved to a different IOU. For example if you were using a xPBD4 (which has both inputs and outputs) then you’ll have to put the inputs and outputs on different IOU modules as there is not an IOU module that is the equivalent of the xPBD4.
3. Fixing References
   Any references in programs/functions to objects that do not exist in the CX9680 must be manually removed/fixed. For example the CX9680 does not have some system variables supported in the bCX such as all the system variables related to the display module (ACCLCDBeeper etc)
4. Other items that need partial or complete manual fixing include…
   1. Alarms, links will convert ok, but references to Graphics, Program, Video may be have to be re-assigned.
   2. Extended logging

Use the dump file created on step #2 for reference when manually re-entering lost configuration.

Article as a document: Procedure For Converting a bCX9640 to a CX9680