ProtoAir FPA-W34 Start-up Guide For Interfacing the ... · The ProtoAir wireless gateway is an external, high performance building automation multi-protocol gateway that is preconfigured

Document Revision: 1.B Web Configurator

Template Revision: 2

ProtoAir FPA-W34 Start-up Guide

For Interfacing the Siemens MAG6000

To Building Automation Systems: BACnet/IP, Modbus TCP/IP and EtherNet/IP

APPLICABILITY & EFFECTIVITY

Explains ProtoAir hardware and installation.

The instructions are effective for the above as of June 2018.

Siemens ProtoAir Start-up Guide

Page 2 of 43

Technical Support

Thank you for purchasing the ProtoAir for Siemens. Please call Siemens for technical support of the ProtoAir product. Sierra Monitor Corporation does not provide direct support. If Siemens needs to escalate the concern, they will contact Sierra Monitor Corporation for assistance. Support Contact Information:

Siemens Industry, Inc. 2060 Detwiler Road, Suite 111 Harleysville, PA 19438 Customer Service: Toll Free (800) 333-7421 Outside US (423) 262-5710

Website: www.usa.siemens.com/eip-gateway

For Support Online: create a support request via usa.siemens.com/support -request

https://support.industry.siemens.com/My/us/en/requests#createRequest

http://www.usa.siemens.com

http://www.usa.siemens.com/eip-gateway


Page 3 of 43

Quick Start Guide

1. Record the information about the unit. (Section 3.1)

2. Set COM settings for the devices that will be connected to ProtoAir. (Section 3.3)

3. Connect Power to ProtoAir’s 3 pin connector. (Section 4)

4. Connect a PC to the ProtoAir via Ethernet cable or connect using Wi-Fi access point to ensure the PC is on 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)

5. Use a web browser to access the ProtoAir Web Configurator page to select the profiles of the devices attached to the ProtoAir and enter the IP Address of each device. Once the devices are selected, the ProtoAir automatically builds and loads the appropriate configuration. (Section 6)


Page 4 of 43

TABLE OF CONTENTS

1 Certification .......................................................................................................................................... 6 1.1 BTL Mark – BACnet® Testing Laboratory ....................................................................................... 6

2 Introduction .......................................................................................................................................... 7 2.1 ProtoAir Gateway ............................................................................................................................ 7

3 ProtoAir Setup ...................................................................................................................................... 8 3.1 Record Identification Data .............................................................................................................. 8 3.2 Point Count Capacity and Registers per Device ............................................................................ 8 3.3 Configuring Device Communications ............................................................................................. 9

3.3.1 Input COM Settings on the Device Connected to the ProtoAir ................................................. 9 3.3.2 Set Node-ID for the Device Attached to the ProtoAir ................................................................ 9 3.3.3 BACnet: Calculating the Default Device Instance ..................................................................... 9

3.4 Attaching the Antenna .................................................................................................................... 9

4 Interfacing ProtoAir to Devices ........................................................................................................ 10 4.1 Device Connections to ProtoAir .................................................................................................... 10

4.1.1 Bias Resistor DIP Switches ..................................................................................................... 11 4.1.2 Termination Resistor ............................................................................................................... 12

4.2 Power-Up ProtoAir ........................................................................................................................ 13

5 Connect the PC to the ProtoAir over Ethernet or Wi-Fi ................................................................. 14 5.1 Connecting to the ProtoAir via Ethernet ....................................................................................... 14

5.1.1 Changing the Subnet of the Connected PC ............................................................................ 14 5.1.2 Changing the IP Address of the ProtoAir with FieldServer Toolbox ....................................... 15

5.2 Connecting to the ProtoAir via Wi-Fi Access Point ...................................................................... 16 5.3 Updating Network Settings ........................................................................................................... 17

5.3.1 Navigate to the FS-GUI Network Settings .............................................................................. 17 5.3.2 IP Settings ............................................................................................................................... 19 5.3.3 Wi-Fi Client Settings ................................................................................................................ 20 5.3.4 Wi-Fi AP – Access Point Settings ........................................................................................... 21 5.3.5 Common Settings .................................................................................................................... 22

6 Configure the ProtoAir ...................................................................................................................... 23

7 BACnet: Setting Node_Offset to Assign Specific Device Instances ........................................... 25

8 How to Start the Installation Over: Clearing Profiles ..................................................................... 26

Appendix A. Troubleshooting .................................................................................................................. 27 Appendix A.1. Lost or Incorrect IP Address ............................................................................................ 27 Appendix A.2. Viewing Diagnostic Information ....................................................................................... 28 Appendix A.3. Checking Wiring and Settings .......................................................................................... 29 Appendix A.4. LED Diagnostics for Communications Between ProtoAir and Devices ........................... 30 Appendix A.5. Taking Diagnostic Capture with the FieldServer Toolbox ................................................ 30 Appendix A.6. Take a Diagnostic Capture via FS-GUI ........................................................................... 33 Appendix A.7. Wi-Fi Signal Strength ....................................................................................................... 34

