TapHome

Delta AC MAX Smart

Modbus TCP
Submitted by
Last updated: 03. 2026
Delta AC MAX Smart

The Delta AC MAX Smart is a Mode 3 AC wallbox for electric vehicle charging, available in 7 kW (single-phase), 11 kW and 22 kW (three-phase) variants. It communicates with TapHome via Modbus TCP over Ethernet on port 502 — no RS-485 wiring is required (unlike the AC MAX Basic which uses Modbus RTU).

The template provides charger and EVSE status monitoring, real-time power metering, and a writable register for charging power limit control. The AC MAX Smart supports a single EVSE connector with offset-based addressing (EVSE 1 = base register + 1000).

The AC MAX Smart shares the same Modbus register document as the Basic variant, but several EVSE-level registers (A:1001, A:1003, A:1007, A:1017, A:1019, A:1047) have been reported as non-functional on the Smart variant by the evcc community. These registers are included in the template and may work with newer firmware versions.

Hardware connection

The AC MAX Smart connects via Ethernet (RJ45). The Ethernet port is located behind a waterproof cap on the bottom of the unit.

Delta AC MAX Smart Ethernet RJ45 port location and cable routing
  1. Remove the waterproof cap
  2. Pass the Ethernet cable through an appropriate conduit or cable gland
  3. Connect the RJ45 cable to the Ethernet port
  4. Secure the cable gland

Use a Category 5 (Cat 5) or better Ethernet cable. Connect the charger to the same local network as TapHome Core.

Mains wiring

The terminal block inside the unit accepts L1, L2, L3, N and PE conductors. Use 10 mm² copper wire with cord end terminals (DIN 46228-4).

Delta AC MAX Smart terminal block with L1, L2, L3, N, PE connections
Wiring diagrams by grounding system

The charger supports TT, TN-C, TN-S, TN-C-S, and IT grounding systems in both single-phase and three-phase configurations.

Delta AC MAX Smart wiring diagrams for TT, TN-C, TN-S, TN-C-S grounding systems
  • Single phase: L1, N, PE
  • Three phase: L1, L2, L3, N, PE (or L1, L2, L3, PE for IT system)

For UK installations on TN-C-S systems, the charger needs a separate ground to a TT system. PME earthing shall not be used for outdoor charging points.

Configuration

DIP switch settings

Six DIP switches on the control board configure charger behavior. Access requires removing the front and middle covers (Torx T20/T30).

DIP PinFunctionOFF (Default)ON
1Phase unbalance protectionDisabledEnabled (limits to 15 A)
2Authorization modeNot availableBluetooth (commissioning)
3Grounding systemTT/TNIT
4-6Maximum currentSee table belowSee table below

Maximum current settings (Pins 4/5/6):

Pin 4Pin 5Pin 6Max Current
OFFOFFOFF6 A (default)
ONOFFOFF8 A
OFFONOFF10 A
ONONOFF12 A
OFFOFFON16 A
ONOFFON20 A*
OFFONON24 A*
ONONON32 A*

* Depends on model configuration. For 16 A models, settings above 16 A fall back to 6 A.

Set the maximum current DIP switches before commissioning. Some vehicles do not initiate a charging session at 6 A (the default).

Enabling Modbus communication

The AC MAX Smart has Modbus TCP enabled by default on port 502. No special configuration is required to activate Modbus communication.

The charger must be set to “Local operation” mode (not OCPP-managed) for external Modbus control to work. This is configured via the Web Configuration Tool.

Web Configuration Tool

Access the charger configuration interface:

Via Ethernet:

  1. Configure laptop IP: 192.168.123.101, Subnet: 255.255.255.0
  2. Open browser, navigate to 192.168.123.123

Via WiFi:

  1. Connect to SSID: Delta-{serial_number}
  2. Password: see Quick Installation Guide
  3. Open browser, navigate to 192.168.5.1

Login: User: admin, Password: see Quick Installation Guide. After 5 failed attempts the account is locked for 5 minutes.

When importing the template in TapHome, provide:

  • IP Address — the charger’s IP on the local network
  • Slave ID — Modbus slave address (default: 1)

Assign a static IP address or DHCP reservation for the charger in the router settings to prevent the address from changing after a power cycle. The charger does not support mDNS discovery.

Device capabilities

Charger and EVSE status

