User Manual Anybus Wireless Bridge Ethernet to Bluetooth

User Manual Anybus Wireless Bridge Ethernet to Bluetooth Rev. 1.20 Connecting Devices TM HMS Industrial Networks Mailing address: Box 4126, 300 04 Halmstad, Sweden Visiting address: Stationsgatan 37, Halmstad, Sweden E-mail: info@hms-networks.com Web: www.anybus.com

Important User Information This document is a product guide describing the main use cases for the module and how to configure it. It also contains general information about the product. The reader of this document is expected to be familiar with high level software design, and communication systems in general. The use of advanced Ethernet and Bluetooth specific functionality may require in-depth knowledge in the networking internals of these networks and/or information from the official specifications. In such cases, the people responsible for the implementation of this product should either obtain the specifications to gain sufficient knowledge or limit their implementation in such a way that this is not necessary. Liability Every care has been taken in the preparation of this product guide. Please inform HMS Industrial Networks AB of any inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial Networks AB, reserve the right to modify our products in line with our policy of continuous product development. The information in this document is subject to change without notice and should not be considered as a commitment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that may appear in this document. There are many applications of this product. Those responsible for the use of this device must ensure that all the necessary steps have been taken to verify that the applications meet all performance and safety requirements including any applicable laws, regulations, codes, and standards. HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that may arise as a result from the use of undocumented features, timing, or functional side effects found outside the documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product are undefined, and may include e.g. compatibility issues and stability issues. The examples and illustrations in this document are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot assume responsibility for actual use based on these examples and illustrations. Intellectual Property Rights HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product described in this document. These intellectual property rights may include patents and pending patent applications in the US and other countries. Trademark Acknowledgements Anybus is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders. Warning: ESD Note: This is a class A product. in a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD control procedures are not followed. Static control precautions are required when handling the product. Failure to observe this may cause damage to the product. User Manual Rev 1.20 Copyright HMS Industrial Networks AB October 2013,

Table of Contents Table of Contents Important User Information Liability... 1 Intellectual Property Rights... 1 Trademark Acknowledgements... 1 Preface Chapter 1 Chapter 2 Preface Safety Warnings & Restrictions... 1 WARNINGS!... 1 RESTRICTIONS... 1 About This Document... 1 Related Documents... 1 Document History... 2 Conventions & Terminology... 2 Support... 2 Installation Power... 4 Ethernet Interface... 4 Status Indicators... 4 General Concepts Configuration Methods... 5 Using the SMART Configuration Mode... 5 Using the WEB Configuration Interface... 6 Reset to Factory Defaults... 7

II Chapter 3 Chapter 4 Bluetooth Profiles and the Wireless Bridge Supported Use Cases Two Wireless Bridges Connected as an Ethernet Bridge... 9 Overview... 9 Set Up the Use Case... 9 One or More Wireless Bridges Connected to a WNP (Wireless Network Platform)... 10 Overview...10 Set Up the Use Case... 10 One or More Wireless Bridges Connected to one Generic Bluetooth Access Point...11 Overview...11 Set Up the Use Case... 11 A Wireless Bridge Roaming Between Two or More Bluetooth Access Points... 12 Overview...12 Set Up the Use Case... 12 A Wireless Bridge Roaming Between Two or More Wireless Bridges... 13 Overview...13 Set Up the Use Case... 13 A PC Wirelessly Connected to a Wireless Bridge... 15 Overview...15 Set Up the Use Case... 15 Appendix 5 Legal and Regulatory Declaration of Conformity...16 Licenses...17

Preface P. Preface P.1 Safety Warnings & Restrictions This equipment is suitable for use in Class I, Division 2, Groups A, B, C and D, or non-hazardous locations only. The combinations of equipment in your own system will be subject to investigation by the local Authority Having Jurisdiction at the time of installation. P.1.1 WARNINGS! EXPLOSION HAZARD! - Do not disconnect equipment unless power has been removed or the area is known to be non-hazardous. EXPLOSION HAZARD! - Substitution of any components may impair the suitability for Class I, Division 2. Warning: This is a class A product.. In a domestic environment, this product may cause radio interference in which case the user may be required to take adequate measures. P.1.2 RESTRICTIONS Wiring terminals must be marked to indicate proper connections for the input power, output power, and control circuits. Field wiring terminals may use copper conductors only, wire size AWG 14, minimum temperature rating 60ºC. This equipment is suitable for use in an ambient temperature of max 65ºC. ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD control procedures are not followed. Static control precautions are required when handling the product. Failure to observe this may cause damage to the product. P.2 About This Document This document describes the various configurations available for this product and how to configure them. For more information, documentation etc., please visit the HMS web site: www.hms-networks.com. P.3 Related Documents Document Quick Setup Guide, AT Command Specification for Author HMS HMS

Preface 2 P.4 Document History Summary of Recent Changes (1.10... 1.20) Change Added safety warnings Page(s) P1 Revision List Revision Date Author(s) Chapter(s) Description 1.00 2011-03-22 KaD - First official release 1.10 2011-04-03 KeL All Converted to FM, minor updates 1.20 2013-10-09 SDa P Added safety warnings P.5 Conventions & Terminology The following conventions are used throughout this manual: Numbered lists provide sequential steps Bulleted lists provide information, not procedural steps The terms Anybus or module refer to the Anybus module. The terms host or host application refer to the device that hosts the Anybus module. Hexadecimal values are written in the format NNNNh, where NNNN is the hexadecimal value. EPA = Ethernet Port Adapter P.6 Support For contact information and support, please refer to the contact and support pages at www.hms-networks.com

Chapter 1 1. Installation

Installation 4 1.1 Power The table below shows typical current at 24 V. Operation Mean (ma) Max (ma) Startup 56.08 Idle 44.0 45.5 Idle, Ethernet 54.0 56.0 Idle + 4xMode LEDs 54.3 56.1 Connecting 60.1 60.6 Connected, Data 48.3 48.4 Connected, Data, Ethernet 54.2 54.4 Connected, Data, Ethernet, 4xMode LEDs 57.8 58.9 1.2 Ethernet Interface The Ethernet interface supports 10/100 Mbps with both MDI/MDI-X auto crossover and polarity correction. 1.3 Status Indicators Description Color Status Meaning PWR Green On Supply voltage is present and application is running PWR Green Off Supply voltage is not present, or no application is running ))) Blue/Purple/Red Blue A Bluetooth connection has been established ))) Blue/Purple/Red Flashing Blue Bluetooth data activity ))) Blue/Purple/Red Purple Bluetooth activity (inquiry, name discovery, connection attempt) ))) Blue/Purple/Red Red Error ))) Blue/Purple/Red Off No Bluetooth activity LAN Yellow On Ethernet link is present LAN Yellow Flashing Ethernet data activity LAN Yellow Off No Ethernet connection

Chapter 2 2. General Concepts 2.1 Configuration Methods The Wireless Bridge supports four main methods for setting and configuring the module: Smart mode - Use the buttons and LED s on the Wireless Bridge to automatically set up the most common use cases. Web interface - An online WEB interface with the most common settings for the Wireless Bridge. AT commands - Connect to the Wireless Bridge over Ethernet using TCP, or directly on Layer 2 and use a terminal such as Hyperterminal to issue AT commands. This method is mainly for more advanced settings and use cases and is not described in this document. All commands available in the web interface and much more are supported throught the use of AT commands. The SNMP protocol - This will not be used or described in this document. 2.2 Using the SMART Configuration Mode If the Mode button is pressed within 5 seconds from power up, the Wireless Bridge will enter SMART configuration mode. The LED s above the button (A, B, C, and D) will show the mode currently selected. When the required mode is selected, it must be confirmed by holding in the Mode button for two seconds. This will cause the LED s to start flashing during the operation of the selected mode.

General Concepts 6 There are currently 9 different modes available: Mode Description LEDs A B C D 1 Configuration mode A 2 Reset to factory defaults. This will reset the entire configuration to B factory defaults. 3 Reset IP settings to factory defaults. This will only reset the IP settings A + B to factory defaults. 4 Wait for Automatic configuration (LED C ). C 5 Initiate Automatic configuration (LED A and C ). A + C 6 Initiate Automatic configuration with Profinet optimizations (LED B and C ). 7 Initiate Automatic configuration to a connectblue WNP (Wireless Network Platform) (LED A, B, and C ). 8 Initiate Automatic configuration with EDR (LED D ). D B + C A + B + C 9 Initiate Automatic configuration with Profinet optimizations and A + D EDR (LED A and LED D ) 10 Reserved for future use. B + D 11 Reserved for future use. A + B + D 12 Reserved for future use. C + D 13 Reserved for future use. A + C + D 14 Reserved for future use. B + C + D 15 Reserved for future use. A + B + C + D Configuration mode can be used to easily access the Ethernet Port Adapter (EPA) if the PC is using DHCP, without having to change the PC s IP settings. This mode should only be used when the PC is connected directly to the EPA, and not if the EPA is connected to a network using a DHCP server. Enable this mode, then connect the Ethernet cable to the computer. The EPA will then use the factory IP settings (192.168.0.98/255.255.0.0) and the configuration interfaces will be enabled (if disabled earlier). The DHCP server will stay enabled until the EPA is rebooted. 2.2.1 Using the WEB Configuration Interface By default, the EPA has the following static IP settings; IP address: 192.168.0.98 Sub net mask: 255.255.0.0 Default gateway: 192.168.0.99 To access the EPA via the Web-based configuration interface, the computer must be set up in the same network, e.g. IP address: 192.168.0.1 and sub net mask: 255.255.0.0. Open a web browser and enter http://192.168.0.98 in the address bar. The most common configuration parameters needed to setup a connection are listed here. If the Wireless Bridge is in factory default, there is no need to log in before configuring the device.

General Concepts 7 An example of the web interface is shown below: 2.2.2 Reset to Factory Defaults It is possible to reset to factory settings in 3 different ways. Enter and confirm SMART mode 2 Issue AT&F Hold in the mode button while the Wireless Bridge is starting. Note: Check that the Ethernet cable is disconnected, and that any firmware update program has been stopped.

Chapter 3 3. Bluetooth Profiles and the Wireless Bridge For Ethernet access using Bluetooth, the Bluetooth Personal Area Network (PAN) profile is used. In this profile, there are two important roles: PANU - Pan User Role. This is the standard client role used when a Bluetooth device is connected to an Ethernet device. Two PANU devices may connect to each other. Several PANU devices may connect to a Bluetooth Access Point supporting the NAP role (see below). NAP - Network Access Point Role. This is a device connected to a network, supporting multiple devices using the PANU role. A maximum of seven simultaneous connections are possible (due to limitations of Bluetooth). NAP is the role normally used by a Bluetooth Access Point. Note: The Wireless Bridge only supports one connection in the NAP role.

Chapter 4 4. Supported Use Cases 4.1 Two Wireless Bridges Connected as an Ethernet Bridge 4.1.1 Overview This use case describes two Wireless bridges connected as bridge between tow Ethernet segments. Both Wireless Bridges support several Ethernet devices and transfer data between the two Ethernet segments. 4.1.2 Set Up the Use Case. This use case can be set up using the SMART button. This is used to transfer data between two Ethernet segments: 1. Power on the first device and enter SMART configuration mode 4. 2. Power on the second device and enter SMART configuration mode 5. 3. Wait for the devices to connect and restart. 4. The first device will now have the IP address 192.168.0.98 and the second will have 192.168.0.99.

Supported Use Cases 10 4.2 One or More Wireless Bridges Connected to a WNP (Wireless Network Platform) 4.2.1 Overview Up to seven Wireless Bridges (or other Bluetooth PANU devices) can be connected to one WNP. All devices connected to the Wireless Bridges and WNP respectively are seen as transparently connected to the same Ethernet network. 4.2.2 Set Up the Use Case. This use case can be set up using the SMART button: 1. Power on the WNP. The WNP must be configured as a Bluetooth Access Point (Bluetooth PAN Profile; the NAP role). Configuration of the WNP is not described in this document. 2. Power on the Wireless Bridge and enter SMART configuration mode 7. 3. Wait for the devices to connect and restart. If settings other than the defaults are required, the built-in web interface must be used. See section Using the WEB Configuration Interface on page 6 for more information on how to use the web interface.

