This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
FrontMiddle
|
|
| Full qualified VSS Path: |
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle |
| Description: |
Properties related to a particular charging port available in the vehicle. |
| Comment: |
If a vehicle has a single charging port, then use the instance AnyPosition. |
Navigation
flowchart LR
Vehicle-->Powertrain
Powertrain-->TractionBattery
TractionBattery-->Charging
Charging-->ChargingPort
ChargingPort-->FrontMiddle
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle is d5b0b57da3fa57eb847f5f9a828688f5
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1 - IsChargingCableConnected
|
|
| Full qualified VSS Path: |
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected |
| Description: |
Indicates whether a charging cable is physically connected to a particular charging port or not. |
Navigation
flowchart LR
Vehicle-->Powertrain
Powertrain-->TractionBattery
TractionBattery-->Charging
Charging-->ChargingPort
ChargingPort-->FrontMiddle
FrontMiddle-->IsChargingCableConnected
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected
[get] OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected is a Sensor.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected is 6c1c71bf0be25246a98bdc80ebcb2446
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2 - IsChargingCableLocked
|
|
| Full qualified VSS Path: |
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked |
| Description: |
Is charging cable locked to prevent removal. |
| Comment: |
Locking of charging cable can be used to prevent unintentional removing during charging. |
Navigation
flowchart LR
Vehicle-->Powertrain
Powertrain-->TractionBattery
TractionBattery-->Charging
Charging-->ChargingPort
ChargingPort-->FrontMiddle
FrontMiddle-->IsChargingCableLocked
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked
[get] OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked is an Actuator.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked is bb1158a3adc95f7ba5efc8ee3b78975b
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3 - IsFlapOpen
|
|
| Full qualified VSS Path: |
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen |
| Description: |
Status of the charging port flap(s). |
| Comment: |
True = at least one flap of this port is open, False = All flaps of this port are closed. |
Navigation
flowchart LR
Vehicle-->Powertrain
Powertrain-->TractionBattery
TractionBattery-->Charging
Charging-->ChargingPort
ChargingPort-->FrontMiddle
FrontMiddle-->IsFlapOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen
[get] OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen is an Actuator.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen is 597e986207e45d18bfa10c84b5cddbe8
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4 - SupportedInletTypes
|
|
| Full qualified VSS Path: |
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes |
| Description: |
A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234. |
| Comment: |
A vehicle may have multiple charging ports. IEC_TYPE_1_AC refers to Type 1 as defined in IEC 62196-2. Also known as Yazaki or J1772 connector. IEC_TYPE_2_AC refers to Type 2 as defined in IEC 62196-2. Also known as Mennekes connector. IEC_TYPE_3_AC refers to Type 3 as defined in IEC 62196-2. Also known as Scame connector. IEC_TYPE_4_DC refers to AA configuration as defined in IEC 62196-3. Also known as Type 4 or CHAdeMO connector. IEC_TYPE_1_CCS_DC refers to EE Configuration as defined in IEC 62196-3. Also known as CCS1 or Combo1 connector. IEC_TYPE_2_CCS_DC refers to FF Configuration as defined in IEC 62196-3. Also known as CCS2 or Combo2 connector. TESLA_ROADSTER, TESLA_HPWC (High Power Wall Connector) and TESLA_SUPERCHARGER refer to non-standardized charging ports/methods used by Tesla. GBT_AC refers to connector specified in GB/T 20234.2. GBT_DC refers to connector specified in GB/T 20234.3. Also specified as BB Configuration in IEC 62196-3. OTHER shall be used for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196. |
Navigation
flowchart LR
Vehicle-->Powertrain
Powertrain-->TractionBattery
TractionBattery-->Charging
Charging-->ChargingPort
ChargingPort-->FrontMiddle
FrontMiddle-->SupportedInletTypes
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes
[get] OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
|
|
|
| Path |
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes |
VSS: Addressing nodes |
| Data type |
string[] |
VSS: Datatypes |
| Allowed values |
['IEC_TYPE_1_AC', 'IEC_TYPE_2_AC', 'IEC_TYPE_3_AC', 'IEC_TYPE_4_DC', 'IEC_TYPE_1_CCS_DC', 'IEC_TYPE_2_CCS_DC', 'TESLA_ROADSTER', 'TESLA_HPWC', 'TESLA_SUPERCHARGER', 'GBT_AC', 'GBT_DC', 'OTHER'] |
VSS: Specifying allowed values |
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes is an Attribute.
The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes is 59bf1b00e04850f4a37a3cd22ae3d52e
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.