The template provides three status indicators:

  • Charger State — overall charger condition read from register A:100: Not ready (0), Operational (1), or Faulted (2)
  • EVSE Condition — OCPP-based EVSE status read from register A:1000 with 10 states: Unavailable, Available, Occupied, Preparing, Charging, Finishing, Suspended EV, Suspended EVSE, Not ready, Faulted. This is the primary status register confirmed working on the Smart variant.
  • Charge State — charging process state read from register A:1001 with states from “not started” through “charging” to “completed” or “error”. Community reports indicate this register may return “illegal data address” on the Smart variant — use EVSE Condition instead.
Power and energy metering

Real-time electrical measurements from the EVSE:

  • Charging Power — instantaneous charging power in watts (A:1005). Confirmed working on the Smart variant, though some firmware versions may have UINT32 format discrepancies.
  • Output Voltage — charging voltage in volts (A:1003, scaled /10)
  • Output Current — charging current in amps (A:1007, scaled /100)
  • Charged Energy — energy transferred to the EV during the current session in Wh (A:1019)
  • Total Power Consumption — total power consumption at the grid connection in watts (A:1047)
  • Charging Time — duration of the current charging session in minutes (A:1017, converted from seconds /60)

Community testing indicates that registers A:1003, A:1007, A:1017, A:1019, and A:1047 may return zero values on some Smart firmware versions. These registers are included in the template and may work with newer firmware. The Charging Power register (A:1005) and EVSE Condition (A:1000) are confirmed working.

Charging control
  • Charging Power Limit (H:1600) — sets the maximum charging power in watts. Writing 0xFFFFFFFF removes the limit (displayed as no value). Reading is confirmed working on the Smart variant. Writing may not take effect on all firmware versions.
Additional capabilities

The AC MAX Smart also exposes registers for per-phase grid power consumption (L1, L2, L3), per-phase EVSE current, max/min charging power determined by EVSE, IEC 62196 plug state, and RFID authentication ID. Communication timeout registers (H:201-203) allow configuring a safety fallback power level if no Charging Power Limit command is received within a specified interval. The Suspend Charging register (H:1602) present in the Basic variant template is not included in the Smart template but may be available. These can be added in a future template update.

The communication timeout feature (registers H:201-203) is useful for safety: if TapHome loses communication with the charger, a preconfigured fallback power level is applied automatically. This can be configured directly via Modbus writes to H:201 (enable), H:202 (timeout in seconds, 0-600) and H:203 (fallback power in watts).

Troubleshooting

No Modbus communication
  1. Verify the Ethernet cable is connected to the RJ45 port (not the USB port)
  2. Confirm the charger is set to “Local operation” mode (not OCPP-managed)
  3. Ensure TapHome Core and the charger are on the same network/subnet
  4. Check that Modbus TCP port 502 is not blocked by a firewall
  5. Try accessing the Web Configuration Tool (192.168.123.123 via Ethernet) to verify the charger is reachable
Register read errors (illegal data address)

Some EVSE registers (particularly A:1001 Charge State) return “illegal data address” on the Smart variant. This is a known limitation. Use the EVSE Condition register (A:1000) for status monitoring instead.

Charging Power reads incorrect values

The Charging Power register (A:1005) may show UINT32 format discrepancies on some firmware versions. If the value appears incorrect, check the firmware version via the Web Configuration Tool and update if a newer version is available.

Charging Power Limit has no effect

Writing to H:1600 has been reported as ineffective on some firmware versions. Ensure the charger firmware is up to date. Firmware updates can be uploaded via the Web Configuration Tool.

LED indicator reference
LED ColorStatus
BlackPower off
Blue (steady)Standby, no vehicle connected
Yellow (steady)Ready to charge, vehicle connected
Blue (slow flash)Charging in progress
GreenCharging completed
Yellow (1 flash)Network connection failure
Yellow (slow flash)Power limited / FW upgrade / log download
Red (slow flash)Fault event
Red (steady)Self-test failure or general malfunction

Available devices

Delta AC MAX Smart Module
Service Attributes
Model
Serial Number
EVSE Count
Charger Error

Delta AC Max Smart

Service Attributes
Model
modbusr(A, 130, String, 19)
Serial Number
modbusr(A, 110, String, 20)
EVSE Count
modbusr(A, 102, Uint16)
Charger Error
modbusr(A, 103, Uint32)
Charging Time Variable Read-only

Duration of current charging session in minutes

Register: A:1017 Uint32 Unit: min numeric

Charging Time

Read
MODBUSR(A, 1017, Uint32) / 60
Output Current Variable Read-only

Actual charging current at the EVSE output in amps

Register: A:1007 Uint32 Unit: A numeric

Output Current

Read
MODBUSR(A, 1007, Uint32) / 100
Output Voltage Variable Read-only

