Home › Technical articles

Đọc bằng tiếng Việt

Maintaining AADvance and Trusted while running: module replacement, firmware and online changes

TDL Industrial Automation · Last updated:

From Rockwell's AADvance and Trusted manuals and release notes: what both manuals advise on online changes and MOC, replacing processors and I/O modules on a running system, Trusted companion slots and SmartSlots, why AADvance firmware is upgraded only in Recovery Mode, AADvance online updates and Trusted Normal and Intelligent Updates, testing after a change and the records to keep.

A safety instrumented system (SIS) runs for years without a stop, and stopping it means stopping the plant or running without that layer of protection. AADvance and Trusted allow some maintenance while the system runs, within limits their manuals set. This article sets out what Rockwell's documents say about replacing modules, upgrading firmware and changing the application on a running system, and the records to keep. It describes the vendor documents, not a work procedure: every change on a running SIS goes through the plant's management of change (MOC) and permit to work. The architectures are covered in AADvance vs Trusted.

1. What both manuals say first

The AADvance safety manual highly recommends that online changes are not performed unless absolutely necessary, as they could reduce the safety integrity of the system while the change is made; alternative safety measures must be in place for its duration (ICSTT-RM446S, p. 85). Online modifications must follow the end user's MOC process and include any checks Rockwell recommends for the product, and changes that affect the system's ability to respond safely are not made online without alternate protection (p. 86). The Trusted safety manual also highly recommends that online changes are not performed; where they have to be, it recommends doing them with alternative safety measures in place or when the affected hazards cannot arise (ICSTT-RM459K, p. 70).

Both manuals make the change procedures the end user's responsibility, with guidance from the system integrator, and ask for special consideration of module and firmware updates, with an impact analysis and an authorization process (ICSTT-RM406J, p. 74; ICSTT-RM459K, pp. 28–29). The AADvance maintenance manual also warns that removing modules, wiring or cables with power applied can cause an arc, and must not be done unless the location is known to be non-hazardous (ICSTT-RM406J, pp. 15, 41).

2. Replacing a module on a running system

AADvance. All modules permit live removal and replacement in redundant configurations, and a faulty module should be replaced so that faults do not accumulate (ICSTT-RM406J, p. 73). A processor can be replaced online provided at least one processor stays fitted and fully operational; modules go in one at a time, each allowed to educate before the next, and the replacement's firmware revision must match the processors already fitted. The same rule applies to I/O modules in a dual or triple termination assembly (ICSTT-RM446S, p. 69).

The locking screw is also a power interlock: a module does not start until it is locked, and unlocking a running module takes it out of service (ICSTT-RM446S, pp. 68–69; ICSTT-RM406J, p. 43). A new module educates, then goes online after a Fault Reset on a processor; one that fails to educate is replaced (ICSTT-RM406J, pp. 44–45, 69–70).

Trusted. All modules permit live removal and replacement, and modules in a fault-tolerant configuration can be removed with no further action. A module with no partner slot or SmartSlot, in a fail-safe configuration, needs override or bypass signals while it is out (ICSTT-RM459K, pp. 27–28).

The TMR processor is repaired online in the adjacent slot (ICSTT-RM459K, p. 34). In this companion slot arrangement a standby processor runs its own diagnostics, is kept updated by the active one and takes over in a bumpless changeover (PD_T8110B/T8110, pp. 26–27). The product description cautions never to remove a module that indicates Active mode, because the chassis may go to its shutdown state, and says changeover is inhibited while any I/O is forced; its section 5.3 gives the replacement steps (p. 40).

High-density I/O can be replaced in a hot-swap pair (companion slot), with a SmartSlot, or by live insertion and removal. The manual asks for one replacement approach per system and a test of the SmartSlot linking cable before use (ICSTT-RM459K, pp. 54–55). One spare part trap: a large application written for a T8111 processor may not fit a T8110B, so the impact analysis checks that it loads (p. 34).