Appendix B. Additional Information ........................................................................................................ 35 Appendix B.1. Updating Firmware ........................................................................................................... 35 Appendix B.2. BACnet: Setting Network_Number for more than one ProtoAir on Subnet ..................... 35 Appendix B.3. Securing ProtoAir with Passwords ................................................................................... 36 Appendix B.4. Mounting .......................................................................................................................... 37 Appendix B.5. Physical Dimension Drawings ......................................................................................... 38

Appendix C. Vendor Information – Siemens .......................................................................................... 39 Appendix C.1. MAG6000 Modbus RTU Mappings to BACnet/IP and EtherNet/IP ................................. 39

Appendix D. Reference ............................................................................................................................. 42 Appendix D.1. Specifications ................................................................................................................... 42

Appendix D.1.1. Compliance with UL Regulations .............................................................................. 42

Appendix E. Limited 2 Year Warranty ..................................................................................................... 43


Page 5 of 43

LIST OF FIGURES

Figure 1: ProtoAir Part Numbers ................................................................................................................... 8 Figure 2: Supported Point Count Capacity ................................................................................................... 8 Figure 3: Registers per Device ..................................................................................................................... 8 Figure 4: COM Settings ................................................................................................................................. 9 Figure 5: RS-485 Connections to the FieldServer ...................................................................................... 10 Figure 6: MAG6000 RS-485 Wiring Setup .................................................................................................. 10 Figure 7: Bias Resistors .............................................................................................................................. 11 Figure 8: Termination Resistor .................................................................................................................... 12 Figure 9: Required Current Draw for the ProtoAir....................................................................................... 13 Figure 10: Power Connections .................................................................................................................... 13 Figure 11: Ethernet Port Location ............................................................................................................... 14 Figure 12: Web Configurator Landing Page ............................................................................................... 17 Figure 13: FS-GUI Landing Page ............................................................................................................... 17 Figure 14: Generic FS-GUI Navigation Panel – Network Settings ............................................................. 18 Figure 15: FS-GUI Ethernet Port Network Settings .................................................................................... 19 Figure 16: FS-GUI Wi-Fi Client Network Settings ....................................................................................... 20 Figure 17: FS-GUI Wi-Fi AP Network Settings ........................................................................................... 21 Figure 18: FS-GUI Common Network Settings ........................................................................................... 22 Figure 19: Web Configurator Screen Showing no Active Profiles .............................................................. 23 Figure 20: Web Configurator Showing Active Profile Additions .................................................................. 24 Figure 21: Web Configurator Node Offset Field.......................................................................................... 25 Figure 22: Active Profiles ............................................................................................................................ 25 Figure 23: Ethernet Port Location ............................................................................................................... 27 Figure 24: Error Messages Screen ............................................................................................................. 28 Figure 25: Diagnostic LEDs ........................................................................................................................ 30 Figure 26: Ethernet Port Location ............................................................................................................... 30 Figure 27: Wi-Fi Signal Strength Listing ..................................................................................................... 34 Figure 28: Web Configurator – Network Number Field ............................................................................... 35 Figure 29: FS-GUI Passwords Page ........................................................................................................... 36 Figure 30: Password Recovery Page ......................................................................................................... 36 Figure 31: DIN Rail ...................................................................................................................................... 37 Figure 32: ProtoAir FPA-W34 Dimensions ................................................................................................. 38 Figure 33: Specifications ............................................................................................................................. 42


Page 6 of 43

1 CERTIFICATION

1.1 BTL Mark – BACnet®1 Testing Laboratory

1 BACnet is a registered trademark of ASHRAE

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 www.BACnetInternational.net for more information about the BACnet Testing Laboratory. Click here for the BACnet PIC Statement.

http://www.bacnetinternational.net/btl/

https://www.sierramonitor.com/sites/default/files/SMC/Documents/Datasheets/Protocols/PDS_BACnet_PIC_Statement.pdf


Page 7 of 43

2 INTRODUCTION

2.1 ProtoAir Gateway

The ProtoAir wireless gateway is an external, high performance building automation multi-protocol

gateway that is preconfigured to auto-discover any of Siemens’ products (hereafter called “device”)

connected to the ProtoAir and automatically configures them for BACnet/IP, Modbus TCP/IP and EtherNet/IP.

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 8 of 43

3 PROTOAIR SETUP

3.1 Record Identif ication 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 Part Number

ProtoAir FPA-W34-1673 Figure 1: ProtoAir Part Numbers

• ProtoAir units have the following 2 ports: RS-485 + Ethernet

3.2 Point Count Capacity and Registers per Device

