He right-clicked the controller in the I/O tree and selected . He unchecked "Major Fault on Controller if Connection Fails While in Run Mode." If the download faulted, he didn't want the controller to halt. He set the "Program Mode to Run Mode" transition action to "Last State" for all outputs. Not safe for all machines, but for this one, better than zeroing out a valve.
90%... "Starting controller."
70%... "Loading project."
A groan. "Alex, batch 880 is at T+3 hours. We're in the exothermic hold phase. How long is the actual download ?"
He clicked .
Alex opened three windows side-by-side. Window 1: RSLogix 5000 with the modified routine. Window 2: The SoftLogix chassis monitor. Window 3: A continuous ping to the remote I/O rack's IP address (192.168.1.10). He also had a VNC connection to the server itself.
Marcus’s voice came back: "We’re stable. All loops re-synced. The blip was acceptable. You’re good." softlogix 5800 download
Marcus sighed. "You have the window. I'm calling the shift manager. Clock starts in ten minutes."
The ping resumed. Reply from 192.168.1.10: time=2ms. Then a flood of replies. The I/O rack was back. In RSLogix, the controller status icon blinked from "Program" to "Running." The Green Run LED on the virtual chassis turned solid. He right-clicked the controller in the I/O tree and selected
50%... "Clearing memory." Alex held his breath. This was the danger zone. If the SoftLogix service crashed now, the server would need a full reboot.
"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." Not safe for all machines, but for this