DSDP170通信模块
本章介绍了检查系统状态的机制：系统故障触点。使用程序中的这些预定义联系人检查：特定故障，如系统配置不匹配、机架丢失或总线故障。
故障/无故障点触点。使用这些触点监控单个、离散和模拟点的故障或缺乏故障状态。
故障/无故障用户触点。使用这些联系人可监视的状态FIP网络上的设备。
报警触点：使用这些触点监控模拟参考是否：达到其报警上限或下限。
故障表：PLC的故障表提供了更广泛的系统操作视图，以及帮助指示多个故障和报警之间的因果关系。
总线控制器和信道状态位：使用这80个状态位监控操作总线控制器和两条总线，并监控多达32TCP/IP通信信道。附加诊断
本章描述了FIP总线控制器对网络故障的正常记录
第8章解释了网络故障信息如何存储在选定区域中以及如何将某些网络故障记录到PLC故障表中
残废系统故障触点在%S内存中有预定义的昵称和位置。他们可以包括在应用程序中以检查故障相关条件。以下系统故障触点对于具有FIP总线控制器的系统特别重要：PLC系统包括一个总线控制器。在CPU配置期间，系统状态故障LOS_IOC已被指定为诊断（而非致命）故障。LOS_ IOC表示总线控制器的丢失；如果发生这种情况，IOC故障的损失将被置于I/O故障表。在本例中，应用程序还监控LOS_IOC
参考如果设置了该参考，则触点将功率流传递到输出线圈，输出线圈使操作员面板上的警告灯通电。故障和无故障触点可用于检测系统上的故障或缺少故障条件离散（%I）或模拟（%AI）参考。
故障触点[故障]将检测离散或模拟输入或输出中的故障，或系统的硬件组件。如果参考有以下情况，则触点通过功率流：错误。故障和无故障触点由来自输入模块。如果无法使用验证器信息，例如设备失去电源或网络连接，或数据未刷新或未激活，故障触点将由FIP总线控制器设置。如果未配置验证程序信息对于消耗，永远不会设置故障触点。
This chapter describes mechanisms for checking the status of the system:
System Fault Contacts. Use these predefined contacts in the program to check for
specific faults such as System Configuration Mismatch, Loss of Rack, or Bus faults.
Fault/No Fault Point Contacts. Use these contacts to monitor individual discrete and
analog points for their fault or lack of fault status.
Fault/No Fault Subscriber Contacts. Use these contacts to monitor the status of
devices on the FIP network.
Alarm Contacts: Use these contacts to monitor whether analog references have
reached their upper or lower alarm limits.
Fault Table: the PLC’s fault tables provide a broader view of system operations and
help indicate causal relationships among multiple faults and alarms.
Bus Controller and Channel Status Bits: Use these 80 status bits to monitor the
operation of the Bus Controller and two busses and to monitor the status of up to 32
TCP/IP communications channels.
Additional Diagnostics
This chapter describes normal logging of network faults by the FIP Bus Controller.
Chapter 8 explains how network fault information can also be stored in a selected area
of PLC memory, and how logging certain network faults into the PLC fault table can be
disabled.System fault contacts have pre-defined nicknames and locations in %S memory. They
can be included in an application program to check for fault-related conditions. The following system fault contacts are of special interest for a system with a FIP Bus Controller:A PLC system includes one Bus Controller. During CPU configuration, the system status
fault LOS_IOC has been designated a diagnostic (rather than fatal) fault. LOS_IOC represents loss of the Bus Controller; if this occurs, the Loss of IOC fault will be placed in the
I/O Fault Table. In this example, the application program also monitors the LOS_IOC
reference. If this reference is set, the contact passes power flow to an output coil, which
energizes a warning light on an operator panel.Fault and No Fault contacts can be used to detect fault or lack of fault conditions on a
discrete (%I) or analog (%AI) reference.
A Fault contact [FAULT] will detect a fault in a discrete or analog input or output, or a
hardware component of the system. The contact passes power flow if the reference has
a fault.Fault and No Fault contacts are driven by consumption of validator information from the
input module. If the validator information cannot be consumed, for example, if a remote
device loses power or network connection, or data is unrefreshed or unprompt, the Fault
contacts will be set by the FIP Bus Controller. If no validator information is configured
for consumption, the Fault contact will never be set.
