Laumas TLB4 weight transmitter

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire; word order and scaling are only confirmed at the hardware-verified rung.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale
firmware_version	0	U16	1
instrument_type	1	U16	1
year_of_manufacture	2	U16	1
serial_number	3	U16	1
program_type	4	U16	1
command_register	5	U16	1
status_register	6	U16	1
gross_weight	7	U32BE	1
net_weight	9	U32BE	1
peak_weight	11	U32BE	1
divisions_and_units_of_measure	13	U16	1
coefficient	14	U32BE	1
inputs	16	U16	1
outputs	17	U16	1
setpoint_1	18	U32BE	1
setpoint_2	20	U32BE	1
setpoint_3	22	U32BE	1
hysteresis_1	38	U32BE	1
hysteresis_2	40	U32BE	1
hysteresis_3	42	U32BE	1

link settings as documented (unverified): RTU; FC 03,16; Data format: 1 start bit, 8 data bits (least significant bit sent first), settable parity bit, settable stop bit.

bench facts as documented (unverified)

max registers/read	32
protocol notes	EEPROM has a limited number of writing operations (100000). The instrument makes sure that no writing occurs if the value to be memorised is equal to the value in memory.
model register	40002
serial register	40004
firmware register	40001
doc revision	1.03

generated by gemini:gemini-3.5-flash · harvested from https://tenzomir.com/wp-content/uploads/woocommerce_uploads/2018/07/TLB4_protocols_manual_EN.pdf (Laumas); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; proved interop-verified on 2026-06-10 · recorded 2026-06-10

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.