OneWireless Planning Guide OW-CDX030

Honeywell OneWireless
OneWireless
Planning Guide
OW-CDX030
R120
April 2010
Release 120
Honeywell
Notices and Trademarks
Copyright 2010 by Honeywell International Sárl.

Release 120 April 2010
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell
International Inc.
Other brand or product names are trademarks of their respective owners.
Honeywell Process Solutions

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA
1-800 822-7673
ii OneWireless Planning Guide R120

Honeywell April 2010
About This Document
This guide contains the planning information for the Honeywell OneWireless system, including
checklists that may be helpful when planning your OneWireless network.
Honeywell does not recommend using devices for critical control, where there is a single point of
failure or where single points of failure result in unsafe conditions. The initial release of
OneWireless is targeted at open loop control, supervisory control, and controls that do not have
environmental or safety consequences. As with any process control solution, the end-user must
weigh the risks and benefits to determine if the products used are the right match for the
application based on security, safety, and performance. Additionally, it is up to the end-user to
ensure that the control strategy sheds to a safe operating condition, if any crucial segment of the
control solution fails.
Release Information
Document Name Document ID Release Publication
Number Date
OneWireless Planning Guide OW-CDX030 120 April 2010
Document Category
Planning and Design
Intended audience
This guide is intended for people who are responsible for planning the installation of the
Honeywell OneWireless network. It is assumed the person responsible for planning a
OneWireless network is familiar with the following:
• Open Standard protocols such as MODBUS and OPC
• Wireless system and techniques
• Wireless security practices
• Wireless Sensor Networks (WSNs)
R120 OneWireless Planning Guide iii

April 2010 Honeywell
For more information

Honeywell OneWireless user documents
The following table lists the other related Honeywell OneWireless documents and
describes the type of information covered in each document.
Document and Description

nd
Honeywell 2 Generation Wireless Release Specifications
• Defines all the technical and environmental specifications for Honeywell
OneWireless components.
Preparing for Industrial Wireless Whitepaper
• Summarizes the benefits of wireless technology in an industrial facility.
Getting Started with Honeywell OneWireless
• Introduces the Honeywell OneWireless system and briefly describes each
component.
• Provides minimal instructions for installing and configuring OneWireless
components and also provides references for finding additional information.
OneWireless Field Network Dictionary
• Defines all the terms used and the components of Honeywell’s OneWireless
system.
OneWireless Multinode Device User’s Guide
• Provides procedures for installing, configuring, and maintaining multinode devices.
• Contains technical specifications.
OneWireless Builder User’s Guide
• Describes the Wireless Builder interface.
• Provides procedures for using the Wireless tool to build Wireless control strategies
and commission wireless devices.
OneWireless System Administration Guide
• Provides procedures for installing, configuring, and maintaining the OneWireless
Server, the Authentication Device, and the industrial wireless network.
• Contains additional troubleshooting information.
iv OneWireless Planning Guide R120


Wireless Builder Parameter Reference
• Defines the user-visible parameters of the Honeywell OneWireless network.
• Provides details of each of the wireless parameters, including their attributes and
their applicability to wireless function blocks.
• Use this document as you build wireless networks and during operation, when you
require detailed information about function block parameters.
OneWireless Transmitter Quick Start Guide
• Contains a quick reference for installing and configuring Honeywell wireless field
devices (pressure transmitters, temperature transmitters, high-level analog input
transmitters and corrosion transmitters).
OneWireless Transmitter User Manuals
• Separate user guides for each wireless transmitter type (pressure transmitter,
temperature transmitter, high-level analog input transmitter, corrosion transmitter)
provides information about the transmitter operating parameters and the function
blocks.
• Contains compliance information and the technical specifications.
OneWireless Multinode Agency Compliance Professional Installation Guide
• Provides specifications and defines the operating conditions for the Honeywell
multinode.
• Contains professional installation instructions for the optional external antennas,
for use with the Honeywell OneWireless Multinode device.
• Available for authorized professional installers.
OneWireless XYR 6000 Transmitter Professional Installation Guide
XYR transmitters.
• Contains professional installation instructions for the wireless transmitters.
• Available for authorized professional installers.
R120 OneWireless Planning Guide v

Other references
The following table describes other sources of information for implementing an industrial
wireless system.

OneWireless Multinode Agency Compliance Professional Installation Guide
multinode.
• Contains professional installation instructions for the optional external antennas
for use with the Honeywell OneWireless Multinode device.
Honeywell Preparing for Industrial Wireless Whitepaper
• Lists the benefits of industrial wireless technology.
• Discusses the planning issues for implementing industrial wireless systems in
the automation and control environment.
Instrumentation, Systems and Automation Society’s (ISA) SP-100 emerging standard
(not yet released)
• Will define a set of standards for implementing wireless systems in the
automation and control environment.
• Will recommend best practices for the wireless systems.
IEEE 802.15.4 RF Standard
• Radio standards that specifically address the requirements of wireless
monitoring and control systems.
IEEE 802.11(a) (b) (g)
• Specifications for wireless local area networks.
vi OneWireless Planning Guide R120

Purpose and scope of document

Installing any type of network requires planning to ensure acceptable levels of
performance, reliability, and security. Additionally, before installing a Honeywell
OneWireless system, you must complete a Radio Frequency (RF) site survey. Honeywell
OneWireless Services can perform a comprehensive site survey for you.
This document is intended to provide a list of considerations when planning your
Honeywell OneWireless network. This document does not cover all possible or
acceptable steps in the deployment of a wireless network. This document is not intended
to replace other existing best practice documents from other organizations.
Agency compliance information

This section contains the Federal Communications Commission (FCC), Industry Canada
(IC) and Radio Frequency compliance statements for the OneWireless Multinode device.
FCC compliance statements

• This device complies with Part 15 of FCC Rules and Regulations. Operation is
subject to the following two conditions:
− This device may not cause harmful interference.
− This device must accept any interference received, including the interference that
may cause undesired operation.
• This equipment has been tested and found to comply with the limits for a Class A
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 radiofrequency energy
and, if not installed and used in accordance with these instructions, may cause
harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user is
required to correct the interference at his own expense.
• Intentional or unintentional changes or modifications must not be made to the
Multinode, unless under the express consent of the party responsible for compliance.
Any such modifications could void the user’s authority to operate the equipment and
voids the manufacturer’s warranty.
IC compliance statements
R120 OneWireless Planning Guide vii

• To reduce potential radio interference to other users, the antenna type and its gain
must be so chosen that the Equivalent Isotropic Radiated Power (EIRP) is not more
than that is permitted for successful communication.
• Operation is subject to the following two conditions.
− This device may not cause interference.
− This device must accept any interference, including interference that may cause
undesired operation of the device.
• The Class A digital apparatus complies with Canadian ICES-003.
Radio Frequency (RF) statement

To comply with FCC’s and Industry Canada’s RF exposure requirements, the following
antenna installation and device operating configurations must be satisfied.
• Remote Point-to-Multi-Point antennas for this unit must be fixed and mounted on
outdoor permanent structures, with a separation distance between the antennas of
greater than 20cm and a separation distance of at least 20cm from all persons.
• Remote Fixed Point–to-Point antennas for this unit must be fixed and mounted on
outdoor permanent structures, with a separation distance between the antennas of
greater than 20cm and a separation distance of at least 100cm from all persons.
• Furthermore, when using integral antennas the Multinode unit must not be co-
located with any other antenna or transmitter device and must have a separation
distance of at least 20cm from all persons.
European Union restriction

France restricts outdoor use to 10mW (10dBm) EIRP in the frequency range of 2,454-
2,483.5 MHz. Installations in France must limit EIRP to 10dBm, for operating modes
utilizing frequencies in the range of 2,454 – 2,483.5MHz.
For additional information

For more information on the Honeywell Multinode Device compliance, see the
OneWireless Multinode Agency Compliance Professional Installation Guide and the
OneWireless Multinode User's Guide.
viii OneWireless Planning Guide R120

Support and Other Contacts

United States and Canada
Contact: Honeywell Solution Support Center
Phone: 1-800-822-7673
Calls are answered by dispatcher between 6:00 am and 4:00 pm
Mountain Standard Time. Emergency calls outside normal working hours
are received by an answering service and returned within one hour.
Fascimile: 1-973-455-5000
Mail: Honeywell TAC, MS L17
1860 W. Garden Lane
Phoenix, AZ, 85027 USA
Europe, Middle East, and Africa (EMEA)

Contact: Honeywell TAC-EMEA
Phone: +32-2-728-2345
Fascimile: +32-2-728-2696
Mail: TAC-BE02
Hermes Plaza
Hermeslaan, 1H
B-1831 Diegem, Belgium
Pacific
Contact: Honeywell Global TAC – Pacific
Phone: 1300-364-822 (toll free within Australia)
+61-8-9362-9559 (outside Australia)
Fascimile: +61-8-9362-9564
Mail: Honeywell Limited Australia
5 Kitchener Way
Burswood 6100, Western Australia
Email: GTAC@honeywell.com
India
Contact: Honeywell Global TAC – India
Phone: +91-20- 6603-9400
Fascimile: +91-20- 6603-9800
Mail: Honeywell Automation India Ltd
56 and 57, Hadapsar Industrial Estate
Hadapsar, Pune –411 013, India
Email: Global-TAC-India@honeywell.com
Korea
R120 OneWireless Planning Guide ix

Contact: Honeywell Global TAC – Korea

Phone: +82-80-782-2255 (toll free within Korea)
Fascimile: +82-2-792-9015
Mail: Honeywell Co., Ltd
4F, Sangam IT Tower B4-4 Block
1590, DMC Sangam-dong, Mapo-gu
Seoul, 121-835, Korea
Email: Global-TAC-Korea@honeywell.com
People’s Republic of China