The total number of registers presented by all of the devices attached to the ProtoAir cannot exceed:

Part number Total Registers

FPA-W34-1673 1,500 Figure 2: Supported Point Count Capacity

Devices Registers Per Device

MAG6000 150 Figure 3: Registers per Device


Page 9 of 43

3.3 Configuring Device Communications

3.3.1 Input COM Settings on the Device Connected to the ProtoAir • The connected serial device MUST have the same baud rate, data bits, stop bits, and parity

settings as the ProtoAir.

• Figure 4 specifies the device serial port settings required to communicate with the ProtoAir.

Port Setting Devices

Protocol Modbus RTU Baud Rate 19200 Parity Even Data Bits 8 Stop Bits 1

Figure 4: COM Settings

NOTE: The COM parameters are adjustable.

3.3.2 Set Node-ID for the Device Attached to the ProtoAir • Set Node-ID for the device attached to ProtoAir to 1.

• Document the Node-ID that is assigned to the device. The Node-ID’s assigned are used for deriving the Device Instance for BACnet/IP. (Section 3.3.3)

NOTE: The Modbus TCP/IP field protocol Node-IDs are automatically set to be the same value as

the Node-ID of the device.

3.3.3 BACnet: Calculating the Default Device Instance • The Device Instance value is automatically generated using the following formula:

BACnet Device Instance = (Device Node-ID) + (Default Node Offset)

NOTE: The default Node Offset is 50,000.

For example, if Device A has a Node-ID of 1 then:

BACnet Device Instance A = (1) + (50000) = 50001

NOTE: The Node-ID is set in Section 3.3.2.

• To reach a specific BACnet Device Instance result, refer to Section 7.

3.4 Attaching the Antenna

Wi-Fi Antenna:

Screw in the Wi-Fi antenna to the front of the unit as shown in Figure 32.


Page 10 of 43

4 INTERFACING PROTOAIR TO DEVICES

4.1 Device Connections to ProtoAir

• Connect the RS-485 network wires to the 3-pin RS-485 connector on the ProtoAir. (Figure 5) o Use standard grounding principles for RS-485 GND

BMS Wiring

ProtoAir Pin #

Pin Assignment

RS-485 + Pin 1 RS-485 + RS-485 - Pin 2 RS-485 -

- Pin 3 RS-485 GND

Figure 5: RS-485 Connections to the FieldServer

G -

+

Figure 6: MAG6000 RS-485 Wiring Setup


Page 11 of 43

4.1.1 Bias Resistor DIP Switches

To enable Bias Resistors, move both the BIAS- and BIAS+ dip switches to the right.

The ProtoAir bias resistors are used to keep the RS-485 bus to a known state, when there is no transmission on the line (bus is idling), to help prevent false bits of data from being detected. The bias resistors typically pull one line high and the other low - far away from the decision point of the logic.

In the RS-485 carrier, the bias resistor is 510 ohms which is in line with the BACnet spec. It should only be enabled at one point on the bus (on the Brian field port were there are very weak bias resistors of 100k). Since there are no jumpers, many Brains can be put on network without running into the bias resistor limit which is < 500 ohms.

NOTE: See www.ni.com/support/serial/resinfo.htm for additional pictures and notes.

Bias Resistor DIP Switches (2 and 3)

Figure 7: Bias Resistors

http://www.ni.com/support/serial/resinfo.htm


Page 12 of 43

4.1.2 Termination Resistor

If the ProtoAir is the last device on the Serial trunk, then the End-Of-Line Termination Switch needs to be enabled. To enable the Termination Resistor, move the TERM dip switch to the right.

Termination resistor is also used to reduce noise. It pulls the two lines of an idle bus together. However, the resistor would override the effect of any bias resistors if connected.

Termination Resistor DIP Switch (1)

Figure 8: Termination Resistor


Page 13 of 43

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 9: Required Current Draw for the ProtoAir

Apply power to the ProtoAir as shown below in Figure 10. 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 10: Power Connections


Page 14 of 43

5 CONNECT THE PC TO THE PROTOAIR OVER ETHERNET OR WI-FI

5.1 Connecting to the ProtoAir via Ethernet

First, connect a CAT5 Ethernet cable (straight through or cross-over) between the local PC and ProtoAir.

There are two ways to access the ProtoAir via an Ethernet connection, either by changing the subnet of the connected PC or using the FieldServer Toolbox to change the IP Address of the ProtoAir.

5.1.1 Changing the Subnet of the Connected PC The default IP Address for the ProtoAir Ethernet connection is 192.168.1.24, Subnet Mask is 255.255.255.0. If the PC and ProtoAir are on different IP networks, assign a static IP Address to the PC on the 192.168.1.xxx network.

For Windows 10:

Right click on > >

> >

Right-click on Local Area Connection > Properties

