Anda di halaman 1dari 126

User manual

UM EN RAD ISM 900 EN BD

900 MHz Trusted Wireless Ethernet


radio with MOTR-9

User manual
900 MHz Trusted Wireless Ethernet radio with MOTR-9

2015-10-26

Designation:

UM EN RAD ISM 900 EN BD

Revision:

This user manual is valid for:


Designation

Version

Order No.

RAD-ISM-900-EN-BD

2900016

RAD-ISM-900-EN-BD-BUS

2900017

RAD-ISM-900-EN-BD/B

2901205

2476_en_K

PHOENIX CONTACT

Please observe the following notes


User group of this manual
The use of products described in this manual is oriented exclusively to:
Qualified electricians or persons instructed by them, who are familiar with applicable
standards and other regulations regarding electrical engineering and, in particular, the
relevant safety concepts.
Qualified application programmers and software engineers, who are familiar with the
safety concepts of automation technology and applicable standards.
Explanation of symbols used and signal words
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety measures that follow this symbol to avoid possible injury or death.
There are three different categories of personal injury that are indicated with a
signal word.
DANGER

This indicates a hazardous situation which, if not avoided, will result in death or serious injury.

WARNING

This indicates a hazardous situation which, if not avoided, could


result in death or serious injury.

CAUTION

This indicates a hazardous situation which, if not avoided, could


result in minor or moderate injury.

This symbol together with the signal word NOTE and the accompanying text
alert the reader to a situation which may cause damage or malfunction to the
device, hardware/software, or surrounding property.
This symbol and the accompanying text provide the reader with additional information or refer to detailed sources of information.
How to contact us
Internet

Up-to-date information on Phoenix Contact products and our Terms and Conditions can be
found on the Internet at:
www.phoenixcontact.com
Make sure you always use the latest documentation.
It can be downloaded at:
www.phoenixcontact.net/catalog

Subsidiaries

If there are any problems that cannot be solved using the documentation, please contact
your Phoenix Contact subsidiary.
Subsidiary contact information is available at www.phoenixcontact.com.

Published by

PHOENIX CONTACT GmbH & Co. KG


Flachsmarktstrae 8
32825 Blomberg
GERMANY
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:
tecdoc@phoenixcontact.com

PHOENIX CONTACT

Please observe the following notes


General terms and conditions of use for technical documentation
Phoenix Contact reserves the right to alter, correct, and/or improve the technical documentation and the products described in the technical documentation at its own discretion and
without giving prior notice, insofar as this is reasonable for the user. The same applies to any
technical changes that serve the purpose of technical progress.
The receipt of technical documentation (in particular user documentation) does not constitute any further duty on the part of Phoenix Contact to furnish information on modifications
to products and/or technical documentation. You are responsible to verify the suitability and
intended use of the products in your specific application, in particular with regard to observing the applicable standards and regulations. All information made available in the technical
data is supplied without any accompanying guarantee, whether expressly mentioned, implied or tacitly assumed.
In general, the provisions of the current standard Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.
This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document is prohibited.
Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.
Other product identifications may be afforded legal protection, even where they may not be
indicated as such.

PHOENIX CONTACT

Table of contents
1

Overview..................................................................................................................................1-3
1.1

Wireless modules ............................................................................................... 1-3


1.1.1
Wireless module types ........................................................................ 1-3

1.2

Trusted Wireless technology .............................................................................. 1-4

1.3

Applications........................................................................................................ 1-5
1.3.1
Ethernet connectivity ........................................................................... 1-5
1.3.2
Device server ...................................................................................... 1-5
1.3.3
Modbus gateway ................................................................................. 1-6
1.3.4
Wireless remote I/O via Modbus ......................................................... 1-6

1.4

Network topology................................................................................................ 1-6

System planning ......................................................................................................................2-3


2.1

Accessing the site .............................................................................................. 2-3

2.2

Path quality analysis ........................................................................................... 2-3

2.3

Signal strength.................................................................................................... 2-3

2.4

Antennas and cabling ......................................................................................... 2-4


2.4.1
Coaxial cable considerations .............................................................. 2-5
2.4.2
Antenna mounting considerations ....................................................... 2-5
2.4.3
Weatherizing connections ................................................................... 2-6
2.4.4
Maintaining system performance ........................................................ 2-6

Installation ...............................................................................................................................3-3
3.1

Mounting ............................................................................................................ 3-3

3.2

Making connections and powering up ................................................................ 3-6


3.2.1
Power connections ............................................................................. 3-6
3.2.2
Ethernet connections .......................................................................... 3-8
3.2.3
Serial port connections ....................................................................... 3-8

3.3

Antenna connections........................................................................................ 3-11

Programming the wireless module...........................................................................................4-3

2476_en_K

4.1

Configuring a PC to communicate with the wireless device ................................ 4-3

4.2

Logging into the wireless module ....................................................................... 4-4

4.3

Viewing device information................................................................................. 4-5

4.4

Basic configuration ............................................................................................ 4-6

PHOENIX CONTACT

RAD-ISM-900-EN-BD

ii

4.5

Configuration ..................................................................................................... 4-7


4.5.1
General configuration .......................................................................... 4-8
4.5.2
LAN settings ....................................................................................... 4-9
4.5.3
Configuring the Network Filter ........................................................... 4-11
4.5.4
Radio configuration ........................................................................... 4-13
4.5.5
I/O Ports ............................................................................................ 4-17
4.5.6
Device information ............................................................................ 4-21
4.5.7
Passwords ........................................................................................ 4-23
4.5.8
Store and retrieve settings ................................................................ 4-24

4.6

Performance..................................................................................................... 4-26

4.7

Maintenance..................................................................................................... 4-28
4.7.1
Software updates .............................................................................. 4-29
4.7.2
Utilities .............................................................................................. 4-29
4.7.3
Reboot .............................................................................................. 4-30
4.7.4
Radio test .......................................................................................... 4-30

4.8

Monitoring/reports ............................................................................................ 4-31


4.8.1
Web log ............................................................................................. 4-31
4.8.2
Radio status ...................................................................................... 4-32
4.8.3
Bridging status .................................................................................. 4-33

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)......................................5-3

PHOENIX CONTACT

5.1

Wireless I/O communications ............................................................................. 5-3


5.1.1
Modbus I/O overview .......................................................................... 5-3
5.1.2
System overview ................................................................................. 5-3
5.1.3
I/O system configuration overview ...................................................... 5-4
5.1.4
Configuring wireless modules connected to I/O .................................. 5-5
5.1.5
Configuring wireless modules connected to the PLC /Modbus master 5-7

5.2

I/O module descriptions...................................................................................... 5-8


5.2.1
Connecting and configuring the I/O modules ...................................... 5-9

5.3

Addressing the remote I/O.................................................................................. 5-9

5.4

Rotary switches ................................................................................................ 5-16

5.5

Register scaling ................................................................................................ 5-16


5.5.1
Digital channels ................................................................................ 5-16
5.5.2
Analog channel scaling ..................................................................... 5-17
5.5.3
Pulse input channels ......................................................................... 5-17
5.5.4
Pulse output channels ....................................................................... 5-17

5.6

Wiring and fail condition DIP switches for the I/O modules ............................... 5-19
5.6.1
Analog input module ......................................................................... 5-19
5.6.2
Digital input module .......................................................................... 5-20
5.6.3
Analog output module ....................................................................... 5-21
5.6.4
Digital output module ........................................................................ 5-22
5.6.5
Combination input/output module ..................................................... 5-23
5.6.6
Digital pulse input module ................................................................. 5-24
5.6.7
Digital pulse output module ............................................................... 5-27

2476_en_K

Table of contents
5.7

Accessing the XML file ..................................................................................... 5-29

Troubleshooting.......................................................................................................................6-3
6.1

LED indicators .................................................................................................... 6-4

6.2

RSSI (Received Signal Strength Indicator)......................................................... 6-5

6.3

General troubleshooting ..................................................................................... 6-6

6.4

Resetting the IP address .................................................................................... 6-7


6.4.1
DOS command ................................................................................... 6-7
6.4.2
Hardware reset ................................................................................... 6-7

Technical and ordering data ....................................................................................................7-3


7.1

Ordering data ..................................................................................................... 7-3


7.1.1
Products ............................................................................................. 7-3
7.1.2
Accessories ....................................................................................... 7-3

7.2

Technical data .................................................................................................... 7-4

Technical appendix................................................................................................................. A-1


A1

Structure of IP addresses .................................................................................. A-1


A 1.1
Valid IP parameters ............................................................................ A-1

A2

Assigning IP addresses ..................................................................................... A-1


A 2.1
Special IP addresses for special applications .................................... A-3
A 2.2
Value 255 in the byte ......................................................................... A-3
A 2.3
Subnet masks .................................................................................... A-3
A 2.4
Examples for subnet masks and computer bits .................................. A-5

Appendices............................................................................................................................. B-1

2476_en_K

B1

List of figures ..................................................................................................... B-1

B2

List of tables ...................................................................................................... B-5

B3

Explanation of terms .......................................................................................... B-7

PHOENIX CONTACT

iii

RAD-ISM-900-EN-BD

iv

PHOENIX CONTACT

2476_en_K

Section 1
This section informs you about
general features of the radio
overview of network topologies
wireless security and management

Overview .........................................................................................................................................1-3

2476_en_K

1.1

Wireless modules ............................................................................................... 1-3


1.1.1
Wireless module types......................................................................... 1-3

1.2

Trusted Wireless technology .............................................................................. 1-4

1.3

Applications........................................................................................................ 1-5
1.3.1
Ethernet connectivity ........................................................................... 1-5
1.3.2
Device server....................................................................................... 1-5
1.3.3
Modbus gateway ................................................................................. 1-6
1.3.4
Wireless remote I/O via Modbus .......................................................... 1-6

1.4

Network topology................................................................................................ 1-6

PHOENIX CONTACT

1-1

RAD-ISM-900-EN-BD

1-2

PHOENIX CONTACT

2476_en_K

Overview

Overview
1.1

Wireless modules

The 900 MHz Ethernet wireless modules utilize license-free Trusted Wireless technology to
provide reliable Ethernet, serial and I/O connectivity over long distances with radio
frequency (RF) data rates up to 500 kbps.
Some of the features of this series include:
1 W transmission power super heterodyne radio transceiver.
Function selection of master, slave or store-and-forward repeater mode.
Selectable 125, 250, or 500 kbps RF data rates with 128/192/256-bit AES encryption.
Built-in device server for integration of RS-232/422/485 devices onto Ethernet
networks.
Embedded web server and SNMP for configuration and diagnostics.
Modbus RTU/TCP compatible for process and industrial applications.
Support of networks with up to 4096 wireless modules.

1.1.1

Wireless module types

There are three variants of the 900 MHz Ethernet wireless modules.
The RAD-ISM-900-EN-BD features an RJ45 connector for connection of 10/100 Mbps
Ethernet devices as well as RS-232 and RS-422/485 ports that can be used as devices
servers or Modbus TCP/RTU gateways. It is freely configurable as a master, slave or
store-and-forward repeater.
The RAD-ISM-900-EN-BD-BUS includes all the functions of the RAD-ISM-900-EN-BD
plus a 5-pin bus connector for analog, digital, or frequency input/output expansion
modules to be attached (see Section 5). The I/O values are accessed using
Modbus/TCP protocol or, for read-only applications, an embedded XML file.
The RAD-ISM-900-EN-BD/B offers basic functionality with only a 10/100Mbps Ethernet
port and slave mode making it ideal for large scale network deployments.
Table 1-1

RAD-ISM-900-EN-BD wireless module types


10/100 Mbps
port

RS-232
port

RS-422/485
port

Expansion I/O
connectivity

Operating modes

RAD-ISM-900-EN-BD

Yes

Yes

Yes

No

Master, slave, storeand-forward repeater

RAD-ISM-900-EN-BD-BUS

Yes

Yes

Yes

Yes

Master, slave, storeand-forward repeater

RAD-ISM-900-EN-BD/B

Yes

No

No

No

Slave

2476_en_K

PHOENIX CONTACT

1-3

RAD-ISM-900-EN-BD

1.2

Trusted Wireless technology

The Trusted Wireless technology used in the RAD-ISM-900-EN-BD wireless modules is


intended specifically for industrial applications. Trusted Wireless technology provides the
following features:
Reliable communication via frequency-hopping spread spectrum (FHSS)
In the license-free 900 MHz frequency band, FHSS uses a selection of many channels from
the entire spectrum of the 902-928 MHz frequency band. The wireless module hops
between these channels in a pseudo-random pattern. This leads to a more robust and
reliable communication by tolerating interference.
Automatic and manual mechanisms for improved coexistence with nearby wireless
networks
Frequency blocking (or black listing) means that certain frequencies can be selectively
hidden. For example, this method allows you to operate several systems in parallel without
any performance limitations. In addition, Trusted Wireless makes use of packet
acknowledgements and re-transmissions to ensure reliable communication.
Secure data encryption
Trusted Wireless is a proprietary technology. The protocol has not been published;
therefore, it is better protected against attacks. In addition, security mechanisms have been
implemented with 128-bit AES data encryption. The data encryption makes sure that
intercepted data packets are not understood.
Long ranges from high receiver sensitivity and variable data transmission speed
The RF data rate is adjustable to match the application requirements (125-500 kbps). By
reducing the data rate, the sensitivity of the receiver is increased, enabling longer range
communication.
Flexible network structure with automatic connection management
Wireless modules can be used to create network structures with up to 4096 devices, which
may include any number of store-and-forward repeaters. In addition, the Trusted Wireless
network supports roaming to allow connection failures to self-heal. Alternative connection
paths are initiated automatically, but should be accounted for during the initial network
design. Devices configured as slaves may only communicate directly to repeaters or
masters.
Point to Point
M

S
S

Self-healing Tree

Star

S
S

R
R
S

Figure 1-1

1-4

PHOENIX CONTACT

R
S

Point to point, start and self-healing network configurations

2476_en_K

Overview
Comprehensive diagnostics

1.3

Applications

RAD-ISM-900-EN-BD wireless modules are for use in industrial applications where


reliable Ethernet connectivity over long distance is required. The low over-the-air data rate
(up to 500 kbps) is ideal for moving small payloads through environments with high
interference, but the limited bandwidth of the wireless system therefore requires
consideration in the design of the network.
Connecting Ethernet devices that may produce large amounts of data (megabytes or
more) can overload the wireless network, resulting in periods of intermittent or undesirable
operation.
The Trusted Wireless technology used in RAD-ISM-900-EN-BD modules was optimized
for poll and response systems, where a local controller requests some data from a remote
device, receives a response from the remote device, then requests data from another
remote device, receives a response, and so on. This optimization guarantees the maximum
amount of bandwidth is available for each transaction and that the overall wireless network
speed does not decrease as the number of wireless devices increases. This makes it ideal
for protocols such as Modbus or Ethernet/IP (explicit messaging). When these wireless
modules are used in systems with protocols that support scanning or unsolicited messages,
such as Ethernet/IP (implicit messaging) or OPC servers, timing parameters (timeouts, scan
rates, message delays, etc.) must be given careful consideration to prevent overloading the
wireless system. For assistance with planning such a network, please contact Phoenix
Contact Technical Service.
Further, when multiple LAN devices are connected to a single wireless module (for
example, two LAN networks are bridged via the wireless modules), any communication
between the Ethernet devices will be forwarded over the wireless connection, regardless of
the intended recipient. Simply, the wireless module will behave like a hub, forwarding any
Ethernet traffic it receives. To prevent this or any other broadcast or multicast traffic from
overloading the wireless system, Network Filtering rules may be used (see Section 4.5.3).

1.3.1

Ethernet connectivity

The most common use for RAD-ISM-900-EN-BD wireless modules is the connection of
10/100 Mbps Ethernet devices. A system consists of a central control station
communicating with one or more remote devices via the wireless connection. The wireless
network is transparent to the Ethernet devices.

1.3.2

Device server

RAD-ISM-900-EN-BD modules equipped with serial ports may be configured for use as
a wireless device server. A system consists of an Ethernet-enabled central control station
communicating with one or more RS-232/422/485 remote devices via the wireless
connection. The serial data is encapsulated in UDP packets by the RAD-ISM-900-EN-BD
modules. Any combination of RS-232 and RS-422/485 devices may be used at the remote
sites (see Section 4.5.5).

2476_en_K

PHOENIX CONTACT

1-5

RAD-ISM-900-EN-BD

1.3.3

Modbus gateway

RAD-ISM-900-EN-BD modules equipped with serial ports may be configured for use as
a wireless Modbus gateway. A system consists of a Modbus TCP central control station
communicating with one or more Modbus RTU remote devices via the wireless connection.
The serial Modbus data is converted to Modbus TCP by the RAD-ISM-900-EN-BD
modules. Any combination of RS-232 and RS-422/485 Modbus RTU devices may be used
at the remote sites. It is not possible to configure the wireless devices for use in a system
with a serial control station and Modbus TCP remote sites (see Section 4.5.5).

1.3.4

Wireless remote I/O via Modbus

RAD-ISM-900-EN-BD-BUS modules feature a bus connector for attaching various I/O


expansion modules. When one or more I/O expansion modules are attached, the wireless
device may be configured to emulate a PLC, and the various I/O points are addressable via
the Modbus protocol or may be monitored via an XML interface. Up to eight I/O expansion
modules may be connected to a RAD-ISM-900-EN-BD-BUS (seeSection 5).

1.4

Network topology

The RAD-ISM-900-EN-BD wireless module can be configured to operate as either a


master, slave or repeater. Depending on the configuration, the modules provide different
functions within the wireless network. These different functions result in a variety of network
topologies.
When determining a network topology, the following guidelines apply:
All wireless devices connected to the master are configured on the same subnetwork
as the wired network interface, and can be accessed by devices on the wired network.
A transceiver configured as a master can only communicate with devices configured as
slaves or repeaters. Conversely, devices configured as slaves can only communicate
with masters and repeaters.

1-6

PHOENIX CONTACT

2476_en_K

Section 2
This section informs you about
factors that affect radio performance
antenna and cable selection

System planning..............................................................................................................................2-3

2476_en_K

2.1

Accessing the site .............................................................................................. 2-3

2.2

Path quality analysis ........................................................................................... 2-3

2.3

Signal strength.................................................................................................... 2-3

2.4

Antennas and cabling ......................................................................................... 2-4


2.4.1
Coaxial cable considerations ............................................................... 2-5
2.4.2
Antenna mounting considerations........................................................ 2-5
2.4.3
Weatherizing connections.................................................................... 2-6
2.4.4
Maintaining system performance ......................................................... 2-6

PHOENIX CONTACT

2-1

RAD-ISM-900-EN-BD

2-2

PHOENIX CONTACT

2476_en_K

System planning

System planning
2.1

Accessing the site

