Mettler Toledo IND570 weighing terminal (needs Modbus TCP option board)

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale
default_rounded_gross_weight	0	F32BE	1
rounded_gross_weight	2	F32BE	1
rounded_tare_weight	4	F32BE	1
rounded_net_weight	6	F32BE	1
gross_weight	8	F32BE	1
tare_weight	10	F32BE	1
net_weight	12	F32BE	1
weight_unit	14	F32BE	1
raw_load_cell_counts	16	F32BE	1
preset_tare	19	F32BE	1
tare	21	I16	1
tare_operation_status	22	I16	1
zero	23	I16	1
zero_operation_status	24	I16	1
clear_tare	25	I16	1
tare_immediate	26	I16	1
print	28	I16	1
increment	203	F32BE	1
scale_capacity	205	F32BE	1
discrete_inputs	802	U16	1
discrete_outputs	804	U16	1
rate_value	900	F32BE	1
change_byte_order_swap_mode	990	I16	1
restart_terminal	997	I16	1
rounded_tare_weight_alt	1000	F32BE	1
display_weight	1002	F32BE	1
scale_status	1004	U16	1

link settings as documented (unverified): RTU/TCP; unit ID 0; FC 03,06; Supports Modbus RTU via COM1, COM2, or COM3. Supports Modbus TCP via EtherNet/IP-Modbus TCP option board.

⚠ IF THIS DEVICE IS USED IN AN AUTOMATIC OR MANUAL FILLING CYCLE, ALL USERS MUST PROVIDE A HARD-WIRED EMERGENCY STOP CIRCUIT OUTSIDE THE DEVICE OF CIRCUITRY. FAILURE TO OBSERVE THIS PRECAUTION COULD RESULT IN BODILY INJURY. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

terminals	COM1 serial port on main board, COM2/COM3 on option board
wiring notes	COM2 and COM3 are provided by the COM2/COM3 option board, which has better anti-interference performance.
protocol notes	Modbus RTU terminal address is set to 0 by default, must be set to 1-15. Modbus TCP read and write areas of memory are offset by 1024.
identification notes	The IND570 terminal automatically detects the presence of a Modbus TCP Kit option board.
power	DeviceNet network power consumption: 11V 50mA, 25V 30mA. Inrush current: 24V 0.7A for 6ms.
environment	Harsh environment enclosure option available.
accuracy	Analog Output: 16 bit resolution - 65536 levels across entire range.
certifications	FCC Part 15 Class A
doc revision	30205335 \| 12 \| 01/2023

field reports — community-sourced, unverified (checked 2026-06-11)

The IND570 requires a command word written to Register 400000 (or equivalent based on addressing mode) before each weight read. The weight register does not auto-update without this command trigger. Alternatively, command 10 or 11 must be written to the command register (HR1025/HR1026 depending on offset) to request continuous updates. [source]
confirmed: Supports Modbus RTU via COM1, COM2, or COM3. Supports Modbus TCP via EtherNet/IP-Modbus TCP option board. — confirmed by Mettler Toledo IND570 PLC Interface Manual (30205335)
confirmed: doc_revision: 30205335 | 12 | 01/2023 — confirmed by Mettler Toledo IND570 PLC Interface Manual
confirmed: Modbus TCP read and write areas of memory are offset by 1024 — confirmed by Mettler Toledo IND570 PLC Interface Manual (Section 5 / Appendix A)

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.