Tecom

Tecom Interface Reference
July 2019
Issue 5
DISCLAIMER
This document contains Honeywell proprietary information. Information
contained herein is to be used solely for the purpose submitted, and no part of
this document or its contents shall be reproduced, published, or disclosed to a
third party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for
a purpose and makes no express warranties except as may be stated in its
written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or
consequential damages. The information and specifications in this document
are subject to change without notice.
Copyright 2019 - Honeywell International Sàrl
2
Contents
CONTENTS
Contents 3
Chapter 1 - Getting started 5
Support and documentation for Tecom 5
Tecom Challenger panels supported 5
Other documentation for Tecom 6
Tecom-specific terms 6
Chapter 2 - Tecom controller setup 7
Connecting Tecom Challenger to the server 7
Cabling 7
Multi-dropping 7
Connecting and configuring Tecom 8
Setting up a Tecom Challenger 8
Communications settings 8
Chapter 3 - Tecom Controller configuration and addressing 11
Defining a Tecom channel 11
Tecom channel Main tab properties 11
Tecom Port tab properties 13
Defining a Tecom controller 16
Tecom controller Main tab properties 16
Defining a Tecom address for a point parameter value 17
Entering an address 18
Using the Address Builder to enter an address 18
Address syntax 18
Tecom Challenger addressing 19
Address codes represented in the server 20
Optimizing scanning performance 21
3
Contents
Exception reporting 21
Periodic scanning 21
Controlling a latched input 22
Controlling outputs 22
Chapter 4 - Server tasks for Tecom 23

Testing communications with the server 23
Troubleshooting Tecom scanning errors 24
Notices 25
4
CHAPTER
1 GETTING STARTED
This reference describes how to set up, configure, and test Tecom Security
Panels (controllers) communications with the EBI server. There is detailed
information for defining the controller using Quick Builder.
Complete each step before commencing the next.
Task Go to:
Set the communication parameters "Communications settings" on page 8
Connect the cables from the server to "Cabling" on page 7

the Tecom controller
Define channels with Quick Builder "Defining a Tecom channel" on page 11
Define controllers with Quick Builder "Defining a Tecom controller" on page 16
Download channel and controller

definitions to the server
Test communications "Testing communications with the server"

on page 23
Troubleshoot communication errors "Troubleshooting Tecom scanning errors"

on page 24
Define points with Quick Builder "Defining a Tecom address for a point
parameter value" on page 17
Support and documentation for Tecom

This section describes the security panel versions that are supported, as well
as documentation resources.
Tecom Challenger panels supported

The server supports the following Tecom Challenger Security panels:
n Version 8 panels with version 8 Firmware—up to version 8.67

n Version 6 panels with version 7 Firmware
5
Chapter 1 - Getting started
Other documentation for Tecom

Read the following documents before using or installing the server Tecom
Challenger interface:
n Challenger Version 8 Programming and Hardware Installation Guide

n Installation Guide for your server
Tecom-specific terms
Access
The condition of an location or building when it is occupied and when the

security system has been set so that normal activity does not set off an alarm.
Armed
The condition of an input, location or building when a change in the status of

any input (from sealed to unsealed) will cause an alarm.
Isolated
The input device has been inhibited from indicating sealed or unsealed status.
It is excluded from functioning as part of the system.
Sealed
The state of an input device when it is NOT activated, such as door closed.
Secure
The condition of an location or building when it is armed (security turned on)

and unoccupied.
Shunt
A procedure which inhibits an input from being activated when it is in an

unsealed condition. For example, shunt prevents a door generating an alarm
when opened for a short time.
Tamper
A situation where an arming Station or associated wiring is tampered with or

accidentally damaged.
Unsealed
The state of an input device when it is activated, such as door open.
6
CHAPTER
2 TECOM CONTROLLER SETUP

This section describes how to set up a Tecom controller for the system.
Connecting Tecom Challenger to the server

The Tecom Challenger system has a hardware capacity of:
n 256 inputs
n 255 relays
n 16 locations
n 16 arming stations
n 16 data gathering panels (including the Tecom Challenger panel)
An arming station is a device connected to the Tecom Challenger LAN that is
the user's control panel for security functions for locations or for access points
(doors).
A data gathering panel is a device connected to the Tecom Challenger LAN
that collects data from other security devices and transfers it to the main
Tecom Challenger control panel.
The server is connected to the Tecom Challenger using an RS-232 serial link.
Serial ports on the Tecom Challenger are connected with direct serial links to
serial ports on the server host, or with an Ethernet connection by using a
terminal server. The Tecom Challenger has an RS-232 communications port
on the serial computer and a printer port on the printer interface board.
Cabling
Communications between the server and the Tecom Challenger is achieved
using a non-standard RS-232 cable. For information on non-standard cabling
for Tecom, refer to the Installation Guide for the server.
Multi-dropping
The Tecom Challenger interface supports multi-dropping of Tecom
Challengers from the single communications line. The addressing range for
multi-dropping is 1–1023. Depending on communications line traffic, the
practical limit is usually 2 or 3.
7
Chapter 2 - Tecom controller setup
Connecting and configuring Tecom

The first stage in configuring the server Tecom Challenger interface is to
establish communications to the Tecom Challenger.
To connect and configure Tecom:

1. Set up the Tecom Challenger.
2. Configure the communications.
3. Connect cables.
4. Use Quick Builder to define channels and controllers and download to the
server.
5. Test communications.
Setting up a Tecom Challenger

TecomMulti-dropping requires each Tecom Challenger controller on the
same channel to have a unique computer ID. The ID is set through a RAS
keypad with LCD display or through the Challenger TS9000 Management
Software. You must assign this in the panel before the server can
communicate with it. The ID may vary between 1–1023 and must be unique on
a communications channel.
You must also assign a ten-digit password.
TIP: For details on programming the Tecom using the Tecom Systems
TS9000 Management Software, refer to the Challenger Version 8
Programming and Hardware Installation Guide.
To set up the Tecom Challenger:

1. Set the Challenger ID.
2. Set the ten-digit password.
TIP: All Tecoms that are on the same channel must have the same
password.
3. Connect the Tecom Challenger to the serial port.
Communications settings
The Tecom Challenger panels communicate at:
8
n 4800 baud
n 8 data bits
n 1 stop bit
n No parity
9
10
CHAPTER
3 TECOM CONTROLLER
CONFIGURATION AND
ADDRESSING
This section describes how to configure a Tecom controller using Quick
Builder.
Defining a Tecom channel

You need to define a channel for the LAN connection the server uses to
communicate with the Tecom controllers.
To define a channel using Quick Builder:

1. Click to add a channel.
2. In the Add Items dialog box, select Channel as the item and Tecom as the
channel type.
3. Enter the channel details on the Main property page for the channel.
4. To complete the channel definition, click the Port tab and define a port.
Tecom channel Main tab properties

Use the Main tab to enter the basic channel properties for a Tecom channel.
Property Description
Name The unique name of the channel. A maximum of 10 alphanumeric

characters (no spaces or double quotes).
Description (Optional) A description of the channel. A maximum of 30

characters can be used, including spaces.
Password The password must be set to the ten-digit password set in the
Tecom Challenger. This must be the same for all Tecom Challengers
connected to the channel.
Marginal The communications alarm marginal limit at which the channel is

Alarm Limit declared to be marginal. When this limit is reached, a high priority
alarm is generated. A channel barometer monitors the total number
11
Chapter 3 - Tecom Controller configuration and addressing
of requests and the number of times the controller did not respond
or response was incorrect. The barometer increments by 2 or more,
depending on the error and decrements for each good call.
To calculate an acceptable limit, multiply the square root of the

number of controllers on the channel by the Marginal Alarm Limit
defined for those controllers. (Normally, you specify the same value
for all controllers on a channel). For example, if there are 9
controllers on the channel and their Marginal Alarm Limit is set to 25,
the value would be [ 3 is square root ] x 25= 75.
Fail Alarm The communications alarm fail limit at which the channel is
Limit declared to have failed. When this barometer limit is reached, an
urgent alarm is generated.
Set this to double the value specified for the channel Marginal Alarm
Limit.
Response Enter the maximum amount of time, in seconds, that the server will
Time wait, after issuing a control, for a response from the controller if you
do not want the default, 10. If there is no response within the
specified time, the server raises an alarm. For example, an OP Fail
alarm would be raised on a point when an OP is being controlled
and there is no response within the specified time.
Exception If exception scanning has been configured, enter the amount of

Scan Rate time, in seconds, the server will automatically scan the device if you
do not want the default, 2.
Diagnostic Enter the amount of time, in seconds, the server will automatically
Scan Rate initiate a scan of the controller to verify communications integrity
with the controller if you do not want the default, 60.
One hardware diagnostic scan is automatically created per scan