Working on a running AADvance or Trusted SISFive steps from top to bottom, from Rockwell's AADvance and Trusted manuals. 1 Back up and record: archive the application and system.ini, a tested backup, the software release and firmware. 2 MOC and permit: impact analysis, authorization, alternative safety measures for the duration, a non-hazardous location before modules are removed under power. 3 Do the work: modules one at a time, allowed to educate, firmware matching; never remove a Trusted processor that shows Active; online updates within their limits, with the Program Enable key or the keyswitch in Maintain. 4 Test: the change and non-regression testing, plus simulator, cross-reference and code compare on Trusted. 5 Record: the change, the test results, faults with serial numbers, forces removed, key back to Run. Red band at the bottom: AADvance processor firmware is not upgraded on a running system; the T9110 takes firmware only in Recovery Mode, where the application stops and outputs de-energize.Working on a running AADvance or Trusted SIS1. Back up, recordbefore touching the systemarchive the running application and system.ini (Trusted)configuration backup copy tested (AADvance)software release and firmware of each module2. MOC and permitthe plant's ownimpact analysis and authorizationalternative safety measures for the durationnon-hazardous location before removing modules under power3. Do the workreplace a module orchange onlineAADvance: one module at a time, educated, matching firmwareTrusted: never remove a processor that shows Activeonline update within its limits; Program Enable key orkeyswitch in Maintain4. Testbefore and after the downloadthe change and non-regression testingTrusted: simulator, cross-reference, code compare5. Recordwhen the work is donethe change and the test resultsfaults and failures with serial numbersforces removed, key back to RunAADvance processor firmware: not upgraded on a running system. The T9110 takesfirmware only in Recovery Mode; the application stops and outputs de-energize.Based on Rockwell Automation ICSTT-RM446S (10/2024) pp. 69, 85–86, 92; ICSTT-RM406J (02/2021) pp. 15,23–29, 73–74; ICSTT-RM459K (11/2023) pp. 27–29, 70–72; PD_T8110B/T8110 Issue 22 p. 40.Read 22 November 2026. Not a work procedure. Figure: drawn by TDL.
Figure 1: Working on a running AADvance or Trusted SIS. On a phone, swipe sideways to see the whole figure.

3. Firmware upgrades

The maintenance manual warns not to upgrade firmware on a running system: ControlFLASH does not warn that the system is running, and control of the application is lost when it reboots (ICSTT-RM406J, pp. 23, 28). It also states that firmware cannot be upgraded when the system is operational: the T9110 accepts firmware only in Recovery Mode, where no application runs and outputs de-energize (p. 29); the safety manual calls Recovery Mode a shutdown mode (ICSTT-RM446S, p. 68). The Recovery Mode firmware is updated first, then the operating firmware, and the version is checked afterwards (ICSTT-RM406J, pp. 25, 29; ICSTT-RM448N, p. 51). A processor firmware upgrade on AADvance is therefore work for a planned shutdown. What can happen online is adding a processor whose firmware already matches; the manual says a second or third processor with a different revision is first upgraded with ControlFLASH (ICSTT-RM406J, p. 44).

Software and firmware come as a set. SIS Workstation 2.01.01 goes with Trusted release 4.0 and AADvance release 2.011 (release notes). The Trusted 3.6.1 release note requires T8110B firmware and the Toolset Suite from the same release, and asks for the notes of earlier major revisions to be reviewed before any update (ICSTT-RN007A, pp. 2–3). The Trusted documents we read neither describe a procedure for upgrading processor firmware on a running system nor rule one out; plan Trusted firmware work from the release notes for your release, with Rockwell Automation support.

4. Changing the application online

AADvance. An online update changes a controller while the application runs: bindings, variables, programs, functions and function blocks, I/O channels and modules, within the limits the configuration guide lists (ICSTT-RM458D, pp. 65–67). Online updates of the I/O configuration are disabled by default and must be enabled first, and memory for online changes and the number of extra POUs are reserved in advance (pp. 59, 65–66). A wrong change can stop the application (p. 66), and the I/O data flow can be interrupted (ICSTT-RM448N, p. 51). The Program Enable key is fitted for the change and removed afterwards (ICSTT-RM446S, p. 92). After a project is migrated from an older AADvance Workbench, the release notes say only a download is supported on those controllers.

Trusted. The safety manual names Normal Updates, limited to changes in logical operation, and Intelligent Updates from release 3.4, enabled per project. With Normal Updates, a change beyond the predefined limits rules out online modification and the application has to be stopped (ICSTT-RM459K, pp. 70–71). Before a revised application goes to a running system, the manual requires simulator testing, cross-reference checks and a code compare, with retest of every program found changed, and the download only with the processor keyswitch in Maintain (pp. 70, 72). High-density I/O changes in the system configuration file (system.ini) need an application stop and restart, and new I/O points not already in the application need the system offline (p. 72). After the work, the keyswitch goes back to Run and the key is removed (p. 86).

The SIS Workstation user guide adds that regular updates cannot add or delete global variables or function blocks, so spares are declared in advance (ICSTT-UM002D, pp. 568–569). The release notes warn that the software does not show when a Trusted download or update has failed, and give the checks to confirm it.

Every change is tested, itself plus non-regression testing, with results recorded (ICSTT-RM406J, p. 74; ICSTT-RM459K, p. 29). Testing against the matrix is covered in Cause and effect matrix and SIS testing.

5. Records and baselines

  • Before the change: the Trusted manual requires the running application and system.ini to be archived, and asks for a reference copy of the tested application to compare against (ICSTT-RM459K, pp. 70–72). The AADvance checklist asks whether the configuration backup copy has been tested (ICSTT-RM446S, p. 92).
  • Baselines: after a declared baseline, at the latest before startup, every change follows the formal procedure (ICSTT-RM459K, p. 29); see also SIS useful life and mission time.
  • Records: each change is traceable and its impact considered before it is authorized (ICSTT-RM406J, p. 74); faults and failures are recorded with module types and serial numbers (p. 73).
  • No forcing as a bypass: both manuals keep I/O forcing for engineering and commissioning; in service, maintenance overrides are built in the application (ICSTT-RM446S, p. 76; ICSTT-RM459K, p. 55).

