APPLICABILITY & EFFECTIVITY

Transcription

1 ProtoAir FPA-W34 Start-up Guide For Interfacing Eaton Products: Greengate, ilumin and Fifth Light To Building Automation Systems: BACnet MS/TP, BACnet/IP, Modbus TCP/IP and Modbus RTU APPLICABILITY & EFFECTIVITY Explains ProtoAir hardware and installation. The instructions are effective for the above as of June Document Revision: 1.A Auto Discovery Template Revision: 1

2 Technical Support Thank you for purchasing the ProtoAir for Eaton. Please call Eaton for Technical support of the ProtoAir product. SMC does not provide direct support. If Eaton needs to escalate the concern, they will contact Sierra Monitor Corporation for assistance. Support Contact Information: Eaton Lighting Systems 203 Cooper Circle Peachtree City, GA Eaton Service: Website: Contact Information

3 Quick Start Guide 1. Record the information about the unit. (Section 3.1) 2. Set the Device COM setting that will be connected to ProtoAir. (Section 3.3) 3. Connect the ProtoAir FPA-W34 3 pin RS-485 port to the Field Protocol cabling (Section 4.1) 4. Connect Power to the ProtoAir 3 pin connector. (Section 4.2) 5. Connect a PC to the ProtoAir via Ethernet cable and change the IP Address of the PC to the same subnet as the ProtoAir. Set the IP Address of the ProtoAir to the subnet of the intended Network and reset IP details of the PC. (Section 5) 6. Set the field protocol settings via the Web Configurator. (Section 6.1) 7. Greengate/iLumin: Use the Discovery function to configure the ProtoAir and to find any light panels connected to the device. (Section 6.2) 8. Fifth Light: Review System Status and potential errors. (Section 6.3) Contact Information

4 TABLE OF CONTENTS Table of Contents... 4 List of Figures Certification BTL Mark - BACnet Testing Laboratory Introduction ProtoAir Gateway Equipment Setup Record Identification Data Point Count Capacity and Registers per Device Configuring Device Communications Interfacing ProtoAir to Device Wiring Field Port to RS-485 BMS Network Power Up ProtoAir Connect the PC to the ProtoAir over Ethernet Connecting to the ProtoAir via the Ethernet Port Using the FieldServer Toolbox to Discover and Connect to the ProtoAir Select System Updating Network Settings Configuring the ProtoAir Select BMS Protocol Set Device Instance for each Lighting Panel Attached to the Device BACnet MS/TP: Setting the MAC Address BACnet Network Greengate/iLumin: Discover and Configure Light Panels Connected to the ProtoAir Fifth Light: System Status BACnet: Setting Device Instance Offset to Assign Specific Device Instances Using the Embedded BACnet Explorer Discover Device List View Device Details and Explore Points/Parameters Edit the Present Value Field Appendix A Useful Features Appendix A.1. SSL/TLS for Secure Connection Appendix A.1.1. Configuring FieldServer as a SSL/TLS Server Appendix A Simple Secure Server Configuration Appendix A Limiting Client Access Appendix A Upload the Authority File to the FieldServer Appendix A Certificate Validation Options Appendix A Set up Server Certificate Appendix A.1.2. Configuring FieldServer as SSL/TLS Client Appendix A Simple Secure Client Configuration Appendix A Limit Server Access Appendix A Certificate Validation Options Appendix A Set up Client Certificate Appendix B Troubleshooting Tips Appendix B.1. Communicating with the ProtoAir over the Network Appendix B.2. Lost or Incorrect IP Address Appendix B.3. Viewing Diagnostic information Appendix B.4. Checking Wiring and Settings Table of Contents

5 Appendix B.5. LED Diagnostics for Communications Between ProtoAir and Devices Appendix B.6. Before Contacting Technical Support take a Diagnostic Capture Appendix B.7. Updating Firmware Appendix B.8. BACnet: Setting Network_Number for more than one ProtoAir on Subnet Appendix B.9. Securing ProtoAir with Passwords Appendix B.10. Mounting Appendix B.11. Physical Dimensions for FPA-W Appendix B.12. Kaspersky Endpoint Security Appendix C Vendor Information Eaton Appendix C Greengate Mappings to BACnet and Modbus Appendix C Greengate Mappings to BACnet and Modbus Appendix C Greengate Mappings to BACnet and Modbus Appendix C Greengate Mappings to BACnet and Modbus Appendix C Greengate Mappings to BACnet and Modbus Appendix C Greengate Mappings to BACnet and Modbus Appendix C.7. Scene ilumin Mappings to BACnet and Modbus Appendix C.8. Channel ilumin Mappings to BACnet and Modbus Appendix D Reference Appendix D.1. Specifications0F Appendix D.1.1. Compliance with UL Regulations Appendix E Limited 2 year Warranty Table of Contents

6 LIST OF FIGURES Figure 1: ProtoAir Part Numbers Figure 2: Supported Point Count Capacity Figure 3: Greengate Point Count per Device Figure 4: ilumin Point Count per Device Figure 5: Connection from ProtoAir to RS-485 Field Network Figure 6: Termination DIP Switch Figure 7: Required Current Draw for the ProtoAir Figure 8: Connecting Power Figure 9: Ethernet Port Figure 10: Select System Page Figure 11: Web Configurator GUI Figure 12: IP Address Settings via Web GUI Figure 13: BMS Settings Window Figure 14: BACnet/IP Settings Window Figure 15: BACnet MS/TP Settings Window Figure 16: Greengate Discovery Window Figure 17: ilumin Discovery Window Figure 18: Discovery Progress Bar Figure 19: The Discovery Tree Figure 20: View & Edit Gateway Parameters Figure 21: View Light Panel Parameters Figure 22: View & Edit BACnet Parameters on a Lighting Panel Figure 23: Saving Configuration Bar Figure 24: Saved Configuration Figure 25: Clear Configuration Window Figure 26: Fifth Light Landing Page System Status Figure 27: System Status Showing Error Messages Figure 28: Switch to Another Product Figure 29: Web Configurator Device Instance Offset Field Figure 30: Web Configurator Screen with Active Profiles Figure 31: FS-GUI BACnet Explorer Button Figure 32: BACnet Explorer Login Page Figure 33: BACnet Explorer Page Figure 34: Discovery Window Figure 35: Device List Figure 36: Device Sub-items Figure 37: Full Device Sub-items Figure 38: Simplified Device Details Figure 39: Additional Device Details Figure 40: Highlighted Present Value Figure 41: Write Property Window Figure 42: Updated Present Value Figure 43: Ethernet Port Location Figure 44: Error Messages Screen Figure 45: Diagnostic LEDs Figure 46: Ethernet Port Location Figure 47: Web Configurator Network Number Field Figure 48: FS-GUI Passwords Page Figure 49: Password Recovery Page List of Figures

7 Figure 50: DIN Rail Figure 51: ProtoAir FPA-W34 Dimensions Figure 52: Kaspersky ES10 Settings Figure 53: Web Anti-Virus Trusted URLs Figure 54: Specifications List of Figures