Actual charging voltage at the EVSE output in volts

Register: A:1003 Uint32 Unit: V numeric

Output Voltage

Read
MODBUSR(A, 1003, Uint32) / 10
EVSE Condition Multi-value Switch Read-only

OCPP-based EVSE status — Unavailable, Available, Occupied, Preparing, Charging, Finishing, Suspended EV, Suspended EVSE, Not ready, Faulted

Register: A:1000 Uint16 enum
Values / States: Unavailable · Available · Occupied · Preparing · Charging · Finishing · Suspended EV · Suspended EVSE · Not ready · Faulted

EVSE Condition

Read switch state
MODBUSR(A, 1000, Uint16)
Total Power Consumption Variable Read-only

Total power consumption at the grid connection including charging losses

Register: A:1047 Uint32 Unit: W numeric

Total Power Consumption

Read
MODBUSR(A, 1047, Uint32)
Charge State Multi-value Switch Read-only

Charging process state — Not started, Connected waiting, Starting, Charging, Suspended, Completed, Completed by user, Error

Register: A:1001 Uint16 enum
Values / States: Charging process not started (no vehicle connected) · Connected, waiting for release (by RFID or local) · Charging process starts · Charging · Suspended (loading paused) · Charging process successfully completed (vehicle still plugged in) · Charging process completed by user (vehicle still plugged in) · Charging ended with error (vehicle still connected)

Charge State

Read switch state
MODBUSR(A, 1001, Uint16)
Charged Energy Variable Read-only

Energy transferred to the EV during current session in Wh

Register: A:1019 Uint32 Unit: Wh numeric

Charged Energy

Read
MODBUSR(A, 1019, Uint32)
Charging Power Variable Read-only
Register: A:1005 Uint32 Unit: W numeric

Charging Power

Read
MODBUSR(A, 1005, Uint32)
Charging Power Limit Variable

Maximum allowed charging power in watts — writable, no-limit value displays as empty

Register: H:1600 Int32 Unit: W numeric

Charging Power Limit

Read
var out := MODBUSR(H, 1600, Int32);
#0xffffffff
if out = 4294967295 
	return(nan);
else
	return(out);
end
Write
MODBUSW(H, 1600, Int32, Va)
Charger State Multi-value Switch Read-only

Overall charger condition — Not ready, Operational, Faulted

Register: A:100 Uint16 enum
Values / States: Not ready · Operational · Faulted

Charger State

Read switch state
MODBUSR(A, 100, Uint16)
Connection: Modbus TCP • Slave ID: $[SlaveId]
Possible improvements (17)
  • H:200 Slave ID — Modbus slave address, default 1 — can also be changed via charger settings
  • H:201 Communication Timeout Enable — 0=Disabled, 1=Enabled — enables safety timeout for comm loss. Confirmed working on Smart
  • H:202 Communication Timeout — 0–600 seconds — if no Charging Power Limit received within timeout, fallback power is applied
  • H:203 Fallback Power — Default charging power (W) applied on communication timeout
  • H:1602 Suspend Charging — 0=Resume, 1=Pause — leaves cable locked while paused. Present in Basic variant template but missing from Smart template. Marked TBC for AC MAX in docs
  • A:1009 Actual Output Power — Float32, watts — available on UFC/SLIM, community reports returns 0 on Smart
  • A:1013 Max Charging Power — UINT32, watts — max charging power determined by EVSE. Confirmed working on Smart per evcc community
  • A:1015 Min Charging Power — UINT32, watts — min charging power determined by EVSE. Confirmed working on Smart per evcc community
  • A:1049 Power Consumption L1 — Float32, watts — per-phase grid consumption (TBC on AC MAX)
  • A:1051 Power Consumption L2 — Float32, watts — per-phase grid consumption (TBC on AC MAX)
  • A:1053 Power Consumption L3 — Float32, watts — per-phase grid consumption (TBC on AC MAX)
  • A:1067 EVSE Total Current — Float32, amps — total EVSE current (TBC on AC MAX)
  • A:1069 EVSE L1 Current — Float32, amps — per-phase EVSE current (TBC on AC MAX)
  • A:1071 EVSE L2 Current — Float32, amps — per-phase EVSE current (TBC on AC MAX)
  • A:1073 EVSE L3 Current — Float32, amps — per-phase EVSE current (TBC on AC MAX)
  • A:1075 ISO 62196 State — UINT16, enum — IEC 62196 plug states A through F (TBC on AC MAX)
  • A:1100 RFID UID — String(19), returns 'Delta Station' on Smart — confirmed working per evcc community

Sources