I never found out who—or what—wrote that ghost rung. But every night since, when Syswin 64-bit runs in its compatibility mode sandbox, I watch the HR area. Waiting for bit 1205 to flip again.
“Marcus,” I whispered. “Pull the revision history.”
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.
“Three people. The original integrator—retired. The plant manager—on vacation. And whoever is watching us right now.” Syswin 64 Bit Omron
At 2:00 AM, the reactor’s temperature didn’t just spike. It screamed.
The next morning, the plant manager called. “Elena, did you install a new logic module last night? The audit log shows a 64-bit Syswin session from a COM port that doesn't exist.”
The phantom timer on Rung 23 reset. The hidden MOV instruction vanished from DM0200. The ladder reverted to its clean, original state. I never found out who—or what—wrote that ghost rung
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.
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.
“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.” “Marcus,” I whispered
The Ghost in the Ladder
And in the Syswin status bar, at the very bottom, a line of red text appeared for three seconds:
But my computer had been off at 2:00 AM. I was in the control room the whole time.
Unless something wants you to find it.