FS Series BACnet v1.

EasyIO FS Series
BACnet User Guide

1
FS Series BACnet v1.1

Document Change Log

th
27 Dec 2019
Created for FS Series ONLY.

2
FS Series BACnet v1.1

Disclaimer

Confidentiality Notice
The information contained in this document is confidential information of EasyIO Holdings Pte Ltd. Such
information and the software described herein, is furnished under a license agreement and may be used
only in accordance with that agreement.
The information contained in this document is provided solely for use by EasyIO Holdings Pte Ltd employees,
licensees, and system owners; and, except as permitted under the below copyright notice, is not to be released to,
or reproduced for, anyone else.
While every effort has been made to assure the accuracy of this document, EasyIO Holdings Pte Ltd is not
responsible for damages of any kind, including without limitation consequential damages, arising from the
application of the information contained herein. Information and specifications published here are current as of
the date of this publication and are subject to change without notice. The latest product
specifications can be found by contacting our corporate headquarters or support channel.

Trademark Notice

EasyIO logo are registered trademarks of EasyIO Holdings Pte Ltd.

CPT Tool is by Online Tools Inc.

BACnet and ASHRAE are registered trademarks of American Society of Heating, Refrigerating and Air-
Conditioning Engineers. All other product names and services, mentioned in this publication, that are
known to be trademarks, registered trademarks, or service marks are the property of their respective
owners.

Copyright and Patent Notice

This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced
to any electronic medium or machine-readable form without prior written consent from EasyIO Holdings Pte Ltd

Copyright © 2019 EasyIO Holdings Pte Ltd. All rights reserved

Disclaimer
The material in this manual is for information purposes only. The contents and the product it
describes are subject to change without notice. EasyIO Holdings Pte Ltd makes no
representations or warranties with respect to this manual. In no event shall EasyIO Holdings Pte Ltd be liable for
any damages, direct or incidental, arising out of or related to the use of this manual.

EasyIO Holdings Pte Ltd

101, Cecil Street #09-07
Tong Eng Building
Singapore 069533

Worldwide and Asia Pacific Support : support@easyio.com

Americas Support : support@easyio.pro
Europe Support : support@easyio.eu

3
FS Series BACnet v1.1

Federal Communication Commission Interference Statement

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15
of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a
residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular installation. If this equipment does
cause harmful interference to radio or television reception, which can be determined by turning the equipment off
and on, the user is encouraged to try to correct the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.
Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void
the user's authority to operate this equipment.

FCC Caution
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation.

FCC Radiation Exposure Statement

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This
equipment should be installed and operated with minimum distance 20cm between the radiator & your body.
RF Exposure: A distance of 20 cm shall be maintained between the antenna and users, and the transmitter module
may not be co-located with any other transmitter or antenna.

4
FS Series BACnet v1.1

Table of Contents
Introduction ................................................................................................................................................................... 6
Prerequisites .................................................................................................................................................................. 6
BACnet Server - Configuration Limitations .................................................................................................................... 7
BACnet Server Configuration ......................................................................................................................................... 8
BACnet Client - Configuration Limitations .................................................................................................................. 13
Device and Points limitation .................................................................................................................................... 13
Objects supported ................................................................................................................................................... 13
BACnet Client Configuration ........................................................................................................................................ 14
BACnet MS/TP best practice (EIA-485) ........................................................................................................................ 22
Technical Support ........................................................................................................................................................ 22

5
FS Series BACnet v1.1

Introduction
The EasyIO FS 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 efficiently is firmware build 51 or later.

Prerequisites
1. CPT Tool dated 10th Oct 2018 or later. Latest CPT at the time of the document is 06th Dec 2019.
2. For FS Series, firmware has to be V3.0b51b or later.

6
FS Series BACnet v1.1

BACnet Server - Configuration Limitations

Objects Properties Supported Optional Total Objects
supported Properties ( FS Series )
Supported
Device Object Identifier Max Master 1
Object Name Max Info Frames
APDU Timeout Description
Number Of APDU Retries
Binary Value Object Identifier Description 512
( BV ) Object Name Priority Array ( BV 0 ~ BV 511 )
Present Value Relinquish Default
Relinquish Default
Analog Value Object Identifier Description 512
( AV ) Object Name Priority Array ( AV 0 ~ AV 511 )
Present Value Relinquish Default
Relinquish Default
Binary Object Identifier Description 32
Schedule Object Name Present Value Schedule 0 ~ Schedule 31
Effective Period Reliability
Schedule Default
Priority for Writing
Weekly Schedule
Exception Schedule

