As shown in the Logical Diagram the Uconnect^® Vehicle Interface shown as Kona provides an interface layer between applications running on the Telematics Unit (TU) or Head Unit (HU) and the Vehicle Components that have been made accessible to the interface.

For example a HU Application can request vehicle CAN data such as vehicle speed or engine RPMs by using the sensor API located in the sensor package. The sensor API are responsible for using the Firmware Service Interface to communicate with the CAN Service. The CAN Service is responsible for retrieving CAN data (vehicle speed, engine RPM, etc.) from the vehicle. In this diagram the V850 in the HU acts as the CAN interface.

Logical Diagram

Specification

The Vehicle Interface specification for R1 provides descriptions of the API behaviors and in many cases sample code. Each specification release contains a description section showing what API changed for each release, a list of the permissions expected by an API, and a change Log providing a summary of API changes. You can find this information in the locations shown in the images below.

Current specification example.

 

Version Information

The Version Information page shows what interfaces have changed in each Vehicle Interface version and the change request associated with those changes.

Links are also provided on this page so you can download a specific API Spec version.

Top