This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Dog Mode

The Dog Mode use case has been derived from the Eclipse Velocitas Dog Mode example and the Eclipse Kuksa.VAL HVAC Service example.

Description

In the Dog Mode use case, an existing vehicle service (such as HVAC for Heating, Ventilation and Air Conditioning) is used for another use case. When a driver enables the dog mode, the vehicle will keep the climate in a status to accomodates the pet while the driver is gone for a few minutes.

The focus on this example is to show how an additional application can reuse existing functionality for new use cases. The vehicle service being used does not need to be adapted for the new use case. The new use case is deployed as an additional functionality, separated from the rest of the existing system.

Architecture Overview

Leda Dog Mode Use Case

  • Cloud or mobile trigger: not part of the Leda image, but can be simulated by issueing MQTT messages
  • Eclipse Velocitas - Vehicle Application: Dog Mode (to be deployed by user as part of the Velocitas tutorial)
  • Eclipse Kuksa.VAL - Example Service: HVAC Service (pre-installed)
  • Eclipse Kuksa.VAL - Data Broker (pre-installed)

Getting started

  1. Follow the Velocitas tutorial: build and deploy your clone of the dog mode example

  2. Download and run the Leda quickstart image

  3. Deploy the application to the container runtime, either manually by using kanto-cm create or by providing a deployment descriptor in /var/containers/manifests. An example deployment descriptor can be found in meta-leda-components. Details on the deployment can be found in Leda Vehicle Applications

  4. Ensure the databroker and the service containers are running and you know how to check their log files

  5. Monitor vehicle data: mosquitto_sub -t dogmode/display

  6. Enable dog mode by using the databroker-cli

     connect
 set Vehicle.Cabin.DogMode 1