Weidmuller WI-GTWY-9, WI-GTWY-9-MD1 User Manual

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

User Manual

WI-GTWY-9-xxx Wireless Gateway

Weidmuller Inc., 821 Southlake Blvd., Richmond, VA 23236

Tel: [phone] Fax: [phone]

Web: www.weidmuller.com

1

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

Thank you for your selection of the WI-GTWY-9 module. We trust it will give

you many years of valuable service.

ATTENTION!

Incorrect termination of supply wires may

cause internal damage and will void warranty.

To ensure your WI-GTWY-9 enjoys a long life,

double check ALL your connections with

the user’s manual

before turning the power on.

Caution!

For continued protection against risk of fire, replace the module fuse F1 only with
the same type and rating.

CAUTION:

To comply with FCC RF Exposure requirements in section 1.1310 of the FCC Rules, antennas
used with this device must be installed to provide a separation distance of at least 20 cm from

all persons to satisfy RF exposure compliance.

DO NOT:

• operate the transmitter when someone is within 20 cm of the antenna

• operate the transmitter unless all RF connectors are secure and any open connectors are

properly terminated.

• operate the equipment near electrical blasting caps or in an explosive atmosphere

All equipment must be properly grounded for safe operations. All equipment should be serviced
only by a qualified technician.

2

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

FCC Notice: WI-I/O 9-x Wireless I/O Module

This user’s manual is for the WI-GTWY-9-xxx
radio telemetry module. This device complies with Part 15.247 of the FCC Rules.
Operation is subject to the following two conditions:

1) This device may not cause harmful interference and

2) This device must accept any interference received, including interference that may cause
undesired operation.

This device must be operated as supplied by Weidmuller, Inc. Any changes or modifications
made to the device without the written consent of Weidmuller, Inc. May void the user’s authority
to operate the device.

End user products that have this device embedded must be supplied with non-standard antenna
connectors, and antennas available from vendors specified by Weidmuller, Inc.. Please contact
for end user antenna and connector recommendations.

Notices: Safety

Exposure to RF energy is an important safety consideration. The FCC has adopted a safety
standard for human exposure to radio frequency electromagnetic energy emitted by FCC
regulated equipment as a result of its actions in Docket 93-62 and OET Bulletin 65 Edition 97-

01.

CAUTION:

To comply with FCC RF Exposure requirements in section 1.1310 of the FCC Rules, antennas
used with this device must be installed to provide a separation distance of at least 20 cm from all
persons to satisfy RF exposure compliance.

DO NOT:

• operate the transmitter when someone is within 20 cm of the antenna

• operate the transmitter unless all RF connectors are secure and any open connectors are

properly terminated.

• operate the equipment near electrical blasting caps or in an explosive atmosphere

All equipment must be properly grounded for safe operations. All equipment should be serviced
only by a qualified technician.

3

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

Limited Lifetime Warranty, Disclaimer and Limitation of Remedies

Weidmuller, Inc. products are warranted to be free from manufacturing defects for the
“serviceable lifetime” of the product. The “serviceable lifetime” is limited to the availability of
electronic components. If the serviceable life is reached in less than three years following the
original purchase from Weidmuller, Inc., Weidmuller, Inc. will replace the product with an
equivalent product if an equivalent product is available.

This warranty does not extend to:

- failures caused by the operation of the equipment outside the particular product's

specification, or

- use of the module not in accordance with this User Manual, or

- abuse, misuse, neglect or damage by external causes, or

- repairs, alterations, or modifications undertaken other than by an authorized Service Agent.

Weidmuller, Inc.’s liability under this warranty is limited to the replacement or repair of the
product. This warranty is in lieu of and exclusive of all other warranties. This warranty does not
indemnify the purchaser of products for any consequential claim for damages or loss of
operations or profits and Weidmuller, Inc. is not liable for any consequential damages or loss of
operations or profits resulting from the use of these products. Weidmuller, Inc. is not liable for
damages, losses, costs, injury or harm incurred as a consequence of any representations, warranties
or conditions made by Weidmuller, Inc. or its representatives or by any other party, except as
expressed solely in this document..

4

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

Important Notice

Weidmuller, Inc.’s products are designed to be used in industrial environments, by experienced
industrial engineering personnel with adequate knowledge of safety design considerations.

Weidmuller, Inc. radio products are used on unprotected license-free radio bands with radio noise
and interference. The products are designed to operate in the presence of noise and interference,
however in an extreme case, radio noise and interference could cause product operation delays or
operation failure. Like all industrial electronic products, Weidmuller, Inc.’s products can fail in
a variety of modes due to misuse, age, or malfunction. We recommend that users and designers
design systems using design techniques intended to prevent personal injury or damage during
product operation, and provide failure tolerant systems to prevent personal injury or damage in
the event of product failure. Designers must warn users of the equipment or systems if adequate
protection against failure has not been included in the system design. Designers must include
this Important Notice in operating procedures and system manuals.

These products should not be used in non-industrial applications, or life-support systems, without
consulting Weidmuller, Inc. first.

1. For WI-GTWY-9-xxx modules, a radio license is not required in most countries,
provided the module is installed using the aerial and equipment configuration described
in the WI-I/O 9-x Installation Guide. Check with your local WI-GTWY-9-xxx
distributor for further information on regulations.

2. For WI-GTWY-9-xxx modules, operation is authorized by the radio frequency regulatory
authority in your country on a non-protection basis. Although all care is taken in the
design of these units, there is no responsibility taken for sources of external interference.
The WI-I/O 9-x intelligent communications protocol aims to correct communication
errors due to interference and to retransmit the required output conditions regularly.
However some delay in the operation of outputs may occur during periods of interference.
Systems should be designed to be tolerant of these delays.

3. To avoid the risk of electrocution, the aerial, aerial cable, serial cables and all terminals of
the WI-GTWY-9-xxx module should be electrically protected. To provide maximum
surge and lightning protection, the module should be connected to a suitable earth and the
aerial, aerial cable, serial cables and the module should be installed as recommended in
the Installation Guide.

4. To avoid accidents during maintenance or adjustment of remotely controlled equipment,
all equipment should be first disconnected from the WI-I/O 9-x module during these
adjustments. Equipment should carry clear markings to indicate remote or automatic
operation. E.g. "This equipment is remotely controlled and may start without warning.
Isolate at the switchboard before attempting adjustments."

5. The WI-GTWY-9-xxx module is not suitable for use in explosive environments without

additional protection.

5

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

How to Use This Manual

To receive the maximum benefit from your WI-GTWY-9-xxx product, please read the
Introduction, Installation and Operation chapters of this manual thoroughly before using the
WI-GTWY-9-xxx.

Chapter Four Configuration explains how to configure the modules using the Configuration
Software available.

Chapter Six Troubleshooting will help if your system has problems.
The foldout sheet WI-GTWY-9-xxx Installation Guide is an installation drawing appropriate for

most applications.

CONTENTS

CHAPTER 1 INTRODUCTION 9

1.1 OVERVIEW 9

1.1.1 Modbus / DF1 WI-GTWY-9-MD1 10

1.1.2 Profibus WI-GTWY-9-PRx 11

1.1.3 Ethernet WI-GTWY-9-ET1 12

1.1.4 DeviceNet WI-GTWY-9-DE1 12

1.1.5 Modbus Plus WI-GTWY-9-M+1 13

1.2 THE WI-GTWY-9-XXX STRUCTURE 13

1.2.1 On-board I/O 14

1.3 THE WIRELESS NETWORK 15

1.3.1 WI-I/O 9-x to WI-GTWY-9-xxx Network 15

1.3.2 WI-GTWY-9-xxx to WI-GTWY-9-xxx Network 16

1.3.3 “Data Concentrator” Networks 17

1.3.4 WI-GTWY-9-xxx Repeaters 18

CHAPTER 2 OPERATION 19

2.1 START-UP 19

2.2 OPERATION 19

2.3 DATABASE 22

2.4 THE HOST - WI-GTWY-9-XXX LINK 24

2.4.1 Modbus / DF1 24

2.4.2 Profibus 24

2.4.3 Ethernet 24

2.5 RADIO SYSTEM DESIGN 25

2.5.1 Radio Signal Strength 25

2.5.2 Repeaters 26

2.6 RADIO COMMS FAILURE 26

2.6.1 Monitoring Communications Failure 27

2.7 SECURITY CONSIDERATIONS 27

CHAPTER 3 INSTALLATION 29

3.1 GENERAL 29

3.2 ANTENNA INSTALLATION 29

3.2.1 Dipole and Collinear antennas. 31

3.2.2 Yagi antennas. 32

6

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

3.3 POWER SUPPLY 32

3.3.1 AC Supply 33

3.3.2 DC Supply 33

3.3.3 Solar Supply 34

3.4 INPUT / OUTPUT 35

3.4.1 Digital Inputs / Outputs 35

3.5 SERIAL PORT 36

3.5.1 RS232 Serial Port 36

3.5.2 RS485 Serial Port 37

3.6 PROFIBUS PORT 38

3.7 ETHERNET PORT 39

3.8 MODBUS PLUS PORT 40

3.9 DEVICENET PORT 41

CHAPTER 4 CONFIGURATION 42

4.1 INTRODUCTION 42

4.2 CONFIGURATION PROGRAM 43

4.2.1 Program Operation 44

4.2.2 Security 47

4.3 UPLOADING AND DOWNLOADING 49

4.3.1 Loading from a WI-GTWY-9-xxx 50

4.4 MAPPINGS WI-GTWY-9-XXX TO WI-I/O 9-X I/O MODULES 51

4.4.1 Mappings from Inputs at Remote WI-I/O 9-x I/O Modules 51

4.4.2 Mappings from WI-GTWY-9-xxx to Outputs at Remote WI-I/O 9-x I/O Modules 52

4.4.3 Don’t Send if in Comm Fail 54

4.4.4 Startup Polls 55

4.4.5 Polls to Remote Modules 55

4.5 MAPPINGS FROM WI-GTWY-9-XXX TO OTHER WI-GTWY-9-XXX MODULES 55

4.5.1 Entering a Block Mapping 57

4.5.2 Host Device Trigger 58

4.5.3 Time Period 59

4.5.4 Real-Time 60

4.5.5 Change-of-State 62

4.5.6 Block Read Mappings 62

4.5.7 Mixing Normal Mappings and Block Mappings 63

4.5.8 Block mapping to Internal I/O registers 63

4.5.9 Comms Fail for Block Mappings 64

4.5.10 “Repeater-only” Configuration 64

4.6 CHANGE SENSITIVITY & I/O VALUE SCALING 65

4.6.1 Change Sensitivity 65

4.6.2 I/O Value Scaling 66

4.6.3 Unit Details 69

4.6.4 Number of TX only transmissions 69

4.6.5 Reset on Buffer Empty (Firmware version 1.83 and later) 69

4.7 SERIAL CONFIGURATION - MODBUS 70

4.7.1 MODBUS Slave 70

4.7.2 MODBUS Master 72

4.8 SERIAL CONFIGURATION - DF1 75

4.9 FIELDBUS CONFIGURATION 80

4.9.1 Fieldbus Mappings 81

4.10 FIELDBUS CONFIGURATION - PROFIBUS SLAVE 87

7

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

4.11 FIELDBUS CONFIGURATION - PROFIBUS MASTER 88

4.11.1 GSD File 88

4.11.2 Protocol and Supported Functions 88

4.11.3 Configuration 88

4.11.4 Configuration Example 96

4.11.5 Message Interface 99

4.11.6 DP Return Codes 119

4.12 FIELDBUS CONFIGURATION - ETHERNET 122

4.12.1 Setting IP Address 122

4.12.2 Modbus TCP 124

4.12.3 EtherNet/IP 127

4.13 FIELDBUS CONFIGURATION – DEVICENET 131

4.13.1 DeviceNet Introduction 131

4.13.2 DeviceNet Address Setting 131

4.13.3 EDS File 131

4.13.4 Protocol and Supported Functions 132

4.14 FIELDBUS CONFIGURATION – MODBUS PLUS 132

4.14.1 Modbus Plus Introduction 132

4.14.2 Modbus Plus Addressing 133

4.14.3 Protocol & Supported Functions 133

4.14.4 Configuration 134

4.15 CONNECTING WI-I/O-EX-1-S-1X SERIAL I/O 135

4.16 ACCESS TO MESSAGE BUFFER COUNT 137

CHAPTER 5 SPECIFICATIONS 138
CHAPTER 6 DIAGNOSTICS 141

6.1 DIAGNOSTICS CHART 141

6.2 DIAGNOSTICS MENU 141

6.3 ETHERNET DIAGNOSTICS 148

6.4 FIELDBUS INDICATING LEDS 150

6.4.1 Ethernet Indicating LED’s 150

6.4.2 Profibus Slave Indicating LED’s 151

6.4.3 Profibus Master Indicating LED’s 152

6.4.4 Modbus Indicating LED’s 153

6.4.5 DeviceNet Indicating LED’s 154

6.5 RADIO PATH TESTING 154

6.6 COMMS LOGGING 156

CHAPTER 7 WARRANTY 160
APPENDIX 1 STATUS REGISTERS 161
APPENDIX 2 IT FUNCTIONALITY 163

8

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

Chapter 1 INTRODUCTION

1.1 Overview

The Wireless Gateway products provide a wireless interface between various fieldbus protocols
used in process and automation applications. The WI-GTWY-9-xxx includes an integral
900MHz license-free radio transceiver, and
transfers transducer and control signals (I/O) using
a highly secure and highly reliable radio protocol.
The 105U-G units provide the same functionality as
the WI-GTWY-9-xxx, but with a fixed frequency
radio suitable for licensed frequencies in the 380 –
520 MHz radio band.

Functionality discussed in this manual for the
WI-GTWY-9-xxx range also applies to the 105U­G range.

The WI-I/O 9-x radio protocol is designed for very
efficient radio band usage, with event reporting
communications, automatic acknowledgment and
error-correction, peer to peer addressing, multiple
path routing, and frequency encoding and data
encryption for system security.

WI-GTWY

Profibus
Ethernet

Modbus
DF1
Internet

Profibus

WI-GTWY

WI-GTWY

WI-I/O 9

Direct I/O

WI-I/O 9

WI-GTWY

Direct I/O

Ethernet

Modbus

WI-GTWY

Profibus

WI-GTWY

WI-I/O 9

Direct I/O

Profibus

Profibus

Profibus

Ethernet

Application types include:

Modbus

• The WI-GTWY-9-xxx interfaces between WI-

WI-GTWY

I/O 9-x wireless I/O and various fieldbus
protocols. Connect wireless I/O to PLC’s, DCS,
SCADA or Internet.

Direct I/O

WI-I/O 9

• Wireless extension of factory automation buses such as Profibus.

• Wireless interconnectivity between different fieldbuses - Ethernet to Profibus to Modbus to

DF1.

9

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

• Combined networks of the above.

The WI-GTWY-9-xxx has eight on-board discrete I/O. Each I/O point can be configured
individually as a contact input signal, or a discrete output signal. Input signals can be sent via its
fieldbus connection to a host device (PLC, DCS etc) or be transmitted by radio to other WI-I/O
9-x units. The output signals can be driven by a host device, or linked to inputs on remote WI­I/O 9-x units.

This document assumes the reader is familiar with the operation of the WI-I/O 9-x I/O modules ­for further information, please refer to the User Manuals for these products.

Ordering information:

WI-GTWY-9-MD1 Modbus Master & Slave / DF1 interface
WI-GTWY-9-PR1 Profibus-DP Slave interface
WI-GTWY-9-PR2 Profibus-DP Master interface
WI-GTWY-9-ET1 Ethernet interface - Modbus TCP, Ethernet IP, FTP, HTML, Email
WI-GTWY-9-DE1 DeviceNet Slave interface
WI-GTWY-9-M+1 Modbus Plus Slave interface
The same ordering codes apply to the WI-GTWY-1 product range.

1.1.1 Modbus / DF1 WI-GTWY-9-MD1

The WI-GTWY-9-MD1 can be configured for Modbus master interface, Modbus slave, or DF1.
Modbus is a Master-Slave protocol originally developed by Modicon (now part of the Schneider

group). It became a popular interconnect protocol with many equipment manufacturers. One
Modbus master controls the Modbus network communications, which can comprise up to 250
Modbus slave devices. The Modbus master can read or write I/O values to/from Modbus slaves.
The WI-GTWY-9-MD1 can be configured as either Modbus Master or Modbus Slave. The
variation of Modbus supported by the WI-GTWY-9-MD1 is “Modbus RTU” (also known as
“Modbus binary”).

DF1 is an Allen-Bradley protocol (Allen-Bradley is now part of the Rockwell Automation
group). DF1 offers both full-duplex (point to point) and half-duplex (multidrop) operation. The
WI-GTWY-9-MD1 only supports the full-duplex operation - this is the default DF1 mode on
most equipment. DF1 full-duplex is a “peer-to-peer” protocol. Either DF1 device can initiate
commands to the other device, and both devices will respond to commands from the other
device.

The WI-GTWY-9-MD1 has two serial connections - RS232 and RS485, on the bottom end plate
of the module. The serial port provides both RS232 and RS485 hardware connections, however
both connections are paralleled internally - both connections cannot be used at the same time.
Either RS232 or RS485 can be used for Modbus communications, however only the RS232
port can be used for DF1. The serial port must be configured to suit the host device. Serial
data rates between 1200 and 19200 baud may be selected, and character types with 7 or 8 data
bits, even/odd/none parity, and 1 or 2 stop bits may be selected.

10

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

The Modbus/DF1 WI-GTWY-9-MD1 has 4300 general-purpose I/O registers. Each discrete,
analog and pulse I/O point takes up one register.

1.1.2 Profibus WI-GTWY-9-PRx

The Profibus WI-GTWY-9-PR1 provides Profibus-DP Slave functionality according to EN

50170. Profibus is a popular automation fieldbus that originated in Germany and is used

extensively by Siemens and other automation suppliers.
The Profibus connection on the WI-GTWY-9-PRx is optically isolated RS485 using an on-board

DC/DC converter. The Profibus port has automatic baudrate detection (9600 bit/s - 12 Mbit/s).
The Profibus Slave WI-GTWY-9-PR1 will connect to a Profibus LAN controlled by an external

master device. The Profibus Master WI-GTWY-9-PR2 will control communications on a
Profibus LAN, and can connect to up to 125 Profibus slave devices.

The Profibus WI-GTWY-9-PR2 I/O database has 4300 registers (each of 16 bit value), however
the Profibus interface limits the amount of I/O that can be transferred via the Profibus port.

Slave unit (PR1). The PR1 slave unit only supports 416 x 8 bit bytes of I/O. Of the 416 bytes of
I/O, there is a maximum 244 input bytes and maximum 244 output bytes - that is, if 244 input
bytes are used then only 172 output bytes can be used (416 – 244). Each byte can represent 8
discrete inputs or outputs, or an 8-bit value, or two bytes can represent a 16-bit value. That is,
analog or pulse I/O can be transferred as 8-bit registers (1 byte) or 16-bit registers (2 consecutive
bytes).

An “output” is a value coming into the WI-GTWY-9-PR1 via the fieldbus (that is, a value
written to the WI-GTWY-9-PR1 from the Profibus master). An input is a value going out from
the WI-GTWY-9-PR2 via the fieldbus (a value read by the Profibus master).

So a Profibus Slave WI-GTWY-9-PR1 could handle up to 1952 (244 x 8) discrete inputs or 244
low resolution analog inputs or 122 (244 x ½) high resolution analog inputs, or some
combination in between.

For example, a Profibus WI-GTWY-9-PR1 can handle 400 discrete inputs, 240 discrete outputs,
90 analog inputs and 60 analog outputs (assume analogs are 16-bit). The number of input bytes
is 230 (400/8 + 90*2). The number of output bytes is 150 (240/8 + 60*2). The total number of
I/O bytes is 380. If the number of analog outputs was increased to 90, then the total output bytes
would be 210 (240/8 + 90*2), and the total number of I/O bytes is 440 - this exceeds the
capacity of the Profibus interface.

Master unit (PR2). The Profibus master interface supports 2048 input bytes and 2048 output
bytes. Each byte can be 8 discrete inputs or outputs, but analog or pulse I/O take up 1 byte for
low resolution values (8-bit) or 2 bytes for high resolution values (16-bit).

So a Profibus Master WI-GTWY-9-PR2 can handle up to 4300 I/O total, but analog or pulse
inputs are limited to 2048 x 8-bit values or 1024 x 16-bit values. The same limit applies to
outputs.

For example, a Profibus Master WI-GTWY-9-PR2 can handle 2000 discrete inputs and 500
analog inputs (assume analogs are 16-bit). The number of input bytes is 1250 (2000/8 + 500*2).
The same unit could handle 4000 discrete outputs and 750 analog outputs. The number of output

11

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

bytes is 2000 (4000/8 + 750*2). The total number of I/O is 3250 which is less than the total limit
of 4300.

