EasyIO FG Series User manual

Peer to Peer v2.1
1
EasyIO FG Series, FS Series and FW Series
Peer to Peer User Guide

Peer to Peer v2.1
2
Document Change Log
06th May 2014
Document created.
20th July 2015
Update for prerequisites.
5th August 2015
Added Time Sync.
17th Dec 2018
Updated disclaimer and support channel emails addresses
Updated images to reflex CPT Tools
Updated document to include FS Series and FW Series.

Peer to Peer v2.1
3
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 : [e-mail]
Americas Support : [e-mail]
Europe Support : [e-mail]

Peer to Peer v2.1
4
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.

Peer to Peer v2.1
5
Table of Contents
Introduction ...................................................................................................................................................................6
Prerequisites ..................................................................................................................................................................7
Sync the Controller Time ...............................................................................................................................................7
Peer to Peer configuration.............................................................................................................................................8
Technical Support ........................................................................................................................................................12

Peer to Peer v2.1
6
Introduction
The Peer to Peer feature is a manufacture specific feature where point sharing is enabled on the network among
the following EasyIO controllers:
1. FS Series controller
2. FG+ series controller
3. FW series controller
4. FT series controller
The P2P service has 256 global registers with each register being a 4 byte register (32bit).
The P2P service creates a cloud like environment of global registers in the network that does not belong to any
specific controller.
The P2P service uses a broadcast protocol to update the registers.
The P2P service is only able to run within the same subnet of the network.
Any controller can write to any register or read any register.
If there are 2 controllers writing to the same register, then the concept of “last write wins” gets taken into account.
Below is a simple diagram displaying the concept of the Peer to Peer feature.

Peer to Peer v2.1
7
Prerequisites
1. CPT Tool dated 6th Dec 2018 or later.
2. FG Series firmware version v1.5b50 or later (EasyIO FG) and v2.0b50 or later for (EasyIO FG+) is required for
best performance.
3. For FS Series, firmware has to be V3.0b50 or later.
4. For FW Series, firmware has to be V1.0b12d or later.
5. For FT Series, firmware has to be V2.1b11 or later.
6. Minimum 2 or more controllers running P2P service in the same subnet.
If there is only one controller running in the same subnet, the broadcast status will be down.
Sync the Controller Time
Failure to perform this will caused the P2P not to run properly.
Step 1
Double click the “service” folder to display all the service objects.
Single clicking the “time” object displays the time object property view in the Right pane of the CPT Tool view.
Double clicking the “time” object opens a new window where configuration of the FG Series Controller RTC is
possible.
Step 2
Double click the “time” object.
In the New Date Time window select the “Configuration” radio button and click the “LocalTime” button.
Step 3
Click the Save button in the New Date Time window. The controller RTC should now be synced with your
computer’s time, inclusive of the Time Zone. This can be verified by reviewing the “Sedona Date Time” option.

Peer to Peer v2.1
8
Peer to Peer configuration
The architecture of the EasyIO F Peer to Peer kit is deployed as shown below in Step 2. The P2P service object can
be dropped anywhere in the Sedona app tree. Our recommendation is to create a separate folder and identify as
you require.
Service
Object
Step 1
Connect to the controller with CPT Tool.
Default login credentials are as below;
IP Address : 192.168.10.11 (FG+ Series) , 192.168.10.12 (FS Series) , 192.168.10.30 (FW Series)
Username : admin
Password :<no password>
Add the controller type P2P kit to the controller by navigating to manage kits and install easyioFGP2P OR
easyioFWP2P into your controller.
Image below shown is the kit for FG+ series and FS Series
Image below shown is the kit for FW series.
Step 2
Choose easyioFGP2P (easyioFWP2P) from Sedona Palette
Drag & drop the P2PService into your App. The object can be dropped in the EasyIO folder or a new folder can be
created for the P2P service.
In the example below, the object is dropped into a new folder named “P2P”.
**Note**
Once the P2P service is in the Sedona apps and enabled, the controller is considered part of the global registers
network.

Peer to Peer v2.1
9
Step 3
Click at the P2PServ to access the property.
Enable the service by selecting the Enable property to true.
The default port for P2P service is UDP 6061. The UDP port cannot be change.
The broadcast status will show only “Alive” if more than 1 controller is detected to have the P2P service enabled
within the network subnet.
***Note***
Please make sure all the controllers that utilize the P2P feature in the network are running the same P2P version
as image below.
The P2P feature has a maxUpdateTime property.
The MaxUpdateTime property if enabled (value > zero) will force a write to the global register even if there is no
change of value is detected. Essentially a “re-write” of the value to the network.
This feature is handy if a message gets missed due to a controller being powered down.
The MaxUpdateTime is tied to an individual P2P object property called enableMaxWrite. The enableMaxWrite
property has to be enabled as well in order for the feature to re-write again once the timer has expired.
The minUpdateTime property is essentially a “delay” to keep the traffic on the network from becoming too
frequent. The factory default is set to 100ms. Depending on your application you may choose to increase that
time up to 1000ms (1sec) delay.
The onStartDataSync allows for the controller to sync it’s value to the network.
If the controller is writing the value to the network, then upon start, the controller will write it’s value out to the
P2P network.
If the controller is reading the value from the network, the upon start, the controller will pull the value from the
P2P network.
Step 4
Drag and drop the P2P object into the P2P service. In the example below a P2P Boolean data type is used.
The other 2 type of P2P object are Float and Integer data type.
The P2P points must reside under the P2PService object to function correctly.

Peer to Peer v2.1
10
Step 5
Click at the P2P point object to access property sheet.
Enable the point by modifying the enable property to “true”object.
If the object needs to write to registers on the network, enable the “readWrite”property.
Configure the address. Address range allowed is from 0 –255.
The bit property is for a Boolean data type objects ONLY. This allows users to fully utilize each bit of the register
and get up to 32 Boolean objects per register instead of only 1 Boolean register per 32 bit.
Example:
Boolean 1 can be configured to be register 0 / bit 0
Boolean 2 can be configured to be register 0 / bit 1
All 32 bits can be utilized, so 32 boolean points per 1 register as long as the bits are assigned properly
The 256 register addresses are shared among all data types.
As an example, if address 1 is used for boolean object then address 1 is no longer valid to be used by float or
integer.
The next object such as float data or integer data will need to occupy address 2 or any other register.
Step 6
Create multiple P2P objects by repeating step 4 and step 5.
If a Float or Integer data type object is used the Bit property is disabled.
It is not necessary to have all the points addressed in a controller.
There may be a situation where only a few controllers are sharing the same point, and the other controller does
not require that specific point.

Peer to Peer v2.1
11
Example:
In case there are 2 controllers writing to a same address then the last write wins.
Step 7
The P2P objects by itself does not write a value to the global registers.
You will need to manually link a valid value to the P2P objects.
Below an example of exporting a valid value to a P2PBoolean object.

Peer to Peer v2.1
12
Technical Support
For technical issue, please contact respective region support channel.
Worldwide and Asia Pacific Support : [e-mail]
Americas Support : [e-mail]
Europe Support : [e-mail]