Page History

• Vehicle.Cabin.Seat.Row1.DriverSide

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)

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:
  datatype: uint8[]
  type: attribute
  default: [2, 3]

Based on the Seat branch definition:

Seat:
  type: branch
  instances:
    - Row[1,2]
    - ["DriverSide","Middle","PassengerSide"]

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?