driver takeover
This topic is unavailable for Lexus vehicles.
Description
Driver Intervention signals and determination of Takeover Status. As well as safety cross checks of associated signals.
Field | datatype | Description |
---|---|---|
utime | string | Best estimate of when this message is from, host clock in UTC |
primaryChannelIntervention | integer | Takeover determined from a primary channel (0 or 1) |
secondaryChannelIntervention | integer | For internal use only : Takeover determined from secondary channel (0 or 1) |
adnDetectedTakeover | integer | For internal use only : Takeover determined from above two channel interventions (0 or 1) |
adnModeCommand | integer | For internal use only: Takeover determined from interventions |
mayIntervention | boolean | In summary, mayIntervention says if there was a driver takeover based on the input from adnDetectedTakeover and ChannelInterventions |
vehicle | string | unique vehicle name the data is associated to. |
topic | string | type of telemetry data |
Topic/channel string
For Realtime API
Pass the comma seperated topic name as a query param
/.vehicle.{vehiclename}.DRIVER_TAKEOVER
For Batch API - TBD
To access the Batch API, you need to include the vehicle name and topic name as path parameters in the URL.
/vehicles/{vehiclename}/topics/DRIVER_TAKEOVER
JSON Output
Order of fields might differ
{
"adnDetectedTakeover": 1,
"adnModeCommand": 1,
"mayIntervention": true,
"primaryChannelIntervention": 1,
"secondaryChannelIntervention": 1,
"topic": "DRIVER_TAKEOVER",
"utime": "1683641886485037",
"vehicle": "vehiclename"
}