Contact: Honeywell Global TAC – China
Phone: +86- 21-2219-6888
800-820-0237
400-820-0386
Mail: Honeywell (China) Co., Ltd
33/F, Tower A, City Center, 100 Zunyi Rd.
Shanghai 200051, People’s Republic of China
Email: Global-TAC-China@honeywell.com
Singapore
Contact: Honeywell Global TAC – South East Asia
Phone: +65-6580-3500
Fascimile: +65-6580-3501
+65-6445-3033
Mail: Honeywell Private Limited
Honeywell Building
17, Changi Business Park Central 1
Singapore 486073
Email: GTAC-SEA@honeywell.com
Taiwan
Contact: Honeywell Global TAC – Taiwan
Phone: +886-7-536-2567
Fascimile: +886-7-536-2039
Mail: Honeywell Taiwan Ltd.
17F-1, No. 260, Jhongshan 2nd Road.
Cianjhen District
Kaohsiung, Taiwan, ROC
Email: Global-TAC-Taiwan@honeywell.com
Japan
Contact: Honeywell Global TAC – Japan
Phone: +81-3-6730-7160
x OneWireless Planning Guide R120

Fascimile: +81-3-6730-7228
Mail: Honeywell Japan Inc.
New Pier Takeshiba, South Tower Building,
20th Floor, 1-16-1 Kaigan, Minato-ku,
Tokyo 105-0022, Japan
Email: Global-TAC-JapanJA25@honeywell.com
Elsewhere
Call your nearest Honeywell office.
World Wide Web

Honeywell Solution Support Online:
http://www.honeywell.com/ps
Training Classes
Honeywell Automation College:
http://www.automationcollege.com
R120 OneWireless Planning Guide xi

Symbol Definitions
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol Definition
ATTENTION: Identifies information that requires special

consideration.
TIP: Identifies advice or hints for the user, often in terms of

performing a task.
REFERENCE -EXTERNAL: Identifies an additional source of

information outside of the bookset.
REFERENCE - INTERNAL: Identifies an additional source of

information within the bookset.
CAUTION Indicates a situation which, if not avoided, may result in equipment

or work (data) on the system being damaged or lost, or may result in
the inability to properly operate the process.
CAUTION: Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury. It may also be used
to alert against unsafe practices.
CAUTION symbol on the equipment refers the user to the product

manual for additional information. The symbol appears next to
required information in the manual.
WARNING: Indicates a potentially hazardous situation, which, if not

avoided, could result in serious injury or death.
WARNING symbol on the equipment refers the user to the product

manual for additional information. The symbol appears next to
required information in the manual.
xii OneWireless Planning Guide R120

Symbol Definitions
Symbol Definition
WARNING, Risk of electrical shock: Potential shock hazard where

HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or
60 VDC may be accessible.
ESD HAZARD: Danger of an electro-static discharge to which

equipment may be sensitive. Observe precautions for handling
electrostatic sensitive devices.
Protective Earth (PE) terminal: Provided for connection of the

protective earth (green or green/yellow) supply system conductor.
Functional earth terminal: Used for non-safety purposes such as

noise immunity improvement. NOTE: This connection shall be
bonded to Protective Earth at the source of supply in accordance
with national local electrical code requirements.
Earth Ground: Functional earth connection. NOTE: This

connection shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.
Chassis Ground: Identifies a connection to the chassis or frame of

the equipment shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.
R120 OneWireless Planning Guide xiii

Symbol Definitions
xiv OneWireless Planning Guide R120

Contents
1. HONEYWELL ONEWIRELESS SOLUTION ................................19

1.1 OneWireless components ............................................................................ 19
1.2 OneWireless mesh network ......................................................................... 20
1.3 OneWireless integration with Experion ...................................................... 21
One Wireless and Experion PKS systems ...........................................................................21
Functionality of OneWireless within Experion PKS ..............................................................21
Use of Multinode within Experion system.............................................................................22
Configuration of the multinode within Experion system ........................................................22
1.4
OneWireless server....................................................................................... 23
Importance of the OneWireless Key Server .........................................................................23
OneWireless server software ...............................................................................................23
Hardware requirements........................................................................................................23
1.5 Wireless Virtual LAN..................................................................................... 25
Enhanced wireless network security ....................................................................................25
1.6 OneWireless multinode devices .................................................................. 26
Wireless System Gateway ...................................................................................................26
Multinode..............................................................................................................................27
Power transmit settings ........................................................................................................27
1.7 OneWireless antennas.................................................................................. 27
1.8 OneWireless sensors.................................................................................... 27
1.9 OneWireless client nodes ............................................................................ 28
1.10 Authentication device ............................................................................... 28
Authentication device requirements .....................................................................................28
1.11 OneWireless software tools ..................................................................... 29
1.12 OneWireless security options .................................................................. 30
Multinode security options....................................................................................................30
OneWireless security features .............................................................................................31
2. ONEWIRELESS IMPLEMENTATION ..........................................33

2.1 Consulting and support services for OneWireless ................................... 33
Services provided.................................................................................................................33
Scope and key deliverables .................................................................................................33
R120 OneWireless Planning Guide xv

Contents
2.2 OneWireless installation requirements .......................................................34

Honeywell recommendation ................................................................................................ 34
OneWireless professional installation requirement.............................................................. 34
Important FCC note............................................................................................................. 34
RF safety, Maximum Permissible Exposure ........................................................................ 35
3. ONEWIRELESS SITE PLANNING .............................................. 37

3.1 Site planning checklist..................................................................................37
3.2 Site survey......................................................................................................38
Physical obstacles............................................................................................................... 38
Preventing interference ....................................................................................................... 38
Recommended RSSI........................................................................................................... 38
Environmental considerations ............................................................................................. 38
3.3 Node placement and coverage.....................................................................39
Multinode coverage area..................................................................................................... 39
Maximum communication path for wireless nodes .............................................................. 39
3.4 Frequency channel requirements for multinode radios ............................40
3.5 Use of multinode antennas...........................................................................41
Multinode antenna requirements ......................................................................................... 41
Approved multinode antennas............................................................................................. 41
3.6 Performing the site survey for mesh network installation ........................43
Site survey requirements..................................................................................................... 43
3.7 About radar signals .......................................................................................44
Dynamic frequency selection............................................................................................... 44
What happens when radar events are detected .................................................................. 44
What to do if there is radar interference .............................................................................. 44
Antenna positioning............................................................................................................. 45
3.8 Monitoring signal strength ...........................................................................46
3.9 Mesh tuning for optimal settings .................................................................47
3.10 Mesh link RSSI threshold ..........................................................................48
3.11 Mesh priority...............................................................................................48
Mesh priority configuration guidelines ................................................................................. 48
Mesh priority values to be used........................................................................................... 48
3.12 MAC address filtering ................................................................................49
3.13 Estimating performance ............................................................................50
Throughput based on signal strength .................................................................................. 50
Throughput based on “hops” ............................................................................................... 51
Throughput based on “Hops” and signal strength ............................................................... 52
xvi OneWireless Planning Guide R120

Contents
4. ONEWIRELESS NETWORK PLANNING ....................................53

4.1 Network planning checklist.......................................................................... 53
4.2 OneWireless topologies ............................................................................... 54
OneWireless integration with a small system .......................................................................54
Small system recommendations ..........................................................................................54
OneWireless integration with a large system .......................................................................55
OneWireless integration with Experion ................................................................................57
4.3 Connecting OneWireless network to the PCN ........................................... 58
Use of spanning tree ............................................................................................................58
Spanning tree root................................................................................................................58
Spanning tree priority configuration......................................................................................58
Additional OneWireless to PCN guidelines ..........................................................................59
4.4 Planning the OneWireless mesh network .................................................. 60
OneWireless mesh network guidelines ................................................................................60
About mesh hopping ............................................................................................................61
Nodes supported..................................................................................................................61
Total number of wireless transmitters supported..................................................................61
4.5 OneWireless communication....................................................................... 62
Data access for monitoring...................................................................................................62
Data access for control ........................................................................................................62
Wi-Fi and multinode protocols..............................................................................................62
4.6 Use of Network Time Protocol (NTP) .......................................................... 63
Direct synchronization ..........................................................................................................63
Indirect synchronization........................................................................................................65
4.7 Integrating OneWireless devices with HART ............................................. 66
Configuring the Lantronix device..........................................................................................66
5. ONEWIRELESS SECURITY PLANNING.....................................67

5.1 Security planning checklist.......................................................................... 67
5.2 About OneWireless security ........................................................................ 67
5.3 Sensor network security .............................................................................. 68
5.4 Mesh network security ................................................................................. 68
5.5 WiFi client security ....................................................................................... 69
5.6 WAP security ................................................................................................. 69
6. ADDING ONEWIRELESS TO AN EXISTING NETWORK ...........71
R120 OneWireless Planning Guide xvii

Contents
6.1 Network switch configuration ......................................................................71

About spanning tree on Cisco switches............................................................................... 71
General switch configuration ............................................................................................... 72
Rapid PVST spanning tree configuration ............................................................................ 72
Example of Rapid PVST spanning tree configuration on Cisco switch................................ 73
6.2 Multinode spanning tree configuration .......................................................77
MST spanning tree configuration......................................................................................... 77
Example of MST spanning tree configuration on Cisco switch ............................................ 78
xviii OneWireless Planning Guide R120

1. Honeywell OneWireless Solution
OneWireless from Honeywell is comprised of industrial wireless hardware devices and
wireless software tools. This section describes the OneWireless network and all its
components.
1.1 OneWireless components

