Skip to main content
v5.33
operator
manufacturer
Last updated on

Modbus TCP API

This document provides a complete overview of the Modbus Slave features of the Charge Controller.
Based on revision v0.14.

1. Config UI parameters reference for Operators​

Parameter nameDescription
Modbus TCP ServerAllows to turn the Charge Controller into a Modbus TCP Server. This allows reading and writing parameters using the Modbus protocol. See the documentation for detailed register information.
Modbus TCP Server Base PortPort number on which the Modbus TCP Server waits for incoming connections on connector 1. In case a second connector is supported, the configured 'port + 1' will be used for that connector.
Modbus TCP Server Register Address SetChoose the set of register addresses that the Modbus TCP Server device will expose to its client.
Modbus TCP Server Allow Start/Stop TransactionAllows transactions to be started/stopped from a Modbus Master device via the controller's Modbus TCP Server interface.
Modbus TCP Server Allow UID DiscloseAllows sending the UID over the Ebee Modbus TCP Server protocol

2. Modbus Unit ID​

The Modbus TCP Server on the charge controller will reply to messages with any Unit ID from 1 to 255.

3. OCPP multiple connector scenarios​

On an OCPP setup with 2 connectors, both controllers are accessible by connecting through the one acting as a master controller. In this case it is necessary to establish a separate connection to each charge controller.

The second connector's controller is accessible on the port corresponding to Modbus TCP Server Base Port + 1.

Assuming that the Modbus TCP Server Base Port is configured on the default port 502, the first connector can be accessed by connecting a Modbus Client to port 502, and the second connector can be accessed by connecting a separate Modbus Client to the first connector charge controller's port 503.

4. Word and byte ordering​

With the notable exception of the values in the register destined to error codes (those with names prefixed with ERROR_CODES_ ) which are explained separately in their corresponding section, all other registers are to be read and written with the high byte first and the low byte after. For double registers (32-bit) the order of the words is the high word first and the low word after.

As an example, if registers 200-201 are read and contain a value of 0x0001 for register 200 and a value of 0x1F40 for register 201, these values are to be read as 0x00011F40, that is a decimal value of 73536.

5. Lowering charging current​

To lower the charging currant the HEMS shall write to the Register HEMS_CURRENT_LIMIT as described in the HEMS configuration options section.

Please note the actual signaled current as indicated by the register named SIGNALED_CURRENT can be lower than the HEMS_CURRENT_LIMIT since other limitations (such as charging cable, or dynamic load management limits) could apply.

6. Supported function codes​

All registers described in this document are HOLDING registers. Therefore, the only supported function codes are:

  • 0x03 -- Read single register
  • 0x06 -- Write single register
  • 0x10 -- Write multiple registers.

7. Bulk read of registers​

It is possible to read a range of registers at a time (bulk read) starting at a specified register and within the boundaries of the register section.

info

If there are gaps with undefined register numbers in this range, value '0' will be returned.

ifthen
the requested range ends in the middle of a 32-bit registerthe last register will be discarded and no value returned. Increase the range by 1

8. General system information​

The register in the first table that follows contain general information about the system, about its status, error states, FW and protocol versions and other system and configuration information.

note on OCPP_CP_STATUS

The Charge Point Status as defined in OCPP 1.5 and 1.6 is available in the OCPP_CP_STATUS register. Note that there's some difference between the two versions, so for example the value 1, which is used for "Occupied", is only valid for OCPP 1.5 and instead in 1.6 a more detailed value is available. For the descriptions of each of the charge point status values, please refer to the OCPP specification that corresponds to the version in use.

For details on how to read and interpret the registers designated for error handling please refer to the section Error states mask mappings.

Register Addr.Bit fieldSizeTypeNameDescription
100-10131:032-BitREADFIRMWARE_VERSIONEbee Application version number. example: 0.91 = (0x30, 0x2E, 0x39, 0x31), 4.40 = (0x34, 0x2E, 0x34, 0x34).
10415:016-BitREADOCPP_CP_STATUS0 = Available 1 = Occupied 2 = Reserved 3 = Unavailable 4 = Faulted 5 = Preparing 6 = Charging 7 = SuspendedEVSE 8 = SuspendedEV 9 = Finishing
105-10631:032-BitREADERROR_CODES_1See Error states mask mappings section for mask bit values.
107-10863:3232-BitREADERROR_CODES_2
109-11095:6432-BitREADERROR_CODES_3
111-112127:9632-BitREADERROR_CODES_4
120-12131:032-BitREADPROTOCOL_VERSIONEbee Modbus Slave Protocol Version number (example: 0.6 = 54). This corresponds to the Doc. Revision at the top of this document.
12215:016-BitREADVEHICLE_STATEControl Pilot vehicle state in decimal format: A = 1, B = 2, C = 3, D = 4, E = 5
12415:016-BitREAD & WRITECP_AVAILABILITYRead or set the Charge Point availability. 0 = Operative. 1 = Inoperative.
13115:016-BitREAD & WRITESAFE_CURRENTMax. charge current under communication failure with the Modbus Master.
168-16931:032-BitREADMANU_SERIAL_1Identifies the serial number as set by the Manufacturer.
This is a non-null terminated ASCII string of maximum 25 characters.
If the string is fewer than 25 characters, it is padded on the left (the lowermost registers) with blank-space ASCII characters.
170-17163:3232-BitREADMANU_SERIAL_2
172-17395:6432-BitREADMANU_SERIAL_3
174-175127:9632-BitREADMANU_SERIAL_4
176-177159:12832-BitREADMANU_SERIAL_5
178-179191:16032-BitREADMANU_SERIAL_6
180207:19216-BitREADMANU_SERIAL_7

9. Meter values from OCPP primary meter​

Meter values are unsigned and sent in 32-bit words.