8 1 CERTIFICATION 1.1 BTL Mark - BACnet 1 Testing Laboratory The BTL Mark on ProtoAir is a symbol that indicates that a product has passed a series of rigorous tests conducted by an independent laboratory which verifies that the product correctly implements the BACnet features claimed in the listing. The mark is a symbol of a high-quality BACnet product. Go to for more information about the BACnet Testing Laboratory. Click here for the BACnet PIC Statement. 1 BACnet is a registered trademark of ASHRAE Page 8 of 66

9 2 INTRODUCTION 2.1 ProtoAir Gateway The ProtoAir gateway is a high-performance, multi-protocol IIoT gateway that is preconfigured to autodiscover any of Eaton s products (hereafter called device ) connected to the ProtoAir and automatically configures them for BACnet MS/TP, BACnet/IP, Modbus TCP/IP or Modbus RTU. It is not necessary to download any configuration files to support the required applications. The ProtoAir is pre-loaded with tested profiles/configurations for the supported devices. FPA-W34 Connectivity Diagram: Page 9 of 66

10 3 EQUIPMENT SETUP 3.1 Record Identification Data Each ProtoAir has a unique part number located on the side or the back of the unit. This number should be recorded, as it may be required for technical support. The numbers are as follows: Model ProtoAir Part Number FPA-W Figure 1: ProtoAir Part Numbers FPA-W34 units have the following 2 ports: RS Ethernet 3.2 Point Count Capacity and Registers per Device The total number of registers presented by all the devices attached to the ProtoAir cannot exceed: Part number Total Registers FPA-W ,000 Figure 2: Supported Point Count Capacity Greengate Devices Point Count Per Device Figure 3: Greengate Point Count per Device ilumin Devices Point Count Per Device Scene 2 Channel 2 Figure 4: ilumin Point Count per Device NOTE: Fifth light points determined by panel configuration. 3.3 Configuring Device Communications The device needs to be on the same IP subnet as the ProtoAir and the configuration PC. Record the following device information for Greengate and ilumin setup: o IP Address o IP Port o Panel Address (Greengate only) o Number of Panels (Greengate only) NOTE: This information is required for Section 6. NOTE: The ilumin application requires a ilumin configuration file to load device details. NOTE: These parameters are not required for Fifth Light application. Page 10 of 66

11 + 4 INTERFACING PROTOAIR TO DEVICE 4.1 Wiring Field Port to RS-485 BMS Network Connect the RS-485 network wires to the 3-pin RS-485 connector on ProtoAir FPA-W34 as shown in Figure 5. o Use standard grounding principles for RS-485 GND See Section 5 for information on connecting to BACnet/IP network. BMS Wiring ProtoAir Pin # Pin Assignment RS Pin 1 RS RS Pin 2 RS Pin 3 RS-485 GND - G Figure 5: Connection from ProtoAir to RS-485 Field Network If the ProtoAir is the last device on the Serial trunk, then the End-Of-Line Termination Switch needs to be enabled. (Figure 6) o o The default setting from the factory is OFF (switch position = left side) To enable the Termination, turn the EOL switch ON (switch position = right side) Termination Resistor DIP Switch (1) Figure 6: Termination DIP Switch Page 11 of 66

12 4.2 Power Up ProtoAir Check power requirements in the table below: Power Requirement for ProtoAir External Gateway Current Draw Type ProtoAir Family 12V DC 24V DC FPA W34 (Typical) 170mA 100mA FPA W34 (Maximum) 240mA 140mA NOTE: These values are nominal and a safety margin should be added to the power supply of the host system. A safety margin of 25% is recommended. Figure 7: Required Current Draw for the ProtoAir Apply power to the ProtoAir as shown below in Figure 8. Ensure that the power supply used complies with the specifications provided in Appendix D.1. The ProtoAir accepts 12-24V DC on pins 4 and 5. Frame GND should be connected. Power to ProtoAir ProtoAir Pin # Pin Assignment Power In (+) Pin 4 V + Power In (-) Pin 5 V - Frame Ground Pin 6 FRAME GND Figure 8: Connecting Power Page 12 of 66

13 5 CONNECT THE PC TO THE PROTOAIR OVER ETHERNET 5.1 Connecting to the ProtoAir via the Ethernet Port Connect a CAT5 Ethernet cable (straight through or cross-over) between the local PC and ProtoAir. Ethernet Port Figure 9: Ethernet Port The default IP Address for the ProtoAir Ethernet connection is , Subnet Mask is If the PC and ProtoAir are on different IP networks, assign a static IP Address to the PC on the xxx network. For Windows 7 or later: Go to > > > > Then right-click on Local Area Connection then click Properties Highlight then click Use the following IP Address: Click twice. Page 13 of 66

14 5.2 Using the FieldServer Toolbox to Discover and Connect to the ProtoAir Install the FS Toolbox application from the USB drive or get it from the Sierra Monitor website. Use the FS Toolbox to find the ProtoAir IP Address and connect for configuration. NOTE: If the connect button is greyed out, the ProtoAir s IP Address must be set to be on the same network as the PC. Page 14 of 66

15 5.3 Select System After setting the PC on the same subnet as the ProtoAir, open a web browser on the PC and enter the IP Address of the ProtoAir; the Ethernet default address is o The Select System Page will appear the first time the FieldServer is accessed. Select the desired protocol. Figure 10: Select System Page The Web Configurator landing page will now appear. Figure 11: Web Configurator GUI NOTE: If the wrong protocol was selected, click the Clear Configuration or Switch to another product button to reset the GUI and go back to the Select System Page. Page 15 of 66

16 5.4 Updating Network Settings From the Web Configurator, Click the Network Settings tab to open the Network Settings page for the ProtoAir. Figure 12: IP Address Settings via Web GUI Modify the IP Address (N1 IP Address field) of the ProtoAir Ethernet port. If necessary, change the Netmask (N1 Netmask field). If necessary, change the IP Gateway (Default Gateway field). NOTE: If the ProtoAir is connected to a managed switch/router, the IP Gateway of the ProtoAir should be set to the IP Address of that managed switch/router. Click the System Restart button at the bottom of the page to apply changes and restart the ProtoAir. Unplug Ethernet cable from PC and connect it to the network switch or router. Record the IP Address assigned to the ProtoAir for future reference. Page 16 of 66

17 6 CONFIGURING THE PROTOAIR 6.1 Select BMS Protocol Going back to the Discovery and Configuration tab, and press BMS Settings button to view/ change the Building Management System (BMS) Settings. Select BACnet/IP, BACnet MS/TP, Modbus TCP/IP, or Modbus RTU protocols. Figure 13: BMS Settings Window Page 17 of 66

