Specifications

C E N T A U R U S P R I M E

1414

State: "AutoDiscovery" on Trunk: 1, VAV Device #5

State: "AutoDiscovery" on Trunk: 1, VAV Device #6

State: "AutoDiscovery" on Trunk: 1, VAV Device #7

When Auto Discover is invoked the Gateway will scan for all VAV device addresses

possible on the requested trunk.

As you can see in the example above, Trane-485 Device address #4 was discovered,

which was a VAV-1 type device.

This process should be completed for all trunks that have Trane-485 devices. When all

trunks have been Auto Discovered, you can then use the (S)ave Discovery option.

 Note 1: This is a lengthy process, taking 5-10 minutes per trunk on a 1200-

baud trunk (older VAV-1s; a bit quicker with the newer 9600-baud VariTrane

devices)

 Note 2: If a controller is dead, unplugged, or not communicating when

Auto-Discover is done, you can manually add the controller to the

discovered data file. You must download the data file to your PC, edit it

to add a line about the missing controller, and then upload the modified

file back into the Gateway. See “Uploading and Downloading files

to the Gateway”

 Files that are in the Gateway on drive C:, and their purpose, are:

STARTUP .BAT - Startup Batch file

GATEWAY.INI - Sets all baud rates, IP Address, BACnet parameters

SOCKET.CFG - IP Configuration file

SOCKETP .EXE - TCP/IP Socket stack

NE2000.COM - Ethernet Driver

TRN_GWAY.EXE - Does all the magic

DATABASE.DAT - Database that is created from Save Discovery

DISC_1 .TXT - Trunk #1 Auto Disc File

DISC_2 .TXT - Trunk #2 Auto Disc File

DISC_3 .TXT - Trunk #3 Auto Disc File

DISC_4 .TXT - Trunk #4 Auto Disc File

CONFIG .TXT - Device configuration file created when the

Auto-Discovery files are merged

XPING.EXE - Test program to verify Ethernet connectivity

(H)elp, (S)ummary, (D)evice, (P)oint, (C)ontrol, (W)atch, (A)utoDisc, (X)-it :A

AUT: (A)uto-Discovery, (S)ave Discovery, (X)-it :S