To achieve the best wireless system performance possible, the installation sites have to be
given careful consideration. The primary requirements for a reliable installation include:
Antenna placement that allows for line-of-sight or adequate signal strength
Primary power source that provides required current
Protection of equipment from exposure to weather or temperature extremes
Suitable entrances for antenna, lightning arrestor, interface or other required cables - if
using remote antennas.
These requirements can be quickly assessed in most applications. A possible exception is
the first item, verifying that a clear line-of-sight exists. A non-obstructed path is ideal;
however, minor obstructions in the signal path will not always block communication. In
general, the need for a clear path becomes greater as the transmission distance increases.

2.2

Path quality analysis

With the exception of short-range applications, a path loss study is generally recommended
for new installations. The exceptions include distances of less than 305 m (1000 ft.) where
no test is required in 90% of applications, and where a test is done with a functional Phoenix
Contact wireless module set to the desired wireless mode, transmit data rate and transmit
power setting. A path loss study predicts the signal strength reliability and estimates the
fade margin of a proposed wireless link. While terrain, elevation and distance are the major
factors in this process, a path loss study also considers antenna gain, coaxial cable loss,
transmitter power and receiver sensitivity to arrive at a final prediction.
Path loss studies are normally performed by a communications consultant, wireless
hardware vendor or a system integrator who uses topographic maps or a software path
analysis to evaluate a proposed path.
Although path studies provide valuable assistance in system planning, they are not perfect
in their predictions. It is difficult, for example, to consider the effects of man-made
obstructions or foliage growth without performing an actual on-air test. Such tests can be
done using temporarily installed equipment.

2.3

Signal strength

The strength of wireless signals in a well-designed network must exceed the minimum level
needed to establish basic communication. The excess signal is known as the fade margin,
and it compensates for variations in signal level which may occur from time to time due to
foliage growth, minor antenna misalignment or changing atmospheric losses.
While the required amount of fade margin differs from one system to another, experience
has shown that a level of 20 dB above the receiver sensitivity threshold is sufficient in most
systems. RAD-ISM-900-EN-BD modules provide a means for direct measurement of
received signal strength using a DC voltmeter. Consult Section 6.2, RSSI (Received Signal
Strength Indicator) for more information.

2476_en_K

PHOENIX CONTACT

2-3

RAD-ISM-900-EN-BD

2.4

Antennas and cabling

The single most important item affecting wireless performance is the antenna system.
Careful attention must be given to this part of an installation, or the performance of the entire
system will be compromised. Quality high-gain antennas should be used at all stations. The
antennas should be specifically designed for use at the intended frequency of operation and
with matching impedance (50 ).
Antennas are made by several manufacturers and fall into two categories: omnidirectional
and yagi directional (see Figure 2-1). An omnidirectional antenna provides equal radiation
and response in all directions and is, therefore, appropriate for use at master stations which
must communicate with an array of remote stations scattered in various directions.
Omnidirectional antennas should also be used where clients will be mobile.

OMNI
Round Reflector Antenna

Vertical
Aperture Angle

YAGI
Directional Antenna

Vertical
Transmit and
Receive Range

Horizontal
Aperture Angle

Figure 2-1

Omni and directional antenna performance characteristics

At remote-fixed stations, a directional antenna, such as a yagi antenna, is typically used.


Directional antennas confine the transmission and reception of signals to a relatively narrow
beam width, allowing greater communication range, and reducing the chances of
interference from other users outside the pattern. It is necessary to aim these antennas in
the desired direction of communication, i.e., at the master station.
The end of the antenna (farthest from support mast) should face the associated station.
Final alignment of the antenna heading can be accomplished by orienting it for maximum
received signal strength.

2-4

PHOENIX CONTACT

2476_en_K

System planning

2.4.1

Coaxial cable considerations

The importance of using a low-loss antenna coaxial cable is often neglected during wireless
module installation. Using the wrong cable can cause huge reductions in efficiency, and
these losses cannot be recovered with any amount of antenna gain or transmitter power.
For every 3 dB of coaxial cable loss, half the transmitter power will be lost before reaching
the antenna. The choice of coaxial cable to use depends on: 1) the length of cable required
to reach the antenna, 2) the amount of signal loss that can be tolerated, and 3) cost
considerations. For long-range transmission paths, where signal is likely to be weaker, a
low-loss cable type is recommended.
For a short range system, or one that requires only a short antenna coaxial cable, a less
efficient cable may be acceptable, and will cost far less than large diameter cable. To judge
the effectiveness of various cables at 916 MHz, refer to Table 2-1.
Table 2-1

Cable types and signal loss at 916 MHz

Cable type

Loss (dB/100 ft.)

RG-58

16.5 dB

RG-213

7.6 dB

PFP 400

3.9 dB

PFP 600

2.5 dB

2.4.2

Antenna mounting considerations

The antenna manufacturers installation instructions must be strictly followed for proper
operation of a directional or omnidirectional antenna. Using proper mounting hardware and
bracket ensures a secure mounting arrangement with no pattern distortion or de-tuning of
the antenna. The following recommendations apply to all antenna installations:
Mount the antenna in the clear, as far away as possible from obstructions such as
buildings, metal objects, dense foliage, etc. Choose a location that provides a clear
path in the direction of the opposite antenna. If the antenna is co-located with another
antenna, try to get at least 0.3 m (1 ft.) separation, either vertically or horizontally,
between the two.
Polarization of the antenna is important. Most systems use a vertically-polarized
omnidirectional antenna at the master station. Therefore, the remote antennas must
also be vertically polarized (elements perpendicular to the horizon). Cross-polarization
between stations can cause a signal loss of 20 dB or more.
When installed indoors, the module must be grounded. Rail-mount versions are
grounded through the mounting rail and a ground lug used on wall-mount versions. A
surge arrestor must be used on the antenna for outdoor installations.

2476_en_K

PHOENIX CONTACT

2-5

RAD-ISM-900-EN-BD

2.4.3

Weatherizing connections

It is important to ensure all the components, including the connectors, are weatherized for
the specific climate where the installation is taking place. If the system is being installed
outdoors, a UV-rated enclosure and components need to be used. Also, all of the cabling
and connectors need to be weatherized.
Proper weatherization of all the connectors in a system will prevent water from entering the
components. Weatherization also prevents degradation of the connector due to UV
radiation, harsh temperatures, temperature changes and even pressure changes.
1. Ensure that all connectors are completely dry before installing.
2. Connect the cable assemblies. If the assemblies are N-type connectors, ensure that the
connection is torqued to 15-25 lbf-in. If the assembly is SMA or RPSMA, ensure that the
connection is torqued to 7-10 lbf-in.
3. Wrap vinyl electrical tape around the connection, extending 2 inches in each direction.
4. Cover the electrical tape with butyl or self-vulcanizing tape, extending 3 inches in each
direction to completely cover the electrical tape. Knead the butyl tape with your fingers
until no seams exist.
5. Cover the butyl tape with electrical tape, again extending beyond the edges of the butyl
tape. If wrapping a vertically hung cable, start at the bottom and work towards the top.
Each wrap should provide at least a 50% overlap.

2.4.4

Maintaining system performance

Over time, any communications system requires a degree of preventative maintenance to


ensure peak operating efficiency. Periodic checks of master and remote sites should be
made to identify and correct potential problems before they become threats to system
operation. The following areas should be given special attention:
Antennas and coaxial cable
Visually inspect the antenna and coaxial cable for physical damage, and make sure the
coaxial connections are tight and properly sealed against the weather. When using
directional antennas, be sure that the antenna heading has not shifted since installation.
The SWR (Standing Wave Ratio) of the antenna system can be checked from time to time
using a through-line wattmeter. Defects in the antenna system will frequently show up as
reflected power on the meter. It is good practice to accept only a maximum reflected power
of about 5%; this corresponds to an SWR of approximately 1.5:1. For any condition
exceeding this value, search for and correct the cause damaged antenna, defective or
improperly installed connectors, water in the coaxial feedline, etc.
2.4.4.1

Cable connections

All power, data, and ground connections should be secure and free of corrosion.
2.4.4.2

Power supply

The voltage of the station power supply should be measured to verify that it is within the
operating specifications for the wireless module. If possible, the wireless module should be
keyed during this test to ensure maximum current draw from the supply. Batteries, if used,
should be checked for charge level and signs of leakage or corrosion.

2-6

PHOENIX CONTACT

2476_en_K

Section 3
This section informs you about
mounting the wireless module
power connections to the wireless module
connecting Ethernet and serial communication
connecting the antenna

Installation .......................................................................................................................................3-3

2476_en_K

3.1

Mounting ............................................................................................................ 3-3

3.2

Making connections and powering up ................................................................ 3-6


3.2.1
Power connections .............................................................................. 3-6
3.2.2
Ethernet connections ........................................................................... 3-8
3.2.3
Serial port connections ........................................................................ 3-8

3.3

Antenna connections........................................................................................ 3-11

PHOENIX CONTACT

3-1

RAD-ISM-900-EN-BD

3-2

PHOENIX CONTACT

2476_en_K

Installation

Installation
3.1

Mounting

Figure 3-1 shows a typical RAD-ISM-900-EN-BD wireless module installation using a


Phoenix Contact power supply, end clamps and a grounding block.
End bracket

End bracket

ive

ce

Re

mit
ns
Tra
k

Lin
RF
R2
r
-03
we
Po 938
L-2
B
FL

Ground
terminal
block
-BD

-EN

00

To protective
Earth Ground

S
D-I
RA

M-9

Power
supply
RAD-ISM-900-EN-BD

To power
source
Figure 3-1

Typical installation

When mounting the module on a standard 35 mm mounting rail, end clamps should be
mounted on both sides of the module(s) to stop the modules from slipping on the rail (see
Figure 3-1).
Modules are installed from left to right on the mounting rail. Install modules to mounting rail
as described in the following steps.
WARNING:
Never install or remove a module while power is applied to any component on the rail.
Before installing or removing a module, disconnect power to the entire station. Make sure
work on the entire station is complete before switching power back on.

2476_en_K

PHOENIX CONTACT

3-3

RAD-ISM-900-EN-BD

WARNING:
Do not connect or disconnect any connector while power is ON. This can cause arcing that
could damage electronics or cause personal injury.
6.

Attach the RAD-ISM-900-EN-BD module to the mounting rail by positioning the


keyway at the top of the module onto the mounting rail (see Figure 3-2).
Then rotate the module inward until the release latch locks the module in place on the
rail. Next, check that the module is fixed securely to the rail by lightly pulling outward on
the module.
Installation

1Position on rail
2 Push in

Removal

3 Lift off rail


2 Rotate out
1 Open latch

Figure 3-2

3-4

PHOENIX CONTACT

Installation and removal from a mounting rail

2476_en_K

Installation
7.

Continue attaching any other module(s) to the mounting rail as described in Step 1.

Use end clamps on each side of the modules to hold them in place on the mounting rail.
8.

When all modules are installed, place an end clamp tight up against the left side of the
leftmost module on the mounting rail. Then place a second end clamp tight up against
the right side of the rightmost module on the mounting rail.

Ground clips built into the RAD-ISM-900-EN-BD make contact with the upper edge of
the rail during installation. This provides a ground path from the module to the rail. This
feature allows all modules to be grounded through the mounting rail to a single earthground.
9.

2476_en_K

Connect the mounting rail to protective earth ground using a grounding terminal block.

PHOENIX CONTACT

3-5

RAD-ISM-900-EN-BD

3.2
3.2.1

Making connections and powering up


Power connections

External interconnecting cables are to be installed in accordance to NEC, ANSI/NFPA70


(for US applications) and Canadian Electrical Code, Part 1, CSA C22.1 (for Canadian
applications) and in accordance to local country codes for all other countries.
Connect a regulated Class 2 DC power source to the module. The supply voltage can range
from 12 to 30 V DC with a nominal voltage of either 12 V DC or 24 V DC recommended. The
power supply must be able to supply 250 mA of current at 24 V DC. Figure 3-3 shows an
installation using a Phoenix Contact MINI power supply.

+24V GND
Power

A
B
RFLink

1 2 3 4

ive

ce

Re

it

m
ns
Tra
k

Lin
RF
R2
r
-03
we
Po 938
-2
L
LB

Ground
terminal
block
-BD

-EN

00

D-I

To protective
earth/ground

-9
SM

RA

L(+)
N(-)
Figure 3-3

3-6

PHOENIX CONTACT

Power connections for the RAD-ISM-900-EN-BD

2476_en_K

Installation
Figure 3-4 provides additional connection details to wire the RAD-ISM-900-EN-BD.

7 mm
(0.28 in.)

0.2-2.5 mm2
(14-24 AWG)

ive

ce

k
Lin
RF
R2
r
we -03
Po 938
-2
L
LB

ns
Tra

Re

mit

Torque screws to
0.5-0.6 Nm (1424 lbf-in.

Figure 3-4

2476_en_K

-BD

-EN

00

-9
SM
D-I
RA

Wiring requirements

PHOENIX CONTACT

3-7

RAD-ISM-900-EN-BD

3.2.2

Ethernet connections

Connect a CAT5 Ethernet cable between the port on the module and the network adapter
card on the computer. Use either a crossover (C/O) or straight-through (1:1) cable as the
wireless module has autocross functionality. The cable should not exceed 100 m (329 ft.) in
length.

Screw terminals
RS-422/485

ive

ce

Re

mit
ns
Tra
k

Lin
RF
R2
r
-03
we
Po 938
-2
L
LB

Ethernet
cable (RJ45)
-BD

-EN

00

S
D-I
RA

M-9

DB-9 connector
(RS-232)

Figure 3-5

3.2.3

Port connections

Serial port connections

Serial ports are used to transfer data to and from other devices. Configuration is done
through the Ethernet port.
RS-232 connections
When the correct RS-232 cable is used to connect the module (see Figure 3-5) to the
computer or PLC/industrial instrument, the TX LED on the wireless module will light. (This
TX LED will also flash when data is passed.)

3-8

PHOENIX CONTACT

2476_en_K

Installation
There are two types of serial port cables that both have DB-9 (9-pin D-sub) connectors (see
Figure 3-6). One is called a straight-through 9-pin serial port cable and the other is called a
null modem cable. On a straight-through cable, it is wired as just that straight through, in
other words, pin 1 is connected to pin 1, pin 2 to pin 2, etc.
A null modem cable crosses over pins 2 and 3 (transmit and receive data) and also crosses
over pins 7 and 8 (clear-to-send [CTS] and ready-to-send [RTS]). A null modem cable
allows two devices to be connected together when they both function as data terminal
equipment (DTE), or when they both function as data communications equipment (DCE).
By swapping the pins, it connects inputs to outputs and vice versa for proper operation.
Equipment with serial ports can be designed as either DTE or DCE. This determines the
functions of pins 2 and 3, and 7 and 8. For example, if pin 7 is an output on one end, then it
will have to be an input on the other end. Computers are typically DTE devices while
modems and wireless modems are DCE. Programmable Logic Controllers (PLCs), flow
computers and other industrial instruments could be either DCE or DTE.
To connect a DCE device to a DTE device, a straight-through cable is used. To connect two
DCE devices together or to connect two DTE devices together, a null modem cable is
required.

Figure 3-6

2476_en_K

RS-232 wire diagrams and pinouts

PHOENIX CONTACT

3-9

RAD-ISM-900-EN-BD
RS-422/485 connections
The module can also be connected to external devices using RS-422 or RS-485. Both 2wire and 4-wire configurations are supported. Although the 4-wire configuration supports
full duplex communications, the wireless module is only half duplex over the air.
RS-422 4-wire connection
RXD (B-)
RXD (A+)
TXD (B-)
TXD (A+)

RS-485 2-wire connection

Power
RF Link
FLBL-2938-03R2

Transmit

Receive

Power
RF Link
FLBL-2938-03R2

RAD-ISM-900-EN-BD

Figure 3-7

3-10

PHOENIX CONTACT

Transmit

Receive

RAD-ISM-900-EN-BD

RS-422/485 2-wire and 4-wire connections

2476_en_K

Installation

3.3

Antenna connections

An antenna should be connected to the connector on the top of the module, labeled ANT 1.
The connector on the module is an MCX socket. An antenna must be connected at all times
to provide a load for the RF power amplifier.

Antenna connection
(Antenna 1)

ive

ce

n
Tra

Re

it
sm

ink

L
RF
R2
r
-03
we
Po 938
-2
BL
L
F

-BD

-EN

00

S
D-I
RA

Figure 3-8

2476_en_K

M-9

MCX plug

Antenna connection

PHOENIX CONTACT

3-11

RAD-ISM-900-EN-BD

3-12

PHOENIX CONTACT

2476_en_K

Section 4
This section informs you about
configuring the PC to communicate with the wireless module
using the web-based configuration software

Programming the wireless module ..................................................................................................4-3

2476_en_K

4.1

Configuring a PC to communicate with the wireless device ................................ 4-3

4.2

Logging into the wireless module ....................................................................... 4-4

4.3

Viewing device information................................................................................. 4-5

4.4

Basic configuration ............................................................................................ 4-6

4.5

Configuration ..................................................................................................... 4-7


4.5.1
General configuration .......................................................................... 4-8
4.5.2
LAN settings ........................................................................................ 4-9
4.5.3
Configuring the Network Filter ........................................................... 4-11
4.5.4
Radio configuration............................................................................ 4-13
4.5.5
I/O Ports............................................................................................. 4-17
4.5.6
Device information ............................................................................. 4-21
4.5.7
Passwords ......................................................................................... 4-23
4.5.8
Store and retrieve settings ................................................................. 4-24

4.6

Performance..................................................................................................... 4-26

4.7

Maintenance..................................................................................................... 4-28
4.7.1
Software updates............................................................................... 4-29
4.7.2
Utilities ............................................................................................... 4-29
4.7.3
Reboot ............................................................................................... 4-30
4.7.4
Radio test .......................................................................................... 4-30

4.8

Monitoring/reports ............................................................................................ 4-31


4.8.1
Web log ............................................................................................. 4-31
4.8.2
Radio status....................................................................................... 4-32
4.8.3
Bridging status ................................................................................... 4-33

PHOENIX CONTACT

4-1

RAD-ISM-900-EN-BD

4-2

PHOENIX CONTACT

2476_en_K

Programming the wireless module

Programming the wireless module


4.1

Configuring a PC to communicate with the


wireless device

The instructions below are for a Windows 2000 operating system. Other operating
systems will be similar but not identical. You may need to be logged in as an administrator
to make these settings.
1.
2.
3.
4.

Go to the Network Connections dialog box, and then select Local Area Connections.
Right-click and select Properties from the context menu.
Highlight Internet Protocol (TCP/IP), and then click the Properties button (see
Figure 4-1).
Click the Use the following IP address button and enter 192.168.254.xxx (xxx can be
between 2 and 253) in the IP address field.
Enter 255.255.255.0 in the Subnet mask field, and then click the OK button.

Figure 4-1

2476_en_K

Internet Protocol (TCP/IP) Properties dialog box

PHOENIX CONTACT

4-3

RAD-ISM-900-EN-BD

4.2
1.
2.
3.

Logging into the wireless module

Apply power to the module and run a browser program (such as Internet Explorer) on
the computer. Wait approximately 10 seconds for the wireless module to boot up.
Enter the following IP address into the Address field of the browser
https://192.168.254.254
Enter the default case-sensitive credentials:

Configuration screen access


Username:

Admin

Password:

admin

Monitoring screen access


Username:

Monitor

Password:

monitor

Authentication mechanisms are used to authenticate an operator accessing the device


and to verify that the operator is authorized to assume the requested role and perform
services within that role.
Access to the management screens for the RAD-ISM-900-EN-BD wireless modules
requires entering an ID and password.
The user name and password are case sensitive.

4.

Check the Agree to the terms and conditions box, and then click the Sign In button.

Figure 4-2

Sign-in screen

Powering multiple devices with factory default IP addresses will cause a network conflict,
and incorrect parameters may be set in the RAD-ISM-900-EN-BD modules. When
programming wireless modules for the first time, it is important to apply power to only one
at a time and change the IP address of each module to a unique IP address (and different
from the PC). Once each device has a unique IP address they can be powered on
together. The IP address of the RAD-ISM-900-EN-BD modules can be changed under
Configuration LAN IP Configuration (see Section 4.5.2, LAN settings). The new IP
address must be known in order to gain access to the RAD-ISM-900-EN-BD module in
the future.

4-4

PHOENIX CONTACT

2476_en_K

Programming the wireless module

4.3

Viewing device information

After signing in, the home page shows the following basic information.

Figure 4-3

Home screen showing device configuration

The fields in this screen are:


Name/Location is a user adjustable field and can be edited on the General
Configuration screen (seeSection 4.5.1, General configuration). Information on where
this wireless module is installed or the site name is shown here. The factory default is
default location.
Device Mode: indicates the mode (master, repeater or slave) that the module is
operating in. The device mode can be configured on the Basic Configuration screen.
Time: The time of the wireless devices internal real-time clock in HH:MM:SS format.
Date: The date of the wireless devices internal real-time clock in MM/DD/YYYY format.
Uptime: Displays how long the wireless device has been in operation since the last
power cycle.
Status: Displays any operating or configuration error messages (see Section 6).
Radio Link: (firmware version 2.07 and later) Displays Active if a valid packet was
received within the last five seconds. Otherwise, the field displays inactive.
RSSI: (firmware version 2.07 and later) Indicates the average signal strength of all
packets received by the wireless module. A value of -151 dBm indicates no link.
Modules configured as a master will not display a valid RSSI value.

2476_en_K

Bandwidth Utilization: (firmware version 2.07 and later) Displays a value indicating
the amount of data being transmitted and received by the module compared to how
much data the device is capable of transmitting and receiving in the wireless network.
It may be used as a gauge to determine if the network traffic should be reduced to
maintain reliable communication. A utilization greater than 70% may indicate a potential
issue in the wireless network.
Firmware Version: (firmware version 2.07 and later) Identifies the version of software
loaded into the wireless module. This is important in the event that an upgrade
becomes available.

PHOENIX CONTACT

4-5

RAD-ISM-900-EN-BD

4.4

Basic configuration

The Basic Configuration screen is only available in firmware version 2.07 and later.

In firmware version 2.07 and later, the left navigation column provides a direct link to the
Basic Configuration screen. An Advanced Configuration category was created to
provide access to items that were included within the Configuration screen in firmware
versions prior to 2.07. Note that, while the name of the screen may be the same, the
content of the page may be different.
Click on Basic Configuration in the left navigation column to view and edit the basic
settings of the RAD-ISM-900-EN-BD module. The basic configuration settings are
adequate to use the module in most applications.

Figure 4-4

General Device Information screen

Device Name/Location: This field accepts text data to name this wireless module or
location. This may be used to help the network administrator identify this device from others
and has no impact on network operation.
Host Name: This field may be used to identify the host controller or other information, if
desired. It has no impact on network operation.
Domain Name: Enter the domain name or other information for the wireless device in this
field, if desired. This information has no impact on network operation.
System Time and Date: The time and date may be entered manually or synchronized with
the PCs internal clock. The wireless module uses a super capacitor to allow it to retain the
date and time in the event of a power outage.
Radio IP Address: Enter a static IP address for the wireless module.

4-6

PHOENIX CONTACT

2476_en_K

Programming the wireless module


If there is a DHCP server on the network that will be used to assign IP addresses to RADISM-900-EN-BD modules, it can be configured in the Advanced Configuration screen
(see Figure 4-6).
If the IP address is changed from the factory default, you will need to know this in order
to log back into the device for future configuration changes. If DHCP addressing is used,
additional software may be necessary to determine the IP address based on the MAC
address of the wireless device.
Network ID: This field specifies the network on which the module operates. To
communicate to another wireless device, it must reside on the same network with the same
network ID. Enter a value between 1 and 4095. If multiple networks are co-located, the
Network IDs must be different.
Radio Mode: Allows the user to select the RAD-ISM-900-EN-BD modules mode of
operation. Operational modes include master, slave and repeater.
Radio ID: A wireless device identification number that identifies the RAD-ISM-900-ENBD module to other wireless devices. Each wireless device in the network must have a
unique Radio ID. Enter a value between 0 and 4095.
Click the Submit button to write the configuration to the wireless module.
If no function is performed for 10 minutes, the web server within the module will
automatically log out and any settings that were not saved will be lost. It is good practice
to click the Submit button after all parameters are entered on each screen.

4.5

Configuration

In firmware version 2.07 and later, the left navigation column provides a direct link to the
Basic Configuration screen. An Advanced Configuration category was created to
provide access to items that were included within the Configuration screen in firmware
versions prior to 2.07. Note that, while the name of the screen may be the same, the
content of the page may be different.

2476_en_K

PHOENIX CONTACT

4-7

RAD-ISM-900-EN-BD

4.5.1

General configuration

Click on Advanced Configuration General in the left navigation column to access the
configuration parameters.

Figure 4-5

General Configuration screen

The following fields are displayed:


Device Name/Location: This field accepts text data to name this wireless module or
location. This is only used to help the network administrator identify this device from others
and has no impact on network operation.
Host Name: This field may be used to identify the host controller or other information, if
desired. It has no impact on network operation.
Domain Name: Enter the domain name of this wireless module, if desired. This information
is text only and has no impact on network operation.
Contact: Enter the name of the network administrator or individual responsible for this
equipment, if desired. It has no impact on network operation.
System Time and Date: The time and date may be entered manually, synchronized with
the PCs internal clock, or downloaded from an NTP Server. The wireless module uses a
super capacitor to allow it to retain the date and time in the event of a power outage.
To use an NTP server, the PC must either be connected to the LAN/WAN where it resides
or the PC can be connected to the Internet. Either way, enter the server address. One
example is the University of Houstons NTP server, which requires the address be entered
as follows:
tick.uh.edu
Click the Submit button to write the configuration to the wireless module.
If no functions are performed for 10 minutes, the program will exit and all parameters must
be re-configured. It is generally good practice to click the Submit button after all
parameters are entered on each screen.

4-8

PHOENIX CONTACT

2476_en_K

Programming the wireless module

4.5.2

LAN settings

Click on Advanced Configuration LAN in the left navigation column to access the
parameters related to configuring network communication.
4.5.2.1

IP Configuration

Click on Advanced Configuration LAN IP Configuration in the left navigation column


to access the parameters related to configuring the network communication.

Figure 4-6

LAN - IP Configuration screen

The following fields are displayed:


LAN Link Speed and Duplex: This determines the speed the module communicates with
the wired LAN device(s). The default value is 10 Mbps. It should be changed to Auto or 100
Mbps only if the LAN devices cannot be set to 10 Mbps.
LAN IP Address: Select the method your network uses to obtain IP addresses. If you are
using static IP addresses, enter the IP address you wish to assign to the wireless module.
Each device on the network must have a different IP address.
If there is a DHCP server on the network that will be used to assign IP addresses to the RADISM-900-EN-BD modules, select Use DHCP To Get IP Address.
If the IP address is changed from the factory default, you will need to know this in order to
log back into the wireless module for future configuration changes. If DHCP addressing is
used, additional software may be necessary to determine the IP address based on the
MAC address of the wireless module.
Enter a Subnet Mask and Default Gateway, if desired.
To access the Internet though this device, enter the IP address of the domain name
server(s) under DNS 1 and DNS 2.
Click the Submit button to write the configuration to the wireless module.

2476_en_K

PHOENIX CONTACT

4-9

RAD-ISM-900-EN-BD
4.5.2.2

SNMP Configuration

The Simple Network Management Protocol (SNMP) forms part of the Internet protocol that
monitors the health and welfare of network equipment such as routers and computers.
To configure SNMP, click on Advanced Configuration LAN SNMP Configuration in
the left navigation column (see Figure 4-7).
The SNMP interface is a lightweight method of changing the configuration of devices
across a network using a simple MIB browser.
The RAD-ISM-900-EN-BD wireless modules generate SNMP traps when one of the
following events occurs:
Cold start when the device powers up.
Warm start generated when the user invokes the Reboot option in the web interface.
Link up generated whenever the slave configuration is changed after the wireless
slave interface is restarted.
Link down generated whenever the slave configuration is changed before the
wireless slave interface is restarted.
Authentication failure generated when the user fails to authenticate via the web
interface.

Figure 4-7

4-10

PHOENIX CONTACT

LAN-SNMP Configuration screen

2476_en_K

Programming the wireless module


SNMP Agent: To disable SNMP, click the Disable button. SNMP v2c is enabled by default
with the following settings:
Table 4-1

Default SNMP settings

Community

Source

Access Control

Public

192.168.254.1

Read only

Private

192.168.254.1

Read/Write

Net

192.168.254.1

Notify

Community Settings: The community setting is a string of up to 30 characters. The


community name acts as a password and is used to authenticate messages sent between
an SNMP slave and a device containing an SNMP server. The community name is sent in
every packet between the slave and the server.
Source: (IP Access List) The IP access list identifies those IP addresses of SNMP
managers permitted to use a given SNMP community. An example of the network address
format is 192.168.42.182/24. The subnet mask of the network is typically annotated in
written form as a slash prefix that trails the network number.
Access Control: Sets the read/write access for the community.
Secure User Configuration Settings: This is the configuration for SNMP version 3.
User Name: A string of up to 30 characters.
Authentication Type: Indicates the algorithm used for authentication; it can be either MD5
or SHA, the latter one being the better algorithm.
Authentication Key: A string of characters used for authentication. Maximum length is
42 characters.
Encryption Type: Defines the encryption algorithm used by the SNMP protocol, and it can
be either DES or AES. AES is the strongest encryption algorithm.
Encryption Key: A string of up to 32 characters.
System information:
Location: The devices physical location, a string of up to 64 characters.
Contact: The person who manages the device, a string of up to 64 characters.
Engine ID: Each SNMPv3 agent has an engine ID that uniquely identifies the agent in
the device. The engine ID may be set by the network administrator and is unique to that
internal network. It is a string of up to 48 characters.
Click the Submit button to write the configuration to the wireless module.

4.5.3

Configuring the Network Filter

The RAD-ISM-900-EN-BD has some limited firewall capabilities and can be configured to
allow or block data from wired devices from being broadcast over the wireless network.
Packets can be filtered by specifying TCP port numbers, source or destination IP addresses
and source or destination MAC addresses. When the network filter is disabled, all Ethernet
traffic that is received at the LAN port of the wireless module will be sent of the wireless
network. This consumes bandwidth and may cause poor performance of the wireless
network. The network filter allows a user to ensure only packets destined for remote devices
are sent of the wireless link.

2476_en_K

PHOENIX CONTACT

4-11

RAD-ISM-900-EN-BD
To configure the network filter parameters, click on Advanced Configuration LAN
Network Filter in the left navigation column.

Figure 4-8

LAN - Network Filter Configuration screen

This feature is most commonly implemented on a wireless device configured as a master


that may also be connected to a LAN with network activity not destined for the wireless
network. In some installations, it may be desirable to enable it on a slave wireless module if
it is connected to several end wired devices that may need to communicate directly to one
another.
To utilize the Network Filter, click the Enable button to begin setting rules to filter traffic.
Packets can be blocked or allowed to pass based on the rules defined in the Network Filter
Rule section. After enabling the specified rule, click the Submit Network Filter Rule button.
It will then be possible to enter rules in the Add Network Filter Rule screen.
To log whenever a packet is blocked based on the rules, click the Enable button under
Network Filter Logging. Occurrences of a blocked packet will be logged in the System Log.
Note that only one entry is logged for all occurrences of a blocked packet per rule.
Network Filter Rules:
Traffic can be filtered by IP address, MAC address or port number, or both IP address and
port number or both MAC address and port number. A specific address or a range of
addresses can be entered. In the Field menu, choose if the rule is to apply to Source (data
coming from a wireless module or device), Destination (data going to a remote wireless
module or device (destination), or Any (data going to or from a wireless module or device).
After each rule is entered, click the Add Rule button. Each rule will then be shown in the
Active Network Filter Rules section. Once all rules are entered, click the Submit Network
Filter Configuration button to write the configuration to the wireless module.

4-12

PHOENIX CONTACT

2476_en_K

Programming the wireless module


Network filter rules can be entered using SNMP.
NOTE:
For an allow rule, if only the IP or MAC addresses of the end Ethernet devices connected
to each slave module are entered, you will not be able to communicate with the slave
wireless modules, via the RF link, for the purpose of changing configuration settings or
remote diagnostics. Be sure to enter the slave/repeater modules IP/MAC addresses in
addition to the end Ethernet devices.
It is typically easier to configure network filter rules to allow or deny packets based on TCP
port numbers in order to prevent the inadvertent blocking of data to or from a specific
device. For instance, in a SCADA system using Modbus TCP, add rules to allow only data
on TCP port 502 (default Modbus TCP port number) and TCP port 8080 (default HMTL
TCP port number, in order to access the web servers of remote wireless devices) will be
less complicated than entering rules for multiple IP addresses

4.5.4

Radio configuration

Click on Advanced Configuration Radio in the left navigation column to access the
parameters related to configuring the wireless communication.
4.5.4.1

Radio settings

To configure the wireless communication parameters, click on Advanced Configuration


Radio Settings in the left navigation column. The default values have been selected to
provide the most reliable system for nearly any application.

Figure 4-9

2476_en_K

Radio - Settings screen

PHOENIX CONTACT

4-13

RAD-ISM-900-EN-BD

Network ID: This specifies the network on which the wireless module operates. To
communicate to another module, it must reside on the same network with the same
network ID. Enter a value between 1 and 4096, in decimal format.
Repeaters in Network: This feature only needs to be set in the master wireless device.
The repeaters and slaves within the network will automatically detect the settings.

It is recommended to only enable this feature when repeaters are used in the network as
it may increase latency in the network.

Retransmit Broadcasts: This feature is only available when the module is set to
function in master mode. All frames sent by the master a broadcast with no
acknowledgements. Enabling this feature forces the master device to repeat every
frame multiple times to increase reliability. The default is 1 meaning every frame will be
sent twice.
Retries: Defines the number of times the module will attempt to transmit a frame before
discarding it. The feature is available in slave and repeater modes. The default is 3. The
user may select between 0 and 255 tries. All frames sent to the master are
acknowledged and, if the first transmission of a frame is received, the wireless module
will not send the frame again.
Hop Pattern ID: This read-only value is calculated directly from the network ID. If there
are multiple networks in an area, ensure that the hop patterns are not the same. If they
are, change one of the network ID numbers.
Radio Mode: Allows the user to select the wireless modules mode of operation.
Operational modes include master, slave and repeater.
Radio ID: A wireless module identification number that identifies the module to other
wireless devices. Each device in the network must have a unique Radio ID. Enter a
value between 0 and 4095.
Data Rate: The RF data rate used by the wireless device protocol. This feature is set
to 500 kbps by default. The user may select between 125, 250 or 500 kbps.
Decreasing the data rate decreases the channel width, which can improve
performance in noisy environments. The RF data rate must be configured to the same
value in each wireless device in the network.
Frame Size: The user may select between latency, balanced, or throughput. Smaller
frames have less latency between each transmission and transfer less data. In
applications with high levels of interference, latency mode may be used to hop faster.
Larger frames hop more slowly (which may be more susceptible to interference) and
send more data on each channel, which is useful for protocols that have large payloads.
This feature is set to Latency by default and is available in all three data rates.
Latency mode has a packet size of 110 bytes, Balanced has a packet size of
264 bytes and Throughput has a size of 440 bytes.
Roaming: Determines whether the wireless module may roam to link to any master or
repeater in the network or if a specific master or repeater must be used. This feature is
set to Yes by default, allowing any slave or repeater to connect to any master on its
respective network.

If a system requires roaming to provide alternate wireless connections, the wireless


network must be designed to accommodate this. Give special consideration to antenna
selection to ensure multiple paths are available

4-14

PHOENIX CONTACT

Tx Power: The transmit power of the wireless device. This feature is set to +30 dBm
by default and is available in all three operational modes. The user may select between
+10 dBm and +30 dBm in 1-dBm increments.

2476_en_K

Programming the wireless module

Fixed Master ID: Defines the master or repeater wireless module address when
roaming in disabled. This feature is disabled by default and is available in the slave and
repeater operational modes. The Fixed Master ID may be between 0 and 4095.
Alternate Fixed Master ID: Alternate masters that can specified if the master listed in
Fixed Master ID field is unavailable. If Roaming is set to No and the wireless module
is unable to link to the Radio ID entered in the Fixed Master ID field, it will attempt to
link to the Radio ID entered in the Alternate Fixed Master ID 1 field, if the Use
Alternate Master ID check box is enabled. If the wireless module is unable to link to
Alternate Fixed Master ID 1, it will attempt to link to the Radio ID entered under
Alternate Fixed Master ID 2 field. Either of the alternate masters can be disabled by
clearing the check box next to the ID field. This setting applies to slaves and repeaters
only. Note that the antennas must be selected such that all possible paths to repeaters
are within the antennas beam width.

Before clicking a different item in the left navigation column, click the Submit button to
transfer the changes from the browser tool to the wireless module. An additional message
appears (see Figure 4-10) prompting to either click the Apply Radio Changes button or
reboot the unit. If the button is clicked, the module re-starts the firmware and additional
configurations can be made using the options in the left navigation column. This requires
approximately 5 seconds. If the module is rebooted, the reboot process requires
approximately 2 minutes.

Figure 4-10
4.5.4.2

Apply Radio Changes button


Wireless security

To enable encryption of the data when it is sent over the wireless connection, click
Advanced Configuration Radio Security from the left navigation column (see
Figure 4-11).

2476_en_K

PHOENIX CONTACT

4-15

RAD-ISM-900-EN-BD
Static AES Security - Enter a 32-digit hexadecimal Key for 128-bit encryption, a 48-digit
hexadecimal Key for 192-bit encryption, a 64-digit hexadecimal Key for 256-bit
encryption or click the Key Generator button and have the program generate a key
automatically. Copy the key into all slave or repeater wireless modules. They must have the
same key in order to communicate.

Figure 4-11

Static AES security screen

Click the Submit button to write the configuration to the wireless module.
4.5.4.3

Frequency blocking

To configure frequency blocking, click on Advanced Configuration Radio Frequency


Blocking in the left navigation column.

Figure 4-12

Frequency Blocking

In applications where there is a known interference problem, frequency bands can be


blocked in the RAD-ISM-900-EN-BD wireless modules to decrease packet loss. The
amount of RF spectrum that can be blocked depends on which RF data rate is used.

4-16

PHOENIX CONTACT

2476_en_K

Programming the wireless module


Up to three separate frequency ranges can be blocked. The sum of the frequency ranges
cannot exceed those listed in the table. The Available Spectrum field indicates how much
more of the band can be blocked.
After inserting all frequency ranges that would cause known interference, click the Submit
button. An additional message appears (see Figure 4-13) prompting to click the Apply
Radio Changes button. This will reboot the unit and the settings will take effect.

Figure 4-13

Apply Radio Changes button

The same frequency ranges must be blocked in every device.

4.5.5

I/O Ports

4.5.5.1

Ethernet port

The RAD-ISM-900-EN-BD can be configured to receive and transmit I/O data between
devices connected to the Ethernet port of a master wireless module and a serial port of a
slave wireless module.
To configure the Ethernet ports, click on Advanced Configuration I/O Ports Ethernet
Ports in the left navigation column. Two advanced functions are available.
Modbus/TCP Gateway
Enabling this feature allows the wireless modules to emulate a Modbus TCP to Modbus
RTU converter. Modbus TCP data packets are converted to Modbus RTU packets and
redirected out the wireless devices serial port(s). Enter the Modbus TCP port number
(default 502) and select channel 1 or 2 from the Connect to Stream drop-down menu.
Gateway/Ethernet Terminal Radio
Enabling this feature allows the wireless modules to emulate a device server by redirecting
data on the LAN port of the master wireless device to the serial port(s) of the slave wireless
devices.

2476_en_K

PHOENIX CONTACT

4-17

RAD-ISM-900-EN-BD
In the Ethernet Terminal Port Parameters field, enter a TCP port number. Only the data
that uses this TCP port is forwarded through the serial ports. From the Protocol type dropdown menu, select either TCP or UDP.

Figure 4-14

Ethernet Ports Configuration screen

From the Connect to Stream drop-down menu, select channel 1 or 2. The Ethernet
terminal port channel selected must be different from the one used for the Modbus/TCP
serial channel selected; they cannot use the same serial channel.
The same serial channel must be selected when configuring the RS-232 or RS-422/485
port(s) on the remote wireless device(s). When finished, click the Submit button.
4.5.5.2

Serial ports

Data can be transferred between the serial port of a master wireless module and the serial
port of a slave wireless module.
There are two independent serial channels (1 and 2) that allow use of the two physical serial
ports on each RAD-ISM-900-EN-BD module (RS-232 and a RS-422/485 port). The serial
port function varies depending on the mode of operation. Serial data transmitted from a
slave modules serial port will only be available at the serial port of the master module. Serial
data transmitted from a master modules serial port will appear at the serial port of each
slave module (broadcast mode).

4-18

PHOENIX CONTACT

2476_en_K

Programming the wireless module


To configure the RS-232/422/485 ports, click on Advanced Configuration I/O Port
Serial Ports in the left navigation column.

Figure 4-15

Serial Ports Configuration screen

The baud rate, data bits, stop bits, parity, and flow control settings must match those of the
serial device that will be connected to the port. Click the option buttons and select from the
drop-down menus to configure the parameters for appropriate port, either RS-232 or RS485. The following fields are duplicated between the RS-232 and RS-485 ports:
Baud Rate: Sets the speed data that flows in/out the serial port.
Data Bits: Sets the number of bits that make up each character.
Parity: Sets the error checking method.
Stop Bits: Sets the number of bits that signify the end of a character.
Flow Control (RS-232 only): Prevents buffer overflow when data streaming into the
wireless module arrives faster than it can be sent out the serial port. The RAD-ISM-900-ENBD modules have a 600-byte buffer. Buffer overflow occurs when transmitting a message
larger than 600 bytes because the over-the-air data rate is much higher than the serial port
data rate. Enable flow control to resolve this.
Full/Half Duplex (RS-422/485 only): Sets the communication method.
Connect to Stream: There are two independent serial streams available for network-wide
serial data. There are also two independent local channels that can be used.
Click the Submit button to write the configuration to the wireless module.
4.5.5.3

Data streaming

Data streaming is used to prevent buffer overflow when data streaming into the wireless
module arrives faster than it can be sent out the serial port.
The RAD-ISM-900-EN-BD modules have a 600-byte buffer. Buffer overflow occurs
when transmitting a message larger than 600 bytes because the over-the-air data rate is
much higher than the serial port data rate.

2476_en_K

PHOENIX CONTACT

4-19

RAD-ISM-900-EN-BD
To configure the data streams, click on Advanced Configuration... IO ports... Data
streaming in the left navigation column.

Figure 4-16

Data Streaming Mode Configuration screen

The buffer is configured on a per-channel basis with each channel (serial 1, serial 2, local 1
and local 2) allowing configuration in either character mode or packet mode.
All wireless devices on the same channel must be set to the use the same mode.

Character mode: Passes data on the first available hop without waiting for the entire
packet. Recommended for high data throughputs such as ASCII data strings.
Packet mode: If the serial port is idle for greater than 3.5 characters intervals (based
on the configured baud rate), it will determine the packet has been received in its
entirety and send the data out the serial port. Packet mode is recommended for smaller
data transfers and where a short delay in a packet at the controller could cause an error,
e.g., Ethernet IP.

4.5.5.4

PLC Interface

This only applies to the RAD-ISM-900-EN-BD-BUS module. Refer to Section 5, Bus


configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only) for details.

4-20

PHOENIX CONTACT

2476_en_K

Programming the wireless module

4.5.6

Device information

4.5.6.1

General device information

Click on Advanced ConfigurationDevice Information General in the left navigation


column to view the current network configuration and device version of the wireless module.

Figure 4-17

General Device Information screen

LAN IP Address: Displays the current IP address of the wireless device. An IP address is
the logical address of a network adapter. The IP address uniquely identifies this module on
the network.
LAN Subnet Mask: Displays the current subnet mask of the wireless device. A subnet
mask is a bit mask used to tell how much of an IP address identifies the subnetwork the host
is on and how much identifies the host.
LAN Default Gateway: Displays the current default gateway of the wireless device. A
default gateway is a node on the network that serves as an master to a different network
(possibly the Internet).
LAN MAC Address: Displays the current MAC address of the LAN port on the wireless
device. Media Access Control address (MAC address) is a unique identifier attached to
most forms of networking equipment. It is the physical address of the hardwired Ethernet
port that is permanently assigned by the manufacturer.
Radio MAC Address: This displays the MAC address of the MOTR-9 radio transceiver.
There are separate MAC addresses for the radio and the physical Ethernet port.
Serial Number: This is the manufacturers serial number of the wireless device.
Firmware Version: Identifies the version of software loaded into the wireless device. This
is important in the event upgrades become available.
Hardware Version: Identifies the version and revision level of the circuit boards.
Radio Firmware Version: Identifies the firmware version of the electronics within the
wireless module.
Radio Firmware Version: Identifies the firmware version of the radio transceiver contained
within the wireless module.

2476_en_K

PHOENIX CONTACT

4-21

RAD-ISM-900-EN-BD
Radio Serial Number: The radio transceivers unique serial identification number.
4.5.6.2

Local diagnostics

Click on Advanced Configuration Device Information Local Diagnostics in the left


navigation column to view the current status of the wireless device. This screen mimics the
LEDs on the module. For more information on the status LEDs, see LED indicators on
page 6-4.

Figure 4-18

4-22

PHOENIX CONTACT

Local Diagnostics screen

2476_en_K

Programming the wireless module


4.5.6.3

Device diagram

Click on Advanced Configuration Device Information Device Diagram in the left


navigation column to view a diagram of the wireless module.

Device diagram screen (RAD-ISM-900-EN-BD-BUS shown)

4.5.7

Passwords

There are administrator passwords and monitor passwords. The administrator can make
changes to the configuration while a monitor can only view information.

2476_en_K

PHOENIX CONTACT

4-23

RAD-ISM-900-EN-BD
To change or set passwords, click on Advanced Configuration Passwords in the left
navigation column.

Figure 4-19

Configuration - Password Modification screen

To change either password, the appropriate password must be entered in all three fields.
Click the Submit button when finished.

4.5.8

Store and retrieve settings

To save the configuration parameters of the wireless module to the PC hard drive, load the
factory default parameters, or send the configuration to the wireless device, click on
Advanced Configuration Store Retrieve Settings in the left navigation column.

Figure 4-20

4-24

PHOENIX CONTACT

Configuration -Store Retrieve Settings screen

2476_en_K

Programming the wireless module


A passphrase is required to protect/validate the file before it can be saved or retrieved from
the PC. It prevents unauthorized users from applying the system configuration file to an
unauthorized node to gain access to the network.

2476_en_K

PHOENIX CONTACT

4-25

RAD-ISM-900-EN-BD

4.6

Performance

Several aspects of the devices performance can be monitored. The LAN Performance
screen (see Figure 4-21) provides information on the activity of the LAN port. The Radio
Performance screen (see Figure 4-23) offers statistics on the performance of the wireless
connection. The Serial Performance screen (see Figure 4-22) presents statistics on the
RS-232/422/485 data.
To access these screens, click on Performance in the left navigation column, and then
click the desired sub-menu. Each section contains a field to set the refresh interval (in
seconds) of the screen.

4-26

PHOENIX CONTACT

Figure 4-21

LAN Performance screen

Figure 4-22

Serial Performance screen

2476_en_K

Programming the wireless module

Figure 4-23

Radio Statistics Performance screen

The Radio Statistics Performance screen displays diagnostic information about the quality
of the wireless link. The upper fields provide received packet diagnostics and the lower
fields display transmitted packet diagnostics.
Table 4-2

Wireless module performance values

Statistic

Description

Maximum
value1

Frames Received

The number of good frames received by the wireless module.

10,000

Receive Errors

The total amount of frames that were missed or contained errors.

10,000

Receive Frames Dropped

The number of frames that were dropped due to lack of memory.

10,000

RF Link Lost Count

The number of times that the module lost link since the last power cycle. 65,535

Success Percent

The percentage of successfully received packets in the wireless link.

100

Assured Transmitted

The total number of frames transmitted by the wireless device

10,000

Frames Retried

The total number of frames that were sent more than once because an
acknowledgement was not received from another wireless device.

10,000

Frames Dropped

The number of frames dropped without being successfully received by


another wireless device because the maximum number of retries was
reached. A high number of dropped frames may indicate a high level of
interference.

10,000

TX Utilization (%)2

The ratio of time slots in which data was transmitted compared to the
number of available time slots averaged over 10 s.

100

RX Utilization (%)2

The ratio of time slots in which data was received compared to the
number of available time slots averaged over 10 s.

100

2476_en_K

PHOENIX CONTACT

4-27

RAD-ISM-900-EN-BD
Table 4-2

Wireless module performance values

Statistic

Description

Maximum
value1

TX Stalled Slots (%)2

The ratio of time slots in which the device had data to transmit but
couldnt due to activity in the wireless network. Values above 10-20%
indicate there is a problem in the wireless network due to interference or
excessive data.

100

Repeated Assured
Transmitted

The total number of frames repeated by the wireless module (repeaters


only).

10,000

Repeated Frames Retried

The total number of frames that were sent more than once because an
acknowledgement was not received from another wireless device
(repeaters only).

10,000

Repeated Frames Dropped

The number of frames that were dropped without being successfully


received by another wireless device because the maximum number of
retries was reached. A high number of dropped frames may indicate a
high level of interference (repeaters only).

Repeater TX Utilization (%)2

The ratio of time slots in which data was transmitted compared to the
number of available time slots averaged over 10 s (repeaters only).

100

Repeater RX Utilization (%)2

The ratio of time slots in which data was received compared to the
number of available time slots averaged over 10 s (repeaters only).

100

Repeater TX Stalled Slots


(%)2

The ratio of time slots in which the device had data to transmit but
couldnt due to activity in the wireless network. Values above 10-20%
indicate there is a problem in the wireless network due to interference or
excessive data (repeaters only)

100

Items with a maximum value of 10,000 normalize with related values when one value reaches the maximum. For
example, when the Frames Received field reaches 10,000, it resets to 5000 and the related Receive Errors
and Receive Frames Dropped fields divide by two. This maintains the ratio between related fields.

Firmware version 2.07 and later

4.7

Maintenance

Various maintenance capabilities are included within the management software.

4-28

PHOENIX CONTACT

2476_en_K

Programming the wireless module

4.7.1

Software updates

To view the version of the firmware, click on Maintenance Software Updates in the left
navigation column

Figure 4-24

Software Updates screen

There are two separate firmware files for the RAD-ISM-900-EN-BD wireless modules.
The first file controls the features and functions of the device as a whole. The MOTR-9 radio
transceiver has a separate firmware file to control the RF functions. Firmware update files
may be released that update one or both files.

4.7.2

Utilities

To access the Utilities screen, click on Maintenance Network Utilities in the left
navigation column.

Figure 4-25

Utilities screen

The Utilities screen includes a field to enter an IP address or host name. Click the Ping
button to find out if it is online and functional.
The Utilities screen also includes a Traceroute field. Enter an IP address or host name in
the field and click the Traceroute button to show the path a packet of information takes to
get to its destination.

2476_en_K

PHOENIX CONTACT

4-29

RAD-ISM-900-EN-BD

4.7.3

Reboot

To access the Reboot Device screen, click on Maintenance Reboot in the left
navigation column.

Figure 4-26

Reboot Device screen

The Reboot Device screen allows the user to reboot the device from the connected
computer. This is convenient if the device is located in a remote location and is not easily
accessible.

4.7.4

Radio test

To access the Radio Test screen, click on Maintenance Radio Test screen in the left
navigation column.

Figure 4-27

Radio Test screen

The Radio Test screen allows transmit and receive tests to be performed. Click the
VSWR Measurement button to disable the frequency-hopping mechanism and begin a
constant carrier transmission at 902.7 MHz for a period of 30 seconds. This function can be
used to do VSWR tests on antennas and coaxial cable, or perform antenna alignment.

4-30

PHOENIX CONTACT

2476_en_K

Programming the wireless module


Click the Background Noise Measurement button to perform a sweep of the 902-928 MHz
band to take a measurement of the RF noise on each channel.
Only one test can be run at a time. Click either the VSWR Test Mode or the Background
Noise Measurement button, but not both.
Once the desired test is selected, click the Measure button to perform the test(s). The
average and peak measurements will be displayed.
For accurate measurements, all other RAD-ISM-900-EN-BD devices in the network
should be powered down to prevent the wireless transmissions from being measured.

4.8

Monitoring/reports

Several screens are available that provide additional information to the user.

4.8.1

Web log

Click on Monitoring/Reports Web Access Log in the left navigation column to display a
list of system facility messages involving web access.

Figure 4-28

Monitoring - Web Access Log screen

The log documents the user who made the changes with a date and time stamp. For
example, this log records if the encryption mode was set, if the operating mode was
changed, etc. The Web Access Log continues to accumulate listings until cleared. To clear
the listings, click the Clear button.

2476_en_K

PHOENIX CONTACT

4-31

RAD-ISM-900-EN-BD

4.8.2

Radio status

Click on Monitoring/Reports Radio Status to review statistics on the devices current


status.

Figure 4-29

Monitoring - Radio Status screen

RSSI: The average signal strength of all packets received by the wireless module. A value
of -151 dBm indicates no RF link.
Units configured as a master will not display a valid RSSI value.

Link Status: This field displays ACTIVE if a valid RF packet was received within the last 5
seconds. Otherwise, this field displays INACTIVE.
Supply (Battery) Voltage: Displays the voltage of the supply that is currently powering the
device.
Temperature: Displays the temperature of the device in degrees Celsius.
The Device Snapshot feature (firmware version 2.07 and later) creates a compressed
archive file containing several individual files with information about the specific wireless
module. This may be useful to technical support when troubleshooting.

4-32

PHOENIX CONTACT

2476_en_K

Programming the wireless module

4.8.3

Bridging status

Click on Monitoring/Reports Bridging Status to review statistics on the interface


between the wireless module and Ethernet connection.

Figure 4-30

2476_en_K

Monitoring - Bridging Status screen

PHOENIX CONTACT

4-33

RAD-ISM-900-EN-BD

4-34

PHOENIX CONTACT

2476_en_K

Section 5
This section informs you about
RAD I/O communications
I/O Module descriptions
addressing remote I/O
rotary switches
register scaling
wiring and fail condition DIP switches
accessing the XML file

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only) .............................................5-3

