trumeter Touch Flow Digital Touchscreen Monitor User Guide

This document describes the use of Modbus in the Vista Touch
range. Modbus is implemented in Vista Touch to enable the reading
of the measured values and the status of the system. This document
defines the configuration and usage of the Modbus features of the
Vista Touch for both Modbus RTU and Modbus TCPIP. The registers are
common to both Modbus communication methods.

By default, both the Modbus RTU and Modbus TCP/IP interfaces are
enabled.

Ensure you’re using the latest firmware in order to
benefit from the features in this document.

Modbus Data Types

Modbus supports 4 data types:

Coils

Inputs
Holding registers

Input registers

Coils and inputs are both 1 bit in size, whereas both Holding
and Input registers are 16 bits wide. Inputs, and Input registers,
can only be read. Coils and Holding registers are both read and
writable. All coil/inputs and registers are addressed in the range
of 0-65535, although only portions of that address range are
implemented, the remaining address space is invalid.

Protocols

Formatting

RTU:

RTU is framed with a minimum of 3.5 byte times (28 bits) of
non-transmission, both before and after the message. The message
itself must be sent without any delays between bytes.

Size (bytes)	1	1	n	2
Description	Unit / Server address (1 to 247)	Function code	Data, amount of varies according to function code	CRC error check

CRC:

The CRC is a 16 bit value, which is appended to the message by
the transmitter, and verified by the receiver.

FAQ (Frequently Asked Questions)

Q: What are the data types supported by Modbus?

A: Modbus supports Coils, Inputs, Holding registers, and Input
registers.

Q: What is the importance of using the latest firmware for
Vista Touch?

A: Using the latest firmware ensures that you benefit from all
the features described in the document.

Q: How are Coils and Inputs different from Holding and Input
registers?

A: Coils and Inputs are 1 bit in size and Holding/Input
registers are 16 bits wide. Coils/Inputs are read and writable
while Holding/Input registers are read-only.

