<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>EV Charge Web Docs | Tridens Technology – Operations</title><link>/ev-charge-web-docs/categories/operations/</link><description>Recent content in Operations on EV Charge Web Docs | Tridens Technology</description><generator>Hugo -- gohugo.io</generator><atom:link href="/ev-charge-web-docs/categories/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs: Chargers</title><link>/ev-charge-web-docs/operations/chargers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/ev-charge-web-docs/operations/chargers/</guid><description>
&lt;p>To access this section in &lt;strong>EV Charge&lt;/strong>, from the &lt;i class="fa fa-bars" aria-hidden="true">&lt;/i> &lt;strong>Menu&lt;/strong>, select &lt;i class="fa fa-wrench" aria-hidden="true">&lt;/i> &lt;strong>Operations&lt;/strong>, and click &lt;strong>Chargers&lt;/strong>. A paginated list of all chargers is shown in a tabular format.&lt;/p>
&lt;p>To generate the chargers list in a spreadsheet, click &lt;i class="fa fa-file" aria-hidden="true">&lt;/i> &lt;strong>CSV&lt;/strong>. To print, click &lt;i class="fa fa-solid fa-print" aria-hidden="true">&lt;/i> &lt;strong>Print&lt;/strong>, and to copy, click &lt;i class="fa fa-copy" aria-hidden="true">&lt;/i> &lt;strong>Copy&lt;/strong>.&lt;/p>
&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note:&lt;/h4>
They are generated, printed, and copied per paginated page.
&lt;/div>
&lt;div class="alert alert-info" role="alert">
&lt;h4 class="alert-heading">Information:&lt;/h4>
You can filter for a charger by name, serial number, model, vendor, operational status, or/and charging status.
&lt;/div>
&lt;p>To see the list of connectors found in a charger, click &lt;i class="fa fa-chevron-circle-right" aria-hidden="true">&lt;/i> &lt;strong>Expand&lt;/strong>.&lt;/p>
&lt;p>Both chargers and connectors can be turned on/off. To achieve this, click &lt;i class="fa fa-power-off" aria-hidden="true">&lt;/i> &lt;strong>Request availability change&lt;/strong>. Turning off a connector will send a request to the charger via OCPP to make that part inoperative.&lt;/p>
&lt;p>Turning a charger/connector on/off is the same as making it available or unavailable to end users. Unavailable chargers in the &lt;strong>EV Charge - Mobile App&lt;/strong> cannot be used to start a session.&lt;/p>
&lt;p>Change availability is the operation (based on OCPP) which provides an operator to manage the availability of the connected charging device from the Tridens EV Charge’s central system. Operation offers to request the connected charging device to change the availability of the charger or specific connector from &lt;code>Unavailable&lt;/code> to &lt;code>Available&lt;/code> and vice-versa.&lt;/p>
&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note:&lt;/h4>
Please note that this feature can not be used if the charging device is not connected with the central system, as in that case the central system does not have any control over the charging device.
&lt;/div>
&lt;div class="alert alert-dark" role="alert">
&lt;h4 class="alert-heading">Tip:&lt;/h4>
Turning a charger/connector on/off can be helpful during maintenance.
&lt;/div>
&lt;p>Furthermore, a connector can be locked/unlocked by clicking &lt;i class="fa fa-unlock" aria-hidden="true">&lt;/i>.&lt;/p>
&lt;p>Some EV chargers lock the connector to prevent it from being removed during charging for safety purposes. The lock/unlock action manually triggers that process. It is typically used for debugging or resolution if the charger does not release the connector due to a malfunction.&lt;/p></description></item><item><title>Docs: Stations</title><link>/ev-charge-web-docs/operations/stations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/ev-charge-web-docs/operations/stations/</guid><description>
&lt;p>To access this section in &lt;strong>EV Charge&lt;/strong>, from the &lt;i class="fa fa-bars" aria-hidden="true">&lt;/i> &lt;strong>Menu&lt;/strong>, select &lt;i class="fa fa-wrench" aria-hidden="true">&lt;/i> &lt;strong>Operations&lt;/strong>, and click &lt;strong>Stations&lt;/strong>. A paginated list of all charging stations is shown in a tabular format.&lt;/p>
&lt;p>To generate the stations&amp;rsquo; list in a spreadsheet, click &lt;i class="fa fa-file" aria-hidden="true">&lt;/i> &lt;strong>CSV&lt;/strong>. To print, click &lt;i class="fa fa-solid fa-print" aria-hidden="true">&lt;/i> &lt;strong>Print&lt;/strong>, and to copy, click &lt;i class="fa fa-copy" aria-hidden="true">&lt;/i> &lt;strong>Copy&lt;/strong>.&lt;/p>
&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note:&lt;/h4>
They are generated, printed, and copied per paginated page.
&lt;/div>
&lt;div class="alert alert-info" role="alert">
&lt;h4 class="alert-heading">Information:&lt;/h4>
You can filter for a charging station by name, serial number, model, vendor, or/and operational status.
&lt;/div>
&lt;p>OCPP-related operations on the charging station include the following:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="#reboot">Reboot&lt;/a>&lt;/li>
&lt;li>&lt;a href="#firmware-upgrade">Firmware upgrade&lt;/a>&lt;/li>
&lt;li>&lt;a href="#diagnostic-logs">Diagnostic logs&lt;/a>&lt;/li>
&lt;li>&lt;a href="#trigger-message">Trigger message&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="reboot">Reboot&lt;/h2>
&lt;p>The &lt;a href="../../stations">charging station&lt;/a> in &lt;strong>EV Charge&lt;/strong> is the network component. To send a reboot request to the charging station, click &lt;i class="fa fa-sync" aria-hidden="true" style="color: red;">&lt;/i> &lt;strong>Reboot&lt;/strong>.&lt;/p>
&lt;h2 id="firmware-upgrade">Firmware upgrade&lt;/h2>
&lt;p>To request a firmware upgrade on the charging station, click &lt;i class="fa fa-upload" aria-hidden="true">&lt;/i> &lt;strong>Firmware update&lt;/strong>. Provide a location (in URL form)&amp;mdash;typically, this is an FTP location or an HTTP address from where the file can be downloaded.&lt;/p>
&lt;div class="alert alert-info" role="alert">
&lt;h4 class="alert-heading">Information:&lt;/h4>
&lt;p>The format of the FTP URL is: &lt;span style="background-color: #161c47; color: #dee2e6; padding: 0px 3px;">ftp://user:password@host:port/path&lt;/span> where &lt;span style="background-color: #161c47; color: #dee2e6; padding: 0px 3px;">user:password@&lt;/span>, &lt;span style="background-color: #161c47; color: #dee2e6; padding: 0px 3px;">:password&lt;/span>, or &lt;span style="background-color: #161c47; color: #dee2e6; padding: 0px 3px;">:port&lt;/span> can be omitted.&lt;/p>
&lt;p>The format of the HTTP address is: &lt;span style="background-color: #161c47; color: #dee2e6; padding: 0px 3px;">http://hostname:port/path&lt;/span> where &lt;span style="background-color: #161c47; color: #dee2e6; padding: 0px 3px;">:port&lt;/span> can be omitted.&lt;/p>
&lt;/div>
&lt;p>The &lt;strong>Retrieve at&lt;/strong> indicates when the charging station will download the file, and the &lt;strong>Install at&lt;/strong> means when the update (in the form of a file) will be installed on the charging station.&lt;/p>
&lt;p>&lt;strong>Retries&lt;/strong> and &lt;strong>Retry interval&lt;/strong> represent how many times and at what interval, respectively, the charging station will re-download the file in case the download fails on the first attempt.&lt;/p>
&lt;p>Clicking &lt;strong>Request&lt;/strong> schedules the firmware upgrade on the charging station.&lt;/p>
&lt;h2 id="diagnostic-logs">Diagnostic logs&lt;/h2>
&lt;p>To request diagnostic logs for the charging station, click &lt;i class="fa fa-file" aria-hidden="true">&lt;/i> &lt;strong>Diagnostic request&lt;/strong>. Provide the periods from which to retrieve the diagnostic logs by configuring the start and stop times.&lt;/p>
&lt;p>Additionally, provide a URL where the logs will be uploaded because OCPP does not work with direct file transfer. You will need an SFTP/FTP server where the file will be pushed or an HTTP address.&lt;/p>
&lt;div class="alert alert-dark" role="alert">
&lt;h4 class="alert-heading">Tip:&lt;/h4>
Download and install an SFTP/FTP client/software, for example, &lt;a href="https://filezilla-project.org/">FileZilla&lt;/a> &lt;i class="fa fa-external-link-alt" style="color: #3176d9" aria-hidden="true">&lt;/i>. Run it as a server on your computer, and provide the URL to &lt;strong>EV Charge&lt;/strong> to download the file to the server.
&lt;/div>
&lt;p>&lt;strong>Retries&lt;/strong> and &lt;strong>Retry interval&lt;/strong> represent how many times and at what intervals the charging station retries to upload the diagnostic logs to the URL if it fails on the first attempt.&lt;/p>
&lt;p>By clicking &lt;strong>Request&lt;/strong>, the charging station will collect its internal logs and send them to the link configured in the URL.&lt;/p>
&lt;h2 id="trigger-message">Trigger message&lt;/h2>
&lt;p>Trigger message is used to trigger specific OCPP actions on the charger, mainly for the purpose of debugging or testing. To trigger a message, click &lt;i class="fa fa-exclamation" aria-hidden="true">&lt;/i> &lt;strong>Trigger message&lt;/strong>, and select the type of trigger message, which could be:&lt;/p>
&lt;ul>
&lt;li>Boot notification&lt;/li>
&lt;li>Diagnostics status notification&lt;/li>
&lt;li>Firmware status notification&lt;/li>
&lt;li>Heartbeat&lt;/li>
&lt;li>Meter values&lt;/li>
&lt;li>Status notification&lt;/li>
&lt;/ul></description></item><item><title>Docs: Authorization</title><link>/ev-charge-web-docs/operations/authorization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/ev-charge-web-docs/operations/authorization/</guid><description>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th>Name&lt;/th>
&lt;th>Description&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>Local offline authorization&lt;/td>
&lt;td>Controls whether the charger will authorize the user when they are offline by using the authorization cache and/or local authorization list.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Local pre-authorize&lt;/td>
&lt;td>Controls whether the charger will use authorization cache and/or local authorization list to start a session without waiting for an authorization response from the central system. The central system can later deauthorize the user at session event exchange.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Local auth list enabled&lt;/td>
&lt;td>Indicates whether the local authorization list is enabled on the charging station.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Set local list max. length&lt;/td>
&lt;td>Charging station’s maximum number of identifiers that can be sent in a single request to update the authorization list.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Local auth list&lt;/td>
&lt;td>Maximum number of identifiers that can be stored in the local authorization list of the charging station.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Allow offline session of unknown id&lt;/td>
&lt;td>Indicates whether the station supports the unknown-offline-authorization feature.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Authorization cache enabled&lt;/td>
&lt;td>Indicates whether the authorization cache is enabled on the charging station.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Authorize remote start&lt;/td>
&lt;td>Indicates whether additional authorization at remote session start request is enabled on the charger. If enabled, the charger issues authorization when it receives the remote start request from mobile/web.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table></description></item><item><title>Docs: Local Authorization Management</title><link>/ev-charge-web-docs/operations/local-authorization-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/ev-charge-web-docs/operations/local-authorization-management/</guid><description>
&lt;p>Local authorization feature provides that the charger can authorize customers/drivers without using the central system, while being offline.&lt;/p>
&lt;p>The central system of Tridens EV Charge instructs the charger about the list of authorization identifiers which can be used locally by the charger to authorize the drivers for charging. Each list has a version for the operational reference. Operation can be used as full override (overrides all identifiers) or differential (add/update the specific identifiers). The system can also request a charger for the version number of the local authorization list. This way an operator/provider can find out which authorization list is currently being set up on the charger.&lt;/p>
&lt;p>To manage the charging station’s local authorization list, the following operations are available from the perspective of the central system of Tridens EV Charge:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Send local authorization list (full update).&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Send local authorization list (differential - partial update).&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Get local authorization list version.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Handling the charging station&amp;rsquo;s configuration settings for local authorization.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Local authorization and authorization cache are separate features and cache does not impact the local authorization list.&lt;/strong>&lt;/p></description></item><item><title>Docs: Authorization Cache</title><link>/ev-charge-web-docs/operations/authorization-cache/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/ev-charge-web-docs/operations/authorization-cache/</guid><description>
&lt;p>Operators/providers may utilize the charger&amp;rsquo;s ability for the authorization cache. Authorization cache autonomously maintains a record of previously presented identifiers (RFID, NFC, certificate, &amp;hellip;) that have been successfully authorized by the central system of Tridens EV Charge. This charger’s feature is controllable from the Tridens central system side by using the configuration keys, as described in &lt;strong>Stations - Live Configuration Parameters&lt;/strong>.&lt;/p>
&lt;p>This feature needs to be used carefully and might only be proper in the following cases:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>For the businesses, where the charging service is available only for post-paid customers, as sessions regulated by the local authorization cache are not authorizing any customer/driver resources, to verify whether customer has enough funds. &lt;/p>
&lt;/li>
&lt;li>
&lt;p>Charging station is located in area with non-stable network connection. &lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>Authorization cache impacts:  &lt;/p>
&lt;ul>
&lt;li>
&lt;p>Cache entries may contain expiry dates, which are considered at validation. &lt;/p>
&lt;/li>
&lt;li>
&lt;p>If authorization happens and an invalid identifier is present in the cache while the charger is online, the charger uses the central system to authorize. &lt;/p>
&lt;/li>
&lt;li>
&lt;p>Authorization cache has no impact on the local authorization list! These two features are separated and local authorization lists are fully controllable from the central system. Also, identifiers from local authorization list should not be added to the authorization cache. If both are used, the local authorization list has priority over the authorization cache for the same identifiers. &lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Local authorization and authorization cache are separate features and cache does not impact the local authorization list.&lt;/strong>&lt;/p></description></item></channel></rss>