EV Charge Web Docs | Tridens Technology – Integrations

Docs: Charging Session Integration

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Session Start Timeout
Driver Authorization
Offline Sessions
Meter Values Reporting
Session Event Retry

Session Start Timeout

Please ensure to configure the session start timeout period on charger side. It covers the time available to start the session, since the acceptance of remote start request or driver authorization.

Remote session start and authorization timeout on charger side represents the time since OCPP RemoteStartTransaction/Authorization acceptance, after which session must be started. If this time is breached, the charger should prevent any session start without the next OCPP RemoteStartTransaction or Authorization operation acceptance.

To avoid fraudulent usage, we suggest using preventive measures by configuring the charger’s timeout period in which the session is expected to start. OCPP 1.6 has a ConnectionTimeOut setting, which can be used, as described below.

Charger may also have other settings which are not part of OCPP 1.6 to handle other preventive scenarios - to tackle those, please check the charger’s specific manual or consult with the manufacturer.

OCPP 1.6 requires support for ConnectionTimeOut setting: Interval in seconds from beginning of status: ‘Preparing’ until incipient Transaction is automatically canceled, due to failure of EV driver to (correctly) insert the charging cable connector(s) into the appropriate socket(s). The Charge Point SHALL go back to the original state, probably: ‘Available’.

Session timeout section is related to ready-session-expiration settings of the central system, as it closes inactive sessions based on the expiration settings and idle job configuration. Make sure to use the consistent ready-session-expiration time on the central system, so it works aligned with the charger.

Example:

The EV driver plugs the connector with the vehicle. Then the driver presses the session start request button on the mobile application, and at this point, session is ready. Ready session expiration time of 30 seconds starts ticking. If it reaches 30 seconds and session did not start yet, then the session gets closed on the central system side and is not being tracked anymore.

Note:

If you experience the session without a customer reference, you need to make sure to configure the suitable timeout settings in dependence with ready-session-expiration settings.

Driver Authorization

As the drivers/customers who intend to charge the vehicle may use the payment types of prepaid, postpaid or pay-now, each session charging needs to be first authorized by the Tridens EV Charge’s central system to verify the driver’s fund sufficiency for beginning the charging session. Thus, charger’s local and offline authorizations lists and caches need to be disabled, to propagate all the authorizations to the central system.

Below is the list of OCPP 1.6 and OCPP 2.0.1 standardized authorization settings. Note that the chargers may have their own customized list of configuration settings, out of standardized scope. As a CPO, please review the charger specific implementation for any additional settings that need to be managed.

Configuration Attribute Name	Description	Restriction	OCPP 1.6 Variable Name	OCPP 2.0.1 Variable Name
Authorize Remote Session Requests	Indicates whether remote start requests need to be authorized by the charger before proceeding to charge.	Set to true, to ensure that the session is still authorized to start.	`AuthorizeRemoteTxRequests`	`AuthorizeRemoteStart`
Authorization Cache Enabled	Indicates whether the charger supports the authorization cache for the driver’s identifiers.	Set to false, to prevent using charger’s local authorization caches.	`AuthorizationCacheEnabled`	`AuthCacheEnabled`
Local Offline Authorization	Indicates whether the charger, when offline, will start a transaction for locally authorized identifiers.	Set to false, to prevent using charger’s local authorization caches.	`LocalAuthorizeOffline`	`LocalAuthorizeOffline`
Allow Offline Session of Unknown Driver	Indicates whether the charger allows authorizing any unknown identifiers that cannot be authorized by local authorization list or authorization cache.	Set to false, to prevent any unverified sessions.	`AllowOfflineTxForUnknownId`	`OfflineTxForUnknownIdEnabled`
Central Contract Validation	Indicates whether the Charge Point can provide a contract certificate that it cannot validate to the Central System for validation as part of the authorization. Used in the scope of ISO 15118’s Plug & Charge.	Set to true, so the central system’s verification is used.	`CentralContractValidationAllowed`	`CentralContractValidationAllowed`
Offline Contract Validation	Indicates whether the charge point will try to validate a contract certificate when it is offline (not connected to the central system). Used in the scope of ISO 15118’s Plug & Charge.	Set to false, so the central system’s verification is used.	`ContractValidationOffline`	`ContractValidationOffline`

Table 1: List of authorization settings to manage in OCPP 1.6 and 2.0.1.

Offline Sessions

Disable the charger to start the charging sessions without allowance of the central system, as it would result in non-customer public sessions.

Make sure to disable LocalAuthorizeOffline and AllowOfflineTxForUnknownId settings of OCPP 1.6 on the charger side.

CPO needs to review the charger specific implementation and configuration, as other settings out of standardized scope may apply.

Meter Values Reporting

Configure session meter values report interval on the charger, so the session’s progress will show up. We advise using a 15 seconds interval. You can usually configure this on the charger’s own dashboard, or use EV Charge dashboard, which can do it by OCPP.

To access this section in EV Charge, from the Menu, click Stations. A paginated list of all stations is shown in a tabular format. Click Actions for the specific station. On the station’s page, click Configuration on the top right corner to access Configuration page, then select Meter tab to regulate the sampling interval. Alternatively, the Custom tab can also be used for this.

Figure 1: Example of setting the interval in the Station’s Configuration form on Tridens EV Charge dashboard.

Note:

The settings can be set by the central system to the charger only when charger is connected to the central system and communicating by OCPP protocol.

To show active power measurement in mobile app, CPO needs to configure the charger to send the certain measurements in scope of the charging session (usually at least kW for power and kWh for energy). Once again, this is usually doable by the charger’s dashboard or EV Charge dashboard, where OCPP’s MeterValuesSampledData setting can be used.

To navigate to this area in EV Charge, go to the Menu and select Stations. You’ll see a paginated list of all stations in a tabular format. Click on Actions for the specific station. Once on the station’s page, on the the top right corner access the Configuration page, then select Meter tab to regulate the sampling measurands. Alternatively, the Custom tab at the top right corner can also be used.

Figure 2: Example of setting measurands in the Station’s Configuration form on Tridens EV Charge dashboard.

Note:

The settings can only be configured by the central system to the charger when the charger is connected to the central system and actively communicating via the OCPP protocol.

Important measurands to cope with:

Name	Description	OCPP 1.6 Name	OCPP 2.0.1 Name
Energy Import	Instantaneous imported energy (Wh or kWh) to the vehicle.	`Energy.Active.Import.Interval`	`Energy.Active.Import.Interval`
Power Import	Instantaneous power (W or kW) import to the EV.	`Power.Active.Import`	`Power.Active.Import`
Current Import	Instantaneous current (A) import to the EV.	`Current.Import`	`Current.Import`
Voltage	Instantaneous voltage (V) supply between grid and EV.	`Voltage`	`Voltage`
Battery State of Charge	Percentage representing the vehicle’s battery state of charge.	`SoC`	`SoC`