Highlight >

Use the following IP Address:

Click twice.

Ethernet Port

Figure 11: Ethernet Port Location


Page 15 of 43

5.1.2 Changing the IP Address of the ProtoAir with FieldServer Toolbox

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

• Double click on the FS Toolbox Utility and click Discover Now on the splash page.

• Find the desired gateway and click the Configure Device button (gear icon) to the right of the gateway information.

• Select Network Settings in the Configure Device window.

• Modify the IP Address (N1 IP Address field) of the gateway Ethernet port. o The following fields may also be changed as needed: Netmask (N1 Netmask field), DHCP

Client State (N1 DHCP Client State field), IP Gateway (Default Gateway field) and DNS 1 & 2 (Domain Name Server fields)

NOTE: If the gateway is connected to a router, the Default Gateway field of the gateway should be

set to the IP Address of the connected router.

NOTE: Do not change the DHCP Server State (N1 DHCP Server State field).

NOTE: If DNS settings are unknown, set DNS1 to “8.8.8.8” and DNS2 to “8.8.4.4”.

• Click Update IP Settings, then click on the Change and Restart to restart the Gateway and activate the new IP Address.

http://www.sierramonitor.com/customer-care/resource-center?filters=software-downloads


Page 16 of 43

5.2 Connecting to the ProtoAir via Wi-Fi Access Point

When the ProtoAir is first powered up the Wi-Fi access point will be enabled allowing direct connection to the ProtoAir via Wi-Fi.

To connect to the ProtoAir Wi-Fi access point:

• Click the icon (found in the bottom-right corner of the computer screen) to open the available Wireless Network Connections.

• Select the desired ProtoAir and click Connect.

• Enter the Security key; the default is 12345678.

The available Wireless Network Connection menu should now show that the computer is connected to the ProtoAir.


Page 17 of 43

5.3 Updating Network Settings

5.3.1 Navigate to the FS-GUI Network Settings After setting a local PC on the same subnet as the ProtoAir (Section 5.1 or Section 5.2), open a web browser on the PC and enter the IP Address of the ProtoAir; the default Ethernet address is 192.168.1.24, the default Wi-Fi access point address is 192.168.50.1. Alternatively, the Web Configurator page can be accessed by clicking the Connect button in the FieldServer Toolbox (Section 5.1.2).

NOTE: If the IP Address of the ProtoAir was previously changed, the assigned IP Address can be

discovered using the FS Toolbox utility. See Appendix A.1 for instructions.

• From the Web Configurator landing page, click the “Diagnostics & Debugging” button to open the

FS-GUI page.

• Find the Navigation tree on the left side of the screen.

Figure 13: FS-GUI Landing Page

Figure 12: Web Configurator Landing Page


Page 18 of 43

• Click the orange arrow next to the ProtoAir CN number and title to expand the tree.

• Click on the orange arrow next to Setup to expand the tree.

• Click on Network Settings.

Figure 14: Generic FS-GUI Navigation Panel – Network Settings


Page 19 of 43

5.3.2 IP Settings IP Settings tab is the landing page when selecting Network Settings on the navigation tree.

To change the IP settings, follow these instructions:

• Enable DHCP Client State to automatically assign IP Settings or modify the settings manually as needed, via these fields: IP Address, Netmask, Default Gateway and Domain Name Server1/2.

NOTE: If the ProtoAir is connected to a router, the Default Gateway of the ProtoAir should be set

to the same IP Address of the router.

• Click Update IP Settings, then click on System Restart to restart the Gateway and activate the new IP Address.

NOTE: If the FS-GUI was open in a browser, the browser will need to be pointed to the new IP

Address of the ProtoAir before the FS-GUI will be accessible again.

IP Setting Fields Definition

Connection Status Status of connection MAC Address Ethernet MAC Address Tx/Rx Msgs Number of transmitted and received messages Tx/Rx Msgs Dropped Number of unanswered Tx or Rx messages

Figure 15: FS-GUI Ethernet Port Network Settings


Page 20 of 43

5.3.3 Wi-Fi Client Settings From the FS-GUI Network Settings landing page, click on the Wi-Fi Client tab.

To change the Wi-Fi client settings, follow these instructions:

• The Wi-Fi Status field must be set to ENABLED to allow the ProtoAir to communicate with other devices via Wi-Fi.

• Enable DHCP to automatically assign all Wi-Fi Client Settings fields or modify the Settings manually, via the fields immediately below the note (Wi-Fi SSID, Wi-Fi Password, IP Address, etc.).

NOTE: If the FieldServer is connected to a router, the IP gateway of the FieldServer should be set

to the same IP Address of the router.

• Click Update IP Settings, then click on the System Restart to restart the gateway and activate the new IP Address.

Wi-Fi Client Fields Definition

