But Scout 4.3 had another layer. The safety logic. She opened the editor (the orange-tinged one that made her sign digital waivers). The STO (Safe Torque Off) was fine, but the SDI (Safe Direction) limit was set too aggressively for the new cam profile.

She recalculated the safe window using Scout’s integrated monitor, cross-checking the PROFIdrive telegram 105 with the actual motor encoder feedback. One decimal place. She adjusted the SDI tolerance from 2.5 mm to 3.1 mm—just enough to breathe, not enough to crash.

She saved the project—a .s79p file that now held 847 objects, 12,000 lines of motion control logic, and her professional pride.

She opened the for the D435-2 PN/DP controller. The motion control loop was textbook: position, velocity, torque. But the transition between the end of the fast-approach phase and the slow-press phase was where Z57 panicked. Scout’s trace function, with its fine-tuned time stamps and 1 ms resolution, revealed the ghost.

Scout v4.3 was her only weapon. To the uninitiated, it looked like a dense thicket of XML, MCC charts, and LAD/FBD blocks. But Mira knew its secrets. She had started on Scout 4.1, survived the migration to 4.3’s stricter DCC (Drive Control Chart) chaining, and learned to love its offline simulation environment as a kind of digital confessional.

That night, alone in the control room with a cooling cup of vending machine coffee, she went deeper.

She hit and traced the graph.

Mira’s boss, Henrik, had given her an ultimatum: “Fix it by Friday, or we roll back to the old pneumatic system.” The old system meant slower cycle times, lost contracts, and a permanent ding on her reputation.