packet.
Connect Amount of time (in seconds) the server waits to connect to the
Timeout controller before abandoning the connection. Type a new value in
this field if you do not want the default, 10 seconds.
Use the default value unless the communications line has a high
error rate.
Read Timeout Amount of time (in seconds) that the server waits for a reply from
the controller. Type a new value in this field if you do not want the
12
default, 2 seconds.
Use the default value unless the communications line has a high
error rate or unless you are using modems.
Item Type Shows the type of item specified when this item was created.
Last Modified Shows the date of the most recent modification to this channel's
property details.
Last This shows the date that the item was last downloaded to the server.
Downloaded
Item Number This field displays the unique item number currently assigned to this
item by Quick Builder. You can change the item number displayed
in this field if you need to match your current server database
configuration. The item number must be between 1 and the
maximum number of channels allowed for your system.
Tecom Port tab properties

The Port tab defines the communication-related properties for a channel. The
Port Type for Tecom can be:
n Serial. A serial communications interface, such as RS-232.
n TerminalServer . A communications link that enables controllers with a

serial interface to be connected to a LAN.
n LANVendor . Not applicable to Tecom.
Serial port properties

The communications port is the computer port to which the Tecom Challenger
is connected. It may be COM1, COM2, or a serial communications board port.
The serial port settings must match the settings on your communication
devices.
Serial Port The device name of the serial port.

Name
13
Baud Rate The number of data bits per second. The default is 4800.
Number of The number of data bits used for transmission. The default is 8.
Data Bits
Stop Bits The number of stop bits used for transmission. The default is 1.
Parity The parity verification used on the port. The default is NONE.
Checksum The type of checksum error detection used for the port. Select the
value that matches the setting on the communication device:
l NONE (default)
l CRC16_0 or CRC16_1 (if Cyclic Redundancy Check (CRC) is set)
l ONESCOMP or TWOSCOMP (if Longitudinal Redundancy Check

(LRC) is set)
l XOR (If exclusive or is set)
XON/XOFF The type of XON/XOFF software flow control used to stop a receiver
from being overrun with messages from a sender. The types are:
l None (default)
l Input (use XON/XOFF to control the flow of data on the receive

line)
l Output (use XON/XOFF to control the flow of data on the
transmit line)
Handshaking For RS-232

Options
l Enable RTS/CTS flow control. Stops a receiver from being overrun
with messages from a sender by using RTS/CTS flow control.
l Detect DCD. Select if the Data Carrier Detect communication
status line of the COM port requires monitoring (usually when
using modem or microwave linking). When selected, the
communications fails if the desired COM status line is not high—
for example, on a dial-up link connection for a modem.
l Detect DSR. Select if the Data Set Ready communication status
line of the COM port requires monitoring (usually when using
modem or microwave linking). When selected, the
communications fails if the desired COM status is not achieved.
14
NOTE: No options available for RS-422.
For RS-485
l Enable Stallion RS-485 Half Duplex. Select if RS-232 to RS-485 is

done using a Stallion EasyConnection adapter.
l Echo (Required for RS-485 2-wire ports) . Select so that the server
expects the messages it sends to the port on the transmit line to
be echoed back on the receive line. Select for a Stallion
EasyConnection adapter or a Black Box converter.
TerminalServer port properties
Terminal The name and port number of terminal server to which the channel is
Server TCP connected.
Host Name
You can specify either a TCP host name or an IP address, but it must
Terminal match the TCP host name used when you installed and internally
Server TCP configured the terminal server.
Port No
Idle Timeout The time, in seconds, the channel waits for a successful connection to
the server before closing the connection.
A value of 0 indicates that the connection is never closed.
Checksum The type of checksum error detection used for the port. Select the
value that matches the setting on the communication device:
l CRC16_0 or CRC16_1 (if Cyclic Redundancy Check (CRC) is set)

l ONESCOMP or TWOSCOMP (if Longitudinal Redundancy Check
(LRC) is set)
l XOR (If exclusive or is set)
15
LANVendor port properties
Port Name Not applicable to Tecom
Defining a Tecom controller

You need to define a controller to describe each PLC on a channel.
To define a controller using Quick Builder:

1. Click to add a controller.
2. In the Add Items dialog box, select Controller as the item and Tecom as
the controller type.
3. Enter the property definitions for the controller on the controller Main
property page.
Tecom controller Main tab properties