Connection Status Status of connection MAC Address, BSSID, Channel Wi-Fi Client MAC Address, BSSID, and Channel Tx/Rx Msgs Number of transmitted and received messages Tx/Rx Msgs Dropped Number of unanswered Tx or Rx messages Pairwise Cipher Type of encryption used for unicast traffic Group Cipher Identifies the type of encryption used for multicast / broadcast traffic Key Mgmt Encryption type Link Connection speed Signal Level Signal level in dBm

Figure 16: FS-GUI Wi-Fi Client Network Settings


Page 21 of 43

5.3.4 Wi-Fi AP – Access Point Settings From the FS-GUI Network Settings landing page, click on the Wi-Fi AP tab.

To change the Wi-Fi AP settings, follow these instructions:

• The Access Point Status Field must be ENABLED to allow connecting to the ProtoAir via Wi-Fi.

• Modify the Settings manually as needed, via these fields: Access Point SSID, Access Point Password, SSID Braodcast, and Channel.

NOTE: The default channel is 11.

• Click Update Wi-Fi Settings, then click on the System Restart to restart the Gateway and activate the Wi-Fi settings.

NOTE: If the FS-GUI was open in a browser via Wi-Fi, the browser will need to be updated with the

new Wi-Fi details before the ProtoAir FS-GUI will be accessible again.

Wi-Fi AP Fields Definition

Connection Status Status of connection MAC Address Access Point’s MAC Address Tx/Rx Msgs Number of transmitted and received messages Tx/Rx Msgs Dropped Number of unanswered Tx or Rx messages

Figure 17: FS-GUI Wi-Fi AP Network Settings


Page 22 of 43

5.3.5 Common Settings From the FS-GUI Network Settings landing page, click on the Common tab.

To change the primary connection when both Ethernet and Wi-Fi Client connections are available:

• Select the desired option from the drop-down menu on the right.

• Click Update Common Settings, then click on System Restart to restart the gateway and activate the new settings.

NOTE: The fields below the update button show the settings as they were set in the IP Settings or

Wi-Fi Client pages. They are not editable on the Common page.

Figure 18: FS-GUI Common Network Settings


Page 23 of 43

6 CONFIGURE THE PROTOAIR

• Follow the steps outlined in Section 5 to access the ProtoAir Web Configurator.

• To set the ProtoAir protocol setup, select the desired setup via the Protocol Selector parameter, click submit and then click System Restart once prompted.

• In the Web Configurator, the Active Profiles are shown below the Configuration parameters. The Active profiles section lists the currently active device profiles, including previous Web Configurator additions. This list is empty for new installations, or after clearing all configurations. (Figure 19)

Figure 19: Web Configurator Screen Showing no Active Profiles


Page 24 of 43

• To add an active profile to support a device, click the Add button under the Active Profiles heading. This will present a drop-down box underneath the Current profile column that lists all the available profiles.

• For every device that is added, assign a unique Node-ID. This specification must match the device’s network settings.

NOTE: If multiple devices are connected to the ProtoAir, set the BACnet Virtual Server Nodes field

to “Yes”; otherwise leave the field on the default “No” setting.

• Once the Profile for the device has been selected from the drop-down list, enter the value of the device’s Node-ID which was assigned in Section 3.3.2.

• Then press the “Submit” button to add the Profile to the list of devices to be configured.

• Repeat this process until all the devices have been added.

• Completed additions are listed under “Active Profiles” as shown in Figure 20.

Figure 20: Web Configurator Showing Active Profile Additions


Page 25 of 43

7 BACNET: SETTING NODE_OFFSET TO ASSIGN SPECIFIC DEVICE INSTANCES


• Node_Offset field shows the current value (default = 50,000).

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 Node_Offset value as needed using the calculation below:

Device Instance (desired) = Node_Offset + Node_ID

For example, if the desired Device Instance for device 1 is 50,001 and the following is true: - Device 1 has a Node-ID of 1

Then plug device 1’s information into the formula to find the desired Node_Offset: 50,001 = Node_Offset + 1

➢ 50,000 = Node_Offset

Once the Node_Offset value is input, it will be applied as shown below:

- Device 1 Instance = 50,000 + Node_ID = 50,000 + 1 = 50,001

• Click “Submit” once the desired value is entered.

Figure 22: Active Profiles

Figure 21: Web Configurator Node Offset Field


Page 26 of 43

8 HOW TO START THE INSTALLATION OVER: CLEARING PROFILES


• At the bottom-left of the page, click the “Clear Profiles and Restart” button.

• Once restart is complete, all past profiles discovered and/or added via Web Configurator are deleted. The unit can now be reinstalled.


Page 27 of 43

Appendix A. Troubleshooting

Appendix A.1. Lost or Incorrect IP Address



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

Ethernet Port




Page 28 of 43

