•
••
•
Auxiliary Drive to ISBus Interface Board IS200ADII GEI-100305
8
The LAN watchdog function is made up of three parts:
• First, the LAN Control Processor (LCP) monitors the ISBus controller’s fault
bits and displays an ADII fault, if the ISBus controller is in a fault state.
• Second, the LCP monitors it’s own communication with the ISBus controller
and if for any reason the ISBus controller is not communicating to LCP, then a
drive fault FLT.xxx ADIIRTM displays.
• If the LCP and the Drive Control Processor (DCP, on the LDCC board) fail to
communicate with each other, then a drive fault is triggered and displays.
The LAN heartbeat function can loop back a signal between the drive and any level
in the LAN hierarchy, such that a higher-level controller can validate the entire
connection pathway, including the drive .
A Programmable Logic
Controller (PLC) used as a
master controller can
generate a heartbeat to the
drive by inverting the
heartbeat from the drive and
sending that value back to the
drive.
The first bit in the drive’s feedback map is used as a heartbeat from the drive to the
master controller. The drive LCP always writes the heartbeat feedback to the same
state as the heartbeat reference. Thus, the master controller can monitor the status of
the communication with the drive by continually toggling the heartbeat to the drive
and monitoring the heartbeat from the drive.
The LCP sets AUXCMD0 if references are being received from the LAN and clears
AUXCMD0 if references are not being received from the LAN. The drive blockware
may be set up to monitor AUXCMD0 and cause a fault FLT.359 LINKLOSS if
AUXCMD0 is cleared.
LAN Faults
The following signals determine LAN health and declare faults:
• AUXCMD0 (master link presence)
• Heartbeat ref, LAN (Lan_Htbt_Ref)
• Heartbeat fbk, LAN (Lan_Htbt_Fbk)
The following faults are associated with the LAN interface: (See Table 6 for
descriptions.)
• FLT.359 LINKLOSS
• FLT.446 LADIINIT
• FLT.447LADIIWDG
• FLT.448 LADIIRTM
• FLT.449 LADIISEL