Beruflich Dokumente
Kultur Dokumente
Ethernet to WLAN
Doc. ID HMSI-27-205
Rev. 1.30
Connecting DevicesTM
+$/067$'&+,&$*2.$5/658+(72.<2%(,-,1*0,/$1208/+286(&29(175<381(&23(1+$*(1
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 Indus-
trial Networks AB, reserve the right to modify our products in line with our policy of continuous product develop-
ment. 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 er-
rors 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 in-
cluding 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.
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed 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.
Table of Contents
Preface Preface
Safety Warnings & Restrictions.............................................................................................................. 5
WARNINGS!............................................................................................................................... 5
RESTRICTIONS......................................................................................................................... 5
About This Document ............................................................................................................................ 5
Related Documents.................................................................................................................................. 5
Document History ................................................................................................................................... 6
Conventions & Terminology .................................................................................................................. 6
Support....................................................................................................................................................... 6
Chapter 1 Installation
Power.......................................................................................................................................................... 8
Ethernet Interface .................................................................................................................................... 8
Status Indicators ....................................................................................................................................... 8
- Alternative 1.......................................................................................................................................... 23
Overview ........................................................................................................................................ 23
Set Up the Use Case...................................................................................................................... 23
PC Connected Wirelessly to Wireless Bridge
- Alternative 2.......................................................................................................................................... 24
Overview ........................................................................................................................................ 24
Set Up the Use Case...................................................................................................................... 24
Multiple Ethernet Devices Connected in Client Mode - Alternative 1.......................................... 25
Overview ........................................................................................................................................ 25
Set Up the Use Case...................................................................................................................... 25
Multiple Ethernet Devices Connected in Client Mode - Alternative 2.......................................... 26
Overview ........................................................................................................................................ 26
Set Up the Use Case...................................................................................................................... 26
One or More Wireless Bridges Connected to a Wired Infrastructure through WLAN.............. 27
Overview ........................................................................................................................................ 27
Set Up the Use Case...................................................................................................................... 27
External WLAN Client Connected to a Wireless Bridge ................................................................. 28
Overview ........................................................................................................................................ 28
Set Up the Use Case...................................................................................................................... 28
Multiclient Mode .................................................................................................................................... 29
Overview ........................................................................................................................................ 29
Set Up the Use Case...................................................................................................................... 29
P. Preface
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, Di-
vision 2.
Warning: This is a class A product.. In a domestic environment, this product may cause radio interfer-
ence 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.
Change Page(s)
Removed section 3.13 in chapter 3
Revision List
P.6 Support
For contact information and support, please refer to the contact and support pages at
www.anybus.com
1. Installation
1.1 Power
The table below shows the typical current at 24 V.
2. General Concepts
1. Smart mode
Use the buttons and LED’s on the Wireless Bridge to automatically set up the most common use
cases.
2. Web interface
An online web interface with the most common settings for the Wireless Bridge.
3. AT commands
Connect to the Wireless Bridge over Ethernet using TCP, or directly on Layer 2 and use a termi-
nal such as Hyperterminal to issue AT commands. This method is mainly for more advanced set-
tings 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.
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 select-
ed. 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.
"Enable DHCP server" can be used to easily access the Wireless Bridge if the PC is using DHCP, with-
out having to change the PC’s IP settings. This mode should only be used when the PC is connected
directly to the module, and not if the module is connected to a network using a DHCP server. Enable
this mode, then connect the Ethernet cable to the computer. The DHCP server will stay enabled until
a reboot.
How to use the other different modes for specific use cases is described later in this document.
There are three main Wireless Bridge modes supported by the Wireless Bridge, and these are referred to
in all the use cases described later in this document.
2. Client mode
In this mode the Wireless Bridge acts as a wireless extension of the wired Ethernet device it is
connected to. The module is configured to take over (clone!) the MAC address of the connected
device. This means that only ONE Ethernet device can be connected to each module, and not
an Ethernet network with several devices connected through an Ethernet switch or hub. In
"Client Mode", the Wireless Bridge cannot be accessed over the Wireless LAN interface. How-
ever, if the Ethernet link is lost, the module will temporarily enter "Multiclient mode" and can
then be accessed again. When the Ethernet link is re-established, the module will revert to "Client
Mode".
3. Multiclient mode
In this mode, the Wireless Bridge acts as in Client mode, but with the addition that multiple de-
vices using the IP layer can be connected.
Ethernet Bridge mode will introduce an extra overhead (because of the encapsulation) and will have a
significantly lower throughput than Client/Multiclient mode.
The Wireless Bridge supports various authentication and encryption methods. The following authenti-
cation methods are supported:
• Open connection
• Shared secret
• WPA and WPA2 Preshared key
• LEAP
• PEAP
The following encryption methods are supported:
• No encryption
• WEP64
• WEP128
• TKIP
• AES/CCMP
The following table shows valid combinations of authentication and encryption methods (x means valid
configuration):
There are a few important considerations that also need to be addressed. If selecting WPA/WPA2 PSK
and TKIP, this is considered to be a WPA connection. If selecting WPA/WPA2 PSK and AES/CCMP,
a WPA2 connection is assumed. It is not possible to have WPA with AES/CCMP encryption.
To use LEAP or PEAP as the authentication algorithm, ensure that the access point supports this, as
not all do. Neither LEAP, PEAP nor WPA/WPA2 PSK will work in ad-hoc mode.
Note: Some access points have support for a combination of WPA and WPA2, as well as AES/CCMP
and TKIP. These options are not supported by the Wireless Bridge.
Key Management
For WEP64 and WEP128, shared keys can be entered in all four possible slots made available by the
AT*AGFPWI Write Encryption/Authentication Key (with Index) command. However, for LEAP,
PEAP and WPA/WPA2 PSK, the password or PSK must be entered in the key slot with index 1 (one).
This key must also be the one currently set as active by the AT*AGAFP Active Encryption/Authenti-
cation Key command.
If using LEAP or PEAP, the username for the Radius server should be entered with the command
AT*AGUN Username, and the domain with command AT*AGDN. For PEAP, the certificate must
also be considered. When receiving the certificate from the Radius server, the SHA-1 fingerprint is cal-
culated and stored in the WEPA for future comparisons. If the certificate changes, or if a different Ra-
dius server is to be used, the new fingerprint must be entered, or the old must be cleared with the
command AT*AGCFP.
If using WPA/WPA2 PSK, it is possible to enter either the preshared key (i.e. the hexadecimal string)
or the password (plain-text), commonly referred to as “WPA-PSK” or “WPA-PWD”. When entering a
password (not a hexadecimal string), the Wireless Bridge will take a few seconds longer during the next
connection after this change, in order to deduce the real key from the password. The module will be
unresponsive while calculating the real key.
By default, the key is entered as an ASCII string. To enter a hexadecimal key, the bytes must be escaped
with the '\' character, e.g. to enter the string "12345" as hexadecimal, the following would be entered:
"\31\32\33\34\35"
3.1.1 Overview
This use case describes two Wireless Bridges connected in Ethernet Bridge mode. Multiple Ethernet de-
vices on each side of the module are supported. The Ethernet data is bridged through a UDP tunnel and
ad-hoc mode is used.
Should the predefined IP addresses already be in use on your network, it may be necessary to configure
the setup manually:
1. Power on the first Wireless Bridge and enter the web configuration. See “Using the Web Con-
figuration Interface” on page 10.
2. Enter the required IP Address (IP_ADDR1), Netmask and Default Gateway. DHCP should be
turned off. Click "Write Network Settings". Note: The IP address must be selected to avoid IP
conflicts.
3. Enter the Network Name (SSID) for the wireless network.
4. Select Operation mode "Ad-Hoc" and select a channel to use, based on your regional domain
settings.
5. Select Security Mode: The options currently available in ad-hoc mode are: "None", "WEP64"
and "WEP128".
6. If security was selected, now enter a key.
7. Under Client Mode, select “Ethernet Bridge”. Enter the IP address of the other Wireless Bridge
(IP_ADDR2) and set the UDP Port, e.g 2000.
8. Click "Write Wireless LAN Settings".
9. Click "Reboot Device".
10. Power on the second Wireless Bridge and enter the web configuration.
11. Repeat step 2 above, but select the IP address entered under Client Mode above (IP_ADDR2).
Click "Write Network Settings".
12. Repeat 3, 4, 5, and 6 above. These values MUST be identical to the ones entered for the previous
Wireless Bridge.
13. Repeat step 7 above, but using the IP address (IP_ADDR1) instead. The port must be the same
as entered under 7 above. Click "Set".
14. Click "Write Wireless LAN Settings".
15. Click "Reboot".
All Ethernet packets will now be tunneled between the two Ethernet segments.
3.2.1 Overview
This use case describes two Wireless Bridges connected in Ethernet Bridge mode. Multiple Ethernet de-
vices on each side of the module are supported. The Ethernet data is bridged through an UDP tunnel,
and Managed (Infrastructure) mode is used.
3.3.1 Overview
This use case uses two Wireless Bridges connected in Ethernet Bridge mode. Here, one of the modules
is connected to a wired network and it does NOT use the wireless connection. Managed (infrastructure)
mode is used.
3.4.1 Overview
This use case describes two Wireless Bridges connected in Client mode. Only one Ethernet device can
be connected to each of the modules. This use case will have higher performance than using the Ether-
net Bridging case (no encapsulation of the Ethernet packages required).
This use case can be set up by using the SMART button and supports ad-hoc mode only.
1. Power on the first module. Enter SMART configuration mode 4 (wait for automatic configura-
tion).
2. Power on the second module. Enter SMART configuration mode 5 (initiate automatic configu-
ration).
3. Wait for the modules to connect and restart.
4. Use SMART mode 11 on each of the modules, to learn the MAC address of the connected device
(Client mode).
Note: This mode required that the device spontaneously sendd Ethernet data on the Ethernet
link. If this not is possible, use the web interface. See section “Using the Web Configuration In-
terface” on page 10 to set up the MAC address manually.
To set up this use case manually, follow these steps:
1. Power on the first Wireless Bridge and enter the web configuration.
2. Enter the SSID for the wireless network.
3. Select Operational mode "Ad-Hoc" and select a channel to use, based on the regional domain
settings.
4. Select Security Mode: The options available in ad-hoc mode are: "None", "WEP64" or
"WEP128".
5. If a security option was selected, now enter a key.
6. Under Client Mode, select Client Mode and set "WLAN MAC Address" to the MAC address
of the module it will be connected to via the wired connection.
7. Click "Write Wireless LAN Settings". Click "Reboot Device".
8. Power on the second Wireless Bridge and enter the web configuration.
9. Repeat 2, 3, 4 and 5 above. These values MUST be identical to the ones entered for the previous
module.
10. Repeat step 6 above. The "WLAN MAC Address" must be set to the MAC address of the device
it will be connected to via the wired connection.
11. Click "Write Wireless LAN Settings". Click "Reboot Device".
All Ethernet packets will now be tunneled between the two Ethernet segments.
3.5.1 Overview
This use case describes two Wireless Bridges connected in Client mode. Only one Ethernet device can
be connected to each of the modules. The Wireless Bridge is connected to a WLAN Access Point that
allows the use of Managed (infrastructure) mode with higher performance as a result.
Both modules must operate in Client or Multiclient mode in this use case.
1. Connect a PC to the Wireless Bridge. See section “Using the Web Configuration Interface” on
page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following parameters are required:
Note: For this SMART mode to operate, it is required that the device spontaneously sends Ethernet packages on
the Ethernet link.
3.6.1 Overview
In this use case only ONE Ethernet device is connected to the Wireless Bridge. The PC is used to access
the Ethernet device, using any Ethernet-based protocol, e.g. a built-in web interface or an Ethernet
based communication protocol e.g. Modbus-TCP.
The Wireless Bridge must operate in Client Mode in this use case.
1. Connect a PC to the Wireless Bridge. See section “Using the Web Configuration Interface” on
page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following parameters are required:
How the PC is set up is dependent on the Wireless LAN solution supported for the PC. Use the WLAN
GUI to search for an ad-hoc network with the same SSID as the one set for the module. Select WEP as
encryption, and select the same WEP key that you entered during the Wireless Bridge configuration.
3.7.1 Overview
In this use case, only ONE Ethernet device is connected to the Wireless Bridge. The PC is used to access
the Ethernet device, using any Ethernet-based protocol, e.g. a built-in web interface or an Ethernet
based communication protocol, e.g. Modbus-TCP. In this case, the Wireless Bridge and the PC are con-
nected to each other via a WLAN Access Point, which allows the use of Managed (infrastructure) mode,
resulting in higher performance.
The Wireless Bridge must operate in Client Mode in this use case.
1. Connect a PC to the Wireless Bridge. See section “Using the Web Configuration Interface” on
page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following are required:
How the PC is is set up is dependent on the Wireless LAN solution supported for the PC. Use the
WLAN GUI to search for a Managed (infrastructure) network with the same SSID as the Access Point.
Select the same security parameters as defined for the Access Point.
3.8.1 Overview
Three or more Wireless Bridges connected in an ad-hoc network. This use case requires Client mode.
The Wireless Bridge must operate in Client Mode in this use case.
1. Connect a PC to each of the Wireless Bridges. See section “Using the Web Configuration Inter-
face” on page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following are required:
3.9.1 Overview
Three or more Wireless Bridges connected through a WLAN Access Point. This use case requires Client
mode. In this case the Wireless Bridges are connected to each other via a WLAN Access Point that al-
lows the use of Managed (infrastructure) mode, resulting in higher performance.
All Wireless Bridges must operate in Client Wireless Mode in this use case.
1. Connect a PC to each of the Wireless Bridges. See section “Using the Web Configuration Inter-
face” on page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following parameters are required:
3.10.1 Overview
In this use case the Wireless Bridges are used to connect to a wired Ethernet infrastructure using a stand-
ard WLAN access point. Other WLAN devices can, of course, be connected to the same access point,
assuming they share the same networking parameters as the Wireless Bridges.
All Wireless Bridges must operate in Client Mode in this use case.
1. Connect a PC to the Wireless Bridge. See section “Using the Web Configuration Interface” on
page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following are required:
3.11.1 Overview
In this use case, some other WLAN client is connected to a Wireless Bridge that in turn is connected to
an Ethernet device.
The Wireless Bridge must operate in Client Mode in this use case.
1. Connect a PC to the Wireless Bridges. See section “Using the Web Configuration Interface” on
page 10 for more information on how to connect to the Wireless Bridge.
2. Define the WLAN connection parameters. The following are required:
The external device must be configured to support ad-hoc mode and use the same WEP key and SSID
as the Wireless Bridge.
3.12.1 Overview
Multiclient mode is used when there is a need to have several devices (3 and 4 in figure above) behind
the Wireless Bridge that communicates with 1 and/or 2. The restriction is that only one device (3 or 4
in the example) can use Layer-2 communication, while the others need to use the IP layer. The Wireless
Bridge must also be configured on the same IP subnet as the other devices.
For devices to use DHCP over the Wireless Bridge connection while in Multiclient mode, the built-in
DHCP relay can be switched on with AT*ANDHCP, to ensure that all packets are forwarded correctly.
In this case, "DHCP Client and DHCP Relay" is recommended.
Multiclient mode is configured with AT*ACEW. If no Layer-2 communication is required, the MAC-
address for AT*ACEW can be set to the Ethernet MAC-address of the Wireless Bridge.
IC Compliance
Operation is subject to the following two conditions:
1. This device may not cause harmful interference
2. This device must accept any interference received, including interference that may cause unde-
sired operation
The installer of this radio equipment must ensure that the antenna is located or pointed such that it does
not emit RF field in excess of Health Canada limits for the general population; consult Safety Code 6,
obtainable from Health Canada's website http://www.hc-sc.gc.ca.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two condi-
tions: (1) this device may not cause harmful interference, and (2) this device must accept any interference
received, including interference that may cause undesired operation.
• This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment generates, uses and can
radiate radio frequency energy and, if not installed and used in accordance with the instructions,
may cause harmful interference to radio communications. However, there is no guarantee that
interference will not occur in a particular installation. If this equipment does cause harmful in-
terference to radio or television reception, which can be determined by turning the equipment
off and on, the user is encouraged to try to correct the interference by one or more of the fol-
lowing measures:
• Re-orient or relocate the receiving antenna
• Increase the separation between the equipment and receiver
• Connect the equipment to an outlet on a circuit different from that to which the receiver
is connected
Consult the dealer or an experienced radio/TV technician for help.
Caution
• Any changes or modifications NOT explicitly APPROVED by connectBlue AB could cause the
module to cease to comply with FCC rules part 15, and thus void the user's authority to operate
the equipment.
• Within the 5180 to 5240 MHz band (5 GHz radio channels 34 to 48) the product are restricted
to indoor operations.
• §15.407 statement; in case of absence of information to transmit or operational failure the prod-
uct will automaticallyv discontinue transmission.
Ad-hoc Frequencies
When operating under the definition of a client in 47 CFR §15.202 is preconfigured to use the most re-
strictive regulatory domain. For this reason the available operating frequency range is limited to channel
1 - 11 (2412 - 2462 MHz) for IEEE802.11b/g. For IEEE802.11a the available operating frequency
range is limited to channels 36 - 48 (5180 - 5240 MHz).
RF-exposure Statement
This modular transmitter MUST have a separation distance of at least 20 cm between the antenna and
the body of the user or nearby persons.
Any notification to the end-user of installation or removal instructions about the integrated radio mod-
ule is NOT allowed.
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)*
EN 301 893 V1.5.1 (2008-12)**
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
4.3 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>
*
*/