tip

When not available, registers contain a 0xffffffff value to indicate that no meter value for the requested register is present.

ifbecausethen
the line-specific power and energy isn't availablethe installation is single-phasedonly the Total Power and Total Energy is available
the meter doesn't support readings
tip

For maintaining backwards compatibility with previous systems, where the METER_TOTAL_ENERG and METER_TOTAL_POW registers were not present, the Total Power and Total Energy values can also be read from the Power and Energy registers corresponding to L1. In that case, the Power and Energy registers for L2 and L3 will return 0xffffffff.

Register Addr.Bit fieldSizeTypeNameDescription
200-20131:032-BitREADMETER_ENERG_L1Energy in Wh (phase 1) from primary meter
202-20331:032-BitREADMETER_ENERG_L2Energy in Wh (phase 2) from primary meter
204-20531:032-BitREADMETER_ENERG_L3Energy in Wh (phase 3) from primary meter
206-20731:032-BitREADMETER_POW_L1Power in W (phase 1) from primary meter
208-20931:032-BitREADMETER_POW_L2Power in W (phase 2) from primary meter
210-21131:032-BitREADMETER_POW_L3Power in W (phase 3) from primary meter
212-21331:032-BitREADMETER_CUR_L1Current in mA (phase 1) from primary meter
214-21531:032-BitREADMETER_CUR_L2Current in mA (phase 2) from primary meter
216-21731:032-BitREADMETER_CUR_L3Current in mA (phase 3) from primary meter
218-21931:032-BitREADMETER_TOTAL_ENERGTotal Energy in Wh from primary meter
220-22131:032-BitREADMETER_TOTAL_POWTotal Power in W from primary meter
222-22331:032-BitREADMETER_VOL_L1Voltage in V (phase 1) from primary meter
224-22531:032-BitREADMETER_VOL_L2Voltage in V (phase 2) from primary meter
226-22731:032-BitREADMETER_VOL_L3Voltage in V (phase 3) from primary meter

10. Dynamic Load Management (DLM)​

This is information mostly concerning the DLM Master. Everything except for register 600 will be available only for devices with a DLM Master role set (meaning a value of 1 or 2 is returned on this register). | -->

Register Addr.Bit fieldSizeTypeNameDescription
60015:016-BitREADDLM_MODEIndicates the DLM mode configured for this device.
The following values represent each mode:
0 = Disabled
1 = DLM Master (With internal DLM-Slave)
2 = DLM Master (Standalone)
3 = DLM Slave (Master-Auto-Discovery)
4 = DLM Slave (Master-Fixed-IP)
61015:016-BitREADDLM_EVSE_SUB_DISTRIBUTION_LIMIT_L1Overall current limit for DLM available for distribution to Evs.
These three registers are for L1, L2, and L3 respectively and the values are in Amps.
61115:016-BitREADDLM_EVSE_SUB_DISTRIBUTION_LIMIT_L2
61215:016-BitREADDLM_EVSE_SUB_DISTRIBUTION_LIMIT_L3
61315:016-BitREAD & WRITEDLM_OPERATOR_EVSE_SUB_DISTRIBUTION_LIMIT_L1Operator current limit for DLM available for distribution to EVs. The 'Operator EVSE Sub-Distribution Limit' is equal or smaller than the 'EVSE Sub-Distribution Limit'.
These three registers are for L1, L2, and L3 respectively and the values are in Amps.
61415:016-BitREAD & WRITEDLM_OPERATOR_EVSE_SUB_DISTRIBUTION_LIMIT_L2
61515:016-BitREAD & WRITEDLM_OPERATOR_EVSE_SUB_DISTRIBUTION_LIMIT_L3
62015:016-BitREADDLM_EXTERNAL_METER_SUPPORTIf enabled, an external, secondary meter allows to also consider the power consumption of additional load. The power available for charging EVs will be adjusted accordingly. Please make sure, 'Meter configuration (Second)' is configured, preferrably to a 3-phase, phase aware meter.
Value of this register is 1 when enabled, 0 when disabled.
62115:016-BitREADDLM_NUM_SLAVES_CONNECTEDThe number of DLM Slaves connected to this Master device.
63015:016-BitREADDLM_OVERALL_CURRENT_APPLIED_L1Overall Current the DLM Master is currently applying (sum of current distributed among the slaves).
These three registers are for L1, L2, and L3 respectively and the values are in Amps.
63115:016-BitREADDLM_OVERALL_CURRENT_APPLIED_L2
63215:016-BitREADDLM_OVERALL_CURRENT_APPLIED_L3
63315:016-BitREADDLM_OVERALL_CURRENT_AVAILABLE_L1Overall Current the DLM Master has available to distribute among the slaves.
These three registers are for L1, L2, and L3 respectively and the values are in Amps.
63415:016-BitREADDLM_OVERALL_CURRENT_AVAILABLE_L2
63515:016-BitREADDLM_OVERALL_CURRENT_AVAILABLE_L3

11. Charge process information​

Charge process information is information collected during, or inferred from, the charging process.

info
Deprecation Note

Registers

  • 705
  • 709

are deprecated and only to be used for clients that implement until version 10 of this protocol.

When using versionUse
< version 10 of this protocol705 and 609
>= version 11 of this protocolinstead of 705 → 716-717
instead of 705 → 709

The older registers can still be read in newer versions for backwards compatibility, but it is discouraged to do so in newer implementations.

Once the values in those registers reach their maximum, they will stay at the maximum value until the next session is started or until the charging process is finished according to each case.

