FS-8700-07 - BACnet ARCNET

Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-07 Bacnet Arcnet
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001

Instruction Manual Part Number FS -8700-07
7/9/2001

1. BACnet Description

The BACnet Arcnet driver allows the FieldServer to transfer data to and from devices using BACnet protocol over an Arcnet highway. The Arcnet card is included with the FieldServer. The FieldServer can emulate either a Server or Client.

The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.

2. Hardware/Software

Supplied by FieldServer Technologies

Provided by user

¹If FieldServer used as BACnet Client.

²If Fieldserver used as BACnet Server.

3. FieldServer as a BACnet Client

3.1 Hardware Connections

It is possible to connect a BACnet device to any of the eight RS232 ports or two RS485 ports. These ports just need to be configured for BACnet in the configuration file.

3.2 Configuration File Structure

Refer to section 4.1 of the Instruction Manual for a description of the operation principle of the FieldServer. The following tables describe parameters that need to be filled out in the configuration file. For convenience, a few example parameters already exist in the supplied PRIMSERV.CSV and SECDSERV.CSV files.

Note that * indicates an optional parameter, with the bold legal value being the default.

3.2.1 Data Arrays

Example

3.2.2   Client Side Connections

Example

3.2.3  Client Side Nodes

Example

3.2.4 Client Side Map Descriptors

Example

4. FieldServer as a BACnet Server

4.1 Hardware Connections

It is possible to connect a BACnet device to any of the eight RS232 ports or two RS485 ports. These ports just need to be configured for BACnet in the configuration file.

Configure the PLC according to manufacturer’s instructions

4.2 Configuration File Structure

Refer to section 4.1 of the Instruction Manual for a description of the operation principle of the FieldServer. The following tables describe parameters that need to be filled out in the configuration file. For convenience, a few example parameters already exist in the supplied PRIMSERV.CSV and SECDSERV.CSV files.

Note that * indicates an optional parameter, with the bold legal value being the default.

4.2.1 Data Arrays

Example

4.2.2  Server Side Connections

Example

4.2.3 Server Side Nodes

Note 1: This Node_ID needs to match the DIP settings on the Arcnet adapter board installed in the FieldServer. Factory DIP switch settings are for station 11, but can be changed as indicated in the Driver Reference section.

Example

4.2.4 Server Side Map Descriptors

Example

Note 2: Units

4.3 Driver Reference Section

4.3.1 Arcnet Adapter Card

4.3.2 Indicator Lights

There is a dual LED located at the PCX backplate. The yellow LED indicates that the PCX is being accessed via its I/O address. The green LED indicates that the PCX is receiving ARCNET traffic on the network.

4.3.3 Node ID Switch

An 8-bit DIP switch is used to set the ARCNET node address. Any value except zero is a valid ARCNET node address. The node ID switch SW1 is read right to left (when viewing the board installed in the FieldServer) with the MSB to the far right (position 1) and the LSB to the far left (position 8). A logic “1” occurs when the switch is moved away from the board (switch is opened). The figure below shows the node ID switch. In this example, the switch is set to the hexadecimal address 11 on the FieldServer (the factory default).

4.3.4 Arcnet cable

The cable to be used with the with the Arcnet card is a RG-62/u cable with BNC connectors. Cable length can be from 6 ft (2 m) between any two nodes or up to 1000ft (305 m) overall. Maximum nodes per segment are 8. It has a 5.5 dB/1000ft max..

4.3.5 Debugging a BACnet connection: Hints and tips

• Disconnect the FieldServer from the BACnet network when transferring BCU images to the BCU.
• Should duplicate object instances be accidentally configured in the FieldServer, then the second call of the instance will overwrite the first one. This may be the cause of a problem where a BACnet Object is being “lost.”
• If “Virtual_BCU_…” is not being indicated as the device description for the FieldServer on the BACnet SCADA system, then the FieldServer is not communicating to the SCADA system. If the present value’s name is being indicated, but the present value shows question marks, then it is most likely that the client side of the FieldServer is not communicating.
• If new points are added to the FieldServer it is important to restart Summit Workstation or BCU, otherwise these new points might not be seen by the FieldServer.
• Poll only the Modbus addresses that exist in the device when communicating with Liebert systems. Polling addresses that are not configured in these systems will cause the connection to fail. The newer versions of Lieberts do not suffer from this problem. Please contact your Lieberts supplier for more information.