Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes

Schneider Electric ATV320 Modbus register map

Also searched as: Altivar Machine ATV320 · ATV320U · ATV320D

1,071 Modbus registers of the Schneider Electric ATV320, with the address on the wire, the 30001-style reference, data type, byte order, unit and scale. Transcribed from ATV320 - communication parameters addresses (V3.5).

Altivar Machine ATV320 variable speed drive; every parameter is a 16-bit holding register at its logic address.

Device type
Variable speed drive
Registers
1,071
Interfaces
Modbus RTU, Modbus TCP
Byte order (multi-register values)
ABCD
Serial settings
19200 baud, 8 data bits, even parity, 1 stop bit

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

  • The Modbus address of the drive is OFF from the factory; set [Modbus Address] (Add) before connecting.
  • Modbus TCP needs an Ethernet communication module.
  • 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 (57 registers); open any other group to load it.

Actual values parameters 11 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 % × 0.1
Motor currentlcr 43205 0x0C84 uint16 A × 0.1
Motor voltageuop 43209 0x0C88 uint16 V
Motor poweropr 43212 0x0C8B int16 %
AO1 physical value without filtersao1 45296 0x14AF int16
Motor speedspd 412005 0x2EE4 uint16
PLC encoder pulsepuc 45612 0x15EB uint16
Output value Customerspd1 412009 0x2EE8 uint16 × 0.01
Ratio D-Axis Current Errorrdae 49677 0x25CC int16 % × 0.1
Measurement parameters 14 registers
Name and key Reference Address Type Byte order Unit Scale
Line mains voltageuln 43208 0x0C87 uint16 V × 0.1
Drive thermal statethd 43210 0x0C89 uint16 %
Motor thermal statethr 49631 0x259E uint16 %
Motor run timerth 43232 0x0C9F uint16
Power on timepth 43234 0x0CA1 uint16
AI1 physical value without filtersai1 45292 0x14AB int16 V × 0.001
AI2 physical value without filtersai2 45293 0x14AC int16 V × 0.001
AI3 physical value without filtersai3 45294 0x14AD int16 mA × 0.001
AI1 input physical image (MAX = 8192)ai1i 45223 0x1466 int16
AI2 input physical image (MAX = 8192)ai2i 45224 0x1467 int16
AI3 input physical image (MAX = 8192)ai3i 45225 0x1468 int16
Power consumptionaph 43231 0x0C9E uint16
IGBT alarm countertac 43236 0x0CA3 uint16 s
Min IGBT frequency timetac2 43243 0x0CAA uint16 s
Status parameters 20 registers
Name and key Reference Address Type Byte order Unit Scale
Drivecom state registereta 43202 0x0C81 bitfield16
Drive statehmis 43241 0x0CA8 uint16
Extended state registereti 43207 0x0C86 bitfield16
Reference channelcrc 48442 0x20F9 bitfield16
Active command channelccc 48443 0x20FA bitfield16
Active configurationcnfs 48021 0x1F54 uint16
Tune selectionstun 49618 0x2591 uint16
Status of motor tune in term of saliencysmot 49646 0x25AD uint16
EtherCAT slave statusecss 46691 0x1A22 uint16
EtherCAT addressecaa 46693 0x1A24 uint16
DRIVECOM : Status wordetad 48604 0x219B bitfield16
Logic result status 1 (PSL 000-015)lrs1 43251 0x0CB2 bitfield16
Logic result status 2 (PSL 016-031)lrs2 43252 0x0CB3 bitfield16
Logic result status 3 (PSL 032-047)lrs3 43253 0x0CB4 bitfield16
Logic result status 4 (PSL 048-063)lrs4 43254 0x0CB5 bitfield16
Logic result status 5 (PSL 064-079)lrs5 43255 0x0CB6 bitfield16
Logic result status 6 (PSL 080-095)lrs6 43256 0x0CB7 bitfield16
Logic result status 7 (PSL 096-111)lrs7 43257 0x0CB8 bitfield16
Logic result status 8 (PSL 112-127)lrs8 43258 0x0CB9 bitfield16
IGBT alarm Nbntj 43242 0x0CA9 uint16
Identification parameters 12 registers
Name and key Reference Address Type Byte order Unit Scale
Drive nominal ratingncv 43012 0x0BC3 uint16
Drive mains voltagevcal 43013 0x0BC4 uint16
Drive nominal currentinv 43018 0x0BC9 uint16 A × 0.1
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
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 8 registers
Name and key Reference Address Type Byte order Unit Scale
I/O parameters 13 registers
Name and key Reference Address Type Byte order Unit Scale
Fault parameters 8 registers
Name and key Reference Address Type Byte order Unit Scale
History parameters 154 registers
Name and key Reference Address Type Byte order Unit Scale
Communication parameters 19 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 524 registers
Name and key Reference Address Type Byte order Unit Scale
Safety function 153 registers
Name and key Reference Address Type Byte order Unit Scale
Function blocks 49 registers
Name and key Reference Address Type Byte order Unit Scale

Source documents

View this map on GitHub (YAML)

Read it by name

Read the ATV320 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.

proxus-mcp.json

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

Ask your assistant

Read rfrd, rfr, otr from atv320-1.

The tool call it makes

read_named(device: "atv320-1", keys: ["rfrd", "rfr", "otr"])

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.

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