1.1.3 Ethernet WI-GTWY-9-ET1

The Ethernet WI-GTWY-9-ET1 provides several different types of Ethernet functionality:
♦ Modbus TCP. Modbus TCP uses Modbus as a base protocol within an Ethernet

communications structure. The WI-GTWY-9-xxx provides class 0, 1 and partially class 2
slave functionality.

♦ EtherNet IP. EtherNet IP is the version of Ethernet used by Allen-Bradley devices. The WI-

GTWY-9-ET1 provides level 2 I/O server CIP (ControlNet and DeviceNet).

♦ Internet functionality. The WI-GTWY-9-ET1 has 1.4Mbyte of non-volatile “flash” memory

for embedded web “pages” (dynamic HTTP), on-board file system, user downloadable web

pages through FTP server, and email functionality (SMTP).
The Ethernet connection is a transformer isolated RJ45 connector, 10/100 Mbit/sec.
The Ethernet WI-GTWY-9-ET1 I/O database has 4300 registers (each of 16 bit value), however

the Ethernet interface only supports 2048 input bytes and maximum 2048 output bytes. Each
byte can be 8 discrete inputs or outputs, but analog or pulse I/O take up 1 byte for low resolution
values (8-bit) or 2 bytes for high resolution values (16-bit).

An “output” is a value coming into the WI-GTWY-9-ET1 via the fieldbus. An input is a value
going out from the WI-GTWY-9-ET1 via the fieldbus.

So an Ethernet WI-GTWY-9-ET1 can handle up to 4300 I/O total, but analog or pulse inputs are
limited to 2048 x 8-bit values or 1024 x 16-bit values. The same limit applies to outputs.

For example, an Ethernet WI-GTWY-9-ET1 can handle 2000 discrete inputs and 500 analog
inputs (assume analogs are 16-bit). The number of input bytes is 1250 (2000/8 + 500*2). The
same unit could handle 4000 discrete outputs and 750 analog outputs. The number of output
bytes is 2000 (4000/8 + 750*2). The total number of I/O is 3250 which is less than the total limit
of 4300.

1.1.4 DeviceNet WI-GTWY-9-DE1

The DeviceNet WI-GTWY-9-DE1 provides DeviceNet 2.0 Slave functionality. DeviceNet is an
automation fieldbus developed by Allen-Bradley (Rockwell Automation).

The DeviceNet connection on the WI-GTWY-9-DE1 is optically isolated RS422 with selectable
baudrate between 125 and 500 Kbit/sec.

The WI-GTWY-9-DE1 I/O database has 4300 registers (each of 16 bit value), however the
DeviceNet interface only supports 512 x 8 bit input bytes and 512 x 8 bit output bytes, and this
limits the amount of I/O that can be transferred via the DeviceNet port.

Each byte can represent 8 discrete inputs or outputs, or an 8-bit value, or two bytes can represent
a 16-bit value. That is, analog or pulse I/O can be transferred as 8-bit registers (1 byte) or 16-bit
registers (2 consecutive bytes).

12







WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

An “output” is a value coming into the WI-GTWY-9-DE1 via the fieldbus (that is, a value
written to the WI-GTWY-9-DE1 from the DeviceNet master). An input is a value going out

from the WI-GTWY-9-DE1 via the fieldbus (a value read by the DeviceNet master).
So a DeviceNet WI-GTWY-9-DE1 can normally handle up to 4096 (512 x 8) discrete inputs or

512 low resolution analog inputs or 256 (512 x ½) high resolution analog inputs, or some
combination in between. It can also handle the same number of outputs; however the total I/O
count cannot exceed the WI-GTWY-9-DE1 database size of 4300.

1.1.5 Modbus Plus WI-GTWY-9-M+1

The Modbus Plus WI-GTWY-9-M+1 provides Modbus Plus Slave functionality. The Modbus
Plus connection on the WI-GTWY-9-M+1 is optically isolated RS485 with standard baudrate of
1 Mbit/sec.

The WI-GTWY-9-M+1 I/O database has 4300 registers (each of 16 bit value), however the
Modbus Plus interface only supports 1024 input registers and maximum 1024 output registers.
Each register can be 16 discrete inputs or outputs, or one analog or counter 16-bit value.

An “output” is a value coming into the WI-GTWY-9-M+1 via the fieldbus. An input is a value
going out from the WI-GTWY-9-M+1 via the fieldbus.

So an Modbus Plus WI-GTWY-9-M+1 can handle up to 4300 I/O total, but analog or pulse
inputs are limited to 1024 x 16-bit values. The same limit applies to outputs.

The Modbus Plus interface allows global data base transactions with routing for up to six
Modbus Plus networks.

1.2 The WI-GTWY-9-xxx Structure

The WI-GTWY-9-xxx has three functional sections:

• The Radio Interface consists of an

I/O database (or "Process Image")
that maintains the latest values of
all I/O in the wireless I/O system.
The I/O database comprises 4300 x
16 bit I/O registers and 4300 x 16
bit status registers. There are also
other registers in the database that
can be used for system
management - they are discussed
later in this manual. NOTE – the
terms ‘Radio Interface’ and ‘I/O
database’ are used interchangeably
throughout the manual.



   
     
  
 
    
   



     

WI-GTWY-9-xxx

   

     

 

    

      

          

   
    

   

   

     

• The radio port allows the WI-GTWY-9-xxx to communicate with other WI-GTWY-9-xxx

and/or WI-I/O 9-x modules using the WI-I/O 9-x protocol. Messages from the WI-I/O 9-x
modules are received by the radio port and used to update the input values in the WI-GTWY-

13

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

9-xxx Radio Interface. The radio port also creates the correct radio message to set outputs on
the remote WI-I/O 9-x modules.

The WI-I/O 9-x protocol is an extremely efficient protocol for radio communications. Radio
messages can be sent using exception reporting - that is, when there is a change of an input
signal - or by read/write messages. Each message can comprise a single I/O value, or multiple
I/O values (termed a “block” of I/O). There are also update messages, which are sent for
integrity purposes. Messages include error checking, with the destination address sending a
return acknowledgment. Up to five attempts are made to transmit the message if an
acknowledgment is not received. The WI-I/O 9-x protocol is designed to provide reliable
radio communications on an open license-free radio channel.

• The Fieldbus port enables communications between a host device, which could be a PLC,

DCS, HMI, intelligent transducer, etc), and the WI-GTWY-9-xxx Radio Interface database. A
“host device” may be one or several devices connected to the same fieldbus or network (for
example, an Ethernet LAN) - in this manual, the LAN is considered as a “host device”.

The fieldbus port decodes messages from the host device and reads or writes I/O values to the
database. The fieldbus port can also generate messages to the host device.

The WI-GTWY-9-xxx I/O database effectively isolates the fieldbus and the radio network. This
provides a high level of system performance. The WI-I/O 9-x radio protocol is very efficient and
reliable for radio communications. It minimizes radio channel usage by "change-of-state"
reporting, and allows the use of intermediate repeater addresses. It also allows peer-to-peer (WI­I/O 9-x to WI-I/O 9-x, WI-GTWY-9-xxx to WI-GTWY-9-xxx) and peer-to-master (WI-I/O 9-x
to WI-GTWY-9-xxx) communications. PLC protocols, by comparison, are designed to provide
transfer of large I/O files by "wire" link. The WI-GTWY-9-xxx retains the advantage of both
protocols in their respective communications media.

1.2.1 On-board I/O

The WI-GTWY-9-xxx has eight on-board discrete I/O. Each I/O point can be used as either a
discrete input (voltage free contact input) or discrete output (transistor output) - an I/O point
cannot be used as both input and output. Each I/O point is linked to two separate I/O registers in
the database - one for the “input” function and one for the “output” function.. If the output
register is set “on” by the fieldbus or by a radio message from a remote module, then the WI­GTWY-9-xxx will automatically set the input register for the same I/O point to “off”. This means
that the output register has priority over the input register - if there is a conflict, the input value is
ignored.

The WI-GTWY-9-xxx also has three internal inputs linked to I/O registers:

♦ Supply voltage status - if the normal supply fails, this status is set on.
♦ Low battery voltage. The WI-GTWY-9-xxx has an internal battery charger to trickle charge a

back-up battery. If the battery voltage is low, this status is set.
♦ Battery voltage - the actual value of the connected battery voltage.

1.2.2 I/O Expansion - WI-I/O-EX-1-S-xx modules

14

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

Where additional discrete or analog I/O is required, an external expansion I/O module can be
connected to the RS485 port of the WI-GTWY-9 module. See section 4.15 for more details on

this.
Note: Serial Expansion modules can only be used with the WI-GTWY-9-MD1 unit under

certain circumstances.

• WI-GTWY-9-MD1 is configured as “Repeater-only”

• WI-GTWY-9-MD1 is configured as a Modbus Master and WI-I/O-EX serial expansion

modules are used as Modbus Slaves.

WI-I/O 9

The WI-I/O-EX modules have the ability to be
configured to communicate the same way as a WI­I/O-9 module using the WIB-net Protocol or via as
a Modbus Slave communicating Modbus RTU

WI-GTWY

WI-I/O 9-K

protocol. They can be setup with an address range
of 1-99, which is selectable via the rotary switches
on end plate of the module.

WI-I/O 9

WI-I/O-9

1.3 The Wireless Network

The WI-GTWY-9-xxx can communicate with up to 490 other addresses - this could be 490 other
WI-I/O 9-x modules, or in the case of WI-I/O 9-K modules, it could be many thousands of
modules (as many WI-I/O 9-K modules can share the same address). WI-GTWY-9-xxx modules
may take up more than one address under some circumstances.

Any WI-GTWY-9-xxx or WI-I/O 9-x module can act as a radio repeater for other modules - that
is, radio messages can be passed onto other modules. Up to five repeater addresses can be
configured for messages transmitted to a WI-GTWY-9-xxx module.

Each module can have a unit address between 1 – 95, but the WI-GTWY-9-xxx also recognizes
repeater addresses in conjunction with the unit address as the module “identifier”. Hence module
#2 is recognized as different to #2 via #57 - #57 being a repeater.

1.3.1 WI-I/O 9-x to WI-GTWY-9-xxx Network

In the wireless I/O system, the WI-GTWY-9-xxx acts as a normal WI-I/O 9-x module (this
covers WI-I/O 9-x I/O, WI-I/O-EX-1-S-1x I/O, WI-I/O 9-x-K and WI-I/O 9-x-C modules).

WI-I/O 9-x modules transmit messages to the WI-GTWY-9-xxx address and the WI-GTWY-9­xxx acknowledges these messages like a normal WI-I/O 9-x module. When a WI-GTWY-9-xxx
transmits messages to change remote outputs, it will "re-try" if it does not receive an
acknowledgment, like a normal WI-I/O 9-x module.

Remote WI-I/O 9-x modules can connect to WI-I/O-EX-1-S-1x modules in the normal way. The
WI-GTWY-9-xxx host can access I/O on WI-I/O-EX-1-S-1x modules by using the intermediate
WI-I/O 9-x as a repeater.

15

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

WI-I/O 9-x modules can transmit input messages directly to outputs on other WI-I/O 9-x module,
as well as the WI-GTWY-9-xxx. The same input can be transmitted to different addresses by
entering two "mapping" configurations at the remote module.

Normal WI-I/O 9-x Messages

I/O registers in a WI-GTWY-9-xxx can be configured (mapped) to outputs at remote WI-I/O 9-x
modules, or I/O registers in WI-GTWY-9-xxx modules. The WI-GTWY-9-xxx will transmit an
I/O message when a “change-of-state” occurs for that I/O register. Registers have a configurable
“sensitivity” value - this determines how
much the register value has to change to

WI-I/O 9

trigger a change message. A change-of­state occurs when the register value has

PLC

PLC

changed by more than the sensitivity
value since the last transmission.

WI-GTWY

WI-GTW Y

The WI-GTWY-9-xxx also transmits
periodic update messages if there has
been no change - if an I/O register is

WI-I/O

mapped to a remote output or another
WI-GTWY-9-xxx, then that register can be configured with an update time.

WI-GTWY-9-xxx modules can transmit to WI-GTWY-9-xxx modules as well as other WI­GTWY-9-xxx modules. There can be multiple WI-GTWY-9-xxx modules in a network - as well
as WI-I/O 9-x I/O. Because the WI-I/O 9-x protocol is peer-to-peer, there are few constraints on
communications between multiple WI-I/O 9-x modules.

Poll Messages

A WI-GTWY-9-xxx can also generate poll messages to remote WI-I/O 9-x modules. These poll
messages act in the same way as a start-up poll - the remote module immediately responds with
update messages for any I/O mappings configured to the WI-GTWY-9-xxx.

Poll messages can be triggered by:

♦ time period, configurable 1 – 4096 sec (1.1 hour), or
♦ real time clock, or
♦ on demand by the host device, by writing to a “trigger register” in the WI-GTWY-9-xxx

1.3.2 WI-GTWY-9-xxx to WI-GTWY-9-xxx Network

Different types of WI-GTWY-9-xxx modules can communicate - for example, a Modbus WI­GTWY-9-xxx can communicate with an Ethernet WI-GTWY-9-xxx. I/O registers in one WI­GTWY-9-xxx can be transmitted to I/O registers in another WI-GTWY-9-xxx. When the WI­GTWY-9-xxx is configured, “mappings” can be entered linking I/O registers to registers in
another WI-GTWY-9-xxx.

As well as the normal “I/O change” messages and update messages, the WI-GTWY-9-xxx has
“block read” and “block write” messages for use with other WI-GTWY-9-xxx modules. These
messages will transmit multiple register values instead of only one as in the normal WI-I/O 9-x
message. The block read/write messages increase the efficiency of radio communications where a

16

WI-GTWY-9-xxx Wireless Gateway User Manual V1.18

WI-GTWY-9-xxx “sees” a large number of changes in its database at the one time. For

example, if a host writes a block of 100 signal values to a WI-GTWY-9-xxx, and 20 of these
values have changed since the last write-operation. If the block is mapped to another WI­GTWY-9-xxx, then the WI-GTWY-9-xxx can transmit all 20 values in one radio message,
instead of 20 messages.

Normal I/O messages can be repeated by any type of WI-I/O 9-x I/O module, however block
read/write messages can only be repeated by other WI-GTWY-9-xxx modules.

Block Read Message

A block read message is a request to another WI-GTWY-9-xxx to transmit the values of a
consecutive block of registers. The destination WI-GTWY-9-xxx will respond with the values,
which will be stored in a corresponding block of registers in the originating WI-GTWY-9-xxx.
A block read message can be triggered by:

♦ time period, configurable 1 – 4096 sec (1.1 hour), or
♦ real time clock, or
♦ on demand by the host device, by writing to a “trigger register” in the WI-GTWY-9-xxx.

Block Write Message

A block write message transmits a consecutive block of register values from one WI-GTWY-9­xxx to a destination WI-GTWY-9-xxx. It can be triggered by:

♦ time period, configurable 1 – 4096 sec (1.1 hour), or
♦ real time clock, or
♦ on demand by the host device, by writing to a “trigger register” in the WI-GTWY-9-xxx, or
♦ a change-of-state event occurring within the block of I/O registers.

If a block write message has been configured to be transmitted on change-of-state, a “time
window” is configured. When a change-of-state occurs in one of the registers in the block, the
time window will be activated. All changes during the time window will be grouped together
and transmitted as one block write message. That is, the block write message will not be sent
immediately the first change-of-state occurs (unless the time window is configured to zero), but
will be sent at the end of the time window - any other registers in the block that change during
the time window will be sent as part of the same message. The time window can be configured
from 0 – 255 seconds.

1.3.3 “Data Concentrator” Networks

WI-GTWY-9-xxx units can act as “data concentrator” units to collect I/O from a local network of
WI-I/O 9-x wireless I/O modules and pass the I/O on to another WI-GTWY-9-xxx as a block.

This type of network reduces the amount of radio traffic and is suitable for systems with a large
number of I/O modules. The system is divided into local sub-networks, each with a WI-GTWY­9-xxx unit. The WI-I/O 9-x modules transmit their I/O vlaues to the WI-GTWY-9-xxx. The WI­GTWY-9-xxx then transfers these values to the “central” WI-GTWY-9-xxx using a block
transfer which is very efficient compared to a lot of individual I/O transmissions.

17

WI-GTWY-9-xxx Wireless Gateway Introduction v1.18

The data concentrator network is different than using the WI-GTWY-9-xxx as a repeater. A
repeater re-transmits each message in the same format. A data concentrator collects the I/O
values as a block, and transmits the complete block in one transmission.

1.3.4 WI-GTWY-9-xxx Repeaters

Any WI-I/O 9-x module can repeat a normal radio message, however only WI-GTWY-9-xxx
modules can repeat a block message. WI-GTWY-9-xxx units connected to a host device can also
act as a repeater for other modules.

Where a WI-GTWY-9-xxx is being used without a host device as a repeater or data-concentrator,
it can be configured as “Repeater-only”. This allows the RS232/485 port to be used for on-line
diagnostics

NETWORK OF
WI-I/O 9-x
UNITS

WI-GTWY

WI-GTWY

TO HOST
DEVICE

NETWORK OF
WI-I/O 9-x
UNITS

WI-GTWY

18

WI-GTWY-9-xxx Wireless Gateway V1.18

Chapter 2 OPERATION

2.1 Start-up

The WI-GTWY-9-xxx operating software and the database configuration are stored in non­volatile memory; however the database I/O register values are lost on power failure (in the same
way as a PLC).

On start-up, the WI-GTWY-9-xxx sends "start-up poll" messages to remote modules based on
the source address of inputs configured in the database (the start-up messages can be disabled by
configuration). The remote modules respond with update messages for their inputs, which sets
initial values in the WI-GTWY-9-xxx I/O database registers. The WI-GTWY-9-xxx provides a
delay of 5 seconds between each start-up poll, to allow the remote module to respond and to
avoid overloading the radio channel.

If there are a lot of remote modules, then this start-up stage may take a significant time, and this
should be allowed for in the system design. The WI-GTWY-9-xxx has an internal battery
charger feature and the use of a back-up battery should be considered if this start-up delay
presents a constraint to system reliability. Start-up polls may be disabled for individual remote
modules in the database configuration.

For the host device, the WI-GTWY-9-xxx provides an "Active" signal on the RS232 port (DCD
pin 1). Its purpose is to indicate to the host that the WI-GTWY-9-xxx is now processing output
messages for the remote modules. When the WI-GTWY-9-xxx powers down (or should an
internal fault occur), the "Active" signal resets (turn “off” or “0”). When the WI-GTWY-9-xxx
starts-up, it holds the "Active" signal in a reset condition (“off” or “0”) for a time equal to the
number of remote addresses (or modules) configured times 5 seconds plus any delay if remote
addresses are offline. For example, if there are 20 remote addresses configured in the WI­GTWY-9-xxx database, then the “active” signal will be held in the reset state for 100 seconds
(20 x 5). During this period, the WI-GTWY-9-xxx will not change any output values in its
database. After this time, the WI-GTWY-9-xxx will set the "Active" signal (to “on” or “1”) - the
host can then send messages to the WI-GTWY-9-xxx to update the output values in the database.

2.2 Operation

The WI-GTWY-9-xxx database can hold values for 4300 I/O signals plus the 8 on-board I/O.
The database registers (also called I/O registers) can be accessed by both the radio port and the
fieldbus port. The host device can change values in the database via the fieldbus, and the WI­GTWY-9-xxx can transmit radio messages out with the new values. Radio messages can be
received with new values for database registers, and these new values can be written to the host
device or read by the host device, via the fieldbus.

The WI-GTWY-9-xxx operation must be configured before the WI-GTWY-9-xxx will function.
Configuration is achieved by creating a configuration file on a PC and downloading this file to
the WI-GTWY-9-xxx. The WI-GTWY-9-xxx configuration may also be "uploaded" to a PC for

19

WI-GTWY-9-xxx Wireless Gateway V1.18

#1

viewing and modification. For more information, refer to the Configuration section of this
document.

Each I/O register in the WI-GTWY-9-xxx database has a 16-bit value. It doesn’t matter if the
remote I/O is digital (discrete), analog or pulse. The host protocol driver in the WI-GTWY-9­xxx will convert the 16 bit value into a value that the host will understand. For example, if the
host device requests a binary/digital read command, the WI-GTWY-9-xxx will convert the 16 bit
value into a binary (1 bit) value before it responds.

The WI-GTWY-9-xxx is able to scale the I/O value between the I/O database and the host device

- this is a user-configurable function.

#14

DIN1

WI-I/O 9-x-1

WI-GTWY-9

An example of normal operation - assume that a remote module has address 14 and the WI­GTWY-9-xxx is address 1. Module #14 is configured with a mapping DI1 → I/O Reg 76 at #1.
When DI1 turns "on", module #14 transmits a message. If the WI-GTWY-9-xxx can hear this
message, it will transmit an acknowledgment back to module #14, and updates the value of I/O
register 76 in the WI-GTWY-9-xxx database. The host device can read I/O register 76 via the
data-bus, or the WI-GTWY-9-xxx may write the value of I/O register 76 to the host device.

