SKF Wireless Machine Condition Sensor CMWA 8800 User Manual

Service manual
SKF Wireless Machine

Condition Sensor
CMWA 8800
User Manual Part No. 32315300-EN

Revision B
WARNING! - Read this manual before using this product. Failure to follow the
instructions and safety precautions in this manual can result in serious injury,
damage to the product, or incorrect readings. Keep this manual in a safe location
for future reference.
Copyright 2015 by SKF USA Inc.

All rights reserved.
5271 Viewridge Court., San Diego, CA 92123-1841 USA
Telephone: (858) 496-3400, Fax: (858) 496-3531
Customer Service: 1-800-523-7514
SKF USA Inc.
SKF is a registered trademark of the SKF Group.
All other trademarks are the property of their respective owners.
SKF 2015
The contents of this publication are the copyright of the publisher and may not be reproduced (even
extracts) unless prior written permission is granted. Every care has been taken to ensure the accuracy of
the information contained in this publication but no liability can be accepted for any loss or damage whether
direct, indirect or consequential arising out of the use of the information contained herein. SKF reserves the
right to alter any part of this publication without prior notice.
Patents: US 4,768,380 US 5,633,811 US 5,679,900 US 5,845,230 US 5,852,351

US 5,854,553 US 5,854,994 US 5,870,699 US 5,907,491 US 5,992,237 US 6,006,164
US 6,124,692 US 6,138,078 US 6,199,422 US 6,202,491 US 6,275,781 US 6,301,514
US 6,437,692 US 6,489,884 US 6,513,386 US 6,633,822 US 6,789,025 US 6,792,360
US 7,103,511 US 7,697,492 WO/2003/048714
Product Support Contact Information
Product Support To request a Return Authorization, Product Calibration or a Product Support Plan, use
the web page links for direct contact and support.
Product Sales - For information on purchasing condition monitoring products, services or customer
support, contact your local SKF sales office.
General Product Information
For general product information (i.e., product data sheet, accessories catalog, etc.), visit the Condition
Monitoring Products page on SKF.com and select the appropriate product link.
Technical Support Group
Discuss/review issues of specific interest with maintenance and reliability specialists from around the world
at the SKF Knowledge Centre.
For technical support on issues like troubleshooting product installation, troubleshooting product
performance, etc., use our technical support web page to contact one of our Technical Support Groups.
Product Registration
Please take a moment to register your product at www.skf.com/cm/register to receive exclusive benefits
offered only to our registered customers, including receiving technical support, tracking your proof of
ownership, and staying informed about upgrades and special offers. (Please visit our website for more
details on these benefits.)
Tell us how were doing!
Its important that youre satisfied with the quality of our product user manuals. We appreciate your
feedback; if you have comments or suggestions for improvement, please tell us how were doing!
090115dc
Table of Contents
Introduction 1
Scope and Purpose .........................................................1
Related Documentation .................................................1
The Basics 3
The CMWA 8800 Sensor ...............................................3
Warnings and Cautions ..........................................3
CMWA 8800 Label ..................................................4
CMWA Long Tag ......................................................4
Repair Service ..........................................................5
Issuing Commands to the Sensor ................................5
Activate the Sensor .................................................5
Deactivate the Sensor ............................................5
Manual Commands .................................................6
Software Commands ..............................................7
The Network ....................................................................8
WirelessHART Terminology ..................................8
The WirelessHART Network Joining Process.....9
Network Layers .......................................................9
The Wireless Sensor Device Manager...................... 11
The Device Manager License Key ...................... 12
Device Manager Configuration Parameters .... 13
The P+F Gateways Web Page 15

Accessing the Web Page ............................................. 15
Verifying the P+F Gateways Firmware Version ..... 16
Known Issues with the Firmware ...................... 16
Network ID and Join Key Parameters ...................... 17
Preparing a Commissioning Gateway....................... 18
Setting up a Commissioning Gateway .............. 18
Joining the Sensors to the Commissioning
Network ...................................................................... 21
The Production Network Settings ..................... 22
P+F Gateways Installation Torque ........................... 22
Comparing P+F with Emerson Gateways ................ 23
SKF Wireless Machine Condition Sensor TOC-1

Service Manual
Wireless Sensor Device Manager 25
Device Manager Installation ....................................... 25
To Install Device Manager .................................. 26
Known Issue #1 Cannot open database......... 27
Known Issue #2 Replace the database .......... 29
Connecting to the Gateway ........................................ 32
Issue: Gateway Connection Failed .................... 33
Troubleshooting the Required Ports ................ 33
Importing Sensors into Device Manager.......... 35
Viewing the Connected Sensors ........................ 36
Verifying the Sensor Firmware.................................. 36
Known Issues in Device Manager.............................. 37
Full Routing vs. Leaf Node ......................................... 38
Expert Features in Device Manager.......................... 39
Wireless or Wired Communication ................... 39
Calibration ............................................................. 40
Generic Command Feature ................................ 41
Data Collection Scheduling ......................................... 42
The Use Cache Check Box .................................. 46
Command 93 Example........................................ 47
Command 9 Example .......................................... 53
Estimating the Time to Capture Waveforms ... 54
Exporting the Measurement Collection Period ....... 54
Manual Data Collection ............................................... 55
Overall Data........................................................... 55
Waveform Data .................................................... 56
Changing the Network ID and Join Key 57
Troubleshooting XML Import to Analyst 59
Network Planning and Diagnostics 63

Network Planning ........................................................ 63
Important Considerations ................................... 63
Wireless Communication Stability Considerations . 64
Location and Signal Strength ............................ 64
Coexistence with WLAN ...................................... 66
Network Commissioning ............................................. 68
Network Diagnostics .................................................... 69
Key Considerations............................................... 69
Topology View....................................................... 69
Network Diagnostic Details ................................ 72
The Network Statistics Report ........................... 74
Troubleshooting Network Issues ............................... 78
Issue: No Sensors Join ....................................... 78
Issue: Some Sensors Do Not Join .................... 78
Issue: One Sensor Does Not Join ..................... 78
TOC-2 SKF Wireless Machine Condition Sensor

Service Manual
Issue: One Sensor Rejoins Over and Over ...... 79
Issue: The Gateway Becomes
Non-responsive................................................. 79
RF Interference and Solutions 81

RF Interference ............................................................. 81
Sources .................................................................. 81
Symptoms ............................................................. 81
Solutions to RF Interference ...................................... 81
Channel Blacklisting ............................................. 81
System Maintenance 83
Adding a New Sensor into Service ............................ 83
Editing a Sensors Name ............................................. 86
Removing a Sensor from Service.............................. 86
Replacing an Existing Sensor in Service .................. 87
Commissioning Network Available Sensor
with Default Security Settings ........................ 87
Commissioning Network Available Sensor
with Production Security Settings ................. 90
No Commissioning Network ............................... 93
Relocating an Existing Sensor in Service ................. 96
Commissioning Network Available .................... 96
No Commissioning Network ............................... 96
Upgrading Sensor Firmware ...................................... 98
Global Firmware Upgrade ................................... 98
Individual Sensor Firmware Upgrade ............... 99
Device Status Indicators ........................................... 101
Device Status ...................................................... 101
Extended Device Status .................................... 102
Standardized Status 0 ....................................... 102
Standardized Status 3 ....................................... 103
Sensor Battery Status ....................................... 103
System Debugging Logs ........................................... 104
Execution Log...................................................... 104
Communication Log ........................................... 104
FAQs 105
Frequently Asked Questions ..................................... 105
CMWA 8800 System Setup Checklist 107
SKF Wireless Machine Condition Sensor TOC-3

Service Manual
1
Introduction
Scope and Purpose
The intended audience for this manual is Certified Service Technician and Technical
Support personnel who provide detailed technical work to customers, either over the
telephone or in person. It is assumed that these people are already familiar with the
SKF @ptitude Monitoring Suite as well as Microsofts Operating Systems for Desktop
(XP, Vista, 7), Server (2008) and Windows Services.
This document is intended to assist Certified Service Technician and Technical Support
personnel in installing, configuring, supporting and troubleshooting the SKF Wireless
Machine Condition Sensor (CMWA 8800) in WirelessHART networks.
The Wireless Sensor Device Manager software application is commonly called Device
Manager in this Service Manual. In some directory paths and file names it is referred
to as WSDM.
SKF @ptitude Analyst is commonly called Analyst in this Service Manual.
PEPPERL+FUCHS is commonly called P+F in this Service Manual.
Related Documentation
Document Part No.

Wireless Sensor Device Manager User Manual P/N 32286200
SKF Wireless Machine Condition Sensor (CMWA 8800) P/N 32257600
System Setup Guide
PEPPERL+FUCHS WirelessHART Gateway WHA-GW
User Manual
PEPPERL+FUCHS WirelessHART Adapter WHA-ADP-
*-Z1(EX1) User Manual
SKF Wireless Machine Condition Sensor 1

Service Manual
2
The Basics
In this chapter, we present some general information about the CMWA 8800 sensor,
the WirelessHART network, and the Wireless Sensor Device Manager software.
The CMWA 8800 Sensor
Warnings and Cautions

Storage temperature should be less than 30 C (86 F). (Note: Some battery life
issues due to crystal build up have come to light under sustained high
temperatures.)
WARNING! Do not twist the plastic top! Doing so voids the warranty and
hazardous area certification. Do not open the plastic top!
Figure 1.
Correct Method of Mounting/Dismounting a Sensor.
WARNING! To obtain proper torque when using a crowfoot wrench, you must
attach the crowfoot 90 degrees of the torque wrench shaft.

Service Manual
The Basics
The CMWA 8800 Sensor
WARNING! Contact with aggressive chemicals may cause severe damage to

the sensor's mechanical construction. For detailed information on chemical
resistance, go to this link https://www.lubrizol.com/Engineered-Polymers/Chemical-
Resistance-Estane.pdf.
Sensors that have mechanical damage should be removed from hazardous areas as
soon as possible.
Figure 2.
SKF Wireless Condition Monitoring Sensor Main Dimensions.
CMWA 8800 Label

The label on the base of each sensor displays the Hardware Version and the MAC
address. The MAC address is assigned by SKF and it serves as a physical identification
and does not change. The first ten characters of the MAC address make up the
manufacturer and products unique ID number (00-1B-1E-E1-A2) assigned by the
HART (Highway Addressable Remote Transducer) Communication Foundation; the last
six characters are the unique device ID assigned by SKF. The label also includes the Ex
marking, operating temperature range, model number, bar code, mounting torque,
radio certification numbers, icon indicating do not throw away the sensor as trash, and
the warning Sensor shall not be opened by unauthorized personnel.
CMWA Long Tag

SKF @ptitude Analyst (called Analyst in this Service Manual) and the Wireless Sensor
Device Manager software (called Device Manager in this Service Manual) use the asset
name as the Long Tag to identify the sensor. The Long Tag contains 32 characters
under the WirelessHART protocol, but Analyst permits only 20 characters so the Long
Tag is truncated. If the truncated tag has a duplicate in the Analyst database, Analyst
appends the names of the subsequent POINTs with .1, .2, and so on. The Long Tag
identifier can be changed in Device Manager.
4 SKF Wireless Machine Condition Sensor

Service Manual
The Basics
Issuing Commands to the Sensor
Repair Service
All repair service must be done at a certified repair center currently San Diego is the
only center. The sensor will be inspected to determine whether the plastic top was
twisted or opened in the field, which would void the warranty.
The expected type of service is battery replacement. The sensor has no repairable
parts. If the printed circuit board (PCB) is not in working condition, it can be replaced at
the customers request. The MAC address of the new PCB will be modified to match
that of the sensor to be replaced. The serviced sensor will be fitted with new top, label,
and O-ring.
LED
Push button
Figure 3.
Wireless Sensor LED and Push Button.
You activate and issue manual commands to the wireless sensor by pressing and
holding its push button for various durations - as you count a number of LED blinks.
Releasing the push button after a specific number of blinks will issue a specific
command to the sensor.
Activate the Sensor

Firmly press and then quickly release the sensors push button. The sensors green LED
immediately blinks once, pauses, then blinks in an accelerating manner, pauses, and
then blinks a short burst to indicate the sensor is active.
Deactivate the Sensor

Firmly press the sensors push button and count four blinks, then release. The sensors
green LED blinks in a decelerating manner, and then stops. The sensor is deactivated.
(Counting five or six blinks will also deactivate the sensor.)

Service Manual
The Basics
Manual Commands
Once the sensor has been activated, you may issue manual commands to the sensor by
pressing and holding its push button down for a specific number of blinks. Reference
the following table:
Press and To issue this command and elicit this LED

hold for: response
1 blink Not used after sensor is activated Verifies the sensor is active
2 blinks (Not implemented at this time) None
Communicate with the gateway for
identification purposes
3 blinks Reset (reboot) the sensor for Short burst
troubleshooting purposes
(wait five seconds after resetting the sensor
before issuing new commands to the
sensor)
4 blinks Deactivate the sensor Blinks in a decelerating
manner, then stops
manner, then stops
manner, then stops
7 blinks Set Network ID to 101, and reset sensor Short burst
8 blinks Set Network ID to 102, and reset sensor Short burst
9 blinks Set Network ID to 1229 (default setting) Short burst
and set Join Key to 44555354 4E455457
4F524B53 524F434B and reset sensor
The actions below are for Technical Service Group (TSG) use only in the Extended
Operations Menu.
15 blinks Access the Extended Operations Menu Confirm by 3 rapid blinks
(for TSG only). after releasing the button.
3 blinks Reset device back to normal operation. Burst of quick blinks.
4 blinks Set update period to 5 minutes (for testing A few rapid blinks. Returns
only; not for production). Note that this will to the regular menu.
shorten the battery life if the sensor is left
in this mode.
5 blinks Reset to factory defaults configuration. A few rapid blinks, then a
Sensor resets to normal operation. Note burst; pause. Returns to the
that this will change the Long Tag and the regular menu.
sensor will show up as a new sensor.
6 blinks Reset of calibration data to factory default. A few rapid blinks, then a
Sensor resets to normal operation. burst; pause. Returns to the
regular menu.
7 blinks Radio Test Menu (for testing only; not for
production).

Service Manual
The Basics
Software Commands
After the Device Manager software is installed and operational, you can issue some
standard procedure commands to the sensors with it. Select a sensor item in the
hierarchy, and then go to the Device tab.
Figure 4.
Sensor / Device Tab, Commands to Sensors.
Flash LED Click this button to cause the connected wireless sensors LED to flash ten
times. This can be useful if you need to identify a device in the network if the label is
damaged or to check communication.
Reset Device Click this button to reset the sensor. If the sensor is connected to the
Device Manager software, resetting the sensor is similar to rebooting a computer; it
helps to clear issues with the device. Note that the sensor will drop off the network, and
then rejoin the network, which takes some time - more time the larger the network.
Reset Pipe If the network manager fails to reassign the Fast pipe function, you can
click this button to de-allocate the fast pipe from this sensor so the gateway can
reassign the resource to other sensors as needed. However, the preferred method is to
set the fast pipe on the P+F gateways Operating Modes web page.
IMPORTANT: You can verify a sensors fast pipe assignment on the P+F gateways
Operating Modes web page. A failure of fast pipe assignment is indicated when a
sensor directly connected to the gateway takes more than two minutes to complete
collecting a waveform.
IMPORTANT: Also on the Sensor / Device tab, entering the Machine Speed for
the sensor is recommended. The value is exported to Analyst for the FAM overlay so
that it does not have to be entered in each FFT plot in Analyst.

Service Manual
The Basics
The Network
The Network
WirelessHART Terminology
HART7 (spec155) added the Wireless command set, including network security terms
such as Network ID and 32 character Join Key, and advertisement. HART7 is backward
compatible. Some terms commonly used with WirelessHART networks are defined
below.
Term Definition
Messages sent by the network manager to announce the networks
Advertisement
existence.
Generally, HART communications are connectionless transactions.
Block transfer extends the protocol to support connection oriented
Block transfer
reliable stream service for large data blocks. Used for sending
waveforms and firmware upgrades.
The sensor publishes data for any of the HART commands at a
Burst mode regular interval. Contrary to polling, no query is made so burst
mode is more efficient.
Burst data for a query are saved in gateway memory. When
Caching queried by the host software, the gateway will return the cache
data instead of polling the data from the sensor.
This is a single device mode which establishes a direct connection
to a selected device. It has four times the transfer rate of a regular
connection. The network manager in the gateway grants fast pipe
mode only to devices which identify themselves as high power
Fast pipe profile devices.
This can be selected manually in the gateways Operating Modes
web page or automatically by the network manager during block
transfer for waveform upload or firmware download. See the
section Full Routing vs. Leaf Node, Power profile.
Responsible for the coordination of communication between the
Network manager
devices and the gateway and between devices.
A device that does not participate in the mesh network. It does not
Leaf node device
help its neighbor.
The full communication specification between adjacent nodes in
Link the network; the communication parameters necessary to move a
packet one hop.
Long tag HART7 32-character logical name for the HART device.
256 slot superframe, 2.56 sec cycle; normal battery life, normal
join process, better user interface response.
P1 profile P1 can be selected during your interaction with the P+F web page
to speed response time. Then, when you are finished, P2 can be
selected for normal network operation to conserve battery life.

Service Manual
The Basics
The Network
Term Definition
2048 slot superframe, 20.48 sec cycle; better battery life, poor
user interface response and slower join process.
P2 profile
P2 is eight times slower than P1; the network assigns the same
number of slots but eight times farther apart.
High or low power device. See the section Full Routing vs. Leaf
Power profile
Node, Power profile.
A device that participates in the mesh network, meaning it helps
Routing device
its neighbor when the neighbor does not have direct access.
Short tag Pre-HART7 8-character logical name for the HART device.
A fixed time interval that may be used for communication between
Slot
neighbors.
Responsible for the joining process of the device and assigning the
Security manager
session key to encrypt and decrypt packets.
A collection of slots repeating at a constant rate. Each slot may
Superframe
have several links associated with it.
KNOWN ISSUE: P2 profile is not working in the P+F gateway firmware version
2.00.02. However, it may work in version 2.00.03 or in gateways from other
manufacturers.
The WirelessHART Network Joining Process

This is a simplified sequence of how the sensors join the network.
The active gateway sends network advertisement signals. These are messages
sent by the network manager to announce the networks existence. The network
manager and security manager are contained in the gateway.
The sensors respond with a Join Request, which consists of the Network ID and
Join Key. The security manager authenticates the Network ID and Join Key and
then allows the sensor to join the network.
The security manager sends session keys to the sensors and routing and
scheduling information.
The sensors begin normal operation, such as publishing data (the four main
variables and device status, etc.).
Network Layers
Physical Layer
IEEE 802.15.4
ISM band 2.40 2.48 GHz
16 x 5 MHz non-overlapping channels in 80 MHz bandwidth
DataLink Layer
Time Synchronized Mesh Network - Time Division Multiple Access (TDMA)

Service Manual
The Basics
The Network
There are 250 slots within one superframe.

Each slot is 10 ms. Therefore, the superframe repeats every 2.5 sec.
133 bytes packet at 250 kbit/s; it takes ~4 ms for an average packet to
complete within the 10 ms
16 channel * 100 slots/sec/channel = 1600 slots per sec
Frequency hopping - Avoid interference and provide reliable communication by
using a different frequency channel in each allocated slot.
WirelessHART networks are extremely reliable in delivering packets of data. The grid
below illustrates how TDMA works. Multiple slots may be allocated to a device within a
superframe depending on the communication demand. Multiple devices can
communicate at the same slot by using different frequencies; for example, sensor 1 and
sensor 2 communicate at the same time by using different frequencies.
Figure 5.
TDMA Slots and Channels Illustrated.
Application Layer
Universal (spec127) Standard commands must be implemented by all HART
devices. For example, they support four main variables PV (Primary), SV
(Secondary), TV (Tertiary), QV (Quaternary) and other device variables, such as
tag names, descriptor, date, final assembly number (FAN), device status. With
CMWA 8800, the PV is velocity overall RMS, SV is enveloped acceleration overall
Pk-to-Pk and TV is temperature. QV is not used.
Common (spec151) Standard commands applicable to many devices, such as
squawk for sensor identification, burst control for data publishing, and block
transfer.
Device Specific Vender specific commands. For example, cyclic update interval,
sample.

Service Manual
The Basics
The Wireless Sensor Device Manager
Device Manager provides the user interface that enables you to set up, commission,
operate and maintain the sensor system. It allows you to change the gateway settings
and also propagates the settings to all sensors in the network (note: this cannot be done
from the gateways web page). After the sensors are set up, and their data collection
schedules are configured and stored in the Device Manager database, you will start the
batch service. The Device Manager batch service runs in the background using the
stored data collection schedules to collect measurements and save them to the
database. Both the UI and batch service are installed from a single installation
application.
The batch service maintains its previous status when the
computer it is installed on is turned off and then turned on again
(or rebooted). For example, if the batch service is stopped when
the computer is turned off, then the batch service will be stopped
when the computer is turned on.
WARNING! The minimum monitor resolution for Device Manager is 1600 x

900. Device Manager does not permit scrolling and some vital functions will be hidden
at lower resolution.
Device Manager exports the collected data to the Analyst database. The diagram below
shows the data flow from the CMWA 8800 all the way through to Analyst and other
applications.
Figure 6.
Data Flow Export to Analyst.
Two additional data flows are possible:

From the gateway directly to the Modbus.
HART OPC server running on the network computer connecting to the gateway.

Service Manual
The Basics
The Device Manager License Key

Device Manager is shipped with a temporary license key that has a fixed expiration date.
The temporary license key and expiration date can be found on the hot sheet inside of
the Device Managers CD case. This temporary license is good for up to 50 sensors only
and allows you to set up the system while the permanent license key is being processed.
When Device Manager is installed and the Plant hierarchy item has been created, then
the permanent license key should be requested from SKF Customer Support Group
(CSG) through the License Management dialog in Device Manager.
Important points to note include:
The license key is good for any number of installations on the same computer.
The license key is good for future software upgrades.
The customer must re-apply for the license key from CSG if the software is moved
to a different computer.
To obtain the license key, follow these steps:
After the first plant is created, go

to Help > License Management.
The License Management

dialog opens.
Enter the temporary license key

from the hot sheet to the
License Key field.
Click Save.
The Expiration date is then
displayed. Up to 50 sensors are
supported in the Current
column.
In the Wanted column, select
the number of the sensors that
the purchased license supports
(500 in this example).
With the License Application
Code now displayed, click the
Copy to clipboard button to
copy the code to your clipboard.
Paste the code in an email and
then send it to CSG.
CSG will return an email with
the new license key to the
customer within 24 hours.

Service Manual
The Basics
Copy the license key from the

email from CSG to the clipboard.
Note: Make sure no extra blank
spaces are copied at the end of
the license key when pasting
into the License Key box.
From the License Key field, click
the Paste from clipboard
button and then click Save.
The Current column will show
the number of sensors that the
license key supports and the
Expiration date box will
disappear.
Device Manager Configuration Parameters

Device Manager configuration parameters are stored in the Settings.config file on the
drive on which the software is installed:
For Windows XP, the default path is \Program Files\SKF-RS\Wireless Sensor
Device Manager - 8800\Settings.config in the root drive.
For Windows 7, the default path is \Program Files(x86)\SKF-RS\Wireless Sensor
Device Manager 8800\Settings.config in the root drive.
Settings.config - Stores the following information:
Information Default Setting

Enables and disables expert <add key="LocalTest" value="False"/>
features in the GUI
Ports used <add key="GatewayPort" value="20004"/>
Port range <add key="PortRangeStartPort" value="7000"/>
Enable/Disable communication <add key="HartCommMode" value="True"/>
logging
Device Manager software program <add key="DebugMode" value="False"/>
execution logging depth <add key="InfoMode" value="True"/>
<add key="DbInfoMode" value="False"/>
<add key="UdpInfoMode" value="False"/>
<add key="BatchInfoMode" value="False"/>
<add key="QueueInfoMode" value="False"/>
<add key="LearnInfoMode" value="False"/>

Service Manual
The Basics
Information Default Setting

<add key="BlockDataInfoMode" value="False"/>
<add key="CommandInfoMode" value="False"/>
XML prefix <add key="SKFXMLExportPrefix" value="WSDM"/>
Note: If there are multiple WSDM
installations on site, the prefix
must be unique for each
installation.
SKF export folder name <add key="SKFExportFolder"
value="C:\WSDM_Export\"/>
Time Synch enable/disable <add key="PerformGatewayTimesynch"
Note: This should be disabled for value="False"/>
P+F gateway firmware version
2.00.02 due to a bug in the
gateway firmware.
Timing configuration <add key="CmdSendingDelay" value="500"/>
Note: Optimized do not change <add key="CmdResponseRetryCount" value="200"/>
<add key="GWResponseTimeout" value="2000"/>
<add key="KeepAlivePeriod" value="60000"/>
<add key="GatewayReconnectDelayMilliseconds"
value="60000"/>
Figure 7.
Example of a Settings.config File.

Service Manual
3
The P+F Gateways Web Page
The P+F gateways web page gives field service personnel a wide range of information
and possible actions to take when pursuing customer issues or questions. In this
chapter, we will discuss the following:
How to access the P+F gateways web page
Known issues with the gateways firmware
The significance of the Network ID and Join Key
Why and how to prepare a commissioning gateway (including a gateway from
another vendor)
How to join the sensors to the commissioning network
Comparison of features available with P+F vs. Emerson gateways
Accessing the Web Page
The P+F gateways web page gives field service personnel a wide range of information
and possible actions when pursuing customer issues or questions. To access this tool,
follow the steps below. You will want to set up the configuration computer to join the
customers network.
Verify with the customer the correct gateway IP address on the network. (The P+F
gateways factory default IP address is 192.168.1.1.)
Enter the gateways IP address into your browsers address bar to access the P+F
gateways configuration web page.
The default username is admin; the default password is also admin.
Figure 8.
Authentication Required Dialog for P+F Gateways Web Page.

Service Manual
Verifying the P+F Gateways Firmware Version
Known Issue Solution

You see the message, Microsoft Internet Download and install Java from this link
Explorer is not able to show the P&F http://java.com/en/download/index.jsp
gateway web page.
Cause: The computer is missing Java to
run Java Applet.
Verifying the P+F Gateways Firmware Version
If the network P+F gateway was not purchased from SKF, verify that the software
Revision is 2.5 or later and the software version is 02.00.02 or later.
Figure 9.
Verify the Gateways Firmware Version.
Known Issues with the Firmware

The following are known issues with the P+F gateways firmware, current software
release 2.5 version 2.00.02:

The web pages do not refresh Manually refresh the web pages to get updates.
automatically.
The manual refresh is very slow if the No solution. Wait until the refresh is complete.
network has many sensors (more than
50) trying to join the network.
P1 or P2 profile options are offered, but No solution at this time P2 does not work in
P2 profile (slower) does not work. the P+F gateways firmware in the current
version.

Service Manual
Network ID and Join Key Parameters

The gateways Time Synch function in Manually set the time in the P+F gateways
gateway firmware version 2.00.02 may Setup web page.
cause the gateway to crash. Time Synch is currently switched off in the
Device Manager software Settings.config file:
<add key="PerformGatewayTimesynch"
value="False"/>
Network ID and Join Key Parameters
The gateway parameters that allow the sensors to join the network are the Network ID
and Join Key. The following table shows the three built-in Network ID options provided
by SKF USA, Inc.
Type of Network Network ID and Join Key

Production network with Use one of the built-in Network IDs (101 or 102) and the
built-in settings factory default Join Key. Built-in network settings are manually
selected on the sensor.
A commissioning network is unnecessary to configure the
sensors to join the production network.
(You should not use 1229 in a production network.)
Commissioning network Allows out-of-the-box sensors to join using the factory default
Network ID (1229) and the factory default Join Key.
Then, modify the default settings to the customized production
network settings before deploying the sensors in the production
network.
(You should not use 1229 in a production network.)
One of the built-in Network ID settings (101 or 102) can be used for a new production
network installation. With the sensors manually set up with either of the built-in
Network ID settings (101 or 102) and the gateway configured accordingly, the
production network is quickly set up and a commissioning network is unnecessary. If
the customer wants to use a customized production Network ID, then a commissioning
network (factory default Network ID 1229) should be set up to customize the sensors
network parameters and test communication between the gateway and the sensors
before final installation.
Pre-configuration services for a customer network can be
arranged through CSG. SKF configures the sensors to join the
production network with the customized Network ID and Join Key
obtained from the customer.

Service Manual
Preparing a Commissioning Gateway
The commissioning gateway always uses the SKF factory default network settings. The
commissioning gateway and sensors being commissioned should be located away from
the production networks signal range (both will temporarily have the same Network ID
and Join Key when the new sensors are switched to the production network settings).
You will use the commissioning gateway to accomplish the following tasks:
Configure new sensors from the factory to join the production network. (Refer to
Chapter 9, System Maintenance, Adding a New Sensor into Service.)
Modify the Long Tag of a sensor to monitor a different machine. (Refer to Chapter
9, System Maintenance, Editing a Sensors Name.)
Configure a new sensor to replace a sensor in the production network. (Refer to
Chapter 9, System Maintenance, Replacing an Existing Sensor in Service.)
Setting up a Commissioning Gateway

To set up a commissioning gateway:
On the gateways web page, expand Parameter to enter Identification parameters
for the gateway to best identify it on the local area network (LAN): Device Long
Tag, Device Tag, Descriptor.
Figure 10.
Enter Descriptive Device Information.
Next, expand Wired Communication > Interfaces > Ethernet. Enter a static IP
address and Netmask settings for the gateway to connect to the LAN.

