Easy Modbus
  1. Home
  2. Modbus register maps
  3. Moxa
  4. ioLogik R1240 RS-485 remote I/O

Sensor (remote I/O module) · Modbus register map

Moxa ioLogik R1240 RS-485 remote I/O Modbus register map

Updated 17 November 2026

Short answer

The ioLogik R1240 is a Moxa RS-485 Modbus RTU remote I/O module with 8 analog inputs (0-10 V, 0-20 mA, 4-20 mA). It supports a repeater or dual RS-485 mode and a Modbus host-connection watchdog. This map covers the shared system registers (model, watchdog, serial settings) and the analog input raw values, min/max, status and range.

This page lists 72 Modbus registers for the Moxa ioLogik R1240 RS-485 remote I/O — 35 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Moxa’s own free documentation (linked below) and checked against it.

Manufacturer
Moxa
Model
ioLogik R1240 RS-485 remote I/O
Equipment type
Sensor (remote I/O module)
Registers
72 (35 writable)
Transport
Modbus RTU
Default unit ID
Not stated
Default serial
9600 baud, 8N1
Documented addressing
hexadecimal, 0-based
Also known as
ioLogik R1240, R1240, R1240-T
Source document
ioLogik R1200 Series User's Manual · Edition 3.4 · rev. 2021-04 · unofficial copy
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: Moxa ioLogik R1240 RS-485 remote I/O

Integration in brief

Read the raw analog values and channel status with function 04 and set each channel range with function 03/06. The host-connection watchdog (0x7564, timeout 0x7565) is shared by the whole series.

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 30000SYS_modelIDUINT16Model ID checkRead
HR 30052SYS_modbusWatchdogFuntionUINT16Enable communication watchdogRead/write
HR 30053SYS_modbusWatchdogTimeoutUINT16Watchdog timeoutRead/write
IR 704AI-00_rawValueUINT16First analog input raw valueRead
IR 992AI-00_statusUINT16First analog input statusRead

Enable Modbus control & writes

Set the device ID (1-99) on the two rotary dials. Put the Initial/Run switch on Initial to configure the unit at 9600 baud, no parity, 8 data bits, 1 stop bit (with ioSearch or the SYS_port* registers), then switch back to Run.

Communication loss & watchdog

SYS_modbusWatchdogFuntion (0x7564) enables the host-connection watchdog, SYS_modbusWatchdogTimeout (0x7565) sets the timeout in seconds (factory default 10 s), SYS_modbusWatchdogStatus (0x7566) shows a timeout. It is disabled by default; safe-status settings only act when it is enabled.

Byte order & addressing

Network setup

Watch out for

Moxa ioLogik R1240 RS-485 remote I/O 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.

