![]() |
||||||
|
|
 |
History Abb Drive Programming Software LinkThe terminal room on Level 4 of the Pelican Island Desalination Plant smelled of ozone and old coffee. Elara Vasquez knelt on a rubber mat, her tablet tethered to an ACS880 drive via a dusty USB-to-ABB cable. On her screen, the Drive Composer Pro interface glowed—a constellation of parameter lists, logic diagrams, and adaptive programming blocks. She opened the . In Drive Composer Pro, parameters aren’t just numbers. They’re a map of the drive’s nervous system: 99.01 (Motor nominal voltage), 20.03 (External fault 1 source), 47.01 (Adaptive programming enable). She navigated to group 47: Adaptive Programming . Hiroshi had used it like a tiny PLC inside the drive—logic gates, timers, comparators, all running at millisecond speed. She downloaded the modified program. The drive’s green LED blinked twice. Parameter save complete. abb drive programming software She pulled up the tool inside Composer Pro. Most techs used the standard control macros—Pump, Fan, Torque. But the plant had been built in 2009 by a reclusive automation engineer named Hiroshi Okada. Hiroshi didn’t use macros. He wrote custom sequential function charts (SFCs) and hid them like traps. Outside, the brine pump ramped up smoothly. The ghost was gone. But Hiroshi’s signature remained—a neat comment at the top of the SFC: The terminal room on Level 4 of the No more forced faults. Just a warning that would appear in the plant’s SCADA history. The pump would keep running—but maintenance would know. She shut the cabinet door. The drive hummed. And for the first time in two weeks, the fault log stayed empty. She opened the Hiroshi had programmed a hidden safety timer . When the conductivity sensor drifted below 4mA—a sign of scaling or air in the line—the drive didn’t stop abruptly. It waited thirty minutes, then pretended to lose communication. It was a cry for help from a machine that couldn’t speak. On step 47 of the SFC, a custom code block read: Philosophy WinEpi 2.0 has been designed as a cooperative platform in order to provide epidemiological tools to scientific and academic community. For this reason it is important to strengthen the self-learning ability including with step-by-step guidelines and solved examples. Functions and examples will be available in different languages and everybody could submit proposal to implement new formulae, to suggest examples and to collaborate as translators. Our aim is that copyright of all material belongs to contributors that share them with the community under Creative Commons licence. Contributors If you would like to contribute to new WinEpi, you can Contact us and indicate that you want to be included in the Contributors database Institutions These institutions and companies support WinEpi project:
|
![]()
|
Optimized for Google Chrome and screen resolutions: horizontal 1280x800 or vertical 800 x 1024