Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/read generic network signal data clarification #170

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/Common/Enums/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -853,6 +853,7 @@
|VEHICLEDATA_ENGINEOILLIFE|28||
|VEHICLEDATA_ELECTRONICPARKBRAKESTATUS|29||
|VEHICLEDATA_CLOUDAPPVEHICLEID|30| Parameter used by cloud apps or the policy server to identify a head unit|
|VEHICLEDATA_OEM_CUSTOM_DATA|31||

### VideoStreamingProtocol

Expand Down
5 changes: 5 additions & 0 deletions docs/VehicleInfo/SubscribeVehicleData/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,11 @@ Purpose

HMI may send SubscribeVehicleData response only for ROOT level items.

!!! note

For OEM specific custom vehicle data items, `oemCustomDataType` will contain a type of OEM specific vehicle data (from schema), and `dataType` will be `VEHICLEDATA_OEM_CUSTOM_DATA`.
For vehicle data items from RPCSpec, `oemCustomDataType` will be omitted, and `dataType` will contain appropriate data type from `VehicleDataType` enum.

!!!

#### Parameters
Expand Down
7 changes: 7 additions & 0 deletions docs/VehicleInfo/UnsubscribeVehicleData/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,13 @@ Purpose

HMI may send SubscribeVehicleData response only for ROOT level items.

!!!

!!! note

For OEM specific custom vehicle data items, `oemCustomDataType` will contain a type of OEM specific vehicle data (from schema), and `dataType` will be `VEHICLEDATA_OEM_CUSTOM_DATA`.
For vehicle data items from RPCSpec, `oemCustomDataType` will be omitted, and `dataType` will contain appropriate data type from `VehicleDataType` enum.

!!!
#### Parameters

Expand Down