Table 2: List of measurands settings in OCPP 1.6 and 2.0.1.

Meter values which are related to the specific charging session and representing measurands related to it.

Session Meter Values Interval

Interval in seconds, by which the charger will send the meter value reports to the central system during the charging session. Suggested interval is 10-15 seconds.

Refers to MeterValueSampleInterval of OCPP 1.6 and SampledDataTxUpdatedInterval of OCPP 2.0.1.

Session Meter Values Measurands

Measurands which the charger will send on ‘Session meter values interval’. Suggested: power, energy, state of charge, voltage, current.

Refers to MeterValuesSampledData of OCPP 1.6 and SampledDataTxUpdatedMeasurands of OCPP 2.0.1.

General Meter Values

General meter values are reported independent of the session and may be required in the scenarios of the sessions which are being terminated by the final parking.

General Meter Values Interval

Interval in seconds, by which the charger will send regular meter value reports to the central system during the charging session.

Refers to ClockAlignedDataInterval of OCPP 1.6 and AlignedDataInterval of OCPP 2.0.1.

General Meter Values Measurands

Measurands which the charger will send on ‘General meter values interval’. Suggested: power offered.

Refers to MeterValuesAlignedData of OCPP 1.6 and AlignedDataMeasurands of OCPP 2.0.1.

Energy Reading Type Detection

Absolute: Energy meter reading which is accumulating consumption of all sessions on one connector.

Relative: Energy meter reading starting from 0 for each session.

The central system of Tridens EV Charge is utilizing the following energy consumption detection for a session, as there are different varieties of reporting types by chargers:

Chargers reporting an absolute energy meter values at session start, intermediate, stop. Energy of all the sessions on the charger so far.
Chargers reporting the session relative energy meter values at session start, intermediate, stop. Energy of the specific session.
Chargers reporting an absolute energy meter value at the start and stop of session, but in the intermediate time, they are sending relative session energy reports (zero based).

Energy Report Validation

The central system of Tridens EV Charge utilizes charging session’s energy consumption validation for the persisted charging session, when receiving the reports from the charger. Connector’s power capability is being verified along with the energy meter reading time. This mechanism serves to overcome an issue when the chargers report the deprecated or excessive energy meter consumption.

Validation is made in two steps, where both need to pass:

Timestamp of reported energy meter reading for the persisted session is verified against the persisted session’s latest valid meter reading. It is considered as valid if the energy meter reading’s timestamp is not older than the previous meter reading’s timestamp.
Reported energy (Wh/kWh) is verified against the capability of the connector. It is considered as valid if the energy consumed over time is possible for the connector’s power capacity in the time difference from the previous valid energy meter report timestamp of the persisted session.

Note:

Make sure to properly set the wattage limit on the connector configuration on Stations - Connectors.

If the connector has lower power capability configured, the energy difference reported will be too large for the configured capability and thus energy meter reports are going to be discarded and energy consumption will not be persisted on the Tridens EV Charge’s sessions.

The scenarios below are based on the charging connector which is capable of 30kW energy flow.

Screnario 1

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2050 Wh	08:01:00	Absolute meter reading.

Scenario 2

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	0 Wh	08:00:00	Session relative meter reading.
Session intermediate	25 Wh	08:00:30	Session relative meter reading.
Session stop	50 Wh	08:01:00	Session relative meter reading.

Scenario 3

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate 1	25 Wh	08:00:30	Session relative meter reading.
Session intermediate 2	50 Wh	08:01:00	Session relative meter reading.
Session stop	2075 Wh	08:01:30	Absolute meter reading.

Scenario 4

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate 1	2025 Wh	08:00:30	Absolute meter reading.
Session intermediate 2	2020 Wh	08:01:00	Absolute meter reading. Valid time, invalid deprecated energy report. Invalid and not impacting the session.
Session stop	2075 Wh	08:01:30	Absolute meter reading.

Scenario 5

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2020 Wh	08:01:00	Absolute meter reading. Valid time, invalid deprecated energy report. Invalid and not impacting the session.

Scenario 6

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate 1	2025 Wh	07:59:59	Absolute meter reading. Invalid deprecated time. Invalid and not impacting the session.
Session intermediate 2	2050 Wh	08:01:00	Absolute meter reading.
Session stop	2075 Wh	08:01:30	Absolute meter reading.

Scenario 7

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2050 Wh	08:00:29	Absolute meter reading. Invalid deprecated time. Invalid and not impacting the session.

Scenario 8

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2500 Wh	08:00:30	Absolute meter reading. Valid time. Invalid excessive energy report over connector’s power capacity. Invalid and not impacting the session.
Session stop	2050 Wh	08:01:00	Absolute meter reading.

Scenario 9

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2500 Wh	08:01:00	Absolute meter reading. Valid time. Invalid excessive energy report over connector’s power capacity. Invalid and not impacting the session.

Session Event Retry

Retry to send the event in case of failure. Suggested value is 3.

Refers to TransactionMessageRetryInterval of OCPP 1.6.

Docs: Charging Session Malfunctions

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Introduction
1. Session charging, but energy not progressing on Tridens
2. Session charging, but session shows 0 kW or 0 A on Tridens
3. No customer assigned on session
4. False time tracking
5. Faulted connector
6. Suspended EV/EVSE
7. Rating failed
8. Billing failed
9. Session did not start
10. Obsolete session, charger stops responding
11. Inadequate session

Introduction

This document describes scenarios of frequent EV charging session malfunctions with solution instructions and preventive measures.

1. Session charging, but energy not progressing on Tridens

Session charging at physical charger. Actual energy transferred >0 kWh, but on Tridens EV Charge web/mobile it shows 0 kWh or is stuck at some point above 0 kWh. This is usually the consequence of connector’s power limit being set too low on Tridens EV Charge dashboard, which causes the session energy validation rejections, as described in Energy Report Validation. Alternative issue might be that charging station is not reporting any energy consumption.

Figure 1: Session’s energy consumption not progressing on Tridens dashboard web/mobile.

Table 1: Solution & preventive measures of scenario 1.