Use the Main tab to define the basic properties for a Tecom controller.
Name The unique name for the controller. A maximum of 10 alphanumeric

characters. (Double quotation marks and spaces are not allowed.)
For LAN connected controllers, the name must not contain

underscore ( _ ) characters. This name is used to look up the IP
address in the TCP/IP database if you do not specify an IP Address
property.
Description (Optional) A description for this controller. A maximum of 30

characters, including spaces, can be entered.
Channel The name of the channel on which the controller communicates. In

Name the list of channel names, click the name. You need to have defined
the channel in order for it's name to appear in the list.
Marginal The communications alarm marginal limit at which the controller is

Alarm Limit declared to be marginal. When this value is reached, a high priority
alarm is generated. This limit applies to the controller barometer
which monitors the total number of requests to the controller and
16
the number of times the controller did not respond or response was
incorrect. The barometer increments by 2 or more, depending on
the error and decrements for each good call.
Type a new value in this field if you do not want the default, 25.
Fail Alarm The communications alarm fail limit at which the controller is
Limit declared to have failed. When this value is reached, an urgent alarm
is generated.
Set this to double the value specified for the controller Marginal
Alarm Limit.
Controller The type of Tecom controller:

Type
l Tecom V8
l Tecom V10
Alarm Check this box to force the server to send a reset to the Tecom
Controller Challenger when an alarm is acknowledged.
Reset
Controller ID Controller ID must match the computer ID of the Tecom Challenger.
Item Type Shows the type of item specified when this item was created.
Last Modified Shows the date of the most recent modification to this channel's
property details.
Last This shows the date that the item was last downloaded to the server.
Downloaded
Item Number This field displays the unique item number currently assigned to this
item by Quick Builder. You can change the item number displayed
in this field if you need to match your current server database
configuration. The number must be between 1 and the maximum
number of controllers allowed for your system.
Defining a Tecom address for a point parameter

value
This section describes how to enter a point parameter value and address
syntax.
17
Entering an address
Valid options for source are: PV, OP, MD, SP.
Valid options for destination are: MD, OP, SP.
For source, and destination addresses the format for a Tecom controller
address is:
ControllerName Address
Part Description
ControllerName The name of the Tecom controller.
Address The address in the controller where the value is recorded.
If you would like help when defining an address, click next to Address to
display Address Builder.
Using the Address Builder to enter an address

To specify a Tecom controller address, enter the following property values:
Address Type Select Controller.
Controller Select the Tecom controller. You need to have defined the controller
for the name to appear in this list.
Address The address in the controller where the value is recorded.
Address syntax
The address syntax takes the following format:
AddressCodeAddressNumber [AreaNumber]
Part Description
AddressCode Specifies the point code for the specific type of Tecom
Challenger point.
AddressNumber The address of the point within the Tecom Challenger. Point
addresses vary according to point type.
AreaNumber Only required when defining timer points that require two
18
Part Description
addresses. For timer points, the AddressNumber specifies the

timer number and AreaNumber specifies the location number.
Tecom Challenger addressing

Addresses within the Tecom Challenger are monitored and controlled from
the server using status points. There are several Tecom Challenger status
point parameters. Addressing depends on the hardware available and the
configuration of the hardware. See the Challenger version 8 Programming
and Hardware Installation Guide for details.
Input (PV)
Each Tecom Challenger provides a number of inputs. An input is an electrical
signal from an intrusion detection device. Typical devices that are monitored
by these inputs include: microswitches, magnetic reed switches, break glass
switches, passive infrared detectors (PIRs), duress buttons, and many other
security devices.
An input status point measures the physical status of the measuring device,
such as high voltage and short circuit. A Latched Input point measures the
alarm state of the point. In general, the server points are only be built to
reference latched input points.
Output (OP)
The panels also have the capability of providing relay outputs. Typical uses of
these relay outputs include controlling electronic door bolts and activating
closed circuit TV cameras.
Timer
There are eight Timer points per location. You can configure Timer number 8
to be a counter, that counts the number of people who enter the location. See
the Challenger version 8 Programming and Hardware Installation Guide for
information on how to configure counters.
A location is a section of a building with specific security requirements. Each
location has two modes:
19
n Armed (the usual working mode of the location during silent (nonworking)
hours)
n Disarmed (the usual mode of the location during working hours)
Alarm states of a location correspond to the activation of the security device in