2476_en_K

5.1

Wireless I/O communications ............................................................................. 5-3


5.1.1
Modbus I/O overview ........................................................................... 5-3
5.1.2
System overview.................................................................................. 5-3
5.1.3
I/O system configuration overview ....................................................... 5-4
5.1.4
Configuring wireless modules connected to I/O................................... 5-5
5.1.5
Configuring wireless modules connected to the PLC /Modbus master 5-7

5.2

I/O module descriptions...................................................................................... 5-8


5.2.1
Connecting and configuring the I/O modules ....................................... 5-9

5.3

Addressing the remote I/O.................................................................................. 5-9

5.4

Rotary switches ................................................................................................ 5-16

5.5

Register scaling ................................................................................................ 5-16


5.5.1
Digital channels ................................................................................. 5-16
5.5.2
Analog channel scaling...................................................................... 5-17
5.5.3
Pulse input channels.......................................................................... 5-17
5.5.4
Pulse output channels........................................................................ 5-17

5.6

Wiring and fail condition DIP switches for the I/O modules ............................... 5-19
5.6.1
Analog input module .......................................................................... 5-19
5.6.2
Digital input module ........................................................................... 5-20
5.6.3
Analog output module........................................................................ 5-21
5.6.4
Digital output module ......................................................................... 5-22
5.6.5
Combination input/output module ...................................................... 5-23
5.6.6
Digital pulse input module.................................................................. 5-24
5.6.7
Digital pulse output module................................................................ 5-27

