Touchpoint Plus Wireless Modbus RTU and TCP
Touchpoint Plus Wireless Modbus RTU and TCP
i
Disclaimer
In no event shall Honeywell be liable for any damages or injury of any nature or kind, no matter how caused, that arise
from the use of the equipment referred to in this manual.
Strict compliance with the safety procedures set out and referred to in this manual, and extreme care in the use of the
equipment, are essential to avoid or minimise the chance of personal injury or damage to the equipment.
The information, figures, illustrations, tables, specifications, and schematics contained in this manual are believed to be
correct and accurate as at the date of publication or revision. However, no representation or warranty with respect to such
correctness or accuracy is given or implied and Honeywell will not, under any circumstances, be liable to any person or
corporation for any loss or damages incurred in connection with the use of this manual.
The information, figures, illustrations, tables, specifications, and schematics contained in this manual are subject to change
without notice.
Unauthorised modifications to the gas detection system or its installation are not permitted, as these may give rise to
unacceptable health and safety hazards.
Any software forming part of this equipment should be used only for the purposes for which Honeywell supplied it. The
user shall undertake no changes, modifications, conversions, translations into another computer language, or copies
(except for a necessary backup copy).
In no event shall Honeywell be liable for any equipment malfunction or damages whatsoever, including (without limitation)
incidental, direct, indirect, special, and consequential damages, damages for loss of business profits, business
interruption, loss of business information, or other pecuniary loss, resulting from any violation of the above prohibitions.
Warranty
Honeywell Analytics warrants the Touchpoint Plus Wireless system against defective parts and workmanship, and will
repair or (at its discretion) replace any components that are or may become defective under proper usage within
12 months from the date of commissioning by a Honeywell Analytics approved representative* or 18 months from
shipment from Honeywell Analytics, whichever is sooner.
This warranty does not cover consumable, batteries, fuses, normal wear and tear, or damage caused by accident, abuse,
improper installation, unauthorized use, modification or repair, ambient environment, poisons, contaminants or abnormal
operating conditions.
This warranty does not apply to sensors or components that are covered under separate warranties, or to any 3 rd-party
cables and components.
Any claim under the Honeywell Analytics Product Warranty must be made within the warranty period and as soon as
reasonably practicable after a defect is discovered. Please contact your local Honeywell Analytics Service representative
to register your claim.
This is a summary. For full warranty terms please refer to the Honeywell Analytics’ General Statement of Limited Product
Warranty, which is available on request.
* A Honeywell Analytics approved representative is a qualified person trained or employed by Honeywell Analytics, or a
qualified person trained in accordance with this manual.
Copyright Notice
Honeywell is the registered trademark of Honeywell Safety and Productivity Solutions (SPS).
Touchpoint is a registered trademark of Honeywell Analytics (HA).
ii
MODBUS INSTALLATION
Contents
1 Introduction ..................................................................................................................................... 4
1.1 How to Use this Document............................................................................................... 4
1.2 Overview ............................................................................................................................ 4
2 Safety Notices ................................................................................................................................. 5
3 How to Install the Bus Interface Board (BIB) (Repair, Upgrade or OEM) ................................... 5
3.1 Modbus RTU Cable ........................................................................................................... 7
3.2 Modbus TCP Cable ........................................................................................................... 7
3.3 Modbus RTU and TCP Electrical Connections ............................................................... 7
3.4 Modbus RTU Chaining / Multi-Drop Mode ...................................................................... 8
4 How to Configure Modbus RTU / TCP Parameters ....................................................................... 9
4.1 How to Configure the Master / Host PC .......................................................................... 9
4.2 How to Configure the TPPLW Modbus RTU Settings .................................................... 9
4.3 How to Configure the TPPLW Ethernet TCP Settings ................................................... 9
5 TPPLW Modbus Register Allocation ........................................................................................... 10
5.1 TPPLW Modbus Register Outline .................................................................................. 10
5.2 Function 02 – Read Input Status ................................................................................... 11
5.2.1 Channel Status ............................................................................................................ 11
5.2.2 System Summary ........................................................................................................ 11
5.3 Function 04 – Read Input Registers .............................................................................. 12
5.3.1 Signal Level Registers (Integer and Float)................................................................... 12
5.3.2 Animation Registers ..................................................................................................... 13
5.3.3 Inputs Registers for TPPLW system ............................................................................ 14
5.3.4 Inputs Registers for TPPLW wireless and RAEMet channel ........................................ 15
5.4 Function 03 / 06 / 16 – Read / Write Holding Registers ................................................ 17
5.4.1 Query Poll Registers .................................................................................................... 17
5.4.2 Command Poll Registers ............................................................................................. 22
5.5 Exception Responses ..................................................................................................... 23
This document uses [Button name] and Menu>Item>Command to signify tasks that are carried out on the TPPLW
Touchscreen.
1.2 Overview
The TPPLW Modbus Interface provides a facility for digital communication between the TPPLW and an external computer
system.
Principal features:
• Operates as a Modbus Remote Terminal Unit (RTU) slave device node.
• Operates as a Modbus TCP slave device node.
• Can be used in Modbus Multi-Drop mode.
• Supports functions 02, 03, 04, 06 and 16 of the Modbus protocol.
• Provides sensor gas readings and alarm status for Fault, Inhibit, Warning, A1, A2, A3, STEL, LTEL and Rate alarms
from all input channels in the system.
• Supports commands to Inhibit, Reset and Acknowledge for Modbus RTU only.
• Asynchronous serial link configurable for baud, bit-rate and parity.
Notes:
• The Modbus broadcast commands are not supported and will be ignored, i.e. it has no output registers at this time.
• There are no standard Modbus function formats defined for the communication of data from a gas detection system
so the host computer system must be programmed to interpret the signal and status data made available by
TPPLW.
• It is recommended that the host computer system should, as a minimum, be programmed to use Function 02 to
collect alarm and status data from all TPPLW channels.
• Full details of the Modbus protocol can be found in the Modicon Modbus Protocol Reference Guide PI-MBUS-300
mentioned above.
• The addressing conventions and register values used follow those set by Modicon. The first digit of the on-board
memory address refers to the data type stored in the register and therefore defines the Modbus function command
that should be used when polling it.
• Touchpoint Plus Wireless provides compatibility with Touchpoint Plus (TPPL) Modbus registers. Therefore,
information on input channels 1 to 64 can also be obtained by using the TPPL Modbus registers. This document
describes only TPPLW dedicated registers.
DANGER
TPPLW Safety systems will be inoperative during parts of this procedure. Ensure that a risk assessment is carried
out and that alternative safety arrangements are in place before commencing.
WARNING
The equipment specified in this manual is only to be installed by the Manufacturer’s trained personnel, or by
competent persons trained in accordance with the Manufacturer’s installation instructions.
WARNING
There is a risk of electric shock when carrying out this procedure. Ensure that the system and backup batteries are
electrically isolated and that residual power is allowed to dissipate before opening the enclosure.
WARNING
If the TPPLW relays are switching mains voltages, hazardous live terminals may be present within the
Relay Output Modules even if the TPPLW is electrically isolated.
CAUTION
The SD Card should be removed before attempting to remove the Control Module cover panel.
3 How to Install the Bus Interface Board (BIB) (Repair, Upgrade or OEM)
To fit or replace the BIB:
1. Power off and isolate the mains supply and backup batteries and any mains-switching relays.
2. Open the Controller enclosure to access the controller cover panel (see figure on next page.)
3. Remove the three cover securing screws (arrowed).
4. Carefully slide the cover off.
SD Card
Modbus RTU
Terminals
5. Locate the Bus Interface Board (BIB) position to the right of the MOBO (see picture below).
6. If required, remove the existing BIB by pulling gently, and place it on a static free surface.
7. Observing the correct orientation, align the connectors and gently push the new BIB into place.
Modbus
PCB
MOBO
B↔
Modbus RTU Logic
A↔
Terminals Solver
D↔
B
I Ethernet
B Connector
8. Carefully slide the cover back into place and refit / tighten the securing screws.
9. Connect the Modbus cables as shown below.
10. Re-connect all other cables as required.
11. Switch on the batteries and Mains power.
12. Wait for the system to initialize and check / test that everything is working correctly.
CAUTION
Some transceiver manufacturers have been known to incorrectly reverse their RS485 Data terminals, which can
cause Tx/Rx to fail. If this happens, simply swap over the TPPLW’s A and B cables and then re-test.
Note: You should connect a 120Ω termination resistor (RT) between A and B to prevent reflections on the RS485 circuit if
TPPLW is the last node in a Modbus system highway.
Note: The external RT is not needed if the logic solver side has an internal RT.
Slave Slave
Node Node
MODBUS
Master Slave
(RT 100 Ω) Node
Slave Slave
Node Node
MODBUS
Master Slave
(RT 100 Ω) Node
Slave Slave
Node Node
Slave Slave
Node Node
Figure 5. Two Modbus Chaining Examples (other layouts may also be used)
Note: TPPLW can be any slave node, and it can support one master node with up to 31 slave nodes when in Multi-Drop
Mode.
Before starting, please refer to the documentation supplied with the host computer for details of its communication and
Modbus configuration, and to the TPPLW Technical Handbook for details on everything else.
Note: It is recommended that the host computer is configured to provide at least two retries in the event of a
communication frame loss with a minimum delay of 1 second between each poll, and a minimum timeout of 2 seconds.
1
11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088
(mA Input)
2
11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101 11102 11103 11104
(mA Input)
...
8
11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200
(mA Input)
9
11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216
(wireless)
...
72
12209 12210 12211 12212 12213 12214 12215 12216 12217 12218 12219 12220 12221 12222 12223 12224
(wireless)
73
12225 12226 12227 12228 12229 12230 12231 12232 12233 12234 12235 12236 12237 12238 12239 12240
(RAEMet)
TWA STEL Alarm 3 Alarm 2 Alarm 1 Inhibit Fault Not Not Not Not Not Not Not Not
Not Used
alarm alarm Summary Summary Summary Summary Summary Used Used Used Used Used Used Used Used
System
11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040
Summary
System
11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056
Summary
System
11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072
Summary
Sensor
Channel Integer Value Float Value Register 1 Float Value Register 2
Index
... ...
Note: The Integer Value format is a 16 bit signed integer, range -10000 to +10000 in steps of 0.1 % FSD - e.g., if FSD is
500 and the reading is 50, then the data will be 100 (10.0 % FSD) – if the channel is mA Input or wireless detector.
Note: The Float Value format is a 32 bit floating point value in accordance with IEEE 754-2008 if the channel is mA Input
or wireless detector.
Note: The Integer Value format is an unsigned 16 bitmask if the channel is wireless relay. Bit 0 (LSB) is 1 if the first relay is
activated. Bit 1 ~ 4 is 1 if the second ~ fifth relay is activated. The Float Value on the wireless relay channel is float-casted
of the integer value.
Sensor
Channel Animation Value
Index
... ...
The data value for each register can be assigned to one of the following:
Status Value
High byte for status: High byte for status: 1: AC, 2: DC, 3: AC+DC
TPPLW Power 30902
Low byte for percentage
High byte for Online Monitoring Status (the monitor’s data availability): 0:
unavailable, 1: available
Monitor available 30903
Low byte for Count of Online Node: the number of online monitors in the
controller
Online Monitor Setting
30904 Online Monitoring value set by user, that is used as threshold to make fault
Count
Analog Relay Status -
30905 u16, bit 0 (LSB): system, bit 1: relay 1, bit 2: relay 2
Main Module
Analog Relay Status -
30906 u16, bit 0 (LSB): relay 1 ~ bit 11: relay 12
Relay Module 1
System setting. 16bit unsigned Integer.
bit 0 (LSB) : Enable Online monitoring Portable Devices. 1 - the online
TPPLW setting 30907
monitoring is applied to all the wireless channel. 0 - exclude portable
wireless device
Table 7. Modbus Registers – TPPLW System Status
381111
9 38101 38102 38103 38104 38105 38106 38107 38108 38109 38110
~381120
10 38121 38122 38123 38124 38125 38126 38127 38128 38129 38130
… … … … … … … … … … … …
73
39381 39382 39383 39384 39385 39386 39387 39388 39389 39390
(RAEMet)
… … … … … … … … …
Note: Each wireless and RAEMet channel - number n - features 20 registers starting from <38101 + (n-9) * 20>. RAEMet channel
(number 73) features register range of 39381 ~ 39390.
GPS Float Value GPS x and y position. The format is same with Channel n Float Value.
DIO Status Digital Input and Output Status. Bit 0 (channel 0) ~ Bit 15 (channel 15).
Digital Input Status == DIO Status BITWISE_AND <Digital Input Active
mask>
Digital Output Status == DIO Status BITWISE_AND <Digital Output
Active mask>
Response
Query Block Active Channel Type Channel ID Query Code Result
Data
Poll Block (Write) (Write) (Write) (Write) (Read)
(Read)
CAUTION
When using Function 6 or Function 16, ensure that the registers related to the command are completely filled before
setting the Block Active register, otherwise an unintended command may be performed.
Result Meaning
0 Success
6 Read range full scale Float (4 Bytes – 32 bit floating point) mA Input or Wireless sensor
7 Read range zero scale Float (4 Bytes – 32 bit floating point) mA Input
39 Read Alarm 1 level (Low) Float (4 Bytes – 32 bit floating point) mA Input or Wireless sensor
40 Read Alarm 2 level(High) Float (4 Bytes – 32 bit floating point) mA Input or Wireless sensor
42 Read STEL level Float (4 Bytes – 32 bit floating point) Wireless sensor
43 Read LTEL level Float (4 Bytes – 32 bit floating point) always 0 on TPPL and TPPLW
44 Read Rate level Float (4 Bytes – 32 bit floating point) always 0 on TPPL and TPPLW
102 Read Gas Name Unicode String – 35 (Unicode chars) + 1(null) mA Input or Wireless sensor
103 Read Channel Tag Name Unicode String – 35 (Unicode chars) + 1(null) input channel
104 Read Gas Unit Unicode String – 35 (Unicode chars) + 1(null) mA Input or Wireless sensor
105 Read peak reading Float (4 Bytes – 32 bit floating point) mA Input channel
123 Read Device Serial Number Unicode String – 12 (Unicode chars) + 1(null) wireless and RAEMet channel
Read DIO Active Mask array of the 16bit unsigned Integer. Bit 0 (channel
0) ~ Bit 15 (channel 15).
129 wireless channel
Word [0] - Digital Input Active mask.
Word [1] - Digital Output Active mask.
131 Read Sensor Limit - Float (4 Bytes – 32 bit floating point) wireless sensor
LowLow
132 Read Sensor Limit - Float (4 Bytes – 32 bit floating point) wireless sensor
OverRange
133 Read Sensor Limit - STEL Float (4 Bytes – 32 bit floating point) wireless sensor
134 Read Sensor Limit - TWA Float (4 Bytes – 32 bit floating point) wireless sensor
Block
Channel Channel ID Query Code Response Data
Register Active Result (40n05)
Type (40n02) (40n03) (40n04) (40n06 to 40n36)
(40n01)
CAUTION
The Command Poll Registers can be accessed by only Modbus RTU while the TPPLW is not login as Service or
Administrator.
The Block Active, Channel Type, Channel ID, Result registers have the same function with Query Poll Registers.
The sole option for Channel Type is 105 – Input Channel.
Note: The Command is permitted only when login on Service or Administrator on the TPPLW.
Command Command
Command Block Active Channel Type Channel ID Result
Code Data
Poll Block (Write) (Write) (Write) (Read)
(Write) (Write)
23 Alarm Acknowledge for all channel The commands apply to all channels. The Channel Type
and Channel ID register values are not used on this
24 Alarm Reset for all channel command.
25 Set Inhibit (analog only: ch1~8) The Channel Type must be set as input ('i' 105). The
Channel ID must be mA Input Channel.
26 Clear inhibit (analog only: ch1~8)
(Updated upon
Value 1 105 2 23 0
request execution)
Exception Description
01 ILLEGAL FUNCTION Only Modbus functions 02, 03, 04, 06, 16 are supported. This response is returned if
any other requests are received.
02 ILLEGAL DATA ADDRESS The register addresses supported by each function are listed in this chapter. Any
attempt to access a register outside of these ranges will result in this error.
03 ILLEGAL DATA VALUE This exception is returned if the request has the incorrect length, or if the maximum
number of registers is exceeded. The maximum number of registers that can be
requested by function 02 is 608, function 04 is 64, and function 03 is 36 for the Query
poll block or 6 for the Command poll block.
06 SLAVE DEVICE BUSY Applies to function 06 only. Once a poll or command block’s active register has been
set, its contents must not be changed until the main program has carried out the
request. This exception is returned if any attempt is made to change an active poll or
command block.
Customer Service:
Tel: 00800 333 222 44 (Freephone number)
Tel: +41 44 943 4380 (Alternative number)
Fax: 00800 333 222 55
Middle East Tel: +971 4 450 5800 (Fixed Gas Detection)
Middle East Tel: +971 4 450 5852 (Portable Gas Detection)
Americas
Honeywell Analytics Inc.
405 Barclay Blvd.
Lincolnshire, IL 60069
USA
Tel: +1 847 955 8200
Toll free: +1 800 538 0363
Fax: +1 847 955 8210
detectgas@honeywell.com
Asia Pacific
Honeywell Analytics Asia Pacific
7F SangAm IT Tower,
Please Note:
434 Worldcup Buk-ro, Mapo-gu,
While every effort has been made to ensure accuracy
Seoul 03922, Zuid-Korea in this publication, no responsibility can be accepted
Korea for errors or omissions. Data may change as well as
legislation and you are strongly advised to obtain
Tel: +82 (0)2 6909 0300 copies of the most recently issued regulations,
Fax: +82 (0)2 2025 0328 standards and guidelines. This publication is not
intended to form the basis of a contract.
India Tel: +91 124 4752700
analytics.ap@honeywell.com
Technical Services
EMEA: HAexpert@honeywell.com
US: ha.us.service@honeywell.com
AP: ha.ap.service@honeywell.com