ABB控制系统用于PFSK115 YM322001-EX卡件
创建事件处理器模块和某些类型的I/O模块都能够创建事件。在以下各节中，这些I/O模块称为SOE模块。在处理器模块上创建事件处理器模块使用全局变量创建事件并将其存储在缓冲器中，参见第3.4.7章。事件是在用户程序周期中创建的。在SOE模块上创建事件SOE模块可以使用输入状态创建事件。事件是在SOE模块周期中创建的。SOE模块将事件存储在处理器模块用来读取事件的中间缓冲区中。中间缓冲区是易失性存储器的一部分，因此，如果电源关闭，事件就会丢失。已读取的每个事件都可以被新事件覆盖。系统事件除了记录全局变量或输入信号变化的事件外，处理器和SOE模块还创建以下类型的系统事件：溢出：由于缓冲区溢出，某些事件未存储。溢出事件的时间戳与导致溢出的事件的时间戳记相对应。初始化：事件缓冲区已初始化。操作模式停止：SOE模块将其操作模式更改为停止。操作模式“运行”：SOE模块将其操作模式更改为“运行”。建立通信：处理器模块和SOE模块之间的通信已开始。失去通信：处理器模块和SOE模块之间的通信被终止。系统事件包含导致事件的模块的SRS标识符。
状态变量
状态变量为用户程序提供标量事件的状态。以下每个状态都连接到一个状态变量，可以分配一个BOOL类型的全局变量：超出下限。超出最低限制。超出上限。超出最高限制。当达到相应状态时，指定的状态变量变为TRUE。3.4.7记录事件处理器模块收集事件：由处理器模块自身创建的I/O模块创建。处理器模块将所有事件存储在其缓冲区中。缓冲区是非易失性存储器的一部分。具有5000个活动的容量。处理器模块按不同来源的事件到达的时间对其进行排列，而不按时间戳对其进行排序。如果事件缓冲区已满，则只要不读取其他事件并因此标记为被覆盖，就不能存储任何新事件。OPC服务器可以读取事件，并将其提供给外部系统进行评估和存储。3.4.8协议和接口通过以太网接口与外部系统通信。这些接口是10/100/1000 BaseT交换机的一部分。四个RJ-45连接器位于连接器板上。模块前板上的LED指示连接状态。有关更多信息，请参阅第3.4.11章。在这些接口上，模块可以处理以下协议：安全相关协议safeethernet连接到PADT
Creating Events
Both the processor module and certain types of I/O modules are able to create events. In the following sections, these I/O modules are referred to as SOE modules. Creating Events on the Processor Module The processor module uses global variables to create the events and stores them in the buffer, see Chapter 3.4.7. The events are created in the user program cycle. Creating Events on SOE Modules SOE modules can create events using the input states. The events are created in the SOE module cycle. The SOE module stores the events in the intermediate buffer that the processor modules use to read them. The intermediate buffer is part of the volatile memory so that the events are lost if the power is switched off. Every event that has be read can be overwritten by a new event. System Events In addition to events, which records changes of global variables or input signals, processor and SOE modules creates the following types of system events: Overflow: Some events were not stored due to buffer overflow. The timestamp of the overflow event corresponds to that of the event causing the overflow. Init: The event buffer was initialized. Operating mode Stop: A SOE module changed its operating mode to STOP. Operating mode 'Run': A SOE module changed its operating mode to Run. Establishing communication: Communication between processor module and SOE module has started. Losing communication: Communication between processor module and SOE module was terminated. System events contain the SRS identifier of the module causing the events.
Status Variables
Status variables provide the user program with the state of scalar events. Each of the following states is connected to a status variable and can be assigned a global variable of type BOOL: Lower limit exceeded. Lowest limit exceeded. High limit exceeded. Highest limit exceeded. The assigned status variable becomes TRUE when the corresponding state is achieved. 3.4.7 Recording Events The processor module collects the events: created by I/O modules created by the processor module itself The processor module stores all the events in its buffer. The buffer is part of the nonvolatile memory.and has a capacity of 5 000 events. The processor module arranges the events from different sources by the time of their arrival and does not sort them by their timestamp. If the event buffer is full, no new events can be stored as long as no further events are read and thus marked as to be overwritten. The OPC server can read the events and make them available to external systems for evaluation and storing. 3.4.8 Protocols and Interfaces Communication with external systems occurs via the Ethernet interfaces. The interfaces are part of a 10/100/1000 BaseT switch. The four RJ-45 connectors are located on the connector board. The LEDs on the front plate of the module indicate the connections statuses. For more information, see Chapter 3.4.11. On these interfaces, the module can process the following protocols: The safety-related protocol safeethernet Connection to the PADT