The OneWireless network provides a multi-functional wireless mesh network that
supports sensors, actuators, and wireless-enabled applications within a single network to
optimize plant productivity and reliability, improve safety and security, and ensure
regulatory compliance. The OneWireless network includes the following components:
• OneWireless Server (Key Server & Wireless Tools)
• Wireless system gateway (WSG)
• Multinode
• Wireless Transmitters
• DCS Client or other client Node
R120 OneWireless Planning Guide 19

1.2. OneWireless mesh network
1.2 OneWireless mesh network

The Honeywell OneWireless network is a wireless co-operative communication
infrastructure between individual wireless devices, each of which is a multi-channel
repeater/transceiver. This type of decentralized infrastructure forms a mesh network.
Nodes act as repeaters to transmit data from nearby nodes to peer nodes that are too far to
reach, resulting in a network that can span large distances, especially over rough or
difficult terrain. Mesh networks are reliable because each node connects to several other
nodes. If one node drops out of the network due to hardware failure or any other reason,
its peers find another route.
20 OneWireless Planning Guide R120

1.3. OneWireless integration with Experion
1.3 OneWireless integration with Experion

Starting with Experion Release R311, Honeywell OneWireless product functionality is
integrated into the Experion PKS product. Within Experion PKS, the wireless process
I/O is treated the same as wired process I/O in terms of data, event, and alarm
information view, access, and configuration.
One Wireless and Experion PKS systems

The following diagram shows an OneWireless network integrated with the Experion
system.
L3/L4 Gateway
L3 PCN
L3 Router
ACE ESV ESC ESF
L1/L2 PCN
FTE L1/L2 Gateway Authentication

L2 Switches Device
Switch
L1 Switches
CF9 CF9
L1/L2 Gateway
PM PM Wireless Mesh Network
I/O I/O
FIM
C300
I/O I/O I/O I/O
Series A I/O
PM
PM PM
PM
I/O
I/O I/O
I/O
Industrial Wireless
I/O ControlNet Field I/O Mobile Station
FTEB + Series A I/O
Transmitters IntelaTrac PKS
Functionality of OneWireless within Experion PKS

Once integrated, the Wireless System Gateway, Multinode, and XYR 6000 Transmitter
wireless nodes exist within the Experion PKS system. The Wireless System Gateway is a
peer with ACE/C200/C300 controllers, and the OneWireless Server is replaced with the
Experion PKS Server. If you are integrating OneWireless with Experion, you should use
the Engineering Tools instead of the OneWireless Server Tools. Because the
OneWireless Server Tools were originally derived from EPKS Engineering Tools, they
contain the same infrastructure (ERDB, Engineering Repository Server, System
Repository, CDA Server, and so on).

1.3. OneWireless integration with Experion
Use of Multinode within Experion system

The multinode has three antennas, which are used for the following purposes:
• Wi-Fi access point
• Mesh network
• Sensor network
Multinodes should be strategically located to achieve the following within the Experion
system:
• Form a mesh network with multiple redundant paths
• Provide dual sensor network communication paths to each XYR 6000 Transmitter
• Increase the Wi-Fi coverage for Wireless Worker client applications within the
customer’s installation.
Configuration of the multinode within Experion system

You configure one or more multinodes to enable Wireless System Gateway (WSG)
functionality in addition to its multinode responsibilities. The WSG has the
responsibility of presenting XYR 6000 Transmitter information for you to use.
The transfer of sensor data is the first priority of the mesh network, and the remaining
bandwidth can be used for Wi-Fi traffic such as Mobile Station and IntelaTrac PKS.

1.4. OneWireless server
1.4
OneWireless server
The OneWireless server node is the primary Key Server and application server for the
OneWireless network. If you are integrating with Experion, the OneWireless Server is
replaced with the Experion PKS Server.
If you are not integrating with Experion, you should place the OneWireless Server in the
OneWireless subnet.
As the Key Server, it acts as the center of trust for the network by generating, issuing,
and managing security keys. All devices on the industrial wireless network must be
authenticated to join the secured network. This node is also used for initial configuration
of wireless devices and to store wireless network system data for configuring wireless
devices.
Importance of the OneWireless Key Server

The availability of the OneWireless system depends on the Key Server. If the Key Server
is compromised, the security of the OneWireless network may be jeopardized. The
following are requirements for the Key Server.
• The communications to the Key Server must be over a secure channel.
• The Key Server must be able to handle all requests with minimum latency.
• Physical access to the Key Server must be limited and must be secure.
OneWireless server software
The software loaded on the OneWireless server includes the following:
• Key Server Manager
• Wireless Builder
• Directory Server
• Security Server
• Network Tools Server
• OPC Server
Hardware requirements
The PC platform that serves as the OneWireless server node must meet the following
minimum requirements.
• Pentium 4, single processor 2.4 GHz
• 1 GB RAM

1.4. OneWireless server
• 40 GB hard disk space with at least 10 GB free for the OneWireless software tools
• Operating System must be Microsoft® Windows® 2003 Server or Windows® XP
• Ethernet capable with wired network access to the wireless gateway
• DVD drive

1.5. Wireless Virtual LAN
1.5 Wireless Virtual LAN

According to the IEEE, VLANs define broadcast domains in a Layer 2 network. VLANs
can group the multinodes to the same LAN segment, regardless of the multinode’s
geographical location. To interconnect two different VLANs, routers or Layer 3 switches
are used.
Wireless VLAN is an extension of Layer 2 wired VLAN (WLAN) in wireless LAN
environment. Wireless VLANs can segregate the WLAN network into disjoined sections,
each of which can serve a different purpose or users.
When VLAN is enabled, all data coming out of the WAN port is VLAN-tagged. This
indicates that an external network unit, such as a router switch or a VLAN-enabled
computer is used for terminating the VLAN traffic. The broadcast traffic is terminated
and isolated by Layer 3 devices (for example, a router or Layer 3 switch does not route
broadcast traffic from one VLAN to another).
With OneWireless R120, multiple wireless VLANs are supported to align with the
Honeywell Systems Network and Security.
Enhanced wireless network security

When wireless VLAN is enabled, an access point can be configured to have multiple
SSIDs to support multiple wireless networks. Each network, per configuration, belongs
to a VLAN. Each wireless VLAN can set its own security level.

1.6. OneWireless multinode devices
1.6 OneWireless multinode devices

The multinode devices form the backbone of the OneWireless network by creating the
mesh network. A multinode device, depending on how it is configured, acts as a gateway
or as a multinode. Because of the power transmission settings and FCC regulations, the
multinodes must be professionally installed. Each multinode device contains one
Frequency Hopping Spread Spectrum (FHSS) radio and two IEEE 802.11a/b/g access
point and mesh radios, as shown in the following figure.
Wireless System Gateway

The Wireless System Gateway (WSG) is a multinode device whose operating mode has
been configured as a gateway, using the Multinode Configuration Tool and defined as the
WSG using Wireless Builder. The WSG connects the mesh network to the plant control
network.

1.7. OneWireless antennas
Multinode
The multinode is a device for which the operating mode has been configured as a
multinode using the Multinode Configuration Tool. The multinode facilitates multinode
communications between the wireless devices and the WSG, and between the wireless
transmitters.
Power transmit settings

The power transmit settings for the multinode radios can be adjusted by an authorized
professional installer using Honeywell tools. The correct power transmit setting must be
calculated based on the cable length, antenna type, and the maximum allowed Equivalent
Isotropically Radiated Power (EIRP) value. Honeywell has determined optimal values to
be used for the power settings through agency certification testing. Refer to the
OneWireless Multinode Agency Compliance Professional Installation Guide for details
on adjusting these settings. Refer to the OneWireless System Administration Guide, for
more information about adaptive transmit power control.
1.7 OneWireless antennas

Honeywell has tested and approved the following types of antennas for use with the
multinode’s radio transmitters.
• Omni directional (integral and remote), Point to Multi-Point
• Sector (remote), Point to Multi-Point
• Directional YAGI (remote), Point to Multi-Point
• Directional DISH (remote), Fixed Point to Point.
See the OneWireless Multinode Agency Compliance Professional Installation Guide for
antenna specifications and additional details, including part numbers.
1.8 OneWireless sensors

OneWireless sensors are XYR6000 wireless transmitters. These are industrial wireless
field devices such as a wireless temperature, pressure, HLAI or corrosion transmitters
that transmit data to wireless multinodes. They are sometimes referred to as leaf nodes.

1.9. OneWireless client nodes
1.9 OneWireless client nodes

Client nodes within the OneWireless network are used to communicate with the
OneWireless server node. Associated software on a client node includes the following:
• OPC DA/AE
• Modbus Serial
• Modbus TCP.
A network client node with network management software can also communicate with
the OneWireless Server for network maintenance and troubleshooting.
1.10 Authentication device

The OneWireless authentication devices is a Personal Digital Assistant (PDA) that runs
Windows Mobile 4.2 with IR capability and Honeywell OneWireless authentication
software installed. The authentication device receives security keys from the
OneWireless server and then transmits a security key to each wireless device. Without a
valid security key, the wireless device cannot be authenticated and is not allowed to join
the industrial wireless network.
Authentication device requirements

The PDA used as the authentication device must meet the following requirements.
• Rated for use in Class 1, Div 2/Div 1 industrial environments, if the wireless devices
are installed in hazardous locations
• Runs Windows Mobile 4.2+ and has IR capability
• A secure password
• PDA docking station.

1.11. OneWireless software tools
1.11 OneWireless software tools

Software tools used in a Honeywell OneWireless system are packaged on an
OneWireless tools media or embedded on the multimode device. The following table
describes the software tools used in a Honeywell OneWireless system.
Software Description
The following software programs are available on the Honeywell OneWireless