Appendix A.2. 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 A.3 for the relevant wiring and settings.

NOTE: The FieldPoP™ button (see Figure 24) allows users to connect to the SMC

Cloud, Sierra Monitor’s device cloud solution for IIoT. The SMC Cloud enables secure

remote connection to field devices through a FieldServer and its local applications for

configuration, management, maintenance. For more information about the SMC Cloud,

refer to the SMC Cloud Start-up Guide.

Figure 24: Error Messages Screen

https://www.sierramonitor.com/sites/default/files/SMC/Documents/StartupGuides/SMC_Cloud_Start-up_Guide.pdf


Page 29 of 43

Appendix A.3. Checking Wiring and Settings

• No COMS on Modbus RTU side. If the Tx/Rx LEDs are not flashing rapidly then there is a COM issue. To fix this, check the following: o Visual observations of LEDs on ProtoAir (Appendix A.4)

o Check baud rate, parity, data bits, stop bits

o Check device address

o Verify wiring

o Verify device is connected to the same subnet as the ProtoAir

o Verify all the devices are listed in Web Configurator (Section 6)

• Field COM problems: o Visual observations of LEDs on the ProtoAir (Appendix A.4)

o Verify IP Address setting

o Verify wiring

NOTE: If the problem still exists, a Diagnostic Capture needs to be taken and sent to technical

support. (Appendix A.5)


Page 30 of 43

Appendix A.4. LED Diagnostics for Communications Between ProtoAir and Devices

See the diagram below for ProtoAir LED Locations.

Tag Description

SS The SPL LED will light if the unit is not getting a response from one or more of the configured devices.

ERR The SYS ERR LED will go on solid indicating there is a system error. 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.

TX The TX LED will flash when a message is received on the serial port on the 3-pin connector. If the serial port is not used, this LED is non-operational.

RX The RX LED will flash when a message is sent on the serial port on the 3-pin connector. If the serial port is not used, this LED is non-operational.

Figure 25: Diagnostic LEDs

Appendix A.5. Taking Diagnostic Capture with the FieldServer Toolbox

Once the Diagnostic Capture is complete, email it to technical support. The Diagnostic Capture

will accelerate diagnosis of the problem.



• Connect a standard Cat5 Ethernet cable between the PC and ProtoAir.

• Double click on the FS Toolbox Utility.

Diagnostic LEDs

Ethernet Port




Page 31 of 43

• 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 32 of 43

o Click on “Start Diagnostic”

o Wait for Capture period to finish, then the Diagnostic Test Complete window will appear

• Step 2: Send Log

o Once the Diagnostic test is complete, a .zip file is saved on the PC

o Choose “Open” to launch explorer and have it point directly at the correct folder

o Contact technical support for delivery directions for the diagnostic zip file


Page 33 of 43

Appendix A.6. Take a Diagnostic Capture via FS-GUI

Diagnostic Capture via FS-GUI is only available on FieldServers with a bios updated/released on November 2017 or later. Completing a Diagnostic Capture through the FieldServer allows network connections (such as Ethernet and Wi-Fi) to be captured.

Once the Diagnostic Capture is complete, email it to technical support. The Diagnostic Capture

will accelerate diagnosis of the problem.

• Open the FieldServer FS-GUI page.

• Click on Diagnostics in the Navigation panel.

• Go to Full Diagnostic and select the capture period.

• Click the Start button under the Full Diagnostic heading to start the capture.

o When the capture period is finished, a Download button will appear next to the Start button

• Click Download for the caputure to be downloaded to the local PC.

• Send the diagnostic zip file to technical support.


Page 34 of 43

Appendix A.7. Wi-Fi Signal Strength

Wi-Fi

<60dBm – Excellent <70dBm – Very good <80dBm – Good >80dBm – Weak

Figure 27: Wi-Fi Signal Strength Listing

NOTE: If the signal is weak or spotty, try to improve the signal strength by checking the antenna

and the ProtoAir position.


Page 35 of 43

Appendix B. Additional Information

Appendix B.1. 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 192.168.1.24

NOTE: Use the FS Toolbox utility if the IP Address is unknown (Appendix A.1)

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

6. Click on the orange “Submit” button.

7. When the download is complete, click on the “System Restart” button.

Appendix B.2. BACnet: Setting Network_Number for more than one ProtoAir on Subnet

For 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 50.

Figure 28: Web Configurator – Network Number Field


Page 36 of 43

Appendix B.3. Securing ProtoAir with Passwords

Access to the ProtoAir can be restricted by enabling a password. 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 send the password recovery token to technical support to receive a temporary password from the customer support team. Access the ProtoAir to set a new password.

Figure 29: FS-GUI Passwords Page

Figure 30: Password Recovery Page


Page 37 of 43

Appendix B.4. Mounting

The ProtoAir can be mounted using the DIN rail mounting bracket on the back of the unit.

Figure 31: DIN Rail

Din Rail Bracket


Page 38 of 43

Appendix B.5. Physical Dimension Drawings

Figure 32: ProtoAir FPA-W34 Dimensions

P1 Serial Port

Power Port

Wi-Fi Antenna Socket


Page 39 of 43

Appendix C. Vendor Information – Siemens

NOTE: All Modbus TCP/IP registers are the same as the Modbus RTU registers for the serial

device. If this point list is needed, contact Siemens technical support. The Modbus TCP/IP

node address of the device is also the same as the Modbus RTU node address.

Appendix C.1. MAG6000 Modbus RTU Mappings to BACnet/IP and EtherNet/IP

Point Name BACnet

Object Type BACnet

Object ID EtherNet/IP Read Tag

Name EtherNet/IP Write

Tag Name

Absolute Volumeflow AI 1 AbsoluteVolumeFlow_XXX Totalizer 1 Reg 1 AI 2 Totalizer 1 Reg 2 AI 3 Totalizer 1 Reg 3 AI 4 Totalizer 1 Reg 4 AI 5 8 Totalizer 2/Batch Reg 1 AI 6 8 Totalizer 2/Batch Reg 2 AI 7 8 Totalizer 2/Batch Reg 3 AI 8 8 Totalizer 2/Batch Reg 4 AI 9 Totalizer 1 AI 10 Totalizer1_XXX Totalizer 2/Batch AI 11 Totalizer2Batch_XXX Run indicator AI 12 Product code AI 13 Capability bits Reg 1 AI 14 Capability bits Reg 2 AI 15 Flowmeter revision AI 16 MODBUS revision AI 17 MODBUS module HW version AI 18 Last Coil Error AI 19 Last Coil Error AI 20 Last HoldReg Error AI 21 Last HoldReg Error AI 22 Flow direction AV 23 Q max. AV 24 Q max. 2 AV 25 Low flow cut off AV 26 Empty pipe on/off AV 27 Error level AV 28 Zero adjust mode AV 29 Manual zero adjust AV 30 Mains Frequency AV 31 Totalizer 1 direction AV 32 Totalizer 2 direction AV 33 Current Output 1 selection AV 34 Current Output 1 direction AV 35 Current Output 1 range AV 36 Current Output 1 time constants AV 37 Digital Output 1 function AV 38 Pulse 1 direction AV 39 Pulse 1 width AV 40 Frequency 1 Direction AV 41 Frequency 1 Fmax. AV 42 Frequency 1 Timeconstants AV 43 Limit Digital mode AV 44 Limit Digital Setpoint min. AV 45 Limit Digital Setpoint max. AV 46 Limit Digital Hysteresis AV 47 Relay Output 1 function AV 48 Limit Relay mode AV 49 Limit Relay Setpoint min. AV 50 Limit Relay Setpoint max. AV 51 Limit Relay Hysteresis AV 52 Error number AV 53 Batch Quantity AV 54 BatchQuantity_XXX BatchQuantityWR_XXX Batch Compensation AV 55 Batch Time error on/off AV 56 Batch time AV 57


Page 40 of 43

Batch overrun on/off AV 58 Batch overrun error AV 59 Batch counter up/down AV 60 Batch Time constants AV 61 Batch cycle counter AI 62 Cleaning cycle time AV 63 Volume per pulse AV 64 Pulse Polarity AV 65 Pulse Timeout AV 66 Input Function AV 67 Totalizer reset AV 68 Force output AV 69 Sensor size AV 70 Calibration factor AV 71 Correction factor AV 72 Excitation frequency AV 73 Operating time AI 74 Error pending list Reg 01 AI 75 ErrorPending1_XXX Error pending list Reg 02 AI 76 ErrorPending2_XXX Error pending list Reg 03 AI 77 ErrorPending3_XXX Error pending list Reg 04 AI 78 ErrorPending4_XXX Error pending list Reg 05 AI 79 ErrorPending5_XXX Error pending list Reg 06 AI 80 ErrorPending6_XXX Error pending list Reg 07 AI 81 ErrorPending7_XXX Error pending list Reg 08 AI 82 ErrorPending8_XXX Error pending list Reg 09 AI 83 ErrorPending9_XXX Error pending list Reg 10 AI 84 Error pending list Reg 11 AI 85 Error pending list Reg 12 AI 86 Error pending list Reg 13 AI 87 Error pending list Reg 14 AI 88 Error pending list Reg 15 AI 89 Error pending list Reg 16 AI 90 Error pending list Reg 17 AI 91 Error pending list Reg 18 AI 92 Error pending list Reg 19 AI 93 Error pending list Reg 20 AI 94 Error pending list Reg 21 AI 95 Error pending list Reg 22 AI 96 Error pending list Reg 23 AI 97 Error pending list Reg 24 AI 98 Error pending list Reg 25 AI 99 Error pending list Reg 26 AI 100 Error pending list Reg 27 AI 101 Error log list Reg 01 AI 102 Error log list Reg 02 AI 103 Error log list Reg 03 AI 104 Error log list Reg 04 AI 105 Error log list Reg 05 AI 106 Error log list Reg 06 AI 107 Error log list Reg 07 AI 108 Error log list Reg 08 AI 109 Error log list Reg 09 AI 110 Error log list Reg 10 AI 111 Error log list Reg 11 AI 112 Error log list Reg 12 AI 113 Error log list Reg 13 AI 114 Error log list Reg 14 AI 115 Error log list Reg 15 AI 116 Error log list Reg 16 AI 117 Error log list Reg 17 AI 118 Error log list Reg 18 AI 119 Error log list Reg 19 AI 120 Error log list Reg 20 AI 121 Error log list Reg 21 AI 122 Error log list Reg 22 AI 123 Error log list Reg 23 AI 124 Error log list Reg 24 AI 125 Error log list Reg 25 AI 126 Error log list Reg 26 AI 127