Register Addr.Bit fieldSizeTypeNameDescription
701-70231:032-BitREADSCHED_DEP_TIME_15118Scheduled departure time (format is hhmmss in big-endian packed BCD with left zero padding) – 15118 only
703-70431:032-BitREADSCHED_DEP_DATE_15118Scheduled departure time (format is ddmmyy in big-endian packed BCD with left zero padding) – 15118 only
70515:016-BitREADDEPRECATED
CHARGED_ENERGY		(Please see the note above this table.)
70615:016-BitREADSIGNALED_CURRENTThe maximum current that’s being signaled to the EV for charging
707-70831:032-BitREADSTART_TIMEFormat is the same as in SCHED_DEP_TIME_15118
70915:016-BitREADDEPRECATED
CHARGE_DURATION		(Please see the note above this table.)
710-71131:032-BitREADEND_TIMEFormat is the same as in SCHED_DEP_TIME_15118
71215:016-BitREADMINIMUM_CUR_LIMITMinimum current limit for charging.
713-71431:032-BitREADREQ_ENERGY_15118EV Required Energy – 15118 only
71515:016-BitREADMAX_CUR_EVThis is the maximum current with which the EV can charge.
It may come from the cable's PR value in analog vehicles, or from the maximum reported by the vehicle via 15118, whichever is lower.
716-71731:032-BitREADCHARGED_ENERGYSum of charged energy for the current session (Wh).
The amount of charged energy will stay at its maximum until the next session is started
718-71931:032-BitREADCHARGE_DURATIONDuration of the charging process in seconds
720-72131:032-BitREADREAD_IDTAG_1OCPP IdTag. This is a non-null terminated string with a max. length of 20 bytes, represented here in five 32-bit registers (or ten consecutive 16-bit regs.).
The string is padded with blank-space characters on the left, or completely filled with blank-space characters when no IdTag is present.
When a charging session is not in progress or the IdTag is not available these registers contain all ASCII-whitespaces.
722-72331:032-BitREADREAD_IDTAG_2
724-72531:032-BitREADREAD_IDTAG_3
726-72731:032-BitREADREAD_IDTAG_4
728-72931:032-BitREADREAD_IDTAG_5
73015:016-BitREADEV_RESS_SOCState of charge of the EV’s battery (Rechargeable Energy Storage System) – 15118 only.
74015:016-BitREADSMART_EV_DETECTED_15118Returns 1 if an EV currently connected is a smart vehicle, or 0 if no EV connected or it is not a smart vehicle.
741-74231:032-BitREADEVCCID_15118_1ASCII representation of the Hex. Values corresponding to the EVCCID. The EVCCID value is 6 bytes, so the ASCII Hex. representation of it has a length of exactly 12 bytes.
This is a non-null terminated string.
Values are all zero when no vehicle is connected, or when the vehicle is not a 15118-capable smart vehicle.
743-74431:032-BitREADEVCCID_15118_2
745-74631:032-BitREADEVCCID_15118_3
74731:032-BitREADREM_TIME_TO_FULL_SOCReturns the remaining time in seconds to full SoC – 15118 only.
74915:016-BitREADIS_IN_CHARGING_LOOP_15118Returns 1 if the EV/EVSE are on a charging loop, 0 otherwise.
750-75131:032-BitREADDC_POWER_DELIVERYReturns the DC power currently delivered in Watts.
75215:016-BitREADAUTH_SOURCESource of authorization. Possible values:
0 = NONE
1 = RFID
2 = INPUT_SWITCH
3 = REMOTE
4 = 15118
5 = AUTOCHARGE
6 = FREECHARGING
7 = POWER_LOSS

12. HEMS configuration options​

Register Addr.Bit fieldSizeTypeNameDescription
100015:016-bitREAD & WRITEHEMS_CURRENT_LIMITCurrent limit of the HEMS module in Amps. This register is intended to be modified by an Energy Manager. If the charge session shall be paused, the register needs to be set to "0"

13. Authorization with IDTag​

Please note that for these registers to be enabled, the corresponding option must be set in the controller HEMS/Modbus setting named Modbus Slave Allow Start/Stop Transaction.

When writing to these registers, the effect will be exactly the same as if one physically presented an RFID card in fron of the card reader. That means it will start/stop the transaction accordingly based on each scenario's workflow.

Note that the registers in this table are WRITE only. To READ the IDTAG currently in use please refer to the registers prefixed with READ_ID_TAG_ on their name.

Register Addr.Bit fieldSizeTypeNameDescription
1110-111131:032-BitWRITEWRITE_IDTAG_1Same format as registers 720-729.
If the IdTag string is fewer than 20 characters, it must be padded on the left (the lowermost registers) with blank-space ASCII characters.
1112-111331:032-BitWRITEWRITE_IDTAG_2
1114-111531:032-BitWRITEWRITE_IDTAG_3
1116-111731:032-BitWRITEWRITE_IDTAG_4
1118-111931:032-BitWRITEWRITE_IDTAG_5

14. Error states mask mappings​

In order to represent any simultaneous error states, the value read from the ERROR_CODES registers can be AND'ed with different mask mappings to identify which individual errors may be present at any given time in the system.

Since only bits 0 to 21 are used in the current specification, it is possibly to read only from registers 111-112 in order to optimize the fetching of values.

For completion however, it is clarified here how to read and interpret the values when reading all 8 registers.

To test for each error individually, the resulting value of reading all registers has to be masked against the corresponding error mask. An example is given below on how to achieve this.

Supposing the following value (presented here in HEX) is read from the ERROR_CODES registers:

Register: 105-106 107-108 109-110 111-112

Value: 0000 0000 0000 0000 0000 0000 4100 0000

Please focus first in the value of registers 111-112.

The bits of a double word are numbered from 0 through 31 with bit 0 being the least significant bit. The word containing bit 0 is the low word and the word containing bit 31 is the high word. Each 32-bit register has the low word first, and each word has the low byte first.