Software Tools media
Key Server Provides user interface for generating and managing wireless
Manager security keys. Contains database to store information about the
secured devices. Use to manage network security.
Wireless Builder Use to configure wireless transmitters and gateways and their
associations. Use to calibrate wireless transmitters and to
upgrade their firmware. Can also be used to read PV data and
validate the online status of the wireless devices.
Directory Server Automatically assigns Honeywell Wireless network address for

the multinodes, WSG, and the wireless transmitters. Maintains
the fixed address range 0xFXXX for the WSG.
OPC Server The OLE for Process Control (OPC) server that provides open
access to all device data.
Network Tool for managing and diagnosing a mesh network comprised of

Management multinodes and wireless transmitters. The tool has a GUI that
and Diagnostics displays nodes within the mesh network and their communication
Tool status.
Authentication Software that you load on the handheld Personal Digital Assistant
Device software (PDA) so that it can function as an authentication device.
The following software programs are preloaded on the multinode.
Multinode Software that is embedded on multinode devices. Includes Web

Configuration Server/HTTPS; SNMP agent; ping utility; trace route utility;
Tool firmware upgrade utility, factory default settings; signal strength
reporting.

1.12. OneWireless security options
1.12 OneWireless security options

A number of security options can be configured for the OneWireless network. See the
“OneWireless Security Planning” section, for guidelines on implementing security.
Multinode security options

Following is a list of the security configuration options, for the multimode WiFi/mesh
communications.
• WEP 64, 128, and 152-bit encryption
• WPA-PSK
• WPA (802.1x) - Dynamic Key
• WPA2/802.11i
• AES-CCM and AES-CCMP with TKIP
• Enable/disable broadcast SSID
• Multiple SSIDs support for layered and secure routing
• MAC address filtering
• Rogue wireless AP detection with e-mail notification
• Wireless AP and wireless client activities monitoring MAC address listing of the
wireless clients
• Support for 50 Wireless VLANs (802.1Q)
Following is the list of the security configuration options, for the multinode FHSS
communications.
• AES
• HTTPS/TLS secure Web

OneWireless security features

• Mutual authentication – both client and server must authenticate with each other
• End-to-end encryption – user data is not allowed to appear in clear text, except at
authorized end points
• Per-client keys – keys are unique for each authorized user
• Key distribution –central management of security keys
• Full support for mobility –users need to move from access point to access point,
without interruption
• Rotating security keys – supports rotating security keys for the secure sessions
between a field device and a multinode.


2. OneWireless Implementation
2.1 Consulting and support services for OneWireless
Honeywell’s wireless network design experts combine their knowledge of Radio
Frequency (RF) fundamentals and signal propagation with their experience in process
control systems, network security, and advanced applications to help you design a high
performance wireless network.
Services provided
Honeywell’s approach to creating a system and network design includes:
• An on-site study of the coverage area desired at the plant
• Existing power and network infrastructure
• The goals for the implementation (both immediate and future)
• A thorough assessment of interfering and operating frequencies currently in use or
ambient in the environment
Honeywell takes particular care to insure robust security and document security
requirements, identify network security threats, review existing security practices,
procedures and safeguards, and identify the causes of any potential security exposures.
Scope and key deliverables

The OneWireless™ System and Network Design report provides:
• Network topology drawing, reflecting switches and access point connection to the
network point of entry at each location
• Complete bill of materials required for implementation
• Detailed analysis report reflecting the following:
− Signal strength, integrity, and speed
− Recommended antennae type and location
− Precise infrastructure placement and mounting
− Interference sources and characteristics
− Best practices related to RF network security and maintenance.

2.2. OneWireless installation requirements
2.2 OneWireless installation requirements

Honeywell recommendation
Honeywell does not recommend using devices for critical control where there is a single
point of failure or where single points of failure result in unsafe conditions. The initial
release of OneWireless is targeted at open loop control, supervisory control, and controls
that do not have environmental or safety consequences. As with any process control
solutions, the end-user must weigh the risks and benefits to determine if the products
used are the right match for the application based on security, safety, and performance.
Additionally, it is up to the end-user to ensure that the control strategy sheds to a safe
operating condition, if any crucial segment of the control solution fails.
OneWireless professional installation requirement

An authorized professional must install the OneWireless XYR 6000 transmitters and
multinode devices. The Federal Communications Commission (FCC) classifies these
devices as professional install devices because they require manual power limit settings
for use with higher gain antennas. This is to ensure Radio Frequency (RF) output power
does not exceed the limits established by the FCC or Radio and Telecommunications
Terminal Equipment Directive (R&TTE).
Honeywell maintains two controlled documents that contain critical installation
requirements for the OneWireless multinode and transmitter that is made available only
to authorized professional installers. The professional installer must read these
documents before installing antennas or making any power adjustments to the devices.
• OneWireless Multinode Agency Compliance Professional Installation Guide
• OneWireless XYR 6000 Transmitter Professional Installation Guide
Important FCC note

Intentional or unintentional changes or modifications must not be made to the multinode,
unless under the express consent of the party responsible for compliance. Any such
modifications could void the user’s authority to operate the equipment and also voids the
manufacturer’s warranty.

RF safety, Maximum Permissible Exposure

To comply with FCC’s and Industry Canada’s Maximum Permissible Exposure (MPE)
specifications, the following antenna installation and device operating configurations
must be satisfied:
• Remote antenna(s) for the multinode devices must be fixed and mounted on outdoor
permanent structures with a separation distance between antennas of at least 20 cm
and a separation distance of at least 20 cm from all persons.
• When using integral antenna(s), the multinode device must not be co-located with
any other antenna or transmitter device, and it must have a separation distance of at
least 20 cm from all persons.


3. OneWireless Site Planning
This section contains information about the site requirements and considerations.
3.1 Site planning checklist

Consideration
Physical obstacles that may be a barrier to proper signal path
External or internal sources of radio interference
Hazardous location certifications for each of the wireless devices (see the
device’s specific user’s guide)
Coverage area required for each multinode

Communication path for each wireless device
Optimal number of multinodes in the network, based on number of supported

wireless transmitters, bandwidth, and placement restrictions
Balance of the transmission rate of wireless transmitters with the battery life
Locations of the wired network access
Power access requirements for the multinodes
Frequency requirements and channel allocation
Transmit power settings
Antenna selection.
Antenna mounting and placement requirements.

3.2. Site survey
3.2 Site survey

A thorough site survey includes a radio frequency survey and an evaluation of all the site
characteristics to determine the optimal placement and operating conditions for all the
OneWireless devices.
Physical obstacles
Consider all the physical obstacles that may be barriers to proper signal path. Learn as
much as you can about the environment in which you are planning to deploy the
OneWireless system. If the surrounding area is congested with metal and cement type
structures, a radio signal might be much more limited than if it were passing through
wood/drywall types of structures.
Preventing interference
Consider whether or not there are external or internal sources of radio interference
frequency present at the site. Potential problems can come from microwave ovens, 2.4-
GHz wireless phones, wireless video security monitors, and other IEE 802.11a/b/g
wireless networks. You may need to experiment with the placement of access points and
settings to see which combination provides the best access.
Recommended RSSI
While FHSS radio sensitivity is around -93 dBm, typical industrial installations must
cope with various sources of noise, non-line of sight conditions, and many signal-
attenuating obstructions. As a result, the recommended Receive Signal Strength Indicator
(RSSI) as measured on the XYR6000 wireless transmitters must be at least -70 dBm for
best results. Better RSSI values result in better link quality, fewer retries and higher
reliability of data delivery.
Environmental considerations
The completely assembled multinode device conforms to FM electrical equipment
requirements for use within Class I, Division 2, Groups A, B, C and D/Zone 2, Group IIC
hazardous locations. For each of the wireless transmitter types, see its user’s guide for the
hazardous location certifications.

3.3. Node placement and coverage
3.3 Node placement and coverage

When planning the OneWireless mesh network, you must consider the number of nodes
and their placement.
Multinode coverage area

When planning the physical placement of the multinodes, consider the amount of overlap
in signal coverage. Honeywell recommends at least a 30% overlap in coverage. You can
adjust the transmit power to reduce or increase the signal to optimize the overlap instead
of moving the multinodes closer or farther apart. When adjusting the transmit power
level, however, you must be careful to not exceed the maximum radio output power
value specified in the OneWireless Multinode Agency Compliance Professional
Installation Guide (available to authorized professional installers).
Maximum communication path for wireless nodes

The following table lists the communication path between each type of wireless devices
and its maximum operating distance. Multinode to multinode communication varies
depending on the type and placement of the antennas.
Communication path Distance in feet Distance in km
Wireless transmitter to multinode 2000 feet .6 km

1
Multinode to multinode 3000 feet Approximately 1 km1
802.11a Wi-Fi Client to multinode 3000 feet Approximately 1 km
802.11b/g Wi-Fi Client to 3000 feet Approximately 1 km

multinode
The multinode supports communications up to 6 miles or 10 km with high gain

antennas.

3.4. Frequency channel requirements for multinode radios
3.4 Frequency channel requirements for multinode

radios
The following table summarizes the channel allocations for the three types of multinode
radios.
Radio type Frequency channel requirements
Mesh radio (802.11): All mesh radios must use the same channel as all
communicates with other other mesh radios to form a mesh network. The
multinodes to form the channel used must be a different channel from the
mesh network. WiFi and FHSS radio channels.
Assign the least used channel to the Mesh radio

(highest preference to mesh networking).
If possible, use the 5.8 GHz band to avoid

interference with the FHSS or WiFi radio.
FHSS radio: All FHSS radios must use the same channel as all
communicates with the other FHSS radios, but it must be a different channel
wireless transmitters. from the one used by the Mesh and WiFi radios.
Assign the second least used channel to the FHSS

radio.
If all three channels are used, the FHSS radio must

