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¶
Vendor / Product |
Interface |
Protocol |
Implementer |
EVerest Module Name |
EVerest Module Supports German Eichrecht |
Tested by chargebyte |
|---|---|---|---|---|---|---|
Eastron SDM230 |
EIA-485 |
Modbus |
✗ |
✗ |
||
Eastron SDM72D-M |
EIA-485 |
Modbus |
✗ |
✓ |
||
Eastron SDM72D-M v2 |
EIA-485 |
Modbus |
✗ |
✓ |
||
Eastron SDM630 v2 |
EIA-485 |
Modbus |
✗ |
✓ |
||
Klefr 693x/694x |
EIA-485 |
Modbus |
✗ |
✓ |
||
Iskra WM3M4/WM3M4C |
EIA-485 |
Modbus |
chargebyte |
PowermeterIskra_WM3M4C |
✗ |
✓ |
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/_generated/modules/SerialCommHub.html.
Note
Most electricity meters which use Modbus as protocol are covered by EVerest’s GenericPowermeter module. See https://github.com/EVerest/everest-core/tree/main/modules/GenericPowermeter/models for latest supported models.
DC¶
Vendor / Product |
Interface |
Protocol |
Implementer |
EVerest Module Name |
EVerest Module Supports German Eichrecht |
Tested by chargebyte |
|---|---|---|---|---|---|---|
Ethernet |
HTTP |
✓ |
✗ |
|||
Ethernet |
HTTP |
✓ |
✗ |
DC Power Modules¶
Vendor / Product |
Interface |
Protocol |
Implementer |
EVerest Module Name |
Tested by chargebyte |
|---|---|---|---|---|---|
CAN |
Proprietary |
✗ |
|||
CAN |
Proprietary |
✓ |
Insulation Monitoring Devices (IMDs)¶
Vendor / Product |
Interface |
Protocol |
Implementer |
EVerest Module Name |
Tested by chargebyte |
|---|---|---|---|---|---|
EIA-485 |
Modbus |
chargebyte (planned) |
TBD |
Residual Current Monitors (RCMs)¶
Vendor / Product |
Interface |
Protocol |
Implementer |
EVerest Module Name |
Tested by chargebyte |
|---|---|---|---|---|---|
Digital In/Out |
none |
chargebyte (in progress) |
✓ |
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 |
✗ |
||
RFID Readers based on NXP’s PN7160 Chip |
I²C/SPI |
Proprietary |
✗ |
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).