Service Manual
Figure 11.
Connect the gateway to the LAN.
Click the Write Ethernet Informations >> button to update the gateway with the
LAN settings. The gateway should be configured now to communicate using the
LAN.
Disconnect the Ethernet cable from the configuration computer and connect it
directly to your LAN.
Launch the gateways web page in the Device Manager host computer to continue
configuring the gateway.
Modify the Ethernet Port Number to the SKF default port of 20004 for the Device
Manager connection.
Figure 12.
Ethernet Port Number.
Verify the current network settings by expanding Parameter > Wireless

Communication > Setup. If the gateway is from SKF, the default commissioning
network ID of 1229 will display and the default Join Keys will be present, but
masked. (The Join Keys are shown on the following page.)
If the Network ID is 1229 and the Join Keys of the commissioning network are present,
the network is ready for the new sensors to join the commissioning network.

Service Manual
If the gateway is not from SKF, or you see a different Network ID,
instructions for changing the network settings are provided below
in the section, Steps to configure a commissioning gateway.
Figure 13.
Verify the Network ID.
If the P+F gateway is NOT from SKF, or if the Network ID is different, then
complete the following steps.
Steps to configure a commissioning gateway:
Set DIP switch 8 to the up

position to disable the security
mode and enable the write
function.
Expand Parameter > Wireless

Communication > Setup.
Change the gateways Network ID SKF Factory Network ID: 1229

and Join Key to the SKF defaults SKF Factory Join Key:
for the commissioning network. 44555354
Note: The gateway requires the 4E455457
Network ID and Join Key to be set 4F524B53
together. The Join Key field is not 524F434B
case sensitive.
Click Write Join Information and
confirm the prompts.
When the upload is done, return
DIP switch 8 to the down position
to disable the write function and
enable the security mode again.

Service Manual
Joining the Sensors to the Commissioning Network
Expand Additional Functions >

Reset.
Click Reform Network to activate
the new network settings.
After the network reform is complete, the network is ready for the new sensors to join
the commissioning network.
Joining the Sensors to the Commissioning Network
If many sensors (50 or more) will be joining the network, Global Advertising can be
initiated to speed up the process. The Global Advertising (or Active Advertising) function
can save considerable time when joining new sensors to the network; the joining
process may be up to 16 times faster with advertising on. The only cost for the time
saved is higher battery consumption temporarily on all devices in the network during
the advertising phase.
Because Global Advertising increases energy consumption of the networks devices, it is
recommended that you use it only when needed, that is, when you expect new devices
to join the network. Note that you can activate Global Advertising without reforming the
network.
To start Global Advertising:
From the gateways Setup web page, you can enter the number of minutes (1 to 255)
to Global Advertising Timeout. Then, click Activate Global Advertising.
Or
From Device Manager, select the gateway hierarchy item. Click the Set Active
Advertising On button.
This function works only with P+F gateways. It will not work with
WirelessHART gateways from other manufacturers.
To start joining the sensors:
Activate the sensors and let them join the commissioning network using the factory
default settings.
Go to the gateways web page to check the sensors status.
As the sensors successfully join the network, they will appear in the Com Stat column of
the gateways Operating Modes web page (refresh the page manually).

Service Manual
P+F Gateways Installation Torque
The Production Network Settings

You can follow the same steps shown above in the section, Steps to configure a
commissioning gateway, to modify the gateways network join settings from the factory
defaults to the final customized settings. However, the network settings modified in this
way are applied only to the gateway.
The gateway will not propagate modified network join settings to the sensors. Only the
Device Manager software enables you to change the gateway settings and also
propagates the new settings to all sensors in the network. This procedure is presented
in Chapter 5, Changing the Network ID and Join Key.
P+F Gateways Installation Torque
The table below provides a guide to tightening the cable glands and cover in order to
maintain the gateways IP rating.
Installation Torque for Cable Glands Type of Cable Glands

2.5 Nm (22 lb-in.) Plastic
4.11 Nm (36 lb-in.) Nickel plated brass
4.11 Nm (36 lb-in.) Stainless steel
Installation Torque for Housing Cover
2.5 Nm (22 lb-in.)

Service Manual
Comparing P+F with Emerson Gateways
Comparing P+F with Emerson Gateways
The table below presents a couple of known differences between the P+F gateway
versus an Emerson gateway. The compatibility of Device Manager and the Emerson
gateway is still under investigation.
P+F Gateway Emerson Gateway
All gateway functions described The functions in the Device Manager Gateway /
for CMWA 8800 in the Wireless Admin tab do not work.
Machine Condition Sensor
Setup Guide and the Wireless
Sensor Device Manager User
Manual should work.
Supports Command 93 for Does not cache Command 93 data. Command 9

caching measured values in must be used to publish trend values. The gateway
gateway memory. Publishes the date/time stamps the measurements when the
last 12 PV (Velocity RMS), SV values are received. The stamps may be off by as
(Env.Acc.Pk-Pk), TV much as one cyclic update interval.
(Temperature) values at 20 min
intervals in a 60 min cycle for
trending. Measurements have
the accurate date/time stamp of
when they were sampled.

Service Manual
4
Wireless Sensor Device Manager
In this chapter, we will present details about installing Device Manager, including
potential problems that may occur. We cover the process of enabling communication in
the network devices and connecting to the gateway, including troubleshooting a failed
connection. A table summarizing known issues with Device Manager is provided.
Additional topics in this chapter include:
Full routing vs. leaf node sensor function
Expert features for service personnel
Data collection scheduling
Manual data collection
Device Manager Installation
Device Manager CD contents:

dotNetFx45_Full_setup.exe
Wireless Sensor Device Manager software
Wireless Sensor Device Manager User Manual
P&F Gateway User Manual
P&F Adapter User Manual

Service Manual
To Install Device Manager
Verify dot Net 4.5 is installed. If

not, install it.
On the Windows 7 or Windows
2008 server, disable User Access
Control (UAC) before installing
Device Manager. Go to Start >
Control Panel and search for uac.
Change the setting to Never notify.
Restart the computer to initiate this
change.
Install MS SQL Server 2008 R2.

(The Express version is available on
the Analyst CD.)
Copy the Server Name string for
later use. You will use the Server
Name as the Database Server for
Device Manager.
The Microsoft Windows user

account must have Administrative
privileges on the local PC to install
and operate Device Manager.
Install Device Manager by following
the Setup Wizard to completion.
Reset the UAC to its original setting

and restart the computer to initiate
the UAC change.

Service Manual
Known Issue #1 Cannot open database
Issue: Device Manager installation

appears to be complete but an error
message appears when you try to
launch the software.
Cause: Unable to disable UAC due to
IT security.
Go to Program Files > SKF-
RS/Wireless Sensor Device
Manager -8800/DB.
Right-click the DB folder.
Go to the DB Properties dialog,
Security tab.
Select Everyone.
(Note: If Everyone does not exist,
click Edit. Then, click Add to create
Everyone.)
Click Edit.
Check Allow for Full control.
Click OK.
Manually attach the database to SQL

Server by using the following steps:
Right-click the Database.

Select Attach to open the Attach
Databases dialog.

Service Manual
In the Attach Databases dialog, click

Add.
In the search window, locate the

database file under the pathway
SKF-RS/Wireless Sensor Device
Manager 8800/DB/.
Select the .mdf file.
Click OK.
In the Attach Databases dialog,

confirm the CMWA8800 database is
the one you want to attach.
Note: You must use the same
Database name that was provided for
the initial installation. For this
example, the database name is
CMWA8800.
Click OK.

Service Manual
The CMWA8800 database now

appears under /Databases under the
computer ID SQLEXPRESS
Known Issue #2 Replace the database
Issue: Device Manager installation The database has been manually attached, but an error
appears to be complete but an error message complains that a column is missing in the table.
message appears when you try to Solution: (depicted below)
launch the software. Detach the database from SQL Server Engine.
Cause: The installation script was Replace the database files with known working database files.
prohibited from updating the Re-attach the database.
database file during the installation.
Manually detach the database to SQL
Server by using the following steps:
Go to the CMWA8800 folder under

/Databases under the computer ID
SQLEXPRESS.
Right-click the CMWA8800 folder.

Select Tasks > Detach to open the
Detach Database dialog.

Service Manual
In the Detach Database dialog, select

the check boxes Drop and Update.
Click OK.
Next, you must replace the database

files with known working database
files, such as WiMon.mdf,
WiMon_log.ldf. Then, re-attach the
database. Follow the steps below.
In the search window, locate the

database file under the path SKF-
RS/Wireless Sensor Device Manager
8800/DB/.
Select the .mdf file.
Click OK.
Note: A copy of an updated version
of the database is included on the CD.
Copy the database file from the CD to
the DB folder before re-attaching the
database file.
In the Attach Database dialog,
confirm the CMWA8800 database as
the one you want to attach.
Note: You must use the same
database name that was provided for
the initial installation.
Click OK.

Service Manual
The CMWA8800 database now

appears under /Databases under the
computer ID SQLEXPRESS

Service Manual
Connecting to the Gateway
The first time Device Manager is launched, the system hierarchy needs to be created.
Refer to the Wireless Sensor Device Manager User Manual for details.
Right-click the root node SKF

Wireless Machine Condition
Sensor System and select
New Plant to create the
plant.
The Plant will display the
Batch Service Management
tab. The Batch Service should
remain Stopped at this time.
Right-click the plant hierarchy

item and select New Network
to create the network.
Right-click the network

hierarchy item and select New
Gateway to create the
gateway.
Enter the IP Address and the
Port Number.
In the Gateway / Properties

tab, click the Gateway
Communication Enable
button.
When communication is
established with the gateway,
the red area changes to green
and the message text updates
to Communication is
enabled.
The gateway connection
should be established too.

Service Manual
Issue: Gateway Connection Failed

It may happen that communication with the gateway is enabled but the gateway is not
connected.
Issue: Gateway is not

connected. The red message
Gateway is not connected
does not change.
One or more of the following Incorrect gateway IP Address

items may be at fault. Check Incorrect Port Number (Remote) (default is 20004)
each item to find the
problem. Incorrect Polling Address (must match the polling address DIP
switch setting default is 0 with all switches in down position)
Gateway and PC are in different subnets
Gateway is faulty
Network cable is faulty
Faulty network hardware (card and/or cable)
Firewall security is blocking the ports used by Device Manager
Troubleshooting the Required Ports

If the Device Manager PC is able to access the gateways web page but Device Manager
failed to connect, a network security firewall may be blocking the ports needed by the
Device Manager software. The following ports are required by default:
Destination: 20004. The gateways UDP server listens at port 20004 (SKF default).
You can test 20004 by connecting to the Telnet server in the gateway from the
host PC. Go to
http://social.technet.microsoft.com/wiki/contents/articles/910.enabling-telnet-
client-in-windows-7.aspx to enable Telnet client in the Device Manager computer.
From the Device Manager computer, in the DOS cmd window, enter Telnet
<Gateway IP address> 20004.
Source: 7000 to 7010. Device Manager uses ports 7000 to 7010 (SKF default) to
initiate communication with the gateways in the network. Ask IT to open these
ports in the firewall.
Two ports in the Port Number Range are used for each gateway. The first port (7000) is
used by the Device Manager UI and the next port (7001) is used by the batch service to
connect with the first gateway, and so on, as shown below.

Service Manual
Figure 14.
Source and Destination Ports for Multiple Gateways.
By default, the Device Manager software initially reserves 10 ports in the network. If
more than five gateways are to be installed, expand the range accordingly. Contact IT
to open these additional ports in the firewall.
Figure 15.
Port Number Range.

Service Manual
Importing Sensors into Device Manager

After Device Manager is connected to the gateway, the list of sensors that are
connected to the gateway need to be imported into Device Manager. Refer to the
Wireless Sensor Device Manager 8800 User Manual for details.
WARNING! First, make sure the batch
service is stopped!
The sensors must be turned on and
appear green in the Com. Stat.
column of the gateways Operating
Modes web page. This is the list of
sensors that will be imported into
Device Manager.
Right click the gateway in the Device
Manager hierarchy.
Select the Find sensors option.
The sensors stored in the gateway are
uploaded to the Device Managers
database.
Once imported, the sensors will
display under the gateway item.
The first time the hierarchy structure is built, the Device Manager
software also uploads the current configuration data from all
wireless sensors branching from the gateway. This may take
several minutes (even tens of minutes) to complete, depending on
the number of sensors.

Service Manual
Verifying the Sensor Firmware
Viewing the Connected Sensors

To view the connected wireless sensors in the Device Manager hierarchy:
Click the + (open) next to the gateway and CMWA 8800 Sensors hierarchy icons to
expand the sensor list.
Figure 16.
Two Wireless Sensors Displayed in the Hierarchy.
The following icon color codes are used to indicate communication status:
Green Indicates that the sensor is available and no active communication is
taking place.
Yellow Indicates that the Device Manager software and sensor are
communicating with each other.
Blue Indicates that the Device Manager softwares batch service and the
sensor are communicating, and the sensor is not currently available from the
Device Manager user interface.
Red Indicates that the sensor cannot be reached.
Verifying the Sensor Firmware
After Device Manager is connected to the gateway and the sensors are imported into
the Device Manager database, you can verify that the sensor firmware is the latest
released version. The current released version is 79 or later.
Figure 17.
Sensor Firmware Tab, Software Revision.

Service Manual
Known Issues in Device Manager
Known Issues in Device Manager

Device Manager shows an empty window upon Delete the file DockPanel.config in the
opening. \Program Files\SKF-RS\Wireless Sensor Device
Cause: The GUI layout file has been corrupted. Manager 8800 folder in the root drive and
then re-launch the software.
Unhandled Exception when closing the Device Install DotNet45.
Manager GUI in Windows 7. dotNetFx45_Full_setup.exe is on CD from SKF.
Cause: Incompatible DotNet version. An Internet connection is required.
Gateway connection status cycles between Make sure there is only one HART UDP master in
connected and disconnected. each network.
Cause: Port conflict at the gateway. Another
HART UDP master, such as another Device
Manager instance in the same network has
connected to the gateway and reserved the
configured ports.
A waveform took too long to upload. Solution #1:
Cause #1: Gateway firmware may be an older Verify the gateway is running the latest firmware
version. version 02.00.20.
A waveform took too long to upload. Solution #2:
Cause #2: Probably related to missing fast pipe Check the gateways Operating Modes web page
for the operation. It should take about 2.5 to see if the fast pipe is granted to the wrong
minutes for a one hop sensor with fast pipe to sensor. If the fast pipe is granted to a sensor
upload the time waveforms. The time increases that is not currently sending waveform data or
proportionally for more hops. receiving a firmware download, deselect the
check box in the Operating Modes web page to
release the fast pipe.
[See the following topic: Full Routing vs. Leaf
Node.] Make sure the sensor with the issue of the long
waveform upload time is configured for Full
routing in the Sensor > Status tab.
Manually start a waveform upload and then
confirm in the gateways web page that the fast
pipe is granted to the sensor.

