search

COVESA / vehicle_signal_specification

Vehicle Signal Specification - standardized way to describe automotive data
Mozilla Public License 2.0
307 stars 157 forks source link

Update screen mirroring in Infotainment.vspec #699

Closed spshin3 closed 2 months ago

spshin3 commented 6 months ago

Resolve "erik's comment" and a DCO problem from PR #686 .

erikbosch commented 6 months ago

This PR addresses screen mirroring, we have since before smartphone projection, see below.

I am no expert in this area, but what is the difference? I.e. what use-cases and technologies are supposed to be covered by the screen mirroring signals? Just want to make sure that we do not duplicate functionality. Is it intended for Chromecast and similar "one way" technologies? (Android Auto, Apple Carplay and MirrorLink already mentioned in projection signals).

If it concerns different but similar technologies that cannot be used in parallel we may continue just extending the SmartphoneProjection branch as needed


SmartphoneProjection:
  type: branch
  description: All smartphone projection actions.

SmartphoneProjection.Active:
  datatype: string
  type: actuator
  allowed: [ 'NONE', 'ACTIVE',  'INACTIVE' ]
  description: Projection activation info.
  comment: NONE indicates that projection is not supported.

SmartphoneProjection.Source:
  datatype: string
  type: actuator
  allowed: ['USB', 'BLUETOOTH', 'WIFI']
  description: Connectivity source selected for projection.

SmartphoneProjection.SupportedMode:
  datatype: string[]
  type: attribute
  allowed: [ 'ANDROID_AUTO', 'APPLE_CARPLAY', 'MIRROR_LINK', 'OTHER' ]
  description: Supportable list for projection.
erikbosch commented 5 months ago

@spshin3 - I converted this PR to a draft as I see that some rework is needed. For example calrifying the different between "SmartphoneScreenMirroring" and "SmartphoneProjection". Will you have time to continue work on this PR in the next weeks?