And, true to form (as colleagues used to say, "Salem is consistently inconsistent!), GE Salem documented NOTHING. In the process, and as CIMPLICITY matured and GE Salem learned how to use CIMPLICITY functions, the way that many functions-PARTICULARLY CPBs (Control Push-Buttons) were changed and changed and changed. SO, in the Mark* V they interposed TCI (Turbine Control Interface), a GE proprietary MS-Windows service to serve as a "buffer" to keep people out of that communication protocol. BUT they didn't want to allow people/control system integrators/anyone to be able to use it to communicate directly with the Mark* turbine control panel. GE Salem opted to use CIMPLICITY (now called PROFICY MACHINE EDITION) as the graphical user interface for the Mark* turbine control system (beginning with Mark* V). THIS is one of the most frustrating parts of the Mark* turbine control system. And, it would help if we could "see" the CSP (Control Sequence Program) to understand a little better the signal being toggled. It's most likely NOT CIMPLICITY that's doing the setting/resetting as much as it's the Operating System in the Mark* V when it gets the command from the HMI (CIMPLICITY) to do the setting/resetting. "Why the number 16 instead of the number 1? It all depends on how the number 16 (decimal) is interpreted in the program." Would Cimplicity do something behind the scenes to set S1_L52T_CPB back to 0? For the logic to work, the Mark V contact has to be pulsed closed, not maintained closed. I haven't found any buttons or procedures that will set S1_L52T_CPB back to 0 (or whatever value is needed to open the contact in the Mark V). Why set the point to 16? Wouldn't 1 make more sense? These is a contact in the Mark V logic called L52T_CPB that should be closed by this button. Ctrl_Turb_Shut uses the AbsoluteSetpoint action to set the point S1_L52T_CPB to 16. Mouse Up calls procedure Ctrl_Turb_Shut. Turbine Shutdown button has an event defined for Mouse Up. There is a button on the main screen labeled Turbine Shutdown. Here's a more detailed description of what I am seeing: Just need to understand how the existing system works. Most likely I am missing some specific info on how Cimplicity interfaces with the Mark V. I think I understand the concepts around Events, Procedures, Points, etc. I've reviewed the GE manual you referenced, as well as Cimplicity's built-in help info.
0 kommentar(er)
