Skip to content

Device product pages #814

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
The diff you're trying to view is too large. We only load the first 3000 changed files.
49 changes: 49 additions & 0 deletions docs/devices-next/chargers/abb-terra-ac-ocpp.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
---
title: ABB Terra AC (OCPP)
custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abb-tac.yaml
hide_table_of_contents: true
---

import DeviceConfig from '@site/src/components/DeviceConfig';
import DeviceFeatures from '@site/src/components/DeviceFeatures';
import SponsorshipRequired from '/docs/_sponsorship_required.mdx';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# ABB Terra AC (OCPP)

<DeviceFeatures features="mA,rfid,sponsorship" />

https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf


<DeviceConfig code={`chargers:
- name: my_charger
type: template
template: ocpp-abb-tac
stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers:
- name: my_charger
type: template
template: ocpp-abb-tac
stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
connecttimeout: 5m # Timeout for the registration of the charging point, optional
meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />

## Template Parameter `ocpp-abb-tac`

| Name | Explanation | Value | Optional |
|-----------|-------------|-------|----------|
| Station ID<br/>`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://&lt;evcc-address&gt;:8887/&lt;stationid&gt;. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no |
| Connector number<br/>`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no |
| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected<br/>`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no |
| Identifier used for authentication of external transactions (RemoteStartTransaction)<br/>`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no |
| Timeout for the registration of the charging point<br/>`connecttimeout` | | Standard: `5m` | no |
| Transmission interval of meter values (MeterValueSampleInterval)<br/>`meterinterval` | | Standard: `10s` | no |
| Manual specification of the meter values to be configured (MeterValuesSampledData)<br/>`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no |

<SponsorshipRequired />

51 changes: 51 additions & 0 deletions docs/devices-next/chargers/abb-terra-ac.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
title: ABB Terra AC
custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abb.yaml
hide_table_of_contents: true
---

import DeviceConfig from '@site/src/components/DeviceConfig';
import DeviceFeatures from '@site/src/components/DeviceFeatures';
import SponsorshipRequired from '/docs/_sponsorship_required.mdx';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# ABB Terra AC

<DeviceFeatures features="mA,sponsorship" />

Requires firmware >= 1.6.5


<DeviceConfig code={`chargers:
- name: my_charger
type: template
template: abb

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter für den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port`} />

## Template Parameter `abb`

| Name | Explanation | Value | Optional |
|-----------|-------------|-------|----------|
| `modbus` | | Auswahl: `rs485`, `tcpip` | no |

<SponsorshipRequired />

46 changes: 46 additions & 0 deletions docs/devices-next/chargers/abl-em4-single-ocpp.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: ABL eM4 Single (OCPP)
custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml
hide_table_of_contents: true
---

import DeviceConfig from '@site/src/components/DeviceConfig';
import DeviceFeatures from '@site/src/components/DeviceFeatures';
import SponsorshipRequired from '/docs/_sponsorship_required.mdx';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# ABL eM4 Single (OCPP)

<DeviceFeatures features="mA,rfid,sponsorship" />

<DeviceConfig code={`chargers:
- name: my_charger
type: template
template: ocpp-abl
stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers:
- name: my_charger
type: template
template: ocpp-abl
stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
connecttimeout: 5m # Timeout for the registration of the charging point, optional
meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />

## Template Parameter `ocpp-abl`

| Name | Explanation | Value | Optional |
|-----------|-------------|-------|----------|
| Station ID<br/>`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://&lt;evcc-address&gt;:8887/&lt;stationid&gt;. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no |
| Connector number<br/>`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no |
| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected<br/>`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no |
| Identifier used for authentication of external transactions (RemoteStartTransaction)<br/>`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no |
| Timeout for the registration of the charging point<br/>`connecttimeout` | | Standard: `5m` | no |
| Transmission interval of meter values (MeterValueSampleInterval)<br/>`meterinterval` | | Standard: `10s` | no |
| Manual specification of the meter values to be configured (MeterValuesSampledData)<br/>`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no |

<SponsorshipRequired />

46 changes: 46 additions & 0 deletions docs/devices-next/chargers/abl-em4-single-sbcx.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: ABL eM4 Single (SBCx)
custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml
hide_table_of_contents: true
---

import DeviceConfig from '@site/src/components/DeviceConfig';
import DeviceFeatures from '@site/src/components/DeviceFeatures';
import SponsorshipRequired from '/docs/_sponsorship_required.mdx';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# ABL eM4 Single (SBCx)

<DeviceFeatures features="mA,sponsorship" />

<DeviceConfig code={`chargers:
- name: my_charger
type: template
template: abl-em4

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port`} advanced={`chargers:
- name: my_charger
type: template
template: abl-em4

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
connector: 1 # Loadpoint (if >1 loadpoint), optional`} />

## Template Parameter `abl-em4`

| Name | Explanation | Value | Optional |
|-----------|-------------|-------|----------|
| `modbus` | | Auswahl: `tcpip` | no |
| Loadpoint (if &gt;1 loadpoint)<br/>`connector` | | Standard: `1` | no |

<SponsorshipRequired />

46 changes: 46 additions & 0 deletions docs/devices-next/chargers/abl-em4-twin-ocpp.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: ABL eM4 Twin (OCPP)
custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/ocpp-abl.yaml
hide_table_of_contents: true
---

import DeviceConfig from '@site/src/components/DeviceConfig';
import DeviceFeatures from '@site/src/components/DeviceFeatures';
import SponsorshipRequired from '/docs/_sponsorship_required.mdx';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# ABL eM4 Twin (OCPP)

<DeviceFeatures features="mA,rfid,sponsorship" />

<DeviceConfig code={`chargers:
- name: my_charger
type: template
template: ocpp-abl
stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)`} advanced={`chargers:
- name: my_charger
type: template
template: ocpp-abl
stationid: EVB-P12354 # Station ID, Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
connecttimeout: 5m # Timeout for the registration of the charging point, optional
meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />

## Template Parameter `ocpp-abl`

| Name | Explanation | Value | Optional |
|-----------|-------------|-------|----------|
| Station ID<br/>`stationid` | Station ID of the charging point. Only required if multiple OCPP charging stations are set up to assign them correctly. A single OCPP charging station can also be automatically assigned. Note: In exceptional cases, it may be necessary to manually append this ID to the OCPP URL of the charging station in the form ws://&lt;evcc-address&gt;:8887/&lt;stationid&gt;. Most charging stations automatically add the ID internally. | Beispiel: `EVB-P12354` | no |
| Connector number<br/>`connector` | For charging stations with multiple connectors. Counting starts at 1 for the first connector. | Standard: `1` | no |
| Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected<br/>`remotestart` | Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! | | no |
| Identifier used for authentication of external transactions (RemoteStartTransaction)<br/>`idtag` | This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. | Beispiel: `evcc` | no |
| Timeout for the registration of the charging point<br/>`connecttimeout` | | Standard: `5m` | no |
| Transmission interval of meter values (MeterValueSampleInterval)<br/>`meterinterval` | | Standard: `10s` | no |
| Manual specification of the meter values to be configured (MeterValuesSampledData)<br/>`metervalues` | | Beispiel: `Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage` | no |

<SponsorshipRequired />

46 changes: 46 additions & 0 deletions docs/devices-next/chargers/abl-em4-twin-sbcx.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: ABL eM4 Twin (SBCx)
custom_edit_url: https://github.com/evcc-io/evcc/blob/master/templates/definition/charger/abl-em4.yaml
hide_table_of_contents: true
---

import DeviceConfig from '@site/src/components/DeviceConfig';
import DeviceFeatures from '@site/src/components/DeviceFeatures';
import SponsorshipRequired from '/docs/_sponsorship_required.mdx';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# ABL eM4 Twin (SBCx)

<DeviceFeatures features="mA,sponsorship" />

<DeviceConfig code={`chargers:
- name: my_charger
type: template
template: abl-em4

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port`} advanced={`chargers:
- name: my_charger
type: template
template: abl-em4

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
connector: 1 # Loadpoint (if >1 loadpoint), optional`} />

## Template Parameter `abl-em4`

| Name | Explanation | Value | Optional |
|-----------|-------------|-------|----------|
| `modbus` | | Auswahl: `tcpip` | no |
| Loadpoint (if &gt;1 loadpoint)<br/>`connector` | | Standard: `1` | no |

<SponsorshipRequired />

Loading