Supported Use Cases 11 4.3 One or More Wireless Bridges Connected to one Generic Bluetooth Access Point 4.3.1 Overview Up to seven Wireless Bridges or other Bluetooth PAN devices can be connected to one Bluetooth access point (note any possible limitations in the selected access point). This use case assumes a static network with no roaming. 4.3.2 Set Up the Use Case 1. Connect a PC to the Wireless Bridges. See section Using the WEB Configuration Interface on page 6 for more information on how to connect to the Wireless Bridge. 2. Define the Bluetooth connection parameters. The following are required. Parameter Device Name Security Mode Passkey Visible for other devices Link Sensitivity Connect to name scheme Low Emission Mode Exclude WLAN Channel Bluetooth address Connection: Device Name Remote Role Required Value No (Yes) Off NAP Comment Name of the device. Not normally used in this case. ON or OFF. Dependent on the setup of the access point to connect to. Same passkey as the access point, if required. Not required. The Wireless Bridge initiates the connection. Defines the sensitivity for roaming. A high value will disconnect the link sooner if the unit moves out of range. If no roaming is required, a low value can be selected. Not valid in this use case, as a fixed connection using the BDADDR of the access point is assumed. Not valid in this use case. Not valid in this use case. Use the Scan function to search for the access point. Setup of the access point is not described in this document.

Supported Use Cases 12 4.4 A Wireless Bridge Roaming Between Two or More Bluetooth Access Points 4.4.1 Overview In this use case, the Wireless Bridge is roaming between several Bluetooth Access Points, e.g. WNPs. 4.4.2 Set Up the Use Case 1. Connect a PC to the Wireless Bridge. See section Using the WEB Configuration Interface on page 6 for more information on how to connect to the Wireless Bridge. 2. Define the Bluetooth connection parameters. The following are required: Parameter Device Name Security Mode Passkey Visible for other devices Link Sensitivity Connect to name scheme Low Emission Mode Exclude WLAN Channel Bluetooth address Connection: Device Name Remote Role Required Value No (Yes) NAP Comment Name of the device. Not normally used in this case. ON or OFF. Depending on the setup of the access point to connect to. Same passkey as the access point, if required. Not required. The Wireless Bridge initiates the connection. This function defines the sensitivity for roaming. A high value will disconnect the link quicker if the unit moves out of range. 1. Connect To First Name. The Wireless Bridge searches for access points. When it finds one, it checks if the name contains the string entered in Connection: Device Name and connects to it. If the name is not correct, it will retry the procedure. 2. Connect To Name. The Wireless Bridge searches for a list of local access points. It connects to the first one where the name contains the string entered in Connection: Device Name : 3. Connect To Best Name. The Wireless Bridge searches for a list of local access points. It connects to the access point with the name in the string entered in Connection: Device Name and which has the best RSSI (Received Signal Strength) value. Select ON or OFF. By setting to ON, other wireless devices in the neighborhood will be less disturbed during the device discovery and connection phase, but on the other hand, the risk for missing a connection attempt increases. Used for coexistence. Exclude WLAN channels not to use. Exclude the same channels in the Access Point. Must be left empty. String used to filter out which Access Point to connect to. See Connect to name scheme. See the documentation for the access point for information on how to set it up.

Supported Use Cases 13 4.5 A Wireless Bridge Roaming Between Two or More Wireless Bridges 4.5.1 Overview In this use case the Wireless Bridge is roaming between two or more Wireless Bridges. 4.5.2 Set Up the Use Case The Network Wireless Bridges 1. Connect a PC to the Wireless Bridges. See section Using the WEB Configuration Interface on page 6 for more information on how to connect to the Wireless Bridge. 2. Define the Bluetooth connection parameters. The following parameters are required: Parameter Required Comment Device Name Name of the device. Not normally used in this case. Security Mode ON or OFF. Dependent on the application requirements. Passkey Dependent on the selected security mode. Visible for other Yes Required for this use case, as Connect To Name is used. devices Link Sensitivity This function defines the sensitivity for roaming. A high value will disconnect the link sooner if the unit moves out of range. It is recommended to use the same value as used by the roaming Wireless Bridge. Connect to name Not valid in this use case, as these units are the receivers of the connection attempts. scheme Low Emission Mode Not valid in this use case, as these units are the receivers of the connection attempts. Exclude WLAN Channel Bluetooth address Connection: Device Name Remote Role Used for co-existence. Exclude WLAN channels not to use. Exclude the same channels as defined for the Roamiing Wireless Bridge. Must be left empty. Must be left empty. Not valid, as these units are the receivers of the connection attempts.