be run in the Inter-cannel mode. In this mode, it runs
in the voids between channels.
Client WiFi (802.11): WiFi radios may be on different channels from one
communicates with PC- another, but any channels used must be different
like devices from the ones used by the Mesh or FHSS radio.
Assign the third least used channel to the Client WiFi

(lowest preference to client applications).
Channels can be alternated as long as they do not

interfere with the FHSS or Mesh radio.

3.5. Use of multinode antennas
3.5 Use of multinode antennas

Multinode antenna requirements
To comply with FCC’s and Industry Canada’s RF MPE specifications, the multinode
antenna installation must meet the following requirements.
• Remote antenna(s) must be fixed and mounted on outdoor permanent structures with
a separation distance between the antennas of at least 20 cm and a separation distance
of at least 20 cm from all persons.
• Integral antennas must not be co-located with any other antenna or transmitter device
and must have a separation distance of at least 20cm from all persons.
Approved multinode antennas

The following table lists antennas that are qualified for use with multimode devices and
defines the operating conditions for each antenna type.
Peak Agency
Antenna Antenna Beam Freq.
Gain Complian
Type Application Width (GHz)
(dBi) ce
Approved Antenna Types/Gains - FHSS Radio
FCC, IC,
Omni Point to
Omni 5 2.4 ETSI,
(integral) Multi-Point
ACMA
FCC, IC,
Omni Point to
Omni 8 2.4 ETSI,
(remote) Multi-Point
ACMA
FCC, IC,
Sector Point to
120° 14 2.4 ETSI,
(remote) Multi-Point
ACMA
Approved Antenna Types/Gains - IEEE 802.11a/b/g Radios
FCC, IC,
2.4
4.5 ETSI,
(802.11b/g)
ACMA
Omni Point to
Omni 5.4
(integral) Multi-Point ETSI
(802.11a)
7
5.8 FCC, IC,
(802.11a) ACMA

3.5. Use of multinode antennas
Peak Agency
Antenna Antenna Beam Freq.
Gain Complian
Type Application Width (GHz)
(dBi) ce
FCC, IC,
Omni Point to 2.4
Omni 8 ETSI,
(remote) Multi-Point (802.11b/g)
ACMA
Omni Point to 5.4
Omni 12 ETSI
(remote) Multi-Point (802.11a)
Omni Point to 5.8 FCC, IC,
Omni 12
(remote) Multi-Point (802.11a) ACMA
FCC, IC,
Sector Point to 2.4
120° 14 ETSI,
(remote) Multi-Point (802.11b/g)
ACMA
Sector Point to 5.4
90° 17 ETSI
(remote) Multi-Point (802.11a)
Sector Point to 5.8 FCC, IC,
90° 17
YAGI Point to 5.8 FCC, IC,
19° 16.5
DISH Fixed Point 5.4
9° 23 ETSI
(remote) to Point (802.11a)
DISH Fixed Point 5.8 FCC, IC,
9° 24
(remote) to Point (802.11a) ACMA

3.6. Performing the site survey for mesh network installation
3.6 Performing the site survey for mesh network

installation
A detailed site survey must always be conducted before the installation and deployment
of a mesh network. For best results, use the multinode configuration tool with other site
survey tools.
The actual throughput of the mesh network depends on many external factors and good
survey input, channel selection and antenna choice and installation contributes to better
performance. You can configure specific parameters on the multinode so that the mesh
networks can be tuned and customized for your specific site.
When operating in Europe, pay special attention to possible radar signal existence in the
deployment site, and if radar signal existence is confirmed, channels without radar
signals must be used for mesh operations.
Site survey requirements

The site survey must, at the minimum, meet the following requirements.
No Item
1 The site survey must be conducted when the factory system is operating,
so that the maximum possible interference is measured and considered.
2 An RF spectrum analysis on 2.40-2.49 GHz band and 5.7-5.9 GHz to

detect any potential RF interference.
Strong interference sources must be dealt with (removed or avoided)

before an installation.
3 A point-to-point 2-node mesh setup in various locations to quantify the

RF propagation ability in the particular environment.
A Received Signal Strength Indicator (RSSI) can serve as one indicator

of the RF environment.
TCP/IP throughput testing, UDP/IP throughput, and packet drop rate

testing must be conducted in all the selected locations to quantify the
quality of the environment.

3.7. About radar signals
3.7 About radar signals

802.11b/g uses the unlicensed 2.4 GHz band. 802.11a uses the unlicensed 5 GHz band. In
many countries, 5 GHz is also used by radar, and regulations state that radar has higher
priority. If the 802.11a devices detect the existence of a radar signal in which it is
operational, will have to hop to a different frequency.
Dynamic frequency selection

Dynamic Frequency Selection (DFS) is supported in all European countries, so you must
consider potential radar interference when multinodes are deployed in Europe. In the
U.S., the multinode supports only channels without the DFS requirement, so radar
interference is not an issue. It is important to validate the presence of radar before
deploying the wireless mesh network. Before you install any equipment, contact the local
authorities to obtain information about any known nearby radar installation for weather
forecast, military, or an airport. Also, if located near a harbor, consider that passing or
incoming ships may use radar that affects the mesh network, and if the ships are not
present during the site survey, the radar is not detected.
What happens when radar events are detected
If during operation, a multinode detects a radar event over the Radio Frequency (RF)
channel that the mesh network uses, it must immediately stop operation or change to
another available RF channel. This requirement is dictated by Federal Communications
Commission (FCC) and European Telecommunications Standards Institute (ETSI)
standards, and is established to allow the sharing of the 5 GHz spectrum between
wireless LAN (WLAN) and military or weather radars that use the same frequencies. As
of firmware release 4.1 build 12, the mesh radio stops its operation when a radar signal is
detected.
What to do if there is radar interference
In cases where severe radar interference is detected, it is possible to build the network
using the 802.11g 2.4GHz band instead of the 802.11a 5GHz band. The mesh radio
shares the 2.4GHz band with the Access Point radio and the FHSS radio. They must be
configured to use distinctly separate channels. This represents a technical alternative for
sites too close to a powerful radar source.

3.7. About radar signals
Antenna positioning
Depending on the site survey results and the specifics of the installed environment,
proper antenna type (omni-directional vs. directional, low-gain vs. high gain, etc) must
be selected. Antennas play critical roles in the setup and operation of wireless mesh
systems, and studies have shown that the 5.8 GHz band is particularly sensitive to the
positioning of antennas. Lab testing has shown that a simple tilt of the receiving antenna
can vary the received signal strength by 14 dbm. Careful positioning of mesh antennas
during deployment can make a big difference in the performance of the mesh network.

3.8. Monitoring signal strength
3.8 Monitoring signal strength

The multinode has a site survey tool that can be used to monitor the received signal
strength of all wireless devices it can hear. The tool must be used during the site-survey
and during deployment for optimal antenna positioning. Refresh the page to get the most
recent RSSI readings.
To open the monitoring tool, perform the following steps.
Step Action
1 Open Internet Explorer and type the following default URL for the multinode
in the address bar, to access the multinode’s configuration tool.
https:// <ip address>
Where ip address is the IP address of the multinode.

2 On the initial screen, type your user name and password and then click Sign
In.
3 From the left pane of the Multinode Configuration Tool, choose
Monitoring/Reports > Adjacent AP List.
4 Refresh the page.

3.9. Mesh tuning for optimal settings
3.9 Mesh tuning for optimal settings

Due to the variety in installation environments, the default configuration/parameter
settings of the mesh network may not be the optimal settings for your site. Following are
the important parameters you can adjust to customize the mesh to its optimal
performance.
• Mesh link RSSI threshold
• Mesh priority
• MAC address filtering

3.10. Mesh link RSSI threshold
3.10 Mesh link RSSI threshold

The RSSI threshold value is checked when a node tries to establish a link with another
node. Both nodes checks the RSSI of its partner against its configured threshold value. If
the RSSI is lower than the threshold value on either side, the link between them is not
established. If the RSSI threshold is too small, the node establishes links with all the
available nodes, even though quality of the link may not be good. Too many links in the
mesh network can result in unnecessary frequent changes of the topology. If the RSSI
threshold is too large, the node may not link with other nodes and isolate itself. This is an
undesirable situation. The proper RSSI threshold must guarantee 2-4 links on each node.
3.11 Mesh priority

Mesh priority sets the 802.1D/ RSTP (Rapid Spanning Tree Protocol) mesh priority. If a
switch that implements RSTP is used, it must be the root of the spanning tree, which
means it must have the highest mesh priority. Mesh priority can also be used to direct
the path from the perimeter multinodes back to the wired gateway. The lower the value
used, the higher the mesh priority.
Mesh priority configuration guidelines

Following is a summary of the mesh priority guidelines.
• Configure the switch to have a higher priority than the default gateway.
• Configure the default gateway to have a higher priority than any other multinode.
• Configure any wired multinode (one that connects directly to the mesh network
through its wired Ethernet link) to have higher priority than any wireless multinode.
• Configure all wireless multinodes to have the same priority that is lower than all
other device types.
Mesh priority values to be used

The latest revision of 802.1D requires the priority to be set to a multiple of 4096.
Therefore, the value must be one of the following:
4096 8192 12288 16384 20480 24576 28672 32768
36864 40960 45056 49152 53248 57344 61440

3.12. MAC address filtering
3.12 MAC address filtering

MAC Address Filtering can be used to further customize the mesh network (only
available in auto-mesh mode)
In some cases, you may want to specifically link to one or a few nodes. You can use
MAC Address Filtering to achieve this. For example, if one multinode (A) is used to
stream video to another multinode (B) that is not the ROOT node, you can specify A to
always connect to B and maybe another node for link backup. This allows video to be
delivered using the shortest path to B.
You can also use the MAC Address Filtering to specify that a set of nodes must NOT be
connected.

