kuksa-val-server is a reature rich in-vehicle data server written in C++ providing authorized access to vehicle data.
Check System Architecture for an overview how KUKSA.val can be used and deployed in a modern Software Defined Vehicle.
kuksa-val-server serves signals described using the COVESA VSS data model. VSS data is provided to applications using a variant based on the W3C VISS Interface or GRPC. KUKSA.val supports VISS V1 https://www.w3.org/TR/vehicle-information-service/ and extensions as well as parts of the upcomming VISS2 standard (Gen2 Core, Gen2 Transport), that are applicable to in-vehicle VSS servers.
See Supported Protocol for a detailled overview of the supported VISS feature.
- Websocket interface, TLS-secured or plain
- Fine-grained authorisation based on JSON Webtokens (RFC 7519)
- Built-in MQTT publisher
- Python viss client to interactively explore and modify the VISS data points and data structure
- Multiple example apps in different programming languages to communicate with different frameworks
- Multiple feeders to provide vehicle data for the
kuksa.valserver - Support most of data types, which is specified in COVESA VSS data model.
If you prefer to build kuksa.val yourself skip to Building KUKSA.val.
Download a current docker image from one of our CI server:
- https://ci.eclipse.org/kuksa/job/kuksa.val/job/master/
- https://kuksaval.northeurope.cloudapp.azure.com/job/kuksaval-upstream/
The container images should work with any OCI compliant container runtime, in this document we assume you are using docker
Import the docker image
docker load -i kuksa-val-b3084b9-amd64.tar.xz
Your build tag may vary, and for ARM machines you need to choose an arm64 images.
Prepare an empty directory $HOME/kuksaval.config. Run the docker image using the tag reported by docker load:
docker run -it --rm -v $HOME/kuksaval.config:/config -p 127.0.0.1:8090:8090 -e LOG_LEVEL=ALL amd64/kuksa-val:b3084b9Alternatively you can run a released version directly from the ghcr.io registry, i.e.
docker run -it --rm -v $HOME/kuksaval.config:/config -p 127.0.0.1:8090:8090 -e LOG_LEVEL=ALL ghcr.io/eclipse/kuksa.val/kuksa-val:0.2.1-amd64
More information on using the docker images can be found here.
To learn, how to build your own docker image see doc/build-docker.md.
If this is succesful you can skip to using kuksa.val.
First you need to fetch the source. ;ake sure you also get the needed submodules, e.g. by using the --recursive flag
git clone --recursive https://github.com/eclipse/kuksa.val.git
If you are using Visual Studio Code, and have a running version of Docker on your computer, KUKSA.val provides a devcontainer configuration. Simply go to the VSCode command palette and use Remote-Containers: Open Folder in Container... to open the cloned KUKSA.val folder, or, if you already opened the folder in your local VSCode instance, choose Remote-Containers: Reopen in Container...
Note: If you are using Docker Desktop or Rancher Desktop on a Mac OS, by default the VM used to run Dockers does not contain enough RAM to build KUKSA.val. Increase the RAM allocation for Docker to at least 4 GB in the Docker Desktop or Rancher Desktop preferences.
Once the devcontainer is running you can continue with compiling.
First install the required packages. On Ubuntu 20.04 this can be achieved by
sudo apt install cmake build-essential libssl-dev libmosquitto-dev
Note: If you use cmake >= 3.14, you do not need to install boost on your system. cmake will download the required boost for building. Otherwise you need install the boost==1.75 on the system.
Create a build folder inside the kuksa-val-server folder and execute cmake
cd kuksa-val-server
mkdir build
cd build
cmake ..If there are any missing dependencies, cmake will tell you. If everythig works fine, execute make
make
(if you have more cores, you can speed up compilation with something like make -j8
Additional information about our cmake setup (in case you need adavanced options or intend to extend it) can be found here.
After you successfully built the kuksa.val server you can run it like this
#assuming you are inside kuksa.val/build directory
cd src
./kuksa-val-server --vss ./vss_release_3.0.json --log-level ALL
Setting log level to ALL gives you some more information about what is going on.
You can also edit config.ini file to configure kuksa val server. This file will be copied to the build directory and used als default config,
if no other config file is specified using the command line option -c/--config-file.
For more information check usage.
The easiest way to try kuksa-val-server out, is to use the test client kuksa_viss_client:
pip install kuksa-viss-client
kuksa_viss_client
The jwt tokens for testing can also be found under kuksa_certificates/jwt.
You can also use the provided python sdk to develop your own kuksa.val clients. More details about kuksa_viss_client can be found here.
Additionally, you can use the example apps and feeders to handle vehicle data, interacting with kuksa-val-server.
Aditionally theres exists a experimental gRPC server. The easist way to test the server is the kuksa_viss_grpc_client. To run the client follow these steps:
cd build/src
./kuksa_viss_grpc_client
If you do not know how to use the client:
./kuksa_viss_grpc_client --help