Topic	Description
Connector’s power capacity configuration on Tridens	Adjust the connector’s power (W) capacity on Tridens EV Charge dashboard to reflect an actual power capacity of the connector. Provide the power value in unit of watts (W). This shall adjust the active session’s energy, once the next session meter values are reported. Future sessions shall contain the proper energy consumption. Session Integrations - Energy Report Validation
Enable reporting of energy consumption on station	Enable the reporting of energy (energy active import) on the physical station’s configuration. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings. Enable Energy.Active.Import.Register in Measurands. Future sessions shall then contain energy consumption reports.
Enable meter values reporting interval on station	Enable the reporting interval for session-related meter values on the physical charging station. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings and adjusting Meter Value Sample Interval. Interval is expected to be between 10-60 seconds. Session Integrations - Meter Values Reporting

2. Session charging, but session shows 0 kW or 0 A on Tridens

EV session charging at physical charger and actual energy is being transferred. Energy is >0 kWh, but power shows 0 kW or current 0 A on Tridens EV Charge web/mobile. This is usually the consequence of insufficient charger configuration in the scope of meter values reporting.

Figure 2: Session’s latest power and amperage missing on Tridens dashboard web/mobile.

Table 2: Solution & preventive measures of scenario 2.

Topic	Description
Enable reporting of energy consumption on station	Enable the reporting of power and current on the physical charging station’s configuration. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings. Enable Power.Active.Import and Current.Import in Measurands. Future sessions shall then contain power and current reports, as long as the charger supports reporting these. Session Integrations - Meter Values Reporting
Enable meter values reporting interval on station	Enable the reporting interval for session-related meter values on the physical charging station. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings and adjusting Meter Value Sample Interval. Interval is expected to be between 10-60 seconds. Session Integrations - Meter Values Reporting

Topic

Description

Enable reporting of energy consumption on station

Enable the reporting of power and current on the physical charging station’s configuration. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings. Enable Power.Active.Import and Current.Import in Measurands. Future sessions shall then contain power and current reports, as long as the charger supports reporting these.

Session Integrations - Meter Values Reporting

Enable meter values reporting interval on station

Enable the reporting interval for session-related meter values on the physical charging station. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings and adjusting Meter Value Sample Interval. Interval is expected to be between 10-60 seconds.

Session Integrations - Meter Values Reporting

3. No customer assigned on session

Session has no customer assigned, but charger is not publicly open.

Figure 3: No customer assigned on Tridens session.

Table 3: Solution & preventive measures of scenario 3.

Topic	Description
Session timeout	Such session state can be a consequence of non-proper configuration of connection timeout & session expiration settings. Adjust based on Session Start Timeout and Idle Session Settings. To avoid fraudulent usage, we suggest using preventive measures by configuring the charger’s timeout period in which the session is expected to start. It covers the time available to start the session, since the acceptance of remote start request or driver authorization at the spot. Remote session start and authorization timeout on charger side represents the pending period to start the session upon the acceptance, after which session start confirmation is expected from the charger. If this time is breached, the charger should prevent any session from starting without the next session authorization acceptance, whether by mobile remote request or authorization at the charger. Example: The EV driver plugs the charger’s connector to the vehicle. Then the driver presses the session start request button on the mobile application, and at this point, session is ready. Ready session expiration time of 30 seconds starts ticking. If it reaches 30 seconds and the session has not started yet, then the session gets closed on the central system side and is not being tracked anymore. Charger needs to discard this session as well by using the compatible timeout period, which is advised to be shorter than the one of the central systems due to the time elapsed for the commands exchange. Session timeout section is related to ready-session-expiration settings of the central system, as it closes inactive sessions based on the expiration settings and idle job configuration. Make sure to use the consistent ready-session-expiration time on the central system, so it works aligned with the charger.
Authorization caches	Disable charging station’s local authorization caches. Adjust physical station’s configuration in Stations - Actions - Configuration - Authorization and invalidate/disable authorization caches. Session Integrations - Driver Authorization
Authorization lists	Disable charging station’s local authorization lists. Adjust physical station’s configuration in Stations - Actions - Configuration - Authorization and disable, erase or update authorization lists. Session Integrations - Driver Authorization

4. False time tracking

Session charging most of the time (has high energy consumption), but parking/fault time is tracked instead. This indicates false connector status reporting.

Figure 4: Tridens session has inconsistent times.

Figure 5: Connector has non-proper status on Tridens web dashboard.

Table 4: Solution & preventive measures of scenario 4.

Topic	Description
Investigate OCPP logs	Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on latest reported connector statuses from the charger in StatusNotification. The condition may be a result of false connector status reporting or invalid timestamp included in the report. OCPP communication view: Stations - Logs - Logged OCPP Communication Session duration scopes (reservation, charging, parking, fault): Sessions - Duration Scopes
Use charging station’s latest firmware	Ensure using the charging station manufacturer’s latest stable firmware, which may already provide a correction. Otherwise, please contact the manufacturer about the connector status reporting issue and provide them the OCPP logs excerpt. Tridens EV Charge Operations - Stations - Firmware

Topic

Description

Investigate OCPP logs

Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on latest reported connector statuses from the charger in StatusNotification. The condition may be a result of false connector status reporting or invalid timestamp included in the report.

OCPP communication view:
Stations - Logs - Logged OCPP Communication

Session duration scopes (reservation, charging, parking, fault):
Sessions - Duration Scopes

Use charging station’s latest firmware

Ensure using the charging station manufacturer’s latest stable firmware, which may already provide a correction. Otherwise, please contact the manufacturer about the connector status reporting issue and provide them the OCPP logs excerpt.

Tridens EV Charge Operations - Stations - Firmware

5. Faulted connector

Session starts charging & charges load, then connector switches to faulted (hardware malfunction) and shows OCPP logs for investigation.

Figure 6: Connector has faulted status on Tridens web dashboard.

Figure 7: Tridens session contains fault time.

Table 5: Solution & preventive measures of scenario 5.

Topic	Description
Investigate OCPP logs	Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on the latest StatusNotification reports from the charger and find error logs. Vendor error codes may indicate a specific error that requires a technician’s action. OCPP communication view: Stations - Logs - Logged OCPP Communication Session duration scopes (reservation, charging, parking, fault): Sessions - Duration Scopes
Use charging station’s latest firmware	Ensure using the charging station manufacturer’s latest stable firmware, which may already provide a correction. Otherwise, please contact the manufacturer about the connector status reporting issue and provide them the OCPP logs excerpt. Tridens EV Charge Operations - Stations - Firmware
Notification on faulted connector	Use notifications to notify the charging infrastructure operator about the malfunction. Notification actions of interest: • Faulted connectors • Session with faulted time To configure notifications of different publishing types, follow instructions: System Configuration - Notifications More notification guidelines for operators are defined in: Integrations - Notifications Guidelines

