TrustedTM AN-T80015 Application Note TrustedTM / SC300E Migration process Issue 01 Apr 08 AN-T80015 Page 1 of 16
TrustedTM AN-T80015 Issue Number Date 1 Apr 08 Revised by Technical Check Authorised by Modification Andy Holgate Nick Owens Pete Stock Initial Issue Introduction The aim of this document is to provide a guide to the process of upgrading a Triguard SC300E system TM TM to a Hybrid SC300E / Trusted system by replacing the SC300E processors (MPPs) with Trusted TM 8161 Bridge Modules controlled by a Trusted processor.
TrustedTM AN-T80015 1. Upgrade Process 1.1. Scope of supply TM The first step of the Trusted required by the customer. SC300E migration process is to understand just what is • Is it a test/demo setup or is it an actual plant upgrade? • Does the client want to replicate the current user interface of the system as closely as possible so as not to confuse the operators.
TrustedTM AN-T80015 1.3. Tags, Discretes, Registers Create tags to get diagnostic data from modules and wire them to the appropriate board in the Toolset. Create logic programs to derive alarms from diagnostic data, for example processor temperature, processor voltage etc. Using the information in the system folder create a spreadsheet of all the tag names, discretes and registers along with descriptions and any other relevant data.
TrustedTM AN-T80015 1.4.3. Firmware calls The SC300E application has several calls to the system firmware such as USR3, USR4, FALT etc. These are user configured and may have bespoke code designed to execute away from the application ladder. This means that if some of the functions in SC300E systems may need redesigning and they cannot be translated easily into ladder, structured text etc. Some calls usually involve system diagnostic functions, and can be replaced by application logic diagnostics. 1.4.4.
TrustedTM AN-T80015 2. Case Study – 2 chassis ESD system 2.1. Scope of Supply This upgrade was performed on a test system built for the purpose of documenting the migration process. 2.2. System Layout 2.2.1. Hardware Layout TM The system comprised a Trusted demo kit linked to a 2 chassis SC300E ESD system with test switches and LEDs to simulate field I/O. 2.2.2.
TrustedTM AN-T80015 2.4. Application logic It was decided to use ladder logic to mirror the existing system as much as possible so as to minimise the change for the users, although there are some things to bear in mind. Each I/O module is mapped to blocks of discretes (Booleans) in groups of eight, which are not necessarily in order.
TrustedTM AN-T80015 An acceptable alternative is to use Structured Text, which allows complex program flow using IF, CASE, REPEAT and other flow control statements. The CASE statement allows the creation of a state machine In SC300E, only one network is run at a time, so the programmer may concentrate on the operation of that network without worrying about its influence on other networks.
TrustedTM AN-T80015 Alarm and Normal, and these state names will also appear in the log. The point can now transfer events from the application to the SOE log, which can be collected either by an OPC TM TM client through the Trusted OPC server, or using the Trusted SOE collector program running on a PC. There is no need to clear the logs. The processor event log contains 200 events and is cyclically overwritten.
TrustedTM AN-T80015 2.5. Diagnostics I/O module and system diagnostics flags are listed in PD 8161 for the SC300E products. TM The Trusted terminal program may be used to access a command line interface, where commands are available to extract information on module status and chassis configuration. Diagnostic data on module health, discrepancies and LFD errors is also available in the application through the I/O connection boards for each module.
TrustedTM AN-T80015 2.6. Mechanical upgrade TM Remove the SC300E ICCBs and replace with the 3x Trusted 8161 Bridge Modules. The Bridge module requires minimum configuration, namely the setting of Unit ID jumpers 0 to 3 to define the chassis address to Trusted™. These are situated on the Triguard chassis as shown here. The four backplane jumpers represent the binary address bits 1, 2, 4 & 8 respectively.
TrustedTM AN-T80015 TM Clicking on a SC300E chassis in the Trusted System Configuration tool and selecting ‘Jumper Config’ will display the required jumper settings for that chassis. The link settings on the Triguard BIC chassis refer to the ‘Triguard Chassis Number’ not the TM ‘Logical Chassis Number’ which is the overall position of the chassis in the Trusted system. The Controller rear view shows all connections available via the Interface Adapters.
TrustedTM AN-T80015 3.
TrustedTM AN-T80015 4. Sample logic comparisons TM Some of the networks can be programmed in Trusted to closely mirror the original.
TrustedTM AN-T80015 TM Some networks cannot be programmed the same way in Trusted which handle the internal diagnostics: as in SC300E, for example those SC300E programming TM Trusted programming 5.
TrustedTM AN-T80015 Migration Process – Flow chart Test setup or full plant upgrade.? What Communication links are required. (Peer-to-Peer, DCS, DMX, OPC etc. How many Trusted controllers required. (cannot communicate with SC300E directly with Peer-to-Peer so all linked systems must be upgraded) In many instances the system will have had software modified and archived without updating the operational or as-built files.