the location. For example, if a person walks through a PIR beam after hours,
an alarm will be generated.
Address codes represented in the server

The table below specifies the address codes represented in the server.
Point Category Address Code Address Range
Input Status IS 1 to 256
Latched Input IP 1 to 256
Relay Output OP 1 to 255
Area Alarms Active ARAA 1 to 16
Area Unsealed Inputs ARUI 1 to 16
Area Isolated Inputs ARII 1 to 16
Area Exit Time AREX 1 to 16
Area Entry Time AREN 1 to 16
Area Local Alarms ARLA 1 to 16
Area Console Warning ARCW 1 to 16
Area Armed ARAR 1 to 16
RAS RAS 1 to 16
DGP* DGP 1 to 16
DGP Battery* BATT 1 to 16
DGP Battery Test* BTEST 1 to 16
DGP Main* MAIN 1 to 16
DGP Fuse* FUSE 1 to 16
20
Point Category Address Code Address Range
DGP Siren* SIREN 1 to 16
Duress DUR 1 to 16
Timer TIMER 1 to 8 (Timer), 1 to 16

(Location)
* Addresses 1 - 15 are for the DGP's attached to the main controller board, address
16 is for the main controller.
Optimizing scanning performance

The maximum amount of data that can be acquired from an controller is
influenced by the rate of sending scan packets to the controller. An
understanding of the Tecom scan packets will help you configure points so
that optimal data acquisition performance can be achieved by maximizing the
amount of data acquired with each scan packet.
The scan packets that have been built can be listed by using the utility
lisscn (list scan). Listing scan packets helps verify the scanning strategy.
See the Configuration Guide for your server for usage of lisscn.
Exception reporting
The server acquires point values from the Tecom Challenger by exception
reporting. Every exception scan period, the server sends a change‐of‐state
poll to each Tecom Challenger. The Tecom Challenger replies with a list of
any points that have changed state, any events that have occurred, or with a
null response (if there has been neither). The server updates any points that
have changed state.
ATTENTION: IS or TIMER type points and values are not reported by

exception. You must configure these for periodic scanning if updates
are required.
Periodic scanning
The change-of-state poll is automatically scheduled by the server for any
Tecom Challenger controller in service.
21
A point that addresses a Tecom Challenger can also have a period poll
configured. This poll enables the server to request the state of the point. You
specify periodic scanning by defining the point PV Scan Period. The scan
period defined is usually 900 seconds, however, points configured for IS or
TIMER require a faster scan period in accordance with their rate of change.
Controlling a latched input

To control a latched input, RAS or DGP to the isolate state, the status point
must be taken off scan by using the Scanning Enabled check box for the
particular status point. The point goes off scan in the server and be controlled
to isolated in the Tecom Challenger controller. If the input, RAS or DGP is de-
isolated in the field, an exception scan will read and process the de-isolate
change of state event. This will bring the status point back on scan within the
server, showing the point's current status.
ATTENTION: The Challenger panel itself is built as DGP 16, but it

cannot be isolated and de-isolated.
Controlling outputs
The only points that allow for output control are relay outputs, points with
location arming and the DGP battery test points (these points start the battery
test).
22
CHAPTER
4 SERVER TASKS FOR TECOM
This section describes tasks for the Tecom controller that you perform on the
server computer.
Testing communications with the server

Use the Tecom test utility, tcmtst, to test communications between the
server and the controller after you have downloaded your channel and
controller definitions to the server database.
Prerequisites
n Set up controllers.
n Connect all cables.
n Enter definitions for controller and channel in Quick Builder project file.
n Download project file definitions to server without errors.
ATTENTION: The server should not be running while using the utility
To run the test utility

1. Open a Command Prompt window and type tcmtst and press
ENTER.
2. Follow the directions as prompted.
You can read the status of arming Stations and DGPs connected to the
Challenger. Note that the 'construct command' option requires knowledge
of the communications protocol, and should only be used by Honeywell
Software Centre staff.
If any errors are encountered, review your channel and controller
definitions.
After verifying that the server is communicating with the Tecom Challenger,
you can build points that reference Tecom Challenger addresses.
23
Chapter 4 - Server tasks for Tecom
Troubleshooting Tecom scanning errors