Supported Use Cases 14 The Roaming Wireless Bridge 3. Connect a PC to the Wireless Bridges. See section Using the WEB Configuration Interface on page 6 for more information on how to connect to the Wireless Bridge. 4. Define the Bluetooth connection parameters. The following are required: Parameter Device Name Security Mode Passkey Visible for other devices Link Sensitivity Connect to name scheme Low Emission Mode Exclude WLAN Channel Bluetooth address Connection: Device Name Remote Role Required Value No (Yes) PANU or PAN Comment Name of the device. Not normally used in this case. Dependent on the application requirements. Dependent on the selected security mode. Not required. The Wireless Bridge initiates the connection. This function defines the sensitivity for roaming. A high value will disconnect the link sooner if the unit moves out of range. It is recommended to use the same value as used by the Roaming Wireless Bridges. 1. Connect To First Name. The Wireless Bridge searches for another Access Point. When one is found, it checks if the name contains the string entered in Connection: Device Name and, if so, connects to it. If the name is not correct, the procedure will be re-tried. 2. Connect To Name. The Wireless Bridge searches for a list of local access points. It connects to the first one where the name contains the string entered in Connection: Device Name : 3. Connect To Best Name. The Wireless Bridge searches for a list of local access points. It connects to the access point where the name contains the string entered in Connection: Device Name and which has the best RSSI (Received Signal Strength) value. Select ON or OFF. By setting this to ON, other wireless devices in the neighborhood will be less disturbed during the device discovery and connection phase, but the risk of missing a connection attempt increases. Used for coexistence. Exclude WLAN channels not to use. Exclude the same channels in the Network Wireless Bridges. Needs to be left empty. String used to filter out which Network Wireless Bridge to connect to. See Connect to name scheme.

Supported Use Cases 15 4.6 A PC Wirelessly Connected to a Wireless Bridge 4.6.1 Overview A PC supporting the Bluetooth profile (PANU role) is connected to a Wireless Bridge. This could be either a Wireless Bridge to a single device, or a Wireless Bridge connected to an Ethernet network with several devices. 4.6.2 Set Up the Use Case 1. Connect a PC to the Wireless Bridges. See section Using the WEB Configuration Interface on page 6 for more on how to connect to the Wireless Bridge. 2. Define the Bluetooth connection parameters. The following are required: Parameter Device Name Security Mode Passkey Visible for other devices Link Sensitivity Connect to name scheme Low Emission Mode Exclude WLAN Channel Bluetooth address Connection: Device Name Required Value Yes Off Comment This is the name that will be shown when searching for the device from the PC. ON or OFF. Dependent on the application requirements. Dependent on the selected security mode. Required to search for the device from the PC. Defines the sensitivity for roaming. A high value will disconnect the link sooner if the unit moves out of range. A low value can be entered if roaming is not required. Not valid in this use case. Not valid in this use case. Not valid in this use case. Must be left empty. Not valid, as the PC is the initiator of the connection in this use case. Remote Role NAP Not valid, as the PC is the initiator of the connection in this use case. The setup of the PC is determined by the Bluetooth software on the PC. Use the Bluetooth GUI to search for a PAN device with the same name as the Wireless Bridge. Use the same security settings on both devices.

Appendix 5 5. Legal and Regulatory 5.1 Declaration of Conformity The product meets the essential requirements according to article of the following EC-Directives): R&TTE Directive 1999/5/EC Effective use of frequency spectrum: EN 300 328 V1.7.1 (2006-10) EMC: EN 301 489-1 V1.8.1 (2008-04) EN 301 489-17 V2.1.1 (2009-05) EN 61000-6-2 (2005) Health and Safety: EN 50371:2002 EN 60950-1:2006 + A11:2009 + A1:2010 (EN 60950-1:2011-01) and/or IEC 60950-1:2005 (2 nd Edition) + A1:2009

Legal and Regulatory 17 5.2 Licenses This product contains software under the following licenses: /* * Copyright (c) 2001-2004 Swedish Institute of Computer Science. * All rights reserved. * * Redistribution and use in source and binary forms, with or without modification, * are permitted provided that the following conditions are met: * * 1. Redistribution of source code must retain the above copyright notice, * this list of conditions and the following disclaimer. * 2. Redistribution in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * 3. The name of the author may not be used to endorse or promote products * derived from this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT * SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT * OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY * OF SUCH DAMAGE. * * This file is part of the lwip TCP/IP stack. * * Author: Adam Dunkels <adam@sics.se> * */