12
Section 8: T-Link TL250/TL300 Operation
8.1
Remote Control
The panel and the DLS software will control this function. The module will be a conduit for the
information. Commands can be sent from the DLS or SA software to allow control of the panel;
Arm/Disarm, Bypass/Un-Bypass, Status Request.
NOTE: DLS2002 and DLS2002SA drivers are required for the PC1616/1832/1864, PC5020 v3.2 and PC4020
v3.31. DLS IV may be used with PC1616/1832/1864 v4.2 and higher only. These drivers can be downloaded
free from www.dsc.com. DLS2002 and DLS2002SA can communicate directly to the T-Link TL250 module.
The DLS software can be used with UL Listed installations only when service personnel are on-site.
8.2
Programming
The T-Link TL250/TL300 can be programmed remotely or locally with the T-Link Console Soft-
ware via the ethernet connection or locally with the T-Link console via the serial port. Program-
ming can also be done through the control panel when connected to a PC1616/1832/1864,
PC4020 or PC5020.
NOTE: TL250 programming cannot be done using DLS software
.
NOTE: On a default unit the T-Link can be reached from the console at IP 192.168.0.99 with a subnet mask
of 255.255.0.0 on port 3064.
8.3
IP Address
Each TL250/TL300 on the same network node must have a unique IP address. This system is
compatible with any device that masks the IP address of the originating device. Dynamic
addressing (DHCP) can also be used with the TL250.
For remote programming, the IP must be known by the T-Link console or the DLS/SA com-
puter(s). For this reason, DSC recommends a Static IP or setting up the DHCP server to always
license the same IP to the TL250/TL300 based on its MAC address.
8.4
Port Usage Table
NOTE: Confirm with the network administrator that the following ports are locked open and that the SG-
DRL3-IP has network access for all required network segments.
8.5
Integrated Call Directions
The T-Link TL250/TL300 features a built-in call direction that will allow signals to be sent to
active receivers as well as a local LAN logging application.
The T-Link TL250/TL300 has a choice of 3 receivers when transmitting signals. Receiver 1,
Receiver 2 and Receiver 3. Should the communications be lost to Receiver 1, the TL250/TL300
will generate a local trouble and send the trouble to the appropriate receiver. The loss of Receiver
2 or 3 does not generate any signal since they are not supervised.
The panel can direct to which receiver the signal will be sent. If a Receiver is lost, the TL250/300
will route the alarm to the backup receiver (if programmed). Receiver 3 will be used for local log-
ging. Any signal sent to Receiver 1 or Receiver 2 will also be sent to Receiver 3. Once the con-
nection has been reestablished to Receiver 1, the TL250/TL300 will resume transmission to it.
NOTE: If Receiver 1, 2 or 3 is not programmed, TL250/TL300 will not attempt to report to the receiver.
NOTE: Receiver 2 is not supported for DVACS installations.
NOTE:Transmissions to receiver 3 are not gaurenteed.
Description
Default
Port #
Protocol Programming Location to Change
T-Link TL250/
TL300
T-Link Source Port
3060
UDP
Section [009] T-Link options from Keypad
T-Link Destination
Port
3061
UDP
Section [010] T-Link options from Keypad
SG-DRL3-IP
T-Link Port
3061
UDP
Section [0B] [0C] from Console S/W
DLS Port
3062
TCP
Section [0D] [0E] from Console S/W
SA Port
3063
TCP
Section [11] [12] from Console S/W
Console S/W Port
3064
TCP
Section [14] [15] from Console S/W
DLS2002
DLS Port
3062
TCP
Modem Configuration Options
DLS SA
SA Port
3063
TCP
Modem Configuration Options
Console
Console Port
3064
TCP
T-Link Console
TFTP
Firmware Upgrade
69
TCP
Summary of Contents for T-LINK TL250
Page 43: ......