3.13. Estimating performance
3.13 Estimating performance

The values from the two tables (Throughput based on signal strength and Throughput
based on “hops”) are based on a best-case scenario. That is, there is little to no 5.8GHz
RF interference sources present while the data is passed. The values are also based only
on the mesh link radio, which means it does not take into account the stability of the link
for the Sensor radio to the sensors nor the wireless client link to the access point radio of
the Multinode.
Throughput based on signal strength

The theoretical data rates and throughput values for the corresponding signal strengths
for wireless bridge connectivity are displayed in the following table. These throughput
values are based on a single point-to-point link between two multinodes.
Signal strength Data rate Throughput
> = 72 54 Mbps 22 Mbps
69% 48 Mbps 20 Mbps
66% 48 Mbps 20 Mbps
63% 36 Mbps 17 Mbps
60% 36 Mbps 17 Mbps
57% 24 Mbps 11 Mbps
45% 24 Mbps 11 Mbps
42% 18 Mbps 9 Mbps
36% 18 Mbps 9 Mbps
33% 12 Mbps 6 Mbps
30% 12 Mbps 6 Mbps
27% 9 Mbps 4.5 Mbps
24% 9 Mbps 4.5 Mbps
< 21% 6 Mbps 3 Mbps
<18% < 6 Mbps < 3 Mbps

Throughput based on “hops”

The throughput values through a specified number of “hops” are shown in the following
table. Hops are defined as the number of devices through which the data must pass to
reach its destination.
Signal
strength 1 Hops 2 Hops 3 Hops 4 Hops
100% 22.0 Mbps 11.0 Mbps 7.3 Mbps 5.5 Mbps

Throughput based on “Hops” and signal strength
25.0
Throughput in Mbps
20.0
15.0
10.0
5.0
0.0
100% 69% 63% 57% 42% 33% 27% 21% 18%
Signal Strength
1 2 3 4
Signal Strength
Hops
100% 69% 63% 33
57% 42% % 27% 21% 18%
1 22.0 20.0 17.0 11.0 9.0 6.0 4.5 3.0 1.0

Throughput in
2 11.0 10.0 8.5 5.5 4.5 3.0 2.3 1.5 0.5
3 7.3 6.7 5.7 3.7 3.0 2.0 1.5 1.0 0.3

Mbps
4 5.5 5.0 4.3 2.8 2.3 1.5 1.1 0.8 0.3

4. OneWireless Network Planning
To adequately design and install the OneWireless network, you must consider and
provide for additional physical network components such as servers, access points,
router, switches, firewall, and so on. This section contains basic information about the
network planning. See also the Honeywell best practices document for OneWireless.
4.1 Network planning checklist

Consider the following network requirements before installing your OneWireless
network.
Network Requirements
The recommended OneWireless network topologies
OneWireless network connected to the Process Control Network

Mesh network configuration
Mesh hopping limitations
Subnets or domains for the OneWireless network
IP address distribution
Single or redundant gateways
Switch configuration
Firewall configuration
Use of spanning tree
Type of NTP setup

4.2. OneWireless topologies
4.2 OneWireless topologies

OneWireless topologies consist of small and large systems. Small systems that consist of
a single controller and minimal HMI and large distributed control systems with multiple
layers of security are considered separately, from the network topology point of view.
Small systems are typically not connected to the Internet and have higher tolerance to
security risks. Large layered systems typically follow Purdue security model.
OneWireless integration with a small system

Small system topologies consist of a minimal process controller and HMI equipment that
can be connected to the OneWireless system directly as shown on the following figure.
Small system recommendations

The OneWireless server and gateways are connected to the same subnet as controllers
and HMI. Other wireless PC-based nodes such as laptops and tablet PCs may be
connected to the OneWireless infrastructure.
Controllers may access wireless data through the gateway using Modbus TCP or serial
Modbus through a Modbus TCP to Serial Modbus converter. Only process variables and
device status are available through Modbus.
HMI devices typically access wireless data through an OPC connection from the
OneWireless Server. Configuration, diagnostic and run-time data provided by wireless
devices are available through OPC.

OneWireless integration with a large system

Large control system topologies use layered network architecture based on the Purdue
security model. Wireless networks present a unique challenge to the layered approach, as
wireless network infrastructure cannot be duplicated for each level and must be used for
multiple purposes at the same time. The best practice approach for deploying
OneWireless network infrastructure is to place it on the dedicated subnet routed to the
rest of the PCN. OneWireless subnet connects to the L3 router just like any other L2
subnet as shown on the following figure.
Large systems based on Experion

Large system not based on Experion
Large system recommendations

The OneWireless network must exist as either a dedicated separate VLAN in the level 3
switch (es) or be on its own switch (es) and connect to the level 3 switch (es) through
routed port(s). Honeywell currently requires that level two FTE networks connect to
level three through routed port(s). In either case, the OneWireless network routes to the
level 3 network and to the level 2 networks, as necessary.

OneWireless integration with Experion

Experion system recommendations
The OneWireless network is connected to the Level 2 network. Wireless System
Gateway is connected to a Level 2 switch. The OneWireless firewall is a new Experion
certified device that is required in this topology. It is designed to protect the wireless
network from unwanted data, such as the FTE broadcasts. However, it allows the CDA
communication between the Wireless System Gateway and the OneWireless Server and
Experion servers. All wireless I/O data goes through the Wireless System Gateway while
other data types goes through the multinode connected to the process control network at
the wireless DMZ.

4.3. Connecting OneWireless network to the PCN
4.3 Connecting OneWireless network to the PCN

Honeywell recommends you establish a separate IP subnet for the OneWireless network.
Connect the OneWireless network to the Plant Control Network (PCN), as a routed
segment off the Level 3 switch, using one of the following methods.
• Establish a dedicated separate VLAN in the Level 3 switch and use it to connect to
the OneWireless network.
• Use separate switch (es) for the OneWireless network and connect to the Level 3
switch using the routed port(s).
See also "Adding OneWireless to an Existing Network" on page 71 for implementation
guidelines.
Use of spanning tree

Honeywell recommends the OneWireless network VLAN in the level 3 switch (es) or the
OneWireless network separate switch (es) that connect to the level 3 switch (es) through
routed port(s) use MSTP (Multiple Spanning Tree Protocol). At a minimum, spanning
tree must be enabled and be compatible with Rapid Spanning Tree Protocol (RSTP). See
the "Multinode spanning tree configuration" section for an example of MSTP
configuration.
Spanning tree root

The root of the spanning tree must be a Level 3 router or a switch closest to the Level 3
router. The second best choice is to make one of OneWireless gateways a root.
Configuring one of the Multinodes to be a root of the spanning tree can cause serious
communication problems and must be avoided.
Spanning tree priority configuration

Spanning tree formation is controlled by assigning mesh priority. Assign the highest
mesh priority (lowest values) to nodes that becomes spanning tree roots. The following
figure shows an example of spanning tree mesh priority with the lower values indicating
preferred root position.

4.3. Connecting OneWireless network to the PCN
Additional OneWireless to PCN guidelines

• Control OneWireless network visibility with static network routes. Do not use
dynamic routing protocols in the PCN.
• Assign each device on the OneWireless network a static IP address. Do not use
DHCP.
• Microsoft Windows nodes on the OneWireless network must be members of the
PCN active directory domain and must participate in Microsoft patching and anti-
virus software updates systems.
• Consider using Access Control Lists (ACLs) in the level three switch (es) to restrict
traffic to and from the OneWireless network and the various PCN levels.
• Optionally, consider placing a stateful firewall that provides routing services
between the level 3 networks and the OneWireless network.
• If you replace a multinode, the replacement must have the same IP address, as the
node being replaced.

4.4. Planning the OneWireless mesh network
4.4 Planning the OneWireless mesh network

The deployment of a OneWireless mesh network permits significant flexibility resulting
in a large number of variations based on the site conditions. This section provides
guidelines for configuring an optimal OneWireless mesh network.
OneWireless mesh network guidelines

• Mesh network radio must use 802.11a bands in 5.8 GHz frequency range (whenever
possible) or what is allowed by the local regulations. Running mesh at 5.8 GHz
allows to simplify the frequency planning within more crowded 5.8 GHz band.
• Wireless sensor frequency must be configured to use one of the non-overlapping 2.4
GHz 802.11 bands that are not used for either mesh or WiFi client access. If all
802.11 channels are used, select guard-band mode of operation for the sensor radio.
• Avoid excessive number of mesh hops to the final destination. The maximum
number of hops from leaf device to WSG is four. That is, there can be four
Multinodes between the client device and the WSG. Every time the network traffic
hops from one mesh link to another, the available bandwidth is cut in half.
• Place high throughput network devices such as cameras no further than one hop
away from the WSG. Multiple hops must only be used when direct single hop is not
possible. Direct link to the gateway is the best way to get the bandwidth required to
run the cameras.
• If a device has both WiFi and copper connections, connect it to Multinode using
copper interface, whenever possible.
• Connect any Multinode to an Ethernet backbone if it is available in the area. Mesh
algorithm can use both wireless and wired links. Wired connections between
Multinodes significantly improve network throughput.

4.4. Planning the OneWireless mesh network
About mesh hopping

While there are no specific recommendations for the type of equipment that may be used
for the OneWireless infrastructure, you must consider network bandwidth as a common
resource shared by all devices and applications running on the network.
Theoretical bandwidth of 802.11a/g networks is about 21 Mbps under ideal conditions.
That number is cut in half with every mesh hop. Knowing your device’s bandwidth
requirements and placing it in the right location within the mesh is the best way to ensure
its performance on the wireless network. The following figure illustrates mesh hop
counting and preferred location of the high throughput devices.
Nodes supported
Honeywell’s mesh network supports up to 20 multinodes that can also function as
gateways between the wired and wireless network. These specifications are expected to
be expanded toward the maximum design specification as capacity testing continues. See
the Honeywell OneWireless Network and Multinode Specifications (EP03-610-100) for
the most up to date capacities.
Total number of wireless transmitters supported

