Líder Balanças LD2051 Modbus register map
Digital weighing indicator: net weight and tare, as whole numbers and as floats
- Official
- 8 registers
- Modbus TCP and RTU
- Revision 1 · 2026-11-10
Official: Written from the manufacturer's documentation, but not tested on a device yet. Check the map against the manufacturer's documentation before you write to a live device. Tested it? Report a test.
Communication
- Protocol
- Modbus TCP and RTU
- Unit ID
- 1
- TCP port
- 502
- Serial
- 9600 8N1 · 9600 baud, 8 data bits, none parity, 1 stop bit
- Byte / word order
- CDAB · bytes big-endian, words low first (word swap)
- Addresses
- 0-based
Connection values are defaults: the device may be configured differently.
Map
- Registers
- 8 holding registers
- Groups
- 1
- Revision
- 1 · 2026-11-10
- Firmware
- Manual for versions from 2051A1 (Modbus RS-485 selection F315 from version D7)
- Added
- ()
- File
- maps/lider-balancas/ld2051.mbmap.json · 4 KB · history
- SHA-256
- 3ffddb1daeee62d51192d5138e29db88908d3846a674068b29517d4e4734391a
- Manufacturer
- liderbalancas.com.br
Sources and notes
- Indicador Digital LD2051 - Manual do Usuário · version 2.7, 2024-10-08 Protocolo Modbus chapter and the F3 serial settings; linked in issue #144 (the link as written in the issue)
Source: Líder Balanças, Indicador Digital LD2051, Manual do Usuário v2.7 (8 October 2024), Modbus chapter
- The Modbus protocol is optional on RS-485 and Ethernet and available on RS-232 by default. Modbus RTU or ASCII on RS-232 (F300 = 4 or 5) or RS-485 (F315 = 0 or 1), Modbus TCP (F316 = 2) or Modbus RTU over TCP (F316 = 1, F300 = 0). FC03 only. The protocol field of this format has no ASCII mode.
- The manual numbers the registers 84, 86, 88 and 90 and gives the hex addresses 0x53, 0x55, 0x57 and 0x59, which are what is sent on the wire (83, 85, 87, 89); this map uses the wire addresses.
- 32-bit values are sent with the least significant word first and the most significant byte first in each word, in RTU, ASCII and RTU over TCP. In Modbus TCP the manual lists the registers at 84 to 90 with the most significant word first, and a second set at 100 to 106 (wire 99 to 105) with the least significant word first, so a Modbus TCP client should use the second set. The first set is correct as written for RTU and RTU over TCP.
- Factory serial settings: 9600 bit/s (F301 for RS-232, F304 for RS-485), 8 data bits, no parity (F308), 1 stop bit (F309). The address (F302) is 1 to 255; the manual gives no default, and 1 is assumed here.
- The document does not give the weight unit; the indicator sends the value in its configured unit.
- Written from the manual; this map has not been tested on a device.
| Area | Address | Name | Type | Access | Unit | Scale | Description |
|---|---|---|---|---|---|---|---|
| HR | 83 | int32 CDAB | R | Net weight as a signed whole number; the document does not say how the decimal point is handled (the Líder LD1050 LCD map reads 0.5 with three decimals as 500). Over Modbus TCP, words come most significant first at this address: use address 99 instead | |||
| HR | 85 | int32 CDAB | R | Tare as a signed whole number. Over Modbus TCP, use address 101 | |||
| HR | 87 | float32 CDAB | R | Net weight as a 32-bit float. Over Modbus TCP, use address 103 | |||
| HR | 89 | float32 CDAB | R | Tare as a 32-bit float. Over Modbus TCP, use address 105 | |||
| HR | 99 | int32 CDAB | R | Same value as address 83, with the least significant word first; listed in the document for Modbus TCP only | |||
| HR | 101 | int32 CDAB | R | Same value as address 85; listed for Modbus TCP only | |||
| HR | 103 | float32 CDAB | R | Same value as address 87; listed for Modbus TCP only | |||
| HR | 105 | float32 CDAB | R | Same value as address 89; listed for Modbus TCP only |
No registers match
Try part of the name, an address (decimal or 0x hex) or clear the filters.
Help improve this map
- I tested it on a deviceReport whether it worked, even if you did not write the map.
- Suggest a correctionEdit the file on GitHub; it opens a pull request.
- Report a problemA wrong address, type, scale or byte order.
- Read the formatWhat each key of the file means (SPEC.md).