So in the case of registers 111-112 the words must first be inverted, to get a value of 0000 4100, and then the bytes of each word must be inverted too, in order to get a value of 0000 0041.

That is to be done for each register pair (105-106, 107-108, 109-110, 111-112), and once it is done, then the whole resulting value can be simply assembled from all registers by starting from a value of 0, and going through each word (register) in order, first shifting to the left then adding.

The result from the case above would be:

0000 0000 0000 0000 0000 0000 0000 0041

Finally, to identify which individual errors are present this value must be AND'ed to each error mask. So by doing the following operation:

0000 0000 0000 0000 0000 0000 0000 0041

AND

0000 0000 0000 0000 0000 0000 0000 0001

Ii is possible to identify that an error "ERR_RCMB_TRIGGERED" is present.

And by continuing doing for example:

0000 0000 0000 0000 0000 0000 0000 0041

AND

0000 0000 0000 0000 0000 0000 0000 0040

It can be observed that also there is an error "ERR_CONTACTOR_WELD" present.

Mask values for bits 0 to 26 (LSB 0) are specified in the following table. Bits 27 to 127 are reserved.

Bit number
(LSB 0)		Mask ValueMask NameDescription
00x01ERR_RCMB_TRIGGEREDResidual current detected via sensor.
10x02ERR_VEHICLE_STATE_EVehicle signals error.
20x04ERR_MODE3_DIODE_CHECKVehicle diode check failed - tamper detection.
30x08ERR_MCB_TYPE2_TRIGGEREDMCB of type 2 socket triggered.
40x10ERR_MCB_SCHUKO_TRIGGEREDMCB of domestic socket triggered.
50x20ERR_RCD_TRIGGEREDRCD triggered.
60x40ERR_CONTACTOR_WELDContactor welded.
70x80ERR_BACKEND_DISCONNECTEDBackend disconnected.
80x100ERR_ACTUATOR_LOCKING_FAILEDPlug locking failed.
90x200ERR_ACTUATOR_LOCKING_WITHOUT_PLUG_FAILEDLocking without plug error.
100x400ERR_ACTUATOR_STUCKActuator stuck cannot unlock.
110x800ERR_ACTUATOR_DETECTION_FAILEDActuator detection failed.
120x1000ERR_FW_UPDATE_RUNNINGFW Update in progress.
130x2000ERR_TILTThe charge point is tilted.
140x4000ERR_WRONG_CP_PR_WIRINGCP/PR wiring issue
150x8000ERR_TYPE2_OVERLOAD_THR_2Car current overload, charging stopped.
160x10000ERR_ACTUATOR_UNLOCKED_WHILE_CHARGINGActuator unlocked while charging.
170x20000ERR_TILT_PREVENT_CHARGING_UNTIL_REBOOTThe charge point was tilted and it is not allowed to charge until the charge point is rebooted.
180x40000ERR_PIC24PIC24 error.
190x80000ERR_USB_STICK_HANDLINGUSB stick handling in progress.
200x100000ERR_INCORRECT_PHASE_INSTALLATIONIncorrect phase rotation direction detected.
210x200000ERR_NO_POWERNo power on mains detected.
220x400000ERR_METER_SECOND_NOT_COMMUNICATINGMeter second not communicating.
230x800000ERR_MONITORING_RELAY_INPUT_TRIGGEREDRCD-MCB Unique input triggered.
240x1000000ERR_STATE_DCharging is paused because state D is detected.
250x2000000DC_ERR_DOOR_OPENDC wallbox door is open
260x4000000ERR_RCD_MAYBE_TRIGGEREDRCD maybe triggered, detected by communication (power) loss on primary meter

15. Error events mask mappings​

The same as described in chapter above applies here, except:

Supposing the following value (presented here in HEX) is read from the ERR_EVT_CODES registers:

Register: 158-159 160-161 162-163 164-165

Value: 0000 0000 0000 0000 0000 0000 4100 0000

Please focus first in the value of registers 164-165.

Bit number
(LSB 0)		Mask ValueMask NameDescription
00x01ERR_EVENT_ACTUATOR_LOCKunused
10x02ERR_EVENT_ACTUATOR_LOCK_WITHOUT_PLUGunused
20x04ERR_EVENT_REBOOT_IN_PROGRESSCharge point reboot was issued
30x08ERR_EVENT_AUTHORIZATION_FAILEDAuthorization failed
40x10ERR_EVENT_AUTHORIZATION_FAILED_NO_STATUSNOTIFAuthorization failed (w/o notification of OCPP backend)
50x20ERR_EVENT_FW_UPDATE_PAUSED_ACTIVE_TRANSACTIONunused
60x40ERR_EVENT_FW_UPDATE_FAILUREFirmware update failed (internet connection?).
70x80ERR_EVENT_FW_UPDATE_ROLLED_BACK_AFTER_FAILUREunused
80x100ERR_EVENT_FW_UPDATE_PACKAGE_MANAGER_FAULTFirmware update failed because the package manager refused the update.
90x200ERR_EVENT_MONITORING_UNINTENDED_RESETUnintended Reset - Power Outage?
100x400ERR_EVENT_TRANSACTION_STOPPED_AFTER_RESETChargePoint rebooted while a transaction (charging) was active. Transaction was implicitely terminated.
110x800ERR_EVENT_SLAVE_DISCONNECTEDA slave disconnected from the master.
120x1000ERR_EVENT_DIAGNOSTICS_FAILUREDiagnostics failed (internet connection?).
130x2000ERR_EVENT_RCMB_ERRORRCMB error
140x4000ERR_EVENT_TEMPERATURE_ALERTunused
150x8000ERR_EVENT_15118_COMMUNICATION_FAILURETCP/TLS 15118 communication failed
160x10000ERR_EVENT_15118_AUTHORIZATION_FAILURE15118 authorization for PnC failed. The signature validation failed
170x20000ERR_EVENT_15118_AUTHENTICATION_FAILURE15118 authentication for PnC failed
180x40000ERR_EVENT_15118_CERT_INSTALLATION_FAILURE15118 Certificate Installation failed
190x80000ERR_EVENT_15118_DEPARTURE_TIME15118 departure time received
200x100000ERR_EVENT_15118_EAMOUNT15118 Energy Amount received
210x200000ERR_EVENT_15118_V2G_SEQUENCE_TIMEOUT15118 V2G Sequence timeout
220x400000ERR_EVENT_15118_V2G_SEQUENCE_ERROR15118 V2G Sequence error
230x800000ERR_EVENT_15118_DC_CABLE_CHECKCable Check error - Not in state C/D
240x1000000ERR_EVENT_15118_DC_POWER_STOPPower stop error - Not in state B
250x2000000ERR_EVENT_15118_DC_ISOLATION_FAULTCable isolation fault
260x4000000ERR_EVENT_15118_DC_UNEXPECTED_CP_STATEUnexpected CP state
270x8000000ERR_EVENT_15118_DC_EVSE_INITIATED_SHUTDOWNEVSE normal shutdown
280x10000000ERR_EVENT_GENERIC_INFORMGeneric event
290x20000000ERR_EVENT_IDTAG_ADDED_OKAdding tag to Auth List or FLL succeeded
300x40000000ERR_EVENT_IDTAG_ADDED_FAILUREAdding tag to Auth List or FLL failed
310x80000000ERR_EVENT_SYSTEM_NOT_READYSystem not yet ready