Service Manual
Full Routing vs. Leaf Node
Full Routing vs. Leaf Node
The Power profile of all sensors must be set to Full routing (high power profile) mode
in the Sensor > Status tab. The network manager in the gateway grants fast pipe
capability only to sensors with the Full Routing power profile. Fast pipe capability is
desired for waveform collection and firmware upgrades.
Figure 18.
Power Profile Full Routing Option.
IMPORTANT! Having all the sensors serve as routers will increase sensor power
consumption. See below for a solution.
Having all the sensors serve as routers will increase sensor power consumption but
there is a solution to this situation. The actual routing capability is set in the gateways
Operating Modes web page. In the Routing Device column, deselect the check boxes
for the sensors so that the network manager will not use the sensor for routing. The
sensors will instead function as leaf nodes to conserve power.

Service Manual
Expert Features in Device Manager
Activate the Expert Features in Device Manager by changing the value of the LocalTest
key to True in the Settings.config file (<add key="LocalTest" value="True"/>). Then,
launch the Device Manager software. Select a sensor in the Device Manager hierarchy
and open the Device tab.
Figure 19.
Sensor > Device Tab with Expert Features Activated.
Wireless or Wired Communication

At the top of the Sensor > Device tab, the expert feature Use wireless / wired
communication displays. Wireless usage must be established first. Then, wired
communication is started by connecting an RS485 modem cable and selecting the
wired option button.
Wireless communication is the standard

operating mode for the sensor.
Wired communication is used in the factory to

talk to the sensor directly to download the
firmware more quickly (about 5 minutes
instead of 25 minutes wirelessly).

Service Manual
Calibration
Calibration is performed during manufacturing. If calibration is needed in the field, it is
important that velocity is calibrated first because the sensor simultaneously makes a
new calibration of the envelope based upon the Pre-calibration factor stored at
manufacturing time.
When the envelope is calibrated, a new Pre-calibration factor is calculated and stored
in the sensor, based upon the new calibrated values of velocity and envelope.
If you want to restore the original Pre-calibration factor stored
at manufacturing time, you must obtain that number and enter it
in Calibration value field. Click Write Pre-Calibration to restore
this value.
How to perform velocity calibration:
Deselect the Use Cache check
box in the gateways Admin tab
to disable the automatic data
collection function.
Set the sensor on a shaker

table.
Apply the velocity calibration
reference at 138 mm/s or 10g
@ 80 Hz.
Enter the velocity reference in
the Calibration value box.
Click Perform Velocity
Calibration. Wait 50 seconds
for the calibration to take effect.
Apply a different frequency and
amplitude setting on the shaker.
For example, 10 mm/s at
700 Hz.
Manually take an overall reading
to verify the velocity calibration
is okay. The overall velocity
should be between 8.88 to 9.2
mm/s.
Go to the Sensor / Process /
Process Data tab and enable
Velocity RMS.
Click Get current values.
Enter the calibration date in the
Date fields on the Device tab.
Enable the Use Cache function
when calibration is complete.
WARNING! Do not modify the Final Assembly Number (FAN).

Service Manual
How to perform envelope calibration:

Enveloped acceleration calibration is not usually necessary. It is automatically calibrated
when the velocity calibration is completed. Enveloped acceleration calibration follows
the same steps as velocity. For accurate calibration of envelope, an amplitude
modulated signal must be applied, for example, 9.82 m/s2 at 2 kHz with 100 Hz @
100% amplitude modulation.
Generic Command Feature

The Generic Command feature allows the expert user to send HART commands directly
to the sensor.
Figure 20.
Sensor > Generic Command Tab.
Here is an example of sending a HART command to the sensor. Command 125 Write
Battery Voltage Threshold Value sets the threshold value for the Battery critically low
alarm. The default value is 3.3 V. The 3.3 V threshold may need to be lowered for
high temperature applications (60 to 85 C, 140 to 185 F) by using the generic
command.
Figure 21.
Generic Command Example.
As shown in the figure above, the setting for critical Power Failure is changed to 2.93 V,
where 403B851E entered in the Data field is the IEEE hex format for 2.93 V decimal
number. Press the Send button to send the command to the sensor.

Service Manual
Data Collection Scheduling
With Device Manager installed, connected to the gateway and operational, refer to the
Wireless Sensor Device Manager User Manual for details on continuing to build the
wireless systems hierarchy, configuring the sensors and scheduling data collection.
This Service Manual presents some recommended setup guidelines for data collection
scheduling and examples for your convenience.
Coordination between settings on various setup tabs is required to properly set up your
wireless sensor data collection. Setup guidelines are provided in the following table,
which indicates the recommended wireless sensor setup for monitoring standard
machinery running at standard speeds (between 1500 and 3600 RPM).
The recommended setup shown in the table assumes that you
are collecting vibration overalls, temperature, and battery
measurements using burst mode. Recall that with burst mode
the sensor publishes data at regular intervals and burst data are
saved in gateway memory. When queried by the host software,
the gateway returns the cache data.
The figure following the table illustrates the recommended Sensor > Burst Control
message settings as described in the table, using Trending Command 93. It shows the
default setup for the wireless sensors joined to a P+F gateway.

Service Manual
Recommended Wireless Sensor Settings for Standard Machinery (1500 3600 RPM)
Sensor > Device Specify the sensors identification (long tag name) and machine speed.
Specify the sensors vibration cyclic update interval and the trending command to use; and
Sensor > Data
specify which measurements the sensor performs and the polling schedule to retrieve and
Collection
store them in the Device Manager database.
Vibration Cyclic Start time 00:00
Enable 1 hour
Update (midnight)
Trending Command 93
Command (CMD93)
Velocity and
Reference time
Envelope Enable Period 24 hours
user preference
Waveform
Reference time
Envelope Pk-Pk Period not
not configurable
and Velocity RMS Enable configurable when
when CMD93 is
(vibration overalls) CMD93 is selected
selected
Temperature Enable N/A Period 1 hour
Gateway > When using burst mode (recommended), specify for Device Manager to retrieve vibration
Admin overalls, temperature, and battery measurement results from the gateways cache.
Use Cache Enable
Sensor > Burst When using burst mode (recommended), specify which measurements the sensor bursts to
Control the gateways cache, and their burst interval.
Message 2 - Message
Burst Mode Message 0 - On Message 1 - On
On 3- Off
Update
20 minutes 60 minutes 60 minutes N/A
Period
Command 9
Slot 0 Battery
Life Command 3
Command / Slot 1 Battery (optional) for
Command 93 N/A
Slot Voltage HART OPC
Slot 2 Battery systems only
Charge
Slot 3 - None
Sensor > Status Each sensors power profile should be set to Full Routing.
To preserve sensor battery life, disable the routing capability on the gateways Operating
Modes web page, in the Routing Device column.

Service Manual
Figure 22.
Recommended Setup for Wireless Sensors Joined to a P+F Gateway.
Notice that the sensor publishes the primary, secondary, and tertiary variables 20
minutes apart, according to the designated Update Period. For example, velocity data
are published at the top of the hour, enveloped acceleration data 20 minutes later, and
then temperature data 20 minutes after that, equaling a 60 minute cycle, as illustrated
below.

Service Manual
Figure 23.
One Data Publishing Cycle, Including the Update Periods.
Note that in the preceding sensor setup table we recommend a setup that polls the
sensors every 24 hours for waveform data, and that polls the gateways cache every
hour for vibration overalls and temperature data (using burst mode). Collecting overalls
and temperature data hourly on noncritical machinery may seem excessive to those
familiar with traditional vibration monitoring technologies. However, it is important to
realize that HART process information systems working with OPC compliant host
servers typically update their data in minutes, and that vibration / temperature data
stored in the gateways cache may be used by these existing process information
systems. Bursting the overalls to the gateway cache hourly makes sense in these
scenarios.
If you want to extend your trend intervals, you may choose to extend the Sensor > Data
Collection tabs Vibration Cyclic Update for the Envelope Pk-Pk and Velocity RMS /
Temperature measurements up to 24 hours (an example is provided below).
IMPORTANT: You must stop the Batch Service temporarily when you are making
any revisions to the data collection schedule. Remember to start it again for
normal operation when you are done.
To stop the Batch Service:

Select the Plant in the Device Manager
hierarchy list.
The Plant will display the Batch Service
Management tab. Click Stop if the Batch
Service is running.

Service Manual
The Use Cache Check Box

The Use Cache check box must be enabled in order for burst mode to work. Device
Manager will not retrieve the sensors measurement results from the gateways cache if
this function is disabled.
To find the Use Cache check box:

Select the gateway in the Device Manager
plant hierarchy list.
Select the Admin tab.
The Use Cache check box is at the bottom
of the Admin tab.
WARNING! You must temporarily disable Use Cache when you are collecting
process data manually. Remember to enable it again for normal operation when
you are done.

Service Manual
Command 93 Example
The first example illustrates a sensor configured with Command 93 (burst mode). The
sensor always bursts the last 12 measurements with accurate date/time stamps. The
system can still recover the last 12 measurements (the trend) even after the gateway
has been down for that period of time.
Figure 24.
Command 93 Burst Mode Data Collection Tab Example.
In Figure 25, the last column on the right shows the trend collection schedule with the
Vibration Cyclic Update set at one, two and three hour intervals, based on the
respective Starting at time. The Starting at time (or Start Time, outlined in red above)
specifies when to take the first measurement of the day. The Vibration Cyclic Update
is the time interval at which the sensor samples a new set of measurements and saves
them in its memory. With the burst Update Period set to 20 minutes (see Figure 22),
the publishing cycle duration is one hour, as shown in Figure 23. The Update Period of
20 minutes works fine for the 1-hour Vibration Cyclic Update interval. However, the 20
minute setting would waste battery power for the 2-hour and 3-hour Vibration Cyclic
Update intervals because the sensor would burst the same set of measurements twice
at one hour intervals with the 2-hour Cyclic Update and three times at one hour
intervals with the 3-hour Cyclic Update. If the Update Period is modified to 40 minutes
for the 2-hour Cyclic Update, and 60 minutes for the 3-hour Cyclic Update, then the
sensor will burst only the new set of measurements once per Vibration Cyclic Update
interval.

Service Manual
Figure 25.
Overall Trending Measurement Schedules.
In Figure 26, the last column on the right shows the waveform collection schedules with
the Vibration Cyclic Update set at one, two and three hour intervals, according to the
respective Starting at time (or Start Time), Reference Time and Period. The
Reference Time is when the Device Manager queries the sensor for the first
measurement of the day, at 8:05 a.m. in this example. The Period is how often the
query is repeated, every 24 hours in this example. The date time stamp (DTS) of the
collected waveform is not at 8:05 a.m. because the sensor only returns the waveform
sampled during its previous Vibration Cyclic Update, which was at 7:30 a.m. for the 1-
hour and 2-hour Cyclic Updates and at 5:30 a.m. for the 3-hour Cyclic Update.
Figure 26.
Waveform Measurement Schedules.
In Figure 27, the last column on the right shows the valid Possible Data Collection
Periods of temperature data for the burst Update Periods of 20, 40 and 60 minutes.
Unlike the vibration readings, the temperature sampling interval is fixed at every 5
minutes regardless of the Vibration Cyclic Update. As a result, with the burst Update
Period set at 20 minutes (which equals a 1-hour burst publishing cycle), all 12
measurements collected within the hour are published to the gateway every hour.
Therefore, all Collection Periods 5, 10, 15, 20, 30 and 60 minutes are valid. Only
the 60 minute Collection Period makes sense with the burst Update Periods set to 40
minutes or 60 minutes, which are equivalent to 2-hour and 3-hour publishing cycles,
respectively.
For 2-hour and 3-hour Vibration Cyclic Updates, you must still
use the 20 minute Update Period if you want to collect
temperature data more often than 60 minutes apart.

Service Manual
Figure 27.
Temperature Trend Measurement Schedules.
IMPORTANT: Some gateway manufacturers do not support Command 93 caching

(e.g., Emmerson and Siemens gateways). If you are using non P+F gateways, you must
use a Command 9 burst message to burst your vibration overalls and temperature
measurement results for use with Device Manager and Analyst systems.
The timeline depicted in Figure 28 is a visual representation of the sequence of events

(the actual times may vary) described above using the Data Collection tab settings
defined as shown in Figure 24. These settings include:
The Vibration Cyclic Update is 1 hour, starting at 00:30.
The waveform Reference Time is 08:05.
The waveform Period is 24 hours.
The temperature Period is 60 minutes.

Service Manual
Figure 28.
Timeline Representing the Sequence of Events Scheduled.
This timeline assumes the network activity begins at 00:00 of the first day. The last
event shown is the bursting of enveloped acceleration Pk-Pk data to the gateway at
23:40. The vibration measurements taken are indicated by VM and are numbered
sequentially (VM1, VM2, etc.). The velocity RMS and the enveloped acceleration Pk-Pk
measurements are collected at the same time. However, they are burst to the gateway
separately.

Service Manual
The colors of the lines are explained as follows:

