Charge points are connected to Monta via a a protocol called Open Charge Point Protocol (OCPP). The protocol allows the charge point and Monta to exchange commands and information in real-time via the internet connection on the charge point to Monta's servers.
One of the functionlties of OCPP, is that it allows Monta, and thereby the operator to alter settings (also known as configuration keys) on the charge point. In practice, this allows for tight device management tailored to how the operator wishes this exact charger should behave.
All chargers connected to Monta fullfill what is known as the "Core Profile". This is a bare minimum standard set of keys set required to be implemented in OCPP. These are defined by the Open Charge Alliance (OCA).
Brand specific configuration keys can be set by the hardware manufactorer. We call these "Custom keys". These are different from the Core Profile keys in that they can be set freely by manufactorers, and there is no standardisation in naming or what can be included.
1. Examples of what can be configured by operators
Note: These are a few examples of what can be configured in the Core Profule. For a full list of OCPP core profile keys, please refer to the Open Charge Alliance OCPP 1.6J
Messaging to Monta
- Heartbeat - an OCPP message sent in a fixed interval intended to let Monta know the charger is still connected.
- Meter Values - OCPP message sent in interval containing total amount of energy charged for this session
General charging behavior
- Connection time out - time in (s) the authorization of a user is active before the charge point times out. For example, 180 seconds means that after authorizing with Monta app or RFID, users have 180 seconds to plug in their car to start charging.
Offline charging behavior
- Authorization cache - saves all authorized RFID to the offline list
- Allow charging for unknown ID when offline
- Keep connector locked when disconnecting EV
Custom keys (brand specific)
- Screen brightness
- LED-indicator brightness
- Beeping sounds
2. What configurations do Monta configure by default?
Monta decides upon some configuration keys on connection. We believe these are the most sensible values, that strike a good balance between functionality while also using a less data, something that is important for charge points on a cellular connection.
Below is a list of what Monta configures for the core profile:
- ConnectionTimeOut: 180
- LocalPreAuthorize: false
- StopTxnAlignedData: ""
- StopTxnSampledData: ""
- LocalAuthorizeOffline: true
- MeterValuesAlignedData: Energy.Active.Import.Register
- MeterValuesSampledData: Energy.Active.Import.Register
- ClockAlignedDataInterval: 0
- MeterValueSampleInterval: 180
- AuthorizationCacheEnabled: false
- AuthorizeRemoteTxRequests: true
- AllowOfflineTxForUnknownId: false
- StopTransactionOnInvalidId: true
- StopTransactionOnEVSideDisconnect: true
- UnlockConnectorOnEVSideDisconnect: true
3. How can the operator change configuration keys?
Operators have accessed to the detailed logs in our so called "CPI Tool"
The charger will now respond with the list of configuration keys that are currently applied. This includes both editable and non editable keys.
Now simply press the edit button on the key you like to change
Now you can edit the value and press "Send" to apply it to the charge point:
Note: You can save the configuration as overwrite, which will force the value even though it might be changed due to some external factors.
Operators are able to configure charge points for specific use cases. Monta will configure some configuration keys, but not all.
In general, if a operator is unsure what a key does, please do not edit it, and contact the hardware manufactorer instead for an explaination.
For a full list of the Core Profile configuration keys, please download OCA whitepaper