What we check first

This is TDL's practice, not a Rockwell Automation requirement.

  • The MOC and the permit come first: the plant names the alternative safety measures and who authorizes the work.
  • We take a tested backup of the Workbench, SIS Workstation or Toolset project (and system.ini on Trusted) and record the software release and module firmware.
  • We read the release notes for the software and firmware pair, and check that a spare module's revision matches the modules fitted.
  • We decide in advance whether the change can be made online at all; AADvance firmware, Trusted high-density I/O changes and changes beyond the update limits need a planned stop.
  • We keep a way back: the archived application, ready to reload in a planned stop.
  • Afterwards we check that no point is left forced, the keyswitch or Program Enable key is back in its run position, and the change and its tests are recorded.

How TDL approaches it

TDL builds SIS for SIL 2 and SIL 3 functions on AADvance and Trusted, including ESD and Fire & Gas, through our ICSS and safety systems service; our yearly maintenance contracts cover scheduled visits and backups compared with the last baseline. At Thai Binh 2 Thermal Power Plant, TDL provided technical consultation for the ESD system on Trusted: field operation and testing according to the SAT documents, Trusted hardware and logic consulting, and resolution of ESD problems and errors. On Vietsovpetro's Central Compressor Platform, TDL supplied the main materials, including the AADvance PLC, and engineering consulting for a SIL 3 fire and gas system. On the Riserblock platform, TDL upgraded a Sieger fire and gas system to AADvance with fault-tolerant I/O.

Frequently asked questions

Can AADvance processor firmware be upgraded while the plant runs?

No. The AADvance maintenance manual warns against upgrading firmware on a running system and states that firmware cannot be upgraded when the system is operational. The T9110 takes firmware only in Recovery Mode, where the application stops and outputs de-energize, so the upgrade belongs in a planned shutdown.

Can a Trusted processor be replaced without stopping the system?

Yes, in the companion slot arrangement: a standby processor is educated by the active one and takes over in a bumpless changeover. The product description says never to remove a module that shows Active mode, and changeover is inhibited while any I/O is forced.

What can be changed with an online update?

On AADvance, the configuration guide lists bindings, variables, programs, functions and function blocks, and I/O channels and modules, with I/O updates enabled first. On Trusted, Normal Updates allow limited logic changes and Intelligent Updates allow more; high-density I/O changes in system.ini and new I/O points need a stop. Both safety manuals highly recommend against online changes.

Can I/O forcing be used as a bypass while a module or transmitter is replaced?

No. Both safety manuals keep forcing for engineering, installation and commissioning, and ask for maintenance overrides built in the application program. A Trusted module without a partner in a fail-safe configuration needs override or bypass signals while it is removed.

What has to be tested after an online change?

The change itself and the rest of the application through non-regression testing, with the results recorded. The Trusted manual also requires simulator testing, cross-reference checks and a code compare before the revised application is downloaded.

Sources

  • Rockwell Automation, ICSTT-RM446S-EN-P, AADvance Controller Safety Manual, 10/2024 — pp. 68–69, 76, 85–86, 92
  • Rockwell Automation, ICSTT-RM406J-EN-P, AADvance Controller Troubleshooting and Maintenance Manual, 02/2021 (written for system release 1.40) — pp. 15, 23–29, 41–45, 69–70, 73–74
  • Rockwell Automation, ICSTT-RM448N-EN-P, AADvance Controller System Build Manual, 09/2024 — p. 51
  • Rockwell Automation, ICSTT-RM458D-EN-P, AADvance Controller Configuration Guide (Workbench 2.x), 02/2021 — pp. 59, 65–67
  • Rockwell Automation, ICSTT-RM459K-EN-P, Trusted TMR System Safety Manual, 11/2023 — pp. 27–29, 34, 54–55, 70–72, 86
  • Rockwell Automation, ICSTT-UM002D-EN-D, AADvance-Trusted SIS Workstation Software User Guide, 10/2023 — pp. 568–569
  • Rockwell Automation, PD_T8110B/T8110, Trusted TMR Processor product description, Issue 22, 06/2016 — pp. 26–27, 40
  • Rockwell Automation, ICSTT-RN007A-EN-P, Trusted TMR Controller Release Note for Revision 3.6.1, 05/2016 — pp. 2–3
  • Rockwell Automation, SIS Workstation Programming Software (T9090, T8090) Release Notes, version 2.01.01, 01/2026 — sections "Firmware requirements", "AADvance project migration" and the note on Trusted downloads (no page numbers in the document)

Read 22 November 2026. This article paraphrases the sources and quotes them only briefly; read the original documents and the release notes for your release before working on a system. Links open the latest edition in Rockwell's literature library; page numbers refer to the edition cited.

Related services:
Oil & gas ICSS & safety systems Yearly maintenance contracts