EasyIO FG BACnet User Guide Version 2 · Points The BACnet driver easyioFGBACnet is dependent on...

FG Series BACnet v2.2

1

EasyIO FG BACnet User Guide Version 2.0


2

Document Change Log

13thMarch 2014 Document created. Only support BACnet IP Server for EasyIO FG Series

30thJune 2014 Major changes in Bacnet protocol implementation.

07thJuly 2014 Bacnet Server and Bacnet Client merge into 1 single kit. 07th March 2015 Limitation for Bacnet Server and Client edited.

08th July 2015 Added diagram for BACnet client.


3

Disclaimer EasyIO FG-32 and EasyIO FG-20 are products by EasyIO Holdings Pte Ltd

The EasyIO FG Series contains the Sedona Framework ®.

Sedona Framework is a trademark of Tridium, Inc.


4

Table of Contents Introduction ................................................................................................................................................................... 5

Prerequisites .................................................................................................................................................................. 5

Device Software Configuration Limitations – BACnet Server ........................................................................................ 6

Device Software Configuration Limitations – BACnet Client ......................................................................................... 6

Configuring the BACnet Server Network ....................................................................................................................... 8

Configuring the BACnet Client Network ...................................................................................................................... 13

Technical Support ........................................................................................................................................................ 20


5

Introduction The EasyIO FG Series is able to operate as a BACnet device and BACnet Client. It is capable of handling the below BACnet protocols;

1. BACnet IP server 2. BACnet MSTP server 3. BACnet IP Client 4. BACnet MS/TP Client

The minimum firmware requirement for the BACnet protocol to run properly is v1.4b33 or later.

Prerequisites 1. CPT Tool dated 27th June 2014 or later. 2. The EasyIO FG Series Sedona Controller. Please note EASY IO FG Series firmware version v1.5b44 or later

(EasyIO FG) and v2.0b44 or later for (EasyIO FG+) is required for best performance. 3. A Micro SD memory card with a memory capacity of 1GB to 16GB. Contact EasyIO support at [email protected] if you need assistance.

mailto:[email protected]


6

Device Software Configuration Limitations – BACnet Server

Objects supported Analog Value , Read Only or Read Write Binary Value , Read Only or Read Write

Priority Array Supported Emergency Override @ 1 Priority 2 @ 2 Priority 3 @ 3 Priority 4 @ 4 Priority 5 @ 5 Priority 6 @ 6 Priority 7 @ 7 Operator Override @ 8 Priority 9 @ 9 Priority 10 @ 10 Priority 11 @ 11 Priority 12 @ 12 Priority 13 @ 13 Priority 14 @ 14 Priority 15 @ 15 Priority 16 @ 16 Relinquish Default Out of Service

Total Analog Value (AV) 128 Total Binary Value (BV) 128

Objects supported (only available in FG+) Analog Schedule Binary Schedule

Priority Array Supported Present Value Total Analog Schedule 16 Total Binary Schedule 16

Objects supported (only available in FG+) Calendar Schedule

Priority Array Supported Present Value Total Calendar 8

Device Software Configuration Limitations – BACnet Client

Total Server devices allowed 20 devices , combination of both IP and MS/TP

Objects supported Analog Input , AI Analog Output , AO Analog Value , AV Binary Input , BI Binary Output , BO Binary Value , BV Multi State Input , MSI Multi State Output , MS0


7

Multi State Value , MSV Total objects allowed per device 15 objects (Combination of above supported object

types)


8

Configuring the BACnet Server Network

The architecture of the driver is deployed as shown below in Step 2. The network object can be dropped anywhere in the Sedona app tree. Our recommendation is to create a separate folder for each network, identified as you require. Bacnet Service

Bacnet Server Network (Both IP and MSTP)

Points (BACnet AVs and BVs) The Bacnet driver kit “easyioFGBACnet is dependent on the installation of the “easyioFGDriver”. Both kits need to be installed to enable configuration of the Bacnet network in an FG Series device. Step 1 Connect to the controller with Sedona Workbench or CPT Tool.

Default login credentials are as below;

IP address : 192.168.10.11 Username : admin Password :<no password> Manage kits to install easyioFGBACnet and easyioFGDriver into your controller. EasyIO FG series controller with firmware V2.2.2.0.05 and above, the easyioFGDriver kit is preinstalled.

Step 2 Choose easyioFGBACnet from kit library.

Drag & drop the BACService into your App. The object can be dropped in the EasyIO folder or a new folder can be

created for the Service Object.

In the example below, the object is dropped into a new folder named “BACnet”.


9

Step 3 Click at the service object to access the property at the property side bar. Configuration of the BACnet communication parameters such MSTP MAC address is carried out here. Select BACnet communication stack to be enabled. By default both IP stack and MSTP stack is disable.

If the communications stack if configured correctly, the status will display as OK.


10

Step 4 From the easyioFGBACnet drag & drop the BACnetServerNetwork into your App. The object is recommended to be drop under the BACnet service object.

The BACnet server and BACnet client object can be coexist under the BACnet service object. There can only be one (1) BACnet service object in a controller. Duplication of BACnet Service object is allowed. Step 5 Click at the Server Network object to access the property at the property side bar. Enable the Server Network. Once the network is enable, the IP service and MSTP service should display OK if both are enable at the BACnet Service object. These statuses are reflected by the BACnet Service object configurations.

Step 6 Drop BACServerBv or BACServerAv type object under the Network Object.


11

Note that the register object must be a child of (dropped below) the Network object. It is possible to create folders below the Network Object to allow logical management of the register objects.

Step 7 By default all registers are set to the disabled mode Enable = false). You will need to enable each register object in the application in order for the register to be discovered by other systems i.e. the BACnet Client.

By default the register are named according to the type followed by the address number. You can enter a preferred name for the object by right click at the object and select action “selObjectName” or manually key in a the property side bar.


12

Maximum character allowed is 63.

A maximum of 64 Analog Values and 64 Binary Values are available. Priority Array supported for these objects are; Emergency Override @ 1 Priority 2 @ 2 Priority 3 @ 3 Priority 4 @ 4 Priority 5 @ 5 Priority 6 @ 6 Priority 7 @ 7 Operator Override @ 8 Priority 9 @ 9 Priority 10 @ 10 Priority 11 @ 11 Priority 12 @ 12 Priority 13 @ 13 Priority 14 @ 14 Priority 15 @ 15 Priority 16 @ 16 Relinquish Default Out of Service Step 8 Use any BACnet Client to discover the device and objects.


13

Configuring the BACnet Client Network

The architecture of the driver is deployed as shown below in Step 2. The network object can be dropped anywhere in the Sedona app tree. Our recommendation is to create a separate folder for each network, identified as you require. Service

Bacnet Client Network (Both IP and MSTP)

Device

Points The BACnet driver easyioFGBACnet is dependent on the installation of the easyioFGDriver. These kit need to be installed to enable configuration of the BACnet client network in a FG Series device. Diagram below shows an EasyIO FG as BACnet IP client.

Diagram below shows an EasyIO FG as BACnet MS/TP client.


14

Step 1 Connect to the controller with Sedona Workbench or CPT Tool. Default login credentials are as below; IP address : 192.168.10.11 Username : admin Password :<no password> Navigate to the Kit Management window in CPT Tool and install the easyioFGBACnet and easyioFGDriver kit into your controller. If the controller firmware is V2.2.2.0.07 or later easyioDriver kit is preinstalled.

Step 2 The EasyIO FG controller comes with a bacnet device discovery option. This option will only work if CPT Tool is used. CPT Tool dated 27th June 2014 or later is a must. Firmware installed in the EasyIO FG Series controller has to be v1.4b33 and above. Step 3 Choose easyioFGBACnet from kit library. Drag & drop the BACService into your App. The object can be dropped in the EasyIO folder or a new folder can be created for the Service Object. In the example below, the object is dropped into a new folder named “BACnet”.


15