I/O registers that receive values from other WI-I/O 9-x or G modules via radio are configured
with a “Communications fail time”. If the WI-GTWY-9-xxx does not receive a message for this
I/O register within the comms-fail time, then the I/O register is given a “comms fail” status
which the host device can read. The I/O value can also be configured to reset to zero on comms­fail.

I/O registers that transmit out to other WI-I/O 9-x or WI-GTWY-9xxx modules are configured
with an “update time” and a “sensitivity”. The WI-GTWY-9-xxx will transmit a message to the
configured remote output whenever the I/O register value changes by the sensitivity amount – if
it has not changed within the update time, the WI-GTWY-9-xxx will send a message anyway.
The WI-GTWY-9-xxx will make five attempts to send a message - if it does not receive an
acknowledgment from the remote module, then the I/O register is given a “comms fail” status
which the host device can read.

Each I/O register has an associated “status” register, which includes information such as comms­fail status. As well as each I/O register having an individual comms-fail status, each remote
module has an overall comms fail status. This status is “set” (on) whenever a comms-fail occurs
for an individual I/O register, and is “reset” (off) whenever a message is received from the
remote module. The WI-GTWY-9-xxx can be configured to not send any update messages to a
remote module if it senses that the remote module is in “comms fail” - that is, if any I/O register
associated with the remote module is in “comms fail”. It will start sending update messages

20

WI-GTWY-9-xxx Wireless Gateway V1.18

again when the WI-GTWY-9-xxx receives a message from the remote module. The default

configuration is that output updates ARE sent during comms fail conditions.

21

WI-GTWY-9-xxx Wireless Gateway V1.18

2.3 Database

The WI-GTWY-9-xxx database (Radio Interface) has 10 000 registers, each of 16 bit size. The
structure of the database is:

Registers Purpose

0 - 4299 I/O registers
4300 - 4399 On-board I/O
4401 - 4499 Comms-fail status and radio strengths for remote modules
5000 - 9499 Status registers - 16 bit status for each I/O signal
9500 - 9999 Status registers for block read/write messages

The register numbers may be used by the Host Protocol Driver to access I/O values and I/O status
information. Each configured I/O point has a 16 bit value (in registers 0000 - 4299), and a 16 bit
status value. The status register is located at 5000 plus the I/O value register. For example, an
I/O point in register number 2560 has a status value in register number 7560 (5000 + 2560).

Details of the status register are provided in Appendix A. The most important part of the status
register is the 15th or most significant bit - this indicates comm-fail status for the I/O register. If
the most significant bit is set, then the I/O register is in comms-fail.

The host device can read the status registers. For example, the communications status of an
output configured at register number 3001 can be examined by reading register number 8001
(5000 + 3001). If the register value is greater than 32767, then the 15th bit is set, indicating that
the output has a communications failure.

2.3.1 On-board I/O and Internal I/O

The WI-GTWY-9-xxx has eight discrete I/O points. These may be used as inputs or as outputs.
Inputs are linked to registers 4300-4307. That is, if a contact connected to DIO1 is “on”, then
register 4300 is given an “on” value. The inverse of the input values are stored in registers 4370-

4377.
Outputs are controlled from registers 4320-4327; that is, if register 4327 is set to an “on” value,

then output DIO8 is activated.
Whenever an output register is set “on”, the corresponding input register is automatically set

“off”. For example, if register 4321 is set to “1”, the WI-GTWY-9-xxx will also set 4301 to “0”.
This means that if both the input and output registers corresponding to the same I/O point are
used in the configuration, then the output register has priority.

Outputs may be written to by either the host device or by a remote WI-I/O 9-x via the radio port.
Input values can be sent to the host device or to a remote module via the radio port.

22

WI-GTWY-9-xxx Wireless Gateway V1.18

The WI-GTWY-9-xxx also monitors its battery voltage and supply voltage. These are stored in
registers 4310 and 4311 respectively, as 16 bit values, scaled so that a value of 16384 decimal

(hex 4000) corresponds to 8 V, and a value of 49152 (hex C000) corresponds to 40V.
A low battery alarm is available at register 4308. This becomes active when the battery voltage

falls below 11.3V, and clears when the battery voltage rises above 11.8V. Supply voltage is also
monitored, and an alarm is available at register 4309. This becomes active if the supply voltage
falls below 8.0V, and clears when the supply voltage rises above 9.0V.

I/O Register Description I/O Register Description

4300 Input value DIO 1 4320 Output value DIO 1
4301 Input value DIO 2 4321 Output value DIO 2
4302 Input value DIO 3 4322 Output value DIO 3
4303 Input value DIO 4 4323 Output value DIO 4
4304 Input value DIO 5 4324 Output value DIO 5
4305 Input value DIO 6 4325 Output value DIO 6
4306 Input value DIO 7 4326 Output value DIO 7
4307 Input value DIO 8 4327 Output value DIO 8
4308 Low battery voltage status
4309 Supply voltage fail status
4310 Battery voltage value
4311 Supply voltage value
4370 - 4379 Inverse values of

4300 - 4309

23

WI-GTWY-9-xxx Wireless Gateway V1.18

“HOST DEVICE”

2.4 The Host - WI-GTWY-9-xxx Link

For the host device, the WI-GTWY-9-xxx "looks" like a single device (or a "virtual PLC"),
containing the I/O for the complete
wireless I/O system.

2.4.1 Modbus / DF1

The user selects whether the WI-

DATA-BUS

DATABASE

I/O

"VIRTUAL PLC"

GTWY-9-MD1 should act as a
Modbus Master or Modbus Slave or
DF1 device.

The data type and baud rate of the serial communications must be configured at the WI-GTWY­9-xxx to match the host. Data types can be 7 or 8 bit, even/odd/no parity, with 1 or 2 stop bits.
Data rates can be 300 - 19200 baud.

The full WI-GTWY-9-xxx database (4300 registers) can be accessed by the Host Device.

2.4.2 Profibus

The Profibus port has auto-detect of baud rate from 9600 bits/sec to 12Mbit/sec - no
configuration is required.

The Profibus units have internal hardware comprising the Profibus Interface. The Profibus
Interface handles all Profibus DP Network communications. The internal Radio Interface is
separate to the Profibus Interface, and handles all radio communications. I/O in the Radio
Interface is linked to I/O in the Profibus Interface in a flexible way via WI Series Configuration
Software.

The Profibus Slave interface provides a total of 416 I/O bytes, with a maximum 244 input bytes
and maximum 244 output bytes. A Profibus byte can contain 8 discrete (binary) values, or two
bytes can be used for a 16-bit analogue or pulse register. So the Profibus interface is limited to
1952 discrete inputs or 122 analogue inputs or a combination. The same applies for outputs.

For example, a Profibus host wants to read 800 discrete inputs (100 bytes) and write 400 discrete
outputs (50 bytes). This will take up 150 bytes of the Profibus Interface, leaving 266 left. The
remaining bytes could be used for 133 analogue I/O - up to 72 analogue inputs (244 – 100
discrete input bytes) plus 61 analogue outputs - or vice-versa.

The Profibus Master interface provides a total of 2048 input bytes and 2048 output bytes. A
byte can contain 8 discrete (binary) values, or two bytes can be used for a 16-bit analogue or
pulse register. So the interface is limited to 4300 discrete inputs (the limit of the WI-GTWY-9­xxx database) or 1024 analogue inputs (the limit of the HMS interface) or a combination. The
same applies for outputs.

2.4.3 Ethernet

The Ethernet port automatically handles Ethernet communications at 10 or 100 Mbit/sec. An IP
address is entered so that other Ethernet devices can recognize the WI-GTWY-9-xxx.

The Ethernet units have internal hardware comprising the Ethernet Interface. The Ethernet
Interface handles all Ethernet Network communications. The internal Radio Interface is separate

24

WI-GTWY-9-xxx Wireless Gateway V1.18

to the Ethernet Interface, and handles all radio communications. I/O in the Radio Interface is
linked to I/O in the Ethernet Interface in a flexible way via WI Series Configuration Software.

The Ethernet Interface provides a total of 2048 input bytes and 2048 output bytes. An Ethernet
byte can contain 8 discrete (binary) values, or two bytes can be used for a 16-bit analog or pulse
register. So the Ethernet Interface is limited to 4300 discrete inputs (the limit of the WI-GTWY­9-xxx database) or 1024 analog inputs (the limit of the Ethernet interface) or a combination. The
same applies for outputs.

For example, an Ethernet host wants to read 500 analog inputs (1000 bytes). The remaining
input bytes (1548) could be used for 12,384 discrete inputs - but the WI-GTWY-9-xxx database
is not this big. Provided there are no outputs required, there could be 3800 discrete inputs (4300
– 500 analogs). If there are outputs required, then the number of discrete inputs available will be
further limited.

2.5 Radio System Design

Each wireless I/O system can have up to 95 unit addresses, although up to 255 WI-I/O 9-K
module can share the same unit address (refer to WI-I/O 9-K User Manual).

Each WI-I/O 9-x module can have up to 31 x WI-I/O-EX-1-S-1x modules connected to it. These
modules are addressed 96 - 127. More than one WI-I/O-EX-1-S-1x module can have the same
address, provided they are not connected to the same WI-I/O 9-x module - that is, #100 via #16
is identified as a different module to #100 via #65.

A constraint that needs to be considered is the capacity of the radio channel. If there is too much
traffic on the radio channel, then the system quickly becomes unreliable. The recommended
maximum average traffic density is 100 messages per minute provided all radio paths are
reliable. If there are marginal radio paths, resulting in re-tries of transmitted messages, then the
maximum traffic density is reduced considerably. Each block read/write messages should be
counted as two messages because of the length of these messages.

A WI-GTWY-9-xxx can be used as a repeater module for messages between other modules.

2.5.1 Radio Signal Strength

The WI-GTWY-9-xxx records the radio signal strength of remote modules that communicate
directly (that is, not via repeaters). There are 95 database registers (4401 – 4495) which store the
radio strengths – corresponding to remote addresses #1 - #95. The radio strength (RSSI) is
measured in dBm (relative to 1mW of RF power). The RSSI value is stored in the 8 least
significant bits of each register - a value of –84 dBm would be stored as decimal 84.

These database registers will hold the strength of the last message received from the address. If a
message is received from a remote module via a repeater, then the measurement is recorded in
the address of the last repeater. For example, if a message is received from #24 directly, then the
RSSI will be recorded in register 4424. If a message is received from #24 via #25, then the RSSI
is recorded in register 4425. The WI-GTWY-9-xxx will not know what the radio strength of the
message from #24 to #25 is. If #25 is another WI-GTWY-9-xxx, then it can record this RSSI
and this register could be mapped to an I/O register in the first WI-GTWY-9-xxx.

25

WI-GTWY-9-xxx Wireless Gateway V1.18

The RSSI registers can be read by the host device, or mapped to I/O registers in other WI­GTWY-9-xxx modules.

The first half of the register (8 most significant bits) will be decimal 0 (hex 00) if the remote
module has active communications. If a comms fail status to this address occurs, the most
significant bit will be set. For example, if the last message received from #38 is –99dBm, then
the 16 bit value of register 4438 will be decimal 99 or hex 0063. If the “comms fail” status for
#38 is set, the 16 bit value of register 4438 will become decimal 32,867 (32768 + 99) or hex

8063.

2.5.2 Repeaters

Radio paths may be extended by using intermediate modules as repeaters. A repeater will
receive and re-transmit the radio message. Up to five repeater addresses can be configured -
that is, a radio message can pass through five intermediate modules. For normal I/O messages,
any WI-I/O 9-x module (except WI-I/O 9-x-K modules) can be used as a repeater, however for
block read/write messages, only WI-GTWY-9-xxx modules can act as repeaters.

2.6 Radio Comms Failure

The WI-GTWY-9-xxx has an internal "communications failure" (comms fail) status for each I/O
point in its database. There is also a comms fail status for each module with direct
communications - see 2.5.1 above.

For I/O registers which are mapped to a remote output or another WI-GTWY-9-xxx, the comms
fail status is set if the WI-GTWY-9-xxx does not receive an acknowledgment for a message
being sent to that remote output. The comms fail status resets when a successful transmission
occurs.

For I/O registers which have been mapped , from a remote input or another WI-GTWY-9-xxx, a
comms fail time period may be configured. If a radio message for this I/O register has not been
received within this time, then this registers comms fail status is set. The comms fail status will
reset when a message is received for this register. If the comms fail time is configured as zero,
then the comms fail status will never be activated. Registers can be configured to reset (go back
to a value of zero) on comms fail.

The communications failure status is bit 15 of the status register for each I/O point. If the host
device reads a register as a digital or binary value, then the WI-GTWY-9-xxx returns bit 15 of
the register (0 or 1) - this is the comms fail bit of a status register.

It is important to use the comms fail status in the overall system design, as any system can fail.
The WI-GTWY-9-xxx also provides an additional comms failure feature to stop the WI-GTWY-

9-xxx transmitting output messages to an individual remote address if the WI-GTWY-9-xxx
already knows that this remote address is in communication failure. This prevents the WI­GTWY-9-xxx from congesting the radio channel with a lot of unnecessary transmissions (and re­transmissions). This function is called "Don’t Send if In Comm Fail" and is configurable by the
user for each individual remote address. The WI-GTWY-9-xxx retains a "remote address comms
fail" status for the remote addresses configured for this function. If any output with this remote

26

WI-GTWY-9-xxx Wireless Gateway V1.18

address goes into communications failure, then the remote address comms fail status is set ("on"

or 1) - every time an input with this remote address receives a radio message, then the remote
address comms fail status is reset ("off" or 0). While the remote address comms fail status is set,
the WI-GTWY-9-xxx disables any output messages being sent to this remote address.

When this feature is configured, all output transmissions are stopped if communications with a
remote module fails for a short period. They will start again when an input message from this
module is received. If the WI-GTWY-9-xxx determines that a output message should be sent to
an output which is disabled because of this feature, then the output message will not be sent and
the comms fail status of that output is set ("on" or 1).

If it is desired to use this function with a remote WI-I/O 9-x module, but there are no inputs from
this module being used, then it is easy to configure an unused input or an internal input (mains
fail or low battery voltage etc). It is the comms fail status for the input, which is used, not the
input itself.

2.6.1 Monitoring Communications Failure

The host device can monitor the communications status of an I/O point by reading the status
register for this point as a binary/discrete register. Modbus, and many other protocols, will
convert a 16 bit register value to a binary/discrete value by returning the most significant bit -
for the status register, this corresponds to the comms status bit.

For example, to monitor the comms status of I/O register 1045, perform a binary/discrete read on
register 6045 (the status register for 1045). A value of “1” will be returned if this I/O point is in
comms fail, and a “0” returned if the status is normal.

If it is desired to monitor the comms status of all I/O points, it is more efficient to only monitor
the comms status of one I/O point at each remote module (if this point is in comms fail, then all
points at the remote module will be in comms fail). If this point is an input, then the comms fail
time for this input can be made short, to give an early warning of a comms problem (this means
that the corresponding update time for the input at the WI-I/O 9-x will need to be short). If the
point is an output, then the update time for the output should be made short.

2.7 Security Considerations

There are three dimensions of security considerations:

1. Failure to operate when required - or “operational reliability”.

The features discussed above optimize operating reliability. Using an acknowledgment and
re-try protocol ensures that the transmitting module is aware whether the transmitted message
has been transmitted reliably. The “comms fail” alarms provide indication if the radio link
has failed to operate.

2. Mal-operation, or operating when not requested.

This problem occurs when an output is “triggered” by the wrong radio device. The WI­GTWY-9-xxx modules use frequency encoding and a very secure addressing system to

27

WI-GTWY-9-xxx Wireless Gateway V1.18

ensure this does not occur. An additional security level using data encryption can also be
selected.

3. Malicious operation, or “hacking”

This is the problem most associated with security concerns - the ability for someone to
access information from a radio system by “listening-in”, or to cause damage by transmitting
radio messages to force outputs.

A security option can be selected during the module configuration to protect against this. The
security option (if selected) adds data encryption to radio messages. Modules in the same
system are automatically configured with the encryption key, such that only these modules
can understand each other. “Foreign” modules will hear the messages, but cannot decrypt the
messages. For more information, refer to section 4.2.2.

28

WI-GTWY-9-xxx Wireless Gateway V1.18

Chapter 3 INSTALLATION

3.1 General

The WI-GTWY-9-xxx module is housed in a rugged aluminum case, suitable for DIN-rail
mounting. Terminals will accept wires up to 12 gauge (2.5 sqmm) in size.

All connections to the module must be low voltage (SELV). Normal 110-240V mains supply
should not be connected to any terminal of the WI-GTWY-9-xxx module. Refer to Section

3.3 Power Supply.
Before installing a new system, it is preferable to bench test the complete system. Configuration

problems are easier to recognize when the system units are adjacent. Following installation, the
most common problem is poor communications caused by incorrectly installed aerials, or radio
interference on the same channel, or the radio path being inadequate. If the radio path is a
problem (i.e. path too long, or obstructions in the way), then higher performance aerials or a
higher mounting point for the aerial may rectify the problem. Alternately, use an intermediate
WI-I/O 9-x Module as a repeater.

The foldout sheet WI-GTWY-9-xxx Installation Guide provides an installation drawing
appropriate to most applications. Further information is detailed below.

Each WI-GTWY-9-xxx module should be effectively earthed/grounded via the "GND" terminal
on the WI-I/O 9-x module - this is to ensure that the surge protection circuits inside the module
are effective.

3.2 Antenna Installation

The WI-GTWY-9-xxx and WI-I/O 9-x modules will operate reliably over large distances. The
distance which may be reliably achieved will vary with each application - depending on the type
and location of antennas, the degree of radio interference, and obstructions (such as hills or trees)
to the radio path. Typical reliable distances are :

USA/Canada 15 miles 6dB net gain antenna configuration permitted (4W ERP)
Australia/NZ 12 km unity gain antenna configuration (1W ERP)

Longer distances can be achieved if one antenna is mounted on top of a hill.
To achieve the maximum transmission distance, the antennas should be raised above

intermediate obstructions so the radio path is true “line of sight”. Because of the curvature of the
earth, the antennas will need to be elevated at least 15 feet (5 metres) above ground for paths
greater than 3 miles (5 km). The modules will operate reliably with some obstruction of the
radio path, although the reliable distance will be reduced. Obstructions that are close to either
antenna will have more of a blocking effect than obstructions in the middle of the radio path. For
example, a group of trees around the antenna is a larger obstruction than a group of trees further
away from the antenna. The WI-GTWY-9-xxx modules provide a test feature that displays the
radio signal strength.

29

WI-GTWY-9-xxx Wireless Gateway V1.18

Line-of-sight paths are only necessary to obtain the maximum range. Obstructions will reduce
the range, however may not prevent a reliable path. A larger amount of obstruction can be
tolerated for shorter distances. For very short distances, it is possible to mount the antennas
inside buildings. An obstructed path requires testing to determine if the path will be reliable ­refer the section 6 of this manual.

Longer distances can be achieved using the licensed 105U units, because they use a lower
frequency and licensed conditions generally allow a higher RF power to be used.

Where it is not possible to achieve reliable communications between two modules, then another
WI-I/O 9-x or WI-GTWY-9-xxx module may be used to receive the message and re-transmit it.
This module is referred to as a repeater.

An antenna should be connected to the module via 50 ohm coaxial cable (eg RG58, RG213 or
Cellfoil) terminated with a male SMA coaxial connector. The higher the antenna is mounted, the
greater the transmission range will be, however as the length of coaxial cable increases so do
cable losses. For use on unlicensed frequency channels, there are several types of antennas
suitable for use. It is important antenna are chosen carefully to avoid contravening the maximum
power limit on the unlicensed channel - if in doubt refer to an authorized service provider.

The net gain of an antenna/cable configuration is the gain of the antenna (in dBi) less the loss in
the coaxial cable (in dB).

The maximum net gain of the antenna/cable configuration permitted is
Country Max. gain (dB)

USA / Canada 6
Australia / New Zealand 0
The gains and losses of typical antennas are

Antenna Gain (dB) Weidmuller Part Nos.

Dipole with integral 15’ cable 0 WI-ANT-DPL-0-16
5dBi Collinear (3dBd) 5 WI-ANT-COL-5-32
8dBi Collinear (6dBd) 8 WI-ANT-COL-8-54
6 element Yagi 10 WI-ANT-YGI-10-6
16 element Yagi 15 WI-ANT-YGI-15-16

Cable type Loss (dB per 30 ft / 10 m)
RG58 -5
RG213 -2.5
Cellfoil -3 WI-CCSMA-N-33 (33’ or 10m)

Cellfoil -6 WI-CCSMA-N-66 (66’ or 20m)

