Industrial Automation Tech Note 36 - TNIA36

Abstract:

This document describes importing a Crimson® 3.0 G3 Kadet file into Crimson 3.1, and the conversion to a CR1000 HMI.

Products:

G3 Kadet: G304K000, G304K200, G306K000, G307K200, G308K000
CR1000: CR1000 04000 00210, CR1000 07000 00210, CR1000 10000 00210

Use Case: Kadet to CR1000 Conversion

The CR1000 line of HMIs is superseding the G3 Kadet line of HMIs. This document describes the conversion process.

Required Software:

Crimson 3.1

Import Process

1. Open Crimson 3.1.
2. Click File-Import.
3. Referring to Figure 1, navigate to the Crimson 3.0 file to import/convert.
4. Select the desired file.
5. Click Open

Figure 1.

Conversion

1. Choose the new HMI from the list.
2. Click OK.

Caveats

While the CR1000 line of HMIs matches up closest to the Kadet line, considering features and price, the CR1000 serial port configuration differs from the Kadet serial port configuration. In some cases ports are lost, in others, they need to be reconfigured. If the application requires more than 2 serial ports, the CR3000 line of HMIs should be used. For applications requiring only 2 serial ports, the tables below show how the ports are mapped after the conversion process.

Serial Port Conversion Tables

Moving Gateway Blocks

Record Configuration

1. Click on the block to move.
2. Note the Start Address.
3. Click the Export Mappings link.
4. Give the file a name.
5. Click Save.
6. Repeat steps 1-5 as needed.

Recreate Configuration

7. Click on the device where the block will be created.
8. Click the Create Gateway Block link.
9. Click on the Pick button next to the Start Address.
10. Select the correct start address, noted in step 2 above.
11. Click OK.
12. Click the Import Mappings link.
13. Navigate to the file saved in step 5.
14. Click Open.
15. Repeat steps 7-14 as needed.
16. Click File-Utilities-Rebuild Comms Blocks from the menu bar to re-optimize the communication requests.

Moving Ports

Drivers and devices are moveable from one port to another.
1. Click on the port to move.
2. Note the driver in use, port settings, device name(s), device settings, and gateway blocks (refer to the previous section on Moving Gateway Blocks) that are associated with the port.
3. Click the Clear Port Settings link.
4. Click on the port to use.
5. Recreate the items noted in #2.
6. Click File-Utilities-Recompile Database from the menu bar to correct tag mapping errors.
7. Complete Gateway Block moving if applicable.
8. Click File-Utilities-Rebuild Comms Blocks from the menu bar to re-optimize the communication requests

Replacing ‘Lost’ Ports

During the conversion process, the Aux ports are removed. As long as there is an available port, the tag mappings can be retained if an identically named device is configured with a driver that has similar mappings on another port.
1. Open the Crimson 3.0 Kadet file.
2. Click on the Aux port that was lost during the conversion.
3. Note the driver in use, port settings, device name(s), device settings, and gateway blocks (refer to the previous section on Moving Gateway Blocks) that are associated with the port.
4. Open the Crimson 3.1 CR1000 file.
5. Click on the port that will be used.
6. Recreate the items noted in #2.
7. Click File-Utilities-Recompile Database from the menu bar to correct tag mapping errors.
8. Complete Gateway Block moving if applicable.
9. Click File-Utilities-Rebuild Comms Blocks from the menu bar to re-optimize the communication requests.

Disclaimer

It is the customer's responsibility to review the advice provided herein and its applicability to the system. Red Lion makes no representation about specific knowledge of the customer's system or the specific performance of the system. Red Lion is not responsible for any damage to equipment or connected systems. The use of this document is at your own risk. Red Lion standard product warranty applies.

Red Lion Technical Support

If you have any questions or trouble contact Red Lion Technical Support by clicking here or calling 1-877-432-9908.

For more information: http://www.redlion.net/support/policies-statements/warranty-statement