Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes
Book a demo

Schneider Electric ATV71 Modbus register map

Also searched as: Altivar 71 · ATV71H

926 Modbus registers of the Schneider Electric ATV71, with the address on the wire, the 30001-style reference, data type, byte order, unit and scale. Transcribed from ATV71_communication_parameters_EN_V5.7_IE67 (2) (V5.7).

Altivar 71 variable speed drive; every parameter is a 16-bit holding register at its logic address, except the 32-bit CiA 402 settings.

Registers Read it by name
Device type
Variable speed drive
Registers
926
Interfaces
Modbus RTU, Modbus TCP
Byte order (multi-register values)
ABCD

Hardware verification

Not yet verified on hardware. The map is transcribed from the vendor document and checked against it by script; check the first readings against the device display.

Verify it on your device What the levels mean

Connection notes

  • Logic addresses are sent unchanged, the convention of Schneider's ATV320 and ATV900 Modbus manuals; not yet confirmed in an ATV71 manual.
  • CMD and ETA have two logic addresses in the workbook; the map keeps the speed-profile one and names the other in the notes.
  • Parameter codes (ETA, CMD, LFR...) are in each register's notes; the drive's display uses the same codes.
  • Writing CMD or setpoints moves the motor. Read-only access is the safe default.

Registers

Grouped as in the vendor document. Measurement, energy and identity groups are shown (53 registers); open any other group to load it.

Actual values parameters 7 registers
Name and key Reference Address Type Byte order Unit Scale
Output velocityrfrd 48605 0x219C int16 rpm
Output frequencyrfr 43203 0x0C82 int16 Hz × 0.1
Motor torqueotr 43206 0x0C85 int16
Motor currentlcr 43205 0x0C84 uint16
Motor voltageuop 43209 0x0C88 uint16 V
Motor poweropr 43212 0x0C8B int16 %
ENA average speedavs 412103 0x2F46 int16 Hz × 0.1
Measurement parameters 10 registers
Name and key Reference Address Type Byte order Unit Scale
Dateday 47392 0x1CDF uint16
Timetime 47393 0x1CE0 uint16
Mains voltageuln 43208 0x0C87 uint16 V × 0.1
Energy consumptionaph 43231 0x0C9E uint16
Drive thermal statethd 43210 0x0C89 uint16 %
Motor thermal statethr 49631 0x259E uint16 %
Resistor thermal statethb 414115 0x3722 uint16 %
Total motor operating timerth 43232 0x0C9F uint16
Total drive operating timepth 43234 0x0CA1 uint16
IGBT alarm timetac 43236 0x0CA3 uint16 s
Status parameters 16 registers
Name and key Reference Address Type Byte order Unit Scale
Status wordeta 48604 0x219B bitfield16
Drive statehmis 43241 0x0CA8 uint16
Extended status wordeti 43207 0x0C86 bitfield16
Extended status word 1lrs1 43251 0x0CB2 bitfield16
Extended status word 2lrs2 43252 0x0CB3 bitfield16
Extended status word 3lrs3 43253 0x0CB4 bitfield16
Extended status word 4lrs4 43254 0x0CB5 bitfield16
Extended status word 5lrs5 43255 0x0CB6 bitfield16
Extended status word 6lrs6 43256 0x0CB7 bitfield16
Extended status word 7lrs7 43257 0x0CB8 bitfield16
Extended status word 8lrs8 43258 0x0CB9 bitfield16
Active reference channelcrc 48442 0x20F9 bitfield16
Active command channelccc 48443 0x20FA bitfield16
Config. activecnfs 48021 0x1F54 uint16
EtherCAT Slave Statusecss 46691 0x1A22 uint16
EtherCAT second Address actual valueecaa 46693 0x1A24 uint16
Identification parameters 20 registers
Name and key Reference Address Type Byte order Unit Scale
Drive nominal ratingncv 43012 0x0BC3 uint16
Drive line voltagevcal 43013 0x0BC4 uint16
Rated drive currentinv 43018 0x0BC9 uint16
Drive software versionvdp 43303 0x0CE6 uint16
Device name (char 1 and 2)pan0 43341 0x0D0C uint16
Device name (char 3 and 4)pan1 43342 0x0D0D uint16
Device name (char 5 and 6)pan2 43343 0x0D0E uint16
Device name (char 7 and 8)pan3 43344 0x0D0F uint16
Device name (char 9 and 10)pan4 43345 0x0D10 uint16
Device name (char 11 and 12)pan5 43346 0x0D11 uint16
Device name (char 13 and 14)pan6 43347 0x0D12 uint16
Device name (char 15 and 16)pan7 43348 0x0D13 uint16
Controller name (char 1 and 2)pav1 46982 0x1B45 uint16
Controller name (char 3 and 4)pav2 46983 0x1B46 uint16
Controller name (char 5 and 6)pav3 46984 0x1B47 uint16
Controller name (char 7 and 8)pav4 46985 0x1B48 uint16
Controller name (char 9 and 10)pav5 46986 0x1B49 uint16
Controller name (char 11 and 12)pav6 46987 0x1B4A uint16
Controller name (char 13 and 14)pav7 46988 0x1B4B uint16
Controller name (char 15 and 16)pav8 46989 0x1B4C uint16
Control parameters 3 registers
Name and key Reference Address Type Byte order Unit Scale
Setpoint parameters 6 registers
Name and key Reference Address Type Byte order Unit Scale
Reference parameters 9 registers
Name and key Reference Address Type Byte order Unit Scale
I/O parameters 25 registers
Name and key Reference Address Type Byte order Unit Scale
Fault parameters 12 registers
Name and key Reference Address Type Byte order Unit Scale
History parameters 126 registers
Name and key Reference Address Type Byte order Unit Scale
Communication parameters 17 registers
Name and key Reference Address Type Byte order Unit Scale
Controller inside parameters 50 registers
Name and key Reference Address Type Byte order Unit Scale
CiA 402 settings 10 registers
Name and key Reference Address Type Byte order Unit Scale
Configuration management 3 registers
Name and key Reference Address Type Byte order Unit Scale
Parameter set switching 64 registers
Name and key Reference Address Type Byte order Unit Scale
Configuration and settings 548 registers
Name and key Reference Address Type Byte order Unit Scale

