Easy Modbus
  1. Home
  2. Modbus register maps
  3. RLE Technologies
  4. LD5200 leak detection controller (Modbus RTU / Modbus TCP slave)

Sensor (leak detection controller) · Modbus register map

RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) Modbus register map

Updated 17 November 2026

Short answer

The LD5200 monitors a water-sensing cable and reports where along the cable a leak is. As a Modbus slave on its EIA-485 ports (or Modbus over Ethernet) it gives leak, cable-break and contamination status, leak distance and current, cable resistances, virtual-zone alarms and the status of the slave panels it polls as a Modbus master. Thresholds and alarm delays are writable holding registers.

This page lists 47 Modbus registers for the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) — 4 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from RLE Technologies’s own free documentation (linked below) and checked against it.

Manufacturer
RLE Technologies
Model
LD5200 leak detection controller (Modbus RTU / Modbus TCP slave)
Equipment type
Sensor (leak detection controller)
Registers
47 (4 writable)
Transport
Modbus RTU, Modbus TCP
Default unit ID
Not stated
Default serial
9600 baud, 8N1
Documented addressing
Modicon 3xxxx/4xxxx (drop the prefix, subtract 1)
32-bit word order
ABCD high word first (big-endian)
Firmware
Documented with firmware 2.3.1
Also known as
LD5200
Source document
LD5200 User Guide · Version 04.22 · rev. 2022-04
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave)

Integration in brief

Read input registers 30001-30011 with FC4: status bits for leak / cable break / contamination, leak distance and unit, leak current and cable data. Read 38001-38002 for the leak position as a float in meters.

Minimum registers to map

Addresses are 0-based wire addresses. Enough to monitor and run the unit; map more as the job needs.

RegisterNameTypeWhyAccess
IR 0StatusBITMAP16Leak / cable break / contamination statusRead
IR 1Leak distanceUINT16Leak distanceRead
IR 2Distance unitsUINT16Distance unitRead
IR 3Leak currentUINT16Leak currentRead
IR 8000Leak location (float)FLOAT32 ABCDLeak location in meters (float)Read
IR 9Virtual zone alarm status, zones 1-16BITMAP16Virtual zone alarms 1-16Read

Enable Modbus control & writes

Set an EIA-485 port function to Modbus-Slave and give it a slave address (1-254, 0 = disabled) and baud rate in the Comm Port Settings menu (LCD) or the Modbus/EIA-485 web page. For Ethernet, set the Modbus/TCP/UDP slave unit identifier on the same page.

Byte order & addressing

Network setup

Watch out for

RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) Modbus registers

Address = 0-based wire address (the documented number is shown under it when it differs) · Order: ABCD = high word first, CDAB = low word first · Scale: engineering value = raw × scale.

47 of 47 shown
RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
IR0doc 30001StatusBITMAP16Readbit 0 = Leak detected; bit 1 = Cable break alarm; bit 2 = Contamination detected
IR1doc 30002Leak distanceLocation of the leak; unit per register 30003.UINT16ft or mRead
IR2doc 30003Distance unitsUINT16Read0 = Meters; 1 = Feet
IR3doc 30004Leak currentLeakage current on the sensing cable.UINT16uARead
IR4doc 30005Cable lengthInstalled sensing-cable length.UINT16ft or mRead
IR5doc 30006Loop 1 resistanceUINT16ohmRead
IR6doc 30007Loop 2 resistanceUINT16ohmRead
IR7doc 30008Resistance per footPublished as ohms x 1000.UINT16× 0.001ohmRead
IR8doc 30009Firmware versionxx.xx x 100.UINT16× 0.01Read
IR9doc 30010Virtual zone alarm status, zones 1-16BITMAP16Readbit 0 = Zone 1 in alarm; bit 1 = Zone 2 in alarm; bit 2 = Zone 3 in alarm; bit 3 = Zone 4 in alarm; bit 4 = Zone 5 in alarm; bit 5 = Zone 6 in alarm; bit 6 = Zone 7 in alarm; bit 7 = Zone 8 in alarm; bit 8 = Zone 9 in alarm; bit 9 = Zone 10 in alarm; bit 10 = Zone 11 in alarm; bit 11 = Zone 12 in alarm; bit 12 = Zone 13 in alarm; bit 13 = Zone 14 in alarm; bit 14 = Zone 15 in alarm; bit 15 = Zone 16 in alarm
IR10doc 30011Virtual zone alarm status, zones 17-32BITMAP16Readbit 0 = Zone 17 in alarm; bit 1 = Zone 18 in alarm; bit 2 = Zone 19 in alarm; bit 3 = Zone 20 in alarm; bit 4 = Zone 21 in alarm; bit 5 = Zone 22 in alarm; bit 6 = Zone 23 in alarm; bit 7 = Zone 24 in alarm; bit 8 = Zone 25 in alarm; bit 9 = Zone 26 in alarm; bit 10 = Zone 27 in alarm; bit 11 = Zone 28 in alarm; bit 12 = Zone 29 in alarm; bit 13 = Zone 30 in alarm; bit 14 = Zone 31 in alarm; bit 15 = Zone 32 in alarm
IR11doc 30012Modbus zone enabled flags, zones 2-16One bit per zone 2-16; the guide's bit labels (0 = zone 2, 15 = zone 16) do not add up.BITMAP16Read
IR12doc 30013Modbus zone 2 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR13doc 30014Modbus zone 2 distanceLeak location reported by that slave.UINT16ft or mRead
IR14doc 30015Modbus zone 3 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR15doc 30016Modbus zone 3 distanceLeak location reported by that slave.UINT16ft or mRead
IR16doc 30017Modbus zone 4 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR17doc 30018Modbus zone 4 distanceLeak location reported by that slave.UINT16ft or mRead
IR18doc 30019Modbus zone 5 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR19doc 30020Modbus zone 5 distanceLeak location reported by that slave.UINT16ft or mRead
IR20doc 30021Modbus zone 6 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR21doc 30022Modbus zone 6 distanceLeak location reported by that slave.UINT16ft or mRead
IR22doc 30023Modbus zone 7 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR23doc 30024Modbus zone 7 distanceLeak location reported by that slave.UINT16ft or mRead
IR24doc 30025Modbus zone 8 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR25doc 30026Modbus zone 8 distanceLeak location reported by that slave.UINT16ft or mRead
IR26doc 30027Modbus zone 9 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR27doc 30028Modbus zone 9 distanceLeak location reported by that slave.UINT16ft or mRead
IR28doc 30029Modbus zone 10 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR29doc 30030Modbus zone 10 distanceLeak location reported by that slave.UINT16ft or mRead
IR30doc 30031Modbus zone 11 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR31doc 30032Modbus zone 11 distanceLeak location reported by that slave.UINT16ft or mRead
IR32doc 30033Modbus zone 12 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR33doc 30034Modbus zone 12 distanceLeak location reported by that slave.UINT16ft or mRead
IR34doc 30035Modbus zone 13 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR35doc 30036Modbus zone 13 distanceLeak location reported by that slave.UINT16ft or mRead
IR36doc 30037Modbus zone 14 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR37doc 30038Modbus zone 14 distanceLeak location reported by that slave.UINT16ft or mRead
IR38doc 30039Modbus zone 15 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR39doc 30040Modbus zone 15 distanceLeak location reported by that slave.UINT16ft or mRead
IR40doc 30041Modbus zone 16 statusSlave leak-detection panel on the LD5200's master port.BITMAP16Readbit 0 = Leak detected; bit 1 = Cable break; bit 2 = Contamination; bit 7 = Communication loss
IR41doc 30042Modbus zone 16 distanceLeak location reported by that slave.UINT16ft or mRead
IR8000doc 38001Leak location (float)Location of leak in meters; MSW at 38001, LSW at 38002.FLOAT32ABCDmRead
HR0doc 40001Leak thresholdTrip current for a leak alarm.UINT16uARead/write
HR1doc 40002Contamination thresholdTrip current for a contamination alarm, 20-295.UINT16uARead/write
HR15doc 40016Leak alarm delay5-995 s.UINT16sRead/write
HR16doc 40017Contamination alarm delay5-995 s.UINT16sRead/write

Notes on this map

Check it against the live device. A register map tells you what the controller can expose; the unit in front of you may differ by firmware or options. Read a few registers and compare them with the unit’s own display; for a 32-bit value the float and byte-order decoder shows all four word orders at once, so a wrong word order or scale is obvious. New to this? Read what a register map is and why addresses are off by one.

Questions about the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave)

What Modbus registers does the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) have?

This map lists 47 registers: 43 input registers, 4 holding registers. 4 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers Modicon 3xxxx/4xxxx (drop the prefix, subtract 1). Every address on this page is the 0-based wire address you put in the request; the documented number is shown under it where it differs. RLE says the start register is numbered from zero: 40001 = 0, 30001 = 0. So input register 30002 (leak distance) is wire address 1 with FC4, holding register 40016 is address 15 with FC3/FC6/FC16.

What byte order does the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) use for 32-bit values?

Multi-register values in this map use ABCD (high word first (big-endian)). Set your client to this order for every 32/64-bit value in the table.

What are the minimum Modbus registers to integrate the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave)?

Start with IR 0 Status (Leak / cable break / contamination status); IR 1 Leak distance (Leak distance); IR 2 Distance units (Distance unit); IR 3 Leak current (Leak current); IR 8000 Leak location (float) (Leak location in meters (float)); IR 9 Virtual zone alarm status, zones 1-16 (Virtual zone alarms 1-16).

How do I enable Modbus control of the RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave)?

Set an EIA-485 port function to Modbus-Slave and give it a slave address (1-254, 0 = disabled) and baud rate in the Comm Port Settings menu (LCD) or the Modbus/EIA-485 web page. For Ethernet, set the Modbus/TCP/UDP slave unit identifier on the same page.

Where is the official RLE Technologies LD5200 leak detection controller (Modbus RTU / Modbus TCP slave) Modbus documentation?

The source is LD5200 User Guide (Version 04.22), revision 2022-04, published free by RLE Technologies at https://WWW.RLETECH.COM/wp-content/uploads/2022/04/LD5200_UserGuide-04-22.pdf.

More RLE Technologies Modbus register maps

Other valves, actuators & sensors register maps

All valves, actuators & sensors Modbus register maps →

Source: LD5200 User Guide · Version 04.22 · rev. 2022-04. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.