Page 41 of 43

Error log list Reg 27 AI 128 Language AV 129 Display line 1 AV 130 Display line 2 AV 131 Display line 3 AV 132 Volumeflow unit AV 133 Volumeflow point AV 134 Totalizer 1 unit AV 135 Totalizer 1 point AV 136 Totalizer 2 unit AV 137 Totalizer 2 point AV 138 System status AI 139 SystemStatus_XXX Error pending 1 AI 140 Error pending 2 AI 141 Error pending 3 AI 142 Error pending 4 AI 143 Error pending 5 AI 144 Error pending 6 AI 145 Error pending 7 AI 146 Error pending 8 AI 147 Error pending 9 AI 148 Batch status AI 149 BatchStatus_XXX Zero adjust progress AI 150 Start Auto Zero Adjust BV 151 Reset Totalizer 1 BV 152 ResetTotalizer1_XXX ResetTotalizer1WR_XXX Hold Totalizer 1 BV 153 HoldTotalizer1_XXX HoldTotalizer1WR_XXX Reset Totalizer 2 BV 154 ResetTotalizer2_XXX ResetTotalizer2WR_XXX Hold Totalizer 2 BV 155 HoldTotalizer2_XXX HoldTotalizer2WR_XXX Start Batch BV 156 StartBatch_XXX StartBatchWR_XXX Pause Batch BV 157 PauseBatch_XXX PauseBatchWR_XXX


Page 42 of 43

Appendix D. Reference

Appendix D.1. Specifications

ProtoAir FPA-W342

Electrical Connections 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

Power Requirements Input Voltage: 12-24V DC Current draw: @ 12V, 240 mA Power Rating: 2.5 Watts

Approvals CE and FCC Class B & C Part 15, TUV approved to UL 60950, IC Canada, RoHS Compliant, PTCRB and CTIA

Power Requirements 12-24V DC Physical Dimensions 4 x 1.1 x 2.7 in (10.16 x 2.8 x 6.8 cm) Weight 0.4 lbs (0.2 Kg) Operating Temperature -20°C to 70°C (-4°F to158°F) Humidity 10-95% RH non-condensing

Wi-Fi 802.11 b/g/n Frequency: 2.4 GHz Channels: 1 to 11 (inclusive) Antenna Type: SMA Encryption: TKIP, WPA & AES

Figure 33: 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 43 of 43

Appendix E. Limited 2 Year Warranty

Sierra Monitor Corporation warrants its products to be free from defects in workmanship or material under normal use and service for two years after date of shipment. Sierra Monitor Corporation will repair or replace any equipment found to be defective during the warranty period. Final determination of the nature and responsibility for defective or damaged equipment will be made by Sierra Monitor Corporation personnel.

All warranties hereunder are contingent upon proper use in the application for which the product was intended and do not cover products which have been modified or repaired without Sierra Monitor Corporation’s approval or which have been subjected to accident, improper maintenance, installation or application, or on which original identification marks have been removed or altered. This Limited Warranty also will not apply to interconnecting cables or wires, consumables or to any damage resulting from battery leakage.

In all cases Sierra Monitor Corporation’s responsibility and liability under this warranty shall be

limited to the cost of the equipment. The purchaser must obtain shipping instructions for the prepaid return of any item under this warranty provision and compliance with such instruction shall be a condition of this warranty.

Except for the express warranty stated above, Sierra Monitor Corporation disclaims all warranties with regard to the products sold hereunder including all implied warranties of merchantability and fitness and the express warranties stated herein are in lieu of all obligations or liabilities on the part of Sierra Monitor Corporation for damages including, but not limited to, consequential damages arising out of/or in connection with the use or performance of the product.