If the Point Detail display for a point shows a bad value (indicated by inverse
video), the point might built with an address that is syntactically valid but not
configured in the controller.
The controller responds to a request to read this address with an NAK
message. Note that NAK messages received in response to a read request
by the server do not contribute to the error count of the controller or channel.
NAK messages received in response to a write request by the server result in
an operator message being sent to the Station as well as contributing to the
controller's error count.
Any NAK messages received are printed in the server error log (which can be
viewed via the Server Diagnostics Program Group).
If NAK messages occur, check the relevant point address to ensure there are
no references to addresses in the controller that are not actually configured
within the controller.
24
Notices
NOTICES
Honeywell Trademarks
IdentiPoint® is a U.S. registered trademark of Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
BACnet® is a registered trademark of the American Society of Heating,
Refrigerating and Air-Conditioning Engineers.
Other brands or trademarks are trademarks of their respective owners.
Trademarks that appear in this document are used only to the benefit of the
trademark owner, with no intention of trademark infringement.
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software
defect or weakness that can be exploited to reduce the operational or security
capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting
Honeywell products and services.
To report a potential security vulnerability against any Honeywell product,
please follow the instructions at:
https://www.honeywell.com/en-us/product-security.
Support
For technical assistance, contact your nearest Honeywell office.
Training classes
Honeywell holds technical training classes on Enterprise Buildings Integrator.
These classes are taught by experts in the field of building control systems.
For more information about these classes, contact your Honeywell
representative.
25
Notices
26

Tecom

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tecom

Uploaded by

Copyright:

Available Formats

Tecom Interface Reference

Chapter 4 - Server tasks for Tecom 23

Set the communication parameters "Communications settings" on page 8

Connect the cables from the server to "Cabling" on page 7

Define channels with Quick Builder "Defining a Tecom channel" on page 11

Define controllers with Quick Builder "Defining a Tecom controller" on page 16

Download channel and controller

Test communications "Testing communications with the server"

Troubleshoot communication errors "Troubleshooting Tecom scanning errors"

Support and documentation for Tecom

Tecom Challenger panels supported

n Version 8 panels with version 8 Firmware—up to version 8.67

Other documentation for Tecom

n Challenger Version 8 Programming and Hardware Installation Guide

The condition of an location or building when it is occupied and when the

The condition of an input, location or building when a change in the status of

The condition of an location or building when it is armed (security turned on)

A procedure which inhibits an input from being activated when it is in an

A situation where an arming Station or associated wiring is tampered with or

The state of an input device when it is activated, such as door open.

2 TECOM CONTROLLER SETUP

Connecting Tecom Challenger to the server

Connecting and configuring Tecom

To connect and configure Tecom:

Setting up a Tecom Challenger

To set up the Tecom Challenger:

3. Connect the Tecom Challenger to the serial port.

Defining a Tecom channel

To define a channel using Quick Builder:

Tecom channel Main tab properties

Name The unique name of the channel. A maximum of 10 alphanumeric

Description (Optional) A description of the channel. A maximum of 30

Marginal The communications alarm marginal limit at which the channel is

To calculate an acceptable limit, multiply the square root of the

Exception If exception scanning has been configured, enter the amount of

One hardware diagnostic scan is automatically created per scan

Tecom Port tab properties

n Serial. A serial communications interface, such as RS-232.

n TerminalServer . A communications link that enables controllers with a

Serial port properties

Serial Port The device name of the serial port.

l CRC16_0 or CRC16_1 (if Cyclic Redundancy Check (CRC) is set)

l ONESCOMP or TWOSCOMP (if Longitudinal Redundancy Check

l Input (use XON/XOFF to control the flow of data on the receive

Handshaking For RS-232

NOTE: No options available for RS-422.

l Enable Stallion RS-485 Half Duplex. Select if RS-232 to RS-485 is

TerminalServer port properties

A value of 0 indicates that the connection is never closed.

l CRC16_0 or CRC16_1 (if Cyclic Redundancy Check (CRC) is set)

LANVendor port properties

Port Name Not applicable to Tecom

Defining a Tecom controller

To define a controller using Quick Builder:

Tecom controller Main tab properties

Name The unique name for the controller. A maximum of 10 alphanumeric

For LAN connected controllers, the name must not contain

Description (Optional) A description for this controller. A maximum of 30

Channel The name of the channel on which the controller communicates. In

Marginal The communications alarm marginal limit at which the controller is

Controller The type of Tecom controller:

Controller ID Controller ID must match the computer ID of the Tecom Challenger.

Defining a Tecom address for a point parameter