MBMap Registry
  1. Devices
  2. Webasto
  3. NEXT

Webasto NEXT Modbus register map

EV charging station with a Modbus TCP server for energy management systems

  • Official
  • 30 registers
  • Modbus TCP
  • Revision 1 · 2026-11-11

Official: Written from the manufacturer's documentation, but not tested on a device yet. Check the map against the manufacturer's documentation before you write to a live device. Tested it? Report a test.

Download .mbmap.json Raw JSON View on GitHub Suggest a correction Report a problem

Communication

Protocol
Modbus TCP
Unit ID
255
TCP port
502
Byte / word order
ABCD · bytes big-endian, words high first
Addresses
0-based

Connection values are defaults: the device may be configured differently.

Map

Registers
30 holding registers
Groups
5
Translation tables
6
Revision
1 · 2026-11-11
Added
()
File
maps/webasto/next.mbmap.json · 10 KB · history
SHA-256
a250d9a08bd4d46f8671779d8ad6e07da37fa0ea11383c13a7dcfe60c6184a11
Manufacturer
webasto.com

Sources and notes

  • Modbus Specification Webasto NEXT (Webasto_NEXT_Modbus_Register_1-00_external_V3) · version 3.00, 2022-04-27
    All registers in the document belong to the master device TQ-DM100

Source: Webasto, Modbus Specification Webasto NEXT, register list revision 3.00 (2022-04-27)

  • Modbus TCP, port 502, unit ID 255. Each wallbox needs its own IP address on the subnet and the energy manager is the Modbus client. All registers are holding registers.
  • Two-register values are listed in the document as address + address+1 (for example 1020+1021); the word order is not stated and big is assumed.
  • The register list is under the master device 'TQ-DM100'. Webasto Live has a setting for its register address set (the TQ-DM100 set is one of the options); this document is only for the NEXT, so the Live is not covered by it.
  • Write-only registers (5000 charge power, 5004 charge current, 5006 start or cancel) are marked W. Safe current and the communication timeout apply if the energy manager stops writing the life bit (6000).
  • Webasto gives no support for this document; the manufacturer's notice says problems that arise from using it are the customer's responsibility.
AreaAddressNameTypeAccessUnitScaleDescription
HR 1000 uint16 R
HR 1001 uint16 R
HR 1002 uint16 R
HR 1004 uint16 R
HR 1006 uint16 R 0 = no error; 1 and above are error codes of appendix 1
HR 1008 uint16 R mA
HR 1010 uint16 R mA
HR 1012 uint16 R mA
HR 1020 uint32 ABCD R W
HR 1024 uint32 ABCD R W
HR 1028 uint32 ABCD R W
HR 1032 uint32 ABCD R W
HR 1036 uint32 ABCD R Wh Meter reading of the charging station
HR 1100 uint16 R A Maximal charging current of the hardware (EVSE, cable, EV)
HR 1102 uint16 R A Minimal charging current of the hardware
HR 1104 uint16 R A
HR 1106 uint16 R A
HR 1108 uint16 R A
HR 1502 uint16 R Wh Energy of the last session; 0 during a session
HR 1504 uint32 ABCD R hhmmss Start of the current or last session as hhmmss
HR 1508 uint32 ABCD R s Duration since the start of the charge
HR 1512 uint32 ABCD R hhmmss End of the last session as hhmmss; 0 during a session
HR 1600 string[10] R OCPP IdTag of the current session, 20 bytes of ASCII hex codes
HR 1620 uint32 ABCD R 1 if the connected EV is a smart vehicle, 0 otherwise
HR 2000 uint16 RW A Maximum charge current during a communication failure
HR 2002 uint16 RW s
HR 5000 uint32 ABCD W W
HR 5004 uint16 W A
HR 5006 uint16 W
HR 6000 uint16 RW Communication monitoring toggle bit: the energy manager writes 1 every half of the timeout and the wallbox resets it to 0

Help improve this map

Esc