“Three people. The original integrator—retired. The plant manager—on vacation. And whoever is watching us right now.”
I didn’t answer. I knew this system. I’d rewritten half its function blocks from the original Japanese documentation. I clicked . Syswin chirped—that awful, optimistic beep—and the background of the ladder turned blue.
“It’s an HR area glitch,” said Marcus, pointing at the data table. The HR (Holding Relay) bit 1205 was flipping states like a dying neuron. “Probably a grounding issue.” Syswin 64 Bit Omron
He did. No changes in six years. But the checksum of the program in the PLC’s EPROM didn’t match the backup on our server. Not by a byte—by a single bit.
I looked at my offline backup drive. The .SYW file’s modified timestamp was 2:00 AM. The same time as the spike. “Three people
“Someone patched this in real-time,” I said. “No stop. No compile. Syswin’s 64-bit driver allows background memory writes if you have the right password.”
It was coming from the DM area (Data Memory). A direct move instruction (MOV #8730 DM0200) that didn’t exist in the printed schematic. A ghost rung. And whoever is watching us right now
That’s when I saw it.
But my computer had been off at 2:00 AM. I was in the control room the whole time.
At 2:00 AM, the reactor’s temperature didn’t just spike. It screamed.