6. Suspended EV/EVSE

Session started charging & charged some load, then connector was switched to suspended EV (charger offering energy, but EV not taking it) or suspended EVSE (charger not offering energy to EV). Please note that suspension may happen temporarily due to energy network load balancing or vehicle’s battery management system, to prevent failures.

Figure 8: Connector has suspended status on Tridens web dashboard.

Figure 9: Tridens session contains parking time, due to suspension.

Table 6: Solution & preventive measures of scenario 6.

Topic	Description
Investigate OCPP logs	Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on the latest StatusNotification reports from the charger. Exact status reason can be found in additional info attributes. Suspended EV means that charger is offering energy, but vehicle is not taking it. Suspended EVSE means that charger is not offering energy. OCPP communication view: Stations - Logs - Logged OCPP Communication Session duration scopes (parking, charging, …): Sessions - Duration Scopes

Topic

Description

Investigate OCPP logs

Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on the latest StatusNotification reports from the charger. Exact status reason can be found in additional info attributes.

Suspended EV means that charger is offering energy, but vehicle is not taking it.

Suspended EVSE means that charger is not offering energy.

OCPP communication view:
Stations - Logs - Logged OCPP Communication

Session duration scopes (parking, charging, …):
Sessions - Duration Scopes

7. Rating failed

Customer’s session was charging successfully, but it ended up in rating-failed status. Failed rating of session can be a consequence of false plan-product catalogue configuration in Tridens Monetization, false customer’s subscription plan configuration in Tridens Monetization or internal error due to maintenance. Rating can be retried manually or by an automated job.

Figure 10: Tridens session with rating-failed status.

Table 7: Solution & preventive measures of scenario 7.

Topic	Description
Manual retry rating	Attempt manual retry rating operation on session by using Tridens EV Charge web dashboard in Sessions - Actions and hit Retry rating. Sessions - Retry Rating
Automated retry rating	Automated retry rating operation is done by automated retry session rating job. Sessions - Retry Rating
Monetization catalogue configuration	Verify whether rate plan configuration is proper in Tridens Monetization.
Customer subscription plan configuration	Verify whether customer’s subscription plan configuration is proper in Tridens Monetization.

8. Billing failed

Customer’s session was charging successfully, but it ended up in billing-failed status. Failed billing of session can be a consequence of false plan-product catalogue configuration in Tridens Monetization, false customer’s subscription plan configuration in Tridens Monetization or internal error due to maintenance. Rating can be retried manually or by an automated job.

Figure 11: Tridens session with billing-failed status.

Table 8: Solution & preventive measures of scenario 8.

Topic	Description
Manual retry billing	Attempt manual retry billing operation on session by using Tridens EV Charge web dashboard in Sessions - Actions and hit Retry billing. Sessions - Retry Billing
Automated retry billing	Automated retry billing operation is done by automated retry session billing job. Sessions - Retry Billing
Monetization catalogue configuration	Verify whether rate plan configuration is proper in Tridens Monetization.
Customer subscription plan configuration	Verify whether customer’s subscription plan configuration is proper in Tridens Monetization.

9. Session did not start

Charging session has been requested to start and was prepared with ready status. Session then never proceeded to start and did not obtain the in-progress status. Eventually, the session becomes closed.

Such session state can be a consequence of non-proper configuration of connection timeout & session expiration settings or missing session event from the charging station.

Figure 12: Prepared session in ready status.

Figure 13: Non-started session has been closed.

Table 9: Solution & preventive measures of scenario 9.

Topic	Description
Ready session expiration on Tridens	Session on the Tridens EV Charge server is considered as idle when not receiving event reports from the charging infrastructure after a certain configured time. Ready session expiration represents allowed inactivity period for a prepared ready charging session. When background job detects a ready session’s inactivity exceeding this time, it finalizes it (rating and closing). Adjust ready session expiration settings on Tridens by following instructions in Tridens EV Charge – Idle Session Settings. Align the expiration period with the Session connection timeout period.
Session connection timeout of station	Ensure to configure the session start connection timeout period on the charging station side. It covers the time available to start the session, since the acceptance of remote session start request or driver authorization. Adjust physical station’s configuration in Stations - Actions - Configuration - Core/General and adjust the Connection timeout, as instructed in Tridens EV Charge – Charging Session Integration – Session Start Timeout Align the timeout with Ready session expiration on Tridens web dashboard.
Station did not report session start event	Verify whether the charging station has reported start session event (OCPP’s StartTransaction or TransactionEventRequest). See OCPP communication logs: Stations - Logs - Logged OCPP Communication If event is missing, ensure using the latest firmware on the charging station, otherwise report an issue to the manufacturer.

10. Obsolete session, charger stops responding

Charging session was charging and progressing, but at some point, the progress was not visible anymore on Tridens web dashboard and mobile application. Eventually, such session was detected as idle and switched from in-progress status to closed. Persisted energy may not reflect the value on the physical charger/vehicle.

Figure 14: Session stopped being tracked and eventually closed.

Table 10: Solution & preventive measures of scenario 10.

Topic	Description
Meter values reporting	Ensure having session meter values reporting enabled. Enable session meter values reporting interval on Stations - Actions - Configuration - Meterings - Interval of 10-60 seconds. Enable session meter values measurands reporting in Stations - Actions - Configuration - Meterings - Measurands. Advised to use Energy.Active.Import.Register, Power.Active.Import and Current.Import. For more guidelines and instructions on configuring the meter values, refer to Tridens EV Charge – Charging Session Integration – Meter Values Reporting.
Ongoing session expiration on Tridens	Session on the Tridens EV Charge server is considered as idle when not receiving event reports from the charging infrastructure after a certain configured time. Ongoing session expiration represents allowed inactivity period for an ongoing in-progress charging session. When background job detects an in-progress session’s inactivity exceeding this time period, it finalizes the session (rating and closing). Adjust ongoing session expiration settings on Tridens by following instructions in Tridens EV Charge – Idle Session Settings.
Charging station’s network issues	Consider that charging station’s web network issues may impact this. In large network inactivity times, session may be detected as idle and closed by ongoing-session-expiration rules on Tridens.
Charging station’s firmware issue	Charging station may stopped operating properly due to firmware issue, full messaging queue, memory overflow or any similar issue. Ensure using the latest stable firmware on the charging station.
Charging station’s hardware issue	Charging station may stopped operating properly due to hardware issue: EV communication error, high temperature, over voltage, power meter failure, reader failure, ground failure or other. Check out OCPP communication logs to find any fault indicators (StatusNotification): Stations - Logs - Logged OCPP Communication

