Alex had done this a hundred times with a physical ControlLogix. Rack, connection, download. The world paused for 2 seconds, the PLC switched to program mode, the new code loaded, and it went back to run. With SoftLogix, it was different. The PLC was a software service. Downloading meant stopping the service .
The dialogue appeared: "WARNING: This operation will place the controller in Program mode and may cause a disruption to the process. Do you wish to continue?"
The progress bar crawled. 10%... "Verifying project." 30%... "Stopping controller." The ping to the I/O rack started timing out. Request timed out. Request timed out. The valves on the physical tank went silent. The pump VFDs froze at their last speed.
He typed into his logbook: "SoftLogix 5800 v20.04 download completed. No fault. Batch 880 unaffected. Lesson: Always, always take the .SLC file backup first."
Marcus’s voice came back: "We’re stable. All loops re-synced. The blip was acceptable. You’re good."
He picked up the wall-mounted phone and dialed the control room. "Marcus, it's Alex. I need a 14-minute maintenance window for the blend tank logic change."
"Total of almost three minutes without control?"
"Five seconds," Alex admitted. "But the SoftLogix service restart takes 90 seconds. Then another 60 seconds for the I/O connections to re-establish and the produced/consumed tags to sync with the packing line."
