TC512V1分布式模塊
每當(dāng)頻道改變。然而，它僅在請(qǐng)求時(shí)向CPU提供數(shù)據(jù)。如果頻道是以快速重復(fù)率運(yùn)行時(shí)，其狀態(tài)的變化可能比CPU所能請(qǐng)求的更快狀態(tài)數(shù)據(jù)。在這種情況下，CPU可能會(huì)丟失一些狀態(tài)值。
詳細(xì)通道狀態(tài)字的初始值為全零。詳細(xì)頻道狀態(tài)字在以下情況下重置為零： FIP總線控制器通電或重啟
CPU從停止轉(zhuǎn)換到運(yùn)行信道中止COMREQ中止信道
示例：檢索命令塊的詳細(xì)通道狀態(tài)此示例檢索通道5的詳細(xì)通道狀態(tài)數(shù)據(jù)，并將其放置在
寄存器100-101。它將COMREQ狀態(tài)字返回到%R10。本章描述FIP總線控制器對(duì)網(wǎng)絡(luò)故障的正常記錄。它解釋了如何將網(wǎng)絡(luò)故障信息存儲(chǔ)在PLC的選定區(qū)域中以及如何禁止將某些網(wǎng)絡(luò)故障記錄到I/O故障表中。
網(wǎng)絡(luò)故障的正常記錄
網(wǎng)絡(luò)診斷通信請(qǐng)求
啟動(dòng)網(wǎng)絡(luò)診斷
停止網(wǎng)絡(luò)診斷，正常記錄網(wǎng)絡(luò)故障
FIP總線控制器通常將兩種類型的網(wǎng)絡(luò)故障記錄到I/O故障表中：
I/O總線故障
如果FIP總線控制器失去冗余網(wǎng)絡(luò)中的一條總線，則I/O總線
記錄的故障類型為“本地?fù)p耗總線1”或“本地?fù)p耗母線2”。
如果FIP總線控制器失去冗余網(wǎng)絡(luò)中的兩條總線，或失去其中一條
只有單工網(wǎng)絡(luò)中的總線，I/O總線故障記錄為“全部丟失”類型通信”。
如果遠(yuǎn)程I/O設(shè)備或通用設(shè)備失去冗余系統(tǒng)中的一條總線網(wǎng)絡(luò)，記錄“遠(yuǎn)程丟失總線1”或“遠(yuǎn)程”類型的I/O總線故障總線2的損耗”。在單工網(wǎng)絡(luò)中，不記錄I/O總線故障。（見(jiàn)損失/增加設(shè)備故障）。
B、 設(shè)備故障丟失/增加（網(wǎng)絡(luò)存在）
FIP總線控制器還記錄以下設(shè)備的丟失/添加（網(wǎng)絡(luò)存在）故障：
配置遠(yuǎn)程I/O和通用設(shè)備。設(shè)備丟失/添加的日志記錄無(wú)法禁用故障。
對(duì)于遠(yuǎn)程I/O設(shè)備，F(xiàn)IP總線控制器關(guān)閉后立即開(kāi)始故障記錄
操作的對(duì)于通用設(shè)備，在以下情況下有大約30秒的時(shí)間延遲
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.