11. Inadequate session

Recognize one of the following:

Sessions shorter than 5 minutes.
Sessions consumed less than 5 kWh of energy.
Non-properly tracked session times: Charging times, parking times, fault times.
No customer assigned on session.
No monetary amount assigned on session.

Table 11: Solution & preventive measures of scenario 11.

Topic	Description
Short session	See Session did not start and Obsolete session, charger stops responding.
Low energy consumption	See Session charging, but energy not progressing on Tridens and Faulted connector.
Session has non-proper times	See False time tracking.
Session has no customer assigned	See No customer assigned on session.
Session has no monetary amount	Verify whether rate plan configuration is proper in Tridens Monetization & whether customer’s subscription plan configuration is proper in Tridens Monetization.

Docs: Payment Terminal Integrations

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Introduction
Configuration
Charging Session Control

Introduction

This document describes the setup requirements for the payment terminal (POS) integration by OCPI or OICP communication protocols on Tridens EV Charge.

Integration involves Payment Terminal Providers (PTP) communicating with the charging infrastructure of charge point operators (CPO).
In this document, the term payment terminal provider is used as a technical term and is considered a synonym for the less technical term POS provider. The Payment Terminal Provider acts as a gateway to the charging infrastructure via OCPI or OICP protocols for charging session control and related data transfer. OCPI protocol offers official payment terminals support. For OICP, a hybrid concept can be utilized.

Notes:

Payment terminal providers can be added to Tridens EV Charge environment.
Payment terminal provider’s charging sessions are stored in Tridens EV Charge as part of an away charging infrastructure network, without a known customer/driver reference.
When the payment terminal provider charging session is utilized on a related CPO’s charging infrastructure that is part of Tridens EV Charge, such sessions appear as part of the home charging infrastructure network for that CPO.
Sessions are part of reporting in Tridens EV Charge for CPOs.

Figure 1: OCPI communication topology for payment terminal providers.

Configuration

Payment terminal providers can be configured in Tridens EV Charge tenant environments for CPOs. The following instructions focus on the OCPI protocol, as it officially defines payment terminal setup and communication (standardized since OCPI 2.2.1).

Configure Payment Terminal Provider

To configure the environment for a roaming Payment Terminal Provider (PTP):

