API for EVerest API clients implementing isolation monitoring.
default local MQTT
The ID of the module as defined in the EVerest config file.
Direction: EVerest to Module
By receiving the start command the monitoring of the isolation status should be started. Measurement data should be sent in user dependent interval until the stop command is received.
Available only on servers:
Accepts the following message:
Start recurring isolation measurements. The device should monitor the isolation status until stopped and publish the resistance data in regular intervals. The actual interval is device dependent.
Direction: EVerest to Module
By receiving the stop command the monitoring of the isolation status should be stoped. Measurement data must not be sent until the next start command is received.
Available only on servers:
Accepts the following message:
Stop recurring measurements. The device should stop to monitor the isolation resistance and stop publishing the data.
Direction: EVerest to Module
The EvseManager will enable a DC voltage to support the testing, but will not enable output relais such that there is no high voltage on the external plug. The "self_test_result" variable must be published once the self testing is done.
Available only on servers:
Accepts the following message:
Start self test. EvseManager will enable a DC voltage to support the testing, but will not enable output relais such that there is no high voltage on the external plug.
Voltage for the isolation monitor self test
Direction: Module to EVerest
This operation is used to send a dataset of measured values. The isolation resistance (in Ohm) is required. The voltage is optional.
Available only on servers:
Accepts the following message:
Isolation monitoring measurement results
Results of an isolation measurement
{
"resistance_F_Ohm": 0,
"voltage_V": 0
}
Direction: Module to EVerest
This operation is used to send the result of the self test.
Available only on servers:
Accepts the following message:
Self test result
Indicates the self test is done and publishes the result. Set "true" for success, "false" for failure.
Direction: Module to EVerest
Available only on servers:
Accepts the following message:
Signal to EVerest that an error happened.
Errors for Isolation Monitor Note that actual isolation faults should just be reported as resistance values, EvseManager will interpret them according to the limits given in the norm and stop charging. This is only to report device errors to indicate valid isolation resistance measurements etc are no longer possible.
{
"type": "CommunicationFault",
"sub_type": "string",
"message": "string"
}
Accepts the following message:
Signal to EVerest that a previously raised error is no longer active.
Errors for Isolation Monitor Note that actual isolation faults should just be reported as resistance values, EvseManager will interpret them according to the limits given in the norm and stop charging. This is only to report device errors to indicate valid isolation resistance measurements etc are no longer possible.
{
"type": "CommunicationFault",
"sub_type": "string",
"message": "string"
}
Accepts the following message:
Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration
64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached
Heartbeat
Accepts the following message:
Signal to EVerest that communication is good or check shall be stopped
Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'
Start recurring isolation measurements. The device should monitor the isolation status until stopped and publish the resistance data in regular intervals. The actual interval is device dependent.
Stop recurring measurements. The device should stop to monitor the isolation resistance and stop publishing the data.
Start self test. EvseManager will enable a DC voltage to support the testing, but will not enable output relais such that there is no high voltage on the external plug.
Voltage for the isolation monitor self test
Isolation monitoring measurement results
Results of an isolation measurement
Self test result
Indicates the self test is done and publishes the result. Set "true" for success, "false" for failure.
Signal to EVerest that an error happened.
Errors for Isolation Monitor Note that actual isolation faults should just be reported as resistance values, EvseManager will interpret them according to the limits given in the norm and stop charging. This is only to report device errors to indicate valid isolation resistance measurements etc are no longer possible.
Signal to EVerest that a previously raised error is no longer active.
Errors for Isolation Monitor Note that actual isolation faults should just be reported as resistance values, EvseManager will interpret them according to the limits given in the norm and stop charging. This is only to report device errors to indicate valid isolation resistance measurements etc are no longer possible.
Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration
64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached
Signal to EVerest that communication is good or check shall be stopped
Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'
Results of an isolation measurement
Indicates the self test is done and publishes the result. Set "true" for success, "false" for failure.
Voltage for the isolation monitor self test
Type of error
Errors for Isolation Monitor Note that actual isolation faults should just be reported as resistance values, EvseManager will interpret them according to the limits given in the norm and stop charging. This is only to report device errors to indicate valid isolation resistance measurements etc are no longer possible.
Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'
64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached