Easy Modbus
  1. Home
  2. Modbus register maps
  3. Lenze
  4. SMVector drive with ESVZAR0 RS-485 Modbus module

Variable frequency drive · Modbus register map

Lenze SMVector drive with ESVZAR0 RS-485 Modbus module Modbus register map

Updated 17 November 2026

Short answer

The SMVector is a Lenze AC Tech inverter (models up to 10 HP in this guide). The ESVZAR0 option module adds Modbus RTU on RS-485. Registers 1-99 are network control and status (control word, status word, frequencies, load, fault, run-hour counters, network speed/PID/torque commands); every drive parameter Pxxx is also readable as register xxx.

This page lists 33 Modbus registers for the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module — 15 writable — with the table, 0-based wire address, data type, word order, scale, units and access of each, re-typed from Lenze’s own free documentation (linked below) and checked against it.

Manufacturer
Lenze
Model
SMVector drive with ESVZAR0 RS-485 Modbus module
Equipment type
Variable frequency drive
Registers
33 (15 writable)
Transport
Modbus RTU
Default unit ID
1
Default serial
9600 baud, 8N2
Documented addressing
derived from parameter numbers
32-bit word order
CDAB low word first (word-swapped)
Firmware
ESVZAR0 module software 1.01, 1.10 or 1.30 (check P494 before writing)
Also known as
SMVector, SMV, ESVZAR0, Lenze AC Tech SMV, CMVMB401C
Source document
SMVector ESVZAR0 RS-485 Modbus Communication Module - Communications Interface Reference Guide · CMVMB401C · unofficial copy
Download CSV all columns JSON Manufacturer PDF ↗

Integration notes: Lenze SMVector drive with ESVZAR0 RS-485 Modbus module

Integration in brief

Set P400 = 2, address/baud/format in P410-P412, then read #23-#29 for status, frequencies, load and fault. To run from the network: assert a terminal set to NET ENABLE, write 0 to #48 to unlock #1 (or the P194 password to also unlock #44), then write control bits to #1 and the speed to #44.

Minimum registers to map

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

RegisterNameTypeWhyAccess
HR 1Drive controlBITMAP16Control word: start/stop/directionWrite
HR 48Unlock controlsUINT16Unlock controlsWrite
HR 44Network speed commandUINT16Network speed commandRead/write
HR 23Drive statusBITMAP16Status wordRead
HR 25Actual frequencyUINT16Actual frequencyRead
HR 29Present fault (high byte) / commanded direction (low byte)UINT16Present faultRead

Enable Modbus control & writes

P400 = 2 (Modbus RTU); P410 address, P411 baud, P412 format. For control set one of P121-P123 to 09 (NET ENABLE) and close that TB-13 input, and P100 to 00, 01, 03 or 04. Use P101 = 06 or bits 12-15 of #1 to make the network the speed reference.

Communication loss & watchdog

Once controls are unlocked via #48, P425 (0-300 s, default 10.0 s) sets the message time-out and P426 the action (default trip fault). Any read keeps it alive.

Byte order & addressing

Network setup

Watch out for

Lenze SMVector drive with ESVZAR0 RS-485 Modbus module 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.

