This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

ElectricMotor
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor
Description: Electric Motor specific data.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor is 1ade64f6b0d05f6c9340e7a667555ae2

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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 - CoolantTemperature
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.CoolantTemperature
Description: Motor coolant temperature (if applicable).
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->CoolantTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.CoolantTemperature
[get]  OK
Vehicle.Powertrain.ElectricMotor.CoolantTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.CoolantTemperature 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.CoolantTemperature

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.CoolantTemperature VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit celsius VSS: Units
Label degree celsius
Description Temperature measured in degree celsius VSS: Sensors & Actuators
Domain temperature

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.CoolantTemperature is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.CoolantTemperature is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.CoolantTemperature is 3c5ea8c7700956518f2ae7a2a0f34f1c

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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 - MaxRegenTorque
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.MaxRegenTorque
Description: Peak regen/brake torque, in newton meter, that the motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxRegenTorque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.MaxRegenTorque
[get]  OK
Vehicle.Powertrain.ElectricMotor.MaxRegenTorque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.MaxRegenTorque 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.MaxRegenTorque

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.MaxRegenTorque VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit Nm VSS: Units
Label newton meter
Description Torque measured in newton meters VSS: Sensors & Actuators
Domain torque
Default value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxRegenTorque is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxRegenTorque is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.MaxRegenTorque is 0e5190c2517b55aa80fcb9bf698e02d6

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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 - Power
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.Power
Description: Current motor power output. Negative values indicate regen mode.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Power

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.Power
[get]  OK
Vehicle.Powertrain.ElectricMotor.Power: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.Power 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.Power

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.Power VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit kW VSS: Units
Label kilowatt
Description Power measured in kilowatts VSS: Sensors & Actuators
Domain power

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.Power is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Power is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.Power is 46b86286fba059349a733fed9a0e3232

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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 - Speed
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.Speed
Description: Motor rotational speed measured as rotations per minute. Negative values indicate reverse driving mode.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Speed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.Speed
[get]  OK
Vehicle.Powertrain.ElectricMotor.Speed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.Speed 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.Speed

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.Speed VSS: Addressing nodes
Data type int32 VSS: Datatypes
Unit rpm VSS: Units
Label revolutions per minute
Description Rotational speed measured in revolutions per minute VSS: Sensors & Actuators
Domain rotational speed

Note: The int32 datatype is a signed 32-bit integer which technically allows values between -2147483648 and 2147483647 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.Speed is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Speed is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.Speed is ca961aa6ca435095a89f9d404a5d849d

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.

5 - Temperature
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.Temperature
Description: Motor temperature.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Temperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.Temperature
[get]  OK
Vehicle.Powertrain.ElectricMotor.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.Temperature 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.Temperature

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.Temperature VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit celsius VSS: Units
Label degree celsius
Description Temperature measured in degree celsius VSS: Sensors & Actuators
Domain temperature

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.Temperature is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Temperature is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.Temperature is 1b7c15e5341052139995bfacea2c05b2

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.

6 - Torque
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.Torque
Description: Current motor torque. Negative values indicate regen mode.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Torque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.Torque
[get]  OK
Vehicle.Powertrain.ElectricMotor.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.Torque 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.Torque

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.Torque VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units
Label newton meter
Description Torque measured in newton meters VSS: Sensors & Actuators
Domain torque

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.Torque is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Torque is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.Torque is aceffe768ddf5b828fff0975349d2433

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.

7 - EngineCode
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.EngineCode
Description: Engine code designation, as specified by vehicle manufacturer.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->EngineCode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.EngineCode
[get]  OK
Vehicle.Powertrain.ElectricMotor.EngineCode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.EngineCode Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.EngineCode

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.EngineCode VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCode is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCode is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCode is e4102a5142ed501495e5edafd3d36dfb

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.

8 - MaxPower
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.MaxPower
Description: Peak power, in kilowatts, that motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxPower

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.MaxPower
[get]  OK
Vehicle.Powertrain.ElectricMotor.MaxPower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.MaxPower 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.MaxPower

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.MaxPower VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit kW VSS: Units
Label kilowatt
Description Power measured in kilowatts VSS: Sensors & Actuators
Domain power
Default value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxPower is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxPower is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.MaxPower is 825ec7911ee958abb199b9f7903df3a6

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.

9 - MaxRegenPower
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.MaxRegenPower
Description: Peak regen/brake power, in kilowatts, that motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxRegenPower

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.MaxRegenPower
[get]  OK
Vehicle.Powertrain.ElectricMotor.MaxRegenPower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.MaxRegenPower 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.MaxRegenPower

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.MaxRegenPower VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit kW VSS: Units
Label kilowatt
Description Power measured in kilowatts VSS: Sensors & Actuators
Domain power
Default value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxRegenPower is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxRegenPower is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.MaxRegenPower is 7f2cb2650ba95485b7156ffe76e27366

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.

10 - MaxTorque
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.MaxTorque
Description: Peak power, in newton meter, that the motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxTorque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.ElectricMotor.MaxTorque
[get]  OK
Vehicle.Powertrain.ElectricMotor.MaxTorque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.MaxTorque 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Powertrain.ElectricMotor.MaxTorque

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.MaxTorque VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit Nm VSS: Units
Label newton meter
Description Torque measured in newton meters VSS: Sensors & Actuators
Domain torque
Default value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxTorque is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxTorque is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Powertrain.ElectricMotor.MaxTorque is cf31eabcde5151f589e9b0f7a6090512

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

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.