Testing and Troubleshooting
Status Indicators
Page 8-4 MDE-3664B TRIND® Start-up, Service, and Parts Manual · June 2013
Figure 8-4: Q13563-04 DCB Indicators
Heart Beat (CPU)
RS-485 (TX)
Read Ant 1 (Overhead)
Read Ant 3 (Overhead)
Bezel I/O Error
RS-485 (RX)
+12 VDC
Vcc (+5 VDC)
J8 Bezel B
J7 Bezel A
The Q13563 DCB will have the following indicator characteristics when operating properly:
• VCC and +12 VDC LEDs on solid (D14 and D13, respectively).
• Heartbeat LED (CPU) blinking (D9).
• RS-485 LED’s strobbing rapidly (D2 and D3).
Note: One may watch the communications begin between the Gateway Board and the DCB
with these LEDs. The first several sequences are the waking up of the DCB and then
commands sent down. This LED activity looks spurious. After a few rounds of that
behavior, the RS-485 LEDs will begin firing at a regular pace, indicating that a link has
been established. The RS-485 LEDs fire at a regular pace only when the Gateway
Board is looking for tags. When the CRIND does not want the Gateway to look for tags
(or has never initiated communication with the Gateway), the RS-485 LEDs fire once
every 10 seconds after any initial wakeup.
• When a car tag has been presented, the READ ANT 1 (D8) or READ ANT 3 (D7) LED
will light, depending upon the side.
• If the Bezel Input Output (I/O) error LED (D6) is on, then one of the Light/Micro Reader
Boards is not connected or has lost communication.