Table of Contents
Advertisement
Programming Worksheets
Before programming the T-Link module, obtain the following items from the
Network Administrator:
1. The static IP address for the T-Link module. (Section [001])
2. The subnet mask for the T-Link module. (Section [002])
3. The static IP address of the receiver. (Section [003])
4. The static IP address of the static gateway for the LAN the T-Link is con-
nected to in a WAN configuration. (Section [004])
Remember This: If you are using a telephone line to back up communication,
be sure to program what phone number you want to use as a backup or dial
direction option in section [000401] 'Communication Toggle Options'. If using
a PC4020 or with a 5020 [380] option 5, enables 3rd number to backup. It is
recommended that T-Link communication be programmed to transmit first as
it is faster than land line communication. If the land line communication is
programmed to communicate first, then the T-Link communication will be
delayed for the duration of the land line call (about 30-45 seconds). The same
idea should apply when using the phone line for backup only.
4.1
Programming via the PC4020 control panel
NOTE:PC4020 Rev04B hardware required.
Programming steps:
Step 1: Program the Hex digits [CAAA] in the telephone number that will be
used for T-Link communications (section [0004000000] 'Communi-
cator + Main Items Phone Numbers').
NOTE: You must delete the [D] in the telephone number first (this is
the dial tone detection).
Step 2: Program YES for 'T-Link Enabled' option, section [000401] 'Communi-
cation Toggles'.
Step 3: If using DLS communication over T-Link then program YES for 'DLS
Enabled' in section [000300], 'DLS Section +DLS Toggles'.
Step 4: Program the dialer direction options for the phone number that has
been programmed to send T-Link communications in section
[000400XX02], where XX = telephone number 00-02 in the 'Commu-
nicator + Main Options'.
NOTE: Auto report SIA section [000401] must be enabled in order for
the T-Link to communicate. The communication format must be pro-
grammed for SIA [000400XX01].
Step 5: Enter section [000406] for T-Link module programming options.
Step 6: Program the static IP address for the T-Link module in section [001].
Step 7: Program the subnet mask for the T-Link module in section [002].
Step 8: Program the receiver static IP address (DRL-IP line card or the PC
running The Reporter IP software) in section [003].
Step 9: If the receiver (DRL-IP or The Reporter IP software) is on a different
network segment than the T-Link module, the gateway address asso-
ciated with the T-Link module must be programmed in section [004].
This is an optional step; please discuss with the network administra-
tor if this is required.
8
Section 4
T-Link Functionality & Troubleshooting
To simplify bench testing and increase diagnostic ability, it is often beneficial to
connect the T-Link and the receiver directly to each other, using an Ethernet
crossover cable (see Section 3.2 "Making an Ethernet Crossover Cable"). The
diagnostic information for use with a crossover cable is outlined in this sec-
tion.
Upon T-Link power-up (without the Ethernet cable connected), LED1 will blink
periodically, approximately once every 12 seconds. This represents the T-Link
attempting to send a TCP/IP socket connection request to the receiver. The T-
Link will try to connect to the receiver until it succeeds. At the same time,
LED2 will remain solid ON indicating that no packets are being received. If
both LEDs do not exhibit this behavior, the T-Link is NOT functioning properly.
3.1
Troubleshooting
If the receiver (either The Reporter IP or the DRL-IP) is properly config-
ured, within a few seconds of connecting the Ethernet cable LED2 will
blink once, after which both LED1 and LED2 will enter a steady ON
state. This represents a successful TCP/IP socket connection with the
receiver. At this point, The Reporter IP or the DRL-IP will be able to
report that the T-Link is connected. Any subsequent alarm messages or
other transmissions will result in both LED1 and LED2 blinking once
each, simultaneously, for each message sent. This behavior represents
the original message being sent/received and a response (i.e., an ACK)
being received/sent.
If LED1 continues to blink once every 12 seconds, and LED2 remains
on, this signifies that no communication can be established with the
receiver. In this case the receiver is not responding and accepting the
socket connection request from the T-Link. This can be caused by the
receiver not being powered, faulty cabling, or incorrect T-Link configu-
ration (incorrect T-Link IP address, subnet mask, gateway, or receiver IP
address).
If LED1 continues to blink once every 2 seconds, and LED2 also blinks
once every 2 seconds, more or less in unison, this represents a prob-
lem either with the receiver or the T-Link configuration. As an example,
if the T-Link is connected to a PC with The Reporter IP installed, but The
Reporter IP application is not running at that instant, this is the LED
behavior that will be seen (assuming all other configuration information
is correct). If The Reporter IP or DRL-IP is running, this could indicate
an improper port setting in either the T-Link or DRL-IP . It could also
indicate an improper receiver IP address, signifying that the address
entered into the T-Link is actually the address of another host on the
network.
Section 3
5
Advertisement
Table of Contents