The net gain of the antenna/cable configuration is determined by adding the antenna gain and the
cable loss. For example, a 6 element Yagi with 66 feet (20 meters) of Cellfoil has a net gain of
4dB (10dB – 6dB).

30

1m minimum

COLINEAR

MAST

EARTH STAKE

INSTALL AERIAL ABOVE

SURGE

COAXIAL CABLE

WEATHERPROOF

STRESS RELIEF LOOP

PROVIDE GOOD

WI-GTWY-9-xxx Wireless Gateway V1.18

For information on antennas and cables for the WI-GTWY-1 licensed products, please refer to
Weidmuller, Inc. or an authorized distributor.

Connections between the antenna and coaxial cable should be carefully taped to prevent ingress
of moisture. Moisture ingress in the coaxial cable is a common cause for problems with radio
systems, as it greatly increases the radio losses. We recommend that the connection be taped,
firstly with a layer of PVC Tape, then with a vulcanizing tape such as “3M 23 tape”, and finally
with another layer of PVC UV Stabilized insulating tape. The first layer of tape allows the joint
to be easily inspected when trouble shooting as the vulcanizing seal can be easily removed.

Where antennas are mounted on elevated masts, the masts should be effectively earthed to avoid
lightning surges. For high lightning risk areas, surge suppression devices between the module
and the antenna are recommended. If the antenna is not already shielded from lightning strike by
an adjacent earthed structure, a lightning rod should be installed above the antenna to provide
shielding.

3.2.1 Dipole and Collinear antennas.

ARRESTOR
(OPTIONAL)

LOCAL OBSTRUCTIONS

GND

ANT

CONNECTORS WITH
“3M 23” TAPE

GROUND
CONNECTION TO
MAST, MODULE
AND SURGE
ARRESTOR

for best performance

ANTENNA

IF GROUND CONDITIONS ARE
POOR, INSTALL MORE THAN

A collinear antenna transmits the same amount of radio power in all directions - it is easy to
install and use. The dipole antenna with integral 15 ft (5m) cable does not require any additional
coaxial cable, however the other collinear antennas do not have integral cable and an external
cable length must be connected - such as the WI-CCSMA-N-33 or WI-CCSMA-N-66 cable kits..

31

WI-GTWY-9-xxx Wireless Gateway V1.18

down

at connec tion

90

o

Collinear and dipole antennas should be mounted vertically, preferably no less than 2 ft (0.6
metre) away from a wall or mast to obtain maximum range. The WI-ANT-DPL-0-16 dipole
antenna is the preferred antenna for use in industrial plants and factories.

3.2.2 Yagi antennas.

A Yagi antenna provides high gain in the forward direction, but lower gain in other directions.
This may be used to compensate for coaxial cable loss for installations with marginal radio path.

The Yagi gain also acts on the
receiver, so adding Yagi
antennas at both ends of a link
provides a double
improvement.

Yagi antennas are directional.
That is, they have positive gain
to the front of the antenna, but

Antenna installed
with drain hol es

negative gain in other
directions. Hence Yagi

Coax feed l ooped