5.7

Accessing the XML file ..................................................................................... 5-29

PHOENIX CONTACT

5-1

RAD-ISM-900-EN-BD

5-2

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

Bus configuration for I/O modules


(RAD-ISM-900-EN-BD-BUS only)
5.1
5.1.1

Wireless I/O communications


Modbus I/O overview

The RAD-ISM-900-EN-BD-BUS features a bus connector for attaching various I/O


expansion modules. When one or more I/O expansion modules are attached, the wireless
module may be configured to emulate a PLC, and the various I/O points are addressable via
the Modbus protocol. Up to eight I/O expansion modules may be connected to each RADISM-900-EN-BD-BUS and the station acts as a single block of Modbus I/O.
The analog I/O values are located in 4xxxx registers, the digital input values located in 1xxxx
registers and the digital outputs are controlled by writing to the 0xxxx registers. The 8position rotary switch on each I/O expansion module determines the specific register
addresses (see TTable 5-1 and Table 5-2). For additional system flexibility, additional serial
and/or Ethernet devices may be connected to the wireless device even when the I/O
expansion modules are connected.

5.1.2

System overview

The RAD-ISM-900-EN-BD-BUS wireless module allows up to eight RAD I/O modules to be


controlled by a Modbus (RTU or TCP) based PLC/PC (or other Modbus master device). The
group of RAD I/O modules, connected to a RAD-ISM-900-EN-BD-BUS wireless module,
act as a single Modbus slave I/O station, and communicate over a wired or wireless serial
communications stream to a Modbus TCP or Modbus RTU master PLC (or other type of
controlling device).
Typical I/O applications
Many application configurations are possible including the following:
1. A master PLC connected to any RAD-ISM-900-EN-BD-BUS wireless module and
configured as either a master or slave. Configured as wireless, the master PLC controls
RAD I/O attached to remotely mounted RAD-ISM-900-EN-BD-BUS wireless modules
in slave mode.
a) Master PLC connects to the module's serial port and uses Modbus RTU.
b) Master PLC connects to the module's Ethernet port and uses Modbus TCP.
2. A master PLC connected to a RAD-ISM-900-EN-BD-BUS wireless module and
configured as a master. The master PLC controls both locally attached RAD I/O and
controls I/O attached to remotely mounted RAD-ISM-900-EN-BD-BUS wireless
modules in slave mode.
Master PLC connects to the modules serial port and uses Modbus RTU
Master PLC connects to the modules Ethernet port and uses Modbus TCP

2476_en_K

PHOENIX CONTACT

5-3

RAD-ISM-900-EN-BD
Additional system flexibility
1.

2.

Any RAD-ISM-900-EN-BD-BUS wireless module can be used in applications where a


master PLC communicates wirelessly to distributed PLCs that are attached to remotely
mounted RAD-ISM-900-EN-BD-BUS wireless modules.
I/O communications uses only one of the two serial communication streams allowing
the other stream to be used simultaneously with other devices connected to the unused
serial and Ethernet ports.

5.1.3

I/O system configuration overview

To enable communications between the RAD I/O and a Modbus-based master, the
following settings need to be configured.
1. RAD-ISM-900-EN-BD-BUS wireless module connected to the I/O:
a) The Modbus address and communications timeout of the RAD-ISM-900-EN-BDBUS wireless module must be set.
b) The I/O must be assigned to the serial or local communication stream that will be
controlling them.
NOTE:
For applications where a single master is polling multiple RAD-ISM-900-EN-BD-BUS I/O
stations, all the I/O stations must be set to the same serial communications stream.
c)

2.

5-4

PHOENIX CONTACT

When the I/O is used as a stand-alone remote I/O station, the module is typically
configured as a slave.
d) If the PLC/Modbus master connects to a RAD-ISM-900-EN-BD-BUS wireless
module in order to use its I/O as an additional, locally mounted I/O, the module can
be configured as a wireless master. In this case, the wireless modules master
settings must also be configured (refer to Typical I/O applications on page 5-3).
Any RAD-ISM-900-EN-BD-BUS wireless module connected to the PLC /Modbus
master:
a) The serial (RS-232) port or Ethernet port connected to the Modbus master may be
assigned to a serial communication stream.
b) If the master is a Modbus TCP (Ethernet) device, the Modbus gateway function
must be enabled. This converts the Modbus TCP commands to the Modbus RTU
commands. These commands are used by the RAD-ISM-900-EN-BD-BUS unit to
control the I/O. The communication conversion is one-way. Only Modbus TCP
commands are converted to Modbus RTU commands. A serial Modbus RTU
master cannot use the Modbus gateway function to talk to other Modbus
TCP-based I/O.
c) The module must be configured as a master.

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.1.4

Configuring wireless modules connected to I/O

PLC interface configuration


To enable communication between the RAD I/O and a Modbus-based master, the Modbus
address and Communications Timeout must be set, and a communications stream must be
assigned. These parameters are found on the PLC Interface Configuration web page.
Configure the wireless module as described in the following steps so the I/O modules can
be accessed.
1. Click Configuration I/O Ports PLC Interface on the left-hand menu.

Figure 5-1
2.

3.

4.

5.

2476_en_K

PLC Configuration menu

Set PLC Emulation Mode.


To enable communications between the RAD I/O and a Modbus-based master, the
PLC Emulation mode must be set to MODBUS.
Enter the PLC Address.
Enter the Modbus node address that you wish to assign to the module. The address
should be between 0 and 254 and must be different from all other Modbus devices in
the network. A wrong address setting will result in the PLC address box resetting to 0.
Enter a Timeout value.
The timeout setting controls a communications watchdog timer that triggers the I/O fault
mode in the event communications between the PLC/Modbus master and the I/O are
disrupted. The timeout default setting is 5 seconds. Enter a value between 0 and
999 seconds. A 0 setting disables the communications watchdog timer. For more
detailed information, see Timeout setting for I/O control on page 5-6.
Enter the value to Connect to a Stream.
One of the two serial or local communication streams must be dedicated to handle the
communication to and from the I/O. Select either of the two serial or local channels.
Since only one stream can control all the I/O in the system, the channel selected must
be the same for the Modbus master, and all I/O connected to all modules.

PHOENIX CONTACT

5-5

RAD-ISM-900-EN-BD
Timeout setting for I/O control
A communications timeout setting is needed because there can be many intermediate
wireless module or Ethernet segments between the Modbus (RTU or TCP) master device
and the various slave modules I/O. Due to the multiple intermediate segments,
communications can be stopped even though the wireless link or Ethernet link to the module
is intact. The timeout function compares the elapsed time between the last Modbus read or
write commands, and a preset value. If the actual time exceeds the timeout preset, the
module assumes that the I/O modules are no longer under control, and sets all the I/O
attached to the module to their fault state. The value should be set to the slowest machine
or process function that the I/O (attached to the module) is controlling.
It is important to note that the I/O will not fail to its fault off condition in the event of an RF link
loss. The I/O will only fail to the fault off condition when the timeout setting value is reached.
Enter a value of 0 will disable the watchdog, and the fault condition will also be disabled.
I/O Timeout diagnostics
In the event of a timeout, the STATUS LED flashes (at a fast two flashes per second rate)
indicating an application error. At the same time, the status LEDs on the I/O module(s) will
turn off completely when a Modbus application error exists. In addition, the wireless module
sends an Ethernet error message via SNMP and makes an entry into the diagnostic log web
page. When communication is re-established by the next Modbus read or write command,
the watchdog is reset, I/O communications automatically resume, an I/O is Operational
SNMP message is sent and a web-based diagnostic log message is entered.

Figure 5-2

Example of SNMP diagnostic error message

Duplicate I/O addresses


NOTE:
If I/O modules are installed with duplicate addresses (rotary switch settings), the I/O data
will be erroneous. When installing or changing I/O modules, ensure that the status LEDs
indicate a valid I/O configuration before reading or writing data to the I/O. Failure to do this
may result in unexpected machine or process operation.
Control I/O from one source
The I/O is designed for control in a typical Modbus (RTU or TCP) master slave system. For
proper system operation, only one Modbus RTU or Modbus TCP master is allowed to
control the I/O modules. If a second Modbus master attempts to connect, the first will be
disconnected. The RAD-ISM-900-EN-BD-BUS wireless module allows the I/O to be
controlled from either Ethernet-based Modbus TCP or serial interface-based Modbus RTU
masters. When assigning the PLC I/O function to a communications stream, ensure that

5-6

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)


there is only one source controlling the I/O: either a single Ethernet master source or a single
serial source, but NOT both. If two I/O control sources are assigned to the I/O stream, the
error message shown in Figure 5-3 is generated.

Figure 5-3

5.1.5

Error message Multiple I/O communication control sources on same


channel

Configuring wireless modules connected to the PLC


/Modbus master

General Configuration
To connect a RAD-ISM-900-EN-BD-BUS wireless module to a Modbus master device
either Modbus RTU serial, or Modbus TCP Ethernet based (i.e., a PLC or PC-based
controller), the module must be configured as a master (refer to Figure 4-6 on page 4-9).
Configuration when connecting to a Modbus RTU master controller
Modbus RTU masters connect to either the RS-232 or RS-422/485 serial ports on the
module.
1. Configure the serial ports physical parameters (baud rate, stop bits, etc.) (refer to I/O
Ports on page 4-17).
2. Configure the RAD-ISM-900-EN-BD-BUS communication stream to the same
communication stream as that used by the RAD-ISM-900-EN-BD-BUS units I/O (refer
to Serial ports on page 4-18).
Configuration when connecting to a Modbus TCP Ethernet master controller
Modbus TCP master devices connect to the Ethernet port on the module.
1. Configure the Ethernet ports link speed and duplex settings (refer to LAN settings on
page 4-9).
2. Configure the Modbus Gateway parameter to Network Gateway and enter 502 as
the port number (refer to Modbus/TCP Gateway on page 4-17).
3. Configure the RAD-ISM-900-EN-BD-BUS communications stream to the same
communications stream as that used by the RAD-ISM-900-EN-BD-BUS unit's I/O (refer
to Serial ports on page 4-18).
Ensure that there is only one source controlling the I/O: either a single Ethernet master
source, or a single serial source, but NOT both on the same communications stream.

2476_en_K

PHOENIX CONTACT

5-7

RAD-ISM-900-EN-BD

5.2

I/O module descriptions

There are seven different I/O modules that can be used with the RAD-ISM-900-EN-BD-BUS
wireless module. They are powered from the module through the 5-pin male/female
connector on either side of the module and I/O module. They feature an 8-position rotary
switch on the top of each module for addressing.
Analog input module RAD-IN-4A-I
This module has four (4) 0-22 mA current inputs. It can either accept powered loops or
provide the power for a loop. The power supply for the loops is common to the module's
power supply.
Analog output module RAD-OUT-4A-I
This module has four (4) 0-22 mA current outputs. It can accept either powered loops or
provide the power for a loop. Each current loop is optically isolated. Internally there are four
DIP switches that determine what happens to each current channel if the wireless link is lost
either fail to 2 mA or maintain the last known value.
Digital input module RAD-IN-8D
This module has eight (8) digital inputs. Each input requires a voltage to trigger it. Each
channel is optically isolated.
Digital output module RAD-OUT-8D
This module has eight (8) digital outputs. Each output is a normally open dry contact.
Internally there are eight DIP switches that determine what happens to each channel if the
network link is lost either fail open or maintain the last known value.
Analog/digital I/O module RAD-IN+OUT-2D-1A-I
This module has a mix of inputs and outputs 1 analog input, 1 analog output, 2 discrete
inputs and 2 discrete outputs. Internally there are DIP switches that determine the fail
condition of the outputs in a similar fashion as described in the above modules.
Pulse input module RAD-IN-2D-CNT
This module has two configurable pulse or frequency inputs. A 5-position DIP switch inside
the module is used to set the mode of each channel, as well as the input impedance,
coupling, speed, and input type (single-ended or differential). It is compatible with the
following common pulse generating devices:
AC sine wave output devices such as magnetic transducers.
Digital pulse output devices such as microprocessor-based flow meters.
Mechanical relay pulse output devices or toggle switches.
Pulse output module RAD-OUT-2D-CNT
This module has two configurable pulse or frequency outputs. A 4-position DIP switch inside
the module is used to set the mode of each channel as well as the speed (high or low).

5-8

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.2.1
1.

2.

3.
4.

Connecting and configuring the I/O modules

Remove the plastic housing from the output modules and set the fail condition DIP
switches as desired for each channel. Refer to Wiring and fail condition DIP switches
for the I/O modules on page 5-19 for more details.
Connect the I/O modules and module to the mounting rail, and slide them together so
the
5-pin male/female connectors mate.
Set the 8-position rotary switch on the I/O modules so each I/O module connected to
the module has a unique address.
Wire the analog and discrete signals. Next, connect the antenna and apply power.

5.3

Addressing the remote I/O

Each wireless module must have a unique Modbus address programmed into it. I/O
modules attached to each module have their analog, discrete, or frequency inputs and
outputs mapped to registers. When a command from the master PLC (through the Modbus
TCP Gateway module) is broadcast to all remote wireless devices, they read the address to
determine if they should respond. Within each command there is a read or write request to
certain registers. Table 5-1 and Table 5-2 are address maps that correlate each I/O channel
to a Modbus register. The different columns relate to different address ranges. For instance,
the module #1 digital outputs are maintained in registers 00017 - 00024.
Note that the registers 40001, 40002, and 40003 show the RSSI, internal temperature and
power supply voltage. The RSSI is presented as a positive number. Add the negative sign
to determine the RSSI in dB. For example, if 67 is the value in the register, the RSSI is
-67dB. The internal temperature is expressed in degrees Celsius and the power supply
voltage in volts.
Table 5-1

Modbus memory map


00xxx

10xxx

40xxx

Reserved

Reserved

RSSI

Reserved

Reserved

Power Supply Voltage

Reserved

Reserved

Temperature

4-16

Reserved

Reserved

Reserved

17-24

Module #1 digital outputs

Module #1 digital inputs

Module #1 raw analog inputs

25-32

Reserved

Reserved

Module #1 raw analog outputs

33-40

Module #2 digital outputs

Module #2 digital inputs

Module #2 raw analog inputs

41-48

Reserved

Reserved

Module #2 raw analog outputs

49-56

Module #3 digital outputs

Module #3 digital inputs

Module #3 raw analog inputs

57-64

Reserved

Reserved

Module #3 raw analog outputs

65-72

Module #4 digital outputs

Module #4 digital inputs

Module #4 raw analog inputs

73-80

Reserved

Reserved

Module #4 raw analog outputs

81-88

Module #5 digital outputs

Module #5 digital inputs

Module #5 raw analog inputs

89-96

Reserved

Reserved

Module #5 raw analog outputs

97-104

Module #6 digital outputs

Module #6 digital inputs

Module #6 raw analog inputs

2476_en_K

PHOENIX CONTACT

5-9

RAD-ISM-900-EN-BD
Table 5-1

Modbus memory map (continued)


00xxx

10xxx

40xxx

105-112

Reserved

Reserved

Module #6 raw analog outputs

113-120

Module #7 digital outputs

Module #7 digital inputs

Module #7 raw analog inputs

121-128

Reserved

Reserved

Module #7 raw analog outputs

129-136

Module #8 digital outputs

Module #8 digital inputs

Module #8 raw analog inputs

137-144

Reserved

Reserved

Module #8 raw analog outputs

145

Reserved

Reserved

Reserved

146

Reserved

Reserved

Reserved

147

Reserved

Reserved

Module #1 digital inputs

148

Reserved

Reserved

Module #1 digital outputs

149

Reserved

Reserved

Module #2 digital inputs

150

Reserved

Reserved

Module #2 digital outputs

151

Reserved

Reserved

Module #3 digital inputs

152

Reserved

Reserved

Module #3 digital outputs

153

Reserved

Reserved

Module #4 digital inputs

154

Reserved

Reserved

Module #4 digital outputs

155

Reserved

Reserved

Module #5 digital inputs

156

Reserved

Reserved

Module #5 digital outputs

157

Reserved

Reserved

Module #6 digital inputs

158

Reserved

Reserved

Module #6 digital outputs

159

Reserved

Reserved

Module #7 digital inputs

160

Reserved

Reserved

Module #7 digital outputs

161

Reserved

Reserved

Module #8 digital inputs

162

Reserved

Reserved

Module #8 digital outputs

501-508

Reserved

Module #1 digital inputs

Module #1 scaled analog inputs

509-516

Reserved

Module #2 digital inputs

Module #2 scaled analog inputs

517-524

Reserved

Module #3 digital inputs

Module #3 scaled analog inputs

525-532

Reserved

Module #4 digital inputs

Module #4 scaled analog inputs

533-540

Reserved

Module #5 digital inputs

Module #5 scaled analog inputs

541-548

Reserved

Module #6 digital inputs

Module #6 scaled analog inputs

549-556

Reserved

Module #7 digital inputs

Module #7 scaled analog inputs

557-564

Reserved

Module #8 digital inputs

Module #8 scaled analog inputs

565

Reserved

Reserved

Module #1 digital inputs

566

Reserved

Reserved

Module #2 digital inputs

567

Reserved

Reserved

Module #3 digital inputs

568

Reserved

Reserved

Module #4 digital inputs

569

Reserved

Reserved

Module #5 digital inputs

570

Reserved

Reserved

Module #6 digital inputs

571

Reserved

Reserved

Module #7 digital inputs

5-10

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)


Table 5-1

Modbus memory map (continued)


00xxx

10xxx

40xxx

572

Reserved

Reserved

Module #8 digital inputs

701-708

Module #1 digital outputs

Reserved

Module #1 scaled analog outputs

709-716

Module #2 digital outputs

Reserved

Module #2 scaled analog outputs

717-724

Module #3 digital outputs

Reserved

Module #3 scaled analog outputs

725-732

Module #4 digital outputs

Reserved

Module #4 scaled analog outputs

733-740

Module #5 digital outputs

Reserved

Module #5 scaled analog outputs

741-748

Module #6 digital outputs

Reserved

Module #6 scaled analog outputs

749-756

Module #7 digital outputs

Reserved

Module #7 scaled analog outputs

757-764

Module #8 digital outputs

Reserved

Module #8 scaled analog outputs

765

Reserved

Reserved

Module #1 digital outputs

766

Reserved

Reserved

Module #2 digital outputs

767

Reserved

Reserved

Module #3 digital outputs

768

Reserved

Reserved

Module #4 digital outputs

769

Reserved

Reserved

Module #5 digital outputs

770

Reserved

Reserved

Module #6 digital outputs

771

Reserved

Reserved

Module #7 digital outputs

772

Reserved

Reserved

Module #8 digital outputs