Navigate to Roaming:
- Go to the Roaming section on the left-side menu of the Tridens EV Charge dashboard.
- Roaming Profile in this case represents environment as the operator of the charging infrastructure (chargers) in the roaming network.
- Roaming Platform here represents the third-party payment terminal provider.
- Submit configuration.
Create Roaming Profile (CPO):
- On the Roaming Profiles tab, create a new profile or use an existing one.
- Name & Code: Assign a name and code to identify the roaming profile.
- Type: Select CPO (charge point operator).
- Protocol: Select OCPI.
- Roaming ID: Three-uppercase-letter identifier that will represent CPO in roaming.
- Submit configuration.
Create Roaming Platform (PTP):
- Create a new Roaming Platform:
- Name & Code: Assign values to identify the platform.
- Type: Select Payment Terminal Provider (PTP).
- URL: Enter the payment terminal provider’s back-office server URL (e.g., https://your-pos-provider.com/api/ocpi).
- Country: Select the origin country of the payment terminal provider.
- Connection Initiation: Select which side will initiate the OCPI connection using the registration token.
- Credentials Exchange (Token):
  - If PTP provides the token: Select “I will use token provided by my roaming partner” and enter the token in the field.
  - If CPO provides the token: Select “I will provide token to my roaming partner” and click Generate. Share the generated token and your connection URL with the payment terminal provider.
Registration:
- Communication must be initiated via registration.
- Register credentials
  - If you used the partner’s token, click “Register credentials” on the selected Roaming Platform.
  - If you provided the token, the payment terminal provider must initiate the registration.
- Update Credentials: Use “Update credentials” to renegotiate credentials if needed.
- Invalidate Credentials: Use “Invalidate credentials” to stop communication/integration.

Figure 2: OCPI communication sequence.

Charging Infrastructure Setup

Once the CPO and PTP are communicating, the payment terminal provider can fetch the CPO’s charging infrastructure (Locations, EVSEs, Connectors). The CPO must populate specific roaming attributes to expose the infrastructure:

Area: Populate the roaming id with a unique identifier and the phone number.
Charger: Populate the roaming id with a unique identifier and mark the roaming attribute as enabled.
Connector: Populate the roaming id with a unique identifier.

Locations and charging infrastructure are reported to the payment terminal provider (push mode) and can also be fetched (pull mode).

Roaming Tariffs

As the charge point operator, you might want to assign roaming tariffs to represent prices for sessions initiated by payment terminal providers (PTP). Set up the Roaming Tariff for ad-hoc payments with the desired prices for energy and time, including taxes. Tariff also contains the max. amount for payment authorization of the charging session.

Important Notes:

Roaming tariffs calculate the expenses the payment terminal provider must pay to the charge point operator.
These prices are not necessarily what the end customer (EV driver) pays.

Configuration Guidelines:

Create Roaming Tariff:
- Navigate to Roaming -> Roaming Tariffs.
- Add a new tariff with a Name and Code.
- Set Status to Active and define the validity time range.
- Submit to create the tariff definition.
Add Tariff Details:
- Inside the tariff, add Tariff Details.
- Recurrency: Select One-time or Daily recurring.
- Priority: Higher priority details override lower ones if time frames overlap.
- Time Frame: Determine the inclusive start date-time and exclusive stop date-time. Select on which days the Tariff Detail applies.
- Pricing: Set the price and VAT percentage for rating metrics (energy, charge time, park time, flat, reservation time, etc.). Empty fields are treated as zero.
- Submit the configuration.
Assign Tariff to Roaming Platform (PTP):
- Navigate back to Roaming -> Roaming Platforms.
- Edit the specific Roaming Platform for the payment terminal provider configured earlier.
- In the setup wizard (usually Step 1), assign the Roaming Tariff.
- Submit the configuration.
Assign Tariff to Charging Infrastructure:
- Navigate to any charging infrastructure level having the Session Settings (also referred to as Session Rating Profile), which is assigned to the charging infrastructure on different levels.
- Assign the Roaming Tariff for the desired scope level:
  - Site
  - Operator
  - Charger
- Submit the configuration.

Once configured, new charging sessions related to this payment terminal provider will have costs calculated based on these settings. Tariffs are reported to the payment terminal provider (push mode) and can also be fetched (pull mode).

Charging Session Control

Operations by which the payment terminal provider can request the charge point operator of Tridens EV Charge to manage the charging session:

Remote session start
Remote session stop

Resulting and intermediate charging session actions are forwarded back to the payment terminal provider by API:

Session start
Session update
Session end
Charging infrastructure status changes
Final consumption report

Session progress is reported to the payment terminal provider (push mode) and can also be fetched (pull mode).

Docs: Charging Identification Device Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Device Type Setup
Device Setup
Assign Device to the Customer
Resign Customer’s Device

These are instructions to set up charging identification devices, e.g., RFID, NFC or certificate and assign them to the customers (drivers).

When the driver presents an identification device to the charger, for example by an RFID swipe, the charger requests the central system to identify and verify whether the driver is eligible to start the charging session.

Consists of multiple steps:

Device Type Setup
Device Setup
Assign Device to the Customer
Resign Customer’s Device

Device Type Setup

Set up the device types, which are intended to be supported. E.g., RFID, NFC, VIN, MAC.

Set up the device type first. To access this section in Monetization, from the Menu, click Devices. Open Device Type section tab on top. Use the green Create new button on the top right corner, so the creation form shows up.

Determine device type name as you desire and assign the code by one of the predefined code tags, which depend on the identification technology to be used, e.g., “RFID”. See the table of predefined device type code tags. You may also use the description box, to append additional helpful information and submit the creation form.

Code Tag	Description
RFID	Radio-frequency identification. Represents a badge or card of the driver.
NFC	Near field communication. Represents mobile or badge device of the driver.
VIN	Vehicle identification number. Represents a vehicle.
MAC	Media access control address, as unique device identifier in the network. May represents a vehicle or other device
ISO15118	Plug & charge of ISO 15118 for vehicle/driver identification. Represents a charging service contract of the vehicle and driver.
…	You can define your custom type as well.

Table 1: Device type’s predefined code tags, representing an identification technology.

Device Setup

Set up an instance of device. On the left side navigation, open the Devices section. Move the the Device section tab on top. Use the green Create new button on the top right corner, so the creation form shows up.

Assign name and code, as best suits you, select the belonging device type, for example an RFID.

Populate the Identifier field by the unique identification value, which is transferred from the charger to the central system, to be verified later when for example swiping an RFID. Submit the form.

Assign Device to the Customer

Once an identification device instance is set up, it is ready to be assigned to an existing customer (driver) with subscription plan.

To access this section in Monetization, from the Menu, click Customers and find the customer for which you would like to assign a device. Open up the customer details by Info button on the right side, under actions column. Then move to the Subscriptions section and expand the subscription which is desired to have an identification device assigned.

Move down to the Services section and find the one which is named CHARGING_SERVICE (also QUANTITY_CHARGING_SERVICE or similar - depends on the catalogue configuration) entry and hit Edit action. Edit the service’s Device column and search for the previously set up identification device, assign it and hit Submit action to update the service.

Figure 1: Find a customer

Figure 2: Expand customer’s subscription and find the suitable service

Figure 3: Assign device to service

Once identification device is assigned to the customer, swiping it (e.g., an RFID card) on the charger will result in charger requesting the central system to verify the device. This is called authorization, by which central system identifies the customer driver and verifies her/his monetary eligibility to start charging.

Once authorization is accepted, the charger is expected to allow the charging process to start.

Note:

Make sure that the customer to which an identification device is assigned has a valid subscription plan with a service, so the customer can be verified if eligible to charge.

If customer is pay-now, make sure credit card is assigned as well.

One device can be assigned to one customer at a time.

Resign Customer’s Device

When there is intention to remove an identification device from the customer, it can be done by navigating to the customer’s details view, as stated in section Assign Device to the Customer. Edit an existing service on hitting the cross button on the device, which is desired to be removed. Hit Submit action to update the service.

Figure 4: Resign customer’s service

Docs: FTP Server Setup

Mon, 01 Jan 0001 00:00:00 +0000

Download and install an SFTP/FTP software, for example, FileZilla . Run it as a server on your platform/computer, and provide the URL to EV Charge dialog to request the charger to use the FTP to upload/download files.

Here is the step-by-step tutorial for the FileZilla software.

1. Download the FileZilla

Download the FileZilla server installer uitable for your MacOS/Windows/Linux platform from FileZilla - The free FTP solution.

2. FileZilla Setup

a. Run the installer.

b. Check the licence agreement.

c. Among the components, select at least Server and Administration Interface.

Figure 1: Administration Interface

d. Choose the installation directory. Default value can be used.

e. Choose how FileZilla’s server is started. Manually (advised for usage on demand) or automatically at system start.

f. Assign adminstration interface’s listenting communication port. Default value can be used.

g. Protect your administration interface with the password and choose how administration interface is initiated (manually advised).

3. FTP setup

a. Once you open up the FileZilla Server, you can connect into it by using administration interface. Use host (localhost or 127.0.0.1), port (as configured in FileZilla setup step) and password (as configured in FileZilla setup step)

b. Assign a directory on your platform’s file system which will be shared. Use an existing directory or create a new directory on your desired path, e.g., C:\shared-directory.

c. FTP Users Setup

i. Open up the FileZilla configuration of user rights management (navigate by Server -> Configure -> Rights Management -> Users).

Figure 2: Users setup

ii. Hit Add User and perform the following:

Assign the user’s name (e.g., ‘mikejones’).

Figure 3: Assigning the user’s name

Determine the password if selecting Require the password to log in.

Figure 4: Password Login

Add a mount point. Assign the native path C:\shared-directory, meanwhile virtual path represents what FTP users can see.

Figure 5: Mount point settings

Assign access rights on the right side, whether users are allowed to read or read/write.

d. FTP Port Setup

To set up the FTP port, follow the steps below:

i. Open up the network configuration wizard (navigate by Server → Network Configuration Wizard).

Figure 6: Network Configuration Wizard

ii. Assign the port range, e.g. 30050-30055.

iii. Assign public IP address or hostname. This is the address by which your FTP will be accessed. Assing your device’s public IP by which your device will be accessible. Alternativelly you can use the domain, if available.

iv. Make sure your platform’s firewall has inbound/outbound TCP ports open for the communication on 30050-30055.

Figure 7: Ports and Protocols

The contents of configured directory C:\shared-directory are now accessble to the FTP user, which can connect to FTP server by using the platform/computer’s IP, for example ftp://miikejones:testpassword@192.168.5.1:30050.

Docs: Log Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Configuration
- Basic Example
- Advanced Example
Reading the Logs

Tridens EV Charge platform can be utilized to log and review the occurred events by the charging infrastructure or those related to the charging sessions control. Feature is called log notifications and is based on the instructions of System Configuration - Notifications, where logging notifications configuration can be made by the Log publishers.

Configuration

Operators can configure to be notified on the wide range of events, related to the charging infrastructure availability and charging session control.

A few events to consider enabling for log notifications, so the operators can track the charging infrastructure’s behavior:

Station connected
Station disconnected
Connector status changed
Reservation created
Reservation canceled
Session started
Session refused
Session’s charging ended
Session ended
Session’s state-of-charge (EV battery) limit breached
Session’s charge time limit breached
Session’s park time limit breached
Session’s fault time limit breached

For the complete list of actions in different scopes, see Notifications.

Basic Example

Basic example is represented in Figure 1 about adding a new logging notification configuration for the event when the charging station successfully connects to the central system of Tridens EV Charge. Log publisher is used with the default template format, as template attribute remained unselected.

Figure 1: Log notification configuration for charging station’s connection establishment with the central system.

Advanced Example

Advanced example is represented by Figures 2 and 3, where Figure 2 shows the logging notification configuration for the event when monetary limit of 50€ has been breached for the customer’s charging session. Filter Monetary limit is mandatory for the event and is set to 50€ threshold in this case. Instead of a default logging notification template, the custom configured notification template named as ‘Monetary Limit Breach 50€’ can be used. Figure 2 shows such notification template configuration on the different section of the UI.

Figure 2: Log notification configuration for the charging session’s monetary limit breach of 50€.

Figure 3: Notification template configuration for monetary limit breach of 50€ for the charging session.

Reading the Logs

Navigate to Stations and select the specific station for which you would like to review its logs and click under Actions to view station details. On the top right icons on the specific station’s page, click View logs icon (Figure 4).

Figure 4: Navigating to view the charging station’s notification logs.

The paginated logs view shows up, as in Figure 5. Time filters can be used to restrict the results range. Use Preferences to manage pagination and appearance.

Figure 5: Filtering the logs.

Docs: Notifications Guidelines

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Notifications Setup Guidelines in General
Notifying EV Drivers
Notifying the Operators

Notifications Setup Guidelines in General

Charging providers usually want to enable the notifying features, so they can inform the EV drivers about the status of their charging session or to inform themselves about the status of the charging infrastructure.

This section can serve as a guide on the options which can be utilized for the notifying. Base general steps for configuring the notifications can be found in Notifications section.

See the following references to find notifications setup technologies:

Notifying EV Drivers

EV drivers (also end users, end customers), usually want to be notified about the status of the charging sessions. Setup of these kind of notifications differs based on the session handling configuration, as described in Sessions - Session Rating Settings. Full list of available notification actions is described in Notifications Scopes and Actions.

The most used actions for notifying the EV drivers during the session by using the push notifications or SMS for mobile devices are the following:

Charging end - Indicating that session’s charging has ended, but parking fees may apply after. You can notify the driver that the charging process is done and prompt them to remove the vehicle.
Battery percentage limit - Indicating that certain amount of battery percentage (configurable) has been breached for the session, if reported by the charger. E.g., EV battery achieved 85%.
Energy limit - Indicating that certain amount of energy in kWh (configurable) has been spent for the session so far. E.g., EV session’s energy consumption achieved 40 kWh.
Charge time limit - Indicating that certain time for charging (configurable) has been spent for the session so far. E.g., EV session charging duration achieved 30 minutes.
Park time limit - Indicating that the certain parking time (configurable) has been spent for the session so far. E.g., EV session in parking mode duration achieved 15 minutes. Prompt driver to remove the vehicle and release the spot.
Park time threshold breach - Indicating that the parking time spent for the session has achieved the configured rating threshold of the EV charging session. From this point, parking time fees may apply. Based on configuration of Sessions - Session Rating Settings.
Monetary limit - Indicating that certain amount of money (configurable) has been spent for the session so far. E.g., EV session charging cost achieved 25€.

For the cases of notifying EV drivers by an email, the following actions may be useful:

Session end - Indicating that the charging session has ended and summary can be published.
Session refused - Indicating that the charging session didn’t succeed, as initial authorization of customer’s resources didn’t succeed.

Notifications are headed to the session’s driver/customer, when an action is related to the specific customer and notification rule’s receiver of type ‘Customer’ is selected. See Fig. 1 below. Applies for the session related actions, as these are customer related. Customer’s primary contact info is used for it, so push notification reference, email or phone number for SMS is taken from there.

See Notifications - Create Notification Rule section.

Fig. 1: Example of notification rule configuration headed to the customer when the EV charging session ends.

Content formatting definition example:

Charging session ${object.contents.session.id?c!'/'} ended.
Consumed ${object.contents.session.totalEnergy?c!'/'}kWh for the cost of ${object.contents.session.usedAmount?c!'/'}€.

Results in:

Charging session 9718 ended. Consumed 29.33kWh for the cost of 8.28€.

Notifying the Operators

Operators may be interested in being notified when significant changes appear on the charging infrastructure. Informing can be done by an email, SMS, logging or API call. Full list of available notification actions is described in Notifications Scopes and Actions.

Actions which can be especially helpful to operators:

Station connected - Indicating that the charging station has established a connection with the central system of Tridens EV Charge. If re-connections are happening, the station may need an urgent review.
Station disconnected - Indicating that the charging station has been disconnected from the central system of Tridens EV Charge. May need an urgent review, as connected station is necessary for availability of operations.
Station booted - Indicating that charging station has sent the boot notification. If the boot was not intentionally triggered, it may need a review.
Status changed - Indicating that the charger’s or connector’s status has changed. Advised to use notification for the transition to the ‘faulted’ status, as it usually needs to be troubleshooted.
Fault time limit - Indicating that certain fault time (configurable) has been spent for the charging session so far. E.g., EV session in fault mode duration breached 5 mintues. Needs operator’s review.

Operator related notifications are usually headed to the specific address (i.e. email), hence notification rule’s receiver of type ‘Base’ is usually selected with the contact populated. See Fig. 2 below.

Alternativelly, email sender (from) can be determined on email template as well.

See Notifications - Create Notification Rule section.

Fig. 2: Example of notification rule configuration headed to the specific operator’s email address when the charging station device disconnects from the central system and the occasion needs to be reviewed.

Content formatting definition example:

Charging station ${object.contents.charging_station.name!'/'} has disconnected from the central system. Id:${object.contents.charging_station.id?c!'/'} Code:${object.contents.charging_station.code!'/'} Address: ${object.contents.charging_station.address!'/'} ZIP: ${object.contents.charging_station.zip!'/'} City: ${object.contents.charging_station.city!'/'} Country: ${object.contents.charging_station.country!'/'} Latitude: ${object.contents.charging_station.latitude?c!'/'} Longitude: ${object.contents.charging_station.longitude?c!'/'}

Results in:

Charging station Tridens Building has disconnected from the central system. Id:5274 Code:f1db01db-3f7c-4804-9d9a-e54cb1037040 Address: Titova 2a ZIP: 2000 City: Maribor Country: SI Latitude: 46.56007700000001 Longitude: 15.6510651.

Docs: Push Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Push Notifications Provider Configuration
Notification Template
Notification Rules Configuration

Set up push notifications for Tridens EV Charge using a third-party solution. Once configuration is established and the configured notification action happens, push notification is expected on the targeting driver/customer device.

Push Notifications Provider Configuration

First of all, configuring the push notifications provider is required. Currently, Firebase is available. See System Configuration - Firebase Configuration.

Notification Template

In the next step, we need to determine the push notification template(s). To achieve this, go to Business Configuration → Templates → Push Notification Templates. There you can manage the message templates. Name the template, assign code as alphanumeric identifier, apply description if necessary and most importantly, enter the formatted content.

See Business Configuration - Templates - Push Notification Templates for more details.

Notification Rules Configuration

Then proceed to the notification rules configuration. Go to System Configuration → Notifications → Notifications and edit your existing configurations. In the Publishers section, add and select new Push action. No need to specify any specific ‘Receivers’, as such notifications are headed to the action’s belonging customer device directly. See Fig. 1 below.

Figure 1: Notification rule configuration with push publisher.

Docs: SMS Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

SMS Provider Configuration
SMS Template
Notification Rules Configuration

Set up SMS notifications for the actions on Tridens EV Charge. Once configuration is established and the configured notification action happens, SMS notification is expected on the targeting receiver.

SMS Provider Configuration

First of all, configuring the SMS notifications provider is required. Currently, Twilio provider is available.

Once you register on Twilio, you can manage your provider configuration in Tridens EV Charge’s dashboard by navigating to System Configuration → Platforms and select Twilio.

Once the form shows up, insert the phone number (E.164 format), client id and client secret, which was provided to you by Twilio following the registration.

SMS Template

In the next step, we need to determine the SMS template(s). To achieve this, go to Business Configuration → Templates → SMS Templates.

There you can manage the message templates. Name the template, assign code as alphanumeric identifier and apply description, if helpful. Then define the dynamically formattable content, which represents an actual content of the SMS notification message.

See Business Configuration - Templates - SMS Templates for more details.

Figure 1: SMS template creation

Notification Rules Configuration

In the Receivers sub-section of a Publisher, add the necessary receivers, as desired:

Base: Enter the specific phone number to which the SMS notification should be sent for the action.
Customer: SMS notification targets to the destination of customer’s primary contact info phone number, if action is related to the specific customer. Applies for the session related actions, as these are related to the customer. Additionally, as a value, Customer Type group can be selected, meaning that SMS notification will apply only if the customer belongs to the specific customer group.

Figure 2: Notification rule configuration with the SMS publisher

Docs: Email Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Email Server (SMTP) Configuration
Email Template
Notification Rules Configuration

Set up email notifications for the actions on Tridens EV Charge. Once configuration is established and the configured notification action happens, email notification is expected on the targeting receiver.

Email Server (SMTP) Configuration

First step to enable email notifications is to equip yourself with an email server, usually by utilizing the email server hosting provider.

Once Simple Mail Transfer Protocol (SMTP) email server is established, enter the SMTP settings into environment of Tridens EV Charge - these settings are manageable in the Site settings section. At the point when SMTP host server is configured on environment with username, password, host and port, proceed to configuring the notification template.

Email Template

In the next step, we need to determine the email template(s). To achieve this, go to Business Configuration → Templates → Email Templates.

There you can manage the message templates. Name the template, assign code as alphanumeric identifier and apply description, if helpful. Determine the subject which will appear on the emails. From, to, carbon-copy, blind-carbon-copy and reply-to are optional - note that from (source) can be auto-assigned based on your email server and to (destination) also gets populated by the notification rule’s receivers, as defined in System Configuration - Notifications.

The most important part comes at the bottom, where dynamically formattable content can be defined by using the content builder.

See Business Configuration - Templates - Email Templates for more details.

Figure 1: Email template creation.

Notification Rules Configuration

In the Receivers sub-section of a Publisher, add the necessary receivers, as desired:

Base: Enter the specific email address to which the notification should be sent.
Customer: Notification targets to the destination of customer’s primary contact info email, if action is related to the specific customer. Applies for the session related actions, as these are related to the customer. Additionally, as a value, Customer Type group can be selected, meaning that notification will apply only if the customer belongs to the specific customer group.

Figure 2: Notification rule configuration with the email publisher.

EV Charge Web Docs | Tridens Technology – Integrations

Docs: Charging Session Integration

Session Start Timeout

Example:

Note:

Driver Authorization

Offline Sessions

Meter Values Reporting

Note:

Note:

Session Related Meter Values

Session Meter Values Interval

Session Meter Values Measurands

General Meter Values

General Meter Values Interval

General Meter Values Measurands

Energy Reading Type Detection

Energy Report Validation

Note:

Session Event Retry

Docs: Charging Session Malfunctions

Introduction

1. Session charging, but energy not progressing on Tridens

2. Session charging, but session shows 0 kW or 0 A on Tridens

3. No customer assigned on session

4. False time tracking

5. Faulted connector

6. Suspended EV/EVSE

7. Rating failed

8. Billing failed

9. Session did not start

10. Obsolete session, charger stops responding

11. Inadequate session

Docs: Payment Terminal Integrations

Introduction

Notes:

Configuration

Configure Payment Terminal Provider

Charging Infrastructure Setup

Roaming Tariffs

Charging Session Control

Docs: Charging Identification Device Setup

Device Type Setup

Device Setup

Assign Device to the Customer

Note:

Resign Customer’s Device

Docs: FTP Server Setup

Docs: Log Notifications Setup

Configuration

Basic Example

Advanced Example

Reading the Logs

Docs: Notifications Guidelines

Notifications Setup Guidelines in General

Notifying EV Drivers

Notifying the Operators

Docs: Push Notifications Setup

Push Notifications Provider Configuration

Notification Template

Notification Rules Configuration

Docs: SMS Notifications Setup

SMS Provider Configuration

SMS Template

Notification Rules Configuration

Docs: Email Notifications Setup

Email Server (SMTP) Configuration

Email Template

Notification Rules Configuration