antennas should be installed
with the central beam
horizontal and must be pointed
exactly in the direction of
transmission to benefit from
the gain of the antenna. The
Yagi antennas may be installed
with the elements in a vertical
plane (vertically polarized) or
in a horizontal plane
(horizontally polarized). For a
two station installation, with
both modules using Yagi
antennas, horizontal
polarization is recommended.
If there are more than two stations transmitting to a common station, then the Yagi antennas
should have vertical polarization, and the common (or “central” station should have a collinear
(non-directional) antenna.

Also note that Yagi antennas normally have a drain hole on the folded element - the drain hole
should be located on the bottom of the installed antenna.

3.3 Power Supply

The WI-GTWY-9-xxx power supply is a switch-mode design which will accept either AC or DC
supply. The module includes an integral battery charger for a backup battery.

The module accepts supply voltages in the following ranges:

32

_

WI-GTWY-9-xxx Wireless Gateway V1.18

12 – 24 volts AC RMS or 9 – 30 volts DC at the “supply” terminals, or

10.8 –15 volts DC at the “battery” terminals.
The power supply should be rated at 1.5 Amps and be CSA Certified Class 2. For use in Class 1

Div 2 explosive areas (USA/Canada), the power supply must be approved for Class 1 Div 2 use.
Note: Connect module to the same ground/earth point as the antenna mounting to avoid

differences in earth potential during voltage surges. The modules need an earth connection for
the internal surge protection to be effective.

For licensed 105U units with RF power above 2W, the unit needs to be powered from
the 12V “Battery” terminals with a power supply of at least 2A rating. Alternately, the
unit can be powered via the SUP1 / SUP2 terminals, provided a backup battery is
connected to the “Battery” terminals to supply the inrush current for the radio transmitter.
This is not required for units with radio power less than 2W.

3.3.1 AC Supply

The AC supply is connected to the “SUP1” and “SUP2” terminals as shown below. The AC
supply should be “floating” relative to earth.

12 – 24 VAC

Power
Supply
AC Out

Optional Battery

Fuse 5A

- +

SUP1

SUP2

GND

BAT+

WI-GTWY

3.3.2 DC Supply

For DC supplies, the positive lead is connected to “SUP1” and the negative to “GND”. The
positive side of the supply must not be connected to earth. The DC supply may be a floating
supply or negatively grounded.

9 – 30 VDC

Power
Supply
DC Out

Optional Battery

Fuse 5A

+

- +

GND

SUP1

SUP2

GND

BAT+

WI-GTWY

33

WI-GTWY-9-xxx Wireless Gateway V1.18

The module may also be powered from an external 11 – 15 VDC battery supply without the need
for a “normal” supply connected to “SUP1”. This external battery supply is connected to
“BAT+” and “GND” terminals. The positive lead of the external supply should be protected by a
5A fuse

SUP1

SUP2

GND

BATTERY SUPPLY

11-15 VDC

Fuse 5A

BAT+

- +

WI-GTWY

.Upon failure of the normal supply, the module may continue to operate for several hours from a
backup battery. The battery charger is designed for sealed or vented lead acid batteries between 5
and 24 amphours - other types of batteries should not be used. Typically, a 5 AHr battery will
supply the WI-GTWY-9-xxx for 1 – 2 days, depending on the type of WI-GTWY-9-xxx.

On return of normal supply, the unit will recharge the battery. The maximum output of the
battery charger is 0.7A when the supply voltage is greater than 12V, and 0.3A for less than 12V.

The WI-GTWY-9-xxx monitors the power supply and provides the following internal values,
which can be mapped as I/O values:

• Power failure (I/O Reg 4309) - if the supply voltage drops below 8V, this status value is set

on, and set off again when the voltage is more than 9V. For AC Supplies, this indicates low
voltage at approximately 10 VAC, and the status is cleared when the supply voltage rises
above approximately 12VAC

• Low battery voltage (I/O Reg 4308) - this status value is set on if the battery voltage drops to

11.3, and resets off when the battery voltage is more than 11.8V.

• Battery voltage value (I/O Reg 4310) - 8 – 40VDC corresponds to hex 4000 – hex C000.

• Supply voltage (I/O Reg 4311) - 8 – 40VDC corresponds to hex 4000 – hex C000.

3.3.3 Solar Supply

A WI-GTWY-9-xxx can be powered from a solar supply using an external regulator. If a 12V
solar supply is used, the 12V battery can be connected to the battery supply connections of the
WI-GTWY-9-xxx and the WI-GTWY-9-xxx will monitor for low battery status and also battery
voltage. If a 24V solar supply is used, the 24V battery should be connected as a DC supply
(SUP1 and GND) - the supply voltage can be monitored however the “supply fail” voltage will
activate too low to be used as a battery fail status.

34

_

contact input

input

+

V

-

_

WI-GTWY-9-xxx Wireless Gateway V1.18

3.4 Input / Output

The WI-GTWY-9-xxx has eight on-board discrete/digital I/O. These act as both discrete inputs
and discrete outputs.

3.4.1 Digital Inputs / Outputs

All eight of the WI-GTWY-9-xxx DIO terminals may be used as discrete inputs. These inputs are
suitable for voltage free contacts (such as mechanical switches) or NPN transistor devices (such
as electronic proximity switches). PNP transistor devices are not suitable. Contact wetting
current of approximately 5mA is provided to maintain reliable operation of driving relays.

Voltage-free

Transistor

DIO

+

DIO

GND

V

WI-GTWY

Each digital input is connected between the appropriate “DIO” terminal and common “COM”.
Each digital input circuit includes a LED indicator which is lit when the digital input is active,
that is, when the input circuit is closed. Provided the resistance of the switching device is less
than 200 ohms, the device will be able to activate the digital input.

DIO

DIO

GND

WI-GTWY

Max 30VDC

0.5A

+

DC

Load

All eight of the WI-GTWY-9-xxx DIO terminals may also be used as discrete outputs. The
digital outputs are transistor switched DC signals, FET output to common rated at 30VDC 500
mA.

Digital outputs may be configured to individually turn off if no command message is received to
that output for a certain period. This feature provides an intelligent watch dog for each output, so
that a communications failure at a transmitting site causes the output to revert to a known state.
See Chapter 4 Configuration for further details.

The output circuit is connected to the appropriate “DIO” terminal. Each digital output circuit
includes a LED indicator which is lit when the digital output is active.

35

WI-GTWY-9-xxx Wireless Gateway V1.18

3.5 Serial Port

3.5.1 RS232 Serial Port

The serial port is a 9 pin DB9 female and provides for connection to a terminal or to a PC for
configuration, field testing and for factory testing. It is also used by the Modbus/DF1 version for
fieldbus connection.

This port is internally shared with the RS485 - ensure that the RS485 is disconnected before
attempting to use the RS232 port. Communication is via standard RS232 signals. The WI­GTWY-9-xxx is configured as DCE equipment with the pinout detailed below.

DB9 Connector Pinout:

Pin Name Direction Function

1 DCD Out

2 RD Out Serial Data Output

3 TD In Serial Data Input

4 DTR In

Used for "active" signal.

Data Terminal Ready - may be used by Host Protocol Driver

5 SG Signal Ground

6 DSR Out Data Set Ready - always high when unit is powered on.

7 RTS In Request to Send - may be used by Host Protocol Driver

8 CTS Out Clear to send - may be used by Host Protocol Driver

9 RI Ring indicate - not connected

Hardware handshaking using the CTS/RTS lines is provided, and are under the control of the
Host Comms Driver. Example cable drawings for connection to a DTE host (a PC) or another DCE
host are detailed below:

3.5.2

RD
TD

SG
RTS
CTS

DSR
DTR
DCD

2
3
5
7
8
6
4
1

2

RD

3

TD

5

SG

7

RTS

8

CTS

6

DSR

4

DTR

1

DCD

RD
TD

SG
RTS
CTS
DSR
DTR

DCD

2
3
5
7
8
6
4
1

2

RD

3

TD

5

SG

7

RTS

8

CTS

6

DSR

4

DTR

1

DCD

MODEM

DB9

MALE

36

DCE HOST

DB9

FEMALE

MODEM

DB9

MALE

DCE HOST

DB9

MALE

WI-GTWY-9-xxx Wireless Gateway V1.18

RS485 Serial Port

RS485 should not be used with the DF1 unit. The RS485 port provides for communication
between the WI-GTWY-9-xxx unit and its host device using a multi-drop cable. Up to 32
devices may be connected in each multi-drop network. Note that the RS485 port is shared
internally with the RS232 port - make sure that the RS232 port is disconnected before using the
RS485 port.

WI-GTWY9

INTERNAL
RESISTOR

EXTERNAL RESISTOR
REQUIRED

TERMINATING
RESISTOR SWITCH
ON = TERMINATION
OFF = NO TERM.

RS485 is a balanced, differential standard but it is recommended that shielded, twisted pair cable
be used to interconnect modules to reduce potential RFI. An RS485 network should be wired as
indicated in the diagram below and terminated at each end of the network with a 120-ohm
resistor. On-board 120 ohm resistors are provided and may be engaged by operating the single
DIP switch in the end plate next to the RS485 terminals. The DIP switch should be in the “1” or
“on” position to connect the resistor. If the module is not at one end of the RS485 cable, the
switch should be off.

It is important to maintain the polarity of the two RS485 wires. On the WI-GTWY-9-xxx,
terminal A (the terminal on the right) is positive and terminal B is negative.

37

WI-GTWY-9-xxx Wireless Gateway V1.18

CONFIGURATION

CONFIGURATION

3.6 Profibus Port

The Profibus RS485 connector is a D9 connector in the top end-plate of the module (see below).
WI-GTWY-9-PR1 (Profibus Slave) End Plate:

PROFIBUS D9

CONNECTOR

RS485

TERMINATION

SWITCH

ANTENNA

CONNECTION

SELECTOR
SWITCHES

DIAGNOSTIC

LED’s

ENABLE

Note: If the “Use Rotary Switch Address” option in configuration software is selected, the two
rotary switches are used to specify the Profibus Node Address in the range 0 – 99. In this case,
the value on the left switch is multiplied by 10 and added to the value on the right switch to give
the node address.

Where the WI-GTWY-9-xxx module is mounted at the end of the RS485 link, the RS485 link
should be terminated by switching the termination switch “on” (down in the above diagram).

WI-GTWY-9-PR2 (Profibus Master) End Plate:

PROFIBUS D9

CONNECTOR

UNUSED D9

CONNECTOR

ANTENNA

CONNECTION

DIAGNOSTIC

LED’s

ENABLE

For the Profibus Master WI-GTWY-9-PR2 a second, unused, connector is also present.
The Profibus RS485 connection should be made to pins 3 and 8 of the Profibus D9 connector.

The pinouts for this connector are:

38

CONFIGURATION

WI-GTWY-9-xxx Wireless Gateway V1.18

Pin Description

1 Not connected
2 Not connected
3 +ve RS485 (Positive)
4 RTS (request to send)
5 GND - Isolated GND from RS485 side
6 +5V - Isolated 5V from RS485 side
7 Not connected
8

-ve RS485 (Negative)

9 Not connected

3.7 Ethernet Port

For WI-GTWY-9-ET1 modules only.
The Ethernet connection uses a standard RJ45 connector on the top end-plate of the module. The

selector switches should all be “off” (in the diagram below, “off” is up).

RJ45 ETHERNET

CONNECTION

SELECTOR
SWITCHES

DIAGNOSTIC

LED’s

ENABLE

ANTENNA

CONNECTION

39

WI-GTWY-9-xxx Wireless Gateway V1.18

CONFIGURATION

3.8 Modbus Plus Port

For WI-GTWY-9-M+1 modules only.
Connection to the Modbus Plus Network is via the 9-pin D-SUB connector located at the antenna

end of the module. Pin-outs are outlined in the table below.

D9 MODBUS

PLUS

SELECTOR
SWITCHES

ANTENNA

CONNECTION

DIAGNOSTIC

LED’s

See section on configuration for description of selector switches.

Modbus Plus 9-pin D-SUB Connector:

Pin Name

1 Cable Shielding
2 MBP Line B
3 MBP Line A

ENABLE

Housing PE

40

CONFIGURATION

WI-GTWY-9-xxx Wireless Gateway V1.18

3.9 DeviceNet Port

For WI-GTWY-9-DE1 modules only.
Connection to the DeviceNet Network is via the 5-pin plugable screw terminal connector located

at the antenna end of the module. Pin-outs are specified below.

DEVICENET

CONNECTION

SELECTOR
SWITCHES

DIAGNOSTIC

LED’s

ENABLE

ANTENNA

CONNECTION

5-pin plugable screw terminal fieldbus connector:
Pin Signal Description

1 V- Negative Supply Voltage
2 CAN_L CAN_L bus line
3 SHIELD Cable shield
4 CAN_H CAN_H bus line
5 V+ Positive supply voltage

DeviceNet uses termination resistors at each physical end of the bus. The termination resistor
should be 121 ohm. This should be connected between CAN_H and CAN_L on the bus.

41

WI-GTWY-9-xxx Wireless Gateway V1.18

Chapter 4 CONFIGURATION

4.1 Introduction

A Windows program is provided to configure the WI-I/O 9-x system. The configuration is done
on a system basis - referred to as a “project” in the program. After the system configuration is
entered, the configuration file can be loaded into each module via the RS232 port.

Each Project is configured with:

• a system address, which is common to every module in the same system, and is used to
prevent "cross-talk" between modules in different systems. Separate networks with different
system addresses may operate independently in the same area without affecting each other.
The system address may be any number between 1 and 32 767. The actual value of the
system address is not important, provided all modules in the same system have the same
system address value. A system address of zero should not be used. The configuration
program automatically offers a random number for the system address - you can change this
to any number in the valid range but we recommend that you use the random number.

• a password for access protection. This is an optional feature. If selected, the project file can
only be opened by entering the correct password.

• a security encryption key, used to encrypt and decrypt radio messages. This is an optional
feature. If selected, the configuration program will offer a random security key, or this can
be over-written with your own key. A key is a string of any 8 ASCII characters.

Each module in the project is configured with a unit address. Each module must have a unique
unit address within the one system. A valid unit address for a WI-GTWY-9-xxx is 1 to 95. A
network may have up to 95 addresses communicating directly via radio (unit addresses 1 to 95).
WI-I/O 9-x I/O modules can have up to 31 modules communicating via RS485 (unit addresses 96
to 127).

The configuration program may allocate more than one unit address to a WI-GTWY-9-xxx if it is
required because of the size of the system. If this is necessary, it will be done automatically by
the configuration software.

Configuration consists of:

1. selecting the types of modules in the system and selecting address values

2. linking (called “mapping”) I/O registers to remote I/O

3. setting operating parameters such as change sensitivities and update times

4. selecting “block mappings” - only for block transfer of I/O registers between WI-GTWY-9­xxx modules

5. selecting fieldbus addressing, and serial port configuration (Modbus & DF1 only)

6. linking Radio Interface registers to Fieldbus Interface registers (All modules except MD1)

42

WI-GTWY-9-xxx Wireless Gateway V1.18

All of these steps must be performed to configure the WI-GTWY-9-xxx module.

4.2 Configuration Program

The configuration software is available on a CD, and needs to be installed on your PC before you
can use it. The CD contains a setup file called setup.exe. Select the configuration software
window on the Product CD and an installation Wizard will guide you through the installation
procedure. To upload and download configuration files to a module, you will need a RS-232
serial cable as shown below.

WI-GTWY-9-xxx PC
DB9 Male DB9 Female

1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9

Required

Optional

43

WI-GTWY-9-xxx Wireless Gateway V1.18

4.2.1 Program Operation

Start the software by either clicking on the start bar and navigating to the Configuration menu or
by running WI SERIES.EXE in the directory selected in the setup stage.

The Initial screen will appear.

From the initial screen, , you can
select an existing project, or start
a new project. The name of the
project will create a new folder
which will eventually contain the
configuration files for the
modules in this system. Project
folders are located under the
folder \Projects\ - for example,
if you create a project called
“Fire Pumps”, then the files for
this project will be found in the
folder c:\……\Projects\Fire Pumps\.

When you have selected the project, a screen will appear
where you may enter the system address.

If you are editing an existing project, the system address
will already have been entered. Do not change the system
address unless you are going to re-program all of the
modules in the system.

Password. You have the option of entering a password to
protect the configuration files against unauthorized
changes. When you open a new project, you will be asked
to enter a password - if you do not enter any text - that
is, press “ESC” or “Enter”, then password protection is
disabled. If you do enter a password, then you will need to
enter this password to access the project. Without the
password, you are unable access the project

The password can be between 6 and 256 characters. You

44

WI-GTWY-9-xxx Wireless Gateway V1.18

can also change password at any time by over-typing the passowrd.

If you are starting a new project, you have the option of “Enabling Security”. This option enables
encryption of the data
sent over the radio. -
please read Section

4.2.2 and the

associated warnings
before using this
option.

To proceed with the
configuration, double­click on the project
name on the menu on
the left side of the
screen. “Units” will
appear. You can now
enter the types of units
which will be used in
the system. If you double-click on “Units”or select the “+” sign beside “Units”, then the modules
that have already been created will be displayed.

Loading configuration from an existing module

To load the configuration from a module, connect the module to the PC via the RS232 cable, put
the module into “Configuration Mode” by pressing the configuration button on the top end-plate,
and click on “Load Unit”. This will allow you to view the module configuration, change it, or
copy it for another module - refer to section 4.3 for full
details.

Adding a new module to the system configuration
To add a new module to the system configuration, click on
“Units” on the left-hand menu and then “Add Unit”.
Select the type of module from the list. For WI-GTWY- 9-
xxx modules, you will be asked to select the bus
protocol. This must match the WI-GTWY-9-xxx module
type you have installed.

You have the option of selecting a unit address for the
module, or allowing the program to select one
automatically. If you choose to select the unit address the
program will display the list of available addresses for you
to select - valid addresses are 1 – 95.

45

WI-GTWY-9-xxx Wireless Gateway V1.18

The default name for a unit will include the unit address. For example, “WI-GTWY#10” is a
WI-GTWY-9-xxx module with unit address 10. You can change the name of a unit - for
example, you could replace the default name with “Pump Station 14”.

46

WI-GTWY-9-xxx Wireless Gateway V1.18

Deleting a Unit

A module can be deleted from the configuration by highlighting the unit and selecting “Delete

Unit”.

4.2.2 Security

There are two security features available. You can enter a password to protect the configuration
files, and you can enable security encryption of the radio transmissions.

The password can be between 6 and 256 characters. The password is case sensitive and any
ASCII characters can be used. If you have entered a password, then this password will need to be
entered whenever the configuration is changed. You are able to change the password from the
“Utilities” menu. If unauthorized access to the files is a concern, we recommend that you change
the password regularly or whenever there is a change of staff.

Data Encryption is an additional level of security. The security option uses a 64 bit security key
to provide data encryption of the radio messages. All modules in the same system will be
configured with the same security key used to encrypt and decrypt the messages. This feature is
available for modules with firmware version 2.1 and higher. If you are adding modules to an old
system which does not have the security encryption feature, then you cannot use security
encryption on the new modules.

Note that the security key is different than the password.

• To enable the security encryption, select the “Enable Security” box on the project display.
An 8-character random security key is automatically generated. If desired, a different security
key may be entered and you will be prompted to enter the security code a second time to
confirm. The security key can be any characters or numbers. Characters are case sensitive.
The security key will never be displayed.

47

WI-GTWY-9-xxx Wireless Gateway V1.18

• If you do not enable security, there will be no data encryption of the radio messages. This is
the default setting.

• If a security key has been entered, this key is downloaded into each module as part of the
configuration download process. You can download another configuration at any time - if
the security key is different, or if there is no security key in the new configuration, the old key
will be over-written.

• You can change the security key in the configuration files simply by entering a new security
key in the security key window. You will be prompted to confirm the new security key.
Note that if you change the security key, it will not match the security key previously loaded
into existing modules.

• If you want to change a configuration, we recommend that you change the archived
configuration, and then download the configuration onto the module. The archived
configuration already has the valid security key.

• If you lose the archived configuration, you can upload the configuration from a module, but
you cannot upload a security key. That is, you can upload the module configuration, view it,
change it - but if you don’t know the original security key, the old key will be over-written
when you download the new configuration. This module will no longer communicate with
other modules in the system as the security key is different.

Warning!!

These security options provide a high level of security, but no data-security system can
provide “100% protection”. But it does make it very difficult for someone to interfere
with the WI-I/O 9-x system - difficult to the point where there would be many easier
alternate ways to cause malicious damage.

The password must be kept in a secure place. Security procedures need to be adopted. If
staff with access to the password leave your organization, we recommend that the password
be changed.

We recommend that you use a random 8-character string for the security key and that you
do not record the key. It is not necessary to know what the security key is. The key will be
recorded in the archived configuration files, and therefore the configuration files should be
held in a secure place and backed up.

The security key does not prevent a hacker uploading a configuration from a module and
downloading with a new security key. This module will no longer operate with other
modules in the system. To prevent this, unauthorized access to modules must be prevented.

The security options provide security against a “hacker” in the following way:

 A hacker cannot listen-in to radio messages without the security key to decrypt the radio

messages. Similarly, a hacker cannot force outputs by transmitting a radio message to a
module without the security key.

 A hacker cannot access the security key from an installed module or from the configuration

files.

48

CONFIGURATION

8

WI-GTWY-9-xxx Wireless Gateway V1.18

 The archived configuration files cannot be changed, downloaded or uploaded without the

password.

If you lose the configuration files, you can regenerate these by uploading the configuration from
every module in the system into a new project with a new security key. After uploading each
module, download the configuration with the new security key.

If you wish to change the security key, simply enter a new key in the configuration program, and
download the new configuration to all modules in the system.

Note on Ethernet WI-GTWY-9-xxx. You are able to access the module configuration of an
Ethernet WI-GTWY-9-xxx via the Ethernet port. To prevent this access, do not select “Enable
Ethernet Debug” on the Ethernet configuration display - see section 4.8.

4.3 Uploading and Downloading

To upload or download a configuration file, the WI-GTWY-9-xxx must be connected to the PC
via a RS232 cable. For Modbus/DF1 units, the host device must be disconnected, even if it is
connected to the RS485 port. Other units do not need to disconnect the data bus. When the PC
is connected, put the WI-GTWY-9-xxx into configuration mode by pressing the small
pushbutton switch in the end plate of the module for 5 seconds, until the ACT LED starts
flashing.

In configuration mode, the WI-GTWY-9-xxx will stop its normal functions.
Make sure the correct
communications port is
selected on the PC - if
necessary, change the
selection from the

ANTENNA

CONNECTION

ENABLE

Utilities menu.
Connect the PC to the
module using the
configuration cable.

The configuration may
be programmed into a
WI-GTWY-9-xxx, or a
configuration may be
loaded from a WI­GTWY-9-xxx. After
programming or
loading is complete,
disconnect the PC from
the WI-GTWY-9-xxx.
Reset the WI-GTWY­9-xxx by removing

WI-I/O 9
End DB9
Male

1
2
3
4
5
6
7

PC End

DB9 Female

1
2
3

Required

4
5
6

Optional

7
8
9

power and re-connecting power. The WI-GTWY-9-xxx will start up normally and the OK LED
will be on. The serial port will have its original set-up.

49

WI-GTWY-9-xxx Wireless Gateway V1.18

4.3.1 Loading from a WI-GTWY-9-xxx

If you load a configuration from a WI-GTWY-9-xxx into a “blank” or new project, then the
program will not be able to display the mappings from remote modules (as the program does not
know what the remote modules are). You will get a warning message like this:

If you open the archived project first, and load into the archived project, then all mappings will
display as normal - any mappings to/from the WI-GTWY-9-xxx will be over-written on the PC
display by the loading process.

If you are unable to load into the archived project, then mappings to remote modules will be
displayed, but mappings from remote inputs will be shown as “Unknown Mappings”.

If you also load the configurations from the other remote modules in the system, then these
unknown mappings will disappear as the program can determine where the remote inputs are.
Alternately, you can select “Link Mapping” and manually enter the remote inputs.

50

WI-GTWY-9-xxx Wireless Gateway V1.18

4.4 Mappings WI-GTWY-9-xxx to

WI-I/O 9-x I/O Modules

To transfer remote input signals to a WI-GTWY-9-xxx, or
transfer a value to a remote output from a WI-GTWY-9­xxx, you set up “I/O mappings”. You enter mappings into
the source unit, not the destination unit. That is, you
configure a mapping at the “input” module. If you want to
transfer an input signal at a WI-I/O 9-x module to a WI­GTWY-9-xxx register, you enter a mapping at the WI-I/O 9­x I/O module. If you want to transfer a WI-GTWY-9-xxx
register to an output signal at a WI-I/O 9-x module, you
enter a mapping at the WI-GTWY-9-xxx module.

To configure mappings, double-click on the module in the left-hand menu - the menu will
expand with selections for that module. Select “Mappings”.

Each mapping comprises only one I/O point. “Block Mappings” provide more advanced
communications between WI-GTWY-9-xxx modules.

4.4.1 Mappings from Inputs at Remote WI-I/O 9-x I/O Modules

Refer to the WI-I/O 9-x I/O User Manual.
When mapping inputs to a WI-GTWY-9-xxx, you will be asked to select an I/O Register. Select

the “…” box beside the “At I/O Register” heading - this will allow you to select the I/O register
between 0 and 4299. Any I/O registers that have already been selected will have a color shading.
The update times, analog sensitivities for these mappings can be set as per normal I/O mappings.
To map several inputs to consecutive I/O registers, use “Shift”-select or “Ctrl” - select to

highlight the inputs, and select the first I/O register in the range. The selected mappings will be
entered with consecutive I/O registers.

51

WI-GTWY-9-xxx Wireless Gateway V1.18

For each “remote input” configured to a WI-GTWY-9-xxx, there is a comms-fail time parameter
in the WI-GTWY-9-xxx. If the WI-GTWY-9-xxx does not receive a message destined to that
I/O register within the “comms fail” time, then the “comms fail” status for that I/O register will
be set - the most significant bit of the status register will be set to 1. The comms fail time
should be more than the corresponding update time at the remote input.

To set the comms fail times, select the WI-GTWY-9-xxx, and select the “Comms Fail Time”
option. Each remote input already mapped to the WI-GTWY-9-xxx will automatically be listed,
including the remote module containing the mapping.

The default value for the
comms-fail time is “disabled”
or zero. To enter a time,
select the I/O register from the
list. The comms-fail time
should be greater than the
update time of the remote
input.

Firmware version 1.76 and later:
The I/O value in the I/O registers can be reset to zero on comms-fail. To enable this, select the

enable box in the “Comms Fail Times” configuration screen. Note that this is a global selection;
comms-fail-reset is configured on all registers or no registers.

4.4.2 Mappings from WI-GTWY-9-xxx to Outputs at Remote WI-I/O 9-x I/O Modules

Mappings can be entered in the WI-GTWY-9-xxx to remote outputs. Select the “Mappings”
option under the WI-GTWY-9-xxx. Select an I/O register and select the remote module and the
output channel.

To map several consecutive I/O registers to several outputs, select the first I/O register in the
range and use “Shift”-select or “Ctrl” - select to highlight the multiple outputs. The selected
mappings will be entered with consecutive I/O registers.

52

WI-GTWY-9-xxx Wireless Gateway V1.18

Change Sensitivities

Radio messages to remote modules can be change messages (when the value of the I/O register
changes) or update messages (when the update time has elapsed). If a change message is sent,
the update period restarts.

You can configure the amount of change required to trigger a change message - this is called the
change sensitivity. Sensitivities are configured for blocks of I/O registers - that is, each I/O
register does not have a unique sensitivity. You can configure up to 50 sensitivity values - that
is, there can be 50 blocks of registers with different sensitivities.

For more information on this, refer to section 4.6.

53

WI-GTWY-9-xxx Wireless Gateway V1.18

Update Times

To change the update times of
output mappings, select the
Update Times option. Any
I/O registers that have already
been mapped to remote
outputs will automatically be
listed. The default update
time is 10 minutes.

Changing Multiple Settings

You can change the Comms
Fail Times or Update Times of several I/O points simultaneously by using the <Shift> Select
feature. For example, if you want to change all times to 1 minute, you could change each
individually, or you could “block” all entries using the “Shift” Select feature and select “Edit”.
You only need to enter the change once to change all of the inputs selected. This feature is also
available with the other configurable parameters.

4.4.3 Don’t Send if in Comm Fail

You can configure a special “Don’t Send if in Comms Fail” mapping. If this is configured for a
particular remote module, the WI-GTWY-9-xxx will not transmit output messages to this remote
address, if there is a communications failure status on any input or output configured for the
same remote address. Output messages will re-start when a message is received from the remote
module. The use of this option can prevent the radio channel becoming congested if there are
many outputs at that module.

To configure this special mapping, select the “New Don’t Send in Comms Fail Mapping” box.
You will be asked to select which remote module this function applies to. You can enter more
than one of these mappings if there are more than one modules.

54

WI-GTWY-9-xxx Wireless Gateway V1.18

4.4.4 Startup Polls

You can enter start up polls for remote modules by using the “New Poll Mapping” box. This
function is the same as for the WI-I/O 9-x I/O modules. A start-up poll is a special message sent
when the WI-GTWY-9-xxx starts up. When the remote module receives a start-up poll, it will
immediately respond with update messages for all its inputs that are mapped to the WI-GTWY-9­xxx. This allows the WI-GTWY-9-xxx to have correct values on start-up.

4.4.5 Polls to Remote Modules

It is possible for a WI-GTWY-9-xxx to send a poll to a remote module at other times apart from
start-up. A poll can be sent under the following events:

• based on a configurable time period

• based on real time clock

• on-demand by the host device.

For information on this configuration, refer to the next section on “Block Mappings”.

4.5 Mappings from WI-GTWY-9-xxx to other WI-GTWY-9-

xxx Modules

Individual links between WI-GTWY-9-xxx modules can be configured under the “Mappings”
selection as described in the previous section. For example, if you want to transfer I/O Reg 144
in WI-GTWY-9-xxx#2 to I/O Reg 286 in WI-GTWY-9-xxx#3, you can enter the following
mapping:

Whenever I/O Reg 144 changed by the sensitivity amount, WI-GTWY-9-xxx#2 would send a
message to WI-GTWY-9-xxx#3 to write the value in I/O Reg 286. The problem arises if there
are a lot of these mappings. Each radio message only relates to one register-register link. If you
want to map 1000 registers from one WI-GTWY-9-xxx to another, then this could generate a lot
of radio messages.

55

WI-GTWY-9-xxx Wireless Gateway V1.18

BLOCK OF I/O

BLOCK WRITE

BLOCK OF I/O

To get around this problem, it is possible to configure “block mappings”. With a block mapping,
multiple registers (a “block of registers”) can be transferred together in the one radio message.
This improves the efficiency of the radio communications.

Read/Write Mappings

The mappings can be “read” or “write” mappings. A Read mapping is a request sent to another
WI-GTWY-9-xxx to return a block of values. A Write mapping is a message sending a block of
values to another WI-GTWY-9-xxx. A Read mapping from WI-GTWY-9-xxx#2 to WI-GTWY­9-xxx#3 could be the same as a Write mapping from WI-GTWY-9-xxx#3 to WI-GTWY-9­xxx#2 (that is, in the reverse direction) - except the Read mapping is initiated from #2 and the
Write mapping is initiated from #3.

REGISTERS

MESSAGE

LOCAL

WI-

GTWY-

9-xxx

ACKNOWLEDGMENT

READ REQUEST

BLOCK READ

MESSAGE

REGISTERS

REMOTE

WI-

GTWY-9-

xxx

Word/Bit Mappings

Read and Write mappings are also selected as Word or Bit mappings - that is, you can select a
Read Word mapping or a Read Bit mapping and you can select a Write Word mapping or a Write
Bit mapping. “Word” refers to a complete 16-bit register value; “Bit” refers to the value of the
most significant bit of a register - this bit is the “binary value” or “digital value” of the register.

If you use a Word block mapping of 50 registers, you are transferring a block of 50 x 16-bit
values. If you use a Bit block mapping of 50 registers, you are only transferring the digital value
of each register - that is 50 x 1 bit values. This is a lot more efficient for a radio message, but
bit mappings are only suitable for discrete or digital I/O. A Bit mapping will convert the 16-bit
register to a single bit, transfer it and store the bit value in the most significant bit of the
destination register.

Note: The maximum block size for each block mapping is 64 registers.

56

WI-GTWY-9-xxx Wireless Gateway V1.18

4.5.1 Entering a Block Mapping

Select the “source” WI-GTWY-9-xxx on the left hand menu - select “Block Mappings” and
then “New Block Mapping” from the right-hand display. The Block Mapping Configuration
display will appear.

Select the “Command Type” from the pop-down window in the centre of the display. The red
arrow will confirm the direction of the block transfer. Now select the destination module - only
the WI-GTWY-9-xxx modules already configured will be shown. If you need to use repeaters in
the radio link, enter the repeater addresses, starting with the repeater closest to the source
module.

Under “Source Gateway”, enter the I/O Register and I/O Count. The I/O Register is the first
register in the block and the I/O Count is the number of registers - in the above example, the
block of registers will be 110 – 124 (15 registers starting at I/O Reg 110).

If you are entering a Write mapping, then the values in this block will be sent to another WI­GTWY-9-xxx. If it is a Read mapping, then values from another WI-GTWY-9-xxx will be sent
to this block.

Under “Destination Gateway”, enter the I/O Register - this is the first register in the block. You
do not need to enter the block size as this will always be the same as the block size in the source
WI-GTWY-9-xxx. In the above example, the destination block will be I/O registers 32 – 46 (15
registers starting at register 32). So, in the above example, a block of 15 x 16-bit values will be
written from I/O Reg 110 – 124 in WI-GTWY-9-xxx#1 to I/O Reg 32 – 46 in WI-GTWY-9­xxx#2.

57

WI-GTWY-9-xxx Wireless Gateway V1.18

Each mapping entered is allocated a status register - the register number appears on the right
hand of the Block Mapping display. These registers store relevant status information about the
block mapping - the structure of the Block Mapping status registers is shown in Appendix 1.

In the above example, the status register for the block mapping has been automatically assigned
to register 9500.

The rest of the mapping configuration involves the mapping trigger - or what initiates the
mapping message.

Firmware version 1.82 and later.

Block write mappings have option to invert the I/O message that will be sent. This can be
selected when adding new write block mapping

Mapping “Triggers”

A block mapping can be “triggered” or initiated by several different methods.

• By the host device writing to a “trigger register” in the source WI-GTWY-9-xxx - the block

mapping message is sent each time the host device writes to the trigger register.

• By configuring a time period - the WI-GTWY-9-xxx will send the block mapping message

if this time period has elapsed since the last message has been sent.

• By configuring a real-time clock - the WI-GTWY-9-xxx will send the block mapping

message at the configured times.

• By a change-of-state within the I/O block. This can only occur for Write mappings. If a

value in the block changes by more than the sensitivity amount, then the block message will
be sent. You can enter a delay period such that the message is sent after the delay period.

Combinations of the above triggers can occur - for example, the block mapping message will be
sent if a change-of-state occurs, AND at the configured real-time, AND when the host device
writes to the trigger register.

4.5.2 Host Device Trigger

58

WI-GTWY-9-xxx Wireless Gateway V1.18

Each block mapping that is configured is allocated a status register in the range 9500 – 9999 (i.e.

one status register for a maximum of 500 possible block mappings). The status register for a
given block mapping is shown on the right hand side of the Block Mapping display (under the
heading “Status Lcn”). Bit 13 of the associated status register is the “Force bit” - if Bit 13 is
turned “on”, then the associated mapping is forced, or triggered. Depending on the module
version, a particular algorithm may apply to the setting of the force bit. This algorithm and details

of the block status registers are given in Appendix 1.

4.5.3 Time Period

On the Block Mapping display, there are two configuration windows - “Period” and “Offset” ­these determine the time period trigger and real-time trigger.

For a time-period trigger, select “Continuous” in the “Period” pop-down window. Under
“Offset” enter the time-period in seconds. In the above example, the mapping will be sent every
300 seconds or 5 minutes.

Note that the time period is after the last transmission - if the block mapping message is triggered
by the host device, or by a change-of-state, then the timer is reset and the time period starts again.

The “Offset” value can be set from 0 – 4095 seconds (68 minutes). If you do not want the
message to be sent on a time period, set the “Offset” value to zero.

If you want the block mapping to be sent only on time period (and not on change as well), select
the “Disable” box in the bottom left hand corner - this disables change messages for this block
mapping. If you want any changes sent within this Time period uncheck Disable box and enter
in time to wait before sending only the I/O that has changed in the Block.

59

WI-GTWY-9-xxx Wireless Gateway V1.18

4.5.4 Real-Time

The block mapping message can be sent at a real-time by setting the “Period” value. In this
example, “period” is set to 6 minutes - the message will be sent every 6 minutes starting at the
beginning of each hour. That is, the message will be sent at XX:00, XX:06, XX:12, XX:18,
XX:24 …. XX:54 - where XX represents any hour of the day.

If “Period” was set to 1 minute, then the message would be sent every minute, on the minute.

The “Offset” value provides an offset to the specified time. In this example, if the “Offset” was
set to 10 seconds, then the messages will be sent 10 seconds later - at XX:00:10, XX:06:10,
XX:12:10 etc.

The reason for the offset is to stagger messages with the same time setting. For example, if you
configure 5 block mappings all to be sent at 10 minutes, then the WI-GTWY-9-xxx will try to
send these messages at the same time - some of the messages will have to wait until the earlier
messages have been sent. If you are sending Read messages as well as Write messages, then the
return messages could clash with outgoing messages.

To avoid this, you can delay some messages using the Offset feature. For example, if you have 5
mappings to be sent at 10 minutes, then the first could have zero offset, the second 3 sec offset,
the third 6 sec offset etc.

If you do not wish to have a real-time trigger, set “Period” to continuous.
If you want the block mapping to be sent only on real-time (and not on change as well), select

the “Disable” box in the bottom left hand corner - this disables change messages for this block
mapping.

60

WI-GTWY-9-xxx Wireless Gateway V1.18

Setting the Clock

The clock within the WI-GTWY-9-xxx can be set by the host device, and read by the host
device. The WI-GTWY-9-xxx provides four clock registers for days/hours/minutes/seconds - the
registers are 4330 – 4333. On power-up, these registers are set to zero. Reg 4333 increments
each second, Reg 4332 increments each minute, Reg 4331 each hour and Reg 4330 each day.

The clock registers are used by the WI-GTWY-9-xxx for the real-time-clock trigger. The host
device can read these registers. The host device can also set the WI-GTWY-9-xxx clock at any
time by writing to the appropriate Set register. The Set registers are : 4340 – 4343. The procedure
for setting the real time clock via these registers depends on the module firmware version (to find
out what firmware version the module contains, simply display the diagnostics menu – see
section on diagnostics). The set registers can also be set via radio using appropriate I/O or block
mappings.

Item Clock Location Set Location

Days 4330 4340
Hours 4331 4341
Minutes 4332 4342
Seconds 4333 4343

Firmware versions up to 1.50:

Registers 4340 – 4343 are normally zero. When a value is written into one of these registers, the
WI-GTWY-9-xxx copies the value into the corresponding clock register, and then sets the Set
register back to zero. For example, if the host device writes a value of 7 into Reg 4341, the WI­GTWY-9-xxx will write 7 into 4331 and set 4341 back to zero.

Firmware version 1.50 and later:
Registers 4340 – 4343 will only be transferred to the corresponding clock registers when their

value changes from 0. For example to write a value of 7 to the hours register, first write the value
0 to the Set hours register 4341, then write the value 7 to the same register. (i.e. by always first
writing the value 0 to the Set register this ensures that the change-of-state from 0 will be
detected). Values must be held (i.e. not change) for approx 200msec to be detected.

61

WI-GTWY-9-xxx Wireless Gateway V1.18

4.5.5 Change-of-State

If a value in the block changes by more than the sensitivity amount, then the block message will
be sent (this can only occur for Write mappings). The sensitivity values are set under the
“Sensitivity” option as per section 4.6.

A delay time can be entered to reduce the number of change triggers in active systems. For
example, if 20 seconds is selected in the “Delay” window, then the change message will be sent
20 seconds after the change-of-state occurs - if other changes occur during the 20 second period,
all of these changes are sent in the one message.

The delay time can be set from 0 – 254 seconds.
If you do not wish change messages to occur, select the “Disable” box.

4.5.6 Block Read Mappings

A Read mapping is a request sent to another WI-GTWY-9 to return a block of values. Like the
Block Write mapping it can be triggered by a Real Time clock, Time period or by Host trigger
however the main difference is that the COS Delay is now a Response Timeout as shown below.

62

WI-GTWY-9-xxx Wireless Gateway V1.18

In the above example WI-GTWY-9#1 is performing a Block Read Request to WI-GTWY-9#2.

WI-GTWY-9#1 will send a block mapping request to WI-GTWY-9#2 who will then send a
block mapping from its I/O registers 52 for a count of 10 to WI-GTWY-9#2 I/O registers 52 –

61. This Block read will be performed using the real time clock at 10-minute intervals. A
response timeout of 5 seconds is used to indicate that if the Block read values have not been
received in 5 seconds then the Comms Fail bit for this block read mapping will be set.

It is not recommended to have the Response Timeout set to 0 seconds as a Comms fail bit will be
set upon transmission.

If the Response Timeout is greater than the Block mapping time period and radio’s are in a High
traffic or poor radio path then instances could occur that received messages could be from
previous block read mapping’s hence giving incorrect values.

If a need for frequent communications between modules is required then Block Write mapping’s
would be more suitable.

4.5.7 Mixing Normal Mappings and Block Mappings

Block mappings can include I/O Registers already used with normal I/O mappings.
For example, a remote WI-I/O 9-x I/O module could map a remote input to I/O Reg 743. At the

WI-GTWY-9-xxx, the host device could read I/O Reg 743, and you could also configure a block
mapping including this register to another WI-GTWY-9-xxx. You could write a block I/O Reg
700 – 800 to another WI-GTWY-9-xxx.

4.5.8 Block mapping to Internal I/O registers

Firmware version 1.80 and later:

63

WI-GTWY-9-xxx Wireless Gateway V1.18

The Block mapping feature will allow a Write Block Mapping to itself. This could be useful if
you have a global output to indicate a comms problem from any remote module by block
mapping the internal status registers to a local DIO output.

4.5.9 Comms Fail for Block Mappings

Each block mapping has an associated mapping number. Up to 500 block mappings may be
entered. A status register is maintained for each block mapping. The most significant bit of this
register contains the comm fail status.

If a block mapping does not receive an acknowledgement from the remote module, then the
comms fail status is set - this can be monitored by the host device.

4.5.10 “Repeater-only” Configuration

Any WI-GTWY-9-xxx module can act as a repeater unit. However a WI-GTWY-9-xxx may
need to be installed as a repeater only (that is, there is no host device connected). In this case,
the base WI-GTWY-9-xxx, the WI-GTWY-9-xxx-MD1 unit would normally be used as this is
the lowest cost of the WI-GTWY-9-xxx modules.

A repeater can be configured as a “Repeater-only” unit. The advantages are:

 the serial port will then provide on-line diagnostics (instead of off-line diagnostics), or
 WI-I/O-EX-1-S-1x serial I/O modules can be connected to the serial port - normally an

MD1 could not be used as the serial ports would already be in use by the protocol device, eg
PLC, etc.

64

WI-GTWY-9-xxx Wireless Gateway V1.18

4.6 Change Sensitivity & I/O Value Scaling

4.6.1 Change Sensitivity

“Change” messages for both individual I/O mappings and block mappings use a sensitivity value
to trigger the message. Sensitivities are configured for blocks of I/O registers - that is, each I/O
register does not have a unique sensitivity. You can configure up to 50 sensitivity values - that
is, there can be 50 blocks of registers with different sensitivities.

Enable scaling

In the above example, three sensitivity blocks have been configured:

1. I/O registers 0 – 49 have a sensitivity of 1000 (or 1.5% of the 16 bit range)

2. I/O registers 100 – 499 have a sensitivity of 250 (or 0.4% of the 16 bit range)

3. I/O registers 1000 – 2999 have a sensitivity of 100 (or 0.15% of the 16 bit range)
All of the registers between 0 and 49 have a sensitivity value of 1000. If register 34 has changed

value by more than 1000 since the last transmission for that register, then a change trigger will
occur for register 34. Sensitivity values are in decimal and can vary between 1 and 65535 (16­bit).

Up to 50 blocks of sensitivities can be configured. If a register is included in more than one
block, then the first sensitivity value configured will be accepted and later values ignored. If
Scaling is configured (refer next section), then the number of blocks is reduced to 25.

Registers which are not included in any block use the “default” sensitivity which is also user­configurable. In the above example, the default sensitivity is 1 and is the sensitivity for all I/O
registers not included in the three blocks.

Important Note. Sensitivity values need to be selected carefully for analogue or counting
registers as small values can result in a large number of change messages, which can overload the

65

WI-GTWY-9-xxx Wireless Gateway V1.18

radio channel. A sensitivity value of 1 in 65535 is a change of 0.0015%. If the host device
writes an analogue value to a WI-GTWY-9-xxx every 100msec, it will change by at least 1 bit
each time. A small sensitivity value will cause a change message to be sent every 100msec. If
there are many analogue values in the same situation, then there would be many change
messages every 100msec. Sensitivity values for analogue I/O should be set to be greater than the
normal process noise of the signal. For example, if a flow signal has a normal process
oscillation of 2.5%, then the sensitivity should be set to 3% (or a value of 2000) to avoid change
transmissions from the process oscillations.

4.6.2 I/O Value Scaling
Firmware version 1.76 and later:

The values in I/O registers can be scaled as the values are transferred to the data bus, or from the
data bus.

The I/O values in the WI-GTWY-9-xxx database registers are stored as 16-bit values (between 0
and FFFF hexidecimal or 0 and 65,535 decimal). Analog inputs at a WI-I/O 9-x I/O module are
scaled hex 4000 (dec 16,384) for 4mA and hex C000 (dec 49152) for 20mA. A 12 mA signal is
half-way in this range at hex 8000 (dec 32,768).

The reason for adding additional scaling between the WI-GTWY-9-xxx database (radio side) and
the data bus is to cater for external host devices which do not handle normal 16-bit values. Two
examples are:

 Honeywell Modbus gateways which only handle 12-bits values (0-4,095 decimal), and
 Sensor / analyzer devices with “signed 16-bit” values. A signed 16-bit value is a 15-bit value

with an additional bit to signify plus (0) or minus (1).
Scaling of I/O registers can be configured in blocks. Different blocks can have different scaling.
Note that scaling only affects values transferred in or out of the data bus port. It has no affect on

the radio side.

66

0

can be

WI-GTWY-9-xxx Wireless Gateway V1.18

Scaling is configured in the “Sensitivities” section of the configuration software. If you select a

new sensitivity/scaling block, you can select/deselect sensitivity or scaling or both. There is no
relationship between sensitivity and scaling -
we use the same configuration area as it is
convenient because both features use blocks of
I/O registers.

In the first example, a block of I/O registers is
configured for both sensitivity and scaling. I/O
block 0 to 79 (total of 80 registers) is
configured with a sensitivity value of 500. The
same block has scaling configured converting

If both
Sensitivity
and Scaling is
required,
either function

the range 16384-49152 on the radio side to 0­4095 on the data bus side.

This is an example of converting a 4-20mA
value to a “Honeywell 12-bit value”. Note that
the scaling works in both directions - for
values being read from the I/O registers to the
data bus, and values written from the data bus
to the I/O registers.

Any values outside of the scaling range are set
to the minimum or maximum value. For
example, if the data bus read a value of 10,000 from a register in this block, as it is less than the
minimum range on the radio side (the min. is 16,384) it will be transferred as 0 which is the
minimum value on the data bus side. If a value of 65,535 is read from another register, then as it
is more than the maximum value on the radio side (max. value is 49,152), then the value is
transferred as 4095 which is the maximum on the data bus side. This works in both directions -
if the data bus tries to write a value of 10,000 to an I/O register in this block, it will be written as
value 49,152 (which is the max. value on the radio side.

Data-bus

Value

4095

Transferring values from
Radio I/O Reg. to Data Bus

0 16384 49152 65535

Radio I/O Reg. Value

Radio

I/O Reg.

Value

49152

16384

Transferring values from
Data Bus to Radio I/O Reg.

0

0 4095

Data-bus Value

67

WI-GTWY-9-xxx Wireless Gateway V1.18

The second example shows another I/O block
(registers 81 to 1080) that has been selected
for scaling only - the sensitivity function has
been disabled (these registers will use the
default sensitivity of 2000 configured on the
main Sensitivity configuration screen).

In this example, the full 16-bit range (0-

65535) is scaled to “signed 16-bit values”. A
value greater than 32767 (which will be seen
as a negative value) can’t be written to the
data bus.

In the last example, Scaling has been
disabled for register block 1100 – 1109.
Only sensitivity functionality is being used.

Note: If Scaling is not used at all, up to 50
blocks can be configured with different
sensitivity values. However is Scaling is
used, then only half this number of blocks is
available.

68

WI-GTWY-9-xxx Wireless Gateway V1.18

4.6.3 Unit Details
Number of Transmission Retries. - Configurable value between 0 – 4, If the WI-GTWY-9 does

not receive an Acknowledgment from a message it will retry up to this configured amount.
Note: Setting to 0 will not allow for any retries. Not recommended for poor radio paths.

4.6.4 Number of TX only transmissions

Under I/O mappings and Block mapping’s is an
option for the WI-GTWY-9 to send messages as a
Transmit only. By default under each section all
messages will be acknowledged. Uncheck the
Acknowledge Message box to make the transmission
TX only.

In the unit details section a Configurable number of
TX only transmissions are available between 1 – 5.

As a Change of State occurs or Timed Update expires
each message will be sent this number of times.

Note: If setting Number of TX only transmissions to 1
ensure you have a good radio path and/or use Output
reset times at destination to indicate comms fails.

4.6.5 Reset on Buffer Empty (Firmware version 1.83 and later)
The WI-GTWY-9 has a series of internal buffers that are used for moving I/O between the Radio

Interface, I/O Database and Fieldbus Interfaces. There are a number of different buffers that the
WI-GTWY-9 uses.

The option of Reset Buffer on Empty will allow for the WI-GTWY-9 to be fully reset to clear its
buffers. By default this is disabled and can be used in applications of when a Gateway is used as
a repeater where there is excessive traffic and also in marginal radio paths. As each message is

69

WI-GTWY-9-xxx Wireless Gateway V1.18

passed via a repeater it will buffer this message in a queue and then forward on and wait for ACK
before it clears the buffer. If system is experiencing high radio message count and poor radio
path creating number of retries, cases could exist that the buffers will empty. Enabling the Reset
on Buffer Empty feature will reset the module and then continue to operate.

4.7 Serial Configuration - MODBUS

The WI-GTWY-9-xxx-MD1 module provides interface for Modbus Slave, Modbus Master and
Allen-Bradley DF1. This Modbus interface uses the Modbus RTU protocol - also known as the
Modbus Binary protocol. This manual assumes that the reader has a good understanding of the
Modbus or DF1 protocol.

4.7.1 MODBUS Slave

If you use the WI-GTWY-9-xxx Modbus Slave interface, then the host device will be a Modbus
Master device. The only configuration required for the Modbus slave interface is selecting the
Modbus address and serial port parameters. This is done in the “Serial Settings” screen. A valid
Modbus slave address is 1 to 255.

Each I/O register (and status register) in the WI-GTWY-9-xxx can act as one of the following
types of Modbus registers

00001-09999 = Output Coils (digital/single bit)
10001-19999 = Input Bits (digital/single bit)
30001-39999 = Input Registers (analog/16 bit)
40001-49999 = Output Registers (analog/16 bit)

For example:

• If the Modbus Master sends the WI-GTWY-9-xxx a “read” command for Modbus input

10457, then the WI-GTWY-9-xxx will respond with the value in I/O register 457.

• If the Modbus Master sends the WI-GTWY-9-xxx a “write” command for Modbus output

02650, then the WI-GTWY-9-xxx will write the value to I/O register 2650.

• If the Modbus Master sends the WI-GTWY-9-xxx a “read” command for Modbus input

30142, then the WI-GTWY-9-xxx will respond with the value in I/O register 142.

• If the Modbus Master sends the WI-GTWY-9-xxx a “write” command for Modbus output

40905, then the WI-GTWY-9-xxx will write the value to I/O register 905.

The WI-GTWY-9-xxx I/O register values are 16 bit (hexadecimal values ‘0000’ to ‘FFFF’, or
decimal 0 to 65535), regardless of whether the register represents a discrete, analog or count point.

70

WI-GTWY-9-xxx Wireless Gateway V1.18

The value of a discrete (digital) I/O point is stored in the WI-GTWY-9-xxx database as a

hexadecimal '0000' (“off”) or hex 'FFFF' (“on”). However the WI-GTWY-9-xxx will respond
with either a ‘0’ (“off”) or ‘1’ (“on”) to a digital read command from the Modbus master - these are
commands 01 and 02. Similarly, the WI-GTWY-9-xxx will accept ‘0’ or ‘1’ from the Modbus
master in a digital write command and store ‘0000’ or ‘FFFF’ in the database location - these
commands are 05 and 15.

The Modbus function codes that the WI-GTWY-9-xxx will respond to are shown in the table
below.

Supported Modbus Function Codes:
Function
Code

01 Read the state of multiple digital output points

02 Read the state of multiple digital input points

03 Read the value of multiple output registers

04 Read the value of multiple input registers

Meaning

05 Set a single digital output ON or OFF

06 Set the value of a single output register

07 Read Exception Status - compatibility - returns zero

08

15 Set multiple digital output points ON or OFF

16 Set multiple output registers

Loopback test
Supported codes 0 return query data
10 clear diagnostic counters
11 bus message count
12 CRC error count
14 slave message count

Analog I/O are 16 bit register values. A value of decimal 8192 (hex 2000) represents 0mA. A value
of 49152 (hex C000) represents 20mA. Each 1 mA has a value of 2048 (hex 0800) - a change of
4096 (hex 1000) is equivalent to a change of 2mA. A 4-20mA signal will vary between 16384 (hex

4000) and 49152 (hex C000). A 0-20mA signal will vary between 8192 (hex 2000) and 49152 (hex
C000).

Pulse counts are stored as a 16-bit register. When the register rolls over, from ‘FFFF’ (hex), the
next value will be ‘0001’. The register will only have a value of ‘0000’ when the remote module
starts up, and the previous count is lost. This value will indicate that the counter has reset.

Modbus Errors

Four Modbus error messages are reported to the Modbus Master. An error response is indicated
by the address of the return message being 128 plus the original slave address.

71

WI-GTWY-9-xxx Wireless Gateway V1.18

Supported Exception Codes:
Exception

Name Description

Code

01 Illegal function The module does not support the function code in the query
02 Illegal data address The data address received in the query is outside the

initialized memory area
03 Illegal data value The data in the request is illegal
06 Busy Unable to process message

4.7.2 MODBUS Master

If you use the WI-GTWY-9-xxx as a Modbus Master, then the host device/s will be Modbus
Slave device/s. If the RS485 port is used, then multiple Modbus Slave devices can be connected
to the WI-GTWY-9-xxx.

The WI-GTWY-9-xxx Modbus Master will generate Modbus read and write commands to the
Modbus Slave devices.

First read the above section on Modbus Slave operation, for an understanding of how the WI­GTWY-9-xxx handles Modbus registers, and the types of Modbus commands the WI-GTWY-9­xxx Master can generate.

The Modbus Master commands are configured in the “Serial Mapping” screen. The serial port is
configured in the same way as described in the above section on Modbus Slave.

To enter a Modbus command, select “New Serial Mapping”. The following example is a digital
write command which writes WI-GTWY-9-xxx I/O registers 20 – 25 (6 registers) to Modbus
outputs 00012 – 00017, at Modbus Slave address 1.

The entry under “I/O Register” is the first I/O register in the WI-GTWY-9-xxx to be transferred

- the “I/O count” is the number of registers to be transferred. If the selected Modbus slave does

72

WI-GTWY-9-xxx Wireless Gateway V1.18

not respond to the command, then the WI-GTWY-9-xxx will write a ‘FFFF’ value to one of its
own registers, configured under “CF Register” - in this case it is register 4800.

The “Command Type” selected is a write command (you can select read or write) - which
means that the values are sent from the WI-GTWY-9-xxx to the Modbus Slave. The type of
write command is a “Digital” write, meaning that the register values will be written as
digital/binary values”.

If the Modbus Slave device does not respond to the Modbus command, the WI-GTWY-9-xxx
will try another 3 times (“Max Retries” = 3). The Modbus command will be sent to the Modbus
Slave every 100msec. The address of the Modbus Slave is 1 (permissible addresses are 1 – 255).
Because a digital write command has been selected, the destination register type will be digital
outputs, with Modbus tag “0xxxxx”. The first destination Modbus location is 12 (or 00012) -
as there are 6 registers transferred, the destination locations will be 00012 – 00017.

The second example is a register read command to the same Modbus Slave (address 1). The
command requests the Modbus Slave to return the values of 10 registers which will be stored in
I/O registers 463 - 473 in the WI-GTWY-9-xxx. As the command is a “register read” command,
the target Modbus locations will be of the type 3xxxx. The starting location is 30001. So the
values of locations 30001 – 30010 in Modbus Slave 1 will be transferred to I/O registers 463 –
473 in the WI-GTWY-9-xxx.

73

WI-GTWY-9-xxx Wireless Gateway V1.18

The CF Register (“comms fail” register) acts as a digital alarm – the value of the register will
normally be 0, and will be set to FFFF (hex) if the slave device does not positively respond to the
serial command within Max Retries attempts. In the examples, the same CF Register (4327 – i.e.
DOT8) has been used for both serial mappings, such that the local digital output will be activated
if the slave fails to respond to either serial command. Alternately, any other internal register
could have been chosen and mapped via radio if desired.

To complete the Fieldbus Configuration, enter any other Modbus commands that may be
required to transfer I/O points between the WI-GTWY-9-xxx and the Modbus Slave devices.

Digital I/O

The value of a digital I/O point is stored in the WI-GTWY-9-xxx database as a hexadecimal '0000'
(“off”) or hex 'FFFF' (“on”). However the WI-GTWY-9-xxx will generate either a ‘0’ (“off”) or
‘1’ (“on”) to a digital output point (Coil) when sending commands to a Modbus slave - these are
commands 05 and 15. Similarly, the WI-GTWY-9-xxx will accept ‘0’ or ‘1’ from the Modbus
slave in response to a digital read command and store ‘0000’ or ‘FFFF’ in the database location ­these commands are 01 and 02.

Analog I/O

Analog I/O from the remote WI-I/O 9-x modules are 16 bit register value. A value of 8192 (hex

2000) represents 0mA. A value of 49152 (hex C000) represents 20mA. Each mA has value of
2048 (hex 0800) - a change of 4096 (hex 1000) is equivalent to a change of 2mA. A 4-20mA

74

WI-GTWY-9-xxx Wireless Gateway V1.18

signal will vary between 16384 (hex 4000) and 49152 (hex C000). A 0-20mA signal will vary
between 8192 (hex 2000) and 49152 (hex C000).

Pulse I/O

Pulse counts from the remote WI-I/O 9-x modules are shown as a 16-bit register. When the
register rolls over, from ‘FFFF’ (hex), the next value will be ‘0001’. The register will only have
a value of ‘0000’ when the remote module starts up, and the previous count is lost. This value
will indicate that the counter has reset.

Modbus Retry Delay

The WI-GTWY-9-xxx Modbus Master configuration includes a feature to limit the frequency at
which slave devices are polled for data. The WI-GTWY-9-xxx will poll each Modbus slave in
order. If there is no delay time entered, the WI-GTWY-9-xxx will poll as quickly as it is able to. If
there is a delay time entered, then this delay time will occur between each poll message.

When updated values are received from the WI-I/O 9-x radio network, the current polling sequence
is interrupted, and the new values are written immediately to the appropriate slaves.

Re-tries on the Serial Port

When communicating with Modbus slaves, the WI-GTWY-9-xxx may be configured to re-try (or
re-send) a message zero or more times if no response is received from a slave. If all retries are
used up, that slave is flagged as being in communication failure. Further attempts to
communicate with the slave will have zero re-tries. When a successful response is received from
the Modbus slave, the communication failure flag is reset and the configured number of re-tries
will be used. This means that an off-line slave device will not unduly slow down the
communications network.

Comms Fail

A “Comms Fail” image location in the WI-GTWY-9-xxx database. This image location should
be in the range 4500 to 4999. If a response is not received from the Modbus slave after all re­tries have been sent, the WI-GTWY-9-xxx will set this Comms Fail image location to
hex(FFFF). When the WI-GTWY-9-xxx sends the next poll for this I/O Command, it will not
send any re-tries if a response is not received to the first message. When a response is eventually
received, the WI-GTWY-9-xxx will reset the value in Comms Fail image location to 0, and the
normal re-try sequence will operate.

Different I/O Commands can use different Comms Fail image locations, however we recommend
that you use the same image location for all I/O Commands to the same Modbus slave address.

4.8 Serial Configuration - DF1

The WI-GTWY-9-xxx DF1 Driver allows the WI-GTWY-9-xxx to communicate with Allen­Bradley devices supporting the DF1 protocol. Supported commands allow communication with
500 CPU devices (SLC and Micrologix) and with PLC2 series devices. DF1 offers both full­duplex (point to point) and half-duplex (multidrop) operation. The WI-GTWY-9-xxx only
supports the full-duplex operation - this is the default DF1 mode on most equipment. DF1 full­duplex is a “peer-to-peer” protocol. Either DF1 device can initiate commands to the other

75

WI-GTWY-9-xxx Wireless Gateway V1.18

Function

device, and both devices will respond to commands from the other device. The WI-GTWY-9­xxx can act as both a command initiator and a command responder.

An Application Note and configuration files are available describing how to configure an Allen­Bradley PLC to communicate with a DF1 WI-GTWY-9-xxx. This is available from the
Weidmuller, Inc. website www.weidmuller.com

The WI-GTWY-9-xxx will initiate the following command types to a command responder,
according to the configuration. The WI-GTWY-9-xxx will automatically generate the correct
command type depending on the configuration you enter. The WI-GTWY-9-xxx will also
respond to these command types if they are sent from a command initiator.

Command Description Code

Comment

Code

Protected Write 0x00
Unprotected Read 0x01
Diagnostic Status 0x06

NONE
NONE

0x00

PLC2 series and SLC / Micrologix
PLC2 series and SLC / Micrologix

Diagnostic Commands
Echo message 0x06 0x00
Unprotected Write 0x08

NONE

PLC2 series and SLC500 / Micrologix
Typed logical Read 0x0F 0xA2 Type SLC500 and Micrologix
Read Bits

0x0F

0xA2 0x85 Reads MSB of each WI-GTWY-9-xxx I/O

register and writes the bits to the destination
register, starting at the LSB of the register.

Min. transfer is 16 bits.
Read Integers
Read Long Ints

0x0F
0x0F

0xA2 0x89 Return signed 16 bit value

0xA2 0x91 Unsigned 16 bit register per long-word
Typed logical Write 0x0F 0xAA Type SLC500 and Micrologix
Write Bits

0x0F

0xAA 0x85 Writes bits from the source register, starting

at the LSB, to the MSB of a block of WI­GTWY-9-xxx I/O registers. Min. transfer is

16 bits.
Write Integers
Write LongIntegers

The SLC and Micrologic PLC’s read/write two types of registers. An “Integer” has a signed 16
bit value (-32768 to 32767). A “Long Integer” has a 32 bit value. The WI-GTWY-9-xxx registers
contain an unsigned 16 bit value (0 to 65535). We recommend that you use Long Integer read/write
commands - the upper 16 bits of the 32 bit value will be ignored. Refer to more information in the
Analog I/O and Pulse I/O sections below. The PLC2 uses unsigned 16 bit registers in the same
format as the WI-GTWY-9-xxx.

The WI-GTWY-9-xxx DF1 driver will update remote outputs whenever a data value changes by
more than the I/O register sensitivity. If the response from a data request contains a changed data

76

0x0F
0x0F

0xAA 0x89 Writes a signed 16 bit value
0xAA 0x91 Low 16 bits of long-word placed in register.

Upper 16 bits ignored.

WI-GTWY-9-xxx Wireless Gateway V1.18

value, the new value will be transmitted to the remote WI-I/O 9-x on the radio network.
Similarly, if the WI-GTWY-9-xxx receives a command to change a data value, the new value

will be transmitted to the remote WI-I/O 9-x module.

The DF1 commands are configured in the “Serial Mapping” screen. The serial port should be
configured in the same way as the host device. If the WI-GTWY-9-xxx acts only as a command
responder, no further configuration is required.

If the WI-GTWY-9-xxx acts as a command initiator, you can enter a “Request Delay” between
commands sent to the host. To enter a DF1 command, select “New Serial Mapping”. The

following example is a file write command which writes WI-GTWY-9-xxx I/O registers 80 –
104 (25 registers) to DF1 files I3.1 to I27.1 at DF1 address 2.

The entry under “I/O Register” (see below) is the first I/O register in the WI-GTWY-9-xxx to be
transferred - the “I/O count” is the number of registers to be transferred.

The “Command Type” selected is a file write command (you can select read or write) - which
means that the values are sent from the WI-GTWY-9-xxx to the host device. The type of write
command is a “Integer” write, meaning that the register values will be written as register values.

The DF1 address of the host device (or “Slave”) is 2.

77

WI-GTWY-9-xxx Wireless Gateway V1.18

Discrete I/O

The value of a digital I/O point is stored in the WI-GTWY-9-xxx database as a hexadecimal '0000'
(“off”) or hex 'FFFF' (“on”). However the WI-GTWY-9-xxx will generate either a ‘0’ (“off”) or
‘1’ (“on”) to a binary file when initiating a “Typed Logical Write” command or responding to a
“Typed Logical Read” command. Similarly, the WI-GTWY-9-xxx will accept ‘0’ or ‘1’ from
responding device to a “Typed Logical Read” command or from an initiating device generating a
“Typed Logical Write” command and store ‘0000’ or ‘FFFF’ in the database location. The file type
for a binary file (bit file) is 0x85.

In the PLC (that is, the DF1 host device), discrete values (“bits”) are stored in 16 bit registers -
each register stores 16 bit values (or 16 discrete values). You can only transfer these values in
groups of 16. That is, a read or write command will transfer a minimum of 16 bits to/from the WI­GTWY-9-xxx. If more than 16 are transferred, then they will be transferred in multiples of 16.
You cannot transfer an individual bit - you must transfer the 16 bits in that PLC register, which
will be transferred to/from 16 consecutive I/O registers in the WI-GTWY-9-xxx.

Note: The PLC reads or writes digital bits starting at the LSB of each register. In the WI-GTWY­9-xxx, only one bit is written to each I/O register, and this is the MSB.

Analog I/O

Analog I/O from the remote WI-I/O 9-x modules are 16 bit register value. A value of 8192 (hex

2000) represents 0mA. A value of 49152 (hex C000) represents 20mA. Each mA has value of
2048 (hex 0800) - a change of 4096 (hex 1000) is equivalent to a change of 2mA. A 4-20mA
signal will vary between 16384 (hex 4000) and 49152 (hex C000). A 0-20mA signal will vary
between 8192 (hex 2000) and 49152 (hex C000).

78

WI-GTWY-9-xxx Wireless Gateway V1.18

Note: If analog values are read to and written from an integer file in an SLC or Micrologix CPU,

integer files contain 16 bit signed values. These represent values in the range -32768 to 32767. The
data values from the WI-I/O 9-x modules are treated as 16 bit unsigned values. To convert the data
from an analog input, move the data from the integer file to a long file (MOV command) then mask
out the high 16 bits (MVM with mask value FFFF). This will result in a long integer value in the
range 0 to 65535.

Alternatively, use a long integer file type to transfer the analog value as a long integer in the range
0-65535.

Pulse I/O

Pulse counts from the remote WI-I/O 9-x modules are shown as a 16-bit register. When the
register rolls over, from ‘FFFF’ (hex), the next value will be ‘0001’. The register will only have a
value of ‘0000’ when the remote module starts up, and the previous count is lost. This value will
indicate that the counter has reset.

Note: The values from the WI-GTWY-9-xxx module are 16 bit unsigned values. When they are
copied to the Integer file in the PLC, they will be treated as 16 bit signed values. These values
may be converted to the original (unsigned) values using the MOV and MVM instructions
described in the previous section (Analog I/O). Again, using a Long Integer type will avoid this
problem.

500 CPU (SLC and MicroLogix) file types and addressing

The WI-GTWY-9-xxx provides a linear address space of 10,000 data words. This is compatible
with PLC2 addresses, but does not match the addressing used by the 500CPU modules (SLC and
Micrologic). These address data by file number and file offset. To address an I/O register, L, in
the WI-GTWY-9-xxx, use DF1 file number L / 100, with the remainder value (L % 100) as the
DF1 file offset. For example, to read I/O register 2643 in the WI-GTWY-9-xxx, read from file
number 26, offset 43.

79

WI-GTWY-9-xxx Wireless Gateway V1.18

4.9 Fieldbus Configuration

All WI-GTWY-9-xxx modules (except MD1) have separate internal hardware comprising the
Fieldbus Interface, consisting of a separate microprocessor and appropriate hardware for the
network connection. This Fieldbus Interface handles all fieldbus communications, and transfers
I/O in the Fieldbus Interface Registers to/from the fieldbus. Conversely, the WI-GTWY-9-xxx
Radio Interface handles all radio communications, and transfers I/O in the Radio Interface
Registers to/from the radio network. For I/O transfer between the radio network and the fieldbus
network, I/O Registers in the Radio Interface must be linked with registers in the Fieldbus
Interface using configuration software.

Depending on the fieldbus protocol, the size of the Fieldbus Interface may be limited (for
example, the Profibus Slave interface supports only 416 bytes I/O). The Radio Interface
supports 10,000 registers, of which 4300 are general-purpose I/O registers. Each Radio Interface
register is 16-bit, even for discrete (or “digital”) input or output values. The Fieldbus Interface
comprises a block of 8-bit bytes (referred to as “locations”). Digital I/O can be packed - each
fieldbus location can hold 8 digital inputs or outputs. Analog or pulse values can be stored as a
low resolution 8-bit value (a single fieldbus location) or as a high resolution 16-bit value (two
consecutive fieldbus locations).

To optimize I/O usage, the WI-GTWY-9-xxx provides a flexible method of data transfer between
the Radio Interface and the Fieldbus Interface. The user configures links between the Radio
Interface and Fieldbus Interface via Fieldbus Mappings in the WI Series Configuration Software.

ANTENNA

RADIO

DRIVER

RADIO

INTERFACE

I/O

DATABASE

I/O REGISTERS

WRITE

DATA BUS

FIELDBUS

INTERFACE

FIELDBUS

LOCATIONS

READ

The diagram shows in more detail the relationship between the Radio Interface and Fieldbus
Interface.

80

Radio Interface

Reg

Ethernet/IP allows 6 output

WI-GTWY-9-xxx Wireless Gateway V1.18

Fieldbus Interface

IN Area

Profibus 244 Bytes

Modbus/TCP 2048 Bytes

Ethernet/IP allows 6 input

Write
from
I/O

connections; each
connection Max 512 bytes

Modbus Plus 2048 bytes

Read from
Host

10,000 x 16-bit

I/O Registers

DeviceNet 512 bytes

OUT Area

Profibus 244 Bytes

Modbus/TCP 2048 Bytes

Read to
I/O Reg

connections; each
connection Max 512 bytes

Modbus Plus 2048 bytes
DeviceNet 512 bytes

Write from
Host

WI-GTWY-9-

Fieldbus

4.9.1 Fieldbus Mappings

The Fieldbus Interface is divided into two distinct areas. The IN Area contains input data that is
made available to the host device. The OUT Area contains output data from the host device. This
is in contrast to the Radio Interface, in which each 16-bit register can be used as input or output.
Also note the size of the Fieldbus Interface is variable, depending on the type of fieldbus.

WI Series Configuration Software provides user configurable Fieldbus Mappings to link the
required Fieldbus I/O to the Radio Interface. Write mappings write I/O values from the Radio
Interface to the Fieldbus IN Area. Read mappings read I/O values from the Fieldbus OUT Area
to the Radio Interface.

If you want to send a value from the WI-GTWY-9-xxx to the host device, use a Fieldbus Write
Mapping. The input data from the Radio Interface (i.e. input data that has either come in from the
radio or from local I/O) will be transferred to the IN Area via the fieldbus write mapping. The
host device can then read this input data from the IN Area.

If you want to send a value from the host device to the WI-GTWY-9-xxx, use a Fieldbus Read
Mapping. The host device can write output data to the OUT Area. The output data from the OUT
Area will then be transferred to the Radio Interface via the fieldbus read mapping. The radio
driver can then either send this output over the radio or to a local I/O.

81

WI-GTWY-9-xxx Wireless Gateway V1.18

Several different configurable transfer modes are also available for fieldbus mappings to ensure
the I/O is formatted according to the requirements of the particular fieldbus protocol or host
device. The six possible types of Fieldbus Mapping are outlined in the table below.

Fieldbus Mapping Types

Transfer Mode Read Mapping Write Mapping

Single Bit

Byte (8-bit)

Word (16-bit)

The WI-GTWY-9-xxx reads a block
of consecutive bits from Fieldbus
OUT Area and stores each bit in
consecutive I/O Registers, as hex
FFFF or 0000.

The WI-GTWY-9-xxx reads
consecutive bytes (8-bit values)
from Fieldbus OUT Area and stores
each byte in the most significant 8­bits of a consecutive I/O register.

The WI-GTWY-9-xxx reads
consecutive words (2x8-bit values)
form Fieldbus OUT Area and stores
each word in a consecutive I/O
Register.

The WI-GTWY-9-xxx takes the
MSB (most significant bit) of a
block of consecutive I/O Registers,
converting the 16 bit I/O register
values into 0 or 1, and writes to
consecutive bits of Fieldbus IN
Area.

The WI-GTWY-9-xxx takes the
most significant 8-bits of
consecutive I/O registers and writes
them to consecutive bytes (8-bit
values) of the Fieldbus IN area.

The WI-GTWY-9-xxx takes
consecutive I/O registers and writes
them to consecutive words (2x8-bit
values) of Fieldbus IN Area.

4.9.2 Transfer Mode

Radio Interface registers are all 16-bit general-purpose input or output registers. That is, analog
inputs or outputs are stored as a 16-bit value. Digital inputs or outputs occupy a whole 16-bit
register and are stored as either 0000(hex) or FFFF(hex) for compatibility with the Radio
Protocol. However, the Fieldbus Interface may contain (depending on the protocol) significantly
less registers than the Radio Interface (see diagram above). Also, certain protocols may require a
different I/O structure than that used by the Radio Interface registers. Consequently, depending
on the fieldbus mapping transfer mode (see above table), Radio Interface registers may or may
not be compressed.

“Word” transfer mode offers no compression, but rather a direct transfer of 16-bit registers
between Radio Interface and Fieldbus Interface. This mode would suit the transfer of registers
containing pulse counts or analog values with no loss of resolution.

“Byte” transfer mode operates on only the most significant BYTE (the first 8 bits) of Radio
Interface registers, but allows these bytes to be consecutively packed in the Fieldbus Interface.
This mode would suit the transfer of analog values in low-resolution, in cases where I/O space is
at a premium. Byte Address Mode is recommended when using byte transfer mode (see Address
Mode section below).

Bit transfer mode operates on only the most significant BIT of Radio Interface registers, but
allows these bits to be consecutively packed in the Fieldbus Interface. This mode would suit the

82

WI-GTWY-9-xxx Wireless Gateway V1.18

transfer of digital I/O in cases where it is not desirable (or possible) to use a whole 16-bit

register just to store a 0 or 1 value.

4.9.3 Endianess

Endianness is the convention that two parties that wish to exchange information will use to send
and receive this information if the information needs to be broken into smaller packets, i.e. data
transmission, radio, etc.

Integers are usually stored as sequences of bytes and the two more common sequences used are
little-endian and big-endian.

Most computer processors agree on bit ordering however this is not always the case.
Below is an analogy of what can happen if the bit orders are different between devices.
Imagine that Device ‘A’ wants to send a hexidecimal value "ABCD" to another devce’B’.

However device’A’ can only do so 2 bits at a time. As device ‘A’ uses big-endian order, it will
first send “AB” and then “CD”.

Device ‘B’ needs to be using the same convention as Device ‘A’ when receiving this information
such that when it receives the first part “AB” it knows that this is the beginning of the value, then
when it receives the next part “CD” it knows that it goes after the first part (big-endian).

If Device ‘B’ is unaware and assumes the inverse (litte-endian), it will end up with the value
around the wrong way, e.g. “CD” and then “AB”, eg “CDAB”

Now if you convert these hexidecimal values back into decimal you will see a significant
difference, which can expalin why when connecting different devcices together the values
sometimes do not line up.

“ABCD” = 43981
“CDAB” = 52651

4.9.4 Address Mode

Configuration software allows the Fieldbus Interface IN and OUT areas to be addressed as an
array of 8-bit bytes (Byte Address Mode) or an array of 16-bit words (Word Address Mode). The
address mode may be required to change depending on the transfer mode, the protocol, or the
particular host device. The Address Mode option is included so that the configuration software
can be setup to use the same I/O addressing method used by the host device. The actual structure
of I/O in this database can only be physically altered via the transfer mode.

The Fieldbus Interface IN and OUT areas are simply a block of I/O memory, exchanged
according to the configured protocol. For example, with a Profibus slave that supports 244 bytes
of inputs, the fieldbus interface IN area could be addressed either as byte locations 1 to 244 or as
word locations 1 to 122. Note that in either case, the underlying database structure is unchanged,
the difference is limited to the Fieldbus IN/OUT Area address that is displayed by configuration
software.

Certain protocols have an inherent or preferred byte or word structure – for example, Modbus is
a protocol that usually operates on 16-bit (word) registers. Consequently, configuration software
will default to the most common address mode for that protocol. Configuration software may
also apply an offset and/or scaling to the IN/OUT Area addressing to suit the particular protocol.

83

WI-GTWY-9-xxx Wireless Gateway V1.18

For example Modbus/TCP areas start from location 1, but other fieldbuses may start at location

0.
Note:

• The Fieldbus Interface IN and OUT Area both number from 0 - that is, there is an input 0 as

well as an output 0 (an offset may apply for some protocols).

• All IN/OUT Area locations accessed by the fieldbus must be part of a fieldbus mapping in the

WI-GTWY-9-xxx - that is, if a host device is writing to bytes 0 – 100 in the OUT Area,
there must be at least one fieldbus read mapping that uses these locations - if not, the
Fieldbus Interface will generate an error response message.

• Fieldbus mappings to/from the IN/OUT areas should always start at location 0 if possible (or

the lowest available unused location). Configuration Software will always automatically
choose the next lowest available location – it is strongly recommended that this topology be
used so as not to place unnecessary processing overhead on the module.

4.9.5 Fieldbus Mapping ConfigurationThe example below shows the Fieldbus Mapping

configuration screen when adding new or editing existing Fieldbus Mappings. Starting
from the left of the screen, the I/O Register selection specifies the starting I/O Register
from the Radio Interface (press the “…” button to make a selection graphically). The I/O
Count parameter specifies how many consecutive I/O Registers are to be transferred or
linked. Command Type and Transfer Mode specify the type of Fieldbus Mapping (see
Fieldbus Mappings table above). Finally, I/O Location specifies the IN or OUT Area
location in the Fieldbus Interface (see earlier diagram).

84

WI-GTWY-9-xxx Wireless Gateway V1.18

Three Fieldbus Mappings are illustrated in the example above. Note that “Word Address Mode”
is selected, meaning that the Fieldbus Interface IN and OUT Areas will be treated as word­addressed arrays by configuration software. The parameters for each fieldbus mapping were setup
using the mapping configuration screen as described above.

The first Fieldbus Mapping is a “Write WORD” mapping, writing I/O Registers 10 – 15 from the
Radio Interface to word-locations 1 – 5 in the Fieldbus IN Area. Because the transfer mode is
“word” complete 16-bit registers are transferred.

The second mapping is a “Read BIT” mapping, reading 12 bits from Fieldbus OUT Area word-
location 1(word address mode is selected) to I/O Registers 30 – 41. Remember that for such a

85

WI-GTWY-9-xxx Wireless Gateway V1.18

BIT transfer, that each individual bit in the Fieldbus Interface is transferred to an entire 16-bit I/O
Register. Note also that there is a word-location 1 for both the Fieldbus OUT and IN areas.

The third mapping is another “Read BIT” mapping, reading 8 bits from Fieldbus OUT Area
word-location 1 to I/O Registers 4320 – 4327 (i.e. local DOT 1 – 8). Note here that we are again
reading from Fieldbus OUT Area word-location 1 (as with the previous mapping). However,
since each word-location contains 16-bits and the last mapping used only 12 of those, we have
been able to follow on from the previous mapping (see below).

The Fieldbus Register Selection screen above was shown when selecting the Fieldbus OUT Area
location for the third mapping in the above example. This screen shows the currently used

portion of the Fieldbus OUT Area, and allows the user to graphically select the location for the
current mapping. NOTE – by default configuration software will always choose the next
available Fieldbus Interface register for fieldbus mappings. Allowing configuration software to
automatically make the selection is strongly recommended wherever possible.

Clicking on the required location in the top panel will alter the currently selected word-location.
Further, clicking individual bits in the “Bit Usage” panel at the bottom of the screen, allows the
current BIT mapping to be specified at the bit-level of the currently selected word.

The lighter blue areas indicate the extent of already existing fieldbus mappings. It can be seen
that bits 0 – 11 of word location 1 have already been used (by the second mapping in the
example). The dark blue area in the register selection screen above shows the extent and location
of the current fieldbus mapping graphically. The status panel at the bottom of the window always
displays the extent of the current selection, which can be seen to be word 1, bit 12 to word 2, bit

3.

86

WI-GTWY-9-xxx Wireless Gateway V1.18

A status location (4500) may be used to give the host device status information about the

Fieldbus Interface. This register will be value 0x0000 if the Fieldbus Interface is “on-line” and
communicating with the fieldbus, or value 0xFFFF if it is “off-line”. If you wish to use a status
register, select the “Enable Status Location” box. This register could be mapped to a remote
module or local output as an alarm.

4.10 Fieldbus Configuration - Profibus Slave

The Profibus WI-GTWY-9-xxx-PR1 acts as a Profibus DP Slave - the host device is a Profibus
Master. If you use the WI-GTWY-9-xxx with a PLC, the PLC configuration tool will require a
GSD file so it can recognize the Profibus interface in the WI-GTWY-9-xxx. This file loads into
the PLC configuration software (for example, Siemens STEP 7). The file is available on the
same CD as the configuration software or from the Weidmuller, Inc. web page
www.weidmuller.com.

Configuration of the Profibus Fieldbus Interface comprises allocating a Profibus Slave address to
the WI-GTWY-9-xxx, and configuring links between the Radio Interface and the Fieldbus
Interface (i.e. Fieldbus Mappings).

The Profibus address can be set in the “Fieldbus Config” screen or via the rotary switch on the
end-plate of the module- valid slave addresses are 1 – 126. If the “Enable Rotary Switch” box is
not selected, then the address entered in the program will be used and the rotary switch value
ignored. If the “Enable Rotary Switch” box is selected, then the address entered in the
configuration program will be ignored and the rotary switch read on start-up of the WI-GTWY-9­xxx.

The Profibus interface has 416 bytes, of which 244 can be used as input bytes, or 244 can be used
as output bytes.

Note: For bit transfers, the bit offset is counted from the least significant bit (LSB) of the byte
(with bit 0 being the LSB) - if you transfer 3 bits with a bit offset of 5, then you will transfer
bits 5-7 of the byte. This is different than the Ethernet unit which counts the offset from the most
significant bit - refer next section.

The fieldbus write mapping in the example below transfers 5x16-bit registers (words) from the
radio interface to the fieldbus interface. Care should be taken that the Profibus Master device
does not attempt to access more I/O than has been setup via fieldbus mappings. i.e. in the
example below, the Profibus Master can read a maximum of 5 words (10 bytes) only from the
WI-GTWY-9-xxx.

87

WI-GTWY-9-xxx Wireless Gateway V1.18

4.11 Fieldbus Configuration - Profibus Master

The WI-GTWY-9-xxx-PR2 implements a complete Profibus-DPV0/DPV1 master. The hardware
is optimized for high throughput and can be used in mono or multi master networks up to 12
Mbit/s. Up to 125 slaves with a total max of 2048 byte input and 2048 byte output data can be
connected.

4.11.1 GSD File

Each device in a Profibus network is associated with a GSD file, containing all necessary
information about the device. In general, the Profibus slave device manufacturer supplies the
relevant GSD files. WI Series Configuration Software uses these files during network
configuration.

4.11.2 Protocol and Supported Functions

The WI-GTWY-9-xxx-PR2 implements a complete Profibus-DPV0/DPV1 master and includes
the following features:

• Up to 125 slaves can be connected

• Up to 2048 bytes input &output data

• Up to 12 Mbit/s on Profibus

• RS-485 optically isolated Profibus interface with on-board DC/DC converter

• Configuration via WI Series Configuration Software

• Acyclic Communication (DPV1)

• Alarm Handling (DPV1)

4.11.3 Configuration

Profibus network configuration is performed via the WI Series Configuration Utility. The WI­GTWY-9-xxx Profibus Master provides up to 2048 bytes of inputs and 2048 bytes of outputs in

88

WI-GTWY-9-xxx Wireless Gateway V1.18

the fieldbus interface for I/O on the Profibus network. I/O in the fieldbus interface must be

linked with I/O in the radio interface via appropriate fieldbus mappings (see 4.8 Fieldbus
Configuration above) for I/O transfer with the radio network.

Configuration of the Profibus network is through the Profibus Network Config tab in WI Series
Configuration Software. Through this section, the entire (local) Profibus network including I/O
data transfer with Profibus slaves is configured. Before a Profibus slave is configured on the
network, its corresponding GSD file must be installed. To install a GSD file choose File|Install
GSD File. Once the GSD file(s) have been installed, the devices corresponding to those GSD
files will appear as devices on the Profibus DP treeview on the left side of the network
configuration screen.

The Profibus network configuration screen is divided into three main areas (see below). The left
hand Profibus DP Treeview displays all the available slaves, i.e. those whose corresponding GSD
files have been installed. The right hand top section Busview displays graphically the devices that
are currently configured on the Profibus network – individual devices can be selected here and
their I/O configuration and other properties viewed/altered. The right hand bottom section
Listview shows the I/O configuration of a particular slave when a slave device is selected in the
busview, or the network configuration (i.e. what slaves are configured and their corresponding
addresses) when the Profibus master node is selected in the busview.

300Adding a Slave to the Network

WI-GTWY-9

Master (0) WI-GTWY-9

To add a Profibus slave to the network, locate the required slave and simply drag the slave icon
onto the visible bus cable on the busview, or right click the required slave and choose add to
network. To add a slave with a specific Profibus node address to the network, locate the required
slave and drag the icon to the network listview (ensure that the master node is selected in the
busview so that the network list is displayed in the listview rather than the slave I/O

89

WI-GTWY-9-xxx Wireless Gateway V1.18

configuration list). The above example shows a slave device being added to the network at node
address 7.

Slave Address

To change the node address of a slave already configured on the network, locate the slave in the
network listview and drag it to the position in the list corresponding to the desired address.
Alternately, the slave address can be modified from the module properties page (see below).

Module Properties (Slave)

To display the properties of a given slave, right click the required slave in the busview and
choose properties (or double click the icon in the busview). Under the general tab, various
details (including GSD file details) relating to the selected slave device are displayed. Several
configurable options are also available (see below).

Profibus Address

The actual Profibus address of the selected slave is shown in the address selection box. Only

available addresses are listed and can be selected as new address.

Watchdog

According to the Profibus specification, a slave device may be configured with a watchdog
function such that the master must poll the slave within a defined interval. If this feature is
enabled and the master fails, the slaves watchdog timer will timeout and the slave will reset
itself.

90

WI-GTWY-9-xxx Wireless Gateway V1.18

Group Assignment

If the slave supports sync/freeze functionality, it can be assigned to the masters sync/freeze
groups by clicking on the checkboxes. The sync/freeze assignment of the groups is also displayed
(these can be changed via the master properties dialog).

Parameter Assignment

A slaves user-specific parameters can be changed via the parameter assignment page. User­specific parameters for a slave device are defined in the corresponding GSD file for the device,
the definition of which are device-specific and should be found in the documentation for the
device.

Parameters can be altered via combo boxes or via direct input of hexadecimal values. The
hexadecimal values for the user_prm_data are displayed at the bottom of the screen and can be
edited directly (consult the device specific documentation for the meaning of these values).

91

WI-GTWY-9-xxx Wireless Gateway V1.18

Adding I/O to a Slave

The possible I/O combinations for a given slave may be fixed or configurable (i.e. modular)
depending on the GSD file for the device. When the I/O configuration is fixed, the fixed I/O are
always defined whenever the device is added to the network. However, for modular devices, the
I/O configuration must be assigned manually.

The GSD file for a modular slave will define a maximum number of I/O slots – each of which
may be configured with an I/O module. The available I/O module’s for a particular slave can be
viewed by expanding the slave node in the Profibus DP Treeview. To add an I/O module to a
slave, first ensure the required slave is selected in the busview, then drag the required I/O module
into a spare slot of the slave listview.

When an I/O module is added to a slave, configuration software will automatically assign that
I/O to the next available space in the fieldbus interface. The input and output addresses that are
assigned here will correspond to the locations that must be transferred via fieldbus mappings in
order to make the I/O available to the radio network. The input and/or output address assigned by
software for a given I/O module can be altered by double clicking on that I/O module entry in the
slave listview (see above).

The start address in the fieldbus interface for the inputs or outputs can be altered in the
corresponding Start field as shown above. Since the WI-GTWY-9-xxx provides for up to 2048
bytes of inputs and 2048 bytes of outputs, the possible range for inputs or outputs is 0 – 2047.

92

WI-GTWY-9-xxx Wireless Gateway V1.18

I/O modules may also have associated user parameter data defined by the corresponding GSD

file. The meaning of these parameters (if applicable) is specific to the slave implementation, and
may be altered via the Parameter Assignment tab of the Module Properties form.

Configuration software also provides an additional I/O module to all slaves that is not defined in
the GSD files, which is the Universal Module. The universal module allows the input/output
length, unit, and consistency to be assigned custom values as required – however not all slave
implementations will support this feature (consult the specific slave documentation for details).

The Length parameter defines the length of the input or output module in either bytes or words
(according to the corresponding Unit parameter). The data consistency over the Profibus network
may be applied to the selected unit (i.e. byte or word) or to the total length of the input or output
selection.

Depending on the particular slave, Manufacturer Specific Data may also apply to an I/O module.
This data is a string of hexadecimal bytes, the meanings of which (if applicable) are device
specific and should be detailed in the documentation for the particular device.

Master Properties

The Profibus master WI­GTWY-9-xxx has some
configurable properties
that affect the entire
Profibus network. These
properties can be accessed
by double clicking the
master icon in the network
busview, or right-clicking
the icon and choosing
properties.

Profibus Tab

The Address parameter
specifies the actual
Profibus address of the
Profibus master (default =

0). Only available
addresses are listed and
can be selected as new
address. The serial baud
rate for the entire Profibus
network is selected – this
is the baud rate that will be used by the master and therefore must also be supported by all slave
devices on the network. Most slaves will support auto baud rate detect, but it should be ensured
that any slave on the network supports the configured baud rate.

The Profile parameter controls the assignment of Bus Parameters for the Profibus network. In
the single master (default) profile, the bus parameters are calculated automatically by
configuration software and are optimized for speed – no other masters may be connected to the

93

WI-GTWY-9-xxx Wireless Gateway V1.18

network. The User Defined profile allows the bus parameters to be manually configured for
special network configurations and should only be used if the user is familiar with the individual
Profibus parameters (see Bus Parameters Tab below).

The storage format determines if word values are stored in big endian (Motorola – most
significant byte has lowest address) or little endian (Intel – Least significant byte has lowest
address) format.

Group Properties Tab

A DP master can send the SYNC and/or FREEZE control commands simultaneously to a group
of slaves for synchronization purposes. Therefore the slaves must be assigned to Sync/Freeze ­groups. Up to 8 groups may be configured as SYNC and/or FREEZE groups. Any slaves that are
configured to belong to a particular group (via that slaves module properties|group assignment
configuration) may be synchronized using the Message Interface instruction
SET_SLAVE_MODE (see section on the Message Interface below).

Bus Parameters Tab

The bus parameters can be adjusted only when the selected profile is user defined (see Profibus
Tab above). These parameters should only be changed if the user is familiar with the individual

Profibus parameters according to the Profibus specification.

Adjustable bus parameters:
Tslot

The slot time determines the maximum length of time the sender has to wait to receive a
response from the partner.

Max. Tsdr + 15 <= Tslot <= 16.383 t_bit
Max Tsdr
The maximum station delay responder determines the maximum length of time required by the

responding node to respond

35 + 2*Tset + Tqui <= Max. Tsdr <= 1.023 t_bit
Min Tsdr
The minimum station delay responder determines the minimum length of time permitted for the

responding node to respond.

11 t_bit <= Min. Tsdr <=Max. Tsdr - 1
Tset
The setup time determines the length of time elapsing in the node between a data frame being

received and a response occurring

1 t_bit <= Tset <= 494 t_bit

94

WI-GTWY-9-xxx Wireless Gateway V1.18

Tqui
The quiet time is the time a modulator needs after recognizing a send frame to switch from send

to receive.

0 t_bit <= Tqui <= MIN(31 t_bit, Min. Tsdr - 1)
Gap Factor
The Gap Factor determines how many token rounds occur before a new active node (master) can

be added to the token ring.

1 <= Gap Factor <= 100
Retry Limit
The Retry Limits determines the number of attempts (repeated message frames) allowed to

access a node.

1 <= Retry Limit <= 15
HSA
All active nodes (masters) scan the network continuously up to the HSA (highest station

address). HSA must be set at minimum to the highest Profibus address (master or slave)
connected to the network.

0 <= HSA <= 126
Delta_Ttr

95

WI-GTWY-9-xxx Wireless Gateway V1.18

This value can be set for multi master networks with the selected profile Multi Master. Delta Ttr
is added to the calculated Ttr to increase the Ttr for using multiple masters in a network.

256 t_bit <= Ttr <= 16.776.960 t_bit

Non-adjustable bus parameters
Ttr

The target rotation time determines the maximum available time for a token pass. During this
time all active nodes (masters) obtain the token one time to send data. WI Series Configuration
Software calculates an optimized Ttr depending on the values of other bus parameters. If an
individual bus parameter is changed, pressing the Recalculate-button recalculates the Ttr
including Delta_Ttr.

Watchdog
The watchdog determines the watchdog time transferred to slaves if the watchdog is enabled.
Tid2
The idle time 2 determines the maximum length required before a transmitting node can send the

next message after sending a message frame that is not acknowledged.

Tid2 = Max. Tsdr
Tid1

The idle time 1 determines the minimum length required before a transmitting node can send the
next message after sending a message frame that is not acknowledged.

Tid1 = 35 + 2*Tset + Tqui
Trdy

The ready time determines the minimum time for a transmitting node to receive a response
message frame.

Trdy = Min. Tsdr

4.11.4 Configuration Example

The Following example describes a simple configuration of a WI-GTWY-9-xxx connected to a
simple Profibus Slave I/O device. Described is the configuration of the local WI-GTWY-9-xxx
Profibus master only, for more detailed configuration examples, an application note can be
downloaded from www.weidmuller.com.

The example will transfer 8 x digital points from the radio network to the slave device. A single
16-bit analog value will be transferred from the Profibus slave to the radio network. Several
configuration steps via WISeries Configuration Software are required:

• Profibus Network Configuration

• Fieldbus Configuration (Fieldbus Mappings)

• Radio Configuration (I/O or Block Mappings)

96

WI-GTWY-9-xxx Wireless Gateway V1.18

Profibus Network Configuration

Once the GSD file for the Profibus slave has been installed, the slave device can be added to the
Profibus network (see Configuration section above). For this example, the slave is a modular
device, therefore we add the necessary I/O modules to the slave. The example requires 8 x digital
points to be transferred to the slave - hence we add the ‘1 Byte Out’ module - and 1 x analog
point (16-bit) to be transferred from the slave – hence we add the ‘2 Byte In’ module (see below).

When these modules are added, configuration software automatically picks the next free fieldbus
interface registers (shown in the Input Address and Output Address columns), which may later be
altered by double-clicking on the relevant I/O module. In this example, the automatically chosen
locations are Fieldbus IN locations 0..1, and Fieldbus OUT location 0.

Fieldbus Configuration.

The next configuration step is to transfer the I/O in the Fieldbus Interface to the Radio Interface
so that the Profibus I/O is available to the radio network. The 8 x digital output to be sent to the
Profibus slave are transferred using a fieldbus write mapping. Since the 8 x digital outputs are all
contained in a ‘1 Byte Out’ module, we use ‘Single Bit Mode’ for the fieldbus write mapping.
The configured mapping (see below) transfers the 8 x I/O Registers 100..107 in the radio
interface to single bits in Fieldbus Location 0 of the fieldbus interface (corresponding to the
Output Address of the corresponding ‘1 Byte Out’ module).

The 1 x analog input to be read from the slave must now be transferred to the radio interface.
Here we use a fieldbus read mapping using a ‘Word Mode’ (16-bit) transfer from Fieldbus
Locations 0..1 to I/O Register 200.

Byte order can be changed by selecting ‘MS Byte’

97

WI-GTWY-9-xxx Wireless Gateway V1.18

WI-GTWY-9

98

WI-GTWY-9-xxx Wireless Gateway V1.18

1) Radio Configuration

To complete the configuration, the I/O that has now been transferred to the radio interface must
be mapped over the radio network. The analog input from the slave is mapped to an analog
output at a remote WI-I/O 9-x-1, the 8 x digital output at the Profibus slave will be activated in
this example via appropriate mapping from 8 x digital input at a remote WI-I/O 9-x-4 (see
below).

4.11.5 Message Interface

99

WI-GTWY-9-xxx Wireless Gateway V1.18

In addition to cyclic data exchange with slave devices, the WI-GTWY-9-xxx Profibus Master
also supports a number of acyclic services that may be triggered via a special Message Interface.
The message interface is by default disabled, but will become enabled by also enabling a “Status
Location” via the fieldbus configuration tab in configuration software.

The message interface is used to instruct the WI-GTWY-9-xxx to perform a specific task, to
request data, to indicate certain events (alarms), or to respond to requests. The message interface
can be controlled via a host or other smart device by constructing the appropriate message in the
Message Interface Area of the WI-GTWY-9-xxx I/O Registers (radio interface). Since the
message interface is part of the radio interface, it may be controlled either remotely via
appropriate block mappings (i.e. remote WI-GTWY-9-xxx), or locally via a device on the
Profibus network (i.e. configuration tool, PLC, or other smart device).

The supported messages are listed in the table below.

Message Description

SET_SLAVE_MODE Send control command to slave(s) (Sync/Freeze)
GET_SLAVE_DIAG Get diagnostic information from a slave
GET_SLAVE_CONFIG Get slave configuration
SET_SLAVE_ADDRESS Set node address of a slave (If supported by slave)
MSAC1_READ acyclic read (class 1)
MSAC1_WRITE acyclic write (class 1)
GET_LIVE_LIST Get information from all nodes on the network
MSAC1_PROFIDRIVE_V3_PARAM_

PROFIdrive v.3 acyclic parameter access

WRITE
MSAL1_ALARM_IND Alarm indication from DPV1 slave
MSAL1_ALARM_CON Confirmation to FB_MSAL1_ALARM_IND

The message interface supports the following types of communication:

• Command - Response

A message is sent by the message initiator, and the message recipient is required to

respond. The message initiator can be either the WI-GTWY-9-xxx or host device.

• Indication

A message is sent by the message initiator, and no response is required. The message

initiator can be either the WI-GTWY-9-xxx or host device.

Message Structure

A message consists of a message header and message data (see table below). The header consists
of a series of 16-bit registers that specifies the type of message and the length of the message
data. The message data may be up to 128 x 16bit registers in length and contain data that is
specific to the particular message.

100