16. Appendix​

16.1. Exhaustive list of Modbus registers​

Here's an exhaustive list of Modbus registers for convinience:

info

All data is transferred in network byte order/big endian.

Device/ProtocolReg. TypeAddressNameR/WNr. Regs.Description
PhoenixInput100EV StatusR1Returns the Control Pilot state
PhoenixInput101Proximity CurrentR1Returns signaled current in Amps
PhoenixInput102Charging Time (seconds)R2Duration since beginning of charge
PhoenixInput104LegacyR1Do not use.
PhoenixInput105Firmware VersionR2Returns the Ebee Application version number. Example: 0.91 = (0x30, 0x2E, 0x39, 0x31) 4.40 = (0x34, 0x2E, 0x34, 0x34).
PhoenixInput107LegacyR1Do not use.
PhoenixInput108Voltage L1R2Returns the voltage of phase 1 of the ocpp meter in V.
PhoenixInput110Voltage L2R2Returns the voltage of phase 2 of the ocpp meter in V.
PhoenixInput112Voltage L3R2Returns the voltage of phase 3 of the ocpp meter in V.
PhoenixInput114Current L1R2Returns the current of phase 1 of the ocpp meter in mA.
PhoenixInput116Current L2R2Returns the current of phase 2 of the ocpp meter in mA.
PhoenixInput118Current L3R2Returns the current of phase 3 of the ocpp meter in mA.
PhoenixInput120Total Power (OCPP Meter Power)R2Returns the power read from the ocpp meter in W.
PhoenixInput122Reactive PowerR2
PhoenixInput124Real PowerR2
PhoenixInput126Power FactorR2
PhoenixInput128EnergyR2Energy read from meter in Wh
PhoenixInput130Max. power ever seen from OCPP MeterR2Max. power value ever seen since boot
PhoenixInput132Charged Energy (Wh)R2Sum of charged energy for the current session
PhoenixInput134Grid FrequencyR2Returns the frequency read from the ocpp meter in Hz.
PhoenixInput136Assumed Maximum Charging Current L1R2
PhoenixInput138Assumed Maximum Charging Current L2R2
PhoenixInput140Assumed Maximum Charging Current L3R2
PhoenixInput200Input valuesR1
PhoenixInput201-R1-
PhoenixInput202Plug lock detectR1Status of plug lock detection
PhoenixInput203-R1-
PhoenixInput204-R1-
PhoenixInput205-R1-
PhoenixInput206-R1-
PhoenixInput207-R1-
PhoenixInput208-R1-
PhoenixHolding310IP Address - 1st OctetR1Get the IP address of the active interface connected to the backend.
PhoenixHolding311IP Address - 2nd OctetR1Get the IP address of the active interface connected to the backend.
PhoenixHolding312IP Address - 3rd OctetR1Get the IP address of the active interface connected to the backend.
PhoenixHolding313IP Address - 4th OctetR1Get the IP address of the active interface connected to the backend.
TQ-DM100Holding1000Charge Point StateR1
TQ-DM100Holding1001Charge StateR1
TQ-DM100Holding1002EVSE StateR1
TQ-DM100Holding1004Cable StateR1
TQ-DM100Holding1006EVSE Error CodeR1
TQ-DM100Holding1008Current L1R1Returns the current of phase 1 of the ocpp meter in mA.
TQ-DM100Holding1010Current L2R1Returns the current of phase 2 of the ocpp meter in mA.
TQ-DM100Holding1012Current L3R1Returns the current of phase 3 of the ocpp meter in mA.
TQ-DM100Holding1020Active PowerR2
TQ-DM100Holding1024Active Power L1R2
TQ-DM100Holding1028Active Power L2R2
TQ-DM100Holding1032Active Power L3R2
TQ-DM100Holding1036EnergyR2
TQ-DM100Holding1100Hardware current limitR1
TQ-DM100Holding1102Minimum current limitR1
TQ-DM100Holding1104Max. Current from EVSER1
TQ-DM100Holding1106Max. Current from CableR1
TQ-DM100Holding1108Max. Current from EVR1
TQ-DM100Holding1200User priorityR1
TQ-DM100Holding1300EV Battery State (% 0-100)R1Returns an estimate of the SoC
TQ-DM100Holding1302EV Battery Capacity (Wh)R2Returns an estimate of the EV Battery Capacity
TQ-DM100Holding1400Schedule TypeR1
TQ-DM100Holding1402Required Energy (Wh)R2
TQ-DM100Holding1406Required Battery State (% 0-100)R1
TQ-DM100Holding1408Scheduled Time (hhmmss)R2
TQ-DM100Holding1412Scheduled Date (yymmdd)R2
TQ-DM100Holding1502Charged Energy (Wh)R1Sum of charged energy for the current session
TQ-DM100Holding1504Start Time (hhmmss)R2Start time of charging process
TQ-DM100Holding1508Charging Time (seconds)R2Duration since beginning of charge
TQ-DM100Holding1512End Time (hhmmss)R2End time of charging process
TQ-DM100Holding1600User IDR2User ID (OCPP IdTag) from the current session. Bytes 0 to 3.
TQ-DM100Holding1602User IDR2User ID (OCPP IdTag) from the current session. Bytes 4 to 7.
TQ-DM100Holding1604User IDR2User ID (OCPP IdTag) from the current session. Bytes 8 to 11.
TQ-DM100Holding1606User IDR2User ID (OCPP IdTag) from the current session. Bytes 12 to 15.
TQ-DM100Holding1608User IDR2User ID (OCPP IdTag) from the current session. Bytes 16 to 19.
TQ-DM100Holding162015118 Smart vehicle detectedR1Returns 1 if an EV currently connected is a smart vehicle, or 0 if no EV connected or it is not a smart vehicle
TQ-DM100Holding2000Safe Current (Amps.)R/W1Max. charge current under communication failure
TQ-DM100Holding2002Comm. Timeout (seconds)R/W1Communication timeout
TQ-DM100Holding5000Charge Power (W)W2
TQ-DM100Holding5004Charge Current (A)W1
TQ-DM100Holding5006Charge Control1Unimplemented
TQ-DM100Holding5008Charge Release1Unimplemented
TQ-DM100Holding5900Free ChargingR/W1Unimplemented
TQ-DM100Holding5902Free Charging ModeR/W1Unimplemented
TQ-DM100Holding6000Life BitR/W10/1 Toggle-Bit
Open Modbus Charge Control Interface (OMCCI)Holding100Firmware VersionR2Returns the Ebee Application version number. Example: 0.91 = (0x30, 0x2E, 0x39, 0x31) 4.40 = (0x34, 0x2E, 0x34, 0x34).
Open Modbus Charge Control Interface (OMCCI)Holding104OCPP CP StatusR1Charge Point status according to the OCPP spec. enumeration
Open Modbus Charge Control Interface (OMCCI)Holding105Error Codes 1R2Aggregated error states (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding107Error Codes 2R2Aggregated error states (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding109Error Codes 3R2Aggregated error states (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding111Error Codes 4R2Aggregated error states (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding120Protocol VersionR2Ebee Modbus TCP Server Protocol Version number (example: 0.6 = {0x30, 0x2E, 0x36}).
Open Modbus Charge Control Interface (OMCCI)Holding122Vehicle (Control Pilot) stateR1A=1, B=2, C=3, D=4, E=5
Open Modbus Charge Control Interface (OMCCI)Holding123Vehicle (Control Pilot) state in Hex. formatR1A = 0x0A, B = 0x0B, etc.
Open Modbus Charge Control Interface (OMCCI)Holding124Charge Point availabilityR/W1Get/Set available/unavailable
Open Modbus Charge Control Interface (OMCCI)Holding131Safe Current (Amps.)R/W1Max. charge current under communication failure
Open Modbus Charge Control Interface (OMCCI)Holding132Comm. Timeout (seconds)R/W1Communication timeout
Open Modbus Charge Control Interface (OMCCI)Holding133Hardware current limitR1
Open Modbus Charge Control Interface (OMCCI)Holding134Operator current limitR1
Open Modbus Charge Control Interface (OMCCI)Holding135RCMB ModeR1
Open Modbus Charge Control Interface (OMCCI)Holding136RCMB Last RMS value (integral part)R1
Open Modbus Charge Control Interface (OMCCI)Holding137RCMB Last RMS value (fractional part)R1
Open Modbus Charge Control Interface (OMCCI)Holding138RCMB Last DC value (integral part)R1
Open Modbus Charge Control Interface (OMCCI)Holding139RCMB Last DC value (fractional part)R1
Open Modbus Charge Control Interface (OMCCI)Holding140Relays StateR1
Open Modbus Charge Control Interface (OMCCI)Holding141Device IDR1This register is a device identifier and always returns the value 0xEBEE (decimal 60398)
Open Modbus Charge Control Interface (OMCCI)Holding142ChargePoint ModelR2ChargePoint Model. Bytes 0 to 3.
Open Modbus Charge Control Interface (OMCCI)Holding144ChargePoint ModelR2ChargePoint Model. Bytes 4 to 7.
Open Modbus Charge Control Interface (OMCCI)Holding146ChargePoint ModelR2ChargePoint Model. Bytes 8 to 11.
Open Modbus Charge Control Interface (OMCCI)Holding148ChargePoint ModelR2ChargePoint Model. Bytes 12 to 15.
Open Modbus Charge Control Interface (OMCCI)Holding150ChargePoint ModelR2ChargePoint Model. Bytes 16 to 19.
Open Modbus Charge Control Interface (OMCCI)Holding152Plug lock detectR1Status of plug lock detection
Open Modbus Charge Control Interface (OMCCI)Holding153Firmware VersionR1Returns the Ebee Application major version number
Open Modbus Charge Control Interface (OMCCI)Holding154Firmware VersionR1Returns the Ebee Application minor version number
Open Modbus Charge Control Interface (OMCCI)Holding155Firmware VersionR1Returns the Ebee Application patch version number
Open Modbus Charge Control Interface (OMCCI)Holding156Build NumberR2Returns the Ebee Application build number
Open Modbus Charge Control Interface (OMCCI)Holding158Error Events 1R2Aggregated error events (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding160Error Events 2R2Aggregated error events (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding162Error Events 3R2Aggregated error events (see Spec. sheet for mask mappings)
Open Modbus Charge Control Interface (OMCCI)Holding164Error Events 4R2Aggregated error events (see Spec. sheet for mask mappings) no error code --- 0x1 no error code --- 0x2 no error code --- 0x4 no error code --- 0x8 no error code --- 0x10 01-02-017 --- 0x20 01-02-018 --- 0x40 no error code --- 0x80 01-03-005 --- 0x100 01-04-001 --- 0x200 01-04-010 --- 0x400 01-04-009 --- 0x800 01-04-006 --- 0x1000 01-04-008 --- 0x2000 01-04-011 --- 0x4000 01-04-012 --- 0x8000 01-04-013 --- 0x10000 01-04-002 --- 0x20000 01-04-003 --- 0x40000 01-06-002 --- 0x80000 01-03-007 --- 0x100000
Open Modbus Charge Control Interface (OMCCI)Holding166Free ChargingR/W10 = Free charging disabled, 1 = Free charging enabled
Open Modbus Charge Control Interface (OMCCI)Holding167Free Charging ModeR/W1Modes 0 to 5 (see Spec. sheet for details)
Open Modbus Charge Control Interface (OMCCI)Holding168Manufacturer serial numberR2Manufacturer serial number. Bytes 0 to 3.
Open Modbus Charge Control Interface (OMCCI)Holding170Manufacturer serial numberR2Manufacturer serial number. Bytes 4 to 7.
Open Modbus Charge Control Interface (OMCCI)Holding172Manufacturer serial numberR2Manufacturer serial number. Bytes 8 to 11.
Open Modbus Charge Control Interface (OMCCI)Holding174Manufacturer serial numberR2Manufacturer serial number. Bytes 12 to 15.
Open Modbus Charge Control Interface (OMCCI)Holding176Manufacturer serial numberR2Manufacturer serial number. Bytes 16 to 19.
Open Modbus Charge Control Interface (OMCCI)Holding178Manufacturer serial numberR2Manufacturer serial number. Bytes 20 to 23.
Open Modbus Charge Control Interface (OMCCI)Holding180Manufacturer serial numberR1Manufacturer serial number. Byte 24 and '
Open Modbus Charge Control Interface (OMCCI)Holding182Phytec-Board temperatureR/W2Phytec-Board temperature from comtraxx system
Open Modbus Charge Control Interface (OMCCI)Holding184Reservation expiry timeR2Reservation expiry time
Open Modbus Charge Control Interface (OMCCI)Holding200Energy L1R2Energy in Wh. (phase 1) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding202Energy L2R2Energy in Wh. (phase 2) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding204Energy L3R2Energy in Wh. (phase 3) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding206Power L1R2Power in W (phase 1) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding208Power L2R2Power in W (phase 2) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding210Power L3R2Power in W (phase 3) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding212Current L1R2Current in mA (phase 1) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding214Current L2R2Current in mA (phase 2) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding216Current L3R2Current in mA (phase 3) from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding218Total EnergyR2Total Energy in Wh. from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding220Total PowerR2Total Power in Wh. from primary meter
Open Modbus Charge Control Interface (OMCCI)Holding222Voltage L1R2Returns the voltage of phase 1 of the ocpp meter in V.
Open Modbus Charge Control Interface (OMCCI)Holding224Voltage L2R2Returns the voltage of phase 2 of the ocpp meter in V.
Open Modbus Charge Control Interface (OMCCI)Holding226Voltage L3R2Returns the voltage of phase 3 of the ocpp meter in V.
Open Modbus Charge Control Interface (OMCCI)Holding500(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding501(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding502(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding503(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding504(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding505(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding506(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding507(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding508(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding509(Reserved)R1
Open Modbus Charge Control Interface (OMCCI)Holding600DLM ModeR1Indicates the DLM mode configured for this device.
Open Modbus Charge Control Interface (OMCCI)Holding610DLM EVSE Sub-distribution Limit L1R1Overall current limit for DLM available for EVs
Open Modbus Charge Control Interface (OMCCI)Holding611DLM EVSE Sub-distribution Limit L2R1Overall current limit for DLM available for EVs
Open Modbus Charge Control Interface (OMCCI)Holding612DLM EVSE Sub-distribution Limit L3R1Overall current limit for DLM available for EVs
Open Modbus Charge Control Interface (OMCCI)Holding613DLM Operator EVSE Sub-distribution Limit L1R/W1Operator current limit for DLM available for distribution to EVs
Open Modbus Charge Control Interface (OMCCI)Holding614DLM Operator EVSE Sub-distribution Limit L2R/W1Operator current limit for DLM available for distribution to EVs
Open Modbus Charge Control Interface (OMCCI)Holding615DLM Operator EVSE Sub-distribution Limit L3R/W1Operator current limit for DLM available for distribution to EVs
Open Modbus Charge Control Interface (OMCCI)Holding620DLM External Meter supportR1Value of this register is 1 when External Meter is enabled, 0 when disabled
Open Modbus Charge Control Interface (OMCCI)Holding621DLM Number of Slaves connectedR1The number of DLM Slaves connected to this Master device
Open Modbus Charge Control Interface (OMCCI)Holding630DLM Overall Current applied L1R1Overall Current (A) the DLM Master is currently applying (sum of current distributed among the slaves)
Open Modbus Charge Control Interface (OMCCI)Holding631DLM Overall Current applied L2R1Overall Current (A) the DLM Master is currently applying (sum of current distributed among the slaves)
Open Modbus Charge Control Interface (OMCCI)Holding632DLM Overall Current applied L3R1Overall Current (A) the DLM Master is currently applying (sum of current distributed among the slaves)
Open Modbus Charge Control Interface (OMCCI)Holding633DLM Overall Current available L1R1Overall Current (A) the DLM Master has available to distribute among the slaves
Open Modbus Charge Control Interface (OMCCI)Holding634DLM Overall Current available L2R1Overall Current (A) the DLM Master has available to distribute among the slaves
Open Modbus Charge Control Interface (OMCCI)Holding635DLM Overall Current available L3R1Overall Current (A) the DLM Master has available to distribute among the slaves
Open Modbus Charge Control Interface (OMCCI)Holding701Scheduled Time (hhmmss)R2Scheduled departure time (format is `hhmmss` in big-endian packed BCD with left zero padding) – 15118 only
Open Modbus Charge Control Interface (OMCCI)Holding703Scheduled Date (yymmdd)R2Scheduled departure time (format is `ddmmyy` in big-endian packed BCD with left zero padding) – 15118 only
Open Modbus Charge Control Interface (OMCCI)Holding705(deprecated) Charged EnergyR1Sum of charged energy for the current session (Wh)
Open Modbus Charge Control Interface (OMCCI)Holding706Signaled CurrentR1The maximum current that's being signaled to the EV for charging
Open Modbus Charge Control Interface (OMCCI)Holding707Start Time (hhmmss)R2Start time of charging process
Open Modbus Charge Control Interface (OMCCI)Holding709(deprecated) Charging Duration (seconds)R1Duration since beginning of charge
Open Modbus Charge Control Interface (OMCCI)Holding710End Time (hhmmss)R2End time of charging process
Open Modbus Charge Control Interface (OMCCI)Holding712Minimum current limitR1Minimum current limit for charging
Open Modbus Charge Control Interface (OMCCI)Holding713EV Required Energy (Wh)R2Returns the amount of energy in Wh required by the EV
Open Modbus Charge Control Interface (OMCCI)Holding715Max. Current EVR1This is the maximum current with which the EV can charge
Open Modbus Charge Control Interface (OMCCI)Holding716Charged EnergyR2Sum of charged energy for the current session (Wh)
Open Modbus Charge Control Interface (OMCCI)Holding718Charging Duration (seconds)R2Duration since beginning of charge
Open Modbus Charge Control Interface (OMCCI)Holding720User IDR2User ID (OCPP IdTag) from the current session. Bytes 0 to 3.
Open Modbus Charge Control Interface (OMCCI)Holding722User IDR2User ID (OCPP IdTag) from the current session. Bytes 4 to 7.
Open Modbus Charge Control Interface (OMCCI)Holding724User IDR2User ID (OCPP IdTag) from the current session. Bytes 8 to 11.
Open Modbus Charge Control Interface (OMCCI)Holding726User IDR2User ID (OCPP IdTag) from the current session. Bytes 12 to 15.
Open Modbus Charge Control Interface (OMCCI)Holding728User IDR2User ID (OCPP IdTag) from the current session. Bytes 16 to 19.
Open Modbus Charge Control Interface (OMCCI)Holding730EV Battery State (% 0-100)R1Returns an estimate of the SoC
Open Modbus Charge Control Interface (OMCCI)Holding74015118 Smart vehicle detectedR1Returns 1 if an EV currently connected is a smart vehicle, or 0 if no EV connected or it is not a smart vehicle
Open Modbus Charge Control Interface (OMCCI)Holding741EVCCID - 15118 onlyR2ASCII representation of the Hex. Values corresponding to the EVCCID. Bytes 0 to 3.
Open Modbus Charge Control Interface (OMCCI)Holding743EVCCID - 15118 onlyR2ASCII representation of the Hex. Values corresponding to the EVCCID. Bytes 4 to 7.
Open Modbus Charge Control Interface (OMCCI)Holding745EVCCID - 15118 onlyR2ASCII representation of the Hex. Values corresponding to the EVCCID. Bytes 8 to 11.
Open Modbus Charge Control Interface (OMCCI)Holding747Remaining time to full SoC - 15118 onlyR2Returns the remaining time in seconds to full SoC
Open Modbus Charge Control Interface (OMCCI)Holding749Is in charging loop - 15118 onlyR1Returns 1 if the EV/EVSE are on a charging loop, 0 otherwise
Open Modbus Charge Control Interface (OMCCI)Holding752Auth. sourceR1Source of authorization (RFID, Input, Remote, 15118, Autocharge, Freecharge, Power Loss... )
Open Modbus Charge Control Interface (OMCCI)Holding1000Hems Current Limit (A)R/W1Current limit of the HEMS module in Amps
Open Modbus Charge Control Interface (OMCCI)Holding1110User IDW2Write user ID (OCPP IdTag) for the current session. Bytes 0 to 3.
Open Modbus Charge Control Interface (OMCCI)Holding1112User IDW2Write user ID (OCPP IdTag) for the current session. Bytes 4 to 7.
Open Modbus Charge Control Interface (OMCCI)Holding1114User IDW2Write user ID (OCPP IdTag) for the current session. Bytes 8 to 11.
Open Modbus Charge Control Interface (OMCCI)Holding1116User IDW2Write user ID (OCPP IdTag) for the current session. Bytes 12 to 15.
Open Modbus Charge Control Interface (OMCCI)Holding1118User IDW2Write user ID (OCPP IdTag) for the current session. Bytes 16 to 19.