Register or Log in

MTR Modbus Information

The Modbus feature on the device allows the user to enable the Modbus query server. You can query this server over Modbus-TCP for status information. NOTE: You must first enable Modbus on the device and enter the required settings in the UI under Administration > Access Configuration > Modbus Slave. Refer to the Modbus Slave section under Configuring Device Access in your user guide. See the MTR product page on our company website to find your product user guide. 

This page includes the necessary details to perform Modbus queries using a Modbus application such as Modbus Poll. Refer to the attached table.

MTR Modbus Query Server Data Set 

Name

Register Number1

Register Address

Size

Description

Data Type

Data / Data Range

Data Interpretation

Notes

GSM Band

#1

0×0000

1 register

GSM Band

16-bit unsigned int

0×0000

GSM 900MHz + DCS 1800MHz

Per Telit HE910 AT Commands Reference (AT#BND?)

0×0001

GSM 900MHz + PCS 1900MHz

0×0002

GSM 850MHz + DCS 1800MHz

0×0003

GSM 850MHz + PCS 1900MHz

0xFFFF

Band could not be obtained

Response may vary based on model.

UMTS Band

#2

0×0001

1 register

UMTS Band

16-bit unsigned int

0×0000

1900 / 2100MHz(FDD I)

Per Telit HE910 AT Commands Reference (AT#BND?)

0×0001

1900MHz(FDD II)

0×0002

850MHz(FDD V)

0×0003

2100MHz(FDD I) + 1900MHz(FDD II) + 850MHz(FDD V)

0×0004

1900MHz(FDD II) + 850MHz(FDD V)

0×0005

900MHz(FDD VIII)

0×0006

2100MHz(FDD I) + 900MHz(FDD VIII)

0×0007

1700/2100MHz(FDD IV, AWS)

0xFFFF

Band could not be obtained

Response may vary based on model.

RSSI

#3

0×0002

1 register

Received Signal Strength Indication

16-bit unsigned

0×0000

-113 dBm or less

Per Telit HE910 Commands Reference (AT+CSQ)

0×0001 – 0x001E

-111 dBm to -53 dBm in 2 dBm steps

0x001F

-51 dBm or greater

0×0063

Not known or not detectable

MCC

#4

0×0003

1 register

Mobile Country Code

16-bit unsigned int

0×0000 – 0x03E7

3-digit MCC (max 999 dec) stored in binary form

Parsed from AT#RFSTS and stored in binary form

0xFFFF

Not known

MNC

#5

0×0004

1 register

Mobile Network Code

16-bit unsigned int

0×0000 – 0x03E7

2 or 3-digit MNC (max 999 dec) stored in binary form

Parsed from AT#RFSTS and stored in binary form

0xFFFF

Not known

WAN IPv4

#6

0×0005

2 registers

PPP WAN IPv4 Address

Four 8-bit unsigned  ints spanning two registers

Each byte 0×00 – 0xFF

Binary form of of the IPv4 address as would be written by inet_pton(). For example, “70.63.161.250″ is stored in two registers as 0x463F, 0xA1FA.  If the IPv4 address is not known or cannot be determined, the registers will contain all zeros.

WAN IPv6

#8

0×0007

8 registers

PPP WAN IPv6 Address

Eight 16-bit unsigned ints

Each register 0×0000 – 0xFFFF

Binary form of of the IPv6 address as would be written by inet_pton(). For example, “2001:0DB8:AC10:FE01:0000:0000:0000:0000″ is stored in eight registers as 0×2001, 0x0DB8, 0xAC10, 0xFE01, 0×0000, 0×0000, 0×0000, 0×0000. If the IPv6 address is not known or cannot be determined, the registers will contain all zeros.

Model Type

#16

0x000F

10 registers

Model Type / Product ID

20 bytes spanning 10 registers, each byte corresponding to a printable ASCII character or NULL (0×00)

Each byte 0×20 – 0x7E, or 0×00

Up to 20 printable ASCII characters, 2 per register, right padded with zeros (0×00). For example, “MTR-H5″ is stored in ten registers as 0x4D54, 0x522D, 0×4835, 0×0000, 0×0000, 0×0000, 0×0000, 0×0000, 0×0000, 0×0000

Note:
1) Data may be read from either the input or holding register number specified. For example, GSM_BAND is available Input Register #1 (Modicon notation: 30001) and in Holding Register #1 (Modicon notation: 40001).