18 Set Device Instance for each Lighting Panel Attached to the Device The Device Instance can be set independently of the site administrator. As an example: A Device Instance is a BACnet Node-ID which is obtained by the network administrator. Each lighting panel connected to the Device will have its own BACnet Device Instance. The values allowed for a BACnet Device Instance can range from 1 to 4,194,303. With the default BACnet Device Instance value of 50,000 the Device Instances values generated will be within the range of 50,000 plus the incremental number of lighting panels that are connected to the ProtoAir. The first lighting panel will therefore be 50,000. To assign a specific Device Instance (or range); change the Device instance value to assigned value of the first lighting panel. The Web Configurator will be displayed as the landing page. Figure 14: BACnet/IP Settings Window Page 18 of 66

19 BACnet MS/TP: Setting the MAC Address BACnet Network Only 1 MAC address is set for ProtoAir regardless of how many light panels are connected to ProtoAir. Set the BACnet MS/TP MAC address of the ProtoAir to a value between 1 to 127 (MAC Master Addresses); this is so that the BMS Front End can find the ProtoAir via BACnet discovery. NOTE: Never set a BACnet MS/TP MAC Address from 128 to 255. Addresses from 128 to 255 are Slave Addresses and can not be discovered by BMS Front Ends that support auto discovery of BACnet MS/TP devices. Enter the following details into the web configuration as per Figure 15 below: Device Instance Enter a range between 1 and 4,194,303 for the ProtoAir. Name Enter a name for the ProtoAir. Location Enter the location of the lighting panel. Device Instance Offset Default of so that Device Instance begins at Network Number Leave as default unless instructed by BMS integrator. Baud Rate Enter a value of 9600, 19200, 38400, or Figure 15: BACnet MS/TP Settings Window Page 19 of 66

20 6.2 Greengate/iLumin: Discover and Configure Light Panels Connected to the ProtoAir For Greengate, click on the Start Discovery button to enter the port, network address, panel address and number of panels for the device. Figure 16: Greengate Discovery Window For ilumin, click on the Start Discovery button to enter the port, network address and ilumin config file to load for the device. Figure 17: ilumin Discovery Window NOTE: To generate an ilumin config file, consult the ilumin manual. Page 20 of 66

21 o o After entering the device details, click on the Start Discovery button and the discovery progress bar will display. Discovering a device may take a few minutes depending on the number of items it contains. Figure 18: Discovery Progress Bar After the discovery process is complete, the discovery tree will immediately come up. The items being marked as green indicate that they have not been configured for protocol conversion. Figure 19: The Discovery Tree o o When clicking on gateways or gateways containing light panels a checkbox will check or uncheck items for protocol conversion. By clicking on a gateway, the parameters will be shown and can be edited. Figure 20: View & Edit Gateway Parameters Page 21 of 66

22 o By clicking on a light panel, parameters for that panel will be shown. Figure 21: View Light Panel Parameters o Clicking on a light displays and allows editing of the preconfigured BACnet parameters. Figure 22: View & Edit BACnet Parameters on a Lighting Panel Once the items for configuration are chosen, click on the Save Configuration button. The save configuration progress bar will appear. This process may take several minutes. Figure 23: Saving Configuration Bar Page 22 of 66

23 When this process is complete, the items on the tree will change from green to black to show that they have been configured. Figure 24: Saved Configuration In order to clear a configuration, click on the Clear Configuration button. An additional option to clear all other device configurations will appear. Figure 25: Clear Configuration Window After clicking on the Clear & Restart button the window will state Configuration cleared. Restarting. After this process is complete, the ProtoAir will automatically restart. Page 23 of 66

24 6.3 Fifth Light: System Status NOTE: Fifth Light configuration must be done on the Fifth Light panel. For Instructions, refer to the Eaton 5 th Light Panel manual. The ProtoAir allows BMS settings to be changed (BBMD settings, Public IP Address, Public IP Port, Router Network Number, Network Number and IP Port) and Fifth Light Panel system information to be reviewed. Figure 26: Fifth Light Landing Page System Status Error messages can be viewed by clicking the heading above a or. Figure 27: System Status Showing Error Messages Page 24 of 66

25 Click the Switch to another product button to clear the current configuration and restart. Figure 28: Switch to Another Product Page 25 of 66

26 7 BACNET: SETTING DEVICE INSTANCE OFFSET TO ASSIGN SPECIFIC DEVICE INSTANCES After setting a local PC to the same subnet as the ProtoAir (Section 5), open a web browser on the PC and enter the IP Address of the ProtoAir; the default address is o o If the IP Address of the ProtoAir has been changed by previous configuration, the assigned IP Address will need to be obtained from the network administrator. The Web Configurator is displayed as the landing page. Device Instance Offset field shows the current value (default = 80,001). o The values allowed for a BACnet Device Instance can range from 1 to 4,194,303. To assign a specific Device Instance (or range); change the Device Instance Offset value as needed using the calculation below: Device Instance (desired) = Offset + Node_ID NOTE: Node_ID is gathered from the Eaton device. For example, if the desired Device Instance for the device 1 is 80,002 and the following is true: - Device 1 has a Node-ID of 1 - Device 2 has a Node-ID of 22 - Device 3 has a Node-ID of 33 Then plug the device 1 s information into the formula to find the desired Offset: 80,002 = Offset ,001 = Offset Once the Offset value is input, it will be applied to all devices as shown below: - Device 1 Instance = 80,001 + Node_ID = 80, = 80,002 - Device 2 Instance = 80,001 + Node_ID = 80, = 80,023 - Device 3 Instance = 80,001 + Node_ID = 80, = 80,034 Click Submit once the desired value is entered. Figure 29: Web Configurator Device Instance Offset Field NOTE: For Fifth Light, the Device Instance is set on the Fifth Light panel. Page 26 of 66

27 8 USING THE EMBEDDED BACNET EXPLORER To access the embedded BACnet Explorer, go to the FS-GUI page and click the BACnet Explorer button. Figure 31: FS-GUI BACnet Explorer Button Then login to the BACnet Explorer page using the supplied username and password. NOTE: The default user name is admin and default password is admin. Figure 32: BACnet Explorer Login Page NOTE: For BACnet/IP, click on the Configuration button on the left side of the landing page to ensure the ProtoAir is on the BACnet/IP network subnet or configure BBMD. Page 27 of 66

28 8.1 Discover Device List From the BACnet Explorer landing page, click on the BACnet Explorer button on the left side of the screen to go to the BACnet Explorer page. Figure 33: BACnet Explorer Page To discover the devices connected to the same subnet as the BACnet Explorer, click the Discover button (binocular icon). This will open the Discovery window, click the checkboxes next to the desired discovery settings and click Discover to start the search. Figure 34: Discovery Window Page 28 of 66

29 NOTE: Allow the devices to populate before interacting with the device list for optimal performance. Any discovery or explore process will cause a green message to appear in the upper right corner of the browser to confirm that the action is complete. Figure 35: Device List 8.2 View Device Details and Explore Points/Parameters To view the device details, click the blue plus sign ( ) next to the desired device in the list. o This will show only some of the device properties for the selected aspect of a device Figure 36: Device Sub-items Page 29 of 66