The number of wireless transmitters each multimode supports depends on the frequency
at which the device transmits to the multinode, as shown in the following list.
• 20 wireless transmitters per multinode at a 1-second reporting rate
• 80 wireless transmitters per multinode at a 5, 10 or 30-second reporting rate.

4.5. OneWireless communication
4.5 OneWireless communication

Open system communications supported by the wireless network infrastructure falls into
two categories:
• Data access applications that use OPC for data access
• Controllers that need wireless data use Modbus
Data access for monitoring

The OneWireless network relies on OPC to provide open system communication to the
wireless sensor data. An OPC server is an integral part of the data access solution. An
OPC server collects wireless device data from gateways using native EPKS CDA
protocol. The data is then accessible to any OPC client application through a standard
OPC DA protocol.
Data access for control

When wireless data is used for control, the open system access protocol of choice is
Modbus. The wireless gateway supports serial and TCP Modbus. The serial Modbus
protocol is suitable for older controllers, while Modbus TCP can be used by newer
controllers. A Modbus server is implemented directly in the wireless gateway.
Wi-Fi and multinode protocols

Other communication protocols used by OneWireless include:
• CDA, which is a Honeywell proprietary protocol used for populating the OPC server
database.
• Simple Network Management Protocol (SNMP), used for monitoring the wireless
network.
Sensor/actuator nodes communicate with multinodes using the FHSS radio link.

4.6. Use of Network Time Protocol (NTP)
4.6 Use of Network Time Protocol (NTP)

Most large networks maintain a coordinated sense of time by using the Network Time
Protocol (NTP). Multinodes can synchronize their internal clocks to be in sync with a
user defined NTP server. The configuration of the NTP time synch depends on the
particular customer installation. This section outlines two means of configuring NTP for
a OneWireless installation. Direct synchronization requires synchronizing directly with
the local NTP server. Indirect synchronization requires synchronizing to the
OneWireless server, which itself is synchronized with the local NTP server.
Direct synchronization
The straightforward way to use NTP time synchronization is to have the wireless
gateway synchronize directly with the site’s time server. The following figure illustrates
the setup of a direct synchronization of NTP.

Local NTP Time Server
Firewall (with UDP Port 123 open)
L1 Switch
Gateway syncrhonizes
with local NTP Time
Server
OneWireless Server
OneWireless Gateway
(time sync root)
OneWireless Multinode OneWireless Multinode
Mulitinodes synchronize
with gateway by using
mesh time
synchronization

Indirect synchronization
In some cases, the network setup may preclude the gateway from communicating directly
with the local NTP server. In these cases, the OneWireless server can be configured to
be a NTP server and the gateway can synchronize with it. Microsoft NTP servers
sometimes use a proprietary implementation of NTP that the gateway cannot use, but the
OneWireless server can be configured as a standard NTP server without affecting the
configuration of the higher level NTP server. The following figure shows indirect
synchronization of NTP setup.
Local NTP Time Server
OneWireless Server
synchronizes with local
Firewall (with UDP Port 123 open)
NTP server
L1 Switch
Gateway syncrhonizes
OneWireless Server with OneWireless Server
OneWireless Gateway
(time sync root)
OneWireless Multinode OneWireless Multinode
Mulitinodes synchronize
with gateway by using
mesh time
synchronization

4.7. Integrating OneWireless devices with HART
4.7 Integrating OneWireless devices with HART

A Lantronix Xpress-DR-IAP Device Server is used to bridge communication between an
RS-232 connection, as supported by Highway Addressable Remote Transducer (HART)
clients and User Datagram Protocol (UDP) over the Ethernet, as supported by the
wireless system gateway. The Lantronix device must be configured to properly tunnel the
serial communication into UDP packets.
Configuring the Lantronix device

Configuring and adding the Lantronix device requires you to perform the following tasks,
which are covered in Getting Started with Honeywell OneWireless guide.
• Install the Lantronix Device Installer software (use the vendor documentation)
• Assign an IP address to the Lantronix device
• Install standard serial tunnel firmware on the Lantronix device
• Configure the standard serial tunnel firmware settings on the Lantronix device.

5. OneWireless Security Planning
This section provides high-level guidance for the users with the knowledge of and
experience in, installing the wireless systems. It is therefore assumed that readers are
familiar with terminology such as MAC addresses, PEAP, RADIUS, and SSID.
5.1 Security planning checklist

The following checklist is a list of items for you to consider when planning the security
for your OneWireless network.
Protection measure
Back up the Key Server and Directory server, every time new nodes are added.
Review the Key Server log periodically to identify security alerts.
Keep the authentication device in a secure location and restrict its access.
Enable mesh security and protect the mesh security key.
Use the Multinode configuration backup function when adding or replacing nodes.
Set access point security to the highest level Wi-Fi devices support.
Add all Microsoft Windows nodes to the PCN active directory domain and allow them to
participate in Microsoft patching and anti-virus updates.
Configure the same pass-phrase on all Multinodes and protect the pass-phrase, for
roaming across mesh coverage area.
5.2 About OneWireless security

Wireless networks lack physical security afforded by a set of wires and have to
compensate for that by state of the art cryptographic security that enables node
authentication and ensures data privacy and integrity.
OneWireless network consists of three independent wireless networks with different
security mechanisms. Following security best practices outlined here makes OneWireless
network as secure as possible, given the state of the art security technology.

5.3. Sensor network security
5.3 Sensor network security

Wireless sensors and actuators operate in secure mode by default, and all data is
cryptographically encrypted and authenticated. There is no way to disable security.
Follow these rules to keep the sensor network secure.
• Back up the Key Server and Directory Server databases every time new nodes are
added to the system. You can use the backups to restore system operation, if the Key
Server fails.
• Periodically review the Key Server log to identify security alerts that may indicate
the malfunctioning devices. You can remove the malfunctioning devices from the
network using the same tool.
• Keep the authentication device in a physically secure location and limit the access to
authorized installers.
• Erase all security keys from the authentication device, before storing it to prevent
unauthorized use.
• Load the authentication device with an adequate number of keys to provision all
devices and set the expiration to a reasonable limit that allows you to finish
provisioning each device.
5.4 Mesh network security

The mesh network can run in a secure or non-secure mode, but Honeywell strongly
recommends you enable the mesh security. When enabled, all messages transmitted
across the mesh are encrypted using 128-bit AES encryption algorithm. Use the
Multinode Configuration Tool to configure the mesh security. Follow these rules for
mesh network security.
• Enable mesh security using static AES-CCM algorithm.
• Protect the mesh security key and distribute it only to authorized personnel.
• If the mesh security key is lost, it cannot be recovered. To keep the network running
and allow replacement of failed nodes or addition of new nodes, use the Multinode
configuration backup function, which contains the security key.

5.5. WiFi client security
5.5 WiFi client security

WiFi clients such as laptop computers, tablet PCs, PDA and other WiFi portable devices
present serious security risks, if WiFi access is not secured properly. Follow these
guidelines for configuring WiFi access point security.
• Set the access point security to the highest-level Wi-Fi devices support – preferably
IEEE 802.11i (WPA2) using IEEE 802.1x and a Remote Authentication Dial in User
Service (RADIUS) server for end user devices. The Microsoft version of a RADIUS
server is the Internet Authentication Service or IAS, which comes free with
Windows Server 2003 and is easily added to an active directory domain controller.
• Do not use wireless devices on the OneWireless network that do not support a
minimum level of security.
• Make all Microsoft Windows nodes on the OneWireless network members of the
PCN active directory domain and verify if the nodes participate in Microsoft
patching and anti-virus software updates.
• If you need to enable roaming across the mesh coverage area, configure the same
pass-phrase on all Multinodes. Protect pass-phrase and allow only authorized
personnel to access it.
5.6 WAP security

When configuring a Wireless Access Point (WAP) Honeywell recommends you to
perform the following:
• Configure a unique SSID. Do not use the default SSID
• Disable SSID broadcast
• Configure authentication for EAP authentication to the Network. PEAP is preferred
• Configure the RADIUS server address
• Configure dynamic WEP
• Configure 802.1-x authentication
• Enable MAC filtering and enter MAC addresses for wireless Stations
For detailed configuration information, refer to the Multinode User’s Guide.

5.6. WAP security

6. Adding OneWireless to an Existing Network
The most likely scenario for a OneWireless installation is one, in which the OneWireless
nodes are added to a pre-existing switched network that contains multiple levels of
switches, firewalls, and routers. This section provides general guidelines for configuring
a switched network to accommodate the OneWireless multinodes.
6.1 Network switch configuration

Network switches typically use a spanning link management protocol to provide path
redundancy and to prevent the development of undesirable network loops. OneWireless
multinodes act as network bridges and are therefore part of any spanning tree to which
they are connected. Constructing a proper spanning tree implementation with
OneWireless nodes requires configuration on both the network switches and the
OneWireless multinodes. This section only discusses configuration options commonly
available on Cisco network switches.
About spanning tree on Cisco switches

