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