Johnson Controls EasyIO FS Series User manual

EasyIO FS Series
BACnet User Guide
LIT-12013777

Disclaimer
Confidentiality Notice
The information contained in this document is confidential information of Johnson Controls (S) 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 Johnson Controls (S) 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, Johnson Controls (S) 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 logos are registered trademarks of Johnson Controls (S) Pte Ltd.
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.
Freeboard is an open source real time Dashboard builder.
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 Johnson Controls (S) Pte Ltd
Copyright © 2019 Johnson Controls (S) 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. Johnson Controls (S) Pte Ltd makes no
representations or warranties with respect to this manual. In no event shall Johnson Controls (S) Pte Ltd be liable for any
damages, direct or incidental, arising out of or related to the use of this manual.
Johnson Controls (S) Pte Ltd
31, International Business Park,
#03-02, Singapore 609921
Singapore 609921
Worldwide and Asia Pacific Support: [email protected]
Americas Support: [email protected]
Europe Support: [email protected]

United States
Canada
This Class (B) digital apparatus meets all the requirements of the Canadian Interference-Causing Equipment Regulations.
Cet appareil numérique de la Classe (B) respecte toutes les exigences du Règlement sur le matériel brouilleur du
Canada.
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two
conditions:
1. This device may not cause interference, and
2. This device must accept any interference, including interference that may cause undesired operation of the
device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence.
L'exploitation est autorisée aux deux conditions suivantes :
1. L'appareil ne doit pas produire de brouillage, et
2. L'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en
compromettre le fonctionnement.
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,maycause harmful interference toradio 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 isconnected.
• Consult the dealer or an experienced radio/TV technician for help.
Warning (Part 15.21)
Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to
operate the equipment.

Table of Contents
Introduction ................................................................................................................................................................... 5
Prerequisites .................................................................................................................................................................. 5
BACnet server configuration limitations........................................................................................................................ 5
BACnet server configuration.......................................................................................................................................... 6
BACnet schedule...................................................................................................................................................... 11
BACnet calendar ...................................................................................................................................................... 11
BACnet trend ........................................................................................................................................................... 12
BACnet client configuration limitations....................................................................................................................... 12
Device and points limitation.................................................................................................................................... 12
BACnet client configuration......................................................................................................................................... 13
SA bus devices ......................................................................................................................................................... 19
Tech tips....................................................................................................................................................................... 21
BACnet MSTP best practice (EIA-485).......................................................................................................................... 21
Technical support......................................................................................................................................................... 22

Introduction
The EasyIO® FS series operates as a BACnet device and BACnet client. The series handles the following BACnet
protocols:
•BACnet IP server
•BACnet MSTP server
•BACnet IP Client
•BACnet MSTP Client
Prerequisites
A prerequisite for the FS series is the latest version of CPT Tools. The firmware must also be V3.0b51b or later.
BACnet server configuration limitations
The FS series controller does not provide power on the SA bus. You must use an external power source.
Objects supported
Properties supported
Optional properties
supported
Total objects
( FS series )
Device
Object Identifier
Object Name
APDU Timeout
Number Of APDU Retries
Max Master
Max Info Frames
Description
1
Binary value (BV)
Object Identifier
Object Name
Present Value
Relinquish Default
Description
Priority Array
Relinquish Default
512
(BV 0 ~ BV 511)
Analog value (AV)
Object Identifier
Object Name
Present Value
Relinquish Default
Description
Priority Array
Relinquish Default
512
(AV 0 ~ AV 511)
Multistate value (MV)
Object Identifier
Object Name
Present Value
Relinquish Default
Description
Priority Array
Relinquish Default
State Text (32)
512
(MV 0 ~ MV 511)
Binary
schedule
Object Identifier
Object Name
Effective Period
Schedule Default
Priority for Writing
Weekly Schedule
Exception Schedule
Description
Present Value
Reliability
32
Schedule 0 ~ Schedule 31
Analog schedule
Object Identifier
Object Name
Effective Period
Schedule Default
Priority for Writing
Weekly Schedule
Exception Schedule
Description
Present Value
Reliability
32
Schedule 32 ~ Schedule 64
Calendar
Object Identifier
Description
16