Analog Object Identifier Description 32

Schedule Object Name Present Value Schedule 32 ~ Schedule 64
Effective Period Reliability
Schedule Default
Priority for Writing
Weekly Schedule
Exception Schedule

Calendar Object Identifier Description 16

Object Name Present Value (Calendar 0 ~ Calendar 15 )
Date List

7
FS Series BACnet v1.1

BACnet Server Configuration

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 server objects)

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.12
Username : admin
Password :<no password>

Add the kits to the controller by navigating to manage kits and install easyioFGBACnet and easyioFGDriver into
your controller.

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”.

8
FS Series BACnet v1.1

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.

**Note**
For MS/TP connection, only Port 1 is supported.
Port 2 DO NOT support BACnet MS/TP.

The BACnet service or in other words, the FS can registered itself to a BBMD device to able to receive broadcast
messages. These is done through the bbmdEnable, bbmdIp and bbmdTTL properties.
If BBMD is not preset or required in the network these properties can be left blank.
EasyIO FG+ and FS Series is NOT a BBMD Device nor BACnet Router.

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

FS Series Baud Rate Supported

9.6k , 19.2K, 38.4K, 76.8K

9
FS Series BACnet v1.1

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 NOT 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.

10
FS Series BACnet v1.1

Step 6
Drop BACServerBv or BACServerAv type object under the Network Object.
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.

11
FS Series BACnet v1.1

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.

Maximum character allowed for objectName is 63 characters.

Please refer to above objects address limitation for respective series.

Step 8
The BACnet objects by itself does not export any valid value.
You will need to manually link a valid value to the BACnet objects.
Below an example of exporting a valid temp value as BACnet objects.

Step 9
Use BACnet Client to discover the device and objects.

12
FS Series BACnet v1.1

BACnet Client - Configuration Limitations

Device and Points limitation
Maximum Recommendation Matrix FS Series
( A combination of IP device and MS/TP Device )
31
Device Count

Points Count per Device 32

Objects supported

Objects Types Supported Object Property Supported

Analog Input , AI Object Identifier

Object Name
Present Value
Analog Output , AO Object Identifier
Object Name
Present Value
Priority Array
Relinquish Default
Analog Value , AV Object Identifier
Object Name
Present Value
Priority Array
Relinquish Default
Binary Input , BI Object Identifier
Object Name
Present Value
Binary Output , BO Object Identifier
Object Name
Present Value
Priority Array
Relinquish Default
Binary Value , BV Object Identifier
Object Name
Present Value
Priority Array
Relinquish Default
Multi State Input , MSI Object Identifier
Object Name
Present Value
Multi State Output , MS0 Object Identifier
Object Name
Present Value
Priority Array
Relinquish Default
13
FS Series BACnet v1.1

Multi State Value , MSV Object Identifier

Object Name
Present Value
Priority Array
Relinquish Default
Loop Object Identifier
Object Name
Present Value

BACnet Client Configuration

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 FS as BACnet IP client.

14
FS Series BACnet v1.1

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

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 CPT Tool.
Default login credentials are as below;
IP address : 192.168.10.12
Username : admin
Password :<no password>

Add the kits to the controller by navigating to manage kits and install easyioFGBACnet and easyioFGDriver into
your controller.

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”.

15
FS Series BACnet v1.1

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.

16
FS Series BACnet v1.1

**Note**
For MS/TP connection, only Port 1 is supported.
Port 2 DO NOT support BACnet MS/TP.

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”.

17
FS Series BACnet v1.1

***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. ***
***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.

Step 7
Double click at the BACnet 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.

18
FS Series BACnet v1.1

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.

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.

19
FS Series BACnet v1.1

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.

***Tips
Each device can only have up to 32 BACnet objects. If more is needed, duplicate the device and assign the same
device ID to both device.

20
FS Series BACnet v1.1

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

21
FS Series BACnet v1.1

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.

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 issue, please contact respective region support channel.

Worldwide and Asia Pacific Support : support@easyio.com

Americas Support : support@easyio.pro
Europe Support : support@easyio.eu

22