Related Manuals for EasyIO FG Series
Summary of Contents for EasyIO FG Series
- Page 1 Peer to Peer v2.1 EasyIO FG Series, FS Series and FW Series Peer to Peer User Guide...
- Page 2 Peer to Peer v2.1 Document Change Log May 2014 Document created. July 2015 Update for prerequisites. August 2015 Added Time Sync. Dec 2018 Updated disclaimer and support channel emails addresses Updated images to reflex CPT Tools Updated document to include FS Series and FW Series.
- Page 3 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.
- Page 4 Peer to Peer v2.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.
-
Page 5: Table Of Contents
Peer to Peer v2.1 Table of Contents Introduction ................................... 6 Prerequisites .................................. 7 Sync the Controller Time ............................... 7 Peer to Peer configuration ............................. 8 Technical Support ................................ 12... -
Page 6: Introduction
Peer to Peer v2.1 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. -
Page 7: Prerequisites
1. CPT Tool dated 6 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. -
Page 8: Peer To Peer Configuration
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. - Page 9 Peer to Peer v2.1 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.
- Page 10 Peer to Peer v2.1 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.
- Page 11 Peer to Peer v2.1 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.
-
Page 12: Technical Support
Peer to Peer v2.1 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...
Need help?
Do you have a question about the FG Series and is the answer not in the manual?
Questions and answers