30 To view the full details of a device, go back to highlighting the device directly (in Figure ) and click the Explore button or double-click the device/object. Figure 37: Full Device Sub-items o Now additional device details are viewable; however, the device can be explored even further Click on one of the device details. Figure 38: Simplified Device Details Page 30 of 66

31 Then click on the Explore button or double-click the device object. Figure 39: Additional Device Details A full list of the device details will appear on the right-side window. If changes are expected since the last explore, simply press the Refresh button that appears on the upper right side of the screen when highlighting individual properties to refresh all the values. NOTE: The Explorer Search Bar will find devices based on their Device ID. NOTE: The Explorer Discovery Tree has 3 levels that correspond to the following. Network number o Device Device object Page 31 of 66

32 8.2.1 Edit the Present Value Field The only recommended field to edit via BACnet Explorer is the device s present value field. NOTE: Other BACnet properties are editable (such as object name, object description, etc.); however, this is not recommended because the BACnet Explorer is a discovery tool not a Building Management System (BMS). To edit the present value, select it in the property listings. Figure 40: Highlighted Present Value Then click the write button (found in the upper right corner of the screen) to bring up the Write Property window. Figure 41: Write Property Window Page 32 of 66

33 Enter the appropriate change and click write. A check will appear inside the save button and the window will close. When the BACnet Explorer page appears the present value will be changed as specified. Figure 42: Updated Present Value Page 33 of 66

34 Appendix A Useful Features Appendix A.1. SSL/TLS for Secure Connection SSL/TLS (Secure Sockets Layer/Transport Layer Security) is a security technology for establishing an encrypted connection between a server and a client. This allows the secure transfer of data across untrusted networks. Appendix A.1.1. Configuring FieldServer as a SSL/TLS Server The following example sets the FieldServer to accept a secure Modbus/TCP connection on port Appendix A Simple Secure Server Configuration Add TLS_Port parameter in the connections section of the configuration file and set to a port number between Connections Adapter, Protocol, TLS_Port N1, Modbus/TCP, 1502 This configuration sets the FieldServer to accept any incoming connection but will not request a client s certificate for verification. This means that the FieldServer end point communication will be encrypted but not authenticated. The FieldServer will send an embedded self-signed certificate if one is requested by a connecting client. NOTE: If a remote client requires a certificate, then request the smc_cert.pem certificate from Sierra Monitor Technical Support and update the remote client s authority as per vendor instructions. Page 34 of 66

35 Appendix A Limiting Client Access In addition to TLS_Port parameter also add Validate_Client_Cert in the connections section of the configuration file and set it to Yes. Connections Adapter, Protocol, TLS_Port, Validate_Client_Cert N1, Modbus/TCP, 1502, Yes The configuration above sets the FieldServer to request and verify a client s certificate against its internal authority file before accepting connection. By default, this means the FieldServer will only accept connections from other FieldServers. In order to load an authority file so that the FieldServer will accept connections from a chosen list of remote clients, configure the FieldServer with the following connection settings: Connections Adapter, Protocol, TLS_Port, Validate_Client_Cert, Cert_Authority_File N1, Modbus/TCP, 1502, Yes, my_authorized_clients.pem This configuration has the FieldServer accept connections from clients who have the correct certificate. The authority file is a collection of client certificates in PEM format. This file can be edited using any text file editor. NOTE: Cert_Authority_File is useful only if Validate_Client_Cert is set to Yes. Appendix A Upload the Authority File to the FieldServer 1. Enter the IP address of the FieldServer into a web browser. 2. Choose the Setup option in the Navigation Tree and Select File Transfer. 3. Choose the General tab. 4. Click on the Browse button and select the PEM file you want to upload. 5. Click on Submit. 6. When it says The file was uploaded successfully, click on the System Restart button. Page 35 of 66