The black lines represent when the vibration measurements (VM#) are taken: at
30 minutes after the hour.
The blue lines represent when the velocity RMS measurement data is scheduled to
burst: at 20 minutes after the hour, according to the one hour Vibration Cyclic
Update setting.
The red lines represent when the enveloped acceleration Pk-Pk measurement data
is scheduled to burst: at 40 minutes after the hour, according to the one hour
Vibration Cyclic Update setting.
The orange lines represent when the temperature measurement data is scheduled
to burst: at the hour (60 minutes). Because the sensor always takes temperature
readings every 5 minutes, the sensor can burst the most recent 12 temperature
measurements after each hour. (The temperature measurements at 5 minutes
apart were omitted from the timeline.)
The dashed purple line represents when the most recently collected waveform data
is requested by Device Manager: at 08:05 of every 24 hour period.
The sequence of events for the day can be described as follows:
With the system coming on line at 00:00, the first temperature reading is taken at
00:05. Subsequent temperature measurements are taken every 5 minutes and at
01:00 the total of 12 taken so far are burst to the gateway.
The first vibration measurement, VM1, is collected at 00:30. VM1 velocity RMS
data is burst at 01:20.
VM2 is collected at 01:30. VM2 and VM1 enveloped acceleration Pk-Pk is burst at
01:40. Remember that the sensor will burst up to the last 12 measurements in
memory.
VM2 and VM1 velocity RMS data is burst at 02:20.
At 02:00, the previous 12 temperature measurements are burst to the gateway.
This is scheduled to occur on the hour, every hour, and is not mentioned again in
this discussion.
VM3 is collected at 02:30. VM3, VM2 and VM1 enveloped acceleration Pk-Pk is
burst at 02:40.
VM3, VM2 and VM1 velocity RMS data is burst at 03:20.
VM4 continues this pattern.
We pick up again with VM8 data collected at 07:30. VM8 through VM1 enveloped
acceleration Pk-Pk is burst at 07:40.
Device Manager requests the latest velocity and enveloped waveform at 08:05.
The 7:30 measurement (VM8) will be sent from the sensor memory.
VM8 through VM1 velocity RMS data is burst at 08:20.
VM9 is collected at 08:30. VM9 through VM1 enveloped acceleration Pk-Pk is
burst at 08:40.
VM9 through VM1 velocity RMS data is burst at 09:20.

Service Manual
VM10 continues this pattern, building up a total of 12 measurements to be sent

with each burst. And so on through the day.
VM24, the last measurement of the first day, is taken at 23:30. VM24 through
VM13 enveloped acceleration Pk-Pk is burst at 23:40.
Thus ends the timeline. Not shown is the activity on the following day when VM24
through VM13 velocity RMS data is burst at 00:20.
If the Period entries and the cyclic update interval do not evenly
divide 24 hours, then the remaining hours do not carry over into
the next day or change the timing of events.

Service Manual
Command 9 Example
The second example illustrates Command 9. If the network is using a non P+F gateway
that does not support caching Command 93, then you must use Command 9 to burst
the sensors Envelope Pk-Pk, Velocity RMS, and Temperature measurement results to
the gateways cache (with less accurate date / time stamps).
Figure 29.
Command 9 Burst Mode Burst Control Tab.
Figure 30.
Command 9 Burst Mode Data Collection Tab.

Service Manual
Exporting the Measurement Collection Period
Figure 31.
Overall Trending Measurement Schedule.
Estimating the Time to Capture Waveforms

How many waveforms can a single instance of Device Manager collect within 24 hours?
Sampling is fast; sending and receiving data is much slower.
It takes about three minutes to collect a waveform from a sensor with the fast pipe
designation that is a single hop from the gateway. That equals 20 waveforms per hour
or 480 waveforms per day. Therefore, if there are more than 480 sensors in the
network, a single instance of Device Manager may not be able to collect all the
waveforms within a day. This speed reflects a limitation of the system with a single
instance of Device Manager.
Each hop adds about three minutes (with the fast pipe), therefore two hops = about six
minutes; three hops = about nine minutes. The number of hops taken can be found in
the gateways Diagnostics Details web page or the Network Statistics Report.
Exporting the Measurement Collection Period
The data collection schedule in the Sensor > Data Collection tab is automatically
exported to update the corresponding points in Analyst.
When using Command 9 as the Trend Command in Device Manager, for velocity and
enveloped acceleration point, the most frequent data collection interval between the
overall and the waveform is exported to the Schedule tab in the POINTs properties in
Analyst. However, when using Command 93, the waveform period is always exported
even if the cyclic update period is more frequent.

Service Manual
Manual Data Collection
Overall Data
If you need to collect overall data manually, follow these steps.
Deselect the Use Cache check box

in the gateways Admin tab to
disable the automatic data
collection function.
To export the manual overall data

to Analyst, you must temporarily
select Command 9 as the
Trending Command.
Select a sensor in the Device
Manager hierarchy.
Open the Data Collection tab.
Select Command 9.
Open the Process tab > Process

Data.
Click Get current values.
Enabled overall vibration and
temperature measurements will be
collected and uploaded to the
Device Manager database. The
new measurement results display.

Service Manual
If the export feature in the Plant >

Export tab is enabled, then the
collected measurement is also
exported to Analyst.
When you are done, remember to
enable the Use Cache check box
again for normal operation.
Return the Trending Command to
Command 93.
Waveform Data
If you need to manually collect waveform data, follow these steps. In the hierarchy,
right-click the desired sensor and select Collect Waveform from the context menu.
The vibration measurement is performed and the progress of the measurement is
displayed. The waveform measurement data is uploaded for the selected sensor. If the
export feature in the Plant > Export tab is enabled, then the collected measurement is
also exported to Analyst.
Figure 32.
Manually Collecting Waveform Data.

Service Manual
5
Changing the Network ID and Join Key
You can change the Network ID and Join Key of the entire network in Device Managers
Gateway > Admin tab. With this method, you can change a tested commissioning
network to the values of the production network and the values are propagated
throughout the network to the sensors. Recall that changing the Network ID on the
gateways web page does not change the entire network.
How to change the Network ID and Join Key of the entire network:
Select the desired gateway in the Device Manager hierarchy.
Click the Admin tab to open it.
Figure 33.
Exchange Network Id and Exchange Join Key Buttons.
Enter the new Network ID in the Network Id field.

If you click Read Network Id, the current Network ID will populate
the Network Id field.
Click Exchange Network Id to send the new Network ID to the network manager
and its connected sensors.
Enter the new Join Key in the Join Key field. The Join Key field is not case
sensitive.
Click Exchange Join Key to send the new Join Key to the network manager and its
connected sensors.
Wait for the network manager to propagate the new settings to all its sensors.

Service Manual
Changing the Network ID and Join Key
Note: The time it takes for all the wireless sensors to update with
the new Network ID and Join Key depends on the number of
sensors and the number of hops of the sensors to the gateway.
When the gateway and the sensors are less than 6 m (20 ft.)
apart with no obstruction in between, it takes at least an hour for
up to 30 sensors to update with the new settings. For a large
production network, it is recommended to modify the settings and
leave it overnight and then reform the network the next day.
Click Reform Network to activate the new settings.
If a sensor fails to join after the network is reformed, take the following actions:
If the sensor is within one hop of the gateway, reverse the Network ID and Join Key
to the previous settings.
Re-join the sensor to the network under the previous settings. (The sensors that
did join under the new settings would disconnect from the network.)
Then, repeat the change to the new Network ID and Join Key as described above,
and wait and reform the network.
If the sensor is more than one hop from the gateway, bring the sensor closer to within
one hop and follow steps above.

Service Manual
6
Troubleshooting XML Import to Analyst
WARNING! You must use SKF @ptitude Analyst 2012 (7400) MR2 with an XML
Import fix or later version. This version fixed an issue concerning Analyst rejecting
Command 93 overall or waveform measurements due to conflicting DTS.
Refer to the Wireless Sensor Device Manager 8800 User Manual for full instructions
on how to set up and enable data export from Device Manager to Analyst. This Service
Manual offers troubleshooting tips for pursuing XML import problems in Analyst.
If Analyst is not showing data for the POINTs of a sensor, follow the steps below.
Start by checking the XML import

setup. In Analyst, go to Customize >
Configure XML Import.
The XML Import Configuration dialog
opens.
Is the Enable processing check box

selected?
Yes Proceed to the next step.

No Enable processing.
Verify the Analyst Input directory path

matches the WSDM SKFExportFolder
key value in the Settings.config file.

No Correct the input directory path
so they match. If the Settings.config
file is changed, restart Device
Manager. Then, click Export node
information to re-export the node
data to the correct folder. (Plant >
Export tab, Export node information
button.) Settings.config file :
<add key="SKFExportFolder" value="C:\WSDM_Export\"/>

Service Manual
Verify the Analyst XML File prefix

matches the WSDM
SKFXMLExportPrefix key value in the
Settings.config file.
Verify the File prefix ends with an
underscore on the right side in the
XML Import Configuration. For
example WSDM_. (An underscore is
not required in the Settings.config file.)

No Correct the file prefix so they
match. If the Settings.config file is Settings.config file :
changed, restart Device Manager. <add key="SKFXMLExportPrefix" value="WSDM"/>
Then, click Export node information
to re-export the node data with the
correct prefix. (Plant > Export tab,
Export node information button.)
In Device Manager, confirm that the
Analyst Export is enabled. (Plant >
Export tab.)

No Enable the Analyst Export
function and verify that Device
Manager is exporting files to the target
input directory. Then, click Export
node information to export the node
data with the correct prefix. (Plant >
Export tab, Export node information
button.)
In Device Manager, confirm that the
Batch Service is running. (Plant >
Batch Service Management tab.)

No Start the Batch Service and
verify that Device Manager is exporting
files to the target input directory.
In Analyst, confirm the Transaction
Server is running.
Yes Restart the Transaction Service.

No Start the Transaction Service.

Service Manual
If there is still a problem with getting

data, check for any XML import errors
reported in the Analyst event log.
With all of these factors verified or corrected, wait long enough for the Transaction
Service to read the files. The waiting time depends on the Period value in the XML
Import Configuration dialog. (The recommended period of 0.017 hours equals one
minute.)

Service Manual
7
Network Planning and Diagnostics
In this chapter, we discuss general rules to follow when planning a new network or
extending an existing one. Important points about the devices, network capabilities and
communication stability are considered. The network diagnostic report is examined and
tips for troubleshooting common network problems are provided.
Network Planning
First, determine the location of the gateway. Ideally, it will be in the center of the
network to maximize the number of single hop connections. Elevation helps the
connectivity. It is best to mount the gateway with no obstruction around the antenna,
for example on a pole; otherwise, at least 15 cm (6 in.) away from the mounting wall.
Next, determine the number of 1-hop sensors, 2-hop sensors, etc. You can use a scale
map to place sensors (note: radio devices are also called motes) at all the required
sensing points for the network. If possible, the access points should be located near the
middle of the distribution of sensors to reduce latency and power usage. On the map,
mark the gateway and access point location(s). Draw a circle with a 50 m (164 ft.)
radius around the access point. Not all sensors within this circle will be able to
communicate directly with the access point, but some sensors outside the circle will, so
it will generally balance out. The number of sensors inside this circle approximates the
number of 1-hop sensors in the deployment.
Next, draw a 100 m (328 ft.) radius circle centered at the access point. The number of
sensors in the ring between 50 and 100 m approximates the number of 2-hop sensors.
Repeat this process with circles of increasing radius size until all sensors have been
encircled and note how many sensors are in each hop. Three hops is the maximum
recommended distance for any mesh network.
Important Considerations
WirelessHART documentation suggests at least 25% of the devices should have
direct connection with the access point (or gateway). The more devices in direct
connection with the access point the better; it improves stability and reduces
latency.
If possible, a sensor should have a maximum of three hops in practice or the
network performance may slow considerably. Use multiple gateways if more than
three hops are required.
Each radio (sensor) should be within the estimated range of at least three other
devices to provide alternative links in the mesh network.
Disable the routing capability for the devices located at the sites perimeter to save
battery power and promote security. Do this on the gateways Operations Mode
web page in the Routing Device column.

Service Manual
Wireless Communication Stability Considerations
Consider elevating the mesh network if ground level is too congested with
obstructions. For example, elevated routers may receive the signals that are
obstructed at ground level and then route them to the gateway, as shown in the
following figure.
Figure 34.
Diagram of an Elevated Mesh Network,
Red Lines Indicate Communication Paths Blocked by Obstacles.
Location and Signal Strength

Radio signal strength decreases in free space with the inverse square of the distance; an
example of Free Space Path Loss (FSPL) is provided below with a link budget calculation
example. In an industrial environment, there are several potential obstacles for radio
waves, for example buildings, walls, pipes, or even moving obstacles like trucks. These
obstacles can reflect, bend, diffuse or block radio waves. The table below lists radio
signal attenuation through common obstacles (source is Dust Networks Inc.).
Material Signal attenuation
Clear glass window 2 dB

Brick wall 2 to 8 dB
Solid wood door 3 dB
Cubicles 3 to 5 dB
Cinder block wall 4 dB
Drywall/sheetrock wood framed 4 to 6 dB
Marble 5 dB

Service Manual
Material Signal attenuation
Metal frame glass with reflective coating (wall or 6 dB

window)
Interior office wall 6 dB
Glass window with security wire 8 dB
Concrete wall 10 to 15 dB
The wireless sensors sensitivity is approximately -90 dBm. For planning purposes, the
gateways transmitter power starts at 8 dBm and the antenna adds 2 dBi. Each obstacle
subtracts from the signal strength.
Link Budget Calculation Example
You can estimate the Receive Signal Strength Index (RSSI) at the sensor as shown in
this example. The gateway and a sensor are 50 m apart and there are two concrete
walls in between them.
P+F Gateway radio power 8 dBm
Antenna gain +2 dBi
FSPL (see note below) -74 dB
2 concrete walls -15 dB * 2
= -94 dBm (RSSI)

Because the estimated RSSI of -94 dBm is below the sensitivity of the receiver in the
sensor (-90 dBm), the connection will be marginal to bad. (Without the two concrete
walls, the RSSI of -64 dBm is a good connection.)
FSPL (dB) is Free Space Path Loss.
For 2.4 GHz, FSPL(dB) = 20log10(d) + 40.19, where d = distance
between the RF source and destination in meters.
For 50 m, FSPL = 20log10(50) + 40.19 = 74 dB.
The system margins can be determined by comparing this sensitivity with the received
signal level. Even with good signal strength, stability can be negatively influenced by
wireless networks or other noise emitters in the 2.4 GHz band. You can check the radio
RSSI and Stability on the gateways Diagnostics > Wireless Communication > Details
web page, which is discussed later in this chapter.

Service Manual
Figure 35.
The Gateways Details Web Page With RSSI and Stability.
Coexistence with WLAN

The Wireless Local Area Network (WLAN) and WirelessHART networks both fully utilize
the 2.4 GHz band. WLAN divides the 2.4 GHz band into 11 overlapping channels (see
the figure below), whereas WirelessHART divides the 2.4 GHz band into 16 distinct
channels. To avoid interference between WLAN channels, it is typical to use only
channels 1, 6, and 11 within the same frequency space because they do not overlap.
This allows WirelessHART to use some channels between 1 and 6, and some between 6
and 11. However, efficiency will be adversely affected.
Also, WLAN does not utilize the channels on a continuous basis. This allows
WirelessHART to use the full bandwidth when there is no WLAN traffic. In this case, the
efficiency of WirelessHART will be severely affected in periods with a lot of WLAN
activity (as transmit power for WLAN is high compared with WirelessHART).
A much better solution is achieved, for example, if the frequency space between WLAN
channels 7 through 11 is reserved for WirelessHART only, which is equivalent to
WirelessHART channels 10 through 16. This allows for continuous activity with
reasonable efficiency for the WirelessHART network.
The WirelessHART channels which fall within the busy WLAN channels can be
blacklisted using the Channel Blacklisting utility in the gateways web page. For details,
refer to Chapter 8, RF Interference and Solutions.

Service Manual
Figure 36.
WLAN Channels in the 2.4 GHz Frequency Band.
Table of WirelessHART Channel Frequencies
WHART Channels Frequency (GHz) WHART channel Frequency Range (GHz)
Center min max

1 2.405 2.4025 2.4075
2 2.41 2.4075 2.4125
3 2.415 2.4125 2.4175
4 2.42 2.4175 2.4225
5 2.425 2.4225 2.4275
6 2.43 2.4275 2.4325
7 2.435 2.4325 2.4375
8 2.44 2.4375 2.4425
9 2.445 2.4425 2.4475
10 2.45 2.4475 2.4525
11 2.455 2.4525 2.4575
12 2.46 2.4575 2.4625
13 2.465 2.4625 2.4675
14 2.47 2.4675 2.4725
15 2.475 2.4725 2.4775
16 2.48 2.4775 2.4825

Service Manual
Network Commissioning
Table of WLAN Channel Frequencies
WLAN Channels Center Frequency (GHz) WLAN channel Frequency Range (GHz)
Center min max

1 2.412 2.401 2.423
2 2.417 2.406 2.428
3 2.422 2.411 2.433
4 2.427 2.416 2.438
5 2.432 2.421 2.443
6 2.437 2.426 2.448
7 2.442 2.431 2.453
8 2.447 2.436 2.458
9 2.452 2.441 2.463
10 2.457 2.446 2.468
11 2.462 2.451 2.473
12 2.467 2.456 2.478
13 2.472 2.461 2.483
Network Commissioning
The recommendations below support successful network commissioning.

Always start up a gateway before turning on the sensors. If you do not, the sensor
will turn itself off within an hour of not finding the gateway and it will not try to
reconnect until the next day. A sensor will wake up to look for a network to join
every 24 hours after it has searched for an hour and failed to connect.
Do not use the Network ID 1229 unless it is a commissioning
network. The sensor will attempt to join for one hour then shut
down completely if the network is not found. It will remain off
until manually re-activated by the push button. This shutdown is
a safeguard in case a sensor from the factory is left on; it will not
consume battery power by searching for the network 1 hour
every day.
If there is commissioning network on site, make sure it is out of the signal range of
the production network.
Test the sensors within the 1-hop distance to the production gateway before
deployment to verify the network settings are correct.
Start up the sensors closest to the gateway first, that is the 1-hop sensors, and
then move out in sequence to the sensors farther away from the gateway. Start up
all 2-hop sensors, then all 3-hop sensors. While building the network, switch on
Global Advertising in the gateway (click Activate Global Advertising in the

Service Manual
Network Diagnostics
gateways Setup web page) and all field devices to shorten the time required for
new sensors to join the network.
The number of sensors joining simultaneously affects network formation time
because these sensors must compete for limited join links and downstream
bandwidth. So when too many sensors sync up at once they will contend for the
same shared access point links which can slow down the overall network formation
time. Start a small group of sensors to join at one time. As mentioned above, if it
takes more than one hour for a sensor to join the network, it will turn off and try
again 24 hours later.
Network Diagnostics
Key Considerations
Formation time Is the network formation time acceptable? The formation time
should be less than one hour because sensors that have not joined by then will
automatically turn off.
Reliability - Verify the reliability is close to 100%. This is the percentage of unique
packets received relative to the number generated. (See the example in Network
diagnostic details later in this chapter. Reliability is indicated in blue.)
All network statistics require at least 15 minutes after the last
mote (nodes are also known as motes) has joined to develop.
Stability The ratio of acknowledged packets to packets sent between two nodes. This
step involves looking at all the discovered paths in the network, and making sure that
every mote has enough good quality neighbors. The bare minimum is that every mote
should have at least three good neighbors. A good neighbor is a neighbor that this mote
can hear at greater than -75 dB RSSI with better than 50% path stability. (See the
example in Network diagnostic details later in this chapter. Stability is indicated in
orange.)
RSSI (Received Signal Strength Index) Indicates the power of the received signal for
each neighboring device. (See the example in Network diagnostic details later in this
chapter. RSSI is indicated in purple.)
Number of joins Verify in the network statistics file that the number of joins of each
sensor stays the same. An increasing number indicates connection reset, which means
dropping from the network or weak signal strength. (See the example in Network
diagnostic details later in this chapter. Number of Joins is indicated in red.)
Two parents Use the gateways web page topology view to identify at least two links
that are available for each sensor. These paths do not have to be in use currently, they
just have to be discovered and reported by the network.
Topology View
The traffic and stability data that display in the topology view represent a single
statistics cycle of 15 minutes. Therefore, the data display only after a statistics cycle of
15 minutes has been completed. Use the colors (a legend is provided below) to

Service Manual
Network Diagnostics
determine if all connected field devices have good quality connections and good quality
alternative paths.
Go to the gateways web page, Diagnostics > Wireless Communication > Topology
View.
Figure 37.
Path to the Topology View.
Another path to access the Topology View is through the

Engineering node. Use the Engineering node path to set up the
Topology View and manipulate the components on the image.
Press the Apply button to finalize the location of the devices.
In the following example, devices with green status icons (with a check mark) are linked
and available. Devices with red status icons and no connection paths have no network
connection and are unavailable.
Figure 38.
Example of the Topology View of a Network.
The color of the connection indicates the stability of the path. A black line indicates that
more time is needed to establish the statistics. Devices linked with dotted lines indicate

Service Manual
Network Diagnostics
the connection is unused and therefore communication can be switched to this

alternative link if the main connection fails. The legends provided below explain how the
stability and traffic of the connection are depicted in the topology view image.
Stability
Color Successfully received Color Successfully received
messages in % messages in %
0-10 50-60
10-20 60-70
20-30 70-80
30-40 80-90
40-50 90-100

Service Manual
Network Diagnostics
Network Diagnostic Details

The introduction of the gateways Diagnostics > Wireless Communication > Details
web page in the firmware version 02.00.02, revision 2.5, or later, is the preferred way
to view network diagnostics. It is easier to read than the Network Statistics Report
obtained through Device Manager and contains almost the same information.
Figure 39.
Path to the Details Web Page.
The diagnostic details are available only after a 15 minute cycle is complete in order to
collect enough data to calculate the statistics. The information represents the
communication status over the last 15 minutes. We recommend exporting the
information (using the Export button) in the CSV format for archiving.

Service Manual
Network Diagnostics
Figure 40.
Diagnostics Details Web Page.
In the following enlarged detail taken from the example above, the sensor East Building
Pump 123 was expanded to show two neighbors: the gateway and the routing node
CMWA_8800_000161. The RSSI and Stability of each neighbor is displayed.
Figure 41.
Sensor with Neighbors Expanded.

Service Manual
Network Diagnostics
The Network Statistics Report

To access the network statics report, select the gateway in the Device Manager
hierarchy. Go to the Gateway > Admin tab, and then click Get Network Statistics. The
path of the file is \CMWA 8800Log\CMWA 8800StatisticLog from the root of the drive
on which the software is installed.
Figure 42.
Gateway / Admin Tab Get Network Statistics.
The network statistics report documents the communication quality in terms of traffic,
retransmissions, stability, and received signal levels between all connected nodes in the
network. An example network statistics report follows. In the example, the average
queue occupancy (avQ) and maximum queue occupancy (maxQ) are highlighted in light
blue in the example. If average queue occupancy is higher than one, and the maximum
occupancy is higher than three, it may indicate a symptom of RF interference. Refer to
Chapter 8, RF Interference and Solutions.

Service Manual
Network Diagnostics
Figure 43.
An Example Network Statistics Report.
Note: Mote is another term for node.

A list that maps MAC (Media Access Control) addresses with Mote IDs is also included in
the report:
MAC MoteID Jn Nbrs WDev State
00-17-0D-00-00-18-1C-41 ap 1 1 0 [Gateway] Oper
00-1B-1E-1A-9A-00-00-99 2 1 7 [8 ,0 ] Oper
00-1B-1E-1A-9A-00-00-96 4 1 3 [9 ,0 ] Oper
00-1B-1E-1A-9A-00-00-93 5 0 0 [4 ,0 ] Idle
00-1B-1E-1A-9A-00-00-91 6 1 2 [2 ,0 ] Oper
00-1B-1E-1A-9A-00-00-9F 7 1 2 [7 ,0 ] Oper
00-1B-1E-1A-9A-00-00-87 8 1 2 [3 ,0 ] Oper
00-1B-1E-1A-9A-00-00-8C 11 1 2 [6 ,0 ] Oper
00-1B-1E-1A-9A-00-00-9A 15 0 0 [0 ,0 ] Idle
00-1B-1E-1A-9A-00-00-90 27 1 2 [5 ,0 ] Oper

Service Manual
Network Diagnostics
The table below describes each column header that displays in the Network Statistics
Report.
Column Description
header
ABPower The average RSSI values for transmissions from mote A to mote B.
ABRx Number of packets mote B received from mote A.
ABTx(Fail) Number of packets transmitted by mote A to mote B, and the number
of packets for which mote A failed to receive acknowledgement.
Packets may fail for a number of reasons, including RF interference or
bit errors.
avQ Average number of packets in the motes queue waiting to be
transmitted.
BAPower The average RSSI values for transmissions from mote B to mote A.
BARx Number of packets mote A received from mote B.
BATx(Fail) Number of packets transmitted by mote B to mote A, and the number
of packets for which mote B failed to receive acknowledgement.
(Not currently implemented. Acknowledgements are not sent for
downstream data transmission.)
Chg Charge consumption, in millicoulombs.
Hop Average number of hops (number of jumps from mote to mote before
reaching the gateway) for this motes data packets to arrive at
manager.
Id Mote ID number.
Jn Number of times the mote joined since the gateways network manager
was last reset.
Late Data latency. The average time (in seconds) for a data packet to travel
from the mote to the gateway manager. The gateway manager
calculates data latency for each packet by subtracting the time the
packet was received at the gateway manager from the packet time
stamp, indicating when the packet was generated by the mote. The
gateway manager averages the data latency of all packets from a mote
to provide the values for network statistics.
Me MAC-layer MIC (message integrity check) errors.
MoteA Describes the path from mote A to mote B.
MoteB
mxQ Maximum number of packets in the motes queue waiting to be
transmitted.
Ne Network-layer MIC (message integrity check) errors.
PkDrp Number of data packets dropped by the mote. Packets may be
dropped because the motes buffer was full and the mote was unable
to generate a packet.
PkDup Number of duplicate packets received. A duplicate packet is sent if no
acknowledgement is received for any hop in the packets journey to
manager. A high number of duplicate packets indicates problems with
the mote-to-mote communication.
PkFwd Number of data packets forwarded by the mote to a neighbor.

Service Manual
Network Diagnostics
Column Description
header
PkLst Number of data packets that manager expected, but did not receive.
PkRx Total number of packets received by network motes.
PkTerm Number of data packets terminated by the mote.
PkTx(Fail) Total number of packets transmitted by network motes, and total
number of packets for which no acknowledgement was received.
Reliability Mote or network reliability
The network statistics report shows an aggregated number for reliability, stability and
latency. In addition, detailed communication information is listed for each sensor,
including relative received signal strength values between communication nodes
(ABPower / BAPower) measured in dBm.
The wireless networks stability is a result of received signal level and background noise
level (for example, from a WLAN). In addition, traffic by people and/or vehicles may
cause temporary loss of stability.
As a general rule, if the stability percentage for a node is above 95%, the operational
margin is OK. If it is lower, you should consider installing additional router nodes to
increase signal to noise ratio, or investigate ways to reduce background noise by moving
WLAN routers or changing WLAN channel usage.

Service Manual
Troubleshooting Network Issues
Issue: No Sensors Join

If no sensors join the network, check the following items:
You did not wait long enough; joining is still in progress.
The sensors are not activated (powered on).
The network ID and/or Join Key of the gateway security manager do not match the
security credentials of the sensors.
The gateway antenna may have an issue, such as: the antenna is blocked, the
antenna or antenna cable is damaged, or the cable length has produced power loss
if a remote antenna is used.
The sensors are all placed too far away (beyond 50 m line of sight) from the
gateway or access point.
P+F gateways do not have an Access Control List (ACL) but other gateways may
have one. If the gateway has an ACL, make sure the sensors are on the list.
Issue: Some Sensors Do Not Join

If some sensors join the network and others do not, you have at least established that
the network manager and access point are functional. The reasons that some sensors
do not join may include:
Some sensors are placed too far away. If you are adding new sensors, make sure
that the sensors that were previously peripheral are now enabled as routing
devices.
Some of the sensors do not have the correct security credentials to join this
network manager (Network ID, Join Key).
The maximum number of sensors on the gateway network manager (250) has
been reached.
If the gateway has an ACL, make sure the sensors are on the list.
The join process has exceeded one hour and sensors that did not join in time have
turned off.
Issue: One Sensor Does Not Join

If the number of sensors that fail to join is small relative to network size (such as 1 or 2
in 100), then the likely reasons include:
The sensor is not activated.
The sensor has an RF problem (it may be broken or the antenna is not attached).
The sensor has the wrong security credentials.
The sensor is placed too far away from the rest of the network.
The maximum number of sensors on the network manager has been reached.

Service Manual
If the gateway has an ACL, make sure the sensor is on the list.
The join process has exceeded one hour and sensors that did not join in time have
turned off.
Issue: One Sensor Rejoins Over and Over

This can be observed in the Number of Joins column in the Details web page. Sensors
should stay connected to the network indefinitely. Possible reasons for a single sensor
to join and drop off the network and join again include:
A power supply problem on the sensor is resetting it.
The RF connectivity to its neighbors is marginal (reception is poor).
The RF connectivity to neighbors is highly transient and unstable (reception is good
but cuts out). The sensor is in a location where RF connectivity can be severed and
then re-established (such as in an enclosure or behind a large obstacle).
Issue: The Gateway Becomes Non-responsive

On very rare occasions, a bottleneck may occur with commands sent to the gateway,
and the gateway may become non-responsive. When this occurs, you can flush (clear)
the gateways command queue to clear the bottleneck.
How to flush the gateways command queue:
In the hierarchy, select the gateway whose command queue you wish to clear.
Right click the gateways hierarchy item, and select Flush from the pop-up menu.
Figure 44.
Flush the Gateways Command Queue.

Service Manual
8
RF Interference and Solutions
RF Interference
Sources
RF interference sources include:
WiFi
Bluetooth
Multiple 802.15.4 networks
Microwave oven, cordless phones, miscellaneous, etc.
Symptoms
RF interference symptoms include:
Reliability is less than 99.9%.
The stability of a large number of paths is less than 60%, even when RSSI is better
than -70 dBm.
Sensors are within operating range (50 m) but have poor path stability, less than
50%.
Upstream latency is greater than 30 seconds.
Average queue occupancy is higher than one, and the maximum occupancy is
higher than three. The average queue and maximum queue can be found in the
network statistics report highlighted in light blue.
Solutions to RF Interference
Potential solutions to RF interference include:

Identify the source of the interference and remove it.
Increase the number of neighbors.
Channel blacklisting (see details below).
Channel Blacklisting
You can use frequency planning and blacklist those channels on the gateway known to
overlap with heavily used WiFi channels. Or the reverse, study the WIFi channels in use
with a laptop and a program like MetaGeek Wi-spy ISMB spectrum analyzer and
software, and then determine the available frequency space and the channels
corresponding within WirelessHART. If there are other wireless networks in the area

Service Manual
RF Interference and Solutions
Solutions to RF Interference
where the WirelessHART network is located, you can make sure that those channels are
not used by multiple networks simultaneously. The example below shows the usage
over channels 1 to 4.
Figure 45.
802.11.g and Background Noise.
Use the Channel Blacklist feature on the gateways Wireless Communication > Setup
web page to disable selected channels. Blacklisting can improve communication
stability and reduce power wasted due to retry attempts on fully blocked channels.
Select the After Restart check box for the channel(s) to blacklist. Then, click Send to
Device to send the new channel list to the gateway.
Figure 46.
Channel Blacklist Feature.

Service Manual
9
System Maintenance
In this chapter, the following system maintenance procedures in Device Manager are
presented:
Adding a new sensor into service
Editing a sensors name
Removing a sensor from service
Replacing an existing sensor in service
Relocating an existing sensor in service
Upgrading sensor firmware
Also described in this chapter are the resources available for device status information
and system debugging:
Device status indicators
System debugging logs
Adding a New Sensor into Service
Commissioning network If the sensor is joining a commissioning network, simply

switch on the sensor and it should be ready to join the network using the default
settings.
Production network with Network ID 101 or 102 If the production network uses
Network ID 101 or 102 and the default Join Key, simply switch on the sensor and set
the Network ID by using the sensors push button and the LED flash sequence to
configure the sensors to join the production network. (Count seven blinks for Network
ID 101; eight blinks for 102.)
Production network with customized Network ID If the production network uses a
customized Network ID and Join Key, you need a commissioning network to configure
the new sensors network settings before it can be put into service in the production
network. Follow the steps below.
The alternative is to use SKFs pre-configuration service.

Service Manual
System Maintenance
To add a sensor to a production network with a customized Network ID:

Go to the Plant / Batch Service
Management tab and Stop the batch
service. Note: The Find sensors
command is unavailable when the
batch service is running.
Turn on the new sensor within the

range of the commissioning network.
Open the Operating Modes web page.
A yellow icon with a small wrench will
display while the new sensor is joining
the network.
Wait until the sensor joins the

network. The sensors yellow icon in
the Com. Status column will turn
green when it joins.
Right-click the gateway node and issue

the Find sensors command to import
the new sensor into the Device
Manager hierarchy.
Wait until the sensor has completed
the import process (that is, the
sensors status indicator turns green).
In the Device Manager Gateway >

Admin tab, enter the production
Network ID in the Network Id field.
Click Exchange Network Id to send

the production Network ID to the
gateway network manager and its
connected sensors.

Service Manual
System Maintenance
Next, enter the production network

join key in the Join Key field.
Click Exchange Join Key to send the
production join key to the gateway
network manager and its connected
sensors.
Wait a few minutes for the gateway
network manager to propagate the
production network settings to the
new sensor.
Go to the gateways Additional

Functions > Reset web page. Click
Reform Network to tell the sensor
and gateway to start using the
production network ID and join key.
The Com. Status indicators for the
sensors will immediately turn red in
the Operating Modes page.
Note: If you click the Reform network
button in Device Manager, the
gateway does not know the sensors
were disconnected and the Com.
Status indicators will remain green.
Verify the sensor has joined the
network by viewing the gateways web
page.
Turn off the sensor and move it out to
Tip: Activate the sensor next to the
production gateway to verify that is
able to join the network before
mounting the sensor to the machine.
Be sure to turn on the batch service
When the new sensor has joined the production network, its POINTs should be exported
automatically to Analyst if the XML export was enabled.

Service Manual
System Maintenance
Editing a Sensors Name
Editing a Sensors Name
To edit a sensors name, modify the Long Tag in the Sensor > Device tab and the name
of the corresponding machine in Analyst will be updated accordingly.
Figure 47.
The Long Tag Identifier.
Removing a Sensor from Service
After switching off a sensor, the gateway will determine it has lost connection with the
sensor in approximately 15 minutes. You can force the sensor icon in the Device
Manager hierarchy to turn red by right-clicking on the sensor to be removed and
executing an Update Device Information command. The status of the corresponding
machine in Analyst will switch to disabled once the status has been exported by Device
Manager.
Figure 48.
Update Device Information Command.

Service Manual
System Maintenance
Replacing an Existing Sensor in Service
You may replace an existing sensor with a new sensor or a sensor that is already active
in the system. In either case, the sensor would first be commissioned in a
commissioning gateway, if one is available. Procedures are provided below to show
how to:
Replace a sensor with a new sensor that has the factory default network ID and join
key with a commissioning network available.
Replace a sensor with a sensor that is active in the production system with a
commissioning network available.
Replace a sensor when a commissioning network is not available.
Never give a sensor the same Long Tag name as an existing tag under the same
gateway. The Long Tag name is a unique identifier, and Device Manager cannot handle
duplicate Long Tag Names (unless replacing an old sensor with a new one, in which
case you should make sure to switch the old sensor off before switching the new sensor
on).
Commissioning Network Available Sensor with Default Security

Settings
This procedure is the same as adding a new sensor to a production network, except in
this case the name of the new sensor must be changed to match the long tag of the
sensor to be replaced. Make sure the commissioning gateway's coverage area and the
wireless sensors coverage area are both outside the production gateway and its
wireless sensors' coverage area.

Switch off the sensor to be replaced in

In the system hierarchy, select the
sensor to be replaced. Force the
sensors status indicator to turn red by
right-clicking the sensor and executing
an Update Device Information
command from the menu. After the
sensors status indicator has turned
red in Device Manager, the
corresponding machine should be
disabled in Analyst.

Service Manual
System Maintenance
Locate the replacement sensor within

the range of a commissioning gateway
that is set up with factory default
network ID and join key.
Switch on the replacement sensor to
join the commissioning network.
Open the Operating Modes web page.
A yellow icon with a small wrench will
display while the new sensor is joining
the network.
Wait until the sensor joins the
network. The sensors yellow icon in
the Com. Status column will turn
green when it joins.

the replacement sensor into the
Device Manager hierarchy.
Select the replacement sensor and go

to the Sensor / Device tab.
Modify the Tag of the new sensor to
match exactly the sensor that it is
replacing.
Update the Machine speed, as
needed, and then click Save. Do NOT change the values
Note: Do not change the Descriptor,
in these fields!
the Final Assembly Number or the
Date.
From the Gateway / Admin tab of the

commissioning gateway in Device
Manager, enter the Network ID and
Join Key of the target production
gateway.
Click the corresponding Exchange
Network Id and Exchange Join Key
buttons to update the gateway and its
connected sensors with the production
gateway's network ID and join key.
Wait a few minutes. (You do not get
any indicators from the gateway.)

Service Manual
System Maintenance

The Com. Status indicators for the
sensors will immediately turn red in
the Operating Modes page.
Note: If you click the Reform network
button in Device Manager, the
gateway does not know the sensors
were disconnected and the Com.
Status indicators will remain green.
network by viewing the gateways web
page.
Turn off the sensor and and properly
mount it in the production network.
Tip: Activate the sensor next to the
production gateway to verify that is
able to join the network before
mounting the sensor to the machine.
Once the sensor has joined the
gateway, right-click the gateway node
and issue the Find sensors command
to turn the status of the replaced
sensors node to green in the
hierarchy. The corresponding machine
in Analyst will be re-enabled.
Perform a Collect Waveforms
command on the replacement sensor,
and then verify the measurements are
correctly collected at the
corresponding sensor in Analyst.


Service Manual
System Maintenance
Commissioning Network Available - Sensor with Production

Security Settings
In this case, you must update the commissioning gateway with the production network
security settings. Make sure the commissioning gateway's coverage area and the
wireless sensors coverage area are both outside the production gateway and its
wireless sensors' coverage area.


From the gateways Wireless
Communication > Setup web page,
configure the commissioning gateway
with the production networks Network
ID and Join Key. Click the Write Join
Information button.


Service Manual
System Maintenance

join the commissioning network, which
now has the production network
security settings.
Locate the replacement sensor within
the range of the commissioning
gateway.
network by viewing the gateway's
Operating Modes web page to see
when the Com. Status indicator turns
to green.

Modify the Tag of the new sensor to
match exactly the sensor that it is
replacing.
in these fields!
Date.
Turn off the sensor and properly

mount it in the production
environment.
Turn on the sensor and let it join the
production network.
Tip: You may want to activate the
sensor next to the production gateway
before mounting the sensor to the
machine. In this way, you can verify
that is able to join the production
network.
Once the sensor has joined the
gateway, right-click the gateway node
and issue the Find sensors command
to turn the status of the replaced
sensors node to green in the
hierarchy. The corresponding machine
in Analyst will be re-enabled.

Service Manual
System Maintenance



Service Manual
System Maintenance
No Commissioning Network
IMPORTANT: A customized sensor must be ordered with the pre-configuration

service to join the network.


Disable the XML export on the the
Plant > Export tab by unchecking
the Enable check box.

join the network. After the
replacement sensor has joined the
network, it will show up in the device
list on the gateways Operating Modes
web page.

Service Manual
System Maintenance


Modify the Tag of the replacement
sensor to match exactly the sensor
that it is replacing.
in these fields!
Date.
Switch off the replacement sensor.

Force the sensors status indicator to
turn red by right-clicking the sensor to
be replaced and executing an Update
Device Information command from
the menu.
After the status of the new sensor has
turned red, delete it from Device
Manager by right-clicking the sensor
and selecting the Delete Sensor
command.
Close the Device Manager application

and then re-launch it.
Activate the replacement sensor with
the modified Long Tag and verify that
it has re-connected to the gateway.
Enable the XML Export in the Plant >

Export tab by selecting the Enable
check box.

Service Manual
System Maintenance
Right-click on the gateway in Device

Manager and perform a Find sensors
command again. The replacement
sensors status indicator will now
return to green in the Device Manager.
In Analyst, the status of the replaced
sensor should return to enable
(green).


Service Manual
System Maintenance
Relocating an Existing Sensor in Service
When a working sensor is moved from one motor to a different motor, the
measurements from each motor should be kept separately in different machines in
Analyst.
Commissioning Network Available

The sensor can be moved to a commissioning network to be renamed for the new
location and then rejoin the production network. This allows Device Manager to create
a new machine for the same sensor in Analyst while keeping the old machine in the
disabled state. Just by changing the Long Tag of the sensor, we can now use the same
sensor to monitor a different motor and keep the measurements from each motor
under separate machines in Analyst.
No Commissioning Network
The Technical Service Group (TSG) will use the Long Tag Editor utility instead to replace
the commissioning network when relocating a sensor to monitor a different motor as
described above. The Long Tag Editor utility enables you to change a sensors Long Tag
on the fly while the sensor is still connecting to the production network.

Service Manual
System Maintenance
Enter the Gateway IP Address, Gateway

Port and Poll Address.
Click Connect to connect to the gateway.
If successfully connected, the MAC
addresses of all connected sensors will
display in the list box on the left.
(Note: The Connect button will toggle to
Disconnect. If more sensors are joining
the network, you can disconnect and then
re-connect to the gateway at any time to
see a refreshed list.)
If the sensor you want to relocate appears

in a short list, select it.
OR
You can quickly search for the sensor in a
long list by entering the last numbers (the
device ID) of the MAC address, and then
clicking Search.
The selected sensors Long Tag appears in
the box labeled: Edit the Long Tag of the
Selected Sensor.
Make the edits you want.
Click Modify to apply the changes.
A new sensor will be created in Device

Manager after you execute a Find
Sensors command.
A new machine with that sensors new
Long Tag will be created in Analyst. The
machine with the original Long Tag will be
disabled.
All measurements from the relocated
sensor will now go to the POINTs in the
new machine in Analyst.
This process can be reversed. If the sensors Long Tag is changed back to the original
Long Tag with the utility, and then a Find Sensors command is executed, the original
machine will be re-enabled while the new machine is disabled. All measurements from
the sensor will again be saved in the POINTs of the previous machine.

Service Manual
System Maintenance
Upgrading Sensor Firmware
You can perform either a global sensor firmware upgrade on all of the networks
sensors, or you may upgrade firmware for an individual sensor. Each process is
described below.
WARNING! Disable the batch service before upgrading sensor firmware.
Global Firmware Upgrade
In the hierarchy, select the network

whose firmware you wish to
upgrade.
(You do not need to select the
Commissioning Network. This
image is an example only.)
Go to the Network > Sensor
Firmware tab.
Click Read HEX-file to upload the

firmware .HEX file.
Verify the correct firmware version
in the New firmware > Software
Revision area.
Click Upgrade Sensors. The

firmware downloads progress
displays on two progress bars, the
individual sensors progress and
the overall global download
progress.
Note: If, for some reason, you are
downgrading to an older version,
you must enable the Force
upgrade check box. Contact TSG
for the compatibility requirements
between firmware and software.

Service Manual
System Maintenance
When the Overall progress bar

indicates 100% complete, the
global firmware update is
complete.
During global firmware upgrade, the new firmware is downloaded sequentially only to
those sensors that have an older firmware version. However, if Force upgrade is
enabled in order to download an older version, firmware will be downloaded to all
connected sensors irrespective of their current firmware version.
This operation takes approximately 20 minutes to upgrade the firmware in each sensor,
if it is in direct contact with the gateway. This time is doubled with each hop/router
between sensor and gateway. If at all possible, it is desirable to bring all sensors to
within one hop of the gateway to perform the upgrade to reduce the time required.
It is recommended that you let Device Manager run until it is completed. If, for any
reason, a sensor temporarily is not responding during upgrade, Device Manager skips to
the next sensor in its list. After completing the list, a new attempt to update the
firmware on skipped sensors is performed. For large systems, it is advisable to begin
the procedure before leaving at the end of the day and then inspect the results the
following day.
Individual Sensor Firmware Upgrade
In the hierarchy, select the sensor

whose firmware you wish to
upgrade.
Go to the Sensor > Sensor
Firmware tab.
Click Read HEX-file to upload the

firmware .HEX file.
Verify the correct firmware version
in the New firmware > Software
Revision area.
Click Upgrade Sensors.

Note: If, for some reason, you are
downgrading to an older version,
you must enable the Force
upgrade check box.

Service Manual
System Maintenance
The Sensor Status area shows the

current upgrade status.
The progress bar indicates the
downloads progress.
Sensor Status Firmware download

OK means the download was
successful. The sensor
automatically restarts (it will drop
from the network and rejoin).
Sensor Status Firmware download
CRC error indicates the
When the firmware upgrade is successful, all Sensor Status
downloaded firmware is corrupted;
options are cleared.
the previous firmware version is
retained.
After a 15 minute delay, the Device
Manager software checks if the
sensor has joined the network
again, reads the new firmware
version from the sensor, and flags
any errors.
If unsuccessful, the Sensor Status
is updated to Firmware update
failed.

Service Manual
System Maintenance
Device Status Indicators
The Sensor > Status tab displays the implemented status bits in the Device Status
byte, Extended Device Status byte, and the Standardized Status 0 byte and
Standardized Status 3 byte, as specified in the HART protocol.
Figure 49.
Sensor > Status Tab, Status Indicators.
For troubleshooting purposes, the status flags indicate the sensors status as described
in the following tables.
Device Status
Specified in the HART Command Summary Specification
Bit No HART Definition Device Manager Implementation
0 Primary Variable Out of Limits Not used
1 Non-Primary Variable Out of Limits Not used
2 Loop Current Saturated Not used
3 Loop Current Fixed Not used
4 More Status Available Set upon any change of status variables,
cleared when new status is read
5 Cold Start Set upon a device reset
6 Configuration Changed Set upon a configuration change, cleared when
new configuration is stored to flash
7 Device Malfunction Set if memory error detected at restart

Service Manual
System Maintenance
Extended Device Status

Specified in the HART Common Tables
0 Maintenance required Not used
1 Device Variable Alert Not used
2 Critical Power Failure Set if battery voltage is measured below 3.3 V
3 Undefined Reserved
Additional Device Status (device specific information)

Device Specific Status byte 0: Not used
Device Specific Status byte 5: Bits used as detailed below:
bit 0 Not used
bit 1 - Firmware download in progress (on the Sensor / Sensor Firmware tab)
bit 2 - Firmware downloaded OK (on the Sensor / Sensor Firmware tab)
bit 3 - Firmware download bad CRC (on the Sensor / Sensor Firmware tab)
bit 4 - Firmware update failed (on the Sensor / Sensor Firmware tab)
bit 5 Not used
bit 6 Not used
Standardized Status 0
Specified in the HART Common Tables
0 Simulation Active Not used
1 Non Volatile Memory Defect Set if flashing of new firmware version fails
2 Volatile Memory Defect Not used
Watchdog Reset Executed Set if watchdog reset is executed, reset if Get
3
Historic Info is executed
4 Voltage Conditions Out of Range Not used
5 Environmental Conditions Out of Range Not used
6 Electronic Defect Set if flashing of new firmware version fails

Service Manual
System Maintenance
Standardized Status 3
Specified in the HART Common Tables to support WirelessHART
Capacity Denied Set if device is unable to acquire communication
bandwidth required to support the burst messaging
0
specified or network manager reduces the bandwidth
allocated to the device.
1 Duplicate Master Detected Not used
Bandwidth allocation pending The device has asked for bandwidth from the Network
2
Manager and is awaiting Network manager response.
Block Transfer Pending The device has a data set (waveform) awaiting transfer
3 to the host or gateway. The Gateway should open the
block transfer port and transfer the data.
4-7 Undefined Reserved
Sensor Battery Status

The lower section of the Sensor > Status tab contains the Battery Management area.
Figure 50.
Sensor > Status Tab, Battery Management.
The green battery charge bar displays the estimated remaining battery capacity in
percentage and mAh. The sensors firmware estimates the remaining battery capacity
and life in days based on the type and number of activities that the sensor has executed.
Battery life estimates are based on operation at room temperature (25 C, 77 F).
A healthy battery voltage ranges from 3.5 to 3.6 V. When a loaded battery voltage
lower than 3.3 V is measured, a Critical power failure message is reported on the
Status tabs Extended Device Status Bit 2. The battery will need to be replaced within
weeks or even days.
Battery voltage is measured. Battery life and battery level are
calculated.
Click Get historic info to see the history of the sensors activities up to the last five
battery replacements.

Service Manual
System Maintenance
System Debugging Logs
Figure 51.
Historic Power Info Records Dialog.
The displayed dates indicate the first dates the sensor joined a network after a battery
replacement. The # fields indicate the number of occurrences for each event. The #
Operation Time field refers to the number of operation days (sensor activated) since
the most recent battery replacement.
System Debugging Logs
Device Manager stores records of its execution and communication events in log files on
the host computers hard drive. These log files are useful for debugging purposes.
WARNING! Both log files continue to grow larger the longer you use Device
Manager and/or the batch service. Therefore it is necessary to regularly delete the files
on a periodic basis, or else you will compromise hard drive space.
Execution Log
The execution log stores Device Manager and batch service activity as:
\CMWA 8800Log\CMWA 8800Log.txt on the hard drive on which Device Manager is
installed. By default, only error messages are logged for the execution events.
However, the execution logs content is user determined by enabling specific commands
in the Settings.config file.
Communication Log
A communication log that stores commands sent from Device Manager to the gateway
and the gateways response back to Device Manager is created for each gateway for
each day. The communication log is stored as:
\CMWA 8800Log\GatewayIPAddress\CMWA 8800CommLogYYYYMMDD.txt.
It is recommended that these historical files are deleted regularly unless they are
necessary for examining system problems.

Service Manual
10
FAQs
Frequently Asked Questions
Why cant I see the Use Cache check box in Device Manager?
(or another control in the Windows dialog at the bottom of a screen, such as the
progress bar during manual data collection)
The required minimum monitor resolution for Device Manager is 1600 x 900.
How many sensors can the network have?

SKF recommends a maximum of 50 sensors for each gateway for performance
reasons. Because the P+F gateways web page user interface slows considerably after
60 to 70 sensors have joined the network, SKF considers any installation of 50 sensors
or more to be a large system installation. Note: Adding gateways will decrease the
number of sensors per gateway and improve the user interface response and network
communication speed.
Can I replace the sensors battery?

No. If the battery life is low, contact CSG to return the sensor to SKF for replacing the
battery.
How long will the sensors battery last?

The battery should last for several years, but battery life cannot be precisely predicted
and will vary based on the following factors:
How often data is taken
Leaf node vs. full routing mode
External temperature and environmental conditions
P1 or P2 profile setting, when available
I get the message License Key Expired even though it is not expired.
Either the file has moved that is, the software was moved to a different computer - or
the software is running a different database.
Can I monitor mobile equipment, such as a crane or forklift, with a CMWA 8800 sensor?
No. The wirelessHART mesh network does not adapt quickly to changing conditions
and therefore does not effectively monitor mobile equipment. When the CMWA 8800 is

Service Manual
FAQs
Frequently Asked Questions
installed in a permanent location, it will achieve high reliability and quality of service
with the lowest power consumption. It is okay to relocate the sensor to monitor
different equipment.
How can I tell if the sensor is connected to the network?

Go to the P+F gateways web page, Operating Modes, and check the device
Communication Status (Com. Status). The icon should be green. Click the Refresh
button the page does not refresh automatically.
Or, you can click the Flash LED button in Device Manager. Select the sensor in the
hierarchy, and then go to the Device tab to access the command button.
How can I tell if the sensor is collecting data on schedule?

It is easiest to check in SKF @ptitude Analyst. You can check in Device Manager also, in
trending or waveform under each sensor.
How can I tell if the sensor is turned on?

Firmly press and then wait for the sensors green LED to flash.
On state: If it flashes once, the sensor is in the On state.
Off to On state: If it blinks once, pauses, then blinks in an accelerating manner,
pauses, and then blinks a short burst, the sensor was Off and is now On.

Service Manual
Appendix A
CMWA 8800 System Setup Checklist
The checklist example below provides a general guideline to follow when setting up the
CMWA 8800 sensors in a WirelessHART network or when troubleshooting issues in a
network. For brevity, in this checklist the SKF Wireless Machine Condition Sensor
System Setup Guide title is shortened to the Setup Guide. The Wireless Sensor Device
Manager User Manual title is shortened to the WSDM User Manual.
IMPORTANT: The checklist assumes your WirelessHART network already

exists and is operational.
Step Done Task and Reference

1. Set up the WirelessHART commissioning gateway. Setup Guide (P/N 32257600),
Chapter 1, System Setup
2. Activate the sensors and join the sensors to the commissioning gateway. Setup
Guide, Chapter 1, System Setup
3. Install Device Manager. WSDM User Manual, Chapter 2, Device Manager Software
Installation (P/N 32286200)
4. Build the wireless systems hierarchy in the Device Manager. WSDM User Manual,
Chapter 3, Sensor Setup and Commissioning (For a new Device Manager installation,
acquire the License Key.)
5. Change the gateways/sensors network ID and join key to join the production
network. Deactivate the sensors. WSDM User Manual, Chapter 3, Sensor Setup and
Commissioning
6. Mount the sensors in the plant and activate the sensors. Setup Guide, Chapter 2,
How to Mount the SKF Wireless Machine Condition Sensor
7. Verify communication quality. WSDM User Manual, Chapter 3, Sensor Setup and
Commissioning
8. If needed, add a P+F Adapter to help routing devices with poor connections. Setup
Guide, Chapter 5, Configuration of the P+F WHA-ADP WirelessHART Adapter
9. Set the Power Profile to Full Routing vs. Leaf Node for all sensors in the network.
Then, be sure to disable routing for all sensors not to be used as routers. (Do this in
the P+F gateways Operating Modes web page.) This Guide, Chapter 4, Wireless
Sensor Device Manager
10. Configure the sensors data collection schedule (bursting of measurement results to
the gateway and polling schedules for retrieving results to the Device Manager
database). WSDM User Manual, Chapter 3, Sensor Setup and Commissioning
11. Start the Device Manager batch service. WSDM User Manual, Chapter 3, Sensor
Setup and Commissioning
12. Set up the data export process to SKF @ptitude Analyst and verify it works. WSDM
User Manual, Chapter 5, Exporting Data to SKF @ptitude Analyst

Service Manual
Service Manual
calibration 40
Index generic HART command 41
use wireless/wired communication 39
A export node information 59
exporting measurement collection period 54
Access Control List (ACL) 78
active advertising 21 F
add a new sensor 83
Analyst database 11 FAN, Final Assembly Number 40
fast pipe 7, 8
B firmware upgrade 98, 99
firmware version 16
batch service 11 firmware, known issues 16
batch service, stop 45 flash LED 7
battery temperature 3 flush gateway command queue 79
blacklisting channels 81
block transfer 8 G
burst mode 8, 42
gateway command queue flush 79
C gateway firmware version 16
gateway installation torque 22
cache 8 gateways web page
change a sensor name 86 access 15
channel blacklisting 81 global advertising 21
commissioning gateway 18
H
D
hazardous area certification 3
data collection
Command 9 53 I
Command 93 47
setup 42 installation torque guidelines 22
Use Cache check box 46 installation, Device Manager 25, 26
waveform time estimate 54
data flow 11 J
database server 26
join network
database, attach 27
fail to join 78
Device Manager database 11
over and over 79
Device Manager, import sensors to database 35
propagate new settings 57
Device Manager, sensor icon color codes 36
device status 101
K
device status, extended 102
Diagnostics Details 72 known issue
DTS, date time stamp 48, 59 Device Manager, empty window 37
Device Manager, gateway connection status
E cycles 37
Device Manager, UAC not disabled 27
edit a sensor name 86
Device Manager, unhandled exception when
exchange join key 57
closing 37
exchange network ID 57
Device Manager, waveform upload slow 37
expert features 39
SKF Wireless Machine Condition Sensor Index - 1

Service Manual
Java applet needed to show gateways web port number 19, 33
page 16 power profile 9, 38
monitor resolution 11
P2 profile 16 R
time synch 17
radio signal strength 64
web page, manual refresh slow 16
relocate a sensor 96, 97
web page, refresh manually 16
Long Tag Editor 96
remove a sensor 86
L
replace a sensor 87, 90, 93
leaf node 8, 38 reset pipe 7
license key 12 reset sensor 7
link 8 routing 9, 38
log files 104 RSSI 69
communication log 104
execution log 104 S
Long Tag 4, 8
security manager 9
Long Tag Editor 96, 97
sensors
activate 5
M
battery 103
MAC address 4 battery historical records 103
manual commands 6 deactivate 5
manual data collection Extended Operations Menu 6
overall data 55 manual commands 6
waveform 56 number of joins 69
monitor resolution 11 removing 86
mote 69, 75 repair 5
replacing 87, 90, 93
N reset 7
service 5
neighbors 69
software commands 7
network
stability 69
add a new sensor 83
status indicators 101, 102
layers 9
settings.config file 13, 14
relocate a sensor 96
setup checklist 107
remove a sensor 86
slot 9
replace a sensor 87, 90, 93
storage temperature 3
network commissioning 68
superframe 9
network diagnostics 69
Network ID 101 or 102 17, 83
T
Network ID and Join Key 17
network manager 8 tag name 86, 87
network planning 63 topology view 69
network statistics report 74 trend data collection
burst update period 47
P vibration cyclic update 47
troubleshoot
P1 profile 8
Device Manager connection to gateway 33
P2 profile 9
Device Manager required ports 33
paths 69, 70
join network 78
Index - 2 SKF Wireless Machine Condition Sensor

Service Manual
U
UAC user access control
disable 26
Use Cache, data collection 46
W
warning, aggressive chemicals 4
warning, do not twist plastic top 3
warranty
do not twist plastic top 3
waveform collection schedule 48
waveform collection time estimate 54
web page access 15
WirelessHART terms 8
WLAN coexistence 66, 77
X
XML Import to Analyst 59
Wireless Sensor Device Manager Index - 3

User Manual

SKF Wireless Machine Condition Sensor CMWA 8800 User Manual

Uploaded by

Document Information

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

SKF Wireless Machine Condition Sensor CMWA 8800 User Manual

Uploaded by

Copyright:

Available Formats

Service manual

SKF Wireless Machine

User Manual Part No. 32315300-EN

Copyright 2015 by SKF USA Inc.

Patents: US 4,768,380 US 5,633,811 US 5,679,900 US 5,845,230 US 5,852,351

Product Support Contact Information

General Product Information

Technical Support Group

Tell us how were doing!

The P+F Gateways Web Page 15

SKF Wireless Machine Condition Sensor TOC-1

Changing the Network ID and Join Key 57

Troubleshooting XML Import to Analyst 59

Network Planning and Diagnostics 63

TOC-2 SKF Wireless Machine Condition Sensor

RF Interference and Solutions 81

CMWA 8800 System Setup Checklist 107

SKF Wireless Machine Condition Sensor TOC-3

Scope and Purpose

Document Part No.

SKF Wireless Machine Condition Sensor 1

The CMWA 8800 Sensor

Warnings and Cautions

SKF Wireless Machine Condition Sensor 3

WARNING! Contact with aggressive chemicals may cause severe damage to

CMWA 8800 Label

CMWA Long Tag

4 SKF Wireless Machine Condition Sensor

Issuing Commands to the Sensor

Activate the Sensor

Deactivate the Sensor

SKF Wireless Machine Condition Sensor 5

Press and To issue this command and elicit this LED

6 SKF Wireless Machine Condition Sensor

SKF Wireless Machine Condition Sensor 7

8 SKF Wireless Machine Condition Sensor

The WirelessHART Network Joining Process

SKF Wireless Machine Condition Sensor 9

There are 250 slots within one superframe.

10 SKF Wireless Machine Condition Sensor

The Wireless Sensor Device Manager

WARNING! The minimum monitor resolution for Device Manager is 1600 x

Two additional data flows are possible:

SKF Wireless Machine Condition Sensor 11

The Device Manager License Key

After the first plant is created, go

The License Management

Enter the temporary license key

12 SKF Wireless Machine Condition Sensor

Copy the license key from the

Device Manager Configuration Parameters

Information Default Setting

SKF Wireless Machine Condition Sensor 13

Information Default Setting

14 SKF Wireless Machine Condition Sensor

Accessing the Web Page

SKF Wireless Machine Condition Sensor 15

Known Issue Solution

Verifying the P+F Gateways Firmware Version

Known Issues with the Firmware

Known Issue Solution

16 SKF Wireless Machine Condition Sensor

Known Issue Solution

Network ID and Join Key Parameters