Reconfiguration

Looking back at the schematics of 6T9's system you pondered how it would be possible to reach any of the three nodes that hadn't reset. Due to the damage in her system, the paths to reach them weren't working, but what if you could change the paths entirely? "MPAD-24, is it possible for 6T9 to perform a reconfiguration that would move any of these nodes into a functioning area?"

"Reconfiguration requires a calibration sequence," the floating robot replied with its monotone voice. "Would you like to perform this process for the selected nodes?"

"Not yet," you replied. "Before that, we need to find and disable any nodes sending reset messages. Otherwise those could erase one of the remaining ones that has the data we need."

You re-examined the messages and soon found the location of one that was broadcasting the reset to the system. "Send a message to this one to cancel the reset," you ordered.

"Acknowledged," replied MPAD-24, and soon the interface showed that the reset broadcasts were no longer active.

"Now perform the calibration to move these nodes," you replied. "How long will it take?"

"Due to system damage, time estimation is not available," stated MPAD-24. After a few minutes, it said, "Calibration failure. Due to system damage, first node cannot be moved." Several minutes later it announced, "Calibration failure. Due to system damage, second node cannot be moved."

"Damn it!" you muttered. If the third one couldn't be moved, there might not be any way to recover the data to keep 6T9's sentience intact. After waiting for several more minutes, MPAD-24 remained silent. Hopefully, that was a good sign.

Finally, MPAD-24 announced, "Calibration complete. Starting reconfiguration." Briefly, the stream of incoming data was disrupted. Since only one node was being moved it didn't take long for her system to perform the operation.

"Send a status request to the moved node," you ordered and then waited anxiously to see if it worked.