950

Reserved

Reserved

Module #1 ID

951

Reserved

Reserved

Module #2 ID

952

Reserved

Reserved

Module #3 ID

953

Reserved

Reserved

Module #4 ID

954

Reserved

Reserved

Module #5 ID

955

Reserved

Reserved

Module #6 ID

956

Reserved

Reserved

Module #7 ID

957

Reserved

Reserved

Module #8 ID

2476_en_K

PHOENIX CONTACT

5-11

RAD-ISM-900-EN-BD

Table 5-2

Modbus Pulse Memory Map

00xxx

40xxx

17 Module #1 Input 1 Value Control Bit

Module #1 Input 1 LSW Value

18 Module #1 Input 2 Value Control Bit

Module #1 Input 1 MSW Value (Pulse mode only)

19

Module #1 Input 1 LSW Value Store (Pulse mode only)

20

Module #1 Input 1 MSW Value Store (Pulse mode only)

21

Module #1 Input 2 LSW Value

22

Module #1 Input 2 MSW Value (Pulse mode only)

23

Module #1 Input 2 LSW Value Store (Pulse mode only)

24

Module #1 Input 2 MSW Value Store (Pulse mode only)

25

Module #1 Output 1 LSW Value

26

Module #1 Output 1 MSW Value (Pulse mode only)

27

Module #1 Output 1 Absolute or Differential Operation LSW

28

Module #1 Output 1 Absolute or Differential Operation MSW

29

Module #1 Output 2 LSW Value

30

Module #1 Output 2 MSW Value (Pulse mode only)

31

Module #1 Output 2 Absolute or Differential Operation LSW

32

Module #1 Output 2 Absolute or Differential Operation MSW

33 Module #2 Input 1 Value Control Bit

Module #2 Input 1 LSW Value

34 Module #2 Input 2 Value Control Bit

Module #2 Input 1 MSW Value (Pulse mode only)

35

Module #2 Input 1 LSW Value Store (Pulse mode only)

36

Module #2 Input 1 MSW Value Store (Pulse mode only)

37

Module #2 Input 2 LSW Value

38

Module #2 Input 2 MSW Value (Pulse mode only)

39

Module #2 Input 2 LSW Value Store (Pulse mode only)

40

Module #2 Input 2 MSW Value Store (Pulse mode only)

41

Module #2 Output 1 LSW Value

42

Module #2 Output 1 MSW Value (Pulse mode only)

43

Module #2 Output 1 Absolute or Differential Operation LSW

44

Module #2 Output 1 Absolute or Differential Operation MSW

45

Module #2 Output 2 LSW Value

46

Module #2 Output 2 MSW Value (Pulse mode only)

47

Module #2 Output 2 Absolute or Differential Operation LSW

48

Module #2 Output 2 Absolute or Differential Operation MSW

49 Module #3 Input 1 Value Control Bit

Module #3 Input 1 LSW Value

50 Module #3 Input 2 Value Control Bit

Module #3 Input 1 MSW Value (Pulse mode only)

51

Module #3 Input 1 LSW Value Store (Pulse mode only)

52

Module #3 Input 1 MSW Value Store (Pulse mode only)

53

Module #3 Input 2 LSW Value

5-12

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)


Table 5-2

Modbus Pulse Memory Map (continued)

00xxx

40xxx

54

Module #3 Input 2 MSW Value (Pulse mode only)

55

Module #3 Input 2 LSW Value Store (Pulse mode only)

56

Module #3 Input 2 MSW Value Store (Pulse mode only)

57

Module #3 Output 1 LSW Value

58

Module #3 Output 1 MSW Value (Pulse mode only)

59

Module #3 Output 1 Absolute or Differential Operation LSW

60

Module #3 Output 1 Absolute or Differential Operation MSW

61

Module #3 Output 2 LSW Value

62

Module #3 Output 2 MSW Value (Pulse mode only)

63

Module #3 Output 2 Absolute or Differential Operation LSW

64

Module #3 Output 2 Absolute or Differential Operation MSW

65 Module #4 Input 1 Value Control Bit

Module #4 Input 1 LSW Value

66 Module #4 Input 2 Value Control Bit

Module #4 Input 1 MSW Value (Pulse mode only)

67

Module #4 Input 1 LSW Value Store (Pulse mode only)

68

Module #4 Input 1 MSW Value Store (Pulse mode only)

69

Module #4 Input 2 LSW Value

70

Module #4 Input 2 MSW Value (Pulse mode only)

71

Module #4 Input 2 LSW Value Store (Pulse mode only)

72

Module #4 Input 2 MSW Value Store (Pulse mode only)

73

Module #4 Output 1 LSW Value

74

Module #4 Output 1 MSW Value (Pulse mode only)

75

Module #4 Output 1 Absolute or Differential Operation LSW

76

Module #4 Output 1 Absolute or Differential Operation MSW

77

Module #4 Output 2 LSW Value

78

Module #4 Output 2 MSW Value (Pulse mode only)

79

Module #4 Output 2 Absolute or Differential Operation LSW

80

Module #4 Output 2 Absolute or Differential Operation MSW

81 Module #5 Input 1 Value Control Bit

Module #5 Input 1 LSW Value

82 Module #5 Input 2 Value Control Bit

Module #5 Input 1 MSW Value (Pulse mode only)

83

Module #5 Input 1 LSW Value Store (Pulse mode only)

84

Module #5 Input 1 MSW Value Store (Pulse mode only)

85

Module #5 Input 2 LSW Value

86

Module #5 Input 2 MSW Value (Pulse mode only)

87

Module #5 Input 2 LSW Value Store (Pulse mode only)

88

Module #5 Input 2 MSW Value Store (Pulse mode only)

89

Module #5 Output 1 LSW Value

90

Module #5 Output 1 MSW Value (Pulse mode only)

91

Module #5 Output 1 Absolute or Differential Operation LSW

2476_en_K

PHOENIX CONTACT

5-13

RAD-ISM-900-EN-BD
Table 5-2

Modbus Pulse Memory Map (continued)

00xxx

40xxx

92

Module #5 Output 1 Absolute or Differential Operation MSW

93

Module #5 Output 2 LSW Value

94

Module #5 Output 2 MSW Value (Pulse mode only)

95

Module #5 Output 2 Absolute or Differential Operation LSW

96

Module #5 Output 2 Absolute or Differential Operation MSW

97 Module #6 Input 1 Value Control Bit

Module #6 Input 1 LSW Value

98 Module #6 Input 2 Value Control Bit

Module #6 Input 1 MSW Value (Pulse mode only)

99

Module #6 Input 1 LSW Value Store (Pulse mode only)

100

Module #6 Input 1 MSW Value Store (Pulse mode only)

101

Module #6 Input 2 LSW Value

102

Module #6 Input 2 MSW Value (Pulse mode only)

103

Module #6 Input 2 LSW Value Store (Pulse mode only)

104

Module #6 Input 2 MSW Value Store (Pulse mode only)

105

Module #6 Output 1 LSW Value

106

Module #6 Output 1 MSW Value (Pulse mode only)

107

Module #6 Output 1 Absolute or Differential Operation LSW

108

Module #6 Output 1 Absolute or Differential Operation MSW

109

Module #6 Output 2 LSW Value

110

Module #6 Output 2 MSW Value (Pulse mode only)

111

Module #6 Output 2 Absolute or Differential Operation LSW

112

Module #6 Output 2 Absolute or Differential Operation MSW

113 Module #7 Input 1 Value Control Bit

Module #7 Input 1 LSW Value

114 Module #7 Input 2 Value Control Bit

Module #7 Input 1 MSW Value (Pulse mode only)

115

Module #7 Input 1 LSW Value Store (Pulse mode only)

116

Module #7 Input 1 MSW Value Store (Pulse mode only)

117

Module #7 Input 2 LSW Value

118

Module #7 Input 2 MSW Value (Pulse mode only)

119

Module #7 Input 2 LSW Value Store (Pulse mode only)

120

Module #7 Input 2 MSW Value Store (Pulse mode only)

121

Module #7 Output 1 LSW Value

122

Module #7 Output 1 MSW Value (Pulse mode only)

123

Module #7 Output 1 Absolute or Differential Operation LSW

124

Module #7 Output 1 Absolute or Differential Operation MSW

125

Module #7 Output 2 LSW Value

126

Module #7 Output 2 MSW Value (Pulse mode only)

127

Module #7 Output 2 Absolute or Differential Operation LSW

128

Module #7 Output 2 Absolute or Differential Operation MSW

129 Module #8 Input 1 Value Control Bit

Module #8 Input 1 LSW Value

5-14

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)


Table 5-2

Modbus Pulse Memory Map (continued)

00xxx

40xxx

130 Module #8 Input 2 Value Control Bit

Module #8 Input 1 MSW Value (Pulse mode only)

131

Module #8 Input 1 LSW Value Store (Pulse mode only)

132

Module #8 Input 1 MSW Value Store (Pulse mode only)

133

Module #8 Input 2 LSW Value

134

Module #8 Input 2 MSW Value (Pulse mode only)

135

Module #8 Input 2 LSW Value Store (Pulse mode only)

136

Module #8 Input 2 MSW Value Store (Pulse mode only)

137

Module #8 Output 1 LSW Value

138

Module #8 Output 1 MSW Value (Pulse mode only)

139

Module #8 Output 1 Absolute or Differential Operation LSW

140

Module #8 Output 1 Absolute or Differential Operation MSW

141

Module #8 Output 2 LSW Value

142

Module #8 Output 2 MSW Value (Pulse mode only)

143

Module #8 Output 1 Absolute or Differential Operation LSW

144

Module #8 Output 1 Absolute or Differential Operation MSW

2476_en_K

PHOENIX CONTACT

5-15

RAD-ISM-900-EN-BD

5.4

Rotary switches

On the top of each I/O module is an 8-position rotary switch. In the address maps in
Table 5-1 and Table 5-2 there are references to module numbers. These module numbers
refer to the position of the rotary switch. Each module must have a different number.

Figure 5-4

I/O module 8-position rotary switch

5.5

Register scaling

5.5.1

Digital channels

A digital output channel can be turned on by writing a 1 to the digital output register, and
off by writing a 0 to the output register.

5-16

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.5.2

Analog channel scaling

Analog channels are scaled as follows:


Current Input =

Current Output =

5.5.3

(Register Value) 22 mA
32767
(X mA) 32767
22 mA

Pulse input channels

If the input channel is set to frequency mode, the value displayed in the corresponding
register will be the input signal frequency in Hz (0-32 kHz).
If the pulse input channel is set to counter mode, each channel will have a 32-bit register
(two consecutive 16-bit registers) assigned to it. The first (LSW) register keeps the current
count (up to 32,767). To manually reset a channel to zero (0), simply write a 1 to the coil
register that corresponds to that channel. Refer to the address map in this section to
determine the correct register. A channel is reset to zero when the coil transitions from a 0
to a 1.
NOTE:
If a pulse input channel is set to counter mode, you may need to periodically reset the
register to prevent overflow. To reset a channel to zero, simply write a 1 to the coil
register that corresponds to that channel. Refer to the address map to determine which
register. A reset command is executed when the coil transitions from a 0 to a 1.

5.5.4

Pulse output channels

If the output channel is set to frequency mode, the value entered in the corresponding
register will be the output signal frequency in Hz (0-32 kHz). In frequency mode, the only
register that will respond to PLC commands is the least significant word (LSW). Because
the most significant word (MSW) exceeds the maximum pulse frequency that the module
can produce, any values written to it will be ignored.
If the pulse output channel is set to counter mode, each channel will have a 32-bit register
(two consecutive 16-bit registers) assigned to it. The counter mode has two different types
of operations: (1) absolute count and (2) differential count. The two modes are described in
the following paragraphs.
Absolute mode
Pulses produced = New pulse count - Previous pulse count
In absolute mode, the total number of pulses provided is equal to the pulse output register
value.
For example, if the previous value in the register was 5 and a new value of 15 is written, 10
pulses will be produced. However, if a new value of 3 were written, the pulse module would
produce enough pulses to wrap the 32-bit register around until it is reset to 0 and then
deliver 3 more pulses. Therefore, the pulse register should be cleared periodically.

2476_en_K

PHOENIX CONTACT

5-17

RAD-ISM-900-EN-BD
Differential mode
Pulses produced = New pulse count
In differential mode, the number of pulses produced is equal to each new value written to
the pulse output register.
For example, if a value of 10 was written to the pulse output register, 10 pulses would be
produced. If a new value of 5 were written, 5 more pulses would be produced.
To initialize absolute or differential counts, refer to the address map to determine which
registers are used to control the operation mode. Absolute mode is initialized by writing 0 to
both control registers: differential mode is specified by writing 1 to the LSW and 0 to the
MSW.
Clearing a counter register
To clear a counter register when using Modbus RTU protocol, use function code 16
(multiple register write) and write a value of 0 (LSW), -32768 (MSW) to the pulse output
counter.
NOTE:
When counter mode is selected, if the number of counts to be delivered is not complete
before a new pulse count is written to the register, the new counts are added to the existing
count.
NOTE:
(For OPC Servers)
If using an OPC server, it may not write the clear register values with a single instruction.
Use differential mode if the OPC server commands cannot clear the counter. There is no
need to clear counters in differential mode.

5-18

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.6

5.6.1

Wiring and fail condition DIP switches for the I/O


modules
Analog input module

If using the analog input module, use the wiring diagram shown in Figure 5-5.

Figure 5-5

2476_en_K

RAD-IN-4A-I analog input module wire diagram

PHOENIX CONTACT

5-19

RAD-ISM-900-EN-BD

5.6.2

Digital input module

If using a digital (discrete) input module, use the wiring diagram shown in Figure 5-6.

Figure 5-6

5-20

PHOENIX CONTACT

RAD-IN-8D digital input module wire diagram

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.6.3

Analog output module

If using the analog output module, use the wiring diagram shown in Figure 5-7.
Inside the analog output module are DIP switches that allow the user to determine the status
of each channel if the RF link is lost. The options are Maintain Last State and Fault Off to a
current value of approximately 2 mA. Release the top part of the housing to access the
internal DIP switches.

Figure 5-7

2476_en_K

RAD-OUT-4A-I analog output module wire diagram

PHOENIX CONTACT

5-21

RAD-ISM-900-EN-BD

5.6.4

Digital output module

If using the digital output module, use the wiring diagram shown in Figure 5-8.
Inside of the digital output module are DIP switches that allow the user to determine the
status of each channel if the RF link is lost. The options are Maintain Last State or Fault Off
(open circuit). Release the top part of the housing to access the internal DIP switches.

Figure 5-8

5-22

PHOENIX CONTACT

RAD-IN-OUT-8D-REL digital output module wire diagram

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.6.5

Combination input/output module

If using the combo module, use the wiring diagram shown in Figure 5-9.
Inside of the combo module are DIP switches that allow the user to determine the status of
each channel if the RF link is lost. The options are Maintain Last State or Fault Off (open
circuit). Release the top part of the housing to access the internal DIP switches.

Figure 5-9

2476_en_K

RAD-OUT-8D-REL digital output module wire diagram

PHOENIX CONTACT

5-23

RAD-ISM-900-EN-BD

5.6.6

Digital pulse input module

The digital pulse input module accepts pulse signals from many different types of devices.

Figure 5-10

RAD-IN-2D-CNT pulse input module wire diagram

Backup power
The digital pulse input module will retain its pulse count if power is removed; however, it will
not record any new pulses. Terminals 5 and 6 are used for connecting the backup power
supply to the module. If primary power (through the bus connector from the module) is lost,
the backup power supply allows the module to continue to record pulses. The backup power
terminals will not supply power to the transceiver or any other module on the bus connector.
DIP switch settings
Refer to Figure 5-9 on page 5-23 for DIP switch configurations.

5-24

PHOENIX CONTACT

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)


AC/DC coupling
Set the jumper to AC coupling if the pulse voltage will never drop below 3.6 V with respect
to the transceiver's power supply negative. This would apply where there is a DC bias
voltage added to the pulse input voltage, and the DC bias exceeds 3.6 V, such as in a
ground loop condition. All other applications, including an AC sine wave input, should be set
to DC Coupling.
Low/high input impedance
The low impedance setting has an input impedance of 1 k, and the high setting has an
impedance of 90 k. High impedance should be used with magnetic transducers to prevent
the current draw from dropping the voltage below the 100 mV AC peak-to-peak minimum.
The low impedance setting should be used with digital and relay interfaces because the
additional current draw will prevent electrical noise from causing false pulse counts.
Counter/frequency operating mode
The pulse input values can be stored in the PLC register in two formats; either a count of the
number of pulses or a frequency value. The frequency setting will take the average number
of pulses every second.
Low/high speed operation
The low speed pulse setting is restricted to a maximum input frequency of 2 Hz with a
minimum pulse width of 70 ms. The high speed setting is designed for pulse frequencies up
to 32 kHz and requires a 10 s minimum pulse width. Use the low speed setting for
mechanical pulse generating devices such as relays and the high speed setting for all other
applications. The low speed setting prevents contact bounce from being recorded as
pulses.
Single ended/differential input
If the pulse signal is expected to be of negative polarity with respect to ground, set the
module to a different input. If the signal is to remain positive at all times, set it to single
ended.

2476_en_K

PHOENIX CONTACT

5-25

RAD-ISM-900-EN-BD
Diagnostic LEDs
There are four diagnostic LEDs on the digital pulse input module. See Figure 5-11 for the
meaning of each LED.

Figure 5-11

5-26

PHOENIX CONTACT

Description of RAD-IN-2CNT digital pulse input module LEDs

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.6.7

Digital pulse output module

The digital pulse output module accurately reproduces pulse counts or frequency outputs
from data contained in PLC registers. It is compatible with mechanical relays and electronic
pulse input devices. Upon power loss, the pulse output is set to 0 Hz.

Figure 5-12

RAD-OUT-2D-CNT digital pulse output module wire diagram

DIP switch settings


The DIP switch settings listed below are applicable for both channel 1 and channel 2. Refer
to Figure 5-12 for DIP switch configurations.
Counter/frequency mode
When counter mode is selected, the module will output a specific number of pulses as
determined by the PLC value written to it. If frequency mode is selected, the pulse output
module will generate pulses with a 50% duty cycle. In frequency mode, the low or high
speed switch setting is ignored.

2476_en_K

PHOENIX CONTACT

5-27

RAD-ISM-900-EN-BD
Low/high speed operation
This switch setting only impacts counter mode. If high speed is selected, the pulses will be
sent at a frequency of 10 kHz with a 50% duty cycle. If low speed is selected, the pulses will
be sent at a frequency of 10 Hz also with a 50% duty cycle.
Diagnostic LEDs
There are three diagnostic LEDs on the Digital Pulse Output Module. See Figure 5-13 for
the meaning of each LED.

