Peripheral Compatibility List

Each charging station consists not only of the actual charging controller, but also of several connected peripheral devices. Depending on the type of charging station, i.e., AC or DC, different peripheral devices are required.

The following lists the manufacturers and models supported for different device classes.

While the open-source EVerest charging stack supports several devices out-of-the-box, others are implemented and maintained by chargebyte as either open-source or closed-source EVerest modules.

Note

If you need some specific component implemented, feel free to contact us.

Electricity Meters

Note

Not all electricity meters support/provide all possible measurement values. Sometimes, this also depends on the meter’s hardware and/or firmware version. Therefore, please check whether your desired meter is compatible with your specific requirements.

AC

Table 2: Supported AC Electricity Meters

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	German Eichrecht Supported [1]	MID Compliant [2]	Tested by chargebyte
Eastron SDM230	EIA-485	Modbus	EVerest	GenericPowermeter	✗	✓	✗
Eastron SDM72D-M	EIA-485	Modbus	EVerest	GenericPowermeter	✗	✓	✓
Eastron SDM72D-M v2	EIA-485	Modbus	EVerest	GenericPowermeter	✗	✓	✓
Eastron SDM630 v2	EIA-485	Modbus	EVerest	GenericPowermeter	✗	✓	✓
Carlo Gavazzi EM580	EIA-485	Modbus	EVerest	CarloGavazzi_EM580	✓	✓	✗
Klefr 693x/694x	EIA-485	Modbus	EVerest	GenericPowermeter	✗	✓	✓
Iskra WM3M4/WM3M4C	EIA-485	Modbus	chargebyte	PowermeterIskra_WM3M4C	✗	✓	✓

[1]

Support in the listed EVerest module implementation.

[2]

Compliance of the device itself.

Note

Multiple EIA-485 devices, which all use Modbus as protocol, can share the same EIA-485 bus. It is required to use the EVerest module SerialCommHub as low-level module to coordinate the individual peripheral modules - even when there is only a single device on the bus. The configuration of the SerialCommHub module can be found on EVerest’s documentation platform: https://everest.github.io/nightly/reference/modules/Misc/SerialCommHub/autogenerated.html.

Note

Most electricity meters which use Modbus as protocol are covered by EVerest’s GenericPowermeter module. See https://github.com/EVerest/EVerest/tree/main/modules/HardwareDrivers/PowerMeters/GenericPowermeter/models for latest supported models.

DC

Table 3: Supported DC Electricity Meters

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	German Eichrecht Supported [3]	MID Compliant [4]	Tested by chargebyte
AST DC650	EIA-485	SLIP	EVerest	AST_DC650	✓	✓	✗
Acrel DJSF1352-RN	EIA-485	Modbus	EVerest	Acrel_DJSF1352_RN	✗	✗	✗
DZG GSH01	EIA-485	SLIP	EVerest	DZG_GSH01	✓	✓	✗
LEM DCBM 400/600	Ethernet	HTTP	EVerest	LemDCBM400600	✓	✓	✗
Isabellenhütte IEM-DCR series	Ethernet	HTTP	EVerest	IsabellenhuetteIemDcr	✓	✓	✗

[3]

Support in the listed EVerest module implementation.

[4]

Compliance of the device itself.

Warning

When using SLIP over EIA-485, the interface can only be used for a point-to-point connection between two devices. In contrast to Modbus, multiple devices cannot be addressed on the same bus.

DC Power Modules

Table 4: Supported DC Power Modules

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	BPT Supported [5]	Tested by chargebyte
SCU DPM series	CAN	Proprietary	EVerest	DPM1000	✗	✗
UUGreen Power RX1000X0	CAN	Proprietary	EVerest	UUGreenPower_UR1000X0	✗	✗
InfyPower	CAN	Proprietary	EVerest	InfyPower	✗	✓
InfyPower BEG1K075G	CAN	Proprietary	EVerest	InfyPower_BEG1K075G	✓	✓
Winline	CAN	Proprietary	EVerest	Winline	✗	✗
Infypower BEG series	CAN	Proprietary	chargebyte	InfypowerDCSupply	✓	✓
Huawei FusionCharge R100040Gx	CAN	Proprietary	EVerest	Huawei_R100040Gx	✗	✗
Huawei FusionCharge V100R023C10	Ethernet	Modbus	EVerest	Huawei_V100R023C10	✗	✗

[5]

Support in the listed EVerest module implementation.

Insulation Monitoring Devices (IMDs)

Table 5: Supported Insulation Monitoring Devices

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	Tested by chargebyte
Bender ISOMETER® isoCHA425HV with AGH420-1/AGH421-1	EIA-485	Modbus	EVerest	Bender_isoCHA425HV	✗
Dold RN 5893	EIA-485	Modbus	EVerest	DoldRN5893	✗

Residual Current Monitors (RCMs)

Table 6: Supported Residual Current Monitors

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	Tested by chargebyte
Western Automation RCM14	Digital In/Out	none	chargebyte (in progress)	CbTarragonDriver	✓

RFID Readers

Table 7: Supported RFID Readers

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	Tested by chargebyte
Stronglink SL032 (RS-485 variant with customer specific Modbus firmware)	EIA-485	Modbus	chargebyte	SL032ModbusTokenProvider	✓
InTallyCom RFBT001	EIA-485	Modbus	chargebyte	SL032ModbusTokenProvider	✓
RFID Readers based on NXP’s PN532 Chip	UART	Proprietary	EVerest	PN532TokenProvider	✗

Note

All EVerest modules which depend on libnfc, such as the PN7160TokenProvider, are not officially supported. This library depends on the deprecated GPIO sysfs interface.

HMI Devices

Table 8: Supported HMI Devices

Vendor / Product	Interface	Protocol	Implementer	EVerest Module Name	Tested by chargebyte
Generic GPIO/Digital Output connected RGB LEDs (without PWM support) for various general charger states	Digital Out	none	chargebyte	GpioLedControl + HmiLed	✓
Generic GPIO/Digital Output connected Single Color LED (without PWM support) for signaling RFID token verification result	Digital Out	none	chargebyte	RfidLedFeedback	✓

Locking Motors (Plug Locks)

Since the electrical interface for plug lock motors is platform-specific, please find the supported motor types and corresponding configuration parameters in the platform specific module’s description (e.g. CbTarragonPlugLock).