Step 4 Click at the service object to access the property at the property side bar. Configuration of the BACnet communication parameters such MSTP MAC address is carried out here. Select BACnet communication stack to be enabled. By default both IP stack and MSTP stack is disable.

If the communications stack if configured correctly, the status will display as OK. Step 5 Choose easyioFGBACnet from kit library.

Drag and drop the BACClientNetwork into your App . The object can be dropped in the EasyIO folder or a new

folder can be created for the Bacnet Network Object.

In the example below, the object is dropped into a new folder named “Bacnet”.

***The BACnet server and BACnet client object can be coexist under the BACnet service object. *** ***There can only be one (1) BACnet service object in a controller. ***


16

***No duplicate BACnet Service object is allowed. *** Step 6 Click at the Client Network object to access the property at the property side bar. Enable the Client Network. Once the network is enable, the IP service and MSTP service should display OK if both are enable at the BACnet Service object. These statuses are reflected by the BACnet Service object configurations.

Optionally the “writeOnStart” and “writeOnUp” can be enabled to allow the client to rewrite a value once any of the mention condition occurred. These options are good to set to true for efficient integration.

**Note** For MS/TP connection, only Port 1 is allowed.


17

Step 7 Double click at the Client object. This will display the CPT custom bacnet device discovery view. To change the view to the standard wire sheet view, click the top right corner and select “Wire Sheet View”.

Make sure you followed step 2 before running the BACnet discovery process.

In the custom view, click discover at the bottom of the page to proceed with BACnet device discovery. Click OK to proceed. Optionally device discovery can be limit to certain BACnet Instance by entering the device instance.

Step 8 The CPT Tool will start its Who-Is and I-Am process. If the device discovery is successful the custom view will display a list of device/devices.

If the list does not show any device after the discovery process this might due to a large network. Increase the max wait seconds at the pop up.


18

Step 9 Drag and drop the desire BACnet device into the Subscribed Pane. Optionally double click the device at the discovered pane can be done to add the controller into the subscribed pane.

Step 10 Double click a BACnet subscribed device to perform the BACnet point’s discovery.

Step 11 Select the desire point/points by clicking at the points. Drag and drop the desire BACnet device into the Subscribed Pane. If more than one (1) point is needed, selecting a group can be perform by holding the “Ctrl” key.


19

Step 12 To view the BACnet objects (subscribed BACnet points) in workspace, toggle the wire sheet view.


20

BACnet MS/TP best practice (EIA-485) Below are a few best practice for BACnet MS/TP wiring guide but not limited to.

1. DO NOT run the MSTP bus cable across or near any high voltage cables.

2. EIA-485 require 3 conductors (wire or some may call it cable) It is TX , RX and a Gnd. The Gnd conductor is not Ground (some may call it earth). So DO NOT ever connect this conductor to the Ground. The 3rd conductor is actually a reference signal for both TX and RX. The TX and RX voltage is measured relative to this Gnd conductor. Connecting this to the Ground will cause a incorrect voltage and may even damaged the transceiver. In case there is no signal reference terminal (such as EasyIO FG Series), you can connect this 3rd conductor to any common terminal within the controller (for example EasyIO FG UO common terminal).

3. Use the correct cables in term of impedance. Always choose low impedance cables. Recommended to run 100 Ohms / 120 Ohms impedance cables.

4. Recommended to run Belden Twisted Shielded Pair cable model number Belden 3106A. If the mention model is not available, any equivalent brand with same characteristic is accepted. Make sure they are EIA-485 standard communication cable where the nominal impedance is 120 Ohm. (NOT Impendence per feet run)

Baud Rate (kbps) Max Distance (Meter) Wire Gauge (AWG)

9600 1200 18

19200 900 18

38400 or higher 600 22

5. DO NOT connect more than 31 BACnet MSTP device in a single network (single trunk).

Technical Support For technical support issues please contact technical support person as below;

Email :[email protected]

EasyIO FG BACnet User Guide Version 2 · Points The BACnet driver easyioFGBACnet is dependent on...

Documents

Transcript of EasyIO FG BACnet User Guide Version 2 · Points The BACnet driver easyioFGBACnet is dependent on...