Most recent vintage Cisco switches implemented several different spanning tree
implementations including the following
• MST (multiple spanning trees)
• PVST+ (per-VLAN spanning tree plus)
• Rapid PVST+ (rapid per-VLAN spanning tree plus).
Normally, the preferred implementation for a Level 2 switched networks is MST, but
there are known problems with the multinode meshing firmware that causes the spanning
tree to respond badly when multinodes are part of a tree that uses MST.
MST uses the Rapid Spanning Tree Protocol (RSTP), which is based on IEEE 802.1w
standard. RSTP provides rapid convergence of the spanning tree and the ability to
change the root of the tree quickly. These attributes are important in ensuring reliable
access to process data in the event of a failure somewhere in the network.
All configuration commands are expressed in Cisco’s IOS command line interface. The
IOS command line interface is universal over Cisco products and well understood by
most network administrators.

6.1. Network switch configuration
General switch configuration

Switch ports that are intended to be used to connect to other switches or with
OneWireless gateways must not have the portfast bpduguard feature enabled. These
options prohibit the transfer of BPDU packets, which are necessary to construct and
maintain a proper spanning tree. The switch shutdowns any port on which the BPDU
guard is enabled and it detects BPDU packets.
The following global configuration commands ensure that both of these features are
disabled globally.
no spanning-tree portfast bpduguard default
no spanning-tree portfast bpdufilter default
Rapid PVST spanning tree configuration
This example of the high-level configuration steps are for a Cisco Catalyst 2950 L2
switch with the following specifications.
• 24 FastEthernet port (F0/1 = F0/24)
• Two Gigabit Ethernet ports (G0/1 and G0/2).
Perform the following steps to configure the Rapid PVST spanning tree.
Step Action
1 Create a virtual LAN (VLAN) with ID 10 and name OneWirelessLAN.
2 Disable loopguard.
3 Configure the spanning-tree mode to be rapid-pvst.
4 Set the spanning tree priority of the VLAN to 4096.
5 Configure the switch ports for spanning tree operation.

Example of Rapid PVST spanning tree configuration on Cisco switch

You can extend the example to other Cisco switches by changing the names of the
interfaces to match those available on the target switch. You may also limit the set of
ports over which the spanning tree is configured.
configure terminal
vlan 10
name OneWirelessLAN
no spanning-tree loopguard default
spanning-tree mode rapid-pvst
spanning-tree vlan 10 priority 4096
interface F0/1
switchport mode access
switchport access vlan 10
spanning-tree portfast disable
interface F0/2
interface F0/2
interface F0/3
interface F0/4
interface F0/5
interface F0/6
interface F0/7


interface F0/8
interface F0/9
interface F0/10
interface F0/11
interface F0/12
interface F0/13
interface F0/14
interface F0/15
interface F0/16
interface F0/17


interface F0/18
interface F0/19
interface F0/20
interface F0/21
interface F0/22
interface F0/23
interface F0/24
interface G0/1
interface G0/2
end

copy running-config startup-config
show span
VLAN0010
Spanning tree enabled protocol rstp
Root ID Priority 4106
Address 000c.85b7.4a80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15
sec
Bridge ID Priority 4106 (priority 4096 sys-id-ext 10)

Address 000c.85b7.4a80
Hello Time 2 sec Max Age 20 sec Forward Delay 15
sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- ---------------------
-----------
Fa0/22 Desg FWD 19 128.22 P2p
Fa0/23 Desg FWD 19 128.23 P2p
Fa0/24 Desg FWD 19 128.24 P2p
Gi0/1 Desg FWD 19 128.25 P2p

6.2. Multinode spanning tree configuration
6.2 Multinode spanning tree configuration

The only configurable parameter for multinode spanning tree configuration is the
multinode’s mesh priority. Members of the spanning tree use this value to determine
which node must be the root of the spanning tree. This is the same priority value used in
the network switch configuration sections previously mentioned.
The multinode allows the mesh priority value to be configured from 1 – 65535, although
you must only use values that are multiples of 4096. Cisco switches enforce this
configuration rule explicitly, but multinodes do not. Configuring the mesh priority to be
an integer multiple of 4096 ensures compatibility with nodes running MSTP. MSTP
uses the lowest 12 bits of the 16-bit priority value for a system ID extension field, leaving
only the highest 4 bits for the actual mesh priority value.
MST spanning tree configuration

Note: MST is not recommended for OneWireless R100 installations because of
instability seen when multinodes reboot and rejoin the network.
This example of the high-level configuration steps are for a Cisco Catalyst 2950 L2
switch with the following specifications.
• 24 FastEthernet port (F0/1 = F0/24)
• Two Gigabit Eth.

Perform the following steps to configure the MST spanning tree.
Step Action
1 Create a virtual LAN (VLAN) with ID 10 and name OneWirelessLAN.
2 Disable loopguard.
3 Set the spanning tree mode to MST.
4 Create, configure, and enable an MST instance:
• Create an MST instance with ID 0 and apply it to the OneWirelessLAN
VLAN.
• Name the MST instance OneWirelessTree.
• Assign revision number 1 to the OneWirelessTree MST instance.
• Set the priority of the MST instance to 4096.
5 Configure switch ports for spanning tree operation:
• Set the port priority to 0 (highest).
• Set path cost to 1 (highest).
Example of MST spanning tree configuration on Cisco switch

You can extend the example to other Cisco switches by changing the names of the
interfaces to match those available on the target switch. You may also limit the set of
ports over which the spanning tree is configured.
configure terminal
vlan 10
name OneWirelessLAN
no spanning-tree loopguard default
spanning-tree mode mst
spanning-tree mst configuration
instance 0 vlan 10
name OneWirelessTree
revision 1
spanning-tree mst 0 priority 4096
interface F0/1
spanning-tree mst 0 port-priority 0
spanning-tree mst 0 cost 1

interface F0/2
interface F0/2
interface F0/3
interface F0/4
interface F0/5
interface F0/6
interface F0/7


interface F0/8
interface F0/9
interface F0/10
interface F0/11
interface F0/12
interface F0/13
interface F0/14


interface F0/15
interface F0/16
interface F0/17
interface F0/18
interface F0/19
interface F0/20


interface F0/21
interface F0/22
interface F0/23
interface F0/24
interface G0/1
interface G0/2
end
copy running-config startup-config

After configuring the switch use the “show span” command to

inspect the status of the spanning tree implementation. If all the
multinodes have their bridging priorities configured correctly,
then the switch must be the root of the spanning tree (unless this
switch is connected to other switches with higher bridging
priorities.)
show span
MST00
Spanning tree enabled protocol mstp
Root ID Priority 4096
Address 000b.fdeb.5540
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 4096 (priority 4096 sys-id-ext 0)

Address 000b.fdeb.5540
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 0
Interface Port ID Designated

Port ID
Name Prio.Nbr Cost Sts Cost Bridge ID
Prio.Nbr
---------------- -------- --------- --- --------- -------------------- --
Fa0/23 0.23 1 FWD 0 4096 000b.fdeb.5540 0.23
Fa0/24 0.24 1 FWD 0 4096 000b.fdeb.5540 0.24
Gi0/1 0.25 1 FWD 0 4096 000b.fdeb.5540 0.25
Gi0/2 0.26 1 FWD 0 4096 000b.fdeb.5540 0.26


Honeywell Process Solutions
1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA

OneWireless Planning Guide OW-CDX030

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OneWireless Planning Guide OW-CDX030

Uploaded by

Copyright:

Available Formats

Honeywell OneWireless

Copyright 2010 by Honeywell International Sárl.

Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions

ii OneWireless Planning Guide R120

OneWireless Planning Guide OW-CDX030 120 April 2010

Planning and Design

R120 OneWireless Planning Guide iii

For more information

Document and Description

iv OneWireless Planning Guide R120

Document and Description

R120 OneWireless Planning Guide v

Document and Description

vi OneWireless Planning Guide R120

Purpose and scope of document

Agency compliance information

FCC compliance statements

R120 OneWireless Planning Guide vii

Radio Frequency (RF) statement

European Union restriction

For additional information

viii OneWireless Planning Guide R120

Support and Other Contacts

Europe, Middle East, and Africa (EMEA)

R120 OneWireless Planning Guide ix

Contact: Honeywell Global TAC – Korea

People’s Republic of China

x OneWireless Planning Guide R120

World Wide Web

R120 OneWireless Planning Guide xi

ATTENTION: Identifies information that requires special

TIP: Identifies advice or hints for the user, often in terms of

REFERENCE -EXTERNAL: Identifies an additional source of

REFERENCE - INTERNAL: Identifies an additional source of

CAUTION Indicates a situation which, if not avoided, may result in equipment

CAUTION: Indicates a potentially hazardous situation which, if not

CAUTION symbol on the equipment refers the user to the product

WARNING: Indicates a potentially hazardous situation, which, if not

WARNING symbol on the equipment refers the user to the product

xii OneWireless Planning Guide R120

WARNING, Risk of electrical shock: Potential shock hazard where

ESD HAZARD: Danger of an electro-static discharge to which

Protective Earth (PE) terminal: Provided for connection of the

Functional earth terminal: Used for non-safety purposes such as

Earth Ground: Functional earth connection. NOTE: This

Chassis Ground: Identifies a connection to the chassis or frame of

R120 OneWireless Planning Guide xiii

xiv OneWireless Planning Guide R120

1. HONEYWELL ONEWIRELESS SOLUTION ................................19

2. ONEWIRELESS IMPLEMENTATION ..........................................33

R120 OneWireless Planning Guide xv

2.2 OneWireless installation requirements .......................................................34

3. ONEWIRELESS SITE PLANNING .............................................. 37

xvi OneWireless Planning Guide R120

4. ONEWIRELESS NETWORK PLANNING ....................................53

5. ONEWIRELESS SECURITY PLANNING.....................................67

6. ADDING ONEWIRELESS TO AN EXISTING NETWORK ...........71

R120 OneWireless Planning Guide xvii

6.1 Network switch configuration ......................................................................71

xviii OneWireless Planning Guide R120

1.1 OneWireless components

R120 OneWireless Planning Guide 19