AGICITY™ DUO & PRO Manuel de configuration
XI.
Annexe 4 : Listing Clefs de configuration
1.
ChargePointId
•
The charge box identity used in the communication with the OCCP backend.
o
MeterSerialNumber
•
if the evcc is unable to read the meterserial then lccl will use this
o
MeterType
•
if the evcc is unable to read the metertype then lccl will use this
o
imsi
•
If the imsi can not be read from the modem then this is setting is used.
o
iccId
•
If the iccId can not be read from the modem then this is setting is used.
o
ChargepointModel
•
refer to
o
constructed
ChargeBoxSerialNumber
•
ChargepointSerialNumber
•
ChargepointVendor
•
WebSocketPingInterval=-1
•
Interval in seconds for pinging the backend using the ocpp-j transport protocols.
o
MeterValuesSampledData=Energy.Active.Import.Register
•
Which measurands of to send in a metervalue request. Comma seperated list of
o
measurands.
LightIntensity=-1
•
A value between 0 and 100 is the percentage of the led intensity, -1 means do not
o
adjust.
HeartBeatInterval
•
the number of seconds between heartbeats.
o
no heartbeats are send when the cp is charging, only metervalues
o
MeterValueSampleInterval
•
the number of seconds between metervalue requests to the server, if not set then
o
HeartBeatInterval is used.
ocpp=SOCPP15
•
choice: SOCPP15, JOCPP15, SOCPP12, JOCPP12 or JOCPP
o
▪
▪
▪
▪
▪
▪
OCPP Chargepoint settings
chargepointModel.html
SOCPP15: OCPP 1.5 using soap
JOCPP15: OCPP 1.5 using websocket/json
SOCPP12: OCPP 1.2 using soap
JOCPP12: OCPP 1.2 using websocket/json
JOCPP: OCPP using websocket/json, the version of the ocpp specification is
automaticly negociated with the backend. The 1.5 has precedence over the
1.2 version.
NOOCPP: Without OCPP backend. The authorization list is used for
authenticating. If the setting 'ocpp.noocpp.auth.all.tokens' is set to false
(default), all tokens are accepted.
IS69685-frn - Rév.01-Novembre 2020
for more info about how this model name is
Page 41 sur 49