Rockwell Automation T80015 Application Note Trusted SC300E Migration Process - Manual (Page 16)

Trusted TM
AN-T80015
Issue 01 Apr 08 AN-T80015 Page 16 of 16
Migration Process – Flow chart
Obtain ‘As
Operational’ system
file
Debug System
Trusted
fault flags
Application logic
Board definitions
Identify
Hardware
Create ini file + hot
repair associations
SC300E
fault flags
Swap MPPs for 8161 Bridge modules
Set links for each chassis, remember Trusted chassis is No1, first SC300E is No2
Fit load resistors to Chassis 2 5v supply to compensate for low current drawn by Bridge modules Hardware Upgrade
Chassis 1 = Trusted controller chassis
What was SC300E chassis 1, is now logical chassis 2
Communication, Modbus settings
SC300E I/O modules have the option of 3-2-1 or 3-2-0. make sure the correct one is selected.
TM117-DMX TMs must appear in the list before any SC300E I/O modules
Set chassis / slot definitions
Create and wire up tags for faults on the SC300E chassis, eg. Slice, internal power, field power,
watchdog etc
Timers issues
Mirror existing system by using ladder logic or start again with FBD
Register mapping
SOE – duplicate tags required
System sizing – mounting of controller, is there room in an existing cabinet?
If in a test or demo system what test panels are needed for inputs and outputs?
Cables and lengths required
In many instances the system will have had software modified and archived without updating the
operational or as-built files. It is very important to base the migration on up to date information to
avoid nasty surprises on site
Identify / create
Registers,
Discretes and Tags
Create spreadsheet of tags, discretes, registers etc in Excel, then create library in Trusted Toolset
Create and wire up tags for faults on the Trusted controller chassis, eg. Expander, Bridge and
comms modules
Scope of Supply
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)
Pre-upgrade tests
Go through the test procedure on the existing system before making any changes to give you a
performance benchmark to test the system against after the upgrade is completed