Figure 5-13

5-28

PHOENIX CONTACT

Description of RAD-OUT-2D-CNT digital pulse output module LEDs

2476_en_K

Bus configuration for I/O modules (RAD-ISM-900-EN-BD-BUS only)

5.7

Accessing the XML file

To access the read-only XML file containing the status of the I/O modules, do the following:
1. Open a web browser and enter the IP address of the RAD-ISM-900-EN-BD-BUS with
connected I/O modules.
2. Log onto the wireless module using the appropriate password. Then click the link on the
left-hand menu to view the file. To access the file using a custom program, such as a
Microsoft Excel spreadsheet, enter the IP address of the module to be accessed in the
following format:
https://aaa.bbb.ccc.ddd/iodata.xml
Figure 5-14 is an example of how the data is displayed for two I/O modules with rotary
switch settings 5 and 6:

Figure 5-14

2476_en_K

Example of data display

PHOENIX CONTACT

5-29

RAD-ISM-900-EN-BD

5-30

PHOENIX CONTACT

2476_en_K

Section 6
This section informs you about
LED indicators and their meaning
connecting and measuring signal strength using the RSSI test port
diagnosis of various problems

Troubleshooting ..............................................................................................................................6-3

2476_en_K

6.1

LED indicators .................................................................................................... 6-4

6.2

RSSI (Received Signal Strength Indicator)......................................................... 6-5

6.3

General troubleshooting ..................................................................................... 6-6

6.4

Resetting the IP address .................................................................................... 6-7


6.4.1
DOS command .................................................................................... 6-7
6.4.2
Hardware reset .................................................................................... 6-7

PHOENIX CONTACT

6-1

RAD-ISM-900-EN-BD

6-2

PHOENIX CONTACT

2476_en_K

Troubleshooting

Troubleshooting
Troubleshooting a wireless network requires a logical process, stepping through the system
in order to isolate and solve the problem.
First, ensure that you have a wireless link (RF Link LED lit solid on all wireless devices in the
network).
Check the quality of the wireless signal using the RSSI voltage (see RSSI (Received Signal
Strength Indicator) on page 6-5) or the web server.
Check the web server of the wireless devices for error messages (see table 6.x).

Table 6-1
Error Message

Meaning

Wireless network
communication
channel overload

The wireless module is being overloaded


with data traffic, either on the LAN or serial
port, or by receiving too much traffic from
the wireless network to process.

Reduce the communication or polling rate


of the system.
Check for malfunctioning devices. Use
network filtering to prevent undesired data
from entering wireless network.
Check for high amounts of interference,
reduce the RF data rates and apply channel
blocking.

Network ID not
programmed

The Network ID field has an invalid setting


in the web server.

Ensure the Network ID is between 1


4095.

Internal storage failure


(HOP)

The internal frequency hopping sequence


is invalid.

Ensure the Hop Pattern ID displays a


number.
Reset the module to factory defaults and
reconfigure.

Invalid blocking
configuration

Channel blocking is incorrectly configured.

Confirm the channel blocking ranges are


correct (a lower frequency to a higher
frequency).
Reduce the amount of blocked channels to
a range supported by the RF data rate.

Internal storage failure


(PROD)

Factory calibration error.

Try restoring the module to factory defaults.

Received out of
sequence message

The wireless module received a packet


May be caused by interference or reflection
from the wireless network out of sequence. of the wireless signal. Adjust antennas and
verify suitable RSSI level.

Contact Phoenix Contact for RMA and


replacement.

Verify each module has a unique ID.


Verify the wireless modules are correctly configured and can communicate to each other by
disconnecting any other devices, connecting a PC to the master, and using a utility (such as
a DOS command prompt) to ping the IP addresses of the remote wireless devices.
If this test is not successful, it is possible that the configuration of the wireless module is
incorrect. If the test is successful, the problem is likely isolated to the devices connected to
the wireless network. To ensure the proper operation of those devices, connect them
together in an appropriate wired network and verify functionality.

2476_en_K

PHOENIX CONTACT

6-3

RAD-ISM-900-EN-BD
If the wireless connection and device operation are independently verified, yet the device
communication fails in the wireless network, contact Phoenix Contact Technical Support.

6.1

LED indicators

Figure 6-1 defines the LED indicator meanings for the RAD-ISM-900-EN-BD wireless
modules.

Power
RF Link
FLBL-2938-03R2

Transmit

Receive

3
6

4
5

7
8
9
RAD-ISM-900-EN-BD

Figure 6-1

LED locations

Table 6-2

LED Descriptions

No.

LED Name

LED Color

LED Status

Description

Status

Green

ON

Normal operation

Flashing slowly

Internal error

Flashing fast

Application error1

22

RS-485 RX

Green

Flashing

RS-422/485 data receive

RS-485 TX

Green

Flashing

RS-422/485 data transmit

42

RS-232 RX

Green

Flashing

RS-232 data receive

RS-232 TX

Green

Flashing

RS-232 data transmit

RF Link

Green

ON

RF link is established

RF Data

Green

Flashing

Data is being
transferred/received

WAN Speed

Green

ON

100Base-T connection

OFF

10Base-T connection

Flashing

Data is detected on Ethernet


port

6-4

PHOENIX CONTACT

WAN Link

Green

Typical application error is an invalid configuration

Not applicable for RAD-ISM-900-EN-BD/B

2476_en_K

Troubleshooting

6.2

RSSI (Received Signal Strength Indicator)

The RSSI test point allows measurement of the received wireless signal at each slave
module (see Figure 6-2). RSSI will not function on a master because there is no method of
determining which slave is connected. The RSSI is a voltage output, ranging from
0-3.5 V DC, and can be measured using a standard voltmeter.
The positive connection for the multimeter is made on the RSSI test point of the module and
the negative connection to the power supply ground. An adapter is available that will
connect to the RSSI connector to allow permanent monitoring of the RSSI voltage
(Order No. 0201744 for the test connector and Order No. 0201663 for the insulating
sleeve).

Common probe () to
terminal No. 2 (GND)
0 to 3.5 V DC
eive

Rec

it
sm
Tran
Link
RF
2
er -03R
Pow 2938
BLFL

-BD

-EN

00

D-IS
RA

M-9

Positive probe () to
RSSI connector
Figure 6-2

RSSI voltage strength check

-50

500 kbps

-55

250 kbps
-60

125 kbps

-65

dBm

-70
-75
-80
-85
-90
-95
-100
-105

1.50

Figure 6-3

2476_en_K

2.00

2.50

3.00

3.50

Volts
Signal strength to voltage comparison

PHOENIX CONTACT

6-5

RAD-ISM-900-EN-BD

6.3

General troubleshooting

Troubleshooting a wireless network requires a logical process, stepping through the system
in order to isolate and solve the problem.
The first step is to ensure there is a good wireless signal. Once a good signal is established,
check the wiring between the wireless module and external devices. After the wiring is
verified, adjust any configuration parameters.
The most practical method of troubleshooting a system is to place all of the components on
a table so that all wireless devices are within 3 m (10 ft.) of each other. This way there will
be a strong wireless signal, and programming each wireless module will not involve
traveling to a remote site. Refer to Table 7-1 to help identify various problems and possible
solutions.
Table 6-3

Troubleshooting procedures
PROBLEM

Unable to open web-based


management

SOLUTION
1.
2.

3.
4.

5.

No wireless link when modules


are within 3 m (10 ft.) of each
other.

1.

No wireless link (field installed)

1.

2.

2.
3.
4.
5.
6.

6-6

PHOENIX CONTACT

Ensure power is applied to wireless module.


Ensure cable is connected between PC and
module (WAN LINK LED will be on if cable is
connected).
Verify network settings of PC match network
settings of module.
The LAN Link and Duplex selection in the module
must match the settings of the connected, wired
network. Select Auto if in doubt.
Confirm IP address of wireless module. If IP
address is unknown, it can be set using a DOS
command. See Section 6.4, Resetting the IP
address.
Ensure one wireless module is programmed as a
master and the others as slaves.
Confirm security settings match in each module.
Check to ensure antennas are connected and
aimed properly.
Inspect antenna connections; they must be tight
and corrosion free.
Increase the mounting height of the antenna to
improve the line-of-sight.
Install larger gain antenna (and/or decrease
coaxial cable loss).
Check the power supply to ensure sufficient
current capacity.
Make sure the center pin of the antennas coaxial
cable is not shorted to ground.

2476_en_K

Troubleshooting
Table 6-3

Troubleshooting procedures
PROBLEM

Able to send data, but no


response from remote device

6.4

SOLUTION
1.

Verify network settings in remote device match


those of the wireless modules and LAN.
a) Each device must have a unique IP address in
the same network (e.g. 192.168.254.xxx).
b) The Subnet Mask must be the same in each
device.
c) The LAN Link and Duplex selection in the
module must match the settings of the
connected, wired network. Select Auto if in
doubt.
d) Ensure encryption settings match in all units.

Resetting the IP address

If the IP address is unknown, access to the wireless module can be restored by changing
the IP address using either a DOS command or a hardware reset.

6.4.1

DOS command

Click the Start Run buttons and type cmd in the open field. Click the OK button and
a DOS window opens. At the prompt, do the following steps.
1. Type arp -s (desired IP address) (MAC address of wireless module) in the DOS
window.
For example: arp -s 192.168.254.200 00-aa-00-62-c6-09
2. Click the Enter button.
3. Type ping -l 1040 (IP address) in the DOS window.
For example: ping -l 1040 192.168.254.200
The character in ping -l is a lower case L. If the IP address assignment is successful, a
reply message appears. To abort the ping, press the <Ctrl>+<C> keys.

6.4.2

Hardware reset

The hardware reset will restore the default IP address 192.168.254.254 as well as the
default user passwords admin for the Admin user and monitor for the Monitor user. To
initiate a hardware reset,
1. Disconnect power from the wireless module.
2. Insert a jumper across pins 2 and 3 on the DB-9 RS-232 port.
3. Reconnect power.
4. Once startup is complete, remove the jumper.

2476_en_K

PHOENIX CONTACT

6-7

RAD-ISM-900-EN-BD
RAD-ISM-900-EN-BD/B reset button
Without the RS-232 port, the RAD-ISM-900-EN-BD/B relies on a reset button accessed
through the venting slots in the bottom of the housing.

Screwdriver

Reset button

Figure 6-4
1.

RAD-ISM-900-EN-BD/B Reset button

Locate the reset button on the bottom of the wireless module within the second middle
vent.

NOTE:
Press the reset button gently. You should feel a soft click as it is pressed. If pressed too
hard, it can damage the connection to the circuit board or damage the circuit board itself.
2.
3.
4.

Use a flat screwdriver to press and hold the reset button for approximately 10 seconds
with the module powered on and fully booted.
After approximately 10 seconds, the status LED will flash once. Release the reset
button and allow the module to reboot.
Once rebooted, the module will return to the factory password defaults and an IP
address of 192.168.254.254.

For technical support, contact Phoenix Contact Technical Service. Please have the model
number of the module available.

6-8

PHOENIX CONTACT

2476_en_K

Section 7
This section informs you about
Ordering information
Technical data

Technical and ordering data............................................................................................................7-3

2476_en_K

7.1

Ordering data ..................................................................................................... 7-3


7.1.1
Products .............................................................................................. 7-3
7.1.2
Accessories ........................................................................................ 7-3

7.2

Technical data .................................................................................................... 7-4

PHOENIX CONTACT

7-1

RAD-ISM-900-EN-BD

7-2

PHOENIX CONTACT

2476_en_K

Technical and ordering data

Technical and ordering data


7.1
7.1.1

Ordering data
Products

Description

Type

Order No.

Wireless module, 900 MHz

RAD-ISM-900-EN-BD

2900016

Wireless module, 900 MHz includes bus connection

RAD-ISM-900-EN-BD-BUS

2900017

Wireless module, 900 MHz, without serial port

RAD-ISM-900-EN-BD/B

2901205

Description

Type

Order No.

Pcs.Pkt.

Module, 8-channel digital input

RAD-IN-8D

2867144

Module, 8-channel digital output with relays

RAD-OUT-8D-REL

2867157

Module, 4-channel analog input

RAD-IN-4A-I

2867115

Module, 4-channel analog output

RAD-OUT-4A-I

2867128

Module, 8-channel digital input and 2-channel analog output

RAD-IN+OUT-2D-1A-I

2867322

Module, pulse input

RAD-IN-2D-CNT

2885223

Module, pulse output

RAD-OUT-2D-CNT

2885236

Antenna, 0 dB gain, omnidirectional, 1.8 m (6 ft.) cable, MCX connector (male)

RAD-ISM-900-ANT-OMNI-0-6

2867160

Antenna, 3 dB gain, omnidirectional fiberglass, type N connector (female)

RAD-ISM-900-ANT-OMNI-FG-3-N

2867791

Antenna, 6 dB gain, omnidirectional fiberglass, type N connector (female)

RAD-ISM-900-ANT-OMNI-FG-6-N

2885579

Enclosure, NEMA 4X pre-wired, includes MINI-UPS, power distribution and


surge protection for 900 MHz wireless system

RAD-SYS-NEMA4X-900

2917188

7.1.2

Pcs.Pkt.

Accessories

Cable, 7.6 m (25 ft.) RG213 with type N connectors (male)

RAD-CAB-RG213-25

2867597

Surge protection, bulkhead mount for 900 MHz wireless module

CN-UB-280DC-BB-ASSY

5603859

Adapter cable, 1.2 m (4 ft.) RG316 with type N (male) and MCX (male)
connectors

RAD-CON-MCX90-N-SS

2885207

2476_en_K

PHOENIX CONTACT

7-3

RAD-ISM-900-EN-BD

7.2

Technical data

General data
Mounting

NS35 mounting rail (EN 60715)

Dimensions (W x H x D)

52 x 99 x 115 mm (2.1 x 3.90 x 4.5 in.)

Weight

296 g

Case material

Polyamide PA non-reinforced with aluminum heatsink

Operating temperature

-40 to 65C (-40 to 149F)

Storage temperature

-40 to 75C (-40 to 167F)

Relative humidity

10 95% non-condensing

Degree of protection

IP20

LED indicators

Status: solid indicates normal operation; flashing indicates error


RS-485TX: flashing indicates RS-422/485 data transmitting
RS-485RX: flashing indicates RS-422/485 data receiving
RS-232TX: flashing indicates RS-232 data transmitting
RS-232RX: flashing indicates RS-232 data receiving
RF LINK: solid when RF link is established; flashes with no wireless
connection
RF DATA: flashes when data is sent/received
WAN LINK: flashes when data is detected on Ethernet port
WAN SPEED: solid when 100Base-T connection exists

Power supply
Power

12 30 V DC, Class 2

Connection

Screw-type terminal, 12-24 AWG

Current consumption, maximum

250 mA @ 24 V DC

RF Link contact

0.5 A 30 V DC

Serial ports1
Port connections

RS-232; 9-pin D-sub female


RS-422/485; 4-pin pluggable screw terminal block

Baud rate (bps)

300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 54900, 115200

Not applicable for RAD-ISM-900-EN-BD/B

Ethernet
Port connection

RJ45

Ethernet transmission rate

10/100 Mbps

Wireless interface
Frequency

902-928 MHz

Transmit power

10 mW (10 dBm) 1 W (30 dBm); adjustable in 1-dBm increments

Antenna connector

MCX female

Receive sensitivity

500 kbps: -92 dBm


250 kbps: -98 dBm
125 kbps: -102 dBm

RSSI test point

0 3.5 V DC

7-4

PHOENIX CONTACT

2476_en_K

Technical and ordering data

Approval/conformance
FCC/IC

Part 15, Section 247

UL

Class I, Div. 2 Groups A, B, C, D

2476_en_K

PHOENIX CONTACT

7-5

RAD-ISM-900-EN-BD

7-6

PHOENIX CONTACT

2476_en_K

Technical appendix

A Technical appendix
A1
A 1.1

Structure of IP addresses
Valid IP parameters

IP parameters comprise the following three elements: IP address, subnet mask, and
default gateway/router.
Valid IP Addresses are:
000.000.000.001 to 126.255.255.255 and 128.000.000.000 to 223.255.255.255
Valid Subnet Masks are:
255.000.000.000 to 255.255.255.252
Default Gateway/Router:
The IP address of the gateway/router must be in the same subnetwork as the address of the
switch.

A2

Assigning IP addresses

bit 1

bit 32

The IP address is a 32-bit address. See Figure A-1. The IP address consists of a network
part and a user part. The network part consists of the network class and the network
address. There are currently five defined network classes (see Table A-1). Classes A, B,
and C are used in modern applications, while classes D and E are hardly ever used. It is
therefore usually sufficient if a network device only recognizes classes A, B, and C.

Figure A-1

Location of bits within the IP address

With binary representation of the IP address, the network class is represented by the first
bits. The key factor is the number of ones before the first zero. The assignment of classes
is shown in Table A-1. The empty cells in the table are not relevant to the network class and
are already used for the network address.
With binary representation of the IP address, the network class is represented by the first
bits. The key factor is the number of ones before the first zero. The assignment of classes
is shown in Table A-1. The empty cells in the table are not relevant to the network class and
are already used for the network address.

2476_en_K

PHOENIX CONTACT

A-1

RAD-ISM-900-EN-BD

Table A-1

Class assignments
Bit 1

Class A

Bit 2

Bit 3

Bit 4

Bit 5

Class B

Class C

Class D

Class E

The bits for the network class are followed by those for the network address and user
address. Depending on the network class, a different number of bits are available, both for
the network address (network ID) and the user address (host ID) (see Table A-2).
Table A-2

Network and User Class Bit assignments


Network ID

Class A

7 bits

Class B

14 bits

Class C

21 bits

Host ID

Class D

21-bit multicast identifier

Class E

27 bits

IP addresses can be represented in decimal or hexadecimal form. In decimal form, bytes


are separated by dots (dotted decimal notation) to show the logical grouping of the
individual bytes (see Figure A-2).
The decimal points do not divide the address into a network and user address. Only the
value of the first bits (before the first zero) specifies the network class and the number of
remaining bits in the address.
7 bits
Class A
0.0.0.0 - 127.255.255.255

24 bits

Network ID

Host ID
14 bits

Class B
128.0.0.0 - 191.255.255.255

16 bits

Network ID

Host ID

21 bits
Class C
192.0.0.0 - 233.255.255.255

8 bits

Network ID

Host ID
28 bits

Class D
224.0.0.0 - 239.255.255.255

Identifier for multicast group


27 bits

Class E
240.0.0.0 - 247.255.255.255
Figure A-2

A-2

PHOENIX CONTACT

Reserved for future applications

Structure of IP Addresses

2476_en_K

Assigning IP addresses

A 2.1

Special IP addresses for special applications

Certain IP addresses are reserved for special functions. The following addresses should not
be used as standard IP addresses.
127.x.x.x addresses
The class A network address 127 is reserved for a loopback function on all PCs,
regardless of the network class. This loopback function may only be used on networked
PCs for internal test purposes.
If a telegram is addressed to a PC with the value 127 in the first byte, the receiver
immediately sends the telegram back to the transmitter. In this way, it is possible to check,
for example, whether the TCP/IP software is correctly installed and configured.
As the first and second layers of the ISO/OSI reference model are not included in the test,
they should be tested separately using the ping function.

A 2.2

Value 255 in the byte

Value 255 is defined as a broadcast address. The telegram is sent to all the PCs that are in
the same part of the network. Examples: 004.255.255.255, 198.2.7.255 or
255.255.255.255 (all the PCs in all the networks). If the network is divided into subnetworks,
the subnet masks must be observed during calculation, otherwise some devices may be
omitted.
0.x.x.x addresses
Value 0 is the ID of the specific network. If the IP address starts with a zero, the receiver is
in the same network.
Example: 0.2.1.1 refers to device 2.1.1 in this network. The zero previously signified the
broadcast address. If older devices are used, unauthorized broadcast and complete
overload of the network (broadcast system) may occur when using the IP address 0.x.x.x.

A 2.3

Subnet masks

Routers and gateways divide large networks into several subnetworks. The subnet mask is
used to assign the IP addresses of individual devices to specific subnetworks. The network
part of an IP address is not modified by the subnet mask. An extended IP address is
generated from the user address and subnet mask. Because the masked subnetwork is
only recognized by the local PC, this extended IP address appears as a standard IP address
to all the other devices.
Structure of the subnet mask
The subnet mask always contains the same number of bits as an IP address. The subnet
mask has the same number of bits (in the same position) set to one, which is reflected in
the IP address for the network class.
Example: A Class A IP address contains a 1-byte network address and a 3-byte PC
address. Therefore, the first byte of the subnet mask may only contain 1s (ones). The
remaining bits (three bytes) then contain the address of the subnetwork and the PC. The
extended IP address is created when the bits of the IP address and the bits of the subnet
mask are ANDed. Because the subnetwork is only recognized by local devices, the
corresponding IP address appears as a normal IP address to all the other devices.

2476_en_K

PHOENIX CONTACT

A-3

RAD-ISM-900-EN-BD
Application
If ANDing the address bits gives the local network address and the local subnetwork
address, the device is located in the local network. If ANDing gives a different result, the
data telegram is sent to the subnetwork router. Figure A-3 shows an example of a Class B
subnet.
Decimal notation: 255.255.192.0
Binary notation: 1111 1111.1111 1111.1100 0000.0000 0000
Class B

Subnet Mask Bits

Using this subnet mask, the TCP/IP protocol software distinguished between devices
that are connected to the local subnetwork and devices that are located in other
subnetworks.
Example: Device 1 wants to establish a connection with device 2 using the above
subnet mask. Device 2 has an IP address of 59.EA.55.32. The IP address for
device 2 is displayed as follows:
Hexadecimal notation: 59.EA.55.3
Binary notation: 0101 1001.1110 1010.0101 0101.0011 00102
The individual subnet mask and the IP address for device 2 are then ANDed bit-bybit by the software to determine whether device 2 is located in the local subnetwork.
ANDing the subnet mast and IP address for device 2 is as follows:
Subnet mask:

1111 1111.1111 1111.1100 0000.0000 0000


AND

IP address:

0101 1001.1110 1010.0101 0101.0011 0010

Result after ANDing:

0101 1001.1110 1010.0100 0000.0000 0000

After ANDing, the software determines that the relevant subnetwork (01) does not
correspond to the local subnetwork (11) and forwards the data telegram to a
subnetwork router.
Figure A-3

A-4

PHOENIX CONTACT

Example for a Class B subnet mask

2476_en_K

Assigning IP addresses

A 2.4

Examples for subnet masks and computer bits

Table A-3

2476_en_K

Examples for subnet masks and computer bits

Subnet Mask

Computer/Host ID

255.255.255.252

2 Bits

255.255.255.248

3 Bits

255.255.255.240

4 Bits

255.255.255.224

5 Bits

255.255.255.192

6 Bits

255.255.255.128

7 Bits

255.255.2545.0

8 Bits

255.255.254.0

9 Bits

255.255.252.0

10 Bits

255.255.248.0

11 Bits

...

...

...

...

255.128.0.0

23 Bits

255.0.0.0

24 Bits

PHOENIX CONTACT

A-5

RAD-ISM-900-EN-BD

A-6

PHOENIX CONTACT

2476_en_K

B Appendices
B1

List of figures

Section 1
Figure 1-1:

Point to point, start and self-healing network configurations .............. 1-4

Figure 2-1:

Omni and directional antenna performance characteristics ............... 2-4

Figure 3-1:

Typical installation ............................................................................. 3-3

Figure 3-2:

Installation and removal from a mounting rail ..................................... 3-4

Figure 3-3:

Power connections for the RAD-ISM-900-EN-BD .......................... 3-6

Figure 3-4:

Wiring requirements ........................................................................... 3-7

Figure 3-5:

Port connections ................................................................................ 3-8

Figure 3-6:

RS-232 wire diagrams and pinouts .................................................... 3-9

Figure 3-7:

RS-422/485 2-wire and 4-wire connections ..................................... 3-10

Figure 3-8:

Antenna connection ......................................................................... 3-11

Figure 4-1:

Internet Protocol (TCP/IP) Properties dialog box ............................. 4-3

Figure 4-2:

Sign-in screen ................................................................................ 4-4

Figure 4-3:

Home screen showing device configuration .................................... 4-5

Figure 4-4:

General Device Information screen ................................................. 4-6

Figure 4-5:

General Configuration screen .......................................................... 4-8

Figure 4-6:

LAN - IP Configuration screen ......................................................... 4-9

Figure 4-7:

LAN-SNMP Configuration screen .................................................. 4-10

Figure 4-8:

LAN - Network Filter Configuration screen .................................... 4-12

Figure 4-9:

Radio - Settings screen ................................................................. 4-13

Figure 4-10:

Apply Radio Changes button ......................................................... 4-15

Figure 4-11:

Static AES security screen ............................................................... 4-16

Figure 4-12:

Frequency Blocking ......................................................................... 4-16

Figure 4-13:

Apply Radio Changes button ........................................................ 4-17

Figure 4-14:

Ethernet Ports Configuration screen .............................................. 4-18

Section 2

Section 3

Section 4

2476_en_K

PHOENIX CONTACT

B-1

RAD-ISM-900-EN-BD
Figure 4-15:

Serial Ports Configuration screen .................................................. 4-19

Figure 4-16:

Data Streaming Mode Configuration screen .................................. 4-20

Figure 4-17:

General Device Information screen ............................................... 4-21

Figure 4-18:

Local Diagnostics screen .............................................................. 4-22

Figure 4-19:

Configuration - Password Modification screen .............................. 4-24

Figure 4-20:

Configuration -Store Retrieve Settings screen ............................... 4-24

Figure 4-21:

LAN Performance screen .............................................................. 4-26

Figure 4-22:

Serial Performance screen ............................................................ 4-26

Figure 4-23:

Radio Statistics Performance screen ............................................ 4-27

Figure 4-24:

Software Updates screen .............................................................. 4-29

Figure 4-25:

Utilities screen ............................................................................... 4-29

Figure 4-26:

Reboot Device screen ................................................................... 4-30

Figure 4-27:

Radio Test screen ......................................................................... 4-30

Figure 4-28:

Monitoring - Web Access Log screen ............................................ 4-31

Figure 4-29:

Monitoring - Radio Status screen .................................................. 4-32

Figure 4-30:

Monitoring - Bridging Status screen .............................................. 4-33

Figure 5-1:

PLC Configuration menu ................................................................. 5-5

Figure 5-2:

Example of SNMP diagnostic error message .................................... 5-6

Figure 5-3:

Error message Multiple I/O communication control sources on same


channel .............................................................................................. 5-7

Figure 5-4:

I/O module 8-position rotary switch .................................................. 5-16

Figure 5-5:

RAD-IN-4A-I analog input module wire diagram .............................. 5-19

Figure 5-6:

RAD-IN-8D digital input module wire diagram .................................. 5-20

Figure 5-7:

RAD-OUT-4A-I analog output module wire diagram ........................ 5-21

Figure 5-8:

RAD-IN-OUT-8D-REL digital output module wire diagram .............. 5-22

Figure 5-9:

RAD-OUT-8D-REL digital output module wire diagram ................... 5-23

Figure 5-10:

RAD-IN-2D-CNT pulse input module wire diagram .......................... 5-24

Figure 5-11:

Description of RAD-IN-2CNT digital pulse input module LEDs ........ 5-26

Figure 5-12:

RAD-OUT-2D-CNT digital pulse output module wire diagram ......... 5-27

Figure 5-13:

Description of RAD-OUT-2D-CNT digital pulse output module LEDs ..528

Figure 5-14:

Example of data display ................................................................... 5-29

Figure 6-1:

LED locations ..................................................................................... 6-4

Section 5

Section 6

B-2

PHOENIX CONTACT

2476_en_K

List of figures
Figure 6-2:

RSSI voltage strength check .............................................................. 6-5

Figure 6-3:

Signal strength to voltage comparison ............................................... 6-5

Figure 6-4:

RAD-ISM-900-EN-BD/B Reset button ............................................... 6-8

Figure A-1:

Location of bits within the IP address ................................................ A-1

Figure A-2:

Structure of IP Addresses ................................................................. A-2

Figure A-3:

Example for a Class B subnet mask ................................................. A-4

Section 7
Appendix A

Appendix B

2476_en_K

PHOENIX CONTACT

B-3

RAD-ISM-900-EN-BD

B-4

PHOENIX CONTACT

2476_en_K

B2

List of tables

Section 1
Table 1-1:

RAD-ISM-900-EN-BD wireless module types ................................. 1-3

Table 2-1:

Cable types and signal loss at 916 MHz ............................................. 2-5

Table 4-1:

Default SNMP settings...................................................................... 4-11

Table 4-2:

Wireless module performance values............................................... 4-27

Table 5-1:

Modbus memory map......................................................................... 5-9

Table 5-2:

Modbus Pulse Memory Map ............................................................. 5-12

Table 6-1:

........................................................................................................... 6-3

Table 6-2:

LED Descriptions................................................................................ 6-4

Table 6-3:

Troubleshooting procedures............................................................... 6-6

Table A-1:

Class assignments ............................................................................ A-2

Table A-2:

Network and User Class Bit assignments .......................................... A-2

Table A-3:

Examples for subnet masks and computer bits ................................. A-5

Section 2

Section 3
Section 4

Section 5

Section 6

Section 7
Appendix A

Appendix B

2476_en_K

PHOENIX CONTACT

B-5

RAD-ISM-900-EN-BD

B-6

PHOENIX CONTACT

2476_en_K

B3

Explanation of terms

AES (Advanced
Encryption Standard)

A symmetric 128-bit block data encryption technique developed by Belgian cryptographers


Joan Daemen and Vincent Rijmen. The U.S. government adopted the algorithm as its
encryption technique in October 2000, replacing the DES encryption it used. AES works at
multiple network layers simultaneously.

AES-CCMP

AES-Counter Mode CBC-MAC Protocol (AES-CCMP) is the encryption algorithm used in


the 802.11i security protocol. It uses the AES block cipher, but restricts the key length to
128 bits. It incorporates two sophisticated cryptographic techniques (counter mode and
CBC-MAC), and adapts them to Ethernet frames to provide a robust security protocol
between the mobile client and the access point.

Bandwidth

The transmission capacity of a given device or network.

Bit

A binary digit.

Browser

An application program that provides a way to look at and interact with all the information on
the World Wide Web.

CTS (Clear To Send)

A signal sent by a wireless device, signifying that it is ready to receive data.

Default Gateway

A device that forwards Internet traffic from the local area network.

DHCP (Dynamic Host


Configuration Protocol)

A networking protocol that allows administrators to assign temporary IP addresses to


network computers by leasing an IP address to a user for a limited amount of time instead
of assigning permanent IP addresses.

DNS - (Domain Name


System [or Service or
Server])

An Internet service that translates domain names into IP addresses. Because domain
names are alphabetic, theyre easier to remember. The Internet, however, is really based on
IP addresses. Every time you use a domain name, a DNS service must translate the name
into the corresponding IP address. For example, the domain name www.example.com
might translate to 198.105.232.4. The DNS system is, in fact, its own network. If one DNS
server doesnt know how to translate a particular domain name, it asks another one, and so
on, until the correct IP address is returned.

Domain

A specific name for a network of computers.

DTIM (Delivery Traffic


Indication Message)

A message included in data packets that can increase wireless efficiency.

Dynamic IP Address

A temporary IP address assigned by a DHCP server.

Encryption

Encoding data transmitted in a network.

Ethernet

IEEE standard network protocol that specifies how data is placed on and retrieved from a
common transmission medium.

Firewall

A set of related programs located at a network gateway server that protects the resources
of a network from other networks.

Firmware

The programming code that runs a device.

2476_en_K

PHOENIX CONTACT

B-7

RAD-ISM-900-EN-BD
Fragmentation

Breaking a packet into smaller units when transmitting over a network medium that cannot
support the original size of the packet.

FTP (File Transfer


Protocol)

A protocol used to transfer files over a TCP/IP network.

Gateway

A device that interconnects networks with different, incompatible communications


protocols.

Half Duplex

Data transmission that can occur in two directions over a single line, but only one direction
at a time.

Hardware

The physical aspect of computers, telecommunications and other information technology


devices.

HTTP (HyperText
Transport Protocol)

The communications protocol used to connect to servers on the World Wide Web.

Infrastructure

A wireless network that is bridged to a wired network via an access point.

IP (Internet Protocol)

A protocol used to send data over a network.

IP Address

The address used to identify a computer or device on a network.

IPSec (Internet Protocol


Security)

A VPN protocol used to implement secure exchange of packets at the IP layer.

ISM band
(Industrial Scientific
Medical band).

A license-free portion of the spectrum open to all users.

LAN

The computers and networking products that make up a local area network.

MAC (Media Access


Control) Address

The unique address that a manufacturer assigns to each networking device.

Mbps (MegaBits Per


Second)

One million bits per second; a unit of measurement for data transmission.

Network

A series of computers or devices connected for the purpose of data sharing, storage, and/
or transmission between users.

Node

A network junction or connection point, typically a computer or work station.

Packet

A unit of data sent over a network.

Passphrase

Used much like a password, a passphrase simplifies the WEP encryption process by
automatically generating the WEP encryption keys.

Ping (Packet INternet


Groper)

An Internet utility used to determine whether a particular IP address is connected to the


network.

B-8

PHOENIX CONTACT

2476_en_K

Explanation of terms
Port

A 16-bit number (1-65535) used by TCP and UDP for application (services) identification on
a given computer. More than one application can be run at a host simultaneously
(e.g., internet server, mail client, FTP client, etc.). Each application is identified by a port
number. In other words, it is the identifier for a logical connector between an application
entity and the transport service.

PPPoE (Point-to-Point
Protocol over Ethernet)

A type of broadband connection that provides authentication (username and password) in


addition to data transport.

PPTP (Point-to-Point
Tunneling Protocol)

A VPN protocol that allows the Point-to-Point Protocol (PPP) to be tunneled through an IP
network. This protocol is also used as a type of broadband connection in Europe.

RADIUS (Remote
Authentication Dial-In
User Service)

An AAA (authentication, authorization and accounting) protocol for applications such as


network access or IP mobility. It is intended to work in both local and roaming situations. It is
a client/server protocol and software that enables remote access servers to communicate
with a central server to authenticate dial-in users and authorize their access to the requested
system or service. RADIUS allows a company to maintain user profiles in a central database
that all remote servers can share. It provides better security, allowing a company to set up a
policy that can be applied at a single administered network point. Having a central service also
means that its easier to track usage for billing and for keeping network statistics. RADIUS is
a de facto industry standard used by a number of network product companies and is a
proposed IETF standard. RADIUS was originally developed by Livingston Enterprises for their
PortMaster series of Network Access Servers, but later (1997) published as RFC 2058 and
RFC 2059 (current versions are RFC 2865 and RFC 2866). The DIAMETER protocol is the
planned replacement for RADIUS, but is still backwards compatible.

RTS Threshold

The number of bytes used for the RTS/CTS handshake boundary. When a packet size is
greater than the RTS threshold, the RTS/CTS handshake is performed.

Roaming

The ability to take a wireless device from one access points range to another without losing
the connection.

Router

A networking device that connects multiple networks together.

RTS (Request To Send)

A networking method of coordinating large packets through the RTS threshold setting.

Server

Any computer whose function in a network is to provide user access to files, printing,
communications and other services.

SPI (Stateful Packet


Inspection) Firewall

A technology that inspects every incoming packet of information before allowing it to enter
the network.

Spread Spectrum

A wide-band radio frequency technique used for more reliable and secure data
transmission.

SSID (Service Set


IDentifier)

A Service Set ID is a network ID unique to a network. Only clients and access points that
share the same SSID are able to communicate with each other.

Static IP Address

A fixed address assigned to a computer or device that is connected to a network.

Static Routing

Forwarding data in a network via a fixed path.

Subnet Mask

An address code that determines the size of the network.

2476_en_K

PHOENIX CONTACT

B-9

RAD-ISM-900-EN-BD
Switch

A device that connects computing devices. A LAN switch allows the grouping of network
devices to limit network traffic.

TCP (Transmission
Control Protocol)

A network protocol for transmitting data that requires acknowledgment from the recipient of
data sent.

TCP/IP (Transmission
Control Protocol/Internet
Protocol)

A set of instructions a computer uses to communicate over a network.

UDP (User Datagram


Protocol)

A network protocol for transmitting data that does not require acknowledgment from the
recipient of the data that is sent.

VPN (Virtual Private


Network)

A security measure to protect data as it leaves one network and goes to another over the
Internet.

WAN (Wide Area Network)

A network that provides communication services between devices in a geographic area


larger than that served by a local area network or a metropolitan area network. A WAN may
use or provide public communication facilities.

WINS - (Windows Internet


Naming Service)

A system that determines the IP address associated with a particular network computer
(name resolution). WINS supports network client and server computers running Windows
operating system and can provide name resolution for other computers with special
arrangements. Determining the IP address for a computer is a complex process when
DHCP servers assign IP addresses dynamically. For example, it is possible for DHCP to
assign a different IP address to a client each time the machine logs on to the network. INS
uses a distributed database that is automatically updated with the names of computers
currently available and the IP address assigned to each one. DNS is an alternative system
for name resolution suitable for network computers with fixed IP addresses.

B-10

PHOENIX CONTACT

2476_en_K