Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: [Modbus] Support UDINT with least significant register first (little-endian word order)

Aperta
  • Qualcosa non va?
#2,837 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
backend, embedded-iot

Direzione di ricerca

Start by reading the PLC4J Modbus tag decoding and payload byte-order code; the issue does not name specific files or tests. Check how UDINT currently handles two holding registers and whether byte order can be separated from register order. Done means a documented way to select least-significant-register-first produces 1431377 for the reported register values.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What happened?

I would like to request support for decoding 32-bit unsigned integer values (UDINT) from Modbus holding registers when the least significant 16-bit register is transmitted first.

My Modbus energy meter exposes a 32-bit unsigned energy value across two consecutive holding registers. The meter returns the least significant register first, followed by the most significant register.

I can read both registers successfully using the UINT data type and manually reconstruct the 32-bit value. However, I have not been able to obtain the expected result directly using UDINT with LITTLE_ENDIAN.

Environment

Protocol: Modbus TCP

Driver: Apache PLC4X Modbus TCP

Device: Modbus energy meter

Unit Identifier: 19

Request timeout: 5000 ms

Default payload byte order: BIG_ENDIAN

Connection URL

String connectionUrl =
"modbus-tcp:tcp://10.10.121.55:502"
+ "?unit-identifier=19"
+ "&request-timeout=5000"
+ "&default-payload-byte-order=BIG_ENDIAN";

Steps to Reproduce

  1. Read the two holding registers as UINT

PlcReadRequest request = connection.readRequestBuilder()
.addTagAddress(
"energy",
"holding-register:29[0..1]:UINT{unit-id: 19}"
)
.build();

The response contains:

response = [55121, 21]
Tag: energy
Response code for energy: OK

The two 16-bit register values are:

First register: 55121

Second register: 21

  1. Reconstruct the unsigned 32-bit value manually

The expected result is calculated by placing the second register in the upper 16 bits and the first register in the lower 16 bits:

long energyValue =
((long) 21 << 16) | 55121L;

Result:

Assembled Energy Value: 1431377

This produces the expected energy value.

  1. Attempt to read the value directly as UDINT

I am unable to obtain the same expected value by reading the two registers directly as UDINT with LITTLE_ENDIAN byte order.

I would like PLC4X to support decoding this register arrangement directly, without requiring applications to read individual registers and reconstruct the value manually.

Expected Behavior

PLC4X should support decoding a 32-bit unsigned integer from two Modbus holding registers when the least significant register is first.

For the example above:

Register 1 (LSW) = 55121
Register 2 (MSW) = 21

Expected UDINT value = 1431377

The driver should provide a documented and supported way to select the register/word order independently of the byte order within each 16-bit register, where necessary.

Actual Behavior

The two registers can be read successfully as UINT, and the expected value can be calculated manually.

However, I cannot obtain the expected result directly using UDINT with LITTLE_ENDIAN.

Requested Enhancement

Please clarify whether the Modbus driver supports 32-bit unsigned integer decoding with least significant register first.

If this arrangement is not currently supported, please consider adding support for configurable 16-bit register/word ordering for multi-register data types such as:

UDINT — unsigned 32-bit integer

DINT — signed 32-bit integer

REAL — 32-bit floating-point value

Other supported multi-register data types, where applicable

The configuration should distinguish between:

Byte order: the ordering of bytes within an individual 16-bit register.

Word/register order: the ordering of the two 16-bit registers that make up a 32-bit value.

These settings should be independently configurable where the protocol and driver implementation permit it.

Additional Information

The Modbus connection and read request are successful, and the response code is OK.

The issue concerns decoding the two register values into the expected 32-bit unsigned integer rather than reading the registers themselves.

Version

v1.0.0

Programming Languages
  • plc4c
  • plc4go
  • plc4j
  • plc4net
  • plc4py
Protocols
  • AB-Ethernet
  • ADS /AMS
  • BACnet/IP
  • C-Bus
  • CANopen
  • EtherNet/IP
  • Firmata
  • IEC-69870
  • KNXnet/IP
  • Modbus
  • OPC-UA
  • PLC4X
  • Profinet
  • S7
  • Simulated
  • SLMP
  • UMAS
Lingua principale
Java
Stelle
1.8k
Fork
514
Merge medio
2g 2h
PR unite (30g)
34

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/plc4x

Tutte le issue di apache/plc4x

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.