The Uconnect^® Kona API provide 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 Kona.

A description of the Kona API can be found in the Kona API Specification.

As shown in the Logical Diagram below a HU Application can request vehicle CAN data such as vehicle speed or engine RPMs by using the Kona sensor API found in the Kona API Specification. The Kona 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 case the V850 in the HU acts as the CAN interface.

 

 

Top

The VP4R logical diagram shows how the Kona API are implemented using a JVM, Java Virtual Machine.

The JamaicaVM is a Java Virtual Machine (JVM) optimized to run on a micro processor. The JamaicaVM contains Java Applications that implement the Java Xlet interface and use the Kona Interface to communicate through the HU's Message Queue to the Native Firmware and Vehicle Components as well as the Application Managment System (AMS) that is also in the JamaicaVM. AMS performs many of the application management functions such as verifying application signatures, installing applications, starting and stopping applications.

The Native Firmware is the HU supplier's software that runs the HU. The Native Firmware is capable if interfacing with the many native services running on the HU. Each of these services is responsbile for communication with the various vehicle components. As the Native Firmware many not be written in Java a JNI interface is present to allow communication with the JamaicaVM.

The Vehicle Components are the physical HU and vehicle hardware components.

 

 

Top

The tech stack view shows how Kona fits into the head unit software.

Top