“`

View Fullscreen

VMoISdbTuAs CToOmmUuCniHcations
May 2025 Revision 07 sdZ DZZZ
Colin Henderson Vista Touch Modbus Communications Spec
Released
KWzZ/’,dEKE&/Ed/> . his ocument and the intellectual property contained herein are the property of rumeter. o part of this document may e disclosed reproduced distri uted or transmitted in any form or y any means ithout prior ritten permission.
EKd/ rinted documents and copies stored outside of rumeter and are uncontrolled.
For the latest version please to refer to the company’s document register. his document may refer to documents hose o nership is outside that of rumeter. he o nership and right to copyright of these documents are ac no ledged. o part of these documents may e used ithout the prior ritten permission of the document o ners.

Version 1.1 2.0 3.0 4.0
5.0, 7.0

Document History

Date

Change Details

20th March 2024 Typographical updates

14th May 2024 VT-FLOW registers and TCPIP addition

4th October 2024 VT-POWER added Accumulated Forward Active Energy data

1st April 2025 25th April 2025

VT-POWER added maximum and minimum values, removed %Load as not applicable
VT-POWER added reset maximum and minimum values to current values.

Revision: 7

©Trumeter

Page 2 of 21

Table of Contents
1 About this document ……………………………………………………………………………………………………………………. 4 2 Modbus Data Types ……………………………………………………………………………………………………………………… 5 3 Protocols …………………………………………………………………………………………………………………………………….. 5 4 Formatting ………………………………………………………………………………………………………………………………….. 6
4.1 RTU ……………………………………………………………………………………………………………………………………….. 6 4.1.1 CRC……………………………………………………………………………………………………………………………….. 6
4.2 TCP/IP ……………………………………………………………………………………………………………………………………. 7 4.3 Error Frame ……………………………………………………………………………………………………………………………. 7 5 Function Codes ……………………………………………………………………………………………………………………………. 8 5.1 Function Code 1 (Read Coils)…………………………………………………………………………………………………….. 8 5.2 Function Code 2 (Read Inputs) ………………………………………………………………………………………………….. 9 5.3 Function Code 3 (Read Holding Registers) ………………………………………………………………………………….. 9 5.4 Function Code 4 (Read Input Registers) ……………………………………………………………………………………. 10 5.5 Function Code 5 (Set Single Coil)……………………………………………………………………………………………… 10 5.6 Function Code 6 (Set Holding Register) …………………………………………………………………………………….. 10 5.7 Function Code 15 (Set Multiple Coils) ………………………………………………………………………………………. 11 5.8 Function code 16 (Set Multiple Holding Registers) …………………………………………………………………….. 11 6 RTU & TCPIP Configuration ………………………………………………………………………………………………………….. 12 6.1 RTU ……………………………………………………………………………………………………………………………………… 12
6.1.1 Slave ID ……………………………………………………………………………………………………………………….. 12 6.1.2 Baud Rate…………………………………………………………………………………………………………………….. 12 6.1.3 Stop Bits ………………………………………………………………………………………………………………………. 12 6.1.4 Parity…………………………………………………………………………………………………………………………… 12 6.2 TCP/IP ………………………………………………………………………………………………………………………………….. 12 6.2.1 DHCP Client ………………………………………………………………………………………………………………….. 12 6.2.2 Configurable options …………………………………………………………………………………………………….. 12 6.3 RTU & TCP/IP ………………………………………………………………………………………………………………………… 12 6.3.1 Modbus Enable …………………………………………………………………………………………………………….. 12 6.3.2 Sentence Protocol…………………………………………………………………………………………………………. 12 6.3.3 Floating point numbers………………………………………………………………………………………………….. 12 7 Address Map ……………………………………………………………………………………………………………………………… 13 8 Generic Registers All Vista Touch Products …………………………………………………………………………………. 14 8.1.1 Function code 2 (Read Status Bits): …………………………………………………………………………………. 14 8.1.2 Function code 3 (Read Configuration Registers): ………………………………………………………………. 15 9 Model Specific Registers …………………………………………………………………………………………………………… 16 9.1 Vista Touch Flow …………………………………………………………………………………………………………………… 16 9.1.1 Function Code 4 (Read Measurement Data): ……………………………………………………………………. 16 9.2 Vista Touch Power…………………………………………………………………………………………………………………. 17 9.2.1 Function Code 4 (Read Measurement Data): ……………………………………………………………………. 17 9.2.2 Function Code 15 (Write to Control Bits): ………………………………………………………………………… 19 9.2.3 Function Code 16 (Write Measurement Data): …………………………………………………………………. 20 10 Appendices………………………………………………………………………………………………………………………………… 21 10.1 Modbus Baud Rates ………………………………………………………………………………………………………………. 21 10.2 Device sample rate ………………………………………………………………………………………………………………… 21

Revision: 7

©Trumeter

Page 3 of 21

1 About this document
This document describes the use of Modbus in the Vista Touch range. Modbus is implemented in Vista Touch to enable the reading of the measured values and the status of the system. This document defines the configuration and usage of the Modbus features of the Vista Touch for both Modbus RTU and Modbus TCPIP. The registers are common to both Modbus communication methods.
By default, both the Modbus RTU and Modbus TCP/IP interfaces are enabled.
** Ensure you’re using the latest firmware in order to benefit from the features in this document **

Revision: 7

©Trumeter

Page 4 of 21

2 Modbus Data Types
Modbus supports 4 data types:1) Coils 2) Inputs 3) Holding registers 4) Input registers
Coils and inputs are both 1 bit in size, whereas both Holding and Input registers are 16 bits wide. Inputs, and Input registers, can only be read. Coils and Holding registers are both read and writable. All coil/inputs and registers are addressed in the range of 0-65535, although only portions of that address range are implemented, the remaining address space is invalid.
3 Protocols
Both RTU and TCPIP are supported. RTU (Remote Terminal Unit) is a serial protocol implemented over the RS485 electrical physical layer and includes commands and data with a CRC (Cyclic Redundancy Check) checksum to ensure reliable data transmission with detection of errors. TCPIP (Transmission Control Protocol/Internet Protocol) is similar to RTU but without the CRC as lower levels of the protocol include error handling. Normal port for Modbus is 502. Both RTU and TCPIP use the same function calls and data structure, only the data encapsulation is different. The Client Server model is used (formerly Master / Slave), with the Client initiating the communication.

Revision: 7

©Trumeter

Page 5 of 21

4 Formatting
4.1 RTU
RTU is framed with a minimum of 3.5 byte times (28 bits) of non-transmission, both before and after the message. The message itself must be sent without any delays between bytes.

Size (bytes) 1 1 n 2

Description Unit / Server address (1 to 247) Function code Data, amount of varies according to function code CRC error check

4.1.1 CRC

The CRC is a 16 bit value, which is appended to the message by the transmitter, and verified by the receiver

own CRC calculation of the message.

The initial value of the CRC is 0xFFFF.

Each byte of the message is exclusively OR-ed with the register contents.

The CRC is then right shifted (/2). If the least significant bit is a 1, then the register is exclusively OR-ed with 0xA001. This process is repeated 8 times.

Polynomial: x16 + x15 + x2 + 1 (CRC-16-ANSI)

Initial value: 65,535

Revision: 7

©Trumeter

Page 6 of 21

4.2 TCP/IP

Size (bytes) 2 2 2 1 1 n

Description Sync identifier Identifies the protocol as Modbus, zero. Payload length (length of subsequent data). Unit / Server address, normally zero, ignored. Function code Data, amount of varies according to function code

4.3 Error Frame
An error frame is transmitted by the server to the client when an error free message is received but the
message content is not valid for the device, be it an unsupported function, or an issue with the data.

Size (bytes) 1 1 1 2

Description Unit / Server address (1 to 247) Function code (same as received function code with 80H added) Error code, listed below CRC error check

Error Codes

Code

Error

1 Unsupported Function 2 Illegal Data Address 3 Illegal Data Value

Revision: 7

©Trumeter

Page 7 of 21

5 Function Codes

Dec. Code

Hex. Code

Function

0x01 Read Coils

0x02 Read Inputs

0x03 Read Multiple Holding

Registers

0x04 Read Input Registers

0x05 Write single coil

0x06 Write single holding

0x0F Write multiple Coils

0x10 Write multiple Holding

Registers

Note.

Access
Coils are read & write capable Inputs are read only Holding registers are read & writeable Input registers are read only Coils are read & write capable Holding registers are read & writeable Coils are read & write capable Holding registers are read & writeable

Supported function code No Yes Yes
Yes No No
No No

Accessing unsupported functions will result in an error code 1 (unsupported function) being returned.

5.1 Function Code 1 (Read Coils)
Coils are bits of information that can be set, cleared, and read.

The 16 bit address of the 1st coil is specified, along with the 16 bit count of the number of coils required in the message request.

The response contains a byte specifying the number of data bytes which contain the requested information, followed by the requested information. Each data byte contains the status of 8 coils. The least significant bit of the first data byte contains the status of the 1st coil requested. The LSB of the next data byte contains the 9th coil, and so on. The last data byte may not by fully occupied with coil statuses and the unused bits will be zero.

Server Function Address Count Bytes Data

Checksum

code

MSB LSB

LSB MSB

Client 0A

00 48

00 0A

xx xx

Server 0A

FF 03

xx xx

Read from server address 0x0A, using function code 1, from address 0x0048, the status of 10 coils. The server

response shows the data is contained within two bytes, and in this case, all the coils are set. Unused bits in the

last data byte as always zero.

Revision: 7

©Trumeter

Page 8 of 21

5.2 Function Code 2 (Read Inputs)
Similar to coils but reflect the status of an input or process. These can only be read.

Server Function Address Count Bytes Data

code

MSB LSB

Checksum
LSB MSB

Client 0A

10 00

00 07

xx xx

Server 0A

xx xx

Read from server address 0x0A, using function code 2, from address 0x1000, the status of 7 inputs. The server

response shows the data is contained within one byte, as shown below.

Coil Status 0x1000 Off 0x1001 On 0x1002 Off 0x1003 On 0x1004 On 0x1005 Off 0x1006 Off
5.3 Function Code 3 (Read Holding Registers)
Holding registers are locations that hold 16 bit values and are used to configure settings such as setpoints. These are settable, and readable.

The 16 bit address of the 1st register is specified, along with the 16 bit count of the number of registers required in the message request.

The response contains a byte specifying the number of data bytes which contain the requested information, followed by the requested information. Each register is two bytes, and whether the least significant byte, or most significant byte, is transmitted first depends on the configuration settings.

Server Function Address Count

code

MSB LSB

Bytes

Data
MSB LSB

Checksum
LSB MSB

Client 0A

00 00

00 04

xx xx

Server 0A

00 00 11 11 12 34 56 78 xx xx

Read from server address 0x0A, using function code 3, contents of the register from address 0x0000 to address

0x003. The server response shows the data is contained within eight bytes. Example is with big endian used.

Address Value 0x0000 0x0001 0x0002 0x0003

0x0000 0x1111 0x1234 0x5678

Revision: 7

©Trumeter

Page 9 of 21

5.4 Function Code 4 (Read Input Registers)
Similar to holding registers, input registers show input or process values and are only readable.

Server Function Address Count Bytes Data

Checksum

code

MSB LSB

LSB MSB

Client 0A

00 48

00 01

xx xx

Server 0A

12 34

xx xx

Read from server address 0x0A, using function code 4, contents of the register from address 0x0000. The

server response shows the data is contained within two bytes, value being 0x1234 (big endian).

5.5 Function Code 5 (Set Single Coil)
Use to set, or clear, a configuration bit.

The 16 bit address of the coil is supplied, along with the required configuration. The configuration is supplied as a 16 bit value, which if 0x0000 clears the coil, and if 0xFF00 sets the bit. Any other value is invalid.

Server Function Address Count

code

MSB LSB

Client 0A

00 53

Server 0A

00 53

Set a coil on server address 0x0A, coil address 0x0053.

Bytes

Data
FF 00 FF 00

Checksum
LSB MSB
xx xx xx xx

Server Function Address Count

code

MSB LSB

Client 0A

00 52

Server 0A

00 52

Clear a coil on server address 0x0A, coil address 0x0052.

Bytes

5.6 Function Code 6 (Set Holding Register)
Used to configure a single holding register.

Data
00 00 00 00

Checksum
LSB MSB
xx xx xx xx

The 16 bit address of the register is supplied, along with the 16 bit value that the register is to contain.

Server Function Address Count Bytes Data

code

MSB LSB

Client 0A

01 23

23 45

Server 0A

01 23

23 45

On server address 0x0A, Set register address 0x0123 to value 0x2345 (big endian)

Checksum
LSB MSB
xx xx xx xx

Revision: 7

©Trumeter

Page 10 of 21

5.7 Function Code 15 (Set Multiple Coils)
Use to set and / or clear, multiple configuration bits.

The 16 bit address of the 1st coil is supplied, along with the 16 bit number of coils to configure.

A byte is supplied showing how many bytes of data are following containing the configuration data.

The subsequent data bytes contain the configuration, 8 coils per byte. The LSB of the 1st data byte is for the coil specified by the address. 0 is off, 1 is on.

Server Function Address Count Bytes Data

code

MSB LSB

Client 03

00 02

01 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00

Server 03

00 02

01 00

On server address 0x03, all the coils from address 0x0002 to 0x0102 are cleared (256 coils).

5.8 Function code 16 (Set Multiple Holding Registers)
Simultaneously configures multiple configuration registers.

Checksum
LSB MSB
xx xx
xx xx

The 16 bit address of the 1st register is supplied, along with the 16 bit count of the registers, and a 8 bit byte containing the amount of data bytes following which contain the register values. Two bytes per register, and the significant order is according to the configuration of the unit.

Server Function Address Count Bytes Data

Checksum

code

MSB LSB

LSB MSB

Client 03

00 00

00 04

01 00 12 11 34 12 78 56

xx xx

Server 03

00 00

00 04

xx xx

On server address 0x03, the registers from address 0x0000 to 0x0003 are preset to the following values using

the little endian data format.

Address Value 0x0000 0x0001 0x0002 0x0003

0x0001 0x1112 0x1234 0x5678

Revision: 7

©Trumeter

Page 11 of 21

6 RTU & TCPIP Configuration
6.1 RTU
6.1.1 Slave ID
Any value between 1 and 247 can be entered.
6.1.2 Baud Rate
Baud rates from 9600 to 192000 are supported.
See Appendices 10.1- Modbus Baud Rate for full list.
6.1.3 Stop Bits
Both 1 and 2 stop bits are supported
6.1.4 Parity
Parity can be None, Even, or Odd
6.2 TCP/IP
6.2.1 DHCP Client
Enable and disable are selectable.
6.2.2 Configurable options
The following parameters are adjustable. IP address and Subnet Mask are only adjustable if DHCP is disabled.
Parameter IP address Subnet mask Gateway
DNS 1 DNS 2 Hostname Interface Name Modbus port address Modbus timeout period
6.3 RTU & TCP/IP
6.3.1 Modbus Enable
Each interface can be independently enabled.
6.3.2 Sentence Protocol
The 16 bit registers can be transferred as either High Byte First (Big Endian) or Low Byte First (Little Endian).
32 bit registers are transferred high word first’
CRC fields are always little endian. Address and count fields are big endian.
6.3.3 Floating point numbers
Floats are 32 bits wide and formatted according to the IEEE-754 standard.

Revision: 7

©Trumeter

Page 12 of 21

7 Address Map
Decimal
Start address End address

Hex Start address End address

Description

0 32,768 33,792 34,816

32,767 33,791 34,816 35,839

0x0000 0x8000 0x8400 0x8800

0x7FFF 0x83FF 0x87FF 0x8BFF

Generic registers Vista Touch Flow Vista Touch Power
345

Note.

Accessing addresses outside the above ranges will result in an error code 2 (illegal data address) being returned.

Revision: 7

©Trumeter

Page 13 of 21

8 Generic Registers All Vista Touch Products

8.1.1 Function code 2 (Read Status Bits):

Address

Dec

Hex

Description

0x0000 Event 1 status

0x0001 Event 2 status

0x0002 Event 3 status

0x0003 Event 4 status

0x0004 Event 5 status

0x0005 Event 6 status

0x0006 Event 7 status

0x0007 Event 8 status

0x0008 Event 9 status

0x0009 Event 10 status

10 – 31 32

0x000A 0x001F 0x0020

Not used. Relay 1 status

0x0021 Relay 2 status

Function Codes R/W
1 2 3 4 15 16 – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R – Y- – – – R

Length (bits)
1 1 1 1 1 1 1 1 1 1 1

Unit
0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active 0=Inactive 1=Active N/A

– Y- – – – R – Y- – – – R

0=Inactive

1=Active

0=Inactive

1=Active

Revision: 7

©Trumeter

Page 14 of 21

8.1.2 Function code 3 (Read Configuration Registers):

Address

Dec

Hex

Description

0x0000 Model type

Function Codes R/W
1 2 3 4 15 16 – – Y- – – R

Length (bytes)
2

Unit
0=Flow 1=Power 2=345

Note.
Accessing unused/unimplemented addresses between 0x0000 and the last register listed above will return zero.
Accessing register addresses after the last register, up to 0x7FFF, will result in an error code 2 (illegal data address) being returned.

Revision: 7

©Trumeter

Page 15 of 21

9 Model Specific Registers

9.1 Vista Touch Flow

9.1.1 Function Code 4 (Read Measurement Data):

Address

Dec

Hex

Description

Function Codes 1 2 3 4 15 16

R/W

Length (bytes)

1 LSB

32,768 0x8000 Flow rate

—Y – – R

0.01

32,770 32,772

0x8002 0x8004

Total 1 Total 2

—Y – – R —Y – – R

0.01

Note.
Accessing unused/unimplemented addresses between 0x8000 and the last register listed above will return zero.
Accessing register addresses after the last register, up to 0x83FF, will result in an error code 2 (illegal data address) being returned.

Unit
US Gal per sec US Gal US Gal

Revision: 7

©Trumeter

Page 16 of 21

9.2 Vista Touch Power

9.2.1 Function Code 4 (Read Measurement Data):

Address

Dec

Hex

Description

Function Codes 1 2 3 4 15 16

R/W

Length (bytes)

1 LSB

33,792 0x8400 Frequency

—Y – – R

33,793 0x8401 Average Voltage L-L

—Y – – R

33,795 0x8403 Average Voltage L-N

—Y – – R

33,797 0x8405 Average Current

—Y – – R

33,799 0x8407 Total Active Power

—Y – – R

33,801 0x8409 Total Apparent Power

—Y – – R

33,803 0x840B Total Reactive Power

—Y – – R

33,806 0x840E Average Power Factor

—Y – – R

33,807 0x840F Average THD Volts

—Y – – R

33,808 0x8410 Average THD Current

—Y – – R

33,809 0x8411 L1 to L2 Voltage

—Y – – R

33,811 0x8413 L2 to L3 Voltage

—Y – – R

33,813 0x8415 L3 to L1 Voltage

—Y – – R

33,815 0x8417 L1 to N Voltage

—Y – – R

33,817 0x8419 L2 to N Voltage

—Y – – R

33,819 0x841B L3 to N Voltage

—Y – – R

33,821 0x841D L1 Current

—Y – – R

33,823 0x841F L2 Current

—Y – – R

33,825 0x8421 L3 Current

—Y – – R

33,827 0x8423 L1 Active Power

—Y – – R

33,829 0x8425 L2 Active Power

—Y – – R

33,831 0x8427 L3 Active Power

—Y – – R

33,833 0x8429 L1 Apparent Power

—Y – – R

33,835 0x842B L2 Apparent Power

—Y – – R

33,837 0x842D L3 Apparent Power

—Y – – R

33,839 0x842F L1 Reactive Power

—Y – – R

33,841 0x8431 L2 Reactive Power

—Y – – R

33,843 0x8433 L3 Reactive Power

—Y – – R

33,848 0x8438 L1 Power Factor

—Y – – R

33,849 0x8439 L2 Power Factor

—Y – – R

33,850 0x843A L3 Power Factor

—Y – – R

33,851 0x843B L1 Voltage THD

—Y – – R

33,852 0x843C L2 Voltage THD

—Y – – R

33,853 0x843D L3 Voltage THD

—Y – – R

33,854 0x843E L1 Current THD

—Y – – R

33,855 0x843F L2 Current THD

—Y – – R

33,856 0x8440 L3 Current THD

—Y – – R

33,857 0x8441 L1 Current Phase Angle

—Y – – R

33,858 0x8442 L2 Current Phase Angle

—Y – – R

33,859 0x8443 L3 Current Phase Angle

—Y – – R

33,860 0x8444 L1 to L2 Voltage Phase Ang

—Y – – R

33,861 0x8445 L1 to L3 Voltage Phase Ang

—Y – – R

33,682 0x8446 Temperature

—Y – – R

33863 0x8447 Total Accumulated Forward

—Y – – R

Active Energy

33865 0x8449 L1 Accumulated Forward Active – – – Y – – R

Energy

0.01Hz

0.01V

0.001A

4VA

4VAr

0.001

0.01%

0.01V

0.001A

1VA

1VAr

0.001

0.01%

0.1

0.1 C

0.1kWH

Type
Unsigned Unsigned Unsigned Unsigned Signed Unsigned Signed Signed Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Signed Signed Signed Unsigned Unsigned Unsigned Signed Signed Signed Signed Signed Signed Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned Signed Signed Signed Signed Signed Signed Unsigned
Unsigned

Revision: 7

©Trumeter

Page 17 of 21

33867 0x844B L2 Accumulated Forward Active – – – Y – – R

Energy

33869 0x844D L3 Accumulated Forward Active – – – Y – – R

Energy

33871 0x844F Average Power Factor

—Y – – R

33872 0x8450 Max Voltage L1-N

—Y – – R

33874 0x8452 Max Voltage L2-N

—Y – – R

33876 0x8454 Max Voltage L3-N

—Y – – R

33878 0x8456 Max Voltage L1-L2

—Y – – R

33880 0x8458 Max Voltage L2-L3

—Y – – R

33882 0x845A Max Voltage L3-L1

—Y – – R

33884 0x845C Min Voltage L1-N

—Y – – R

33886 0x845E Min Voltage L2-N

—Y – – R

33888 0x8460 Min Voltage L3-N

—Y – – R

33890 0x8462 Min Voltage L1-L2

—Y – – R

33892 0x8464 Min Voltage L2-L3

—Y – – R

33894 0x8466 Min Voltage L3-L1

—Y – – R

33896 0x8468 Max Current L1

—Y – – R

33898 0x846A Max Current L2

—Y – – R

33900 0x846C Max Current L3

—Y – – R

33902 0x846E Min Current L1

—Y – – R

33904 0x8470 Min Current L2

—Y – – R

33906 0x8472 Min Current L3

—Y – – R

0.1kWH

0.001

0.01V

0.001A

Unsigned
Unsigned
Signed Unsigned Unsigned Unsigned Signed Signed Signed Unsigned Unsigned Unsigned Signed Signed Signed Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned

Accessing unused/unimplemented addresses between 0x8400 and the last register listed above will return zero.
Accessing register addresses after the last register, up to 0x87FF, will result in an error code 2 (illegal data address) being returned.

Revision: 7

©Trumeter

Page 18 of 21

9.2.2 Function Code 15 (Write to Control Bits):

Address

Dec

Hex

Description

33,792 33,793

0x8400 0x8401

Set ALL Max and Min values to the current live values Set Max Voltage (L1-N) = Voltage (L1-N)

33,794 0x8402

Set Max Voltage (L2-N) = Voltage (L2-N)

33,795 0x8403

Set Max Voltage (L3-N) = Voltage (L3-N)

33,796 0x8404

Set Max Voltage (L1-L2) = Voltage (L1-L2)

33,797 0x8405

Set Max Voltage (L2-L3) = Voltage (L2-L3)

33,798 0x8406

Set Max Voltage (L3-L1) = Voltage (L3-L1)

33,799 0x8407

Set Min Voltage (L1-N) = Voltage (L1-N)

33,800 0x8408

Set Min Voltage (L2-N) = Voltage (L2-N)

33,801 0x8409

Set Min Voltage (L3-N) = Voltage (L3-N)

33,802 0x840A

Set Min Voltage (L1-L2) = Voltage (L1-L2)

33,803 0x840B

Set Min Voltage (L2-L3) = Voltage (L2-L3)

33,804 0x840C

Set Min Voltage (L3-L1) = Voltage (L3-L1)

33,805 0x840D

Set Max Current (L1) = Current (L1)

33,806 0x840E

Set Max Current (L2) = Current (L2)

33,807 0x840F

Set Max Current (L3) = Current (L3)

33,808 0x8410

Set Min Current (L1) = Current (L1)

33,809 0x8411

Set Min Current (L2) = Current (L2)

33,810 0x8412

Set Min Current (L3) = Current (L3)

Function Codes R/W
1 2 3 4 15 16 —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W —- Y – W

Length (bits)
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Unit
0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value 0=No action 1=Set value

Note
Accessing undefined register addresses between 0x8400 and 0x87FF, will result in an error code 2 (illegal data address) being returned.

Revision: 7

©Trumeter

Page 19 of 21

9.2.3 Function Code 16 (Write Measurement Data):

Address

Dec

Hex

Description

Function Codes 1 2 3 4 15 16

R/W

Length (bytes)

33872 33874 33876 33878 33880 33882 33884 33886 33888 33890 33892 33894 33896 33898 33900 33902 33904 33906

0x8450 0x8452 0x8454 0x8456 0x8458 0x845A 0x845C 0x845E 0x8460 0x8462 0x8464 0x8466 0x8468 0x846A 0x846C 0x846E 0x8470 0x8472

Max Voltage L1-N (Note 1) Max Voltage L2-N (Note 1) Max Voltage L3-N (Note 1) Max Voltage L1-L2 (Note 1) Max Voltage L2-L3 (Note 1) Max Voltage L3-L1 (Note 1) Min Voltage L1-N (Note 1) Min Voltage L2-N (Note 1) Min Voltage L3-N (Note 1) Min Voltage L1-L2 (Note 1) Min Voltage L2-L3 (Note 1) Min Voltage L3-L1 (Note 1) Max Current L1 (Note 1) Max Current L2 (Note 1) Max Current L3 (Note 1) Min Current L1 (Note 1) Min Current L2 (Note 1) Min Current L3 (Note 1)

—- – Y W

1 LSB

Type

Notes:-
1) Writing to any address within the range 0x8450 to 0x8472 will reset ALL the maximum and minimum values (registers 0x8450 to 0x8472) to the current live values.
Accessing undefined register addresses between 0x8400 and 0x87FF, will result in an error code 2 (illegal data address) being returned.

Revision: 7

©Trumeter

Page 20 of 21

10 Appendices
10.1 Modbus Baud Rates

28,800 52,800 76,800 100,800 124,800 148,800 172,800

9,600 33,600 57,600 81,600 105,600 129,600 153,600 177,600

Baud Rates
14,400 38,400 62,400 86,400 110,400 134,400 158,400 182,400

19,200 43,200 67,200 91,200 115,200 139,200 163,200 187,200

10.2 Device sample rate
New data is available up to a maximum of 0.33 samples per second.

24,000 48,000 72,000 96,000 120,000 144,000 168,000 192,000

Revision: 7

©Trumeter

Page 21 of 21

Documents / Resources

trumeter Touch Flow Digital Touchscreen Monitor [pdf] User Guide
Touch Flow Digital Touchscreen Monitor, Flow Digital Touchscreen Monitor, Digital Touchscreen Monitor, Touchscreen Monitor, Monitor

References

User Manual

trumeter Touch Flow Digital Touchscreen Monitor User Guide

Touch Flow Digital Touchscreen Monitor

Product Information

Specifications

Product Usage Instructions

About this document

Modbus Data Types

Protocols

Formatting

CRC:

FAQ (Frequently Asked Questions)

Q: What are the data types supported by Modbus?

Q: What is the importance of using the latest firmware for
Vista Touch?

Q: How are Coils and Inputs different from Holding and Input
registers?

Documents / Resources

References

Leave a comment

Cancel reply