72 of 72 shown
Moxa ioLogik R1240 RS-485 remote I/O Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
CO704doc 0x02C0AI-00_resetMinValueBITRead/write1 = reset min. value
CO705doc 0x02C1AI-01_resetMinValueBITRead/write1 = reset min. value
CO706doc 0x02C2AI-02_resetMinValueBITRead/write1 = reset min. value
CO707doc 0x02C3AI-03_resetMinValueBITRead/write1 = reset min. value
CO708doc 0x02C4AI-04_resetMinValueBITRead/write1 = reset min. value
CO709doc 0x02C5AI-05_resetMinValueBITRead/write1 = reset min. value
CO710doc 0x02C6AI-06_resetMinValueBITRead/write1 = reset min. value
CO711doc 0x02C7AI-07_resetMinValueBITRead/write1 = reset min. value
CO736doc 0x02E0AI-00_resetMaxValueBITRead/write1 = reset max. value
CO737doc 0x02E1AI-01_resetMaxValueBITRead/write1 = reset max. value
CO738doc 0x02E2AI-02_resetMaxValueBITRead/write1 = reset max. value
CO739doc 0x02E3AI-03_resetMaxValueBITRead/write1 = reset max. value
CO740doc 0x02E4AI-04_resetMaxValueBITRead/write1 = reset max. value
CO741doc 0x02E5AI-05_resetMaxValueBITRead/write1 = reset max. value
CO742doc 0x02E6AI-06_resetMaxValueBITRead/write1 = reset max. value
CO743doc 0x02E7AI-07_resetMaxValueBITRead/write1 = reset max. value
IR704doc 0x02C0AI-00_rawValueUINT16Read
IR705doc 0x02C1AI-01_rawValueUINT16Read
IR706doc 0x02C2AI-02_rawValueUINT16Read
IR707doc 0x02C3AI-03_rawValueUINT16Read
IR708doc 0x02C4AI-04_rawValueUINT16Read
IR709doc 0x02C5AI-05_rawValueUINT16Read
IR710doc 0x02C6AI-06_rawValueUINT16Read
IR711doc 0x02C7AI-07_rawValueUINT16Read
IR736doc 0x02E0AI-00_rawValueMinUINT16Read
IR737doc 0x02E1AI-01_rawValueMinUINT16Read
IR738doc 0x02E2AI-02_rawValueMinUINT16Read
IR739doc 0x02E3AI-03_rawValueMinUINT16Read
IR740doc 0x02E4AI-04_rawValueMinUINT16Read
IR741doc 0x02E5AI-05_rawValueMinUINT16Read
IR742doc 0x02E6AI-06_rawValueMinUINT16Read
IR743doc 0x02E7AI-07_rawValueMinUINT16Read
IR768doc 0x0300AI-00_rawValueMaxUINT16Read
IR769doc 0x0301AI-01_rawValueMaxUINT16Read
IR770doc 0x0302AI-02_rawValueMaxUINT16Read
IR771doc 0x0303AI-03_rawValueMaxUINT16Read
IR772doc 0x0304AI-04_rawValueMaxUINT16Read
IR773doc 0x0305AI-05_rawValueMaxUINT16Read
IR774doc 0x0306AI-06_rawValueMaxUINT16Read
IR775doc 0x0307AI-07_rawValueMaxUINT16Read
IR992doc 0x03E0AI-00_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR993doc 0x03E1AI-01_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR994doc 0x03E2AI-02_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR995doc 0x03E3AI-03_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR996doc 0x03E4AI-04_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR997doc 0x03E5AI-05_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR998doc 0x03E6AI-06_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR999doc 0x03E7AI-07_statusUINT16Read0 = normal; 1 = burnout; 2 = over range; 3 = under range
IR30000doc 0x7530SYS_modelIDUINT16Read
IR30025doc 0x7549SYS_vendorIDUINT16Read
IR30026doc 0x754ASYS_unitIDUINT16Read
IR30037doc 0x7555SYS_productNameSTRING[20]Read
IR30058doc 0x756ASYS_rs485PortModeUINT16Read0 = initial-repeater; 1 = initial-dual RS- 485; 2 = run-repeater; 3 = run-dual RS-485
HR704doc 0x02C0AI-00_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR705doc 0x02C1AI-01_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR706doc 0x02C2AI-02_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR707doc 0x02C3AI-03_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR708doc 0x02C4AI-04_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR709doc 0x02C5AI-05_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR710doc 0x02C6AI-06_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR711doc 0x02C7AI-07_modeUINT16Read/write0 = 0-10 V; 1 = 0-20 mA; 2 = 4-20 mA burnout; 3 = 4-20 mA
HR30052doc 0x7564SYS_modbusWatchdogFuntionUINT16Read/write0 = Disable; 1 = Enable
HR30053doc 0x7565SYS_modbusWatchdogTimeoutUINT16sRead/write
HR30054doc 0x7566SYS_modbusWatchdogStatusUINT16Read/write0 = Normal; 1 = Timeout
HR30056doc 0x7568SYS_restartDeviceWrite 404 to trigger.UINT16Read/write
HR30057doc 0x7569SYS_loadFactoryDefaultWrite 404 to trigger.UINT16Read/write
HR30060doc 0x756CSYS_port0BaudrateUINT16Read/write1 = 1200; 2 = 2400; 3 = 4800; 4 = 9600; 5 = 19200; 6 = 38400; 7 = 57600; 8 = 115200; 9 = 921600
HR30061doc 0x756DSYS_port1BaudrateUINT16Read/write1 = 1200; 2 = 2400; 3 = 4800; 4 = 9600; 5 = 19200; 6 = 38400; 7 = 57600; 8 = 115200; 9 = 921600
HR30064doc 0x7570SYS_port0StopBitUINT16Read/write0 = 1; 1 = 2
HR30065doc 0x7571SYS_port1StopBitUINT16Read/write0 = 1; 1 = 2
HR30066doc 0x7572SYS_port0ParityUINT16Read/write0 = None; 1 = Even; 2 = Odd
HR30067doc 0x7573SYS_port1ParityUINT16Read/write0 = None; 1 = Even; 2 = Odd

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 Moxa ioLogik R1240 RS-485 remote I/O

What Modbus registers does the Moxa ioLogik R1240 RS-485 remote I/O have?

This map lists 72 registers: 16 coils, 37 input registers, 19 holding registers. 35 of them can be written. Registers vary with firmware, options and configuration, so confirm against the device.

Are the Moxa ioLogik R1240 RS-485 remote I/O Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers hexadecimal, 0-based. 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. Each row prints the hex protocol address and a 1-based reference number (0x0000 = 00001/10001/30001/40001). The hex address is sent on the wire; the table (coil, discrete input, input or holding) is set by the function code column.

What are the minimum Modbus registers to integrate the Moxa ioLogik R1240 RS-485 remote I/O?

Start with IR 30000 SYS_modelID (Model ID check); HR 30052 SYS_modbusWatchdogFuntion (Enable communication watchdog); HR 30053 SYS_modbusWatchdogTimeout (Watchdog timeout); IR 704 AI-00_rawValue (First analog input raw value); IR 992 AI-00_status (First analog input status).

How do I enable Modbus control of the Moxa ioLogik R1240 RS-485 remote I/O?

Set the device ID (1-99) on the two rotary dials. Put the Initial/Run switch on Initial to configure the unit at 9600 baud, no parity, 8 data bits, 1 stop bit (with ioSearch or the SYS_port* registers), then switch back to Run.

What happens when the Moxa ioLogik R1240 RS-485 remote I/O loses Modbus communication?

SYS_modbusWatchdogFuntion (0x7564) enables the host-connection watchdog, SYS_modbusWatchdogTimeout (0x7565) sets the timeout in seconds (factory default 10 s), SYS_modbusWatchdogStatus (0x7566) shows a timeout. It is disabled by default; safe-status settings only act when it is enabled.

Where is the official Moxa ioLogik R1240 RS-485 remote I/O Modbus documentation?

The source is ioLogik R1200 Series User's Manual (Edition 3.4), revision 2021-04. Moxa doesn't publish it on its own website, so this map was re-typed from a free copy at https://cdn11.bigcommerce.com/s-hltjsp5jm3/content/pdfs/moxa-iologik-r1200-series-manual.pdf. It may be an older revision, so check it against the live unit.

More Moxa Modbus register maps

Other remote i/o modules register maps

All remote i/o modules Modbus register maps →

Source: ioLogik R1200 Series User's Manual · Edition 3.4 · rev. 2021-04 · unofficial copy. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.