Source documents

  • ATV71_communication_parameters_EN_V5.7_IE67 (2) , Schneider Electric, FA225538, V5.7 (accessed 2026-11-09) XLSX attachment of the support article (https://se.my.site.com/ckmContent/sfc/servlet.shepherd/document/download/069Kj00000kGiIKIA0).

View this map on GitHub (YAML)

Read it by name

Read the ATV71 with an AI assistant

The Proxus Industrial MCP Server includes this map. Set it on the device, and Claude, Cursor or VS Code reads registers by key with the right type, byte order, scale and unit. It only reads.

Get the MCP server

proxus-mcp.json

{
  "devices": {
    "atv71-1": {
      "protocol": "modbus-tcp",
      "host": "192.168.10.40",
      "unit_id": 1,
      "map": "schneider-electric/atv71"
    }
  }
}

Ask your assistant

Read rfrd, rfr, uop from atv71-1.

The tool call it makes

read_named(device: "atv71-1", keys: ["rfrd", "rfr", "uop"])

Have this device? Verify the map.

Ask your assistant to run verify_device_map. It reads every register once, read-only, checks that the values are plausible and asks you to compare two values with the display. You get a report and a prefilled GitHub issue to submit; your name goes on this map’s verified list.

How verification works

Collecting from many devices?

Proxus reads Modbus TCP and RTU devices next to the machines, keeps the history and delivers the values to dashboards, databases and AI.

Modbus in Proxus Industrial connectivity

Data: Modbus Register Maps by Proxus contributors, CC BY 4.0.