JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
Table of Contents
Notes from Kickoff
Below is the start of translating the uServices definitions of seating capabilities to a technology neutral tabular format as agreed in our kick-off meeting on October 18th. Please take a look, iterate, comment and let me know if you have questions Paul Boyes
Agreed by Group:
- Start a position D in architecture - see architecture diagram below
- Safety considerations to be noted but not exhaustively
Terminology Alignment (WIP)
Aligning on information types is critical.
Notes:
- Seating accounts for over 1/5th of VSS.yaml. This is due to the many facets of seating and the number of instances.
- Seat Configuration:
- Vehicle.Cabin.SeatRowCount - number of rows - defaults to 2
- Vehicle.Cabin.SeatPosCount - array of number of seats per row - defaults to 2,3 which is 2 in row 1 and 3 in row 2
- Even though the default says only 2 seats in row 1, generated (yaml) it has Driver, Middle and Passenger
- Related:
- Vehicle.VehicleIdentification.VehicleSeatingCapacity - provides seating capacity vehicle
- Vehicle.Cabin.DriverPosition - driver left, middle or right
Seat Identity
Identifying a specific seat within a vehicle. This is based on location within the vehicle.
| Information Type | Values (per GM uServices) | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / Mapping |
|---|---|---|---|---|---|---|---|---|
Seat Seat identity for 3 rows with 3 seats per row, front to back (looking towards front of vehicle from within the vehicle) |
| row1_driver |
Note: Driver seat typically has more functions than others. Typical ECUs are DriverSeatModule and PassengerSeat Module, that are picked up as is (SW content & interfaces) and moved from left to right of vehicle based on region). This is done to reduce variant complexity management and vehicle network & Interface configuration Vehicle.Cabin.Seat.DriverPosition sets the DriverSide in VSS. It is allows ['LEFT', 'MIDDLE', 'RIGHT'] . In uServices, it does not appear Driver Position or similar is spelled out. Decision: For Seating Capabilities, not how it is done internally to your organization, can we align around VSS Vehicle.Cabin.Seat? Stupid Question Erik Jaegervall bear with me : How does Vehicle.Cabin.SeatPosCount work with what is actually generated for vss.yaml (the instances) and/or how you use? For instance, in Cabin.vspec the default is SeatPosCount: Based on the Seat branch definition: Seat: The following instances are generated per row: Vehice.Cabin.Seat.Row1.DriverSide, Vehice.Cabin.Seat.Row1.Middle, Vehice.Cabin.Seat.Row1.PassengerSide It is implied or just well known that in this case you just don't use Middle? What if SeatPosition is [1,1] ... DriverSide and PassengerSide or the same? What if it is your instances are ["DriverSide","Middle1","Middle2"PassengerSide"] and your SeatPosition is [3,4]? I guess it is implied, industry knowledge or incumbent on the implementor to spell it out? Right? Comment from Erik Jaegervall 2024-12-18: In general - how to indicate whether a VSS signal or a seat instance actually exists is up to the implementation. It might be based on that you do changes to your in VSS (for example with The There have been discussions if the instance-part should be removed from the VSS-spec and especially from the full dot-notated paths, as that is rather deployment information. That "core" VSS should specify that there can be multiple seats, and possibly that row/pos are attributes that seat can have, but specifying the actual instances is rather for the implementation. That would be a bit similar to the Android zone concept. | TBD | ||||
|
| |||||||
| row1_driver |
| ||||||
|
| |||||||
|
| |||||||
|
| |||||||
|
| |||||||
|
| |||||||
|
|
Seat Identity Illustrations
tbd
Seat Components
Seat components that are movable or controllable, electrically driven.
| Information Type | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / mapping | Notes |
|---|---|---|---|---|---|---|---|---|---|
Seat Component Moveable Seating Component (Electrically Driven) | Complete seat | All | Added |
| |||||
Lumbar
| 5
|
| SEAT_LUMBAR_VERTICAL SEAT_LUMBAR_FORE_AFT | ||||||
Cushion Side Bolster | 12
| Pictures would be good focus must be on Mechatronic components | Right and Left Back (upper) bolsters | Inflaation level 0-100% | SEAT_CUSHION_SIDE_SUPPORT | ||||
Backrest Side Bolster | 11
| Right and Left Cushion (lower) bolsters | Inflation level 0-100% |
| SEAT_LUMBAR_SIDE_SUPPORT | ||||
Upper Shoulder (fwd/backward) | 9 | ||||||||
Backrest (was Cushion Front) | 10 |
| |||||||
Cushion Extension | 13 Blue thing | Thigh Extension? | Either works | ||||||
Headrest | 4 |
| |||||||
Airbag |
| ||||||||
Neck Scarf (fan) | 6 | ||||||||
Seat Belt (height) |
Seat Component Illustrations (maintained on Miro)
Bolsters and Bladders:
Seat & Component Movements or Positions
Words describing control parameters or changeable properties related to movement or position.
| Information Type | Definition | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / Mapping | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Direction | Direction of seat or component movement |
| Needs Clarification. Percent of total? clicks? x, y, z axis values? | fore | depends on the component | Applied by seat or component like:
| Is Fold a direction? Team agreed it is a capability | |||
| aft | depends on the component | ||||||||
| depends on the component | Applied by Seat or Component like:
| Applied by seat or component like:
| |||||||
| depends on the component | |||||||||
| increase | depends on the component | Applied by inflatable Component like:
| |||||||
| decrease | depends on the component | ||||||||
| angles | depends on the component | Applied by Component like:
degrees - Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline.
degrees - Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward. | |||||||
| ||||||||||
| Position | position on horizontal plane (x-axis) or vertical plane (z-axis) of seat or component | needs clarification Position vs Direction | Should height be separate? Is y-axis needed? |
Seat position on vehicle x-axis. mm - Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.
mm - Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported. | AI: align what position means | |||||
| Tilt Angle | tilt angle of seat or component (also known as recline) | duplicate to Tilt / Recline (angles) | duplicate to Tilt / Recline (angles) under "direction" above |
degrees - Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline.
degrees - Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward. |
Seat Heating and Cooling
Words describing control parameters or changeable properties related to seat heating and cooling.
| Information Type | Definition | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Mapping | Android Alignment / mapping | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
Temperature |
| |||||||||
|
| |||||||||
| ||||||||||
| ||||||||||
| ||||||||||
| ||||||||||
| Fan Speed |
| |||||||||
| ||||||||||
| ||||||||||
| ||||||||||
| ||||||||||
| ||||||||||
|
Seat Massage
| Information Type | Definition | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / Mapping | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Massage Capability | Is the seat capable of providing massage. | yes/no or true/false | we need a general discover mechanism | Overlaps with with Seat Massage Type | ||||||
| Massage Status | On/Off | Overlaps with Seat Massage Type |
| |||||||
| Massage Types | Available massage types for a specific seat, including none. | Values will vary by OEM, therefore, need a capability to determine types per seat. | Massage Patterns | |||||||
| Seat Massage Type |
| Need discovery capability as will vary by seat. | ||||||||
| Massage Intensity | Intensity of massage | ?? | 1-5? | Vehicle.Cabin.Seat.Row1.PassengerSide.Massage - Seat massage level. 0 = off. 100 = max massage. |
Seat Haptics
Haptics are seat or component vibrations used to alert the driver or provide feedback. Used by ADAS.
| Information Type | Definition | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / Mapping |
|---|---|---|---|---|---|---|---|---|---|
| Delay Between Pulses | internal calibration at the moment, based on the requestor | ||||||||
| Haptic Pulses |
Seat Occupancy and Safety
| Information Type | Definition | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / Mapping | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Seat Occupancy Status |
| Vehicle.Cabin.Seat.Row1.Middle.IsOccupied - boolean - is or is not occupied. No Unkown. | ||||||||
| ||||||||||
| ||||||||||
| Seat Occupant ID | ?? | What is this? |
| |||||||
| Child seat |
| added | ||||||||
| Seat Belt Status |
| Vehicle.Cabin.Seat.Row1.PassengerSide.IsBelted - boolean - is or is not belted/fastened Related:
| ||||||||
|
Other Seat Information
| Information Type | Definition | Values | Illustration # | BMW | Ford | GM | Volvo Cars | VSS Alignment / Mapping | Android Alignment / Mapping | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Side of Seat | Side of a specific Seat |
| duplicate to "SEATS" | |||||||
| Seat Switch |
|
Seat Capability Alignment (WIP)
Column Definitions
- Capability: A concise name for the capability
- Description: A brief description of the capability and what it does and enables
- Inputs: What data (must align with VSS) is required by the capability
- Outputs: What data (must align with VSS) is output by the capability
- Dependencies: Other capabilities, processes, or systems the capability depends on
- Assumptions/Constraints: Any assumptions or limitations that should be considered
- Considerations: Including safety, security, performance, regulations, diagnostics…
- Location in Architecture: For context where does it sit in an architecture
General questions regarding API invocation:
- Can we use "actuate with commands, report with signals" as a general strategy?
- Do we use transaction IDs to tie commands to output signals/results?
Seat Movement and Position
Capability | Description | Inputs | Outputs | Dependencies | Assumptions /Constraints | VSS Examples / Mapping | Android Examples / Mapping | Notes |
| Movement & Position - Control | ||||||||
| Move Seat Incrementally | Move the identified seat in the specified direction. When a user commands a seat in a certain direction, it will incrementally move in that direction. |
|
| One request/trigger moves one increment. | N/A | |||
| Move Seat to Specified Position | Set the seat position for the identified seat. This is entire seat position forward, back, up down. |
|
|
Seat position on vehicle x-axis. mm - Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.
mm - Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported. | What is the position definition? ISO 8895 What is status? Position Status. | |||
| Move Seat Component Incrementally | Move the identified seat and component in the specified direction. When a user commands a seat component in a certain direction, it will incrementally move in that direction until the user ceases their request. |
|
| N/A | Different classes of comportment? Certain directions apply to different components? Need to enumerate the components? Component type? | |||
| Set Seat Component Position Per Seat | Set the seat component position for the identified seat. This is position of the component only. |
|
| Applied by Component and Direction like:
| ||||
| Store Seat Position | Stores current seat and component positions |
| N/A | |||||
| Recall Seat Position | Recall seat and component positions |
| N/A | |||||
| Fold Headrest | Fold or unfold headrest |
| Align with move seat compontent? | |||||
| Fold Seat | Fold or unfold seat |
| Align with move seat component | |||||
| Movement & Position - Status / Data | ||||||||
| Get Seat Position Per Seat | Get the seat position for the identified seat. This is entire seat position. |
|
| |||||
| Get Seat Component Position Per Seat | Get the seat component position for the identified seat. This is position of the component only. |
|
| |||||
| Get Seat Ids / Locations | Provides the list of seats available in "this" Vehicle |
| Array of:
| |||||
Seat Movement Illustrations:
A 
(Seat Height or Seat Up/Down)
B 
Seat Forward/Backward
C 
Seat Recline
D 
Cushion Extension
E 
Cushion Tilt
F 
Headrest Height or Headrest Fwd/Backward
Seat Heating and Cooling
Capability | Description | Inputs | Outputs | Dependencies | Assumptions /Constraints | VSS Examples / Mapping | Android Examples / Mapping | Notes |
| Heating & Cooling - Control | ||||||||
| TBD | ||||||||
| Seat Heating & Cooling - Status / Data | ||||||||
| Get Seat Heating Per Seat | Get the heating mode and level for the identified seat |
|
| |||||
| Get Seat Component Heating Per Seat | Get the heating mode and level for the identified seat and component |
|
| |||||
Seat Massage
Capability | Description | Inputs | Outputs | Dependencies | Assumptions /Constraints | VSS Examples / Mapping | Android Examples / Mapping | Notes |
| Massage - Control Per Seat | ||||||||
| Set Seat Massage Per Seat | Set the massage type and intensity for the identified seat |
|
| It will be difficult to agree on massage types / patterns. So added a capability to determine what massage types or patterns are available per set. | ||||
| Massage - Status / Data Per Seat | ||||||||
| Get Seat Massage Per Seat | Get the massage type and intensity for the identified seat |
|
| |||||
| Get Massage Status | identifies if massage is on or off for specific set(s) |
|
| |||||
| Get Seat Massage Capability | identifies if seats support massage |
|
| |||||
| Get Seat Massage Types (Patterns) | Provides a list of available massage types for a specific seat. May be none. |
|
| Need to consider in what format? Bounded array of string values? | ||||
Seat Haptics
Capability | Description | Inputs | Outputs | Dependencies | Assumptions /Constraints | VSS Examples / Mapping | Android Examples / Mapping | Notes |
| Haptics - Control | ||||||||
| Activate Haptics | Activate seat haptic notification for driver's seat |
| What is a haptic seat? Where does it fit? Use use case to help define. | |||||
| Haptics - Status / Data | ||||||||
Seat Occupancy and Safety
Capability | Description | Inputs | Outputs | Dependencies | Assumptions /Constraints | VSS Examples / Mapping | Android Examples / Mapping | Notes |
| Seat Occupant Safety - Status / Data Per Seat | ||||||||
| Get Seat Occupant Safety Per Seat | Get the occupant safety status for the identified seat |
|
| |||||
| Get Child Seat Status | Allows user to determine if a Child Seat is installed |
|
| |||||
Zonal Architecture for Reference
Overview
Content Tools