TrustedTM AN-T80017 Application Note Regent to Trusted Migration This document describes the steps needed to replace a Regent processor chassis with a Trusted processor chassis. This replaces the Regent processor and communications modules and providing a future path to expansion of the Trusted system side. It assumes a knowledge of Trusted application design.
TrustedTM AN-T80017 Regent to Trusted Migration 1. Hardware The migration principles are identical for Regent (panel mount) and Regent +Plus (rack mount) because the internal circuitry is the same, as is the software. In this document, the term ‘Regent’ is used for both variants. The Regent processor chassis with processor and communications modules is replaced by a Trusted processor chassis with communications modules.
TrustedTM AN-T80017 Regent to Trusted Migration 1.1.
TrustedTM AN-T80017 Regent to Trusted Migration 2. Electrical The chassis and its modules are powered from a dual 24Vdc (nominal) supply, each supply providing at least 250W through 20A MCBs. If the Regent system power supplies are to be replaced, the T8200 range is recommended. These have 250W units in sets of three to match the Regent power needs.
TrustedTM AN-T80017 Regent to Trusted Migration Figure 2 Example Power Supply Overview Issue 2 June 08 AN-T80017 5
TrustedTM AN-T80017 Regent to Trusted Migration 3. Installation Both the Regent and Trusted are 3-2-0 degradation systems. When fully healthy, all three slices are working (3). On one fault, the remaining two slices can continue operating as long as they agree (2). On a fault in one of the two remaining slices, the system shuts down (0).
TrustedTM AN-T80017 Regent to Trusted Migration 4. Application There is no automated tool for application conversion from Regent to Trusted, and the applications are very different. However, it is possible to copy the functionality with the resulting programs looking similar to the original programs. Use the following steps to ease the process. In this section, ‘Winterpret’ is used as the name of the Regent application tool. Its predecessor was PDS, which is still in use on the older Regent systems.
TrustedTM AN-T80017 Regent to Trusted Migration Channel LEDs may be prevented from showing faults using the MONITOR_MASK as in Winterpret. The digital input monitoring thresholds are also entered on board parameters, as are any other parameters required in the Winterpret application. 4.3. Declaration of variables In Regent, the Modbus address map is automatically assigned to variables according to their position in the list.
TrustedTM AN-T80017 Regent to Trusted Migration 4.6. FLOAT function blocks These are very similar to Trusted structured text programs, and were designed to handle floating point arithmetic. Winterpret ladder programs can only handle integer arithmetic. These may be replicated as structured text in Trusted. 4.7. MODBUS MASTER function blocks These are replaced by the Modbus Master editor in the Trusted system configurator, for the appropriate communications interface.
TrustedTM AN-T80017 Regent to Trusted Migration 5. Application Examples Figure 3 Regent I/O Module Configuration Regent I/O configuration allows names to be applied to each I/O point and fault point which do not appear in the shared variables (the equivalent of the Trusted dictionary). It also allows the naming of 16-bit registers to carry all I/O points or faults in one tag, as shown above. The I/O operation is configured in the table (thresholds, redundant modules etc.).
TrustedTM AN-T80017 Regent to Trusted Migration In Trusted, all variables must be named in the dictionary and then connected to the appropriate data point on the board definition. The OEM parameters are used to specify the I/O operational parameters. The board definitions also handle some of the voting required, e.g. there is only one DO board below for both modules but two fault boards.
TrustedTM AN-T80017 Regent to Trusted Migration The Regent multiplexer module is a special case. This has multiple sub-windows for each multiplexer slave input or output board. Each multiplexed point can be given a name.
TrustedTM AN-T80017 Regent to Trusted Migration The Trusted implementation for multiplexed I/O is to use many separate I/O definitions. The Regent 7491 module should be declared before the I/O boards. Again, OEM parameters are used to define the board addresses.
TrustedTM AN-T80017 Regent to Trusted Migration Regent variables can be declared in the Shared Variables lists as Control Relays (Booleans), Registers (integers) and Floating Point Registers (reals). Variables can also be declared in the I/O connection table as the name of I/O data points, and even implicitly as local variables inside function blocks. Trusted variables must all be declared in the dictionary lists and used in the I/O connection table and programs.
TrustedTM AN-T80017 Regent to Trusted Migration Winterpret shared registers and shared floating point registers are in separate lists. Trusted integers and reals are all in the same list.
TrustedTM AN-T80017 Regent to Trusted Migration Winterpret allows multiple programs, each containing function blocks in different languages. Each program may be loaded and controlled separately. Trusted applications have only one ‘program’ containing multiple ‘function blocks’ by comparison, though the descriptive terms are different.
TrustedTM AN-T80017 Regent to Trusted Migration Regent ladder logic function blocks are on a fixed grid with 10 columns wide. Trusted FBD/LD programs allow free design with user function blocks. These two programs are not identical in their operation.
TrustedTM AN-T80017 Regent to Trusted Migration Regent is capable of floating point arithmetic in separate Math function blocks, using a structured text language similar to Trusted ST. In this case, FBD has been used as its replacement.
TrustedTM AN-T80017 Regent to Trusted Migration Regent has scaling functions as a separate function block language. These may be implemented with conversion tables or with programming in ST, or using FBD as implemented here.
TrustedTM AN-T80017 Regent to Trusted Migration Regent has a separate function block language for defining points to be collected by Sequence of Events. In Trusted, the evented points may be configured as outputs and wired to SOE boards (there is no native SOE on Regent I/O modules when in a hybrid system).
TrustedTM AN-T80017 Regent to Trusted Migration Communication settings are very different, by definition of the different architecture. Regent can have six ports which may be for diagnostics (COMM), text output (ASCII), Modbus slave or master or Regent Peer network. Trusted does not need allocation of a diagnostic port, and does not implement text output or Regent peer network. In this case, the ports are essentially unused.
TrustedTM AN-T80017 Regent to Trusted Migration Issue 2 June 08 AN-T80017 22
ICS Triplex technologies and services are available worldwide. Hall Road Maldon Essex CM9 4LA UK Tel: +44 1621 854444 Fax: +44 1621 851531 www.icstriplex.com For technical support email: support@icstriplex.com Sales enquiries: sales@icstriplex.
