DSRF197模擬量通信框架
而前幾頁所述的程序聯(lián)系人類型可根據(jù)需要使用為了捕獲系統(tǒng)中所選點(diǎn)、模塊或元件的故障或報警狀態(tài)，PLC的故障表是所有類型故障發(fā)生時自動生成的日志。
這種故障信息的組合提供了系統(tǒng)操作的更廣泛視圖并且有助于指示多個故障和警報之間的因果關(guān)系。
I/O故障表中的故障數(shù)
I/O故障表最多可包含32個故障。其他錯誤會導(dǎo)致表溢出，并丟失錯誤。系統(tǒng)參考IO_FULL（%S00010）設(shè)置為表明：故障表已滿。
發(fā)生故障時，前16個將記錄到表中，并保持在表中，直到再次清除；如果表溢出，這16個錯誤都不會被刪除。過失17通過32，故障表作為先進(jìn)先出堆棧運(yùn)行。當(dāng)故障33發(fā)生時，
故障17從表中刪除。清除故障表將刪除所有故障列表。
清除故障
必須從I/O故障表中清除故障，以便在PLC CPU和待清除的相關(guān)故障觸點(diǎn)。
可以從編程器屏幕或通過清除故障表中的故障應(yīng)用程序。
清除故障表將刪除其中包含的故障；它不清除中的故障條件系統(tǒng)。如果導(dǎo)致故障的條件仍然存在并被檢測到，則故障將通常再次報告。但是，如果故障被配置為致命故障
（停止PLC的一個），清除后將不再報告故障。這允許PLC進(jìn)入運(yùn)行模式。
總線錯誤率高導(dǎo)致的設(shè)備故障損失
如果總線出現(xiàn)高錯誤率（可能是由于電氣干擾或損壞的電纜）、設(shè)備故障丟失可能會記錄到故障表中。裝置損耗與I/O總線故障一起記錄的故障通常可歸因于總線安裝質(zhì)量差。應(yīng)盡快糾正導(dǎo)致總線錯誤的情況。FIP總線控制器產(chǎn)生的故障
對于FIP總線故障，顯示屏顯示故障發(fā)生的日期和時間以及以下信息：I/O故障的位置始終包括FIP的機(jī)架和插槽并且可選地包括遠(yuǎn)程訂戶地址。
故障位置還可能包括的遠(yuǎn)程機(jī)架和插槽遠(yuǎn)程I/O設(shè)備中出現(xiàn)故障的I/O模塊。不習(xí)慣。
已發(fā)生故障的一般類型。對于診斷故障
CPU設(shè)置故障參考。對于致命故障，CPU設(shè)置故障參考并將其自身置于停止模式。
進(jìn)一步解釋了故障類別：電路故障、模塊故障、I/O總線故障、塊丟失和IOC軟件異常。提供有關(guān)電路和模塊故障的附加信息。
While the types of program contacts described on the previous pages can be used as needed
to capture the fault or alarm status of selected points, modules, or elements in the system,
the PLC’s fault tables are an automatically-generated log of faults of all types as they occur.
This grouping together of fault information provides a broader view of system operations
and helps indicate causal relationships among multiple faults and alarms.
Number of Faults in the I/O Fault Table
The I/O Fault Table can contain up to 32 faults. Additional faults cause the table to overflow, and faults are lost. The system reference IO_FULL (%S00010) is set to indicate that
the fault table is full.
As faults occur, the first 16 are logged into the table and remain there until the table is
cleared again; none of these 16 faults will be dropped if the table overflows. For faults 17
through 32, the Fault Table operates as a First-In-First-Out stack. When fault 33 occurs,
fault 17 is dropped from the table. Clearing the Fault Table removes all the fault listings Clearing Faults
Faults must be cleared from the I/O Fault Table to be cleared in the PLC CPU and for the
associated fault contacts to be cleared.
Faults can be cleared from the Fault Table either from the programmer screen or by the
application program.
Clearing the fault table removes the faults it contains; it does not clear fault conditions in
the system. If the condition that caused a fault still exists and is detected, the fault will
normally be reported again. However, if the fault has been configured as a Fatal fault
(one that stops the PLC), the fault will not be reported again after clearing. This allows
the PLC to go to Run mode.
Loss of Device Faults Caused by High Bus Error Rate
If the bus is experiencing a high error rate (possibly due to electrical interference or
damaged cable), Loss of Device faults may be logged into the Fault Table. Loss of Device
faults that are logged in conjunction with I/O Bus Faults can usually be attributed to the
poor quality of the bus installation. The condition causing the bus errors should be corrected as soon as possible.Faults Generated by the FIP Bus Controller
For a FIP bus fault, the display shows the date and time the fault occurred, and the following information:
The location of an I/O fault always includes the rack and slot of the FIP
Bus Controller and optionally includes the remote subscriber address.
The fault location may also include the remote rack and slot of the
faulted I/O module within a remote I/O device.
Not used.
Not used.
The general type of fault that has occurred. For diagnostic faults, the
CPU sets fault references. For fatal faults, the CPU sets fault references
and places itself in STOP mode.
Further explains fault categories: Circuit Fault, Module Fault, I/O Bus
Fault, Loss of Block, and IOC Software Exception.
Provides additional information about Circuit and Module Faults.