BACnet server configuration
You can deploy the architecture of the driver, as per the below procedure. You can drop the network object
anywhere in the Sedona app tree. It is best practice to create a separate folder for each network.
Bacnet Service
Bacnet Server Network (IP and MSTP)
Points (BACnet server objects)
The BACnet driver kit, easyioFGBACnet,is dependent on the installation of the easyioFGDriver. To install both kits
to enable configuration of the BACnet network in an FS series device, complete the following steps:
1. Connect to the controller with Sedona Workbench or CPT Tools with the following default logon
credentials:
•IP address: 192.168.10.12
•Username: admin
•Password: <no password>
2. To add the kits to the controller, navigate to the kit management and install easyioFGBACnet and
easyioFGDriver on your controller.
3. Select easyioFGBACnet from the kit library, drag the BACService object into the EasyIO folder on your app.
Alternatively, you can create a new folder for the Service Object. In the following example, the object is in
a new folder with a BACnet label.
Object Name
Date List
Present Value
(Calendar 0 ~ Calendar 15)
Trend logs
(Support boolean,
float and integer)
Object Identifier
Object Name
Object Type
Enable
Stop When Full
Buffer Size
Log Buffer
Record Count
Total Record Count
Event State
Logging Type
Status Flag
Log Interval
Description
Trigger
32
(Trend 0 ~ Trend 31)

4. To view the property on the property sidebar, click the BACnet service object. In the below example, there
is the configuration of the BACnet communication parameters, such as the MSTP MAC address.
5. Select the BACnet communication stack that you want to enable. By default, both the IP stack and MSTP
stack are disabled.

Note: For the MSTP connection, Port 1 is supported. Port 2 does not support BACnet MSTP. EasyIO FS
series is not a BBMD device or BACnet router. The FS BACnet service can register itself to a BBMD device
to receive broadcast messages through the bbmdEnable, bbmdIp, and bbmdTTL properties. If BBMD is not
preset or required in the network, these properties must be blank. If the communications stack is
configured correctly, the status displays OK.
FS Series Baud Rate Supported
9.6k , 19.2K, 38.4K, 76.8K
6. From the easyioFGBACnet object, drag BACnetServerNetwork into the BACnet service object on your app.
Note: The BACnet server and BACnet client object can coexist under the BACnet service object. There can
only be one BACnet service object in a controller. You cannot duplicate the BACnet service object.
7. To view the property on the property sidebar, click the Server Network object and enable the server
network. If the IP service and MSTP service are enabled correctly for the BACnet Service object, the status
displays OK.

8. Drag the BACServerBV, BACServerAV, BACServerMSV, BACServerTrend, or BACSchedule type object under
the Network object. The register object must be a child folder of the network object.
Note: By default, all registers are set to the disabled mode of enable = false. If you want other systems,
such as BACnet client, to discover the register, you must enable each register object in the application. By
default, the registers are named according to the type followed by the address number. To enter a
preferred name for the object, right-click the object and select selObjectName or manually enter the
object name in the property sidebar. The maximum number of characters permitted for objectName is 63.
As shown in the figure, you must also add the instanceNumber object. The instance number limitation is 0
to 512.

9. Use the manual process to link a valid value to the BACnet objects. The BACnet objects do not export any
valid value by themselves. In the following figure, to export a valid temp value as a BACnet object, write
from the temp value to the BACnetAV object.

10. After the BACnet objects are linked, use a BACnet client to discover the device and objects.
BACnet schedule
The binary and analog schedules are supported in the FS series. The schedule objects are read-only objects in CPT
Tools. A BACnet client is required to write to the schedule objects. All values are stored in the flash memory and
included in a backup. Each schedule day can hold up to eight events or four periods. You can link the output of the
schedule object to internal logic. The schedule object complies to the BACnet standard. All compatible BACnet
clients can write to the schedule object.
BACnet calendar
The calendar schedule is supported in the FS series. The schedule objects are read-only objects in CPT Tools. A
BACnet client is required to write to the schedule objects. All values are stored in the flash memory and included in
a backup. Each calendar object can hold up to 16 calendar dates or date ranges.

BACnet trend
The EasyIO FS series supports the BACnet trend. There are a total of 32 BACnet trends available. You can configure
the trends as Boolean trend, Analog trend, or Multistate trend. Each trend allows up to 1,000 records. The trend
performs a first in first out process, when the stopIsFull policy is set to false.
To clear the records, right-click the BACnetTrend object, click Actions, and click clearRecords. Use the manual
process to link a valid value to the BACnet Trend objects. The BACnet Trend objects do not trend any valid value by
themselves. You can trend a valid temp value as a BACnet object.
BACnet client configuration limitations
Device and points limitation
In V3.0b54 firmware or newer, the FS series supports the Johnson Controls SA Bus series thermostat. These models
are limited to NS8000 and NSA7000. You can use MSTP devices and SA Bus devices on the same bus. You can
connect a maximum of five SA bus devices to each FS RS-485 bus.
Maximum Recommendation Matrix
(A combination of IP device and MSTP Device + SA Bus
devices)
FS Series
Device Count
63
(For example, 32 IP devices
and 31 MSTP devices, where
you can only have a
maximum of five SA Bus
devices)
Points Count per Device
32
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
Multi State Value, MSV
Object Identifier
Object Name
Present Value
Priority Array
Relinquish Default
Loop
Object Identifier
Object Name
Present Value
BACnet client configuration
You can drop the network object anywhere in the Sedona app tree. For example, you can create a separate folder
for each network.
Service
BACnet client Network (Both IP and MSTP)
Device
Points
The BACnet driver, easyioFGBACnet,is dependent on the installation of the easyioFGDriver. To enable the
configuration of the BACnet client network in a FS series device, you must install these kits. To install the kits,
complete the following steps:
1. Connect to the controller with Sedona Workbench or CPT Tools with the following default logon
credentials:

•IP address : 192.168.10.12
•Username : admin
•Password :<no password>
2. To add the kits to the controller, navigate to the kit management and install easyioFGBACnet and
easyioFGDriver on your controller.
3. Select easyioFGBACnet from the kit library, drag the BACService object into the EasyIO folder on your app.
Alternatively, you can create a new folder for the Service Object. In the following example, the object is in
a new folder with a BACnet label.
4. To view the property on the property sidebar, click the service object. In the above example, there is the
configuration of the BACnet communication parameters, such as the MSTP MAC address.
5. Select the BACnet communication stack that you want to enable. By default, both the IP stack and MSTP
stack are disabled.

Note: For the MSTP connection, Port 1 is supported. Port 2 does not support BACnet MSTP. EasyIO FS
series is not a BBMD Device nor BACnet Router. The FS BACnet service can register itself to a BBMD device
to receive broadcast messages through the bbmdEnable, bbmdIp, and bbmdTTL properties. If BBMD is not
preset or required in the network, these properties must be blank. If the communications stack is
configured correctly, the status displays OK.
6. To view the property on the property sidebar, click the Server Network object and enable the server
network. If the IP service and MSTP service are enabled correctly for the BACnet Service object, the status
displays OK.
7. Drag the BACServerBV, BACServerAV, BACServerMSV, BACServerTrend, or BACSchedule type object under
the Network object. The register object must be a child folder of the network object.
Note: The BACnet server and BACnet client object can coexist under the BACnet service object. There can
only be one BACnet service object in a controller. No duplicate BACnet service object is allowed.

8. To view the property on the property sidebar, click the client network object and enable the client
network. After you enable the network, the IP service and MSTP service displays OK. You can view the
status in the BACnet service object configurations. Alternatively, you can enable writeOnStart and
writeOnUp to permit the client to rewrite a value when certain conditions occur. For efficient integration,
set the conditions to true.
9. Double-click the BACnet client object, which displays in the CPT custom BACnet device discovery view. To
change the view to the standard wiresheet view, click the Menu icon and select WireSheet View.
10. In the custom view, click Discover to proceed with the BACnet device discovery and click OK. Alternatively,
you can enter the device instance information to limit the device discovery to a specific BACnet instance.
CPT Tools begins a Who-Is and I-Am process. If the device discovery is successful, the custom view displays
a list of devices. If there is a large network, a device might not appear after the discovery process. If this
occurs, you must increase the maximum wait seconds.

11. Drag the BACnet device to the Subscribed pane. Alternatively, double-click the device in the discovered
pane.
12. Double-click a BACnet device to perform the BACnet point discovery.
13. To select the points, click the required points and drag the BACnet device to the Subscribed pane. If you
require more than one point, press the Ctrl key to select a group or press the Shift key to select sequential
points.

Note: Each device can have up to 32 BACnet objects. If you require more objects, duplicate the device and
assign the same device IDs to both devices.
14. To view the subscribed BACnet points in the workspace, toggle the wiresheet view.

SA bus devices
Sedona 2.0 Framework supports the SA Bus device. You must ensure that your controller firmware is V3.0b54 or
later. The SA Bus devices are BACnet subordinate devices and do not support device discovery. You must manually
add the device to the application.
To add the SA Bus device, complete the following steps:
1. Drag the device from userLib in CPT Tools to the BACnet client Network wiresheet. The device information
auto-populates in the wiresheet.
Note: SA Bus devices have two terminals for communication and two terminals for 15 VDC power. You
must source the 15 VDC power externally. Connect the communication wires, SA+ and SA- , to the RS485
D+ and D- terminals on the FW controller. You can connect SA bus devices with other MSTP devices in the
same trunk.

2. Set the subordinate property to true, enter the subordinate MAC address, and then enter the BACnet
device ID. In the following figure, you can view a successful communication, where the deviceName
property has a value.
3. To view the objects, double-click the device.