33 of 33 shown
Lenze SMVector drive with ESVZAR0 RS-485 Modbus module Modbus register map
TableAddressNameDescriptionTypeOrderScaleUnitsAccessValues / bits
HR1doc #1 (4X 40002)Drive controlSet one bit per write (0x0008 start, 0x0004 stop). Unlock via #48 first.BITMAP16Writebit 0 = Quick stop; bit 1 = Lock security (ends network control); bit 2 = Stop (per P111); bit 3 = Start; bit 4 = Inhibit; bit 5 = Network reference off; bit 6 = Set reverse; bit 7 = Set forward; bit 8 = Stop forcing manual reference; bit 9 = Force manual reference (P101); bit 10 = DC braking on; bit 11 = DC braking off; bit 12 = Network reference select (bits 12-15 enumeration)
HR19doc #19 (4X 40020)Drive familyReads 72 for SMVector.UINT16Read
HR21doc #21 (4X 40022)Drive size indexVoltage / power rating code (table 7 of the guide).UINT16Read
HR23doc #23 (4X 40024)Drive statusBITMAP16Readbit 0 = Running (0 = stopped); bit 1 = Quick stop active; bit 2 = Commanded direction reverse; bit 3 = Actual direction reverse; bit 4 = Network reference sets active source; bit 5 = Network enable active; bit 6 = Closed loop (PID on); bit 7 = AUTO source; bit 8 = Set point source code bit 0; bit 9 = Set point source code bit 1; bit 10 = Set point source code bit 2; bit 11 = Set point source code bit 3; bit 12 = Control source code bit 0; bit 13 = Control source code bit 1; bit 14 = Network control enabled; bit 15 = DC braking active
HR24doc #24 (4X 40025)Command frequencyUINT16× 0.1HzRead
HR25doc #25 (4X 40026)Actual frequencyUINT16× 0.1HzRead
HR26doc #26 (4X 40027)Load (high byte) / run status (low byte)High byte = load % of rated current; low byte = operational status code.UINT16Read
HR27doc #27 (4X 40028)Actual direction (high byte) / control mode (low byte)High: 0 fwd, 1 rev. Low: 0 local, 1 terminal, 2 remote keypad, 3 net only, 4 net control.UINT16Read
HR28doc #28 (4X 40029)Speed source (high byte) / auto-manual (low byte)High: 0 keypad ... 11 network, 12 jog. Low: 0 manual, 1 auto.UINT16Read
HR29doc #29 (4X 40030)Present fault (high byte) / commanded direction (low byte)High byte = fault code (see notes). Low: 0 fwd, 1 rev.UINT16Read
HR37doc #37 (4X 40038)Actual PID setpointSigned, one decimal.INT16× 0.1Read
HR38doc #38 (4X 40039)PID setpoint commandINT16× 0.1Read
HR39doc #39 (4X 40040)PID feedbackINT16× 0.1Read
HR40doc #40 (4X 40041)Keypad speed commandUINT16× 0.1HzRead/write
HR41doc #41 (4X 40042)Keypad PID setpoint commandINT16× 0.1Read
HR42doc #42 (4X 40043)Keypad torque commandUINT16× 0.1%Read/write
HR44doc #44 (4X 40045)Network speed commandP102 to P103. Used when the network is the speed reference.UINT16× 0.1HzRead/write
HR46doc #46 (4X 40047)Network torque command0.0-400.0 %.UINT16× 0.1%Read/write
HR48doc #48 (4X 40049)Unlock controls0 unlocks register #1; the password (P194, default 225) unlocks all.UINT16Write
HR49doc #49 (4X 40050)Unlock parametersPassword (P194) unlocks all writable registers except #1.UINT16Write
HR50doc #50 (4X 40051)Parameter versionUINT16Read
HR60doc #60 (4X 40061)Total run time hoursLow word at #60, high word at #61.UINT32CDABhRead
HR64doc #64 (4X 40065)Total power-on hoursLow word at #64, high word at #65.UINT32CDABhRead
HR70doc #70 (4X 40071)Network controlled digital output + relayNeeds P140/P142 = 25 (network controlled).BITMAP16Read/writebit 9 = TB-14 output energized; bit 10 = Relay energized
HR71doc #71 (4X 40072)Network controlled analog outputNeeds P150 = 09 (network controlled).UINT16× 0.1%Read/write
HR400doc #400 (4X 40401)P400 network protocolUINT16Read/write0 = Not active; 1 = Remote keypad; 2 = Modbus RTU
HR402doc #402 (4X 40403)P402 module statusUINT16Read0 = Not initialized; 1 = Init: module to EPM; 2 = Init: EPM to module; 3 = Online; 4 = Failed initialization; 5 = Time-out error; 6 = Initialization failed; 7 = Initialization error
HR410doc #410 (4X 40411)P410 network address1-247, default 1.UINT16Read/write
HR411doc #411 (4X 40412)P411 baud rateUINT16Read/write0 = 2400; 1 = 4800; 2 = 9600 (default); 3 = 19200; 4 = 38400; 5 = 57600; 6 = 115200
HR412doc #412 (4X 40413)P412 data formatUINT16Read/write0 = 8N2 (default); 1 = 8N1; 2 = 8E1; 3 = 8O1
HR425doc #425 (4X 40426)P425 network message time-out0.0-300.0 s, default 10.0 s.UINT16× 0.1sRead/write
HR426doc #426 (4X 40427)P426 time-out actionUINT16Read/write0 = Not active; 1 = Stop (P111); 2 = Quick stop; 3 = Inhibit; 4 = Trip fault (default)
HR530doc #530 (4X 40531)P530 terminal and protection statusBITMAP16Readbit 2 = Protection status; bit 3 = Fast current limit; bit 4 = Input TB-1; bit 6 = Input TB-13A; bit 7 = Input TB-13B; bit 8 = Input TB-13C; bit 9 = Output TB-14; bit 10 = Relay output; bit 11 = Charge relay; bit 12 = Assertion level switch

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 Lenze SMVector drive with ESVZAR0 RS-485 Modbus module

What Modbus registers does the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module have?

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

Are the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module Modbus addresses 0-based or 1-based?

The manufacturer's document numbers registers derived from parameter numbers. 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. Lenze numbers registers by drive register #, and Modbus 4X/3X register = drive register + 1. The drive register # is the wire address: the guide's example reads #60 with start address 0x003C. Drive parameter Pxxx is register #xxx (P103 = #103).

What byte order does the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module use for 32-bit values?

Multi-register values in this map use CDAB (low word first (word-swapped)). Set your client to this order for every 32/64-bit value in the table.

What are the minimum Modbus registers to integrate the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module?

Start with HR 1 Drive control (Control word: start/stop/direction); HR 48 Unlock controls (Unlock controls); HR 44 Network speed command (Network speed command); HR 23 Drive status (Status word); HR 25 Actual frequency (Actual frequency); HR 29 Present fault (high byte) / commanded direction (low byte) (Present fault).

How do I enable Modbus control of the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module?

P400 = 2 (Modbus RTU); P410 address, P411 baud, P412 format. For control set one of P121-P123 to 09 (NET ENABLE) and close that TB-13 input, and P100 to 00, 01, 03 or 04. Use P101 = 06 or bits 12-15 of #1 to make the network the speed reference.

What happens when the Lenze SMVector drive with ESVZAR0 RS-485 Modbus module loses Modbus communication?

Once controls are unlocked via #48, P425 (0-300 s, default 10.0 s) sets the message time-out and P426 the action (default trip fault). Any read keeps it alive.

Where is the official Lenze SMVector drive with ESVZAR0 RS-485 Modbus module Modbus documentation?

The source is SMVector ESVZAR0 RS-485 Modbus Communication Module - Communications Interface Reference Guide (CMVMB401C). Lenze doesn't publish it on its own website, so this map was re-typed from a free copy at https://www.precision-elec.com/wp-content/uploads/2014/08/lenze-ac-tech-rs485-modbus-communications-reference.pdf. It may be an older revision, so check it against the live unit.

More Lenze Modbus register maps

Other variable frequency drives register maps

All variable frequency drives Modbus register maps →

Source: SMVector ESVZAR0 RS-485 Modbus Communication Module - Communications Interface Reference Guide · CMVMB401C · unofficial copy. Register numbers, types, scaling and units are reproduced as published; descriptions are our own.