36 Appendix A Certificate Validation Options If connections must be limited to only a particular domain (vendor devices), include Check_Remote_Host to specify the domain/host name. Connections Adapter, Protocol, TLS_Port, Validate_Client_Cert, Cert_Authority_File, Check_Remote_Host N1, Modbus/TCP, 1502, Yes, my_authorized_clients.pem, SMC The configuration above tells the FieldServer to only accept connections that have the correct certification and is coming from the specified host. The Check_Remote_Host value is synonymously known as common name, host name or domain etc. The common name can be obtained by the following methods: Ask the certificate issuer for the host name. Use online tools to decode the certificate (for example: If the program openssl is installed on the local PC, then run the following command to get the common name: openssl x509 -in certificate.pem -text noout Appendix A Set up Server Certificate Make sure the certificate is in PEM format. Otherwise, convert it to PEM format (reference the link below). support.ssl.com/knowledgebase/article Configure the FieldServer to use a custom certificate as shown below: Connections Adapter, Protocol, TLS_Port, Server_Cert_File N1, Modbus/TCP, 1502, my_server_cert.pem Page 36 of 66

37 Appendix A.1.2. Configuring FieldServer as SSL/TLS Client The following Node configurations set the FieldServer to open a secure Modbus/TCP connection to Server at IP Address on port Appendix A Simple Secure Client Configuration Add Remote_Node_TLS_Port parameter in the nodes section of the configuration file and set to a port number between Nodes Node_Name, Node_ID, Protocol, Adapter, IP_Address, Remote_Node_TLS_Port PLC_11, 11, Modbus/TCP, N1, , 1502 The above configuration sets the FieldServer to connect to a remote server but does not request a server s certificate for verification. This means that the FieldServer end point communication will be encrypted but not authenticated. If requested by a remote server, the FieldServer will send an embedded self-signed certificate. Appendix A Limit Server Access Add the Validate_Server_Cert parameter to the client node section of the configuration.., Remote_Node_TLS_Port, Validate_Server_Cert.., 1502, Yes The above configuration sets the FieldServer to request and verify the server s certificate against its own internal authority file before finalizing the connection. By default, this means the FieldServer will only establish connections to other FieldServers.., Remote_Node_TLS_Port, Validate_Server_Cert, Cert_Authority_File.., 1502, Yes, my_authorized_servers.pem The above configuration sets the FieldServer to use a specified PEM file to allow custom server connections. The authority file is a collection of server certificates in PEM format. This file can be edited using any text file editor (such as notepad). When the file has all required certificates, paste it into the PEM formatted server certificate. Now the FieldServer will connect to a server if it can find the server s certificate in the authority file. NOTE: Cert_Authority_File is useful only if Validate_Client_Cert is set to Yes. To upload the Certificate to the FieldServer follow the directions for the authority file in Appendix A Appendix A Certificate Validation Options Use the Check_Remote_Host element as described in Appendix A Appendix A Set up Client Certificate Make sure the certificate is in PEM format. Otherwise, convert it to PEM format (reference the link below). support.ssl.com/knowledgebase/article Configure the FieldServer to use a custom certificate as shown below:, Client_Cert_File, my_client_cert.pem Page 37 of 66

38 Appendix B Troubleshooting Tips Appendix B.1. Communicating with the ProtoAir over the Network Confirm that the network cabling is correct. Confirm that the computer network card is operational and correctly configured. Confirm that there is an Ethernet adapter installed in the PC s Device Manager List, and that it is configured to run the Modbus TCP/IP protocol. Check that the IP netmask of the PC matches the ProtoAir. The Default IP Address of the ProtoAir is , Subnet Mask is o o o Go to Start Run Type in ipconfig The account settings should be displayed. o Ensure that the IP Address is X and the netmask Ensure that the PC and ProtoAir are on the same IP Network, or assign a Static IP Address to the PC on the X network. Page 38 of 66

39 Appendix B.2. Lost or Incorrect IP Address Ensure that FieldServer Toolbox is loaded onto the local PC. Otherwise, download the FieldServer-Toolbox.zip via the Sierra Monitor Resource Center Software Downloads. Extract the executable file and complete the installation. Ethernet Port Figure 43: Ethernet Port Location Connect a standard CAT5 Ethernet cable between the user s PC and ProtoAir. Double click on the FS Toolbox Utility and click Discover Now on the splash page. Check for the IP Address of the desired gateway. If correcting the IP Address of the gateway: click the settings icon on the same row as the gateway, then click Network Settings, change the IP Address and click Update IP Settings to save. Page 39 of 66

40 Appendix B.3. Viewing Diagnostic information Type the IP Address of the ProtoAir into the web browser or use the FieldServer Toolbox to connect to the ProtoAir. Click on Diagnostics and Debugging Button, then click on view, and then on connections. If there are any errors showing on the Connection page, refer to Appendix B.4 for the relevant wiring and settings. Figure 44: Error Messages Screen Appendix B.4. Checking Wiring and Settings No COMS on Greengate, ilumin or Fifth Light side. Check the following: Check Greengate, ilumin or Fifth Light IP Address Check Ethernet switch and cable Check Ethernet LEDs (Appendix B.5) Verify device is connected to the same subnet as the ProtoAir No COMS on the Ethernet protocol. To fix this, check the following: Visual observations of LEDs on the ProtoAir (Appendix B.5) Check device address Verify wiring Verify device is connected to the same subnet as the ProtoAir Verify IP Address setting NOTE: If the problem still exists, a Diagnostic Capture needs to be taken and sent to support. (Appendix B.6) Page 40 of 66

41 Appendix B.5. LED Diagnostics for Communications Between ProtoAir and Devices See the diagram below for LED locations to ProtoAir. Diagnostic LEDs Tag Description SS The SPL LED will light if the unit is not getting a response from one or more of the configured devices. The SYS ERR LED will go on solid 15 seconds after power up. It will turn off after 5 seconds. A steady ERR red light will indicate there is a system error on unit. If this occurs, immediately report the related system error shown in the error screen of the FS-GUI interface to support for evaluation. PWR This is the power light and should show steady green at all times when the unit is powered. The TX LED will flash when a message is received on the serial port on the 3-pin connector. TX If the serial port is not used, this LED is non-operational. The RX LED will flash when a message is sent on the serial port on the 3-pin connector. RX If the serial port is not used, this LED is non-operational. Figure 45: Diagnostic LEDs Appendix B.6. Before Contacting Technical Support take a Diagnostic Capture When a problem occurs that cannot be resolved with regular troubleshooting, take a log via the FieldServer Toolbox. Send this log together with a detailed description of the problem to Controltechsupport@eaton.com for evaluation. The Diagnostic Capture will allow us to rapidly diagnose the problem. NOTE: While all necessary documentation is shipped with the FieldServer on the USB flash drive, these documents are constantly being updated. Newer versions may be available on the Sierra Monitor website Resource Center. Ensure that FieldServer Toolbox is loaded onto the local PC. Otherwise, download the FieldServer-Toolbox.zip via the Sierra Monitor Resource Center Software Downloads. Extract the executable file and complete the installation. Ethernet Port Figure 46: Ethernet Port Location Page 41 of 66

42 Connect a standard CAT5 Ethernet cable between the PC and ProtoAir. Double click on the FS Toolbox Utility. Step 1: Take a Log o Click on the diagnose icon of the desired device o Ensure Full Diagnostic" is selected (this is the default) NOTE: If desired, the default capture period can be changed. Page 42 of 66

43 o Click on Start Diagnostic o When the capture period is finished, the Diagnostic Test Complete window will appear Step 2: Send Log o Once the diagnostic test is complete, a.zip file will be saved on the PC o o Click Open to launch explorer and have it point directly at the correct folder the diagnostic zip file to Controltechsupport@eaton.com Page 43 of 66

44 Appendix B.7. Updating Firmware To load a new version of the firmware, follow these instructions: 1. Extract and save the new file onto the local PC. 2. Open a web browser and type the IP Address of the FieldServer in the address bar. NOTE: Default IP Address is NOTE: Use the FS Toolbox utility if the IP Address is unknown (Appendix B.2). 3. Click on the Diagnostics & Debugging button. 4. In the Navigation Tree on the left-hand side, do the following: a. Click on Setup b. Click on File Transfer c. Click on the Firmware tab 5. In the Firmware tab, click on Choose Files and select the firmware file extracted in step Click on the orange Submit button. 7. When the download is complete, click on the System Restart button. Appendix B.8. BACnet: Setting Network_Number for more than one ProtoAir on Subnet For both BACnet MS/TP and BACnet/IP, if more than one ProtoAir is connected to the same subnet, they must be assigned unique Network_Number values. On the main Web Configuration screen, update the BACnet Network Number field and click submit. The default value is Figure 47: Web Configurator Network Number Field Page 44 of 66

45 Appendix B.9. Securing ProtoAir with Passwords Access to the ProtoAir can be restricted by enabling a password on the FS-GUI Passwords page click Setup and then Passwords in the navigation panel. There are 2 access levels defined by 2 account names: Admin and User. The Admin account has unrestricted access to the ProtoAir. The User account can view any ProtoAir information, but cannot make any changes or restart the ProtoAir. The password needs to be a minimum of eight characters and is case sensitive. If the password is lost, click cancel on the password authentication popup window, and the password recovery token to Controltechsupport@eaton.com to receive a temporary password from the customer support team. Access the ProtoAir to set a new password. Figure 48: FS-GUI Passwords Page Figure 49: Password Recovery Page Page 45 of 66

46 Appendix B.10. Mounting The ProtoAir can be mounted using the DIN rail mounting bracket on the back of the unit. Din Rail Bracket Figure 50: DIN Rail Page 46 of 66

47 Appendix B.11. Physical Dimensions for FPA-W34 Power Port P1 Serial Port Figure 51: ProtoAir FPA-W34 Dimensions Page 47 of 66

48 Appendix B.12. Kaspersky Endpoint Security 10 If Kaspersky Endpoint Security 10 is installed on the user s PC, the software needs to be modified to allow the PC to register bridges on FieldPoP. NOTE: This problem is specific to KES10, Kaspersky 2017 does not have this problem. To fix the problem, the ProtoAir ( in Figure 31) must be set as a trusted URL to the "Web Anti-Virus"->"Settings" as shown below. Figure 52: Kaspersky ES10 Settings Figure 53: Web Anti-Virus Trusted URLs Page 48 of 66

49 Appendix C Vendor Information Eaton Appendix C Greengate Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register Reset BV Relay01 BV 1 1 Relay02 BV 2 2 Relay03 BV 3 3 Relay04 BV 4 4 Relay05 BV 5 5 Relay06 BV 6 6 Relay07 BV 7 7 Relay08 BV 8 8 Relay09 BV 9 9 Relay010 BV Relay011 BV Relay012 BV Relay013 BV Relay014 BV Relay015 BV Relay016 BV Relay017 BV Relay018 BV Relay019 BV Relay020 BV Relay021 BV Relay022 BV Relay023 BV Relay024 BV Relay025 BV Relay026 BV Relay027 BV Relay028 BV Relay029 BV Relay030 BV Relay031 BV Relay032 BV Remote01 BV Remote02 BV Remote03 BV Remote04 BV Remote05 BV Remote06 BV Remote07 BV Remote08 BV Remote09 BV Remote010 BV Remote011 BV Remote012 BV Remote013 BV Remote014 BV Remote015 BV Remote016 BV Remote017 BV Remote018 BV Remote019 BV Remote020 BV Remote021 BV Remote022 BV Remote023 BV Remote024 BV Remote025 BV Remote026 BV Remote027 BV Remote028 BV Remote029 BV Page 49 of 66

50 Remote030 BV Remote031 BV Remote032 BV Remote033 BV Remote034 BV Remote035 BV Remote036 BV Remote037 BV Remote038 BV Remote039 BV Remote040 BV Remote041 BV Remote042 BV Remote043 BV Remote044 BV Remote045 BV Remote046 BV Remote047 BV Remote048 BV Remote049 BV Remote050 BV Remote051 BV Remote052 BV Remote053 BV Remote054 BV Remote055 BV Remote056 BV Remote057 BV Remote058 BV Remote059 BV Remote060 BV Remote061 BV Remote062 BV Remote063 BV Remote064 BV Switch01 BI Switch02 BI Switch03 BI Switch04 BI Switch05 BI Switch06 BI Switch07 BI Switch08 BI Switch09 BI Switch010 BI Switch011 BI Switch012 BI Switch013 BI Switch014 BI Switch015 BI Switch016 BI Switch017 BI Switch018 BI Switch019 BI Switch020 BI Switch021 BI Switch022 BI Switch023 BI Switch024 BI Switch025 BI Switch026 BI Switch027 BI Switch028 BI Switch029 BI Switch030 BI Switch031 BI Switch032 BI Switch033 BI Switch034 BI Page 50 of 66

51 Switch035 BI Switch036 BI Switch037 BI Switch038 BI Switch039 BI Switch040 BI Switch041 BI Switch042 BI Switch043 BI Switch044 BI Switch045 BI Switch046 BI Switch047 BI Switch048 BI Switch049 BI Switch050 BI Switch051 BI Switch052 BI Switch053 BI Switch054 BI Switch055 BI Switch056 BI Switch057 BI Switch058 BI Switch059 BI Switch060 BI Switch061 BI Switch062 BI Switch063 BI Switch064 BI Appendix C Greengate Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register Reset BV Relay01 BV 1 1 Relay02 BV 2 2 Relay03 BV 3 3 Relay04 BV 4 4 Relay05 BV 5 5 Relay06 BV 6 6 Relay07 BV 7 7 Relay08 BV 8 8 Relay09 BV 9 9 Relay010 BV Relay011 BV Relay012 BV Relay013 BV Relay014 BV Relay015 BV Relay016 BV Relay017 BV Relay018 BV Relay019 BV Relay020 BV Relay021 BV Relay022 BV Relay023 BV Relay024 BV Relay025 BV Relay026 BV Relay027 BV Relay028 BV Relay029 BV Relay030 BV Relay031 BV Relay032 BV Page 51 of 66

52 Relay033 BV Relay034 BV Relay035 BV Relay036 BV Relay037 BV Relay038 BV Relay039 BV Relay040 BV Relay041 BV Relay042 BV Relay043 BV Relay044 BV Relay045 BV Relay046 BV Relay047 BV Relay048 BV Remote01 BV Remote02 BV Remote03 BV Remote04 BV Remote05 BV Remote06 BV Remote07 BV Remote08 BV Remote09 BV Remote010 BV Remote011 BV Remote012 BV Remote013 BV Remote014 BV Remote015 BV Remote016 BV Remote017 BV Remote018 BV Remote019 BV Remote020 BV Remote021 BV Remote022 BV Remote023 BV Remote024 BV Remote025 BV Remote026 BV Remote027 BV Remote028 BV Remote029 BV Remote030 BV Remote031 BV Remote032 BV Remote033 BV Remote034 BV Remote035 BV Remote036 BV Remote037 BV Remote038 BV Remote039 BV Remote040 BV Remote041 BV Remote042 BV Remote043 BV Remote044 BV Remote045 BV Remote046 BV Remote047 BV Remote048 BV Remote049 BV Remote050 BV Remote051 BV Remote052 BV Remote053 BV Page 52 of 66

53 Remote054 BV Remote055 BV Remote056 BV Remote057 BV Remote058 BV Remote059 BV Remote060 BV Remote061 BV Remote062 BV Remote063 BV Remote064 BV Switch01 BI Switch02 BI Switch03 BI Switch04 BI Switch05 BI Switch06 BI Switch07 BI Switch08 BI Switch09 BI Switch010 BI Switch011 BI Switch012 BI Switch013 BI Switch014 BI Switch015 BI Switch016 BI Switch017 BI Switch018 BI Switch019 BI Switch020 BI Switch021 BI Switch022 BI Switch023 BI Switch024 BI Switch025 BI Switch026 BI Switch027 BI Switch028 BI Switch029 BI Switch030 BI Switch031 BI Switch032 BI Switch033 BI Switch034 BI Switch035 BI Switch036 BI Switch037 BI Switch038 BI Switch039 BI Switch040 BI Switch041 BI Switch042 BI Switch043 BI Switch044 BI Switch045 BI Switch046 BI Switch047 BI Switch048 BI Switch049 BI Switch050 BI Switch051 BI Switch052 BI Switch053 BI Switch054 BI Switch055 BI Switch056 BI Switch057 BI Switch058 BI Page 53 of 66

54 Switch059 BI Switch060 BI Switch061 BI Switch062 BI Switch063 BI Switch064 BI AI_State01 BI AI_State02 BI AI_State03 BI AI_State04 BI AI_State05 BI AI_State06 BI AI_State07 BI AI_State08 BI AI_State09 BI AI_State010 BI AI_State011 BI AI_State012 BI AI_State013 BI AI_State014 BI AI_State015 BI AI_State016 BI AI_State017 BI AI_State018 BI AI_State019 BI AI_State020 BI AI_State021 BI AI_State022 BI AI_State023 BI AI_State024 BI AI_State025 BI AI_State026 BI AI_State027 BI AI_State028 BI AI_State029 BI AI_State030 BI AI_State031 BI AI_State032 BI AI01 AI AI02 AI AI03 AI AI04 AI Appendix C Greengate Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register Reset BV Relay01 BV 1 1 Relay02 BV 2 2 Relay03 BV 3 3 Relay04 BV 4 4 Relay05 BV 5 5 Relay06 BV 6 6 Relay07 BV 7 7 Relay08 BV 8 8 Remote01 BV Remote02 BV Remote03 BV Remote04 BV Remote05 BV Remote06 BV Remote07 BV Remote08 BV Remote09 BV Page 54 of 66

55 Remote010 BV Remote011 BV Remote012 BV Remote013 BV Remote014 BV Remote015 BV Remote016 BV Remote017 BV Remote018 BV Remote019 BV Remote020 BV Remote021 BV Remote022 BV Remote023 BV Remote024 BV Remote025 BV Remote026 BV Remote027 BV Remote028 BV Remote029 BV Remote030 BV Remote031 BV Remote032 BV Remote033 BV Remote034 BV Remote035 BV Remote036 BV Remote037 BV Remote038 BV Remote039 BV Remote040 BV Remote041 BV Remote042 BV Remote043 BV Remote044 BV Remote045 BV Remote046 BV Remote047 BV Remote048 BV Remote049 BV Remote050 BV Remote051 BV Remote052 BV Remote053 BV Remote054 BV Remote055 BV Remote056 BV Remote057 BV Remote058 BV Remote059 BV Remote060 BV Remote061 BV Remote062 BV Remote063 BV Remote064 BV Switch01 BI Switch02 BI Switch03 BI Switch04 BI Switch05 BI Switch06 BI Switch07 BI Switch08 BI Page 55 of 66

56 Appendix C Greengate Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register Reset BV Relay01 BV 1 1 Relay02 BV 2 2 Relay03 BV 3 3 Remote01 BV Remote02 BV Remote03 BV Remote04 BV Remote05 BV Remote06 BV Remote07 BV Remote08 BV Remote09 BV Remote010 BV Remote011 BV Remote012 BV Remote013 BV Remote014 BV Remote015 BV Remote016 BV Remote017 BV Remote018 BV Remote019 BV Remote020 BV Remote021 BV Remote022 BV Remote023 BV Remote024 BV Remote025 BV Remote026 BV Remote027 BV Remote028 BV Remote029 BV Remote030 BV Remote031 BV Remote032 BV Remote033 BV Remote034 BV Remote035 BV Remote036 BV Remote037 BV Remote038 BV Remote039 BV Remote040 BV Remote041 BV Remote042 BV Remote043 BV Remote044 BV Remote045 BV Remote046 BV Remote047 BV Remote048 BV Remote049 BV Remote050 BV Remote051 BV Remote052 BV Remote053 BV Remote054 BV Remote055 BV Remote056 BV Remote057 BV Remote058 BV Remote059 BV Remote060 BV Page 56 of 66

57 Remote061 BV Remote062 BV Remote063 BV Remote064 BV Switch01 BI Switch02 BI Switch03 BI Switch04 BI Switch05 BI Switch06 BI Switch07 BI Switch08 BI Switch09 BI Switch010 BI Switch011 BI Switch012 BI Switch013 BI Switch014 BI Switch015 BI Switch016 BI Switch017 BI Switch018 BI Switch019 BI Switch020 BI Switch021 BI Switch022 BI Switch023 BI Switch024 BI Switch025 BI Switch026 BI Switch027 BI Switch028 BI Switch029 BI Switch030 BI Switch031 BI Switch032 BI Switch033 BI Switch034 BI Switch035 BI Switch036 BI Switch037 BI Switch038 BI Switch039 BI Switch040 BI Switch041 BI Switch042 BI Switch043 BI Switch044 BI AI01 AI AI02 AI AI03 AI Appendix C Greengate Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register Reset BV Relay01 BV 1 1 Relay02 BV 2 2 Relay03 BV 3 3 Relay04 BV 4 4 Relay05 BV 5 5 Relay06 BV 6 6 Relay07 BV 7 7 Relay08 BV 8 8 Relay09 BV 9 9 Page 57 of 66

58 Relay010 BV Relay011 BV Relay012 BV Relay013 BV Relay014 BV Relay015 BV Relay016 BV Remote01 BV Remote02 BV Remote03 BV Remote04 BV Remote05 BV Remote06 BV Remote07 BV Remote08 BV Remote09 BV Remote010 BV Remote011 BV Remote012 BV Remote013 BV Remote014 BV Remote015 BV Remote016 BV Remote017 BV Remote018 BV Remote019 BV Remote020 BV Remote021 BV Remote022 BV Remote023 BV Remote024 BV Remote025 BV Remote026 BV Remote027 BV Remote028 BV Remote029 BV Remote030 BV Remote031 BV Remote032 BV Remote033 BV Remote034 BV Remote035 BV Remote036 BV Remote037 BV Remote038 BV Remote039 BV Remote040 BV Remote041 BV Remote042 BV Remote043 BV Remote044 BV Remote045 BV Remote046 BV Remote047 BV Remote048 BV Remote049 BV Remote050 BV Remote051 BV Remote052 BV Remote053 BV Remote054 BV Remote055 BV Remote056 BV Remote057 BV Remote058 BV Remote059 BV Remote060 BV Remote061 BV Remote062 BV Page 58 of 66

59 Remote063 BV Remote064 BV Switch01 BI Switch02 BI Switch03 BI Switch04 BI Switch05 BI Switch06 BI Switch07 BI Switch08 BI Switch09 BI Switch010 BI Switch011 BI Switch012 BI Switch013 BI Switch014 BI Switch015 BI Switch016 BI Switch017 BI Switch018 BI Switch019 BI Switch020 BI Switch021 BI Switch022 BI Switch023 BI Switch024 BI Switch025 BI Switch026 BI Switch027 BI Switch028 BI Switch029 BI Switch030 BI Switch031 BI Switch032 BI Switch033 BI Switch034 BI Switch035 BI Switch036 BI Switch037 BI Switch038 BI Switch039 BI Switch040 BI Switch041 BI Switch042 BI Switch043 BI Switch044 BI Switch045 BI Switch046 BI Switch047 BI Switch048 BI Switch049 BI Switch050 BI Switch051 BI Switch052 BI Switch053 BI Switch054 BI Switch055 BI Switch056 BI Switch057 BI Switch058 BI Switch059 BI Switch060 BI Switch061 BI Switch062 BI Switch063 BI Switch064 BI AI_State01 BI AI_State02 BI Page 59 of 66

60 AI_State03 BI AI_State04 BI AI_State05 BI AI_State06 BI AI_State07 BI AI_State08 BI AI_State09 BI AI_State010 BI AI_State011 BI AI_State012 BI AI_State013 BI AI_State014 BI AI_State015 BI AI_State016 BI AI_State017 BI AI_State018 BI AI_State019 BI AI_State020 BI AI_State021 BI AI_State022 BI AI_State023 BI AI_State024 BI AI_State025 BI AI_State026 BI AI_State027 BI AI_State028 BI AI_State029 BI AI_State030 BI AI_State031 BI AI_State032 BI AI01 AI AI02 AI AI03 AI AI04 AI Appendix C Greengate Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register Reset BV Relay01 BV 1 1 Relay02 BV 2 2 Relay03 BV 3 3 Relay04 BV 4 4 Relay05 BV 5 5 Relay06 BV 6 6 Relay07 BV 7 7 Relay08 BV 8 8 Relay09 BV 9 9 Relay010 BV Relay011 BV Relay012 BV Relay013 BV Relay014 BV Relay015 BV Relay016 BV Relay017 BV Relay018 BV Relay019 BV Relay020 BV Relay021 BV Relay022 BV Relay023 BV Relay024 BV Relay025 BV Relay026 BV Relay027 BV Page 60 of 66

61 Relay028 BV Relay029 BV Relay030 BV Relay031 BV Relay032 BV Relay033 BV Relay034 BV Relay035 BV Relay036 BV Relay037 BV Relay038 BV Relay039 BV Relay040 BV Relay041 BV Relay042 BV Relay043 BV Relay044 BV Relay045 BV Relay046 BV Relay047 BV Relay048 BV Relay049 BV Relay050 BV Relay051 BV Relay052 BV Relay053 BV Relay054 BV Relay055 BV Relay056 BV Relay057 BV Relay058 BV Relay059 BV Relay060 BV Relay061 BV Relay062 BV Relay063 BV Relay064 BV Remote01 BV Remote02 BV Remote03 BV Remote04 BV Remote05 BV Remote06 BV Remote07 BV Remote08 BV Remote09 BV Remote010 BV Remote011 BV Remote012 BV Remote013 BV Remote014 BV Remote015 BV Remote016 BV Remote017 BV Remote018 BV Remote019 BV Remote020 BV Remote021 BV Remote022 BV Remote023 BV Remote024 BV Remote025 BV Remote026 BV Remote027 BV Remote028 BV Remote029 BV Remote030 BV Remote031 BV Remote032 BV Page 61 of 66

62 Remote033 BV Remote034 BV Remote035 BV Remote036 BV Remote037 BV Remote038 BV Remote039 BV Remote040 BV Remote041 BV Remote042 BV Remote043 BV Remote044 BV Remote045 BV Remote046 BV Remote047 BV Remote048 BV Remote049 BV Remote050 BV Remote051 BV Remote052 BV Remote053 BV Remote054 BV Remote055 BV Remote056 BV Remote057 BV Remote058 BV Remote059 BV Remote060 BV Remote061 BV Remote062 BV Remote063 BV Remote064 BV Switch01 BI Switch02 BI Switch03 BI Switch04 BI Switch05 BI Switch06 BI Switch07 BI Switch08 BI Switch09 BI Switch010 BI Switch011 BI Switch012 BI Switch013 BI Switch014 BI Switch015 BI Switch016 BI Switch017 BI Switch018 BI Switch019 BI Switch020 BI Switch021 BI Switch022 BI Switch023 BI Switch024 BI Switch025 BI Switch026 BI Switch027 BI Switch028 BI Switch029 BI Switch030 BI Switch031 BI Switch032 BI Switch033 BI Switch034 BI Switch035 BI Switch036 BI Switch037 BI Page 62 of 66

63 Switch038 BI Switch039 BI Switch040 BI Switch041 BI Switch042 BI Switch043 BI Switch044 BI Switch045 BI Switch046 BI Switch047 BI Switch048 BI Switch049 BI Switch050 BI Switch051 BI Switch052 BI Switch053 BI Switch054 BI Switch055 BI Switch056 BI Switch057 BI Switch058 BI Switch059 BI Switch060 BI Switch061 BI Switch062 BI Switch063 BI Switch064 BI AI_State01 BI AI_State02 BI AI_State03 BI AI_State04 BI AI_State05 BI AI_State06 BI AI_State07 BI AI_State08 BI AI_State09 BI AI_State010 BI AI_State011 BI AI_State012 BI AI_State013 BI AI_State014 BI AI_State015 BI AI_State016 BI AI_State017 BI AI_State018 BI AI_State019 BI AI_State020 BI AI_State021 BI AI_State022 BI AI_State023 BI AI_State024 BI AI_State025 BI AI_State026 BI AI_State027 BI AI_State028 BI AI_State029 BI AI_State030 BI AI_State031 BI AI_State032 BI Page 63 of 66

64 Appendix C.7. Scene ilumin Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register scene AO sceneft AO Appendix C.8. Channel ilumin Mappings to BACnet and Modbus Point Name BACnet Object Type BACnet Object ID Modbus Register channel AO channelft AO Page 64 of 66

65 Appendix D Reference Appendix D.1. Specifications0F2 Electrical Connections Power Requirements Approvals Power Requirements Physical Dimensions Weight Operating Temperature Humidity ProtoAir FPA-W34 One 3-pin Phoenix connector with: RS-485 (Tx+ / Rx- / gnd) One 3-pin Phoenix connector with: Power port (+ / - / Frame-gnd) One Ethernet 10/100 BaseT port Input Voltage: 12-24V DC Current 12V, 240 ma Power Rating: 2.5 Watts CE and FCC Class B & C Part 15, TUV approved to UL pending, IC Canada, RoHS Compliant, PTCRB and CTIA 12-24V DC 4 x 1.1 x 2.7 in (10.16 x 2.8 x 6.8 cm) 0.4 lbs (0.2 Kg) -20 C to 70 C (-4 F to158 F) 10-95% RH non-condensing Figure 54: Specifications Appendix D.1.1. Compliance with UL Regulations For UL compliance, the following instructions must be met when operating ProtoAir. The units shall be powered by listed LPS or Class 2 power supply suited to the expected operating temperature range. The interconnecting power connector and power cable shall: o Comply with local electrical code o Be suited to the expected operating temperature range o Meet the current and voltage rating for ProtoAir Furthermore, the interconnecting power cable shall: o Be of length not exceeding 3.05m (118.3 ) o Be constructed of materials rated VW-1, FT-1 or better If the unit is to be installed in an operating environment with a temperature above 65 C, it should be installed in a Restricted Access Area requiring a key or a special tool to gain access. This device must not be connected to a LAN segment with outdoor wiring. 2 Specifications subject to change without notice Page 65 of 66