TC512V1分布式模块
每当频道改变。然而，它仅在请求时向CPU提供数据。如果频道是以快速重复率运行时，其状态的变化可能比CPU所能请求的更快状态数据。在这种情况下，CPU可能会丢失一些状态值。
详细通道状态字的初始值为全零。详细频道状态字在以下情况下重置为零： FIP总线控制器通电或重启
CPU从停止转换到运行信道中止COMREQ中止信道
示例：检索命令块的详细通道状态此示例检索通道5的详细通道状态数据，并将其放置在
寄存器100-101。它将COMREQ状态字返回到%R10。本章描述FIP总线控制器对网络故障的正常记录。它解释了如何将网络故障信息存储在PLC的选定区域中以及如何禁止将某些网络故障记录到I/O故障表中。
网络故障的正常记录
网络诊断通信请求
启动网络诊断
停止网络诊断，正常记录网络故障
FIP总线控制器通常将两种类型的网络故障记录到I/O故障表中：
I/O总线故障
如果FIP总线控制器失去冗余网络中的一条总线，则I/O总线
记录的故障类型为“本地损耗总线1”或“本地损耗母线2”。
如果FIP总线控制器失去冗余网络中的两条总线，或失去其中一条
只有单工网络中的总线，I/O总线故障记录为“全部丢失”类型通信”。
如果远程I/O设备或通用设备失去冗余系统中的一条总线网络，记录“远程丢失总线1”或“远程”类型的I/O总线故障总线2的损耗”。在单工网络中，不记录I/O总线故障。（见损失/增加设备故障）。
B、 设备故障丢失/增加（网络存在）
FIP总线控制器还记录以下设备的丢失/添加（网络存在）故障：
配置远程I/O和通用设备。设备丢失/添加的日志记录无法禁用故障。
对于远程I/O设备，FIP总线控制器关闭后立即开始故障记录
操作的对于通用设备，在以下情况下有大约30秒的时间延迟
FIP总线控制器工作。
The Bus Controller refreshes this data in its own memory every time the status of the
channel changes. However, it supplies the data to the CPU only on request. If the channel is
operating with a fast repetition rate, its status may change faster than the CPU can request
the status data. In that case, some status values may be missed by the CPU.
The initial value of the Detailed Channel Status words is all zeros. The Detailed Channel
Status Words are reset to zero when:
The FIP Bus Controller is powered up or restarted
The CPU transitions from STOP to RUN
A channel abort COMREQ aborts the channel
Example Retrieve Detailed Channel Status Command Block
This example retrieves detailed channel status data for channel 5 and places it in
Registers 100-101. It returns the COMREQ Status word to %R10 This chapter describes normal logging of network faults by the FIP Bus Controller. It explains how network fault information can also be stored in a selected area of PLC
memory, and how to disable logging certain network faults into the I/O fault table.
Normal logging of network faults
Network Diagnostic COMREQ
Start Network Diagnostic
Stop Network Diagnostic Normal Logging of Network Faults
The FIP Bus Controller normally logs two types of network faults to the I/O fault table:
A. I/O Bus Faults
If the FIP Bus Controller loses one of the busses in a redundant network, an I/O Bus
Fault is logged of the type “Local Loss Bus 1” or “Local Loss bus 2”.
If the FIP Bus Controller loses both busses in a redundant network or it loses the one
and only bus in a simplex network, an I/O Bus Fault is logged of the type “Loss All
Comm”.
If a remote I/O device or generic device loses one of the busses in a redundant
network, an I/O Bus Fault is logged of the type “Remote Loss Buss 1” or “Remote
Loss Bus 2”. In a simplex network, I/O Bus Faults are not logged. (See Loss/Addition of
Device Faults).
B. Loss/Addition of Device Faults (Network Presence)
The FIP Bus Controller also logs loss/addition of device (network presence) faults for
configured remote I/O and generic devices. This logging of loss/addition of device
faults cannot be disabled.
For remote I/O devices, fault logging starts immediately after the FIP Bus Controller is
operational. For generic devices, there is a time delay of approximately 30 seconds after
the FIP Bus Controller is operational.
