Service Integration

Services can make sure, that when you write a VSS data point, something is actually happening. Eclipse Velocitas has an example seat or hvac service. If your Vehicle App makes use of e.g. Vehicle.Cabin.Seat.Row1.Pos1.Position or other seat/hvac specific data points you are in for some real action. To learn more, visit Vehicle Services .

Our maintained devenv-runtimes package ( Velocitas Lifecycle Management ) comes with the support of adding further Vehicle Services to the runtime.json of a package. More information here . (A general vehicle mock service is also coming soon!)

Modify existing services

For more advanced usage you can also try to modify existing services. Check out the seat service for example, modify it and integrate it into your Vehicle App repository.

Create your own services

If you want to create your own service the KUKSA.VAL Services repository contains examples illustrating how such kind of vehicle services can be built. You need to write an application that talks to KUKSA.VAL listening to changes of a target value of some VSS data point and then do whatever you want. You can achieve this by using the KUKSA.VAL gRPC API with any programming language of your choice (learn more about gRPC ).

Mock Service and Mock Service Integration

The Vehicle Mock Service is a dummy service allowing to control all specified actuator- and sensor-signals via a configuration file. These configuration files are expressed in a Python-based domain-specific language (DSL). The default behavior is predefined in mock.py

The Mock Service is already integrated in all our Vehicle Runtimes . To be able to configure it, you need to add a custom mock.py in the root of your Vehicle App Project. The Mock Service Container will pick it up automatically.