├── .devcontainer ├── Dockerfile └── devcontainer.json ├── .github └── workflows │ ├── ci.yml │ └── ocaas.yaml ├── .gitignore ├── .gitmodules ├── .markdownlint.json ├── .ort.yml ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING ├── LICENSE ├── NOTICE.md ├── README.md ├── SECURITY ├── assets ├── icons │ └── logo.svg ├── js │ └── ga.js ├── logo │ ├── color.ai │ ├── eclipse-leda-logo-cropped.png │ ├── eclipse-leda-logo-cropped.xcf │ ├── font.txt │ ├── icon.png │ ├── leda_mew.jpg │ ├── logo.cdr │ ├── logo.pdf │ ├── logo_01_cmyk.ai │ ├── logo_01_cmyk.eps │ ├── logo_01_cmyk.pdf │ ├── logo_01_rgb.ai │ ├── logo_01_rgb.jpg │ ├── logo_01_rgb.png │ ├── logo_02_cmyk.ai │ ├── logo_02_cmyk.eps │ ├── logo_02_cmyk.pdf │ ├── logo_02_rgb.ai │ ├── logo_02_rgb.jpg │ ├── logo_02_rgb.png │ ├── logo_03_cmyk.svg │ └── logo_03_cmyk_cropped.svg └── scss │ └── _variables_project.scss ├── config.toml ├── content └── en │ ├── _index.html │ ├── docs │ ├── __shared │ │ └── usage-overview.md │ ├── _config.yml │ ├── _index.md │ ├── about │ │ ├── _index.md │ │ ├── architecture │ │ │ ├── _index.md │ │ │ ├── leda-arch-highlevel.drawio │ │ │ ├── leda-arch-highlevel.png │ │ │ ├── leda-arch-highlevel.svg │ │ │ ├── leda-arch-overview.drawio │ │ │ ├── leda-arch-overview.png │ │ │ ├── leda-arch-overview.svg │ │ │ ├── leda-arch-reference-implementation.drawio │ │ │ ├── leda-arch-reference-implementation.png │ │ │ ├── leda-arch-reference-implementation.svg │ │ │ ├── leda-build-highlevel.drawio │ │ │ ├── leda-build-highlevel.png │ │ │ ├── leda-build-highlevel.svg │ │ │ ├── leda-deploy-highlevel.drawio │ │ │ ├── leda-deploy-highlevel.png │ │ │ └── leda-deploy-highlevel.svg │ │ ├── features.md │ │ ├── goals.md │ │ ├── releases │ │ │ ├── 0.1.0 │ │ │ │ ├── leda-0.1.0-M1.md │ │ │ │ ├── leda-0.1.0-M2.md │ │ │ │ ├── leda-0.1.0-plan.md │ │ │ │ └── scan-report-web-app_0.1.0-M1.html │ │ │ └── _index.md │ │ └── roadmap.md │ ├── app-deployment │ │ ├── _index.md │ │ ├── carsim │ │ │ ├── _index.md │ │ │ ├── carsim-arch-overview.drawio │ │ │ ├── carsim-arch-overview.png │ │ │ ├── carsim-arch-overview.svg │ │ │ ├── carsim-databroker-cli.png │ │ │ ├── carsim-databroker-cli2.png │ │ │ ├── kantui_carsim.png │ │ │ ├── kantui_driversim.png │ │ │ ├── kinetic.drawio │ │ │ ├── kinetic.png │ │ │ └── kinetic.svg │ │ ├── cloud2device-messages │ │ │ ├── _index.md │ │ │ ├── c2d-architecture-overview.drawio │ │ │ ├── c2d-architecture-overview.png │ │ │ └── sdv-health-connectivity.png │ │ ├── dog-mode │ │ │ ├── _index.md │ │ │ ├── dogmode.drawio │ │ │ └── dogmode.png │ │ ├── kuksa-databroker │ │ │ ├── _index.md │ │ │ ├── custom-vss-mappings │ │ │ │ ├── _index.md │ │ │ │ ├── kuksa-databroker-cli.png │ │ │ │ ├── vss-overlay.drawio │ │ │ │ └── vss-overlay.png │ │ │ └── kuksa-databroker-cli.png │ │ ├── seat-adjuster │ │ │ ├── _index.md │ │ │ ├── architecture-seat-adjuster.md │ │ │ ├── can-seat-adjuster.md │ │ │ ├── deploy-seat-adjuster.md │ │ │ ├── develop-seat-adjuster.md │ │ │ ├── interact-seat-adjuster.md │ │ │ ├── seatadjuster.drawio │ │ │ └── seatadjuster.png │ │ └── velocitas │ │ │ └── _index.md │ ├── build │ │ ├── _index.md │ │ ├── build-terminal.png │ │ ├── compliance │ │ │ ├── _index.md │ │ │ └── a4f_leda_overview_20230621.png │ │ ├── concepts.md │ │ ├── dev-and-maintenance │ │ │ ├── _index.md │ │ │ ├── rust │ │ │ │ ├── _index.md │ │ │ │ ├── kanto-auto-deployer.md │ │ │ │ ├── kantui.md │ │ │ │ └── notes-on-kanto-grpc.md │ │ │ └── shell │ │ │ │ ├── _index.md │ │ │ │ └── sdv-health.md │ │ ├── devenv │ │ │ ├── _index.md │ │ │ ├── build-kas-manually.md │ │ │ ├── github-codespaces │ │ │ │ ├── _index.md │ │ │ │ ├── github-code-new-codespace.png │ │ │ │ ├── github-codespaces-advanced.md │ │ │ │ └── github-codespaces-remote-explorer.png │ │ │ ├── github-runner │ │ │ │ ├── _index.md │ │ │ │ ├── nextnumber.png │ │ │ │ └── token.png │ │ │ ├── restricted-internet-environments │ │ │ │ └── _index.md │ │ │ └── vscode-devcontainer.md │ │ ├── ghcsco.png │ │ ├── github │ │ │ ├── github-workflow-optimizations.drawio.svg │ │ │ ├── github-workflow-optimizations.png │ │ │ ├── github-workflow.drawio.svg │ │ │ ├── github-workflow.png │ │ │ └── index.md │ │ ├── metalayer.md │ │ ├── misc │ │ │ ├── _index.md │ │ │ ├── diskusage.md │ │ │ └── partitioning │ │ │ │ ├── _index.md │ │ │ │ ├── leda-disk-layout-qemux86-64.drawio │ │ │ │ ├── leda-disk-layout-qemux86-64.png │ │ │ │ └── leda-disk-layout-qemux86-64.svg │ │ ├── release │ │ │ ├── _index.md │ │ │ └── validation.md │ │ ├── run-build.md │ │ ├── runqemu │ │ │ ├── _index.md │ │ │ └── qemu-runner-script.png │ │ └── tests │ │ │ ├── _index.md │ │ │ ├── gh-robot-report-with-failed.png │ │ │ ├── leda-tests-overview.drawio │ │ │ ├── leda-tests-overview.png │ │ │ ├── robot-keywords.md │ │ │ └── rust-tests.md │ ├── customization │ │ ├── _index.md │ │ ├── custom-images │ │ │ └── _index.md │ │ ├── deploying-containers │ │ │ └── _index.md │ │ └── faq │ │ │ └── _index.md │ ├── device-provisioning │ │ ├── _index.md │ │ ├── container-management │ │ │ ├── _index.md │ │ │ ├── cloud-connectivity.md │ │ │ ├── container-management-detail.json │ │ │ ├── container-management-list.json │ │ │ ├── container-metrics-request.json │ │ │ ├── container-metrics-response.json │ │ │ ├── container-metrics.md │ │ │ ├── container-registries.md │ │ │ ├── container-update-agent.md │ │ │ ├── currentstate-leda.json │ │ │ ├── leda-desired-state.json │ │ │ ├── orchestration.md │ │ │ └── simulate-connectivity.json │ │ ├── manual-provisioning.md │ │ ├── script-provisioning.md │ │ ├── self-update │ │ │ ├── _index.md │ │ │ ├── activate-command.json │ │ │ ├── api │ │ │ │ └── _index.md │ │ │ ├── cleanup-command.json │ │ │ ├── download-command.json │ │ │ ├── leda-self-update.drawio.svg │ │ │ ├── leda-self-update.png │ │ │ ├── rauc-integration.md │ │ │ ├── self-update-arch.drawio.svg │ │ │ ├── self-update-arch.png │ │ │ ├── self-update-tutorial.md │ │ │ ├── start-update-example.json │ │ │ └── update-command.json │ │ └── vehicle-update-manager │ │ │ ├── _index.md │ │ │ ├── message-flow.md │ │ │ ├── message-flow.md.deprecated │ │ │ ├── vehicle-update-manager-arch.drawio.svg │ │ │ ├── vehicle-update-manager-arch.png │ │ │ └── vehicle-update-manager-configuration.md │ ├── general-usage │ │ ├── _index.md │ │ ├── cheatsheet.md │ │ ├── docker-setup │ │ │ ├── _index.md │ │ │ └── leda-docker-compose-up.gif │ │ ├── download-releases │ │ │ └── _index.md │ │ ├── gps-configuration │ │ │ └── _index.md │ │ ├── linux-setup │ │ │ └── _index.md │ │ ├── raspberry-pi │ │ │ ├── _index.md │ │ │ └── raspberry-can-hats.md │ │ ├── running-qemu │ │ │ ├── _index.md │ │ │ ├── canbus.md │ │ │ ├── filetransfer.md │ │ │ ├── leda-bootsequence.png │ │ │ ├── sdv-health1.png │ │ │ └── systemctl-status-k3s.png │ │ ├── sdv-introduction │ │ │ ├── _index.md │ │ │ ├── abstract-architecture.drawio │ │ │ ├── abstract-architecture.png │ │ │ ├── digitalauto-prototype.png │ │ │ ├── digitalauto-vehicle-api.png │ │ │ ├── kuksa-actuation.drawio │ │ │ ├── kuksa-actuation.png │ │ │ ├── vehicle-mock.drawio │ │ │ ├── vehicle-mock.png │ │ │ ├── velocitas-flow.drawio │ │ │ ├── velocitas-flow.png │ │ │ ├── vss-tree.drawio │ │ │ └── vss-tree.png │ │ ├── utilities │ │ │ ├── _index.md │ │ │ ├── blueprint-selector-1.png │ │ │ ├── blueprint-selector.md │ │ │ ├── can-forward.md │ │ │ ├── kanto-auto-deployer.md │ │ │ ├── kantui-large.png │ │ │ ├── kantui.md │ │ │ ├── sdv-ctr-exec.md │ │ │ ├── sdv-device-info-example-output1.png │ │ │ ├── sdv-device-info.md │ │ │ ├── sdv-health-example-errors.png │ │ │ ├── sdv-health-example-errors2.png │ │ │ ├── sdv-health-output.png │ │ │ ├── sdv-health.md │ │ │ ├── sdv-kanto-ctl-example-output1.png │ │ │ ├── sdv-kanto-ctl.md │ │ │ ├── sdv-motd.md │ │ │ ├── sdv-motd.png │ │ │ └── sdv-provision.md │ │ └── wifi-configuration │ │ │ ├── _index.md │ │ │ └── connecting-to-wifi.md │ ├── leda-incubator │ │ ├── _index.md │ │ ├── cloud-connector │ │ │ ├── _index.md │ │ │ ├── cloud-connector-fork.drawio.svg │ │ │ ├── cloud-connector-fork.png │ │ │ ├── cloud-connector-runtime.drawio.svg │ │ │ └── cloud-connector-runtime.png │ │ ├── otel-integration │ │ │ └── _index.md │ │ ├── self-update-agent │ │ │ ├── _index.md │ │ │ ├── self-update-agent-arch.drawio.svg │ │ │ ├── self-update-agent-arch.png │ │ │ ├── self-update-agent-deploy.drawio.svg │ │ │ └── self-update-agent-deploy.png │ │ └── vehicle-update-manager │ │ │ ├── _index.md │ │ │ ├── vehicle-update-manager-arch.drawio.svg │ │ │ └── vehicle-update-manager-arch.png │ ├── overview.puml │ ├── project-info │ │ ├── _index.md │ │ ├── community │ │ │ ├── Eclipse Leda - Slides SDV Contribution Day - September 2022.pdf │ │ │ └── _index.md │ │ ├── contribution-guidelines.md │ │ ├── dependencies.md │ │ ├── logo │ │ │ ├── _index.md │ │ │ ├── _variables_project.scss │ │ │ ├── eclipse-leda-logo-black.png │ │ │ ├── eclipse-leda-logo-cropped.png │ │ │ ├── eclipse-leda-logo-white-transparent.png │ │ │ ├── eclipse-leda-logo.zip │ │ │ ├── eclipse-leda-logo_01_cmyk.ai │ │ │ ├── eclipse-leda-logo_01_cmyk.eps │ │ │ ├── eclipse-leda-logo_01_cmyk.pdf │ │ │ ├── eclipse-leda-logo_01_rgb.ai │ │ │ ├── eclipse-leda-logo_01_rgb.jpg │ │ │ ├── eclipse-leda-logo_01_rgb.png │ │ │ ├── eclipse-leda-logo_02_cmyk.ai │ │ │ ├── eclipse-leda-logo_02_cmyk.eps │ │ │ ├── eclipse-leda-logo_02_cmyk.pdf │ │ │ ├── eclipse-leda-logo_02_rgb.ai │ │ │ ├── eclipse-leda-logo_02_rgb.jpg │ │ │ ├── eclipse-leda-logo_02_rgb.png │ │ │ ├── eclipse-leda-logo_03_cmyk.svg │ │ │ ├── eclipse-leda-logo_03_cmyk_cropped.svg │ │ │ └── icon.png │ │ ├── privacy-information.md │ │ └── security.md │ └── vss │ │ └── _index.md │ ├── leda-logo.png │ └── logo_01_rgb-background.png ├── data └── consent.yaml ├── layouts ├── 404.html ├── _default │ ├── _markup │ │ └── render-codeblock-mermaid.html │ └── baseof.html ├── blog │ └── baseof.html ├── docs │ └── baseof.html ├── partials │ ├── analytics-with-consent.html │ └── footer.html ├── shortcodes │ ├── img.html │ └── raw.html └── swagger │ └── baseof.html ├── package-lock.json ├── package.json ├── static ├── assets │ ├── eclipse-leda-arch-overview.drawio │ ├── eclipse-leda-arch-overview.png │ ├── eclipse-leda.png │ ├── googlefa99e46d982661fb.html │ ├── icon.png │ ├── leda-architecture-details.png │ └── project-logo │ │ ├── eclipse-leda-logo-cropped.png │ │ ├── icon.png │ │ ├── logo_01_rgb.jpg │ │ ├── logo_01_rgb.png │ │ ├── logo_02_rgb.jpg │ │ └── logo_02_rgb.png └── googlefa99e46d982661fb.html ├── themes └── .gitkeep └── vss ├── build-vss-docs.sh ├── output └── Vehicle │ ├── ADAS │ ├── ABS │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsEngaged │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ └── _index.md │ ├── ActiveAutonomyLevel │ │ └── _index.md │ ├── CruiseControl │ │ ├── IsActive │ │ │ └── _index.md │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ ├── SpeedSet │ │ │ └── _index.md │ │ └── _index.md │ ├── EBA │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsEngaged │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ └── _index.md │ ├── EBD │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsEngaged │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ └── _index.md │ ├── ESC │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsEngaged │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ ├── IsStrongCrossWindDetected │ │ │ └── _index.md │ │ ├── RoadFriction │ │ │ ├── LowerBound │ │ │ │ └── _index.md │ │ │ ├── MostProbable │ │ │ │ └── _index.md │ │ │ ├── UpperBound │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── LaneDepartureDetection │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ ├── IsWarning │ │ │ └── _index.md │ │ └── _index.md │ ├── ObstacleDetection │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ ├── IsWarning │ │ │ └── _index.md │ │ └── _index.md │ ├── PowerOptimizeLevel │ │ └── _index.md │ ├── SupportedAutonomyLevel │ │ └── _index.md │ ├── TCS │ │ ├── IsEnabled │ │ │ └── _index.md │ │ ├── IsEngaged │ │ │ └── _index.md │ │ ├── IsError │ │ │ └── _index.md │ │ └── _index.md │ └── _index.md │ ├── Acceleration │ ├── Lateral │ │ └── _index.md │ ├── Longitudinal │ │ └── _index.md │ ├── Vertical │ │ └── _index.md │ └── _index.md │ ├── AngularVelocity │ ├── Pitch │ │ └── _index.md │ ├── Roll │ │ └── _index.md │ ├── Yaw │ │ └── _index.md │ └── _index.md │ ├── AverageSpeed │ └── _index.md │ ├── Body │ ├── BodyType │ │ └── _index.md │ ├── Hood │ │ ├── IsOpen │ │ │ └── _index.md │ │ └── _index.md │ ├── Horn │ │ ├── IsActive │ │ │ └── _index.md │ │ └── _index.md │ ├── Lights │ │ ├── Backup │ │ │ ├── IsDefect │ │ │ │ └── _index.md │ │ │ ├── IsOn │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Beam │ │ │ ├── High │ │ │ │ ├── IsDefect │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Low │ │ │ │ ├── IsDefect │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Brake │ │ │ ├── IsActive │ │ │ │ └── _index.md │ │ │ ├── IsDefect │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── DirectionIndicator │ │ │ ├── Left │ │ │ │ ├── IsDefect │ │ │ │ │ └── _index.md │ │ │ │ ├── IsSignaling │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Right │ │ │ │ ├── IsDefect │ │ │ │ │ └── _index.md │ │ │ │ ├── IsSignaling │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Fog │ │ │ ├── Front │ │ │ │ ├── IsDefect │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Rear │ │ │ │ ├── IsDefect │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Hazard │ │ │ ├── IsDefect │ │ │ │ └── _index.md │ │ │ ├── IsSignaling │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── IsHighBeamSwitchOn │ │ │ └── _index.md │ │ ├── LicensePlate │ │ │ ├── IsDefect │ │ │ │ └── _index.md │ │ │ ├── IsOn │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── LightSwitch │ │ │ └── _index.md │ │ ├── Parking │ │ │ ├── IsDefect │ │ │ │ └── _index.md │ │ │ ├── IsOn │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Running │ │ │ ├── IsDefect │ │ │ │ └── _index.md │ │ │ ├── IsOn │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── Mirrors │ │ ├── Left │ │ │ ├── IsHeatingOn │ │ │ │ └── _index.md │ │ │ ├── Pan │ │ │ │ └── _index.md │ │ │ ├── Tilt │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Right │ │ │ ├── IsHeatingOn │ │ │ │ └── _index.md │ │ │ ├── Pan │ │ │ │ └── _index.md │ │ │ ├── Tilt │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── PowerOptimizeLevel │ │ └── _index.md │ ├── Raindetection │ │ ├── Intensity │ │ │ └── _index.md │ │ └── _index.md │ ├── RearMainSpoilerPosition │ │ └── _index.md │ ├── RefuelPosition │ │ └── _index.md │ ├── Trunk │ │ ├── Front │ │ │ ├── IsLocked │ │ │ │ └── _index.md │ │ │ ├── IsOpen │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Rear │ │ │ ├── IsLocked │ │ │ │ └── _index.md │ │ │ ├── IsOpen │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── Windshield │ │ ├── Front │ │ │ ├── IsHeatingOn │ │ │ │ └── _index.md │ │ │ ├── WasherFluid │ │ │ │ ├── IsLevelLow │ │ │ │ │ └── _index.md │ │ │ │ ├── Level │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Wiping │ │ │ │ ├── Intensity │ │ │ │ │ └── _index.md │ │ │ │ ├── IsWipersWorn │ │ │ │ │ └── _index.md │ │ │ │ ├── Mode │ │ │ │ │ └── _index.md │ │ │ │ ├── System │ │ │ │ │ ├── ActualPosition │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── DriveCurrent │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Frequency │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBlocked │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsEndingWipeCycle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsOverheated │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsPositionReached │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWiperError │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWiping │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Mode │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── TargetPosition │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── WiperWear │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Rear │ │ │ ├── IsHeatingOn │ │ │ │ └── _index.md │ │ │ ├── WasherFluid │ │ │ │ ├── IsLevelLow │ │ │ │ │ └── _index.md │ │ │ │ ├── Level │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Wiping │ │ │ │ ├── Intensity │ │ │ │ │ └── _index.md │ │ │ │ ├── IsWipersWorn │ │ │ │ │ └── _index.md │ │ │ │ ├── Mode │ │ │ │ │ └── _index.md │ │ │ │ ├── System │ │ │ │ │ ├── ActualPosition │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── DriveCurrent │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Frequency │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBlocked │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsEndingWipeCycle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsOverheated │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsPositionReached │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWiperError │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWiping │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Mode │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── TargetPosition │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── WiperWear │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ └── _index.md │ ├── Cabin │ ├── Convertible │ │ ├── Status │ │ │ └── _index.md │ │ └── _index.md │ ├── Door │ │ ├── Row1 │ │ │ ├── Left │ │ │ │ ├── IsChildLockActive │ │ │ │ │ └── _index.md │ │ │ │ ├── IsLocked │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOpen │ │ │ │ │ └── _index.md │ │ │ │ ├── Shade │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Window │ │ │ │ │ ├── IsChildLockEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsOpen │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Right │ │ │ │ ├── IsChildLockActive │ │ │ │ │ └── _index.md │ │ │ │ ├── IsLocked │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOpen │ │ │ │ │ └── _index.md │ │ │ │ ├── Shade │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Window │ │ │ │ │ ├── IsChildLockEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsOpen │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Row2 │ │ │ ├── Left │ │ │ │ ├── IsChildLockActive │ │ │ │ │ └── _index.md │ │ │ │ ├── IsLocked │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOpen │ │ │ │ │ └── _index.md │ │ │ │ ├── Shade │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Window │ │ │ │ │ ├── IsChildLockEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsOpen │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Right │ │ │ │ ├── IsChildLockActive │ │ │ │ │ └── _index.md │ │ │ │ ├── IsLocked │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOpen │ │ │ │ │ └── _index.md │ │ │ │ ├── Shade │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Window │ │ │ │ │ ├── IsChildLockEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsOpen │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Position │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Switch │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── DoorCount │ │ └── _index.md │ ├── DriverPosition │ │ └── _index.md │ ├── HVAC │ │ ├── AmbientAirTemperature │ │ │ └── _index.md │ │ ├── IsAirConditioningActive │ │ │ └── _index.md │ │ ├── IsFrontDefrosterActive │ │ │ └── _index.md │ │ ├── IsRearDefrosterActive │ │ │ └── _index.md │ │ ├── IsRecirculationActive │ │ │ └── _index.md │ │ ├── PowerOptimizeLevel │ │ │ └── _index.md │ │ ├── Station │ │ │ ├── Row1 │ │ │ │ ├── Left │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Right │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Row2 │ │ │ │ ├── Left │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Right │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Row3 │ │ │ │ ├── Left │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Right │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Row4 │ │ │ │ ├── Left │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Right │ │ │ │ │ ├── AirDistribution │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── FanSpeed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Temperature │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── Infotainment │ │ ├── HMI │ │ │ ├── Brightness │ │ │ │ └── _index.md │ │ │ ├── CurrentLanguage │ │ │ │ └── _index.md │ │ │ ├── DateFormat │ │ │ │ └── _index.md │ │ │ ├── DayNightMode │ │ │ │ └── _index.md │ │ │ ├── DistanceUnit │ │ │ │ └── _index.md │ │ │ ├── EVEconomyUnits │ │ │ │ └── _index.md │ │ │ ├── FuelEconomyUnits │ │ │ │ └── _index.md │ │ │ ├── FuelVolumeUnit │ │ │ │ └── _index.md │ │ │ ├── TemperatureUnit │ │ │ │ └── _index.md │ │ │ ├── TimeFormat │ │ │ │ └── _index.md │ │ │ ├── TirePressureUnit │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Media │ │ │ ├── Action │ │ │ │ └── _index.md │ │ │ ├── DeclinedURI │ │ │ │ └── _index.md │ │ │ ├── Played │ │ │ │ ├── Album │ │ │ │ │ └── _index.md │ │ │ │ ├── Artist │ │ │ │ │ └── _index.md │ │ │ │ ├── PlaybackRate │ │ │ │ │ └── _index.md │ │ │ │ ├── Source │ │ │ │ │ └── _index.md │ │ │ │ ├── Track │ │ │ │ │ └── _index.md │ │ │ │ ├── URI │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── SelectedURI │ │ │ │ └── _index.md │ │ │ ├── Volume │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Navigation │ │ │ ├── DestinationSet │ │ │ │ ├── Latitude │ │ │ │ │ └── _index.md │ │ │ │ ├── Longitude │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Mute │ │ │ │ └── _index.md │ │ │ ├── Volume │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── PowerOptimizeLevel │ │ │ └── _index.md │ │ ├── SmartphoneProjection │ │ │ ├── Active │ │ │ │ └── _index.md │ │ │ ├── Source │ │ │ │ └── _index.md │ │ │ ├── SupportedMode │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── Lights │ │ ├── AmbientLight │ │ │ └── _index.md │ │ ├── IsDomeOn │ │ │ └── _index.md │ │ ├── IsGloveBoxOn │ │ │ └── _index.md │ │ ├── IsTrunkOn │ │ │ └── _index.md │ │ ├── LightIntensity │ │ │ └── _index.md │ │ ├── Spotlight │ │ │ ├── Row1 │ │ │ │ ├── IsLeftOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsRightOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsSharedOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Row2 │ │ │ │ ├── IsLeftOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsRightOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsSharedOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Row3 │ │ │ │ ├── IsLeftOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsRightOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsSharedOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Row4 │ │ │ │ ├── IsLeftOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsRightOn │ │ │ │ │ └── _index.md │ │ │ │ ├── IsSharedOn │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── PowerOptimizeLevel │ │ └── _index.md │ ├── RearShade │ │ ├── Position │ │ │ └── _index.md │ │ ├── Switch │ │ │ └── _index.md │ │ └── _index.md │ ├── RearviewMirror │ │ ├── DimmingLevel │ │ │ └── _index.md │ │ └── _index.md │ ├── Seat │ │ ├── Row1 │ │ │ ├── Pos1 │ │ │ │ ├── Airbag │ │ │ │ │ ├── IsDeployed │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Backrest │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ ├── Height │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Recline │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Headrest │ │ │ │ │ ├── Angle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Height │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Heating │ │ │ │ │ └── _index.md │ │ │ │ ├── Height │ │ │ │ │ └── _index.md │ │ │ │ ├── IsBelted │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOccupied │ │ │ │ │ └── _index.md │ │ │ │ ├── Massage │ │ │ │ │ └── _index.md │ │ │ │ ├── Occupant │ │ │ │ │ ├── Identifier │ │ │ │ │ │ ├── Issuer │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Subject │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Position │ │ │ │ │ └── _index.md │ │ │ │ ├── Seating │ │ │ │ │ ├── Length │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Switch │ │ │ │ │ ├── Backrest │ │ │ │ │ │ ├── IsReclineBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsReclineForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Headrest │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsCoolerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWarmerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Massage │ │ │ │ │ │ ├── IsDecreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsIncreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Seating │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Tilt │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Pos2 │ │ │ │ ├── Airbag │ │ │ │ │ ├── IsDeployed │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Backrest │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ ├── Height │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Recline │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Headrest │ │ │ │ │ ├── Angle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Height │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Heating │ │ │ │ │ └── _index.md │ │ │ │ ├── Height │ │ │ │ │ └── _index.md │ │ │ │ ├── IsBelted │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOccupied │ │ │ │ │ └── _index.md │ │ │ │ ├── Massage │ │ │ │ │ └── _index.md │ │ │ │ ├── Occupant │ │ │ │ │ ├── Identifier │ │ │ │ │ │ ├── Issuer │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Subject │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Position │ │ │ │ │ └── _index.md │ │ │ │ ├── Seating │ │ │ │ │ ├── Length │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Switch │ │ │ │ │ ├── Backrest │ │ │ │ │ │ ├── IsReclineBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsReclineForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Headrest │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsCoolerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWarmerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Massage │ │ │ │ │ │ ├── IsDecreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsIncreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Seating │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Tilt │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Pos3 │ │ │ │ ├── Airbag │ │ │ │ │ ├── IsDeployed │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Backrest │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ ├── Height │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Recline │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Headrest │ │ │ │ │ ├── Angle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Height │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Heating │ │ │ │ │ └── _index.md │ │ │ │ ├── Height │ │ │ │ │ └── _index.md │ │ │ │ ├── IsBelted │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOccupied │ │ │ │ │ └── _index.md │ │ │ │ ├── Massage │ │ │ │ │ └── _index.md │ │ │ │ ├── Occupant │ │ │ │ │ ├── Identifier │ │ │ │ │ │ ├── Issuer │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Subject │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Position │ │ │ │ │ └── _index.md │ │ │ │ ├── Seating │ │ │ │ │ ├── Length │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Switch │ │ │ │ │ ├── Backrest │ │ │ │ │ │ ├── IsReclineBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsReclineForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Headrest │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsCoolerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWarmerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Massage │ │ │ │ │ │ ├── IsDecreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsIncreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Seating │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Tilt │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Row2 │ │ │ ├── Pos1 │ │ │ │ ├── Airbag │ │ │ │ │ ├── IsDeployed │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Backrest │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ ├── Height │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Recline │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Headrest │ │ │ │ │ ├── Angle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Height │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Heating │ │ │ │ │ └── _index.md │ │ │ │ ├── Height │ │ │ │ │ └── _index.md │ │ │ │ ├── IsBelted │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOccupied │ │ │ │ │ └── _index.md │ │ │ │ ├── Massage │ │ │ │ │ └── _index.md │ │ │ │ ├── Occupant │ │ │ │ │ ├── Identifier │ │ │ │ │ │ ├── Issuer │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Subject │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Position │ │ │ │ │ └── _index.md │ │ │ │ ├── Seating │ │ │ │ │ ├── Length │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Switch │ │ │ │ │ ├── Backrest │ │ │ │ │ │ ├── IsReclineBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsReclineForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Headrest │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsCoolerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWarmerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Massage │ │ │ │ │ │ ├── IsDecreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsIncreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Seating │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Tilt │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Pos2 │ │ │ │ ├── Airbag │ │ │ │ │ ├── IsDeployed │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Backrest │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ ├── Height │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Recline │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Headrest │ │ │ │ │ ├── Angle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Height │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Heating │ │ │ │ │ └── _index.md │ │ │ │ ├── Height │ │ │ │ │ └── _index.md │ │ │ │ ├── IsBelted │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOccupied │ │ │ │ │ └── _index.md │ │ │ │ ├── Massage │ │ │ │ │ └── _index.md │ │ │ │ ├── Occupant │ │ │ │ │ ├── Identifier │ │ │ │ │ │ ├── Issuer │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Subject │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Position │ │ │ │ │ └── _index.md │ │ │ │ ├── Seating │ │ │ │ │ ├── Length │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Switch │ │ │ │ │ ├── Backrest │ │ │ │ │ │ ├── IsReclineBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsReclineForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Headrest │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsCoolerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWarmerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Massage │ │ │ │ │ │ ├── IsDecreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsIncreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Seating │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Tilt │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Pos3 │ │ │ │ ├── Airbag │ │ │ │ │ ├── IsDeployed │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Backrest │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ ├── Height │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Recline │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ ├── Support │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Headrest │ │ │ │ │ ├── Angle │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Height │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Heating │ │ │ │ │ └── _index.md │ │ │ │ ├── Height │ │ │ │ │ └── _index.md │ │ │ │ ├── IsBelted │ │ │ │ │ └── _index.md │ │ │ │ ├── IsOccupied │ │ │ │ │ └── _index.md │ │ │ │ ├── Massage │ │ │ │ │ └── _index.md │ │ │ │ ├── Occupant │ │ │ │ │ ├── Identifier │ │ │ │ │ │ ├── Issuer │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Subject │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Position │ │ │ │ │ └── _index.md │ │ │ │ ├── Seating │ │ │ │ │ ├── Length │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Switch │ │ │ │ │ ├── Backrest │ │ │ │ │ │ ├── IsReclineBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsReclineForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Lumbar │ │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── SideBolster │ │ │ │ │ │ │ ├── IsLessSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ ├── IsMoreSupportEngaged │ │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Headrest │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsCoolerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsDownEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltBackwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsTiltForwardEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsUpEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── IsWarmerEngaged │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Massage │ │ │ │ │ │ ├── IsDecreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsIncreaseEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Seating │ │ │ │ │ │ ├── IsBackwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsForwardEngaged │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Tilt │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── SeatPosCount │ │ └── _index.md │ ├── SeatRowCount │ │ └── _index.md │ ├── Sunroof │ │ ├── Position │ │ │ └── _index.md │ │ ├── Shade │ │ │ ├── Position │ │ │ │ └── _index.md │ │ │ ├── Switch │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Switch │ │ │ └── _index.md │ │ └── _index.md │ └── _index.md │ ├── CargoVolume │ └── _index.md │ ├── Chassis │ ├── Accelerator │ │ ├── PedalPosition │ │ │ └── _index.md │ │ └── _index.md │ ├── Axle │ │ ├── Row1 │ │ │ ├── SteeringAngle │ │ │ │ └── _index.md │ │ │ ├── TireAspectRatio │ │ │ │ └── _index.md │ │ │ ├── TireDiameter │ │ │ │ └── _index.md │ │ │ ├── TireWidth │ │ │ │ └── _index.md │ │ │ ├── Wheel │ │ │ │ ├── Left │ │ │ │ │ ├── Brake │ │ │ │ │ │ ├── FluidLevel │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsBrakesWorn │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsFluidLevelLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── PadWear │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Speed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Tire │ │ │ │ │ │ ├── IsPressureLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Pressure │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Temperature │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Right │ │ │ │ │ ├── Brake │ │ │ │ │ │ ├── FluidLevel │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsBrakesWorn │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsFluidLevelLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── PadWear │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Speed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Tire │ │ │ │ │ │ ├── IsPressureLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Pressure │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Temperature │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── WheelCount │ │ │ │ └── _index.md │ │ │ ├── WheelDiameter │ │ │ │ └── _index.md │ │ │ ├── WheelWidth │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Row2 │ │ │ ├── SteeringAngle │ │ │ │ └── _index.md │ │ │ ├── TireAspectRatio │ │ │ │ └── _index.md │ │ │ ├── TireDiameter │ │ │ │ └── _index.md │ │ │ ├── TireWidth │ │ │ │ └── _index.md │ │ │ ├── Wheel │ │ │ │ ├── Left │ │ │ │ │ ├── Brake │ │ │ │ │ │ ├── FluidLevel │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsBrakesWorn │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsFluidLevelLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── PadWear │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Speed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Tire │ │ │ │ │ │ ├── IsPressureLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Pressure │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Temperature │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ ├── Right │ │ │ │ │ ├── Brake │ │ │ │ │ │ ├── FluidLevel │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsBrakesWorn │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── IsFluidLevelLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── PadWear │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Speed │ │ │ │ │ │ └── _index.md │ │ │ │ │ ├── Tire │ │ │ │ │ │ ├── IsPressureLow │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Pressure │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ ├── Temperature │ │ │ │ │ │ │ └── _index.md │ │ │ │ │ │ └── _index.md │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── WheelCount │ │ │ │ └── _index.md │ │ │ ├── WheelDiameter │ │ │ │ └── _index.md │ │ │ ├── WheelWidth │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── AxleCount │ │ └── _index.md │ ├── Brake │ │ ├── IsDriverEmergencyBrakingDetected │ │ │ └── _index.md │ │ ├── PedalPosition │ │ │ └── _index.md │ │ └── _index.md │ ├── ParkingBrake │ │ ├── IsEngaged │ │ │ └── _index.md │ │ └── _index.md │ ├── SteeringWheel │ │ ├── Angle │ │ │ └── _index.md │ │ ├── Extension │ │ │ └── _index.md │ │ ├── Position │ │ │ └── _index.md │ │ ├── Tilt │ │ │ └── _index.md │ │ └── _index.md │ ├── Track │ │ └── _index.md │ ├── Wheelbase │ │ └── _index.md │ └── _index.md │ ├── Connectivity │ ├── IsConnectivityAvailable │ │ └── _index.md │ └── _index.md │ ├── CurbWeight │ └── _index.md │ ├── CurrentLocation │ ├── Altitude │ │ └── _index.md │ ├── GNSSReceiver │ │ ├── FixType │ │ │ └── _index.md │ │ ├── MountingPosition │ │ │ ├── X │ │ │ │ └── _index.md │ │ │ ├── Y │ │ │ │ └── _index.md │ │ │ ├── Z │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── Heading │ │ └── _index.md │ ├── HorizontalAccuracy │ │ └── _index.md │ ├── Latitude │ │ └── _index.md │ ├── Longitude │ │ └── _index.md │ ├── Timestamp │ │ └── _index.md │ ├── VerticalAccuracy │ │ └── _index.md │ └── _index.md │ ├── CurrentOverallWeight │ └── _index.md │ ├── Driver │ ├── AttentiveProbability │ │ └── _index.md │ ├── DistractionLevel │ │ └── _index.md │ ├── FatigueLevel │ │ └── _index.md │ ├── HeartRate │ │ └── _index.md │ ├── Identifier │ │ ├── Issuer │ │ │ └── _index.md │ │ ├── Subject │ │ │ └── _index.md │ │ └── _index.md │ ├── IsEyesOnRoad │ │ └── _index.md │ └── _index.md │ ├── EmissionsCO2 │ └── _index.md │ ├── Exterior │ ├── AirTemperature │ │ └── _index.md │ ├── Humidity │ │ └── _index.md │ ├── LightIntensity │ │ └── _index.md │ └── _index.md │ ├── GrossWeight │ └── _index.md │ ├── Height │ └── _index.md │ ├── IsBrokenDown │ └── _index.md │ ├── IsMoving │ └── _index.md │ ├── Length │ └── _index.md │ ├── LowVoltageBattery │ ├── CurrentCurrent │ │ └── _index.md │ ├── CurrentVoltage │ │ └── _index.md │ ├── NominalCapacity │ │ └── _index.md │ ├── NominalVoltage │ │ └── _index.md │ └── _index.md │ ├── LowVoltageSystemState │ └── _index.md │ ├── MaxTowBallWeight │ └── _index.md │ ├── MaxTowWeight │ └── _index.md │ ├── OBD │ ├── AbsoluteLoad │ │ └── _index.md │ ├── AcceleratorPositionD │ │ └── _index.md │ ├── AcceleratorPositionE │ │ └── _index.md │ ├── AcceleratorPositionF │ │ └── _index.md │ ├── AirStatus │ │ └── _index.md │ ├── AmbientAirTemperature │ │ └── _index.md │ ├── BarometricPressure │ │ └── _index.md │ ├── Catalyst │ │ ├── Bank1 │ │ │ ├── Temperature1 │ │ │ │ └── _index.md │ │ │ ├── Temperature2 │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Bank2 │ │ │ ├── Temperature1 │ │ │ │ └── _index.md │ │ │ ├── Temperature2 │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── CommandedEGR │ │ └── _index.md │ ├── CommandedEVAP │ │ └── _index.md │ ├── CommandedEquivalenceRatio │ │ └── _index.md │ ├── ControlModuleVoltage │ │ └── _index.md │ ├── CoolantTemperature │ │ └── _index.md │ ├── DTCList │ │ └── _index.md │ ├── DistanceSinceDTCClear │ │ └── _index.md │ ├── DistanceWithMIL │ │ └── _index.md │ ├── DriveCycleStatus │ │ ├── DTCCount │ │ │ └── _index.md │ │ ├── IgnitionType │ │ │ └── _index.md │ │ ├── IsMILOn │ │ │ └── _index.md │ │ └── _index.md │ ├── EGRError │ │ └── _index.md │ ├── EVAPVaporPressure │ │ └── _index.md │ ├── EVAPVaporPressureAbsolute │ │ └── _index.md │ ├── EVAPVaporPressureAlternate │ │ └── _index.md │ ├── EngineLoad │ │ └── _index.md │ ├── EngineSpeed │ │ └── _index.md │ ├── EthanolPercent │ │ └── _index.md │ ├── FreezeDTC │ │ └── _index.md │ ├── FuelInjectionTiming │ │ └── _index.md │ ├── FuelLevel │ │ └── _index.md │ ├── FuelPressure │ │ └── _index.md │ ├── FuelRailPressureAbsolute │ │ └── _index.md │ ├── FuelRailPressureDirect │ │ └── _index.md │ ├── FuelRailPressureVac │ │ └── _index.md │ ├── FuelRate │ │ └── _index.md │ ├── FuelStatus │ │ └── _index.md │ ├── FuelType │ │ └── _index.md │ ├── HybridBatteryRemaining │ │ └── _index.md │ ├── IntakeTemp │ │ └── _index.md │ ├── IsPTOActive │ │ └── _index.md │ ├── LongTermFuelTrim1 │ │ └── _index.md │ ├── LongTermFuelTrim2 │ │ └── _index.md │ ├── LongTermO2Trim1 │ │ └── _index.md │ ├── LongTermO2Trim2 │ │ └── _index.md │ ├── LongTermO2Trim3 │ │ └── _index.md │ ├── LongTermO2Trim4 │ │ └── _index.md │ ├── MAF │ │ └── _index.md │ ├── MAP │ │ └── _index.md │ ├── MaxMAF │ │ └── _index.md │ ├── O2 │ │ ├── Sensor1 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor2 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor3 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor4 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor5 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor6 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor7 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor8 │ │ │ ├── ShortTermFuelTrim │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── O2WR │ │ ├── Sensor1 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor2 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor3 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor4 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor5 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor6 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor7 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Sensor8 │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Lambda │ │ │ │ └── _index.md │ │ │ ├── Voltage │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── OBDStandards │ │ └── _index.md │ ├── OilTemperature │ │ └── _index.md │ ├── OxygenSensorsIn2Banks │ │ └── _index.md │ ├── OxygenSensorsIn4Banks │ │ └── _index.md │ ├── PidsA │ │ └── _index.md │ ├── PidsB │ │ └── _index.md │ ├── PidsC │ │ └── _index.md │ ├── RelativeAcceleratorPosition │ │ └── _index.md │ ├── RelativeThrottlePosition │ │ └── _index.md │ ├── RunTime │ │ └── _index.md │ ├── RunTimeMIL │ │ └── _index.md │ ├── ShortTermFuelTrim1 │ │ └── _index.md │ ├── ShortTermFuelTrim2 │ │ └── _index.md │ ├── ShortTermO2Trim1 │ │ └── _index.md │ ├── ShortTermO2Trim2 │ │ └── _index.md │ ├── ShortTermO2Trim3 │ │ └── _index.md │ ├── ShortTermO2Trim4 │ │ └── _index.md │ ├── Speed │ │ └── _index.md │ ├── Status │ │ ├── DTCCount │ │ │ └── _index.md │ │ ├── IgnitionType │ │ │ └── _index.md │ │ ├── IsMILOn │ │ │ └── _index.md │ │ └── _index.md │ ├── ThrottleActuator │ │ └── _index.md │ ├── ThrottlePosition │ │ └── _index.md │ ├── ThrottlePositionB │ │ └── _index.md │ ├── ThrottlePositionC │ │ └── _index.md │ ├── TimeSinceDTCCleared │ │ └── _index.md │ ├── TimingAdvance │ │ └── _index.md │ ├── WarmupsSinceDTCClear │ │ └── _index.md │ └── _index.md │ ├── PowerOptimizeLevel │ └── _index.md │ ├── Powertrain │ ├── AccumulatedBrakingEnergy │ │ └── _index.md │ ├── CombustionEngine │ │ ├── AspirationType │ │ │ └── _index.md │ │ ├── Bore │ │ │ └── _index.md │ │ ├── CompressionRatio │ │ │ └── _index.md │ │ ├── Configuration │ │ │ └── _index.md │ │ ├── DieselExhaustFluid │ │ │ ├── Capacity │ │ │ │ └── _index.md │ │ │ ├── IsLevelLow │ │ │ │ └── _index.md │ │ │ ├── Level │ │ │ │ └── _index.md │ │ │ ├── Range │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── DieselParticulateFilter │ │ │ ├── DeltaPressure │ │ │ │ └── _index.md │ │ │ ├── InletTemperature │ │ │ │ └── _index.md │ │ │ ├── OutletTemperature │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── Displacement │ │ │ └── _index.md │ │ ├── ECT │ │ │ └── _index.md │ │ ├── EOP │ │ │ └── _index.md │ │ ├── EOT │ │ │ └── _index.md │ │ ├── EngineCode │ │ │ └── _index.md │ │ ├── EngineCoolantCapacity │ │ │ └── _index.md │ │ ├── EngineHours │ │ │ └── _index.md │ │ ├── EngineOilCapacity │ │ │ └── _index.md │ │ ├── EngineOilLevel │ │ │ └── _index.md │ │ ├── IdleHours │ │ │ └── _index.md │ │ ├── IsRunning │ │ │ └── _index.md │ │ ├── MAF │ │ │ └── _index.md │ │ ├── MAP │ │ │ └── _index.md │ │ ├── MaxPower │ │ │ └── _index.md │ │ ├── MaxTorque │ │ │ └── _index.md │ │ ├── NumberOfCylinders │ │ │ └── _index.md │ │ ├── NumberOfValvesPerCylinder │ │ │ └── _index.md │ │ ├── OilLifeRemaining │ │ │ └── _index.md │ │ ├── Power │ │ │ └── _index.md │ │ ├── Speed │ │ │ └── _index.md │ │ ├── StrokeLength │ │ │ └── _index.md │ │ ├── TPS │ │ │ └── _index.md │ │ ├── Torque │ │ │ └── _index.md │ │ └── _index.md │ ├── ElectricMotor │ │ ├── CoolantTemperature │ │ │ └── _index.md │ │ ├── EngineCode │ │ │ └── _index.md │ │ ├── MaxPower │ │ │ └── _index.md │ │ ├── MaxRegenPower │ │ │ └── _index.md │ │ ├── MaxRegenTorque │ │ │ └── _index.md │ │ ├── MaxTorque │ │ │ └── _index.md │ │ ├── Power │ │ │ └── _index.md │ │ ├── Speed │ │ │ └── _index.md │ │ ├── Temperature │ │ │ └── _index.md │ │ ├── Torque │ │ │ └── _index.md │ │ └── _index.md │ ├── FuelSystem │ │ ├── AverageConsumption │ │ │ └── _index.md │ │ ├── ConsumptionSinceStart │ │ │ └── _index.md │ │ ├── HybridType │ │ │ └── _index.md │ │ ├── InstantConsumption │ │ │ └── _index.md │ │ ├── IsEngineStopStartEnabled │ │ │ └── _index.md │ │ ├── IsFuelLevelLow │ │ │ └── _index.md │ │ ├── Level │ │ │ └── _index.md │ │ ├── Range │ │ │ └── _index.md │ │ ├── SupportedFuel │ │ │ └── _index.md │ │ ├── SupportedFuelTypes │ │ │ └── _index.md │ │ ├── TankCapacity │ │ │ └── _index.md │ │ ├── TimeSinceStart │ │ │ └── _index.md │ │ └── _index.md │ ├── PowerOptimizeLevel │ │ └── _index.md │ ├── Range │ │ └── _index.md │ ├── TractionBattery │ │ ├── AccumulatedChargedEnergy │ │ │ └── _index.md │ │ ├── AccumulatedChargedThroughput │ │ │ └── _index.md │ │ ├── AccumulatedConsumedEnergy │ │ │ └── _index.md │ │ ├── AccumulatedConsumedThroughput │ │ │ └── _index.md │ │ ├── Charging │ │ │ ├── ChargeCurrent │ │ │ │ ├── DC │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase1 │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase2 │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase3 │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── ChargeLimit │ │ │ │ └── _index.md │ │ │ ├── ChargePlugType │ │ │ │ └── _index.md │ │ │ ├── ChargePortFlap │ │ │ │ └── _index.md │ │ │ ├── ChargeRate │ │ │ │ └── _index.md │ │ │ ├── ChargeVoltage │ │ │ │ ├── DC │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase1 │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase2 │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase3 │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── IsCharging │ │ │ │ └── _index.md │ │ │ ├── IsChargingCableConnected │ │ │ │ └── _index.md │ │ │ ├── IsChargingCableLocked │ │ │ │ └── _index.md │ │ │ ├── IsDischarging │ │ │ │ └── _index.md │ │ │ ├── MaximumChargingCurrent │ │ │ │ ├── DC │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase1 │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase2 │ │ │ │ │ └── _index.md │ │ │ │ ├── Phase3 │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ ├── Mode │ │ │ │ └── _index.md │ │ │ ├── PowerLoss │ │ │ │ └── _index.md │ │ │ ├── StartStopCharging │ │ │ │ └── _index.md │ │ │ ├── Temperature │ │ │ │ └── _index.md │ │ │ ├── TimeToComplete │ │ │ │ └── _index.md │ │ │ ├── Timer │ │ │ │ ├── Mode │ │ │ │ │ └── _index.md │ │ │ │ ├── Time │ │ │ │ │ └── _index.md │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── CurrentCurrent │ │ │ └── _index.md │ │ ├── CurrentPower │ │ │ └── _index.md │ │ ├── CurrentVoltage │ │ │ └── _index.md │ │ ├── DCDC │ │ │ ├── PowerLoss │ │ │ │ └── _index.md │ │ │ ├── Temperature │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── GrossCapacity │ │ │ └── _index.md │ │ ├── Id │ │ │ └── _index.md │ │ ├── IsGroundConnected │ │ │ └── _index.md │ │ ├── IsPowerConnected │ │ │ └── _index.md │ │ ├── MaxVoltage │ │ │ └── _index.md │ │ ├── NetCapacity │ │ │ └── _index.md │ │ ├── NominalVoltage │ │ │ └── _index.md │ │ ├── PowerLoss │ │ │ └── _index.md │ │ ├── ProductionDate │ │ │ └── _index.md │ │ ├── Range │ │ │ └── _index.md │ │ ├── StateOfCharge │ │ │ ├── Current │ │ │ │ └── _index.md │ │ │ ├── Displayed │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ ├── StateOfHealth │ │ │ └── _index.md │ │ ├── Temperature │ │ │ ├── Average │ │ │ │ └── _index.md │ │ │ ├── Max │ │ │ │ └── _index.md │ │ │ ├── Min │ │ │ │ └── _index.md │ │ │ └── _index.md │ │ └── _index.md │ ├── Transmission │ │ ├── ClutchEngagement │ │ │ └── _index.md │ │ ├── ClutchWear │ │ │ └── _index.md │ │ ├── CurrentGear │ │ │ └── _index.md │ │ ├── DiffLockFrontEngagement │ │ │ └── _index.md │ │ ├── DiffLockRearEngagement │ │ │ └── _index.md │ │ ├── DriveType │ │ │ └── _index.md │ │ ├── GearChangeMode │ │ │ └── _index.md │ │ ├── GearCount │ │ │ └── _index.md │ │ ├── IsElectricalPowertrainEngaged │ │ │ └── _index.md │ │ ├── IsLowRangeEngaged │ │ │ └── _index.md │ │ ├── IsParkLockEngaged │ │ │ └── _index.md │ │ ├── PerformanceMode │ │ │ └── _index.md │ │ ├── SelectedGear │ │ │ └── _index.md │ │ ├── Temperature │ │ │ └── _index.md │ │ ├── TorqueDistribution │ │ │ └── _index.md │ │ ├── TravelledDistance │ │ │ └── _index.md │ │ ├── Type │ │ │ └── _index.md │ │ └── _index.md │ ├── Type │ │ └── _index.md │ └── _index.md │ ├── RoofLoad │ └── _index.md │ ├── Service │ ├── DistanceToService │ │ └── _index.md │ ├── IsServiceDue │ │ └── _index.md │ ├── TimeToService │ │ └── _index.md │ └── _index.md │ ├── Speed │ └── _index.md │ ├── StartTime │ └── _index.md │ ├── Trailer │ ├── IsConnected │ │ └── _index.md │ └── _index.md │ ├── TraveledDistance │ └── _index.md │ ├── TraveledDistanceSinceStart │ └── _index.md │ ├── TravelledDistance │ └── _index.md │ ├── TripDuration │ └── _index.md │ ├── TripMeterReading │ └── _index.md │ ├── VehicleIdentification │ ├── AcrissCode │ │ └── _index.md │ ├── BodyType │ │ └── _index.md │ ├── Brand │ │ └── _index.md │ ├── DateVehicleFirstRegistered │ │ └── _index.md │ ├── KnownVehicleDamages │ │ └── _index.md │ ├── MeetsEmissionStandard │ │ └── _index.md │ ├── Model │ │ └── _index.md │ ├── OptionalExtras │ │ └── _index.md │ ├── ProductionDate │ │ └── _index.md │ ├── PurchaseDate │ │ └── _index.md │ ├── VIN │ │ └── _index.md │ ├── VehicleConfiguration │ │ └── _index.md │ ├── VehicleInteriorColor │ │ └── _index.md │ ├── VehicleInteriorType │ │ └── _index.md │ ├── VehicleModelDate │ │ └── _index.md │ ├── VehicleSeatingCapacity │ │ └── _index.md │ ├── VehicleSpecialUsage │ │ └── _index.md │ ├── WMI │ │ └── _index.md │ ├── Year │ │ └── _index.md │ └── _index.md │ ├── VersionVSS │ ├── Label │ │ └── _index.md │ ├── Major │ │ └── _index.md │ ├── Minor │ │ └── _index.md │ ├── Patch │ │ └── _index.md │ └── _index.md │ ├── Width │ └── _index.md │ └── _index.md ├── vspecjson2markdown.py └── vss.mako.md /.devcontainer/Dockerfile: -------------------------------------------------------------------------------- 1 | # Update the NODE_VERSION arg in docker-compose.yml to pick a Node version: 18, 16, 14 2 | ARG NODE_VERSION=16 3 | FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${NODE_VERSION} 4 | 5 | # VARIANT can be either 'hugo' for the standard version or 'hugo_extended' for the extended version. 6 | ARG VARIANT=hugo 7 | # VERSION can be either 'latest' or a specific version number 8 | ARG VERSION=latest 9 | 10 | # Download Hugo 11 | RUN apt-get update && apt-get install -y ca-certificates openssl git curl && \ 12 | rm -rf /var/lib/apt/lists/* && \ 13 | case ${VERSION} in \ 14 | latest) \ 15 | export VERSION=$(curl -s https://api.github.com/repos/gohugoio/hugo/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4)}') ;;\ 16 | esac && \ 17 | echo ${VERSION} && \ 18 | case $(uname -m) in \ 19 | aarch64) \ 20 | export ARCH=ARM64 ;; \ 21 | *) \ 22 | export ARCH=64bit ;; \ 23 | esac && \ 24 | echo ${ARCH} && \ 25 | wget -O ${VERSION}.tar.gz https://github.com/gohugoio/hugo/releases/download/v${VERSION}/${VARIANT}_${VERSION}_Linux-${ARCH}.tar.gz && \ 26 | tar xf ${VERSION}.tar.gz && \ 27 | mv hugo /usr/bin/hugo 28 | 29 | # Hugo dev server port 30 | EXPOSE 1313 31 | 32 | # [Optional] Uncomment this section to install additional OS packages you may want. 33 | # 34 | # RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ 35 | # && apt-get -y install --no-install-recommends 36 | 37 | # [Optional] Uncomment if you want to install more global node packages 38 | # RUN sudo -u node npm install -g 39 | -------------------------------------------------------------------------------- /.devcontainer/devcontainer.json: -------------------------------------------------------------------------------- 1 | // For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: 2 | // https://github.com/microsoft/vscode-dev-containers/tree/v0.245.2/containers/hugo 3 | { 4 | "name": "Hugo (Community)", 5 | "build": { 6 | "dockerfile": "Dockerfile", 7 | "args": { 8 | // Update VARIANT to pick hugo variant. 9 | // Example variants: hugo, hugo_extended 10 | // Rebuild the container if it already exists to update. 11 | "VARIANT": "hugo_extended", 12 | // Update VERSION to pick a specific hugo version. 13 | // Example versions: latest, 0.73.0, 0,71.1 14 | // Rebuild the container if it already exists to update. 15 | "VERSION": "latest", 16 | // Update NODE_VERSION to pick the Node.js version: 12, 14 17 | "NODE_VERSION": "14" 18 | } 19 | }, 20 | 21 | // Configure tool-specific properties. 22 | "customizations": { 23 | // Configure properties specific to VS Code. 24 | "vscode": { 25 | // Set *default* container specific settings.json values on container create. 26 | "settings": { 27 | "html.format.templating": true 28 | }, 29 | 30 | // Add the IDs of extensions you want installed when the container is created. 31 | "extensions": [ 32 | "bungcip.better-toml", 33 | "davidanson.vscode-markdownlint" 34 | ] 35 | } 36 | }, 37 | 38 | // Use 'forwardPorts' to make a list of ports inside the container available locally. 39 | "forwardPorts": [ 40 | 1313 41 | ], 42 | 43 | // Use 'postCreateCommand' to run commands after the container is created. 44 | // "postCreateCommand": "uname -a", 45 | 46 | // Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. 47 | "remoteUser": "node" 48 | } 49 | -------------------------------------------------------------------------------- /.github/workflows/ci.yml: -------------------------------------------------------------------------------- 1 | # /******************************************************************************** 2 | # * Copyright (c) 2022 Contributors to the Eclipse Foundation 3 | # * 4 | # * See the NOTICE file(s) distributed with this work for additional 5 | # * information regarding copyright ownership. 6 | # * 7 | # * This program and the accompanying materials are made available under the 8 | # * terms of the Eclipse Public License 2.0 which is available at 9 | # * http://www.eclipse.org/legal/epl-2.0 10 | # * 11 | # * SPDX-License-Identifier: EPL-2.0 12 | # ********************************************************************************/ 13 | 14 | name: CI workflow 15 | 16 | on: 17 | workflow_dispatch: 18 | push: 19 | branches: 20 | - "main" 21 | 22 | jobs: 23 | Build-documentation: 24 | runs-on: ubuntu-latest 25 | name: Building documentation 26 | steps: 27 | - name: Checkout repository 28 | uses: actions/checkout@v2 29 | 30 | - name: Setup Hugo 31 | uses: peaceiris/actions-hugo@v2 32 | with: 33 | hugo-version: "0.110.0" 34 | extended: true 35 | 36 | - name: Download theme 37 | run: | 38 | git clone https://github.com/google/docsy.git themes/docsy 39 | 40 | - name: Install theme 41 | working-directory: ./themes/docsy 42 | run: | 43 | npm i 44 | 45 | - name: Build 46 | run: | 47 | export NODE_PATH=$NODE_PATH:`npm root -g` 48 | npm i -g postcss postcss-cli autoprefixer 49 | echo "Build documentation for GitHub Pages" 50 | hugo 51 | 52 | # only publish pages if it's the upstream 53 | - name: Publish to GH Pages 54 | if: github.repository_owner == 'eclipse-leda' 55 | uses: peaceiris/actions-gh-pages@v3 56 | with: 57 | github_token: ${{ secrets.GITHUB_TOKEN }} 58 | publish_dir: ./public 59 | publish_branch: gh_pages 60 | -------------------------------------------------------------------------------- /.github/workflows/ocaas.yaml: -------------------------------------------------------------------------------- 1 | # /******************************************************************************** 2 | # * Copyright (c) 2023 Contributors to the Eclipse Foundation 3 | # * 4 | # * See the NOTICE file(s) distributed with this work for additional 5 | # * information regarding copyright ownership. 6 | # * 7 | # * This program and the accompanying materials are made available under the 8 | # * terms of the Apache License 2.0 which is available at 9 | # * https://www.apache.org/licenses/LICENSE-2.0 10 | # * 11 | # * SPDX-License-Identifier: Apache-2.0 12 | # ********************************************************************************/ 13 | 14 | name: OCaaS Compliance checks 15 | 16 | on: 17 | workflow_dispatch: 18 | workflow_call: 19 | pull_request: 20 | types: 21 | - opened 22 | push: 23 | paths: 24 | - '.ort.yml' 25 | 26 | jobs: 27 | ocaas-scan: 28 | runs-on: ubuntu-22.04 29 | if: github.repository_owner == 'SoftwareDefinedVehicle' 30 | steps: 31 | - name: OCaaS Scans 32 | id: ocaas 33 | uses: docker://osmipublic.azurecr.io/ocaas-ci:latest 34 | continue-on-error: true # Built artifacts also should also be uploaded if the scan finds violations. 35 | with: 36 | args: auth generate-token run start download 37 | env: 38 | OCAAS_USERNAME: ${{ secrets.OCAAS_USERNAME }} 39 | OCAAS_PASSWORD: ${{ secrets.OCAAS_PASSWORD }} 40 | PROJECT_NAME: "Eclipse Leda Website" 41 | PIPELINE_ID: 377 # Your pipeline ID. Provided by the OSMI team. 42 | VCS_URL: ${{ github.server_url }}/${{ github.repository }}.git 43 | VCS_REVISION: ${{ github.ref_name }} 44 | APPLICATION_CATEGORY: "BT11" 45 | BLOCKING: true 46 | REPORT_FILES: SCAN_REPORT_WEB_APP_HTML 47 | OUTPUT_DIR: reports/ 48 | - name: Upload reports 49 | id: upload 50 | uses: actions/upload-artifact@v3 51 | with: 52 | name: oss-compliance-reports 53 | path: reports/ 54 | - name: Check for violations 55 | if: steps.ocaas.outcome != 'success' || steps.upload.outcome != 'success' 56 | run: exit 1 57 | -------------------------------------------------------------------------------- /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "themes-docsy"] 2 | path = themes/docsy 3 | url = https://github.com/google/docsy.git 4 | 5 | -------------------------------------------------------------------------------- /.markdownlint.json: -------------------------------------------------------------------------------- 1 | { 2 | "MD033": false, 3 | "MD013": { 4 | "line_length": 160 5 | } 6 | } -------------------------------------------------------------------------------- /.ort.yml: -------------------------------------------------------------------------------- 1 | # Curation for OSS OCaaS findings. For reference, see : https://github.com/oss-review-toolkit/ort/blob/main/docs/config-file-ort-yml.md 2 | excludes: 3 | paths: 4 | - pattern: "themes/docsy/**" 5 | reason: "BUILD_TOOL_OF" 6 | comment: "Docsy is a theme for Hugo and we are not using the Go module" 7 | -------------------------------------------------------------------------------- /NOTICE.md: -------------------------------------------------------------------------------- 1 | # Notices for Eclipse Leda 2 | 3 | This content is produced and maintained by the Eclipse Leda project. 4 | 5 | * Project home: https://projects.eclipse.org/projects/automotive.leda 6 | 7 | ## Trademarks 8 | 9 | Eclipse Leda is a trademark of the Eclipse Foundation. 10 | 11 | ## Copyright 12 | 13 | All content is the property of the respective authors or their employers. For 14 | more information regarding authorship of content, please consult the listed 15 | source code repository logs. 16 | 17 | ## Declared Project Licenses 18 | 19 | This program and the accompanying materials are made available under the terms 20 | of the Apache License, Version 2.0 which is available at 21 | https://www.apache.org/licenses/LICENSE-2.0. 22 | 23 | SPDX-License-Identifier: Apache-2.0 24 | 25 | ## Source Code 26 | 27 | The project maintains the following source code repositories: 28 | 29 | * https://github.com/eclipse-leda/leda 30 | * https://github.com/eclipse-leda/leda-distro 31 | * https://github.com/eclipse-leda/meta-leda 32 | 33 | ## Third-party Content 34 | 35 | This project leverages the following third party content. 36 | 37 | gohugoio/hugo (0.96.0) 38 | 39 | License: Apache License 2.0 40 | Project: https://github.com/gohugoio/hugo 41 | Source: https://github.com/gohugoio/hugo/releases/tag/v0.96.0 42 | 43 | google/docsy 44 | 45 | License: Apache License 2.0 46 | Project: https://github.com/google/docsy 47 | Source: https://github.com/google/docsy 48 | 49 | 50 | ## Cryptography 51 | 52 | Content may contain encryption software. The country in which you are currently 53 | may have restrictions on the import, possession, and use, and/or re-export to 54 | another country, of encryption software. BEFORE using any encryption software, 55 | please check the country's laws, regulations and policies concerning the import, 56 | possession, or use, and re-export of encryption software, to see if this is 57 | permitted. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Eclipse Leda Documentation 2 | 3 | ![Eclipse Leda](static/assets/eclipse-leda.png) 4 | 5 | This repository contains the sources of the main user documentation of the [Eclipse Leda](https://github.com/eclipse-leda/) project. 6 | 7 | The rendered documentation is available at [https://eclipse-leda.github.io/leda/](https://eclipse-leda.github.io/leda/) 8 | 9 | ## Introduction 10 | 11 | The Eclipse Leda project provides system image "recipes" to deliver a functional and always-available Linux-based image/distribution in the context of SDV (Software Defined Vehicle), by pulling together individual contributor pieces from [Eclipse SDV](https://sdv.eclipse.org/) and the larger OSS community. 12 | 13 | The quickstart images help to learn how the SDV development, test and deployment lifecycle works from an E2E perspective, including the deployment of applications into the container runtimes on constrained embedded devices. 14 | 15 | The ready images are also useful for quickly setting up showcases with virtual or real hardware devices. 16 | 17 | Eclipse Leda provides a Poky-based reference build pipeline and an OpenEmbedded Metalayer [meta-leda](https://github.com/eclipse-leda/meta-leda) for integration into existing Yocto-based projects. 18 | 19 | ## Building the documentation 20 | 21 | Pre-Requisites: 22 | 23 | - Hugo 0.96.0 (preinstalled in DevContainer, otherwise see [Installing Hugo](https://gohugo.io/getting-started/installing/)) 24 | - Theme "docsy" [https://www.docsy.dev/](https://www.docsy.dev/): `git clone https://github.com/google/docsy.git themes/docsy && (cd themes/docsy; npm i)` 25 | - Docsy Dependencies: `npm i -g postcss postcss-cli autoprefixer` 26 | 27 | Building the documentation (in devcontainer): 28 | 29 | - Change to `vss/` and run `./build-vss-docs.sh` to generate the VSS reference documentation 30 | - Run hugo: `hugo server` 31 | - Open browser at [http://localhost:1313/](http://localhost:1313/) 32 | 33 | ### Graphic Conversions 34 | 35 | See [Docsy documentation](https://www.docsy.dev/docs/adding-content/iconsimages/) 36 | 37 | - Inkspace for logo conversion: `apt-get install inkscape` 38 | - `inkscape --export-plain-svg assets/icons/logo.svg assets/logo/logo_02_cmyk.eps` 39 | 40 | ## Contributing 41 | 42 | If you want to contribute bug reports or feature requests, please use *GitHub Issues*. 43 | 44 | ## License and Copyright 45 | 46 | This program and the accompanying materials are made available under the 47 | terms of the Apache License 2.0 which is available at 48 | [https://www.apache.org/licenses/LICENSE-2.0](https://www.apache.org/licenses/LICENSE-2.0) 49 | 50 | For details, please see our license [LICENSE](LICENSE) 51 | -------------------------------------------------------------------------------- /SECURITY: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | This project implements the Eclipse Foundation Security Policy 4 | 5 | * https://www.eclipse.org/security 6 | 7 | ## Reporting a Vulnerability 8 | 9 | Please report vulnerabilities to the Eclipse Foundation Security Team at 10 | security@eclipse.org 11 | -------------------------------------------------------------------------------- /assets/js/ga.js: -------------------------------------------------------------------------------- 1 | import * as params from '@params'; 2 | 3 | 4 | analyticsID = params["googleAnalyticsID"]; 5 | 6 | // If the GA ID was not defined in the hugo config, it would be set as null 7 | // Therefore we should skip execution in those cases 8 | if (analyticsID !== null) { 9 | console.log(`GA enabled for ID ${analyticsID}`); 10 | 11 | const gaScript = document.createElement("script"); 12 | gaScript.src = `https://www.googletagmanager.com/gtag/js?id=${analyticsID}`; 13 | gaScript.async = true; 14 | document.head.appendChild(gaScript); 15 | 16 | window.dataLayer = window.dataLayer || []; 17 | function gtag() { 18 | dataLayer.push(arguments); 19 | } 20 | gtag('js', new Date()); 21 | gtag('config', analyticsID); 22 | } else { 23 | console.log("Google Analytics enabled, but ID was never defined.") 24 | } 25 | -------------------------------------------------------------------------------- /assets/logo/color.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/color.ai -------------------------------------------------------------------------------- /assets/logo/eclipse-leda-logo-cropped.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/eclipse-leda-logo-cropped.png -------------------------------------------------------------------------------- /assets/logo/eclipse-leda-logo-cropped.xcf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/eclipse-leda-logo-cropped.xcf -------------------------------------------------------------------------------- /assets/logo/font.txt: -------------------------------------------------------------------------------- 1 | https://www.dafont.com/olney.font 2 | 3 | -------------------------------------------------------------------------------- /assets/logo/icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/icon.png -------------------------------------------------------------------------------- /assets/logo/leda_mew.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/leda_mew.jpg -------------------------------------------------------------------------------- /assets/logo/logo.cdr: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo.cdr -------------------------------------------------------------------------------- /assets/logo/logo.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo.pdf -------------------------------------------------------------------------------- /assets/logo/logo_01_cmyk.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_01_cmyk.ai -------------------------------------------------------------------------------- /assets/logo/logo_01_cmyk.eps: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_01_cmyk.eps -------------------------------------------------------------------------------- /assets/logo/logo_01_cmyk.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_01_cmyk.pdf -------------------------------------------------------------------------------- /assets/logo/logo_01_rgb.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_01_rgb.ai -------------------------------------------------------------------------------- /assets/logo/logo_01_rgb.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_01_rgb.jpg -------------------------------------------------------------------------------- /assets/logo/logo_01_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_01_rgb.png -------------------------------------------------------------------------------- /assets/logo/logo_02_cmyk.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_02_cmyk.ai -------------------------------------------------------------------------------- /assets/logo/logo_02_cmyk.eps: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_02_cmyk.eps -------------------------------------------------------------------------------- /assets/logo/logo_02_cmyk.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_02_cmyk.pdf -------------------------------------------------------------------------------- /assets/logo/logo_02_rgb.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_02_rgb.ai -------------------------------------------------------------------------------- /assets/logo/logo_02_rgb.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_02_rgb.jpg -------------------------------------------------------------------------------- /assets/logo/logo_02_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/assets/logo/logo_02_rgb.png -------------------------------------------------------------------------------- /assets/scss/_variables_project.scss: -------------------------------------------------------------------------------- 1 | $primary: #403F4C ; 2 | $secondary: #6daed1 ; 3 | $td-enable-google-fonts: false; 4 | -------------------------------------------------------------------------------- /content/en/_index.html: -------------------------------------------------------------------------------- 1 | +++ 2 | title = "Leda" 3 | linkTitle = "Leda" 4 | +++ 5 | 6 | 7 | 15 | 16 | {{< blocks/cover title="Eclipse Leda - Quickstart images for software-defined vehicle development" 17 | image_anchor="center" height="full">}} 18 |
19 | 20 | Get started with Eclipse Leda 21 | 22 |
23 | {{< /blocks/cover >}} 24 | -------------------------------------------------------------------------------- /content/en/docs/__shared/usage-overview.md: -------------------------------------------------------------------------------- 1 | 1. Download [latest Eclipse Leda release](/leda/docs/general-usage/download-releases/) 2 | 2. Run Eclipse Leda 3 | - on [emulated Qemu devices](/leda/docs/general-usage/running-qemu/) or 4 | - on [Raspberry Pi 4](/leda/docs/general-usage/raspberry-pi/) 5 | 3. Configure device, e.g. [provision the device](/leda/docs/device-provisioning/) 6 | 4. Explore the [device tools](/leda/docs/build/misc/tools/) 7 | 5. Develop your first Vehicle App using [Eclipse Velocitas template](https://github.com/eclipse-velocitas/vehicle-app-python-template) 8 | 6. [Deploy a Vehicle App to the device](/leda/docs/app-deployment/) 9 | -------------------------------------------------------------------------------- /content/en/docs/_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-cayman -------------------------------------------------------------------------------- /content/en/docs/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Documentation" 3 | date: 2022-05-09T14:24:56+05:30 4 | no_list: true 5 | --- 6 | 7 | ![Eclipse Leda](/leda/assets/eclipse-leda.png) 8 | 9 | The Eclipse Leda project provides system image "recipes" to deliver a functional and always-available Linux-based image/distribution in the context of SDV (Software Defined Vehicle), by pulling together individual contributor pieces from [Eclipse SDV](https://sdv.eclipse.org/) and the larger OSS community. 10 | 11 | The quickstart images help to learn how the SDV development, test and deployment lifecycle works from an E2E perspective, including the deployment of applications into the container runtimes on constrained embedded devices. 12 | 13 | The ready images are also useful for quickly setting up showcases with virtual or real hardware devices. 14 | 15 | Eclipse Leda provides a Poky-based reference build pipeline and an OpenEmbedded Metalayer [meta-leda](https://github.com/eclipse-leda/meta-leda) for integration into existing Yocto-based projects. 16 | 17 | ## Usage 18 | 19 | {{% readfile "/docs/__shared/usage-overview.md" %}} 20 | 21 | Supported Machines / Build Configurations 22 | 23 | - Emulated Qemu: x86-64, ARM64, ARM 24 | - Raspberry Pi 4 25 | 26 | ## Introduction Video 27 | 28 | {{< youtube id="91hNeQ3kf0w" title="Eclipse Leda - Build your ideas in the playground and make it automotive ready!" >}} 29 | 30 | ## Components Overview 31 | 32 | ![Eclipse Leda Component Overview](/leda/assets/eclipse-leda-arch-overview.png) 33 | 34 | ## Features 35 | 36 | - Publish/Subscribe infrastructure for **local messaging and cloud connectivity** 37 | - Lightweight **container runtime** 38 | - **Vehicle Update Manager** to orchestrate deployments of Vehicle Applications over the air (SOTA) 39 | - **Self Update Agent** for firmware-over-the-air (FOTA) updates 40 | - **Example Vehicle Seat Service** implementation 41 | - **Metrics and logs collector** for Vehicle Apps 42 | 43 | See [About - Features](/leda/docs/about/features/) for more details about current implementation and [About - Roadmap](/leda/docs/about/roadmap/) for our future work. 44 | 45 | ## License and Copyright 46 | 47 | This program and the accompanying materials are made available under the 48 | terms of the Apache License 2.0 which is available at 49 | [https://www.apache.org/licenses/LICENSE-2.0](https://www.apache.org/licenses/LICENSE-2.0) 50 | 51 | For details, please see our license [NOTICE](https://github.com/eclipse-leda/leda/blob/main/NOTICE.md) 52 | -------------------------------------------------------------------------------- /content/en/docs/about/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "About Leda" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | The Eclipse Leda project will provide system image “recipes” to deliver a functional Linux-based image/distribution in the context of SDV (Software Defined Vehicle), by pulling together individual contributons from the SDV and the larger OSS community. 8 | 9 | The Eclipse Leda distribution will work with build scripts, package definitions, image build pipelines, etc, with the goal to pull SDV projects and dependecies from the larger OSS community into a working Linux system. Such system images (or other useful forms of delivery, as determined by the project) will be made available for consumption for anyone who is interested in working with the SDV tech stack. These deliveries take the form of container (base) images, installable/flashable image files, etc (again to be evolved by the project team according to community needs). Also in scope is concise and useful documentation for consumers of the project's deliverables, plus a method of delivering that documentation. 10 | 11 | In the context described above - the ambition of SDV to build a technology ecosystem for software-defined vehicle concern - a prime challenge will be the combination of these initially diverse components into a coherent and useful whole: all the software components in the world will not have the impact needed to transform the automotive industry unless we can make them play together coherently an form a functional portfolio. As a first step towards that goal, this proposal (Eclipse Leda) is for a "SDV distribution" project that pulls together individual contributor pieces from SDV and the larger OSS community, to deliver a functional and always-available Linux-based image/distribution with two primary goals: 12 | 13 | - be the crystalization point for functionally integrating diverse SDV-scope projects into a working whole 14 | 15 | - deliver a continually available, always working starting image for developers interested in getting going with the SDV tech stack 16 | 17 | -------------------------------------------------------------------------------- /content/en/docs/about/architecture/leda-arch-highlevel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/about/architecture/leda-arch-highlevel.png -------------------------------------------------------------------------------- /content/en/docs/about/architecture/leda-arch-overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/about/architecture/leda-arch-overview.png -------------------------------------------------------------------------------- /content/en/docs/about/architecture/leda-arch-reference-implementation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/about/architecture/leda-arch-reference-implementation.png -------------------------------------------------------------------------------- /content/en/docs/about/architecture/leda-build-highlevel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/about/architecture/leda-build-highlevel.png -------------------------------------------------------------------------------- /content/en/docs/about/architecture/leda-deploy-highlevel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/about/architecture/leda-deploy-highlevel.png -------------------------------------------------------------------------------- /content/en/docs/about/features.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Features" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | - **Publish/Subscribe messaging infrastructure for cloud connectivity** by [Eclipse Kanto](https://github.com/eclipse-kanto/) 8 | - local messaging for applications and SDV system components via an MQTT message broker 9 | - connection to a backend messaging hub, such as Azure IoT Hub or the IoT Suite 10 | - device identification and authentication for cloud connectivity by using TLS device certificates 11 | - **Container runtime** 12 | - An OCI-compliant container orchestration for vehicle applications and services by [Eclipse Kanto](https://github.com/eclipse-kanto/) 13 | - [containerd.io](https://containerd.io/) as the default container runtime. Both layers of container runtimes can be exchanged with other implementations 14 | - A **Vehicle Update Manager** to orchestrate deployments of Vehicle Applications, configurations and base operating system updates 15 | - An example Vehicle Seat Service implementation to showcase 16 | - the [Eclipse Velocitas](https://projects.eclipse.org/projects/automotive.velocitas) programming model, 17 | - the [Eclipse Kuksa.VAL](https://github.com/eclipse/kuksa.val) vehicle databroker and 18 | - the [Covesa Vehicle Signal Specification](https://github.com/COVESA/vehicle_signal_specification) 19 | - the communication with basic vehicle communication networks such as CAN-Bus (CAN Feeder) 20 | - A **Self Update Agent** for firmware-over-the-air (FOTA) updates, using an A/B deployment strategy 21 | - Integration with [RAUC](https://www.rauc.io/) 22 | - An [OpenTelemetry collector](https://github.com/open-telemetry/) and example configurations to collect and publish logs and metrics of containerized Vehicle Applications to the cloud backend for further processing 23 | 24 | The features of the reusable build recipes implemented as an [OpenEmbedded](https://www.openembedded.org) metalayer `meta-leda` are: 25 | 26 | - Build recipes for a [Yocto](https://www.yoctoproject.org/)-based distribution to build SDV-related software components 27 | - Build recipes for customizations of the target device's storage structure to enable A/B system updates 28 | - Build recipes for pre-packaging container images into the device during the manufacturing process to minimize initial online provisioning time 29 | - A customized minimal setup for use on constrained devices and a full setup with convenient developer tools 30 | - Ready images for virtual devices, for automated testing and evaluation purposes, eg QEMU ARM-64 31 | - Ready images for physical devices, for evaluation and demo purposes, eg Raspberry Pi 4 32 | -------------------------------------------------------------------------------- /content/en/docs/about/releases/0.1.0/leda-0.1.0-plan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Release Plan 0.1.0" 3 | date: 2023-04-12T14:24:56+05:30 4 | weight: 100 5 | --- 6 | 7 | The release plan is available at [https://projects.eclipse.org/projects/automotive.leda/releases/0.1.0](https://projects.eclipse.org/projects/automotive.leda/releases/0.1.0) 8 | 9 | ## Release Date 10 | 11 | -Thursday, June 1, 2023- - We didn't meet the planned release date. Work is in progress on IT build infrastructure and OSS IP and license compliance. 12 | 13 | New: Tuesday, August 1, 2023 14 | 15 | ## Deliverables 16 | 17 | The team plans to deliver the following features: 18 | 19 | - Leda Quickstart Images for Qemu (x86_64, arm64), Raspberry Pi and Docker 20 | - Yocto / OpenEmbedded meta-layer for better reusability of the Eclipse SDV Vehicle.Edge stack in customized distributions for constrained devices 21 | - User documentation (Reference, Example Use Cases) 22 | - Automated system tests using Robot Framework 23 | - IP scanning with Eclipse Oniro Compliance Toolchain 24 | - Pre-Integrated Eclipse SDV Vehicle.Edge stack 25 | 26 | The core SDV.EDGE stack in Leda would contain the following components for the first release (based upon availability): 27 | 28 | - Eclipse Kuksa.VAL: Data Broker 29 | - Eclipse Kanto: Container Management, Vehicle Update Manager 30 | - Eclipse Leda Incubator: Cloud Connector (Azure), Self Update Agent, Utilities (e.g kantui) 31 | 32 | The following components are not yet released in public or did not yet finished the project review, and may only be added to the release on shorter notice: 33 | 34 | - (Eclipse Backend-Function-Bindings) 35 | - (Eclipse SommR) 36 | - (OTA Client) 37 | 38 | ## Compatibility 39 | 40 | Compatibility to previous versions is not considered for this first release. 41 | 42 | ## Internationalization 43 | 44 | No efforts towards i18n are done in this release. 45 | 46 | ## Target Environments 47 | 48 | - Linux (virtual, qemu) 49 | - Raspberry Pi 4 (consumer grade) -------------------------------------------------------------------------------- /content/en/docs/about/releases/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Releases" 3 | date: 2023-04-12T14:24:56+05:30 4 | weight: 10 5 | --- 6 | 7 | The Eclipse Leda project follows the Eclipse Release process. 8 | Please see [Eclipse Project handbook](https://www.eclipse.org/projects/handbook/#release) for details about the process. 9 | 10 | The release plans overview for Eclipse Leda is available at [https://projects.eclipse.org/projects/automotive.leda/governance](https://projects.eclipse.org/projects/automotive.leda/governance) 11 | 12 | -------------------------------------------------------------------------------- /content/en/docs/about/roadmap.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Roadmap" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | - Initial Open Source contribution expected by Q2 2022 (Done) 8 | - A first milestone build is expected end of 2022 (Done) 9 | - Plan for the first release cycle to be created in Q1/2023 (In Progress - Q2/2023) 10 | - Release cycles are planned every 3-6 months 11 | - Release planning will be conducted together with corresponding Eclipse projects 12 | 13 | ## Backlog 14 | 15 | The Leda team maintains a backlog roadmap using GitHub projects at [https://github.com/orgs/eclipse-leda/projects/1/views/1](https://github.com/orgs/eclipse-leda/projects/1/views/1) 16 | 17 | ## Future Work 18 | 19 | The project intends to be the integration and collaboration platform for Software defined Vehicle functionality. 20 | 21 | Exemplary future work: 22 | 23 | - Migrate to official Eclipse Kanto releases for Cloud Connector, Container Management and Vehicle Update Manager 24 | - Include reference implementations from the [Eclipse Software Defined Vehicle working group](https://projects.eclipse.org/working-group/eclipse-software-defined-vehicle) projects: 25 | - Eclipse Velocitas 26 | - Eclipse Kuksa 27 | - Eclipse SommR 28 | - Eclipse Chariott 29 | - Eclipse Muto 30 | - Eclipse Backend function Bindings (BfB) 31 | - Eclipse SDV Blueprints 32 | - Include and showcase more features regarding development, operation and monitoring of Vehicle Services and Vehicle Applications 33 | 34 | If you have feedback, please use [GitHub Issues](https://github.com/eclipse-leda/) 35 | -------------------------------------------------------------------------------- /content/en/docs/app-deployment/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Vehicle Applications" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | This chapter contains use cases and examples for SDV applications. 8 | 9 | Some of these example are taken from the following sources: 10 | 11 | - [Digital.Auto](https://digital.auto) and its [playground](https://digitalauto.netlify.app/) 12 | - [Eclipse Velocitas tutorials](https://eclipse.dev/velocitas/docs/tutorials/) 13 | - [Eclipse Kuksa.VAL examples](https://github.com/eclipse/kuksa.val.services) 14 | - [Eclipse SDV Blueprints](https://projects.eclipse.org/projects/automotive.sdv-blueprints) 15 | - [Eclipse Chariott examples](https://github.com/eclipse-chariott/chariott/tree/main/examples/applications) 16 | -------------------------------------------------------------------------------- /content/en/docs/app-deployment/carsim/carsim-arch-overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/carsim/carsim-arch-overview.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/carsim/carsim-databroker-cli.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/carsim/carsim-databroker-cli.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/carsim/carsim-databroker-cli2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/carsim/carsim-databroker-cli2.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/carsim/kantui_carsim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/carsim/kantui_carsim.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/carsim/kantui_driversim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/carsim/kantui_driversim.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/carsim/kinetic.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/carsim/kinetic.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/cloud2device-messages/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Cloud2Device Messages" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 20 5 | --- 6 | 7 | ![c2d-overview](c2d-architecture-overview.png) 8 | 9 | In order to verify that the device and the cloud connector can successfully receive messages sent by the cloud backend, we will send a dummy message to the device. 10 | 11 | ## Pre-Requisites 12 | 13 | - Device is up and running, e.g by [running in qemu](/leda/docs/general-usage/running-qemu/) 14 | - Eclipse Leda has successfully booted 15 | - The device has been provisioned and configured, see [Device Provisioning](/leda/docs/device-provisioning/) 16 | 17 | ## Validating configuration 18 | 19 | First, let's check that the cloud connection is active. 20 | 21 | - Login as `root` 22 | - Run sdv-health and check for the *SDV Connectivity* section: 23 | 24 | ```bash 25 | sdv-health 26 | ``` 27 | 28 | ![sdv-health-connectivity](sdv-health-connectivity.png) 29 | 30 | - Start watching the output of the cloud connector: 31 | 32 | ```bash 33 | kantui 34 | ``` 35 | 36 | - Select the `cloud-connector` container and press `L` to watch the logs 37 | 38 | > *Note:* When an unknown type of message is received, the cloud connector will log an error: 39 | > 40 | > ```text 41 | > 2022/04/13 16:04:41.911727 [agent] ERROR Handler returned error err="cannot deserialize cloud message: invalid character 'H' looking for beginning of value 42 | > ``` 43 | 44 | - Start watching on the MQTT message broker: 45 | 46 | ```bash 47 | mosquitto_sub -h localhost -t '#' --pretty -v 48 | ``` 49 | 50 | > *Note:* When a known type of message is received, the cloud connector will forward the message to the MQTT broker into the corresponding topic `$appId/$cmdName` 51 | 52 | ## Sending a Device Message 53 | 54 | - Go to the Web Console of Azure IoT Hub 55 | - Select the device 56 | - Click on "Send Message" 57 | - Enter a C2D payload and click "Send" 58 | 59 | Alternatively, on command line, use the Azure CLI client. Replace `DeviceId` and `IotHubName` with the appropriate names of your IoT Hub and device. 60 | 61 | ```bash 62 | az iot device c2d-message send \ 63 | --device-id ${DeviceID} \ 64 | --hub-name ${IotHubName} \ 65 | --data 'Hello World' 66 | ``` 67 | -------------------------------------------------------------------------------- /content/en/docs/app-deployment/cloud2device-messages/c2d-architecture-overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/cloud2device-messages/c2d-architecture-overview.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/cloud2device-messages/sdv-health-connectivity.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/cloud2device-messages/sdv-health-connectivity.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/dog-mode/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Dog Mode" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | The **Dog Mode** use case has been derived from the [Eclipse Velocitas Dog Mode example](https://eclipse.dev/velocitas/docs/about/use_cases/dog_mode/) and the [Eclipse Kuksa.VAL HVAC Service example](https://github.com/eclipse/kuksa.val.services/tree/main/hvac_service). 8 | 9 | ## Description 10 | 11 | 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. 12 | 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. 13 | 14 | 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. 15 | 16 | ## Architecture Overview 17 | 18 | ![Leda Dog Mode Use Case](dogmode.png) 19 | 20 | - Cloud or mobile trigger: not part of the Leda image, but can be simulated by issueing MQTT messages 21 | - Eclipse Velocitas - Vehicle Application: **Dog Mode** (to be deployed by user as part of the Velocitas tutorial) 22 | - Eclipse Kuksa.VAL - Example Service: **HVAC Service** (pre-installed) 23 | - Eclipse Kuksa.VAL - **Data Broker** (pre-installed) 24 | 25 | ## Getting started 26 | 27 | 1. Follow the Velocitas tutorial: build and deploy your clone of the [dog mode example](https://eclipse.dev/velocitas/docs/about/use_cases/dog_mode/) 28 | 2. Download and run the Leda quickstart image 29 | 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](https://github.com/eclipse-leda/meta-leda/blob/main/meta-leda-components/recipes-sdv/eclipse-leda/kanto-containers/example/seatservice.json). Details on the deployment can be found in [Leda Vehicle Applications](/leda/docs/app-deployment/velocitas/) 30 | 4. Ensure the databroker and the service containers are running and you know how to check their log files 31 | 5. Monitor vehicle data: `mosquitto_sub -t dogmode/display` 32 | 6. Enable dog mode by using the `databroker-cli` 33 | 34 | connect 35 | set Vehicle.Cabin.DogMode 1 36 | -------------------------------------------------------------------------------- /content/en/docs/app-deployment/dog-mode/dogmode.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/dog-mode/dogmode.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/kuksa-databroker/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "VSS & Kuksa.VAL" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | To generically interact with the Vehicle Signals which are managed in the Eclipse Kuksa.VAL Databroker, 8 | you can either use the natively installed `databroker-cli` command line tool, or use the CLI tool from an updated and released containerized image. 9 | 10 | ## Kuksa Databroker CLI 11 | 12 | To install a new version of the Kuksa Databroker CLI container, follow these steps: 13 | 14 | 1. Create the container in Kanto: 15 | 16 | kanto-cm create --i --t --network=host --name=databroker-cli ghcr.io/eclipse/kuksa.val/databroker-cli:master 17 | 18 | 2. Start the command line tool within a container in interactive mode: 19 | 20 | kanto-cm start --a --i --name databroker-cli 21 | 22 | 3. In the databroker shell, connect to the databroker via the URL `http://127.0.0.1:30555/`: 23 | 24 | connect http://127.0.0.1:30555/ 25 | 26 | ![Kuksa Databroker CLI Container](kuksa-databroker-cli.png) 27 | 28 | ## Kuksa Client 29 | 30 | To install a new version of the Kuksa Client container, follow these steps: 31 | 32 | 1. Pull the container image 33 | 34 | ctr --namespace kanto-cm image pull ghcr.io/eclipse/kuksa.val/kuksa-client:master 35 | 36 | 2. Create the container in Kanto Namespace: 37 | 38 | ctr --namespace kanto-cm container create --net-host --tty ghcr.io/eclipse/kuksa.val/kuksa-client:master kuksa-client 39 | 40 | 3. Start the container in detached mode: 41 | 42 | ctr --namespace kanto-cm tasks start --detach kuksa-client 43 | 44 | 4. Start the command line tool with additional command line options: 45 | 46 | ctr --namespace kanto-cm tasks exec --tty --exec-id sometask kuksa-client /kuksa-client/bin/kuksa-client --port 30555 --protocol grpc --insecure 47 | -------------------------------------------------------------------------------- /content/en/docs/app-deployment/kuksa-databroker/custom-vss-mappings/kuksa-databroker-cli.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/kuksa-databroker/custom-vss-mappings/kuksa-databroker-cli.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/kuksa-databroker/custom-vss-mappings/vss-overlay.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/kuksa-databroker/custom-vss-mappings/vss-overlay.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/kuksa-databroker/kuksa-databroker-cli.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/kuksa-databroker/kuksa-databroker-cli.png -------------------------------------------------------------------------------- /content/en/docs/app-deployment/seat-adjuster/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Seat Adjuster" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | The **seat adjuster** is an example to showcase how to create a vehicle application which senses and actuates signals in the vehicle 8 | for Eclipse Leda with help of Eclipse Velocitas and Eclipse Kuksa 9 | . The aim is not to build the best available seat adjuster application possible but to show how one can use the applied technologies 10 | to build a companion app for the interaction with a vehicle. 11 | If you are new to the concepts around Eclipse SDV and the mentioned projects 12 | we recommend to read the [SDV Tutorial](/leda/docs/general-usage/sdv-introduction/) first. 13 | 14 | ## Description 15 | 16 | The idea of the seat adjuster application is to have a custom application to move the driver seat to positions defined 17 | in a driver profile hosted by a third-party web service. 18 | 19 | ![Leda Seat Adjuster Use Case](./seatadjuster.png) 20 | 21 | The setup contains the following components: 22 | 23 | - Cloud or mobile trigger: not part of the Leda image, but we simulate it by issuing MQTT messages 24 | - **Seat Adjuster** : Developed with Eclipse Velocitas to be deployed by user 25 | - Eclipse Kuksa.val - **KUKSA Databroker** (pre-installed with Eclipse Leda) 26 | - **Mock Service**: Example provider for Eclipse Kuksa.VAL which mocks the behavior of the vehicle. 27 | - Seat ECU and the separate Seat Motor hardware can be emulated using a virtual CAN-Bus, which is beyond the scope of this guide. 28 | 29 | In the following paragraphs, we next introduce the [architecture and the assumed data flow](architecture-seat-adjuster) 30 | before we explain the [development](develop-seat-adjuster) and [deployment](deploy-seat-adjuster) steps. 31 | If you are more interested in the general development steps, you may directly jump to the [develop seat adjuster](develop-seat-adjuster). 32 | -------------------------------------------------------------------------------- /content/en/docs/app-deployment/seat-adjuster/seatadjuster.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/app-deployment/seat-adjuster/seatadjuster.png -------------------------------------------------------------------------------- /content/en/docs/build/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Building Leda" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 9 5 | --- 6 | 7 | Running BitBake to build your own images requires some extra setup on the build machine. Please see the following chapters for more information about the build process itself and how to setup a development and build infrastructure. 8 | 9 | ![Build Shell](build-terminal.png) 10 | 11 | If you are interested to contribute or to get in touch with us, please see our [Community](/leda/docs/project-info/community/) pages and [Contribution Guidelines](/leda/docs/project-info/contribution-guidelines/). 12 | 13 | For reporting security vulnerabilities, please follow our [Security Policy](/leda/docs/project-info/security/). 14 | -------------------------------------------------------------------------------- /content/en/docs/build/build-terminal.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/build-terminal.png -------------------------------------------------------------------------------- /content/en/docs/build/compliance/a4f_leda_overview_20230621.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/compliance/a4f_leda_overview_20230621.png -------------------------------------------------------------------------------- /content/en/docs/build/dev-and-maintenance/rust/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Rust Utils" 3 | date: 2023-01-03T17:24:56+05:30 4 | weight: 1 5 | --- -------------------------------------------------------------------------------- /content/en/docs/build/dev-and-maintenance/shell/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Shell Utils" 3 | date: 2023-01-03T17:24:56+05:30 4 | weight: 1 5 | --- -------------------------------------------------------------------------------- /content/en/docs/build/devenv/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Setup development environment" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | There are multiple variants on how to set up a build environment: 8 | 9 | - with [GitHub Codespaces](/leda/docs/build/devenv/github-codespaces/) - recommended for developers with restricted internet access, such as corporate proxies, or with Windows hosts 10 | - with [VSCode DevContainer](/leda/docs/build/devenv/vscode-devcontainer/) - recommended for Linux hosts 11 | - Custom setup - for teams 12 | -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-codespaces/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Codespaces" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | # Setting up Development Environment in GitHub Codespaces 8 | 9 | ## Install the GitHub Codespaces Extension 10 | 11 | *Note:* When using our DevContainer, the *GitHub Codespaces* extension is pre-installed. 12 | 13 | - Start VSCode 14 | - Go to *Extensions* 15 | - Search for "GitHub Codespaces" 16 | - Click *Install* 17 | 18 | Alternatively, create a new codespace via the GitHub web interface: 19 | 20 | ![](github-code-new-codespace.png) 21 | 22 | Select a big enough machine type for Yocto/BitBake, e.g. 16 CPU. You need at leasst 50GB disk space. 23 | 24 | ![](github-codespaces-remote-explorer.png) 25 | 26 | ## Building Leda in a Github Codespace 27 | 28 | After successfully obtaining and connecting to a codespace you can build Leda either with kas or manually: 29 | 30 | - To build with kas follow the instructions at: [Building with kas](/leda/docs/build/devenv/build-kas-manually/#building-with-kas) 31 | 32 | - To build manually: [Building manually](/leda/docs/build/devenv/build-kas-manually/#building-manually) 33 | 34 | 35 | ## Private Repositories 36 | 37 | When using GitHub Codespaces with submodules and private repositories, 38 | a separate tool for git authentication is required (see [VSCode issue #109050](https://github.com/microsoft/vscode/issues/109050)), as the authentication token provided to the GitHub Codespaces virtual machine only allows access to the main repository. 39 | 40 | Git Credential Manager: 41 | https://aka.ms/gcm 42 | 43 | Installation: 44 | ``` 45 | curl -LO https://raw.githubusercontent.com/GitCredentialManager/git-credential-manager/main/src/linux/Packaging.Linux/install-from-source.sh && 46 | sh ./install-from-source.sh && 47 | git-credential-manager-core configure 48 | ``` 49 | -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-codespaces/github-code-new-codespace.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/devenv/github-codespaces/github-code-new-codespace.png -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-codespaces/github-codespaces-advanced.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Advanced topics" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | ## Git Authentication 8 | 9 | For private repositories, we need to separately authenticate against the submodule repositories, as 10 | GitHub Codespaces will only inject a token with access rights to the current repository. 11 | 12 | 1. Change to the users home directory 13 | 14 | ```bash 15 | cd ~ 16 | ``` 17 | 18 | 2. Install [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) 19 | 20 | ```bash 21 | curl -LO https://raw.githubusercontent.com/GitCredentialManager/git-credential-manager/main/src/linux/Packaging.Linux/install-from-source.sh && 22 | sh ./install-from-source.sh && 23 | git-credential-manager-core configure 24 | ``` 25 | 26 | 3. Configure a credential store typ, e.g. `git config --global credential.credentialStore plaintext` 27 | 4. Verify with `git config --global -l`, it should show git-credential-manager-core as the credential helper. 28 | 29 | ## Update the submodules 30 | 31 | Run `git submodule update --recursive` 32 | 33 | See [VSCode Issue #109050](https://github.com/microsoft/vscode/issues/109050) for details. 34 | 35 | ## Setup skopeo 36 | 37 | Skopeo is needed to download various files during the build: 38 | 39 | ```bash 40 | sudo mkdir -p /run/containers/1000 41 | sudo chmod a+w /run/containers/1000 42 | skopeo login ghcr.io --authfile ~/auth.json --username 43 | ``` 44 | 45 | Enter your token when asked for the password. 46 | -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-codespaces/github-codespaces-remote-explorer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/devenv/github-codespaces/github-codespaces-remote-explorer.png -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-runner/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "GitHub Runner" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | # Create a new GitHub Runner for this repo 7 | 8 | Start with creating a new azure VM: 9 | - Ubuntu Server Latest, currently 20.04 10 | - Size Standard D16ds v5 11 | - The admin user should be called "runner" 12 | 13 | Once the VM is ready: 14 | 1. Stop the VM 15 | 2. Go to "Disk" and resize the OS disk to 512 GB 16 | 3. Start the VM again 17 | 18 | # Run the script to setup the runner 19 | 20 | Log on to the VM as runner. Either copy the `scripts/PrepVMasGHRunner.sh` onto the VM or create a new script: 21 | ```bash 22 | nano prep.sh 23 | ``` 24 | 25 | Copy the content of the PrepVMasGHRunner.sh from this repo into the new file, save it and make it executable: 26 | ```bash 27 | chmod 755 prep.sh 28 | ``` 29 | 30 | Call it with the token and the next available nummer, see below how to get this items: 31 | ```bash 32 | ./prep.sh "ASYVOMU........DTCFCMBA" 3 33 | ``` 34 | 35 | In the Azure portal go the VM, go to the "network" section and delete the rule opening port 22. 36 | Congratulation, you are done! 37 | 38 | # How to get the token and the number to call the script 39 | 40 | In the repo, go to "Settings" -> "Actions". You see the currently provisioned runners: 41 | 42 | ![Alt text](nextnumber.png "Find next number") 43 | 44 | Pick the next number and pass it to the script. 45 | 46 | To get the token press the green button in the above screenshot. The token is in the command: 47 | 48 | ![Alt text](token.png "Get the token") 49 | 50 | -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-runner/nextnumber.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/devenv/github-runner/nextnumber.png -------------------------------------------------------------------------------- /content/en/docs/build/devenv/github-runner/token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/devenv/github-runner/token.png -------------------------------------------------------------------------------- /content/en/docs/build/devenv/vscode-devcontainer.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "VSCode DevContainer" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | ## Preparation 8 | 9 | - Obtain the [Docker Engine](https://docs.docker.com/engine/install/) for your distribution and add your non-privileged user to the docker group (`sudo usermod -aG docker $USER` ) 10 | - Install [Visual Studio Code](https://code.visualstudio.com/download ) 11 | 12 | ## Visual Studio Code: Development Containers 13 | 14 | - Open Visual Studio Code 15 | - Open Command Palette (`F1`) and select `Clone repository in Container Volume` 16 | - Select `eclipse-leda/meta-leda` and the main branch. 17 | - Adapt proxy configurations if necessary (`.devcontainer/proxy.sh`) 18 | 19 | *For a clean remote build machine, you may want to [set up a development environment on GitHub CodeSpaces](/leda/docs/build/devenv/github-codespaces/)* 20 | 21 | ## Building Leda in a VSCode DevContainer: 22 | 23 | After successfully setting up your DevContainer you can build Leda either with kas or manually: 24 | 25 | - To build with kas follow the instructions at: [Building with kas](/leda/docs/build/devenv/build-kas-manually/#building-with-kas) 26 | 27 | - To build manually: [Building manually](/leda/docs/build/devenv/build-kas-manually/#building-manually) 28 | 29 | 30 | ## Authentication 31 | 32 | The build process requires online connection and you must be authenticated to access private repositories. 33 | 34 | 1. Create a GitHub Personal Access Token (PAT) at https://github.com/settings/tokens and grant `read:packages` permission 35 | 2. Use `Configure SSO` and authorize your PAT for the organization 36 | 3. On the build host, authenticate to ghcr.io: `skopeo login ghcr.io --authfile ~/auth.json --username ` and enter the PAT as password 37 | - You may need to create the folder where skopeo is storing authentication information beforehand: 38 | ```bash 39 | sudo mkdir -p /run/containers/1000 40 | sudo chmod a+w /run/containers/1000 41 | ``` 42 | 4. Start the bitbake build process 43 | 44 | -------------------------------------------------------------------------------- /content/en/docs/build/ghcsco.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/ghcsco.png -------------------------------------------------------------------------------- /content/en/docs/build/github/github-workflow-optimizations.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/github/github-workflow-optimizations.png -------------------------------------------------------------------------------- /content/en/docs/build/github/github-workflow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/github/github-workflow.png -------------------------------------------------------------------------------- /content/en/docs/build/misc/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Miscellaneous" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 9 5 | --- -------------------------------------------------------------------------------- /content/en/docs/build/misc/diskusage.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Resource Consumptions" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | ## Baseline (no apps installed) 8 | 9 | Baseline: 400 MB 10 | 11 | Installed components: 12 | 13 | - Container Management: runc, containerd, container-management 14 | - System Services: systemd, openssh, mosquitto, mosquitto-clients 15 | - No cloud connector or edgecontainerd yet. 16 | - No self update agent 17 | - No containers, no vehicle apps etc. 18 | 19 | ```bash 20 | root@qemux86-64:/bin# df -h 21 | Filesystem Size Used Avail Use% Mounted on 22 | /dev/root 2.5G 506M 1.8G 22% / 23 | ``` 24 | 25 | - Memory Usage: 200MB 26 | 27 | ```bash 28 | root@qemux86-64:/# free 29 | total used free shared buff/cache available 30 | Mem: 1.9G 329.6M 1.4G 16.6M 222.2M 1.6G 31 | Swap: 32 | ``` 33 | 34 | ## Component Details 35 | 36 | Dependencies 37 | 38 | - cni (container networking): 51 MB 39 | - containerd-ctr: 26 MB 40 | - containerd: 46 MB 41 | - dapr cli: 38 MB 42 | - helm cli: 43 MB 43 | - runc: 10 MB 44 | 45 | SDV Components 46 | 47 | - vehicle-data-cli: 2.3 MB (dynamic) 48 | 49 | Medium: 50 | 51 | - Linux Kernel (Poky minimal / Leda distro kernel): 8 MB / 21 MB 52 | - oci-image-tool: 9 MB 53 | - oci-runtime-tool: 7 MB 54 | - sshd: 1 MB 55 | - libstdc++: 2 MB 56 | - lic: 2 MB 57 | - libcrypto: 3 MB 58 | - containerd-shim: 7 MB 59 | - containerd-shim-runc-v1: 9 MB 60 | - containred-shim-runc-v2: 9 MB 61 | - libsystemd: 1 MB 62 | - busybox: 1 MB 63 | -------------------------------------------------------------------------------- /content/en/docs/build/misc/partitioning/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Partition Layout" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | The bootable Leda Quickstart images are disk image with multiple partitions: 8 | 9 | - Two bootloader partitions, to enable A/B update process 10 | - A separate partition to hold bootloader status information 11 | - An optional rescue partition with basic operating system and tooling 12 | - Two rootfs partitions with a full installation of the operating system, to enable A/B update process 13 | - A data partition for storing container runtime data 14 | 15 | ## Partition Layout for QEMU x86-64 16 | 17 | The x86_64 image uses GRUB as a bootloader and the partition layout is as follows: 18 | 19 | ![Leda Disk Layout for QEMU x86-64](leda-disk-layout-qemux86-64.png) 20 | 21 | ## Partition Layout for QEMU ARM-64 22 | 23 | The partition layout for QEMU ARM-based images are comparable, except: 24 | 25 | - Bootloader is replaced with U-Boot 26 | 27 | ## Partition Layout for Raspberry Pi 28 | 29 | The partition layout for Raspberry Pi images are comparable, except: 30 | 31 | - Bootloader is replaced with U-Boot 32 | - The last partition (the data partition) is marked as growable, to allow the use of the larger SD-Card capacities for container runtime data -------------------------------------------------------------------------------- /content/en/docs/build/misc/partitioning/leda-disk-layout-qemux86-64.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/misc/partitioning/leda-disk-layout-qemux86-64.png -------------------------------------------------------------------------------- /content/en/docs/build/release/validation.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Validating" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | ## Validating the release 8 | 9 | Steps to validate if a release is properly working: 10 | 11 | 1. Create a new pre-release from your branch 12 | 2. Download the release artifacts onto a clean system. 13 | 14 | Do not use your build environment, to minimize the impact of existing environment configuration from BitBake etc. 15 | 3. Run the `run-leda` scripts to execute Qemu 16 | 17 | *Note: You should test each of the release archives, for each target machine.* 18 | 4. Follow the [Device Provisioning](/leda/docs/device-provisioning/) guide 19 | 5. Perform some verification tests (see below) 20 | 6. Cleanup: Delete the pre-release and the git tag: 21 | 22 | git push --delete origin 23 | 24 | ## Ideas for manual verification steps 25 | 26 | *Note: These are just for manual testing, as we intend to extend the automated tests as much as possible.* 27 | 28 | - Operating system level 29 | - Run `sdv-health` on the shell 30 | - Verify disk partitions and RAUC status, e.g. `rauc status` 31 | - Verify network interface and CAN-Bus with `ip addr` 32 | - Container runtime 33 | - Check status of containers with `kantui` 34 | -------------------------------------------------------------------------------- /content/en/docs/build/run-build.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Run the build" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 3 5 | --- 6 | 7 | ## Run the full build 8 | 9 | To setup the environment and build the Leda image, please refer to: [Setup development environment](/leda/docs/build/devenv/). 10 | 11 | ## Running QEMU from existing build 12 | 13 | - Use `kas shell -c "runqemu qemux86-64 ovmf kvm nographic" ` to execute the image. 14 | - Replace `qemux86-64` with one of the other qemu machines, such as `qemuarm64` 15 | - Use the keyword `slirp` to enable user-networking which does not require root privileges on the host. `tun` is default but requires setup on the host. 16 | - Continue with [Device Provisioning](/leda/docs/device-provisioning/) 17 | 18 | ### Variations of runqemu command line 19 | 20 | - Use `runqemu ovmf` 21 | - `ovmf` will enable the UEFI support for IA32 (x86) and X64 (x86-64) guests, for testing the dual-boot capabilities and SDV Self-Update mechanisms 22 | - All other options are now part of the default Leda distribution configuration (see *leda-qemu-settings.inc*) 23 | - Continue with [Device Provisioning](/leda/docs/device-provisioning/) 24 | 25 | ## Running QEMU in the background 26 | 27 | To start QEMU in the background enter, use `nohup` and bring the process into the background. 28 | 29 | ```bash 30 | nohup runqemu qemux86-64 nographic qemuparams="-m 2048 -pidfile qemu.pid" & 31 | ``` 32 | 33 | The image is then reachable via `ssh root@192.168.7.2` 34 | This will write a file qemu.pid in the current directory including the process ID of QEMU. Once done, ``kill -9 `` kills the process. 35 | 36 | ## Running with kas-shell 37 | 38 | If you've chosen to build the Leda image with kas, you can use the kas-shell to run QEMU, with kas setting up the environment for you. To do that change to the main working directory and run: 39 | 40 | ```bash 41 | kas shell -c 'runqemu slirp nographic ovmf sdv-image-full' 42 | ``` 43 | 44 | ## DHCP Configuration 45 | 46 | As the Leda Quickstart image will try to retrieve its IP address via DHCP broadcast request, it is good to run a DHCP daemon on the host, listening on the respective TAP network interface of QEMU. This will then simulate a LAN with DHCP server and let's us control which IP address gets assigned to multiple QEMU instances. 47 | 48 | The [run-dhcp.sh](https://github.com/eclipse-leda/leda-distro/blob/main/scripts/run-dhcp.sh) utility will run an ISC-DHCP server on the host. The default configuration has a couple of MAC addresses preconfigured. 49 | -------------------------------------------------------------------------------- /content/en/docs/build/runqemu/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Runqemu" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 5 5 | --- 6 | 7 | {{% pageinfo color="warning" %}} 8 | The content of this page has been marked **outdated** by the core development team. 9 | 10 | If you would like to contribute and help keeping this documentation up to date, 11 | please fork [https://github.com/eclipse-leda/leda](https://github.com/eclipse-leda/leda/fork) 12 | and create a pull request. 13 | 14 | Check the Eclipse [Get Involved!](https://www.eclipse.org/contribute/) FAQ for pre-requisites 15 | and the [Eclipse Leda Contribution Guidelines](https://eclipse-leda.github.io/leda/docs/project-info/contribution-guidelines/) 16 | for general information. 17 | {{% /pageinfo %}} 18 | 19 | QEMU's command line option can get quiet complex. Yocto is providing a convenient wrapper script called `runqemu`, which takes configurations into account which have been populated during the build process and also takes care of TAP networking setup and teardown. Unfortunately, it can only be used within an OpenEmbedded build environment. 20 | 21 | Running without runqemu: when you need more control over qemu options 22 | 23 | ```bash 24 | qemu-system-x86_64 -kernel .\bzImage-qemux86-64.bin -nographic -m 2G -append "console=ttyS0 root=/dev/vda1" -drive file=.../sdv-image-full-qemux86-64.ext4 25 | ``` 26 | 27 | Running with runqemu: simple and some convenient flags are supported 28 | 29 | runqemu ovmf sdv-image-full 30 | 31 | 32 | Running with leda: no options, runs the default settings only 33 | 34 | leda 35 | 36 | ![](qemu-runner-script.png) 37 | 38 | ## Enabling KVM for better performance 39 | 40 | The performance of qemux86_64 is much better when KVM can be used. 41 | Try running with: 42 | 43 | runqemu ovmf kvm 44 | 45 | *Note: You may need to set up KVM for your host machine first, please refer to [How to enable KVM for Poky qemu](https://wiki.yoctoproject.org/wiki/How_to_enable_KVM_for_Poky_qemu)* 46 | 47 | ```bash 48 | /workspaces/leda-distro/build-sdv-x86_64 (imageformatcleanup ✗) $ ls -al /dev/kvm 49 | crw-rw---- 1 root kvm 10, 232 May 16 06:46 /dev/kvm 50 | ``` 51 | -------------------------------------------------------------------------------- /content/en/docs/build/runqemu/qemu-runner-script.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/runqemu/qemu-runner-script.png -------------------------------------------------------------------------------- /content/en/docs/build/tests/gh-robot-report-with-failed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/tests/gh-robot-report-with-failed.png -------------------------------------------------------------------------------- /content/en/docs/build/tests/leda-tests-overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/build/tests/leda-tests-overview.png -------------------------------------------------------------------------------- /content/en/docs/build/tests/robot-keywords.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Robot Keywords" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | In the Leda Robot Tests, keywords are used for reusable functionality. Common keywords are defined in `resources/docker-snapshot/dockerfiles/leda-tests/leda_keywords.resource` 8 | 9 | The goal is to treat the Leda Quickstart image as a black box, utilizing as much as possible with public APIs. 10 | 11 | ## Interaction with Self Update Agent 12 | 13 | - `Trigger to start update`: Send a "Desired State Request" to the target, to install a RAUC Update Bundle 14 | - `Connect and Subscribe to Listen`: Wait for the asynchronous messages which indicate a successful installation of an update 15 | 16 | ## Arbitrary Commands 17 | 18 | Nevertheless, during implementation of test cases, it may be necessary to execute lower level processes for system level tests. For that, a fallback is possible to execute arbitrary test commands via remote SSH connection. These commands are executed through another docker container running in the same Docker network (`leda-network`) and allow access to the target QEMU instances: 19 | 20 | - `Leda Execute`: Execute an arbitrary shell command via SSH on the test target 21 | -------------------------------------------------------------------------------- /content/en/docs/build/tests/rust-tests.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Rust Tests" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | _Note:_ The Rust tests are being replaced with test cases implemented in Robot. 8 | 9 | ### Cross Compiling to X86_64 on Ubuntu 20.04 10 | 11 | There is currently a step to cross-compile tests to X86_64. In order to successfully run the step, you need to make sure that the following artifacts are available on the runner: 12 | 13 | - rustc + cargo: ``curl https://sh.rustup.rs -sSf | sh`` 14 | - docker: follow https://docs.docker.com/engine/install/ubuntu/ and afterwards https://docs.docker.com/engine/install/linux-postinstall/ 15 | - build-essential: ``sudo apt-get install build-essential`` 16 | - cross (0.1.16): ``cargo install cross --version 0.1.16`` 17 | - jq: ``sudo apt-get install jq -y`` 18 | 19 | You may restart your current shell so that all components are available as env vars. 20 | -------------------------------------------------------------------------------- /content/en/docs/customization/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Customizing" 3 | date: 2023-01-03T17:24:56+05:30 4 | weight: 10 5 | --- 6 | 7 | When you want to reuse Leda for your custom setup or hardware we do not directly provide BSPs for (see [Hardware](../customization/custom-images#Hardware)) you can reference the following chapters. They describe the general approaches for different level of customization - from deploying different sets of containers from those provided by default to building completely custom distros based on meta-leda. -------------------------------------------------------------------------------- /content/en/docs/customization/deploying-containers/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Deploying Containers" 3 | date: 2023-01-03T17:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | 8 | ## Kanto-auto-deployer (KAD) 9 | 10 | This service has been implemented as a stopgap solution by the Leda team since as of now the Kanto CM-native mechanism 11 | for initial container deployment does not suit the needs of the Leda Quickstart image well. 12 | 13 | In-depth documentation on its operation and development can be found in [Kanto Auto deployer](../../build/dev-and-maintenance/rust/kanto-auto-deployer). 14 | 15 | In the Leda Distro KAD runs as a service that continuously monitors the directory defined with the BitBake variable `KANTO_MANIFESTS_DEV_DIR` in the distro config recipes. 16 | By default, the Leda quickstart images use `KANTO_MANIFESTS_DEV_DIR=/data/var/containers/manifests"`. 17 | So, these manifests are again stored in the persistent **data**-partition and can be modified after the image has been deployed. 18 | 19 | **Important: KAD supports the [Kanto Container Management Manifest Template](https://eclipse.dev/kanto/docs/references/containers/container-config/#template) 20 | AND the [Container Internal State Representation](../../build/dev-and-maintenance/rust/kanto-auto-deployer//#internal-state-representation). For future compatiblity reasons it is recommended that you choose [Kanto Container Management Manifest Template](https://eclipse.dev/kanto/docs/references/containers/container-config/#template).** 21 | 22 | A standard set of containers is deployed through meta-leda, the manifests for which can be found in `meta-leda/meta-leda-components/recipes-sdv/eclipse-leda/kanto-containers/core` and `meta-leda/meta-leda-components/recipes-sdv/eclipse-leda/kanto-containers/example`. 23 | 24 | The advantage of this service is that it can be restarted very quickly (`systemctl restart kanto-auto-deployer`), without having to restart the _whole_ container-management service. The implemented filewatcher (the `--daemon` flag) allows you to quickly create/edit (or even `touch` them) container manifests on the device that would be on-the-fly deployed after saving. This allows for rapid testing when creating new container manifests. 25 | 26 | ## Kanto Container Management init-dir 27 | 28 | This feature of Kanto Container Managament by the Kanto Teams is currently under development and hence unstable. That is why it is not used as of the test-0.0.6 release of Leda Distro and 0.1.0-M1 release of meta-leda. -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Device Provisioning" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 3 5 | --- 6 | 7 | The device needs to be configured before it can make a connection to the cloud. 8 | 9 | The following initial configuration steps are required: 10 | 11 | - Create a device in the cloud backend, such as Azure IoT Hub 12 | - Configure authentication on device 13 | - Configure credentials for accessing private container registries 14 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Container Management" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 10 5 | --- 6 | 7 | Leda is using Kanto Container Management as the upper-layer container runtime and container orchestration engine. 8 | 9 | Besides the command line tool `kanto-cm`, Kanto also has remote interfaces to manage containers. 10 | 11 | ## Remote Interface 12 | 13 | Kanto's container-management service offers a remote interface via local messaging (MQTT) to interact with a digital twin on the cloud side. 14 | This feature can be easily enabled by setting `"things": { "enabled": true }` in `/etc/container-management/config.toml`. 15 | 16 | When one of the cloud connector components, such as leda-contrib-cloud-connector or Kanto's azure-connector, is connected to a cloud backend, the container-management will publish its own information using Eclipse Ditto and Eclipse Hono messages. For this, container-management only needs the device Id, gateway Id and tenant Id. 17 | 18 | 19 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/cloud-connectivity.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Cloud Connectivity" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | ## Simulation of cloud connectivity 8 | 9 | 1. Container Management starts and subscribes to `edge/thing/response` 10 | 2. Cloud Connector starts and publishes the following message to `edge/thing/response` as soon as the connection is online: 11 | 12 | {{}} 13 | 14 | - `namespace` is `azure.edge` for Kanto's Azure Cloud Connector 15 | - `gatewayId` indicates the hostname of the Azure IoT Hub 16 | - `deviceId` is the identifier for the device, this can either be part of the Azure Connection String or part of the device authentication certificate (CN) 17 | - `tenantId` is a configuration setting in the cloud connector 18 | 19 | > **Note:** You can simulate the cloud connector trigger by issueing the MQTT message manually on command line: 20 | 21 | ```shell 22 | mosquitto_pub -t 'edge/thing/response' -m '{"deviceId":"dummy-namespace:dummy-gateway:dummy-device-id","tenantId":"dummy-tenant-id"}' 23 | ``` 24 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/container-management-detail.json: -------------------------------------------------------------------------------- 1 | { 2 | "topic": "/::edge:containers/things/twin/commands/modify", 3 | "headers": { 4 | "response-required": false 5 | }, 6 | "path": "/features/Container:", 7 | "value": { 8 | "definition": [ 9 | "com.bosch.iot.suite.edge.containers:Container:1.5.0" 10 | ], 11 | "properties": { 12 | "status": { 13 | "name": "seatservice-example", 14 | "imageRef": "ghcr.io/eclipse/kuksa.val.services/seat_service:v0.1.0", 15 | "config": { 16 | "domainName": "seatservice-example-domain", 17 | "hostName": "seatservice-example-host", 18 | "env": [ 19 | "VEHICLEDATABROKER_DAPR_APP_ID=databroker", 20 | "BROKER_ADDR=databroker-host:30555", 21 | "RUST_LOG=info", 22 | "vehicle_data_broker=info" 23 | ], 24 | "restartPolicy": { 25 | "type": "UNLESS_STOPPED" 26 | }, 27 | "extraHosts": [ 28 | "databroker-host:host_ip" 29 | ], 30 | "portMappings": [ 31 | { 32 | "proto": "tcp", 33 | "hostPort": 30051, 34 | "hostPortEnd": 30051, 35 | "containerPort": 50051, 36 | "hostIP": "localhost" 37 | } 38 | ], 39 | "networkMode": "BRIDGE", 40 | "log": { 41 | "type": "JSON_FILE", 42 | "maxFiles": 2, 43 | "maxSize": "1M", 44 | "mode": "BLOCKING" 45 | } 46 | }, 47 | "createdAt": "2023-02-02T08:46:33.792687313Z", 48 | "state": { 49 | "status": "RUNNING", 50 | "pid": 13627, 51 | "startedAt": "2023-02-02T09:51:08.049572297Z", 52 | "finishedAt": "2023-02-02T09:50:51.752255799Z" 53 | } 54 | } 55 | } 56 | } 57 | } 58 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/container-management-list.json: -------------------------------------------------------------------------------- 1 | { 2 | "topic": "/::edge:containers/things/twin/commands/modify", 3 | "headers": { 4 | "response-required": false 5 | }, 6 | "path": "/features/SoftwareUpdatable", 7 | "value": { 8 | "definition": [ 9 | "org.eclipse.hawkbit.swupdatable:SoftwareUpdatable:2.0.0" 10 | ], 11 | "properties": { 12 | "status": { 13 | "softwareModuleType": "oci:container", 14 | "installedDependencies": { 15 | "ghcr.io%2Feclipse%2Fkuksa.val%2Fdatabroker.:0.2.5": { 16 | "group": "ghcr.io/eclipse/kuksa.val/databroker", 17 | "name": "", 18 | "version": "0.2.5" 19 | }, 20 | "ghcr.io%2Feclipse%2Fkuksa.val.services%2Fseat_service.:v0.1.0": { 21 | "group": "ghcr.io/eclipse/kuksa.val.services/seat_service", 22 | "name": "", 23 | "version": "v0.1.0" 24 | }, 25 | "ghcr.io%2Feclipse-leda%2Fleda-contrib-cloud-connector%2Fcloudconnector.:latest": { 26 | "group": "ghcr.io/eclipse-leda/leda-contrib-cloud-connector/cloudconnector", 27 | "name": "", 28 | "version": "latest" 29 | }, 30 | "ghcr.io%2Feclipse-leda%2Fleda-contrib-self-update-agent%2Fself-update-agent.:build-20": { 31 | "group": "ghcr.io/eclipse-leda/leda-contrib-self-update-agent/self-update-agent", 32 | "name": "", 33 | "version": "build-20" 34 | }, 35 | "ghcr.io%2Feclipse-leda%2Fleda-contrib-vehicle-update-manager%2Fvehicleupdatemanager.:latest": { 36 | "group": "ghcr.io/eclipse-leda/leda-contrib-vehicle-update-manager/vehicleupdatemanager", 37 | "name": "", 38 | "version": "latest" 39 | } 40 | } 41 | } 42 | } 43 | } 44 | } 45 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/container-metrics-request.json: -------------------------------------------------------------------------------- 1 | { 2 | "topic": "dummy-namespace/dummy-gateway:dummy-device-id:edge:containers/things/live/messages/request", 3 | "headers": { 4 | "timeout": "10", 5 | "response-required": true, 6 | "content-type": "application/json", 7 | "correlation-id": "3fdc463c-293c-4f39-ab19-24aef7944550" 8 | }, 9 | "path": "/features/Metrics/inbox/messages/request", 10 | "value": { 11 | "frequency": "5s" 12 | } 13 | } -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/container-metrics-response.json: -------------------------------------------------------------------------------- 1 | { 2 | "topic": "dummy-namespace/dummy-gateway:dummy-device-id:edge:containers/things/live/messages/data", 3 | "headers": { 4 | "content-type": "application/json", 5 | "response-required": false 6 | }, 7 | "path": "/features/Metrics/outbox/messages/data", 8 | "value": { 9 | "snapshot": [ 10 | { 11 | "originator": "Container:54274233-1a32-4e2a-bd09-2fd672daa2a4", 12 | "measurements": [ 13 | { 14 | "id": "cpu.utilization", 15 | "value": 0.060487465000000004 16 | }, 17 | { 18 | "id": "memory.total", 19 | "value": 2076409856 20 | }, 21 | { 22 | "id": "memory.used", 23 | "value": 1941504 24 | }, 25 | { 26 | "id": "memory.utilization", 27 | "value": 0.09350292739122888 28 | }, 29 | { 30 | "id": "net.readBytes", 31 | "value": 3074 32 | }, 33 | { 34 | "id": "net.writeBytes", 35 | "value": 3944 36 | }, 37 | { 38 | "id": "pids", 39 | "value": 5 40 | } 41 | ] 42 | } 43 | ], 44 | "timestamp": 1675431034 45 | } 46 | } 47 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/container-metrics.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Container Metrics" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | ### Container Metrics 8 | 9 | Container-level metrics, such as CPU utilization or memory usage, can be retrieved on-demand and continuously by enabling the container metrics events. 10 | This is done by sending a request to the topic `command//:::edge:containers/req//request`: 11 | 12 | 1. Enable Container Metrics with a frequency of `5s`: 13 | 14 | {{}} 15 | 16 | Example command line: 17 | 18 | ```shell 19 | mosquitto_pub -t command//dummy-namespace:dummy-gateway:dummy-device-id:edge:containers/req/3fdc463c-293c-4f39-ab19-24aef7944550/request -m '{"topic":"dummy-namespace/dummy-gateway:dummy-device-id:edge:containers/things/live/messages/request","headers":{"timeout":"10","response-required":true,"content-type":"application/json","correlation-id":"3fdc463c-293c-4f39-ab19-24aef7944550"},"path":"/features/Metrics/inbox/messages/request","value":{"frequency":"5s"}}' 20 | ``` 21 | 22 | 2. Container Metrics answers with an additional message for each container in the topic `e//::edge:containers` 23 | 24 | {{}} 25 | 26 | 3. To disable Container Metrics, send a request with frequency of `0s`: 27 | 28 | ```shell 29 | mosquitto_pub -t command//dummy-namespace:dummy-gateway:dummy-device-id:edge:containers/req/3fdc463c-293c-4f39-ab19-24aef7944550/request -m '{"topic":"dummy-namespace/dummy-gateway:dummy-device-id:edge:containers/things/live/messages/request","headers":{"timeout":"10","response-required":true,"content-type":"application/json","correlation-id":"3fdc463c-293c-4f39-ab19-24aef7944550"},"path":"/features/Metrics/inbox/messages/request","value":{"frequency":"0s"}}' 30 | ``` 31 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/container-registries.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Container Registries" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 5 5 | --- 6 | 7 | When deploying containerized applications, the container runtime will pull container images from a (remote) container registry. 8 | 9 | The pulled container images and their layers are then stored in a local storage. 10 | 11 | ## Private Container Registries 12 | 13 | To be able to pull container images, the container runtime needs access to the container registry. 14 | Some container registries require authentication. 15 | The Kanto Container Manager can be configured to use credentials when accessing remote container registries. 16 | 17 | In the Leda images, the *sdv-kanto-ctl* tools allows to easily add authentication to the container manager configuration: 18 | 19 | ```shell 20 | sdv-kanto-ctl add-registry -h -u -p 21 | ``` 22 | 23 | For example, to access container images from GitHub Packages in a private repository, you need a GitHub Personal Access Token (PAT) with the `read: packages` scope. 24 | Then, add the repository as shown below: 25 | 26 | ```shell 27 | sdv-kanto-ctl add-registry -h ghcr.io -u github -p 28 | ``` 29 | 30 | *sdv-kanto-ctl* will make the necessary modifications to `/etc/container-management/config.json` and restarts the `container-management.service` systemd unit, 31 | so that the changes take effect. You may need to recreate or restart the container if a previous pull failed. 32 | 33 | Please see the [Eclipse Kanto Container Manager Configuration reference](https://eclipse.dev/kanto/docs/references/containers/container-manager-config/) 34 | for details. 35 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/orchestration.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Orchestration" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 3 5 | --- 6 | 7 | # Container Management 8 | 9 | The container management will respond to the cloud connectivity status message by initially sending a list of containers: 10 | 11 | 1. Container Management responds with a list of containers in the topic `e//::edge:containers` 12 | 13 | {{}} 14 | 15 | 2. Container Management answers with an additional message for each container in the topic `e//::edge:containers` 16 | 17 | {{}} 18 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/container-management/simulate-connectivity.json: -------------------------------------------------------------------------------- 1 | { 2 | "deviceId":"::", 3 | "tenantId":"" 4 | } 5 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/activate-command.json: -------------------------------------------------------------------------------- 1 | { 2 | "activityId": "1234567890", 3 | "timestamp": 1687510087, 4 | "payload": { 5 | "baseline": "BASELINE NAME", 6 | "command": "ACTIVATE" 7 | } 8 | } -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/cleanup-command.json: -------------------------------------------------------------------------------- 1 | { 2 | "activityId": "1234567890", 3 | "timestamp": 1687510087, 4 | "payload": { 5 | "baseline": "BASELINE NAME", 6 | "command": "CLEANUP" 7 | } 8 | } -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/download-command.json: -------------------------------------------------------------------------------- 1 | { 2 | "activityId": "1234567890", 3 | "timestamp": 1687510087, 4 | "payload": { 5 | "baseline": "BASELINE NAME", 6 | "command": "DOWNLOAD" 7 | } 8 | } -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/leda-self-update.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/device-provisioning/self-update/leda-self-update.png -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/self-update-arch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/device-provisioning/self-update/self-update-arch.png -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/start-update-example.json: -------------------------------------------------------------------------------- 1 | { 2 | "activityId": "random-uuid-as-string", 3 | "timestamp": 123456789, 4 | "payload": { 5 | "domains": [ 6 | { 7 | "id": "self-update", 8 | "components": [ 9 | { 10 | "id": "os-image", 11 | "version": "${VERSION_ID}", 12 | "config": [ 13 | { 14 | "key": "image", 15 | "value": "http://leda-bundle-server/sdv-rauc-bundle-minimal-qemux86-64.raucb" 16 | } 17 | ] 18 | } 19 | ] 20 | } 21 | ] 22 | } 23 | } -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/self-update/update-command.json: -------------------------------------------------------------------------------- 1 | { 2 | "activityId": "1234567890", 3 | "timestamp": 1687510087, 4 | "payload": { 5 | "baseline": "BASELINE NAME", 6 | "command": "UPDATE" 7 | } 8 | } -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/vehicle-update-manager/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Vehicle Update Manager" 3 | date: 2022-072109T14:24:56+05:30 4 | weight: 7 5 | --- 6 | 7 | The *Vehicle Update Manager* delegates two different types of updates: 8 | 9 | 1. The *Desired State* on the container layer 10 | 2. The *Self Update* on operating system layer 11 | 12 | ![Vehicle Update Manager Architecture Overview](vehicle-update-manager-arch.png) 13 | 14 | ## Desired State 15 | 16 | The *Desired State* is applied at runtime on the container layer. 17 | 18 | This type of update mechanism can update vehicle applications, vehicle services and other containers together with configuration resources or data files at runtime. 19 | If the applications support it, the rollout can also use high-availability strategies, such as rolling deployments. You can find out more about more about 20 | the [Container Update Agent here](../container-management/container-update-agent). 21 | 22 | ## Self Update 23 | 24 | The *Self Update* is applied on reboot of the device only. 25 | 26 | This type of update mechanism is used for system-level updates which require the operating system to be rebooted to take effect. 27 | You can find out more about the [Self Update Agent in the tutorial](../self-update/self-update-tutorial). 28 | -------------------------------------------------------------------------------- /content/en/docs/device-provisioning/vehicle-update-manager/vehicle-update-manager-arch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/device-provisioning/vehicle-update-manager/vehicle-update-manager-arch.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Getting Started" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | {{% readfile file="../__shared/usage-overview.md" markdown="true" %}} 8 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/docker-setup/leda-docker-compose-up.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/docker-setup/leda-docker-compose-up.gif -------------------------------------------------------------------------------- /content/en/docs/general-usage/download-releases/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Download latest release" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | - [Milestone 0.1.0-M1](/leda/docs/about/releases/0.1.0/leda-0.1.0-m1/) 8 | 9 | ## Latest Release Artifacts 10 | 11 | **Note: There are no official releases yet. 12 | The artifacts available on the Release page are for testing the build and release workflows. 13 | They should be considered as unstable nightly builds from the main branch. 14 | Releases marked `-M1`, `-M2`, `-RC1` etc. are preparations for official releases according to the Eclipse Release process.** 15 | 16 | Go to the [Eclipse Leda Releases](https://github.com/eclipse-leda/leda-distro/releases) page and download the release archive for the respective machine. 17 | The release archives container the disk image and the respective Linux kernel: 18 | 19 | | Machine | Filename | Description | 20 | | ------- | -------- | ----------- | 21 | | QEMU x86_64 | eclipse-leda-qemu-x86_64.tar.xz | For running QEMU x86 64-Bit | 22 | | QEMU ARM 64 | eclipse-leda-qemu-arm64.tar.xz | For running QEMU ARM 64-Bit | 23 | | Raspberry Pi 4 | eclipse-leda-raspberrypi.tar.xz | For running on Raspberry Pi 4 (SD-Card Image) | 24 | 25 | ## Using GitHub CLI tool 26 | 27 | To download all files of the latest release using the GitHub CLI: 28 | 29 | - Install [GitHub CLI](https://github.com/cli/cli), e.g. for Ubuntu: 30 | 31 | ```shell 32 | curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg 33 | echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null 34 | sudo apt update 35 | sudo apt install gh 36 | ``` 37 | 38 | - Authenticate to GitHub: 39 | 40 | ```shell 41 | gh auth login 42 | ``` 43 | - Download Leda latest release: 44 | 45 | On Linux: 46 | 47 | ```shell 48 | mkdir leda && cd leda 49 | 50 | gh release download \ 51 | --pattern '*.zip' \ 52 | --pattern 'eclipse-leda-*' \ 53 | --repo eclipse-leda/leda-distro 54 | ``` 55 | 56 | On Windows: 57 | 58 | ```shell 59 | gh release download --pattern "*.zip" --pattern "eclipse-leda-*" --repo eclipse-leda/leda-distro 60 | ``` 61 | 62 | - Continue with [Running Eclipse Leda on QEMU](/leda/docs/general-usage/running-qemu/) or [Running Eclipse Leda on Raspberry Pi 4](/leda/docs/general-usage/raspberry-pi/) 63 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/raspberry-pi/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Running on Raspberry Pi" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 3 5 | --- 6 | 7 | What you need: 8 | 9 | - A Raspberry Pi 4B (64 Bit) with 2 GiB of RAM or more, recommended is 8 GiB 10 | - Network connection (Ethernet or Wifi) with transparent internet access 11 | - Optional keyboard and display (makes it easier to troubleshoot) 12 | 13 | Steps: 14 | 15 | - Download the [latest released SD-Card Image](/leda/docs/general-usage/download-releases/): `eclipse-leda-raspberrypi.tar.xz` 16 | - Uncompress the SD Card image: 17 | 18 | apt-get install -y xz-utils 19 | tar xf eclipse-leda-raspberrypi.tar.xz 20 | bzip2 -d -f sdv-image-all-raspberrypi4-64.wic.bz2 21 | 22 | - Flash the `sdv-image-all-raspberrypi4.wic` file to an SD-Card 23 | - On Linux: 24 | - Install bmap tools: `sudo apt-get install -y bmap-tools` 25 | - Insert SD Card and check which device is mounted: `sudo fdisk -l` 26 | - Unmount the device: `sudo umount /dev/mmcblk[X]` 27 | - `sudo bmaptool copy --bmap sdv-image-all-raspberrypi4-64.wic.bmap sdv-image-all-raspberrypi4-64.wic /dev/mmcblk[X]` 28 | - *Note: Using `bmap` is **much** faster but works the same as with plain `dd if= of=dev/mmcblk[x]`.* 29 | - On Windows: 30 | - [Raspberry Pi Imager](https://www.raspberrypi.org/documentation/installation/installing-images/) 31 | - [Balena Etcher](https://www.balena.io/etcher/) 32 | - *Optional: If you need to adapt the network configuration eg Wifi credentials, edit the configuration files on the `boot` partition.* 33 | - Shutdown the Raspberry and insert the SD-Card into the Raspberry Pi SD-Card slot at the bottom 34 | - Power on your Raspberry to boot the image 35 | - Login with `root` 36 | - Check disk space: 37 | - The `raspberry-growdisk` system service will do this automatically on first boot. 38 | - To manually enlarge the available disk space on the SD-Card, resize the disk partition: `parted /dev/mmcblk0 resizepart 6 100% && resize2fs /dev/mmcblk0p6`. 39 | 40 | *Note: Due to changes in the disk partition, the partition number (`6` in the example) may have changed.* 41 | - Verify with `df -h`. 42 | 43 | - Verify and wait until container runtime is started: `systemctl status container-management` 44 | - *Optional:* Check the system health: `sdv-health` 45 | - Continue with [Device Provisioning](/leda/docs/device-provisioning/) 46 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/raspberry-pi/raspberry-can-hats.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "CAN-Bus extensions" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 2 5 | --- 6 | 7 | The Eclipse Leda quickstart image has CAN-Bus kernel modules and some CAN hardware drivers pre-installed. 8 | However, some hardware configuration needs to be adapted at boot time depending on the specific CAN-Extension being attached to the device. 9 | 10 | On Raspberry Pi, there is a `/boot/config.txt` file where you can configure the `dtoverlay` options accordingly. 11 | 12 | > **Note:** After modification, the device **requires rebooting** for the changes to take effect. 13 | 14 | ## MCP2515 based modules 15 | 16 | Products: 17 | 18 | - [Waveshare RS485 CAN HAT for Raspberry Pi](https://www.waveshare.com/rs485-can-hat.htm) 19 | 20 | ```shell 21 | dtoverlay=mcp2515-can0,oscillator=12000000,interrupt=25,spimaxfrequency=2000000 22 | ``` 23 | 24 | ## MCP2518FD based modules 25 | 26 | Products: 27 | 28 | - [Waveshare 2-Channel Isolated CAN FD Expansion HAT for Raspberry Pi, Multi Protections](https://www.waveshare.com/product/raspberry-pi/2-ch-can-fd-hat.htm) 29 | 30 | ```shell 31 | dtoverlay=2xMCP2517FD 32 | #dtoverlay=2xMCP2518FD-spi0 33 | ``` 34 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/running-qemu/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Running on QEMU" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 4 5 | --- 6 | 7 | If you want to execute the image without building first, grab the latest release or build artifacts from [https://github.com/eclipse-leda/leda-distro/](https://github.com/eclipse-leda/leda-distro/) 8 | 9 | ## Recommendations 10 | 11 | - A **Linux host** with 8 vCPUs, 16GB of RAM and SSD storage is recommended 12 | - Your Linux user should be **sudoer** to allow TAP network interfaces to be set up 13 | 14 | ## QEMU x86_64 15 | 16 | - Install [Qemu](https://www.qemu.org/), e.g. for Ubuntu: 17 | 18 | sudo apt-get update -y 19 | sudo apt-get install -y xz-utils qemu-system-x86-64 20 | 21 | - Download [latest Eclipse Leda release](/leda/docs/general-usage/download-releases/) 22 | - Uncompress the archive 23 | 24 | tar xf eclipse-leda-qemu-x86_64.tar.xz 25 | 26 | - Run QEMU on Linux: 27 | 28 | ./run-leda.sh 29 | 30 | - Run QEMU on Windows: 31 | 32 | run-leda.cmd 33 | 34 | ![Leda boot sequence](leda-bootsequence.png) 35 | 36 | - Login as `root` without password on login prompt 37 | - Verify and wait until container runtime is started: `systemctl status container-management` 38 | - *Optional:* Check the system health: `sdv-health` 39 | 40 | ![sdv-health](sdv-health1.png) 41 | 42 | *Note: The status of some containers (e.g. cloud connector) are expected to stay in **FAILED** status as long as the **Device Provisioning** steps are not completed.* 43 | 44 | - Continue with [Device Provisioning](/leda/docs/device-provisioning/) 45 | 46 | ## QEMU ARM 64-Bit 47 | 48 | - Install [Qemu](https://www.qemu.org/), e.g. for ARM 64-Bit: `sudo apt install qemu-system-aarch64` 49 | - Download [latest Eclipse Leda release](/leda/docs/general-usage/download-releases/) 50 | - Uncompress the archive 51 | 52 | tar xf eclipse-leda-qemu-arm64.tar.xz 53 | 54 | - Run QEMU on Linux: 55 | 56 | ./run-leda.sh 57 | 58 | - Run QEMU on Windows: 59 | 60 | run-leda.cmd 61 | 62 | - Login as `root` without password on login prompt 63 | - Verify and wait until container runtime is started: `systemctl status container-management` 64 | - *Optional:* Check the system health: `sdv-health` 65 | 66 | *Note: The status of some containers (e.g. cloud connector) are expected to stay in **FAILED** status as long as the **Device Provisioning** steps are not completed.* 67 | 68 | - Continue with [Device Provisioning](/leda/docs/device-provisioning/) 69 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/running-qemu/filetransfer.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Transferring Files" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | --- 6 | 7 | # Sharing a directory with the guest 8 | 9 | When you want to copy files between the host and the guest, an easy way is to use an SFTP tunnel. 10 | With `sshfs`, you can mount a local directory to a remote directory via SSH. 11 | 12 | ## Pre-Requisites 13 | 14 | Installation of needed packages: 15 | 16 | - Run `apt-get install sshfs` on your host 17 | - Enable `CORE_IMAGE_EXTRA_INSTALL += " openssh-sftp-server"` in `local.conf` of your image (e.g. in the local_conf_header section in your kas file) 18 | - Verify SFTP connection working with `sftp -P 2222 root@localhost` 19 | 20 | ## Transfering files from host to guest 21 | 22 | When you want to copy files from the host to the guest, an easy way is to use an SFTP tunnel. 23 | With `sshfs`, you can mount a local directory to a remote directory via SSH. 24 | 25 | - Create a mount point on your host: `mkdir remote` 26 | - Open the SSH Filesystem tunnel: `sshfs root@localhost:/ remote/ -p 2222` 27 | - Check files: `ls -al remote/` - you should see the root filesystem of the device now 28 | - You can now easily copy files: `cp foo.txt remote/home/root/` 29 | 30 | ## Transfering files from guest to host 31 | 32 | _Note:_ The reverse direction, e.g. initiating an SSH tunnel from within the device to the host, is currently not supported by the installed software on the image. 33 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/running-qemu/leda-bootsequence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/running-qemu/leda-bootsequence.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/running-qemu/sdv-health1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/running-qemu/sdv-health1.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/running-qemu/systemctl-status-k3s.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/running-qemu/systemctl-status-k3s.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/abstract-architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/abstract-architecture.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/digitalauto-prototype.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/digitalauto-prototype.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/digitalauto-vehicle-api.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/digitalauto-vehicle-api.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/kuksa-actuation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/kuksa-actuation.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/vehicle-mock.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/vehicle-mock.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/velocitas-flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/velocitas-flow.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/sdv-introduction/vss-tree.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/sdv-introduction/vss-tree.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Utilities" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 15 5 | --- 6 | 7 | The quickstart image contains the following utilities. 8 | These utility scripts are meant to be convenience tools for users and developers. 9 | They help to experiment with the container deployment, device provisioning or vehicle data access. 10 | 11 | - **sdv-health:** Show SDV software components health status 12 | - **kantui:** A text user interface for kanto-cm to manage containers (start, stop, logs, redeploy all) 13 | - **sdv-device-info:** Show and update device information 14 | - **sdv-provision:** Generate device certificates and configuration of cloud connection 15 | - **sdv-motd:** Message-of-the-Day shown after login prompt 16 | - **can-forward:** Forwarding a CAN-bus network interface into a containerized Vehicle Application 17 | - **kanto-auto-deployer:** Automatically deploys containers on boot. Runs as a systemd service, and can also be invoked by a user directly. 18 | - **sdv-ctr-exec:** Execute arbitrary commands in existing containers 19 | - **sdv-kanto-ctl:** Manage the Kanto Container Management configuration via CLI 20 | - **blueprint-selector:** Deploy and fetch new SDV blueprints easily with an interactive CLI 21 | 22 | > Note: 23 | These scripts are not meant to be reused or called from production software. 24 | Their behaviour or command line syntax is not a stable API and should not be trusted for automation purposes. 25 | For details, please see [leda-utils](https://github.com/eclipse-leda/leda-utils/) 26 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/blueprint-selector-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/blueprint-selector-1.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/can-forward.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "CAN Forward" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 6 5 | --- 6 | 7 | The `can-forward` help script can be used to forward an existing CAN-Bus interface on the host system to a container process. 8 | 9 | > Note: Warning! The script does not yet support Kanto (or containerd) as a container runtime. It has been implemented for k3s. 10 | 11 | ## Usage 12 | 13 | ```shell 14 | root@qemux86-64:~# can-forward --help 15 | 16 | Usage: /usr/bin/can-forward {-h} {-p PID} {-c container} 17 | 18 | hw_can Host CAN hw interface to forward. Default: can0 19 | -c container Attemmpt to get netns PID from a running container: (docker, ctr). Default: seat_service 20 | -p PID Use provided PID for transferring vxcan interface (e.g.: docker inspect -f '{{ .State.Pid }}' container) 21 | -h Prints this message 22 | ``` 23 | 24 | The script performs the following steps: 25 | 26 | - Find the process ID of the target container process 27 | - Check and modprobe `vxcan` 28 | - Check and modprobe `can-gw` 29 | - Create a new virtual CAN interface (`vxcanX`) 30 | - Create a new virtual CAN interface (`vxcanX+1`) 31 | - Link both interfaces together 32 | - Move the second interface (`vxcanX+1`) into the namespace of the target container 33 | - Set up a bi-directional CAN-Bus packet forwarding between both interfaces using `cangw` 34 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/kantui-large.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/kantui-large.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-device-info-example-output1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/sdv-device-info-example-output1.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-device-info.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "SDV Device Info" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 3 5 | --- 6 | 7 | Displays the current device configuration, such as Device ID. 8 | 9 | > Note: **Requires** the *Cloud Connector* component to be configured and running. 10 | 11 | Usage: 12 | 13 | ```shell 14 | sdv-device-info 15 | ``` 16 | 17 | ![Eclipse Leda Device Info Example Output](../sdv-device-info-example-output1.png) 18 | 19 | ## Usage 20 | 21 | Synposis: `./sdv-device-info [options] [command]` 22 | 23 | Full help: 24 | 25 | ```shell 26 | root@qemux86-64:~# sdv-device-info --help 27 | sdv-device-info v0.2 28 | Usage: /usr/bin/sdv-device-info [options] [command] 29 | Show SDV device configuration information 30 | Example: /usr/bin/sdv-device-info show 31 | 32 | Commands: 33 | show : Display configuration (default command) 34 | help : This message 35 | env : Format output for use in scripts 36 | 37 | Options: 38 | --ansi | -a : Don't use colored output. 39 | --norestart | -n : Do not automatically restart services 40 | --verbose | -v : Enable verbose mode. 41 | --help | -h : This message. 42 | ``` 43 | 44 | ## Use in scripts 45 | 46 | To use device information on other scripts, it may be useful to source the device information variables into the current environment variable context: 47 | 48 | Synposis: `source ./sdv-device-info env` 49 | 50 | Example: 51 | 52 | ```shell 53 | $ source ./sdv-device-info env 54 | $ echo $DEVICE_ID 55 | exampledevice1 56 | ``` 57 | -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-health-example-errors.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/sdv-health-example-errors.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-health-example-errors2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/sdv-health-example-errors2.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-health-output.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/sdv-health-output.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-kanto-ctl-example-output1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/sdv-kanto-ctl-example-output1.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-motd.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "SDV MotD" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 5 5 | --- 6 | 7 | The `sdv-motd` script provides an alternative motd profile, which displays some additional information after login. 8 | 9 | The script does not have any command line options. 10 | 11 | Example output: 12 | 13 | ![Eclipse Leda Message Of The Day](../sdv-motd.png) -------------------------------------------------------------------------------- /content/en/docs/general-usage/utilities/sdv-motd.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/general-usage/utilities/sdv-motd.png -------------------------------------------------------------------------------- /content/en/docs/general-usage/wifi-configuration/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Wifi Configuration" 3 | date: 2023-01-03T17:24:56+05:30 4 | weight: 20 5 | --- 6 | 7 | BSP packages for emulated WiFi devices (QEMU) and hardware device drivers are provided in `meta-leda` for [supported hardware](../../customization/custom-images#hardware). 8 | They usually do not require extra configuration. 9 | 10 | For a guide on how to connect to a wireless network check the [_Connecting to Wi-Fi networks_](connecting-to-wifi) page. 11 | 12 | ## Raspberry Pi 4B 64 13 | 14 | The required kernel modules and binary blobs are provided with the `sdv-wifi-kernel-config.inc` config file and the `packagegroup-sdv-rpi4wifi` packagegroup. These 15 | are included in `sdv-image-full.bb` and `sdv-image-minimal.bb` by default. 16 | 17 | If you, however, decide to define your own custom image based on [_Custom Distros_](../../customization/custom-images), 18 | you would have to make sure the packagegroup is installed to enable WiFi connectivity. 19 | 20 | ## QEMU 21 | 22 | QEMU images provide the kernel modules necessary to set-up a virtual wlan interface and connect it to a virtual wifi network. This can be useful in various testing scenarios. 23 | 24 | To create and link a virtual WiFi interface to eth0, boot your QEMU image and run: 25 | 26 | ```shell 27 | $ ip link add link eth0 name wlan0 type virt_wifi 28 | ``` 29 | 30 | The SSID of the virtual network you can connect to is `VirtWifi`. 31 | 32 | _Note:_ Leda Quickstart QEMU images set the name of the default virtual ethernet interface to `eth0` through kernel CMDLINE configurations (`net.ifnames=0 biosdevname=0`). 33 | If you are building a custom image with a different kernel CMDLINE replace `eth0` with the name of your virtual interface (check `ifconfig`). 34 | -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Incubator" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 8 5 | --- 6 | 7 | The [Leda Incubator project](https://projects.eclipse.org/proposals/eclipse-leda-incubator) is a place for new software-defined-vehicle related software components which are in incubation state. 8 | 9 | The goal of the Eclipse Leda Incubator is to foster collaboration in the Eclipse Software Defined Vehicle (SDV) ecosystem, and hopefully results in work proceeding to contribution by their original authors into upstream projects. The Eclipse Leda Incubator would not make any releases itself. 10 | 11 | The project hosts software-defined vehicle components which are fitting into the general Eclipse Leda scope, but do not fit to either being part of Leda itself, which should be upstreamed into other projects in the future, or which are still highly experimental and should not be considered for any kind of production use. 12 | -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/cloud-connector/cloud-connector-fork.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/leda-incubator/cloud-connector/cloud-connector-fork.png -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/cloud-connector/cloud-connector-runtime.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/leda-incubator/cloud-connector/cloud-connector-runtime.png -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/otel-integration/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "OpenTelemetry Integration" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 10 5 | --- 6 | 7 | The OpenTelemetry integration shall be used to connect the edge device's application log files to an existing DevOps infrastructure on the cloud side. 8 | 9 | **Status:** Open for initial contribution 10 | 11 | ## Background 12 | 13 | The legacy approach to logging of vehicle applications is outdated and prevents application developers from retrieving near-time information 14 | on the application's health in a fleet. Existing log or remote diagnostic systems for vehicles may still use a "file upload on remote request" approach. 15 | 16 | For a more streamlined and updated way of accessing applications logs, the idea is to expore the use of current Cloud DevOps methods and 17 | technologies and apply them to remote vehicle edge system devices. 18 | 19 | ## Goals and Wishlist 20 | 21 | - Collect logs from containerized applications (and system logs) on the edge device 22 | - Control the edge's log manager configuration remotely and on-demand: 23 | - Enable and disable 24 | - One-shot activation schedules 25 | - Changing log levels 26 | - Apply filtering or sampling configurations 27 | - Trigger logging based on locally evaluated, dynamic conditions (IF condition=true THEN stream logs and metrics of app X for 15 minutes) 28 | - Retrieve and stream log messages from the edge device to an existing cloud backend (e.g. Grafana, Loki, ELK, Prometheus). 29 | The point here being that the endpoints should be vendor-neutral and use open standard protocols. 30 | - Retrieve application logs in different ways: 31 | - streamed near-time debug/trace logs for application developers in development and testing environments 32 | - streamed error logs for fleet operators for production environments 33 | - packaged, file-based logs for offroad (offline) vehicles 34 | - Retrieve container metrics, such as CPU, memory, disk i/o, network usage and other I/O 35 | This is interesting for application developers, for system integrators and for fleet operators to optimize their products and services. 36 | - Enable distributed tracing of application requests using span IDs, trace IDs or correlation IDs 37 | For future troubleshooting and support purposes, an integration of cloud-side applications and edge-side applications into commercial operation 38 | of distributed vehicle systems may become necessary. 39 | 40 | ## Source Repository 41 | 42 | Source Repository: 43 | 44 | -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/self-update-agent/self-update-agent-arch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/leda-incubator/self-update-agent/self-update-agent-arch.png -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/self-update-agent/self-update-agent-deploy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/leda-incubator/self-update-agent/self-update-agent-deploy.png -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/vehicle-update-manager/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Vehicle Update Manager" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 15 5 | --- 6 | 7 | The vehicle update manager is used in the context of [OTA Software Updates](/leda/docs/device-provisioning/vehicle-update-manager). 8 | 9 | ## Overview 10 | 11 | Vehicle Update Manager (VUM) is an extended version of the [Eclipse Kanto Container Manager](https://github.com/eclipse-kanto/container-management) that is being able to **handle new desired state for the software on the whole vehicle device**. 12 | 13 | ![Vehicle Update Manager Scope](./vehicle-update-manager-arch.png) 14 | 15 | ## Implementation 16 | 17 | The desired state comes as a multi document YAML content and it includes a list of container resources: 18 | 19 | - Container 20 | - Configuration 21 | 22 | VUM detects the system-level update custom resource and passes it for further processing to the [Self Update Agent](/leda/docs/leda-incubator/self-update-agent/). 23 | 24 | VUM also monitors the self-update agent and the control plane, and compiles and report the current state of the device. 25 | 26 | ## Source Repository 27 | 28 | Source Repository: 29 | -------------------------------------------------------------------------------- /content/en/docs/leda-incubator/vehicle-update-manager/vehicle-update-manager-arch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/leda-incubator/vehicle-update-manager/vehicle-update-manager-arch.png -------------------------------------------------------------------------------- /content/en/docs/overview.puml: -------------------------------------------------------------------------------- 1 | @startuml buildArch 2 | title Eclipse Leda Build Architecture 3 | 4 | [This repository] as self 5 | [Yocto] as yocto 6 | [Poky] as poky 7 | [BitBake] as bitbake 8 | [ExternalSources] as externalSources 9 | [Meta-Base] as metaBASE 10 | [Meta-Poky] as metaPOKY 11 | [Meta-Yocto-BSP] as metaYOCTOBSP 12 | 13 | [Meta-Raspberry] as metaRPI4 14 | 15 | [meta-leda] as metaSDV 16 | [SDVSources] as sdvSources 17 | 18 | [Build AArch64 QEMU] as buildAARCH64QEMU 19 | [Build AArch64 RPi4] as buildAARCH64RPi4 20 | [Build ARM QEMU] as buildARMQEMU 21 | [Build X86_64 QEMU] as buildX8664QEMU 22 | 23 | [Image X86_64 QEMU] as imageX8664QEMU 24 | 25 | self -> yocto : uses 26 | yocto -> poky : uses 27 | poky -> bitbake : uses 28 | bitbake -> metaBASE : pulls 29 | bitbake -> metaPOKY : pulls 30 | bitbake -> metaYOCTOBSP : pulls 31 | 32 | metaBASE -> externalSources : pulls 33 | metaPOKY -> externalSources : pulls 34 | metaYOCTOBSP -> externalSources : pulls 35 | 36 | metaSDV -> sdvSources : pulls 37 | 38 | buildX8664QEMU -> metaSDV : pulls 39 | buildAARCH64RPi4 -> metaSDV : pulls 40 | buildARMQEMU -> metaSDV : pulls 41 | buildAARCH64QEMU -> metaSDV : pulls 42 | 43 | buildAARCH64RPi4 -> metaRPI4 : pulls 44 | 45 | buildX8664QEMU -> imageX8664QEMU : builds 46 | 47 | @enduml -------------------------------------------------------------------------------- /content/en/docs/project-info/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Project Information" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 20 5 | --- 6 | 7 | -------------------------------------------------------------------------------- /content/en/docs/project-info/community/Eclipse Leda - Slides SDV Contribution Day - September 2022.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/community/Eclipse Leda - Slides SDV Contribution Day - September 2022.pdf -------------------------------------------------------------------------------- /content/en/docs/project-info/community/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Community" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 1 5 | resources: 6 | - name: slides-sdv-contrib-day-sept2022 7 | src: Eclipse Leda - Slides SDV Contribution Day - September 2022.pdf 8 | --- 9 | 10 | Thanks for your interest in this project and in our community. 11 | 12 | * 13 | 14 | ## Contact 15 | 16 | Contact the project developers via the project's "dev" list. 17 | 18 | * 19 | 20 | ## Developer resources 21 | 22 | Information regarding source code management, builds, coding standards, and 23 | more. 24 | 25 | * 26 | 27 | The project maintains the following source code repositories 28 | 29 | * 30 | * 31 | * 32 | 33 | ## Publications 34 | 35 | * [Eclipse Leda Introduction Video](https://www.youtube.com/watch?v=91hNeQ3kf0w) - YouTube, 2min 36 | * [Eclipse SDV - First Contribution Day (June 2022)](https://www.youtube.com/watch?v=yOVHyG0aZ7M&list=PLy7t4z5SYNaRYI7lH26szREOi9pfqxOUU&index=8) - Session Recording, YouTube, 26min 37 | * [Eclipse SDV - Second Contribution Day (September 2022)](https://www.youtube.com/watch?v=hiFriZhv1NE&list=PLy7t4z5SYNaRYI7lH26szREOi9pfqxOUU&index=17) - Session Recording, YouTube, 30min 38 | * [Eclipse Leda - Slides SDV Contribution Day - September 2022](./Eclipse%20Leda%20-%20Slides%20SDV%20Contribution%20Day%20-%20September%202022.pdf) - Slides (PDF) 39 | -------------------------------------------------------------------------------- /content/en/docs/project-info/dependencies.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Dependencies" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 3 5 | --- 6 | 7 | | Dependency | Type | License | URL | 8 | | --- | --- | --- | --- | 9 | | poky | OpenEmbedded Metalayer | MIT | | 10 | | meta-virtualization | OpenEmbedded Metalayer | MIT | | 11 | | meta-networking | OpenEmbedded Metalayer | MIT | | 12 | | meta-rauc | OpenEmbedded Metalayer | MIT | | 13 | | meta-openembedded | OpenEmbedded Metalayer | MIT | | 14 | | meta-security | OpenEmbedded Metalayer | MIT | | 15 | | meta-rauc-community | OpenEmbedded Metalayer | MIT | | 16 | | meta-raspberrypi | OpenEmbedded Metalayer | MIT | | 17 | -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/_variables_project.scss: -------------------------------------------------------------------------------- 1 | $primary: #403F4C ; 2 | $secondary: #6daed1 ; 3 | $td-enable-google-fonts: false; 4 | -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo-black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo-black.png -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo-cropped.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo-cropped.png -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo-white-transparent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo-white-transparent.png -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo.zip -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_01_cmyk.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_01_cmyk.ai -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_01_cmyk.eps: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_01_cmyk.eps -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_01_cmyk.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_01_cmyk.pdf -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_01_rgb.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_01_rgb.ai -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_01_rgb.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_01_rgb.jpg -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_01_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_01_rgb.png -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_02_cmyk.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_02_cmyk.ai -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_02_cmyk.eps: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_02_cmyk.eps -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_02_cmyk.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_02_cmyk.pdf -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_02_rgb.ai: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_02_rgb.ai -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_02_rgb.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_02_rgb.jpg -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/eclipse-leda-logo_02_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/eclipse-leda-logo_02_rgb.png -------------------------------------------------------------------------------- /content/en/docs/project-info/logo/icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/docs/project-info/logo/icon.png -------------------------------------------------------------------------------- /content/en/docs/project-info/security.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Security Policy" 3 | date: 2022-05-09T14:24:56+05:30 4 | weight: 10 5 | --- 6 | 7 | This project implements the Eclipse Foundation Security Policy 8 | 9 | * [https://www.eclipse.org/security](https://www.eclipse.org/security) 10 | 11 | ## Reporting a Vulnerability 12 | 13 | Please report vulnerabilities to the Eclipse Foundation Security Team at 14 | security@eclipse.org 15 | 16 | ## Supported Yocto Versions 17 | 18 | | Version | Supported | 19 | | ----------------------- | ------------------ | 20 | | Yocto 4.x (Kirkstone) | Yes | 21 | | Yocto 3.4 (Honister) | EOL | 22 | | Yocto 3.3 | Untested | 23 | | Yocto < 3.3 | No | 24 | 25 | **Important: When you use the quickstart images for non-volatile setups, it is essential to reconfigure the system and harden it.** 26 | 27 | ## Configuration Items 28 | 29 | * Disable system user (root) password and login 30 | * Disable SSH login with password 31 | * Adding a new Linux user with restricted permissions 32 | * Adding SSH key based authentication 33 | * Container Secrets 34 | * Device identity certificates for cloud connection 35 | * Access credentials for private container registries 36 | 37 | ### Device Identity for Cloud Connector 38 | 39 | | Method | Implementation | Intended use | 40 | | -------------- | -------------- | ---------------------------- | 41 | | Pre-Shared Symmetric Key | Azure IoT Hub Connection String | Development | 42 | | Certificates | X.509 Certificates | Production | 43 | -------------------------------------------------------------------------------- /content/en/docs/vss/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Vehicle Signals" 3 | date: 2023-05-09T14:24:56+05:30 4 | weight: 5 5 | no_list: true 6 | --- 7 | 8 | This chapter contains a reference of the vehicle signal metadata from the [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) Release 3.1. 9 | 10 | The Vehicle Signals Specification is a tree of standardized information signals. 11 | 12 | It starts with the [`Vehicle`](vehicle/) root node. -------------------------------------------------------------------------------- /content/en/leda-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/leda-logo.png -------------------------------------------------------------------------------- /content/en/logo_01_rgb-background.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/content/en/logo_01_rgb-background.png -------------------------------------------------------------------------------- /data/consent.yaml: -------------------------------------------------------------------------------- 1 | items: 2 | - title: Google Analytics 3 | description: This code gives us insight into the number of people that visit our website, where they are from and what they are clicking on. 4 | is_functional: false 5 | script_file: ga.js 6 | -------------------------------------------------------------------------------- /layouts/404.html: -------------------------------------------------------------------------------- 1 | {{ define "main"}} 2 |
3 |
4 |

Not found

5 |

Oops! This page doesn't exist. Try going back to our home page.

6 |
7 |
8 | {{ end }} 9 | -------------------------------------------------------------------------------- /layouts/_default/_markup/render-codeblock-mermaid.html: -------------------------------------------------------------------------------- 1 |
2 | {{- .Inner | safeHTML }} 3 |
4 | {{ .Page.Store.Set "hasMermaid" true }} 5 | -------------------------------------------------------------------------------- /layouts/_default/baseof.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | {{ partial "head.html" . }} 5 | 6 | 7 |
8 | {{ partial "navbar.html" . }} 9 |
10 |
11 |
12 | {{ block "main" . }}{{ end }} 13 |
14 | {{ partial "footer.html" . }} 15 |
16 | {{ if .Site.Params.EnableAnalyticsScripts }} 17 | {{ partial "analytics-with-consent" . }} 18 | {{ end }} 19 | {{ partialCached "scripts.html" . }} 20 | 21 | 22 | -------------------------------------------------------------------------------- /layouts/blog/baseof.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | {{ partial "head.html" . }} 5 | 6 | 7 |
8 | {{ partial "navbar.html" . }} 9 |
10 |
11 |
12 |
13 | 16 | 21 |
22 | {{ with .CurrentSection.OutputFormats.Get "rss" -}} 23 | 24 | 25 | 26 | {{ end -}} 27 | {{ block "main" . }}{{ end }} 28 |
29 |
30 |
31 | {{ partial "footer.html" . }} 32 |
33 | {{ if .Site.Params.EnableAnalyticsScripts }} 34 | {{ partial "analytics-with-consent" . }} 35 | {{ end }} 36 | {{ partial "scripts.html" . }} 37 | 38 | 39 | -------------------------------------------------------------------------------- /layouts/docs/baseof.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | {{ partial "head.html" . }} 5 | 6 | 7 |
8 | {{ partial "navbar.html" . }} 9 |
10 |
11 |
12 |
13 | 16 | 21 |
22 | {{ partial "version-banner.html" . }} 23 | {{ if not .Site.Params.ui.breadcrumb_disable }}{{ partial "breadcrumb.html" . }}{{ end }} 24 | {{ block "main" . }}{{ end }} 25 |
26 |
27 |
28 | {{ partial "footer.html" . }} 29 |
30 | {{ if .Site.Params.EnableAnalyticsScripts }} 31 | {{ partial "analytics-with-consent" . }} 32 | {{ end }} 33 | {{ partial "scripts.html" . }} 34 | 35 | 36 | -------------------------------------------------------------------------------- /layouts/partials/footer.html: -------------------------------------------------------------------------------- 1 | {{ if .Page.Store.Get "hasMermaid" }} 2 | 3 | 6 | {{ end }} 7 | 8 | {{ $links := .Site.Params.links }} 9 |
10 |
11 |
12 |
13 | {{ with $links }} 14 | {{ with index . "user"}} 15 | {{ template "footer-links-block" . }} 16 | {{ end }} 17 | {{ end }} 18 |
19 |
20 | {{ with $links }} 21 | {{ with index . "developer"}} 22 | {{ template "footer-links-block" . }} 23 | {{ end }} 24 | {{ end }} 25 |
26 |
27 | {{ with .Site.Params.copyright }}© {{ now.Year}} {{ .}}. {{ T "footer_all_rights_reserved" }}.{{ end }} 28 | {{ with .Site.Params.privacy_policy }}{{ T "footer_privacy_policy" }}{{ end }} 29 | {{ if not .Site.Params.ui.footer_about_disable }} 30 | {{ with .Site.GetPage "about" }}

{{ .Title }}

{{ end }} 31 | {{ end }} 32 |
33 |
34 |
35 |
36 | {{ with $links }} 37 | {{ with index . "eclipse"}} 38 | {{ template "footer-links-block-text" . }} 39 | {{ end }} 40 | {{ end }} 41 |
42 |
43 |
44 | {{ define "footer-links-block" }} 45 |
    46 | {{ range . }} 47 |
  • 48 | 49 | 50 | 51 |
    • 52 | {{ end }} 53 |
54 | {{ end }} 55 | {{ define "footer-links-block-text" }} 56 | 67 | {{ end }} -------------------------------------------------------------------------------- /layouts/shortcodes/img.html: -------------------------------------------------------------------------------- 1 | {{- $alt := .Get "alt" -}} 2 | {{- $res := resources.GetMatch (.Get "src") -}} 3 | {{- $ws := slice 480 768 1366 1920 -}} 4 | {{- $srcset := slice -}} 5 | {{- range $ws -}} 6 | {{/* to avoid creating an image that is larger than the source */}} 7 | {{- if (le . $res.Width) -}} 8 | {{- $w := printf "%dx" . -}} 9 | {{- $url := ($res.Resize $w).RelPermalink | safeURL -}} 10 | {{- $fmt := printf "%s %dw" $url . -}} 11 | {{- $srcset = $srcset | append $fmt -}} 12 | {{- end -}} 13 | {{- end -}} 14 | {{- $set := delimit $srcset "," -}} 15 |
16 | {{ $alt }} 23 |
{{ $alt }}
24 |
-------------------------------------------------------------------------------- /layouts/shortcodes/raw.html: -------------------------------------------------------------------------------- 1 | {{.Inner}} -------------------------------------------------------------------------------- /layouts/swagger/baseof.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | {{ if .Site.Params.GoogleAnalyticsID }} 5 | {{ partial "analytics-gtag.html" . }} 6 | {{ end }} 7 | {{ partial "head.html" . }} 8 | {{ if .IsHome }}{{ .Site.Title }}{{ else }}{{ with .Title }}{{ . }} | {{ end }}{{ .Site.Title }}{{ end }} 9 | 10 | 11 | 12 |
13 | {{ partial "navbar.html" . }} 14 |
15 |
16 |
17 |
18 | 21 | 26 |
27 | {{ if not .Site.Params.ui.breadcrumb_disable }}{{ partial "breadcrumb.html" . }}{{ end }} 28 | 29 | 30 | {{ block "main" . }}{{ end }} 31 |
32 |
33 |
34 | {{ partial "footer.html" . }} 35 |
36 | {{ partial "scripts.html" . }} 37 | 38 | 39 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "private": true, 3 | "scripts": { 4 | "format": "prettier --write assets/scss/*" 5 | }, 6 | "devDependencies": { 7 | "autoprefixer": "^10.4.14", 8 | "hugo-extended": "^0.118.2", 9 | "postcss": "^8.4.21", 10 | "postcss-cli": "^10.1.0", 11 | "prettier": "^3.0.3" 12 | } 13 | } 14 | -------------------------------------------------------------------------------- /static/assets/eclipse-leda-arch-overview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/eclipse-leda-arch-overview.png -------------------------------------------------------------------------------- /static/assets/eclipse-leda.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/eclipse-leda.png -------------------------------------------------------------------------------- /static/assets/googlefa99e46d982661fb.html: -------------------------------------------------------------------------------- 1 | google-site-verification: googlefa99e46d982661fb.html -------------------------------------------------------------------------------- /static/assets/icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/icon.png -------------------------------------------------------------------------------- /static/assets/leda-architecture-details.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/leda-architecture-details.png -------------------------------------------------------------------------------- /static/assets/project-logo/eclipse-leda-logo-cropped.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/project-logo/eclipse-leda-logo-cropped.png -------------------------------------------------------------------------------- /static/assets/project-logo/icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/project-logo/icon.png -------------------------------------------------------------------------------- /static/assets/project-logo/logo_01_rgb.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/project-logo/logo_01_rgb.jpg -------------------------------------------------------------------------------- /static/assets/project-logo/logo_01_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/project-logo/logo_01_rgb.png -------------------------------------------------------------------------------- /static/assets/project-logo/logo_02_rgb.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/project-logo/logo_02_rgb.jpg -------------------------------------------------------------------------------- /static/assets/project-logo/logo_02_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/static/assets/project-logo/logo_02_rgb.png -------------------------------------------------------------------------------- /static/googlefa99e46d982661fb.html: -------------------------------------------------------------------------------- 1 | google-site-verification: googlefa99e46d982661fb.html -------------------------------------------------------------------------------- /themes/.gitkeep: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/eclipse-leda/leda/fa3b1e531bfd8d0be87fc070160e84fc8f9ac60b/themes/.gitkeep -------------------------------------------------------------------------------- /vss/build-vss-docs.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # /******************************************************************************** 3 | # * Copyright (c) 2023 Contributors to the Eclipse Foundation 4 | # * 5 | # * See the NOTICE file(s) distributed with this work for additional 6 | # * information regarding copyright ownership. 7 | # * 8 | # * This program and the accompanying materials are made available under the 9 | # * terms of the Apache License 2.0 which is available at 10 | # * https://www.apache.org/licenses/LICENSE-2.0 11 | # * 12 | # * SPDX-License-Identifier: Apache-2.0 13 | # ********************************************************************************/ 14 | # 15 | # Setup: 16 | # sudo apt-get install python3.10 17 | # sudo apt-get update 18 | # sudo apt-get install pip 19 | # pip install vss-tools 20 | # git clone https://github.com/COVESA/vss-tools.git 21 | 22 | # git clone --recurse-submodules https://github.com/COVESA/vehicle_signal_specification 23 | # pushd vehicle_signal_specification 24 | # git checkout --detach 25 | # git for-each-ref refs/remotes/origin --format='../%(refname:lstrip=3) %(refname:lstrip=3)'|grep -v ' HEAD$' |xargs -n 2 git worktree add 26 | # popd 27 | 28 | ./vspecjson2markdown.py -I release/3.1/spec -i VehicleSignalSpecification.vspec -u release/3.1/spec/units.yaml -o output 29 | 30 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Body/Horn/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Horn 3 | 4 | date: 2023-06-05T12:38:42.047467 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Body.Horn` | 12 | | Description: | Horn signals. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Body 22 | 23 | Body-->Horn 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Body.Horn](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Body.Horn/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Body.Horn` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Body.Horn` is `09c76633887f52268b960740eb969c89` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Body.Horn.IsActive](isactive/) (Horn active or inactive. True = Active. False = Inactive.) 59 | 60 | 61 | ## Feedback 62 | 63 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 64 | 65 | | | | 66 | |---|---| 67 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Body.Horn) | 68 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 69 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 70 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 71 | 72 | ## About VSS 73 | 74 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 75 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 76 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 77 | 78 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Body/Lights/Beam/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Beam 3 | 4 | date: 2023-06-05T12:38:43.921691 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Body.Lights.Beam` | 12 | | Description: | Beam lights. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Body 22 | 23 | Body-->Lights 24 | 25 | Lights-->Beam 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.Body.Lights.Beam](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Body.Lights.Beam/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.Body.Lights.Beam` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.Body.Lights.Beam` is `6685308a9d955ecdad92a7cc68666a12` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.Body.Lights.Beam.High](high/) (Beam lights.) 61 | - [Vehicle.Body.Lights.Beam.Low](low/) (Beam lights.) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Body.Lights.Beam) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Body/Lights/Fog/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Fog 3 | 4 | date: 2023-06-05T12:38:44.342019 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Body.Lights.Fog` | 12 | | Description: | Fog lights. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Body 22 | 23 | Body-->Lights 24 | 25 | Lights-->Fog 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.Body.Lights.Fog](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Body.Lights.Fog/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.Body.Lights.Fog` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.Body.Lights.Fog` is `1e90cf42bb825217b283c7285a606953` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.Body.Lights.Fog.Front](front/) (Fog lights.) 61 | - [Vehicle.Body.Lights.Fog.Rear](rear/) (Fog lights.) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Body.Lights.Fog) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Body/Mirrors/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mirrors 3 | 4 | date: 2023-06-05T12:38:44.960044 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Body.Mirrors` | 12 | | Description: | All mirrors. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Body 22 | 23 | Body-->Mirrors 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Body.Mirrors](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Body.Mirrors/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Body.Mirrors` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Body.Mirrors` is `a4ea618914885a239ef5fa62c671a800` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Body.Mirrors.Left](left/) (All mirrors.) 59 | - [Vehicle.Body.Mirrors.Right](right/) (All mirrors.) 60 | 61 | 62 | ## Feedback 63 | 64 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 65 | 66 | | | | 67 | |---|---| 68 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Body.Mirrors) | 69 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 70 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 71 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 72 | 73 | ## About VSS 74 | 75 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 76 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 77 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 78 | 79 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Body/Raindetection/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Raindetection 3 | 4 | date: 2023-06-05T12:38:42.087766 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Body.Raindetection` | 12 | | Description: | Rainsensor signals. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Body 22 | 23 | Body-->Raindetection 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Body.Raindetection](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Body.Raindetection/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Body.Raindetection` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Body.Raindetection` is `f16759f3dcfb5be4832e962da29ebd6c` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Body.Raindetection.Intensity](intensity/) (Rain intensity. 0 = Dry, No Rain. 100 = Covered.) 59 | 60 | 61 | ## Feedback 62 | 63 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 64 | 65 | | | | 66 | |---|---| 67 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Body.Raindetection) | 68 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 69 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 70 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 71 | 72 | ## About VSS 73 | 74 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 75 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 76 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 77 | 78 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Body/Windshield/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Windshield 3 | 4 | date: 2023-06-05T12:38:42.129633 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Body.Windshield` | 12 | | Description: | Windshield signals. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Body 22 | 23 | Body-->Windshield 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Body.Windshield](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Body.Windshield/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Body.Windshield` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Body.Windshield` is `73efba535dcb5032b9edc43406b050b8` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Body.Windshield.Front](front/) (Windshield signals.) 59 | - [Vehicle.Body.Windshield.Rear](rear/) (Windshield signals.) 60 | 61 | 62 | ## Feedback 63 | 64 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 65 | 66 | | | | 67 | |---|---| 68 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Body.Windshield) | 69 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 70 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 71 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 72 | 73 | ## About VSS 74 | 75 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 76 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 77 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 78 | 79 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Cabin/Convertible/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Convertible 3 | 4 | date: 2023-06-05T12:39:01.284472 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Cabin.Convertible` | 12 | | Description: | Convertible roof. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Cabin 22 | 23 | Cabin-->Convertible 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Cabin.Convertible](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Cabin.Convertible/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Cabin.Convertible` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Cabin.Convertible` is `2aece85d39d6569e93cf842387a645d9` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Cabin.Convertible.Status](status/) (Roof status on convertible vehicles.) 59 | 60 | 61 | ## Feedback 62 | 63 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 64 | 65 | | | | 66 | |---|---| 67 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Cabin.Convertible) | 68 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 69 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 70 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 71 | 72 | ## About VSS 73 | 74 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 75 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 76 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 77 | 78 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Cabin/Door/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Door 3 | 4 | date: 2023-06-05T12:38:48.924439 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Cabin.Door` | 12 | | Description: | All doors, including windows and switches. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Cabin 22 | 23 | Cabin-->Door 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Cabin.Door](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Cabin.Door/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Cabin.Door` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Cabin.Door` is `fd7f4d16f8965419a9a69fd66b40c1d7` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Cabin.Door.Row1](row1/) (All doors, including windows and switches.) 59 | - [Vehicle.Cabin.Door.Row2](row2/) (All doors, including windows and switches.) 60 | 61 | 62 | ## Feedback 63 | 64 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 65 | 66 | | | | 67 | |---|---| 68 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Cabin.Door) | 69 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 70 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 71 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 72 | 73 | ## About VSS 74 | 75 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 76 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 77 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 78 | 79 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Cabin/RearviewMirror/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: RearviewMirror 3 | 4 | date: 2023-06-05T12:38:48.065514 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Cabin.RearviewMirror` | 12 | | Description: | Rearview mirror. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Cabin 22 | 23 | Cabin-->RearviewMirror 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Cabin.RearviewMirror](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Cabin.RearviewMirror/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Cabin.RearviewMirror` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Cabin.RearviewMirror` is `e655b654ab9f55bbb04952a99755efae` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Cabin.RearviewMirror.DimmingLevel](dimminglevel/) (Dimming level of rearview mirror. 0 = undimmed. 100 = fully dimmed.) 59 | 60 | 61 | ## Feedback 62 | 63 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 64 | 65 | | | | 66 | |---|---| 67 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Cabin.RearviewMirror) | 68 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 69 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 70 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 71 | 72 | ## About VSS 73 | 74 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 75 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 76 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 77 | 78 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Cabin/Seat/Row1/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Row1 3 | 4 | date: 2023-06-05T12:38:50.903862 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Cabin.Seat.Row1` | 12 | | Description: | All seats. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Cabin 22 | 23 | Cabin-->Seat 24 | 25 | Seat-->Row1 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.Cabin.Seat.Row1](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Cabin.Seat.Row1/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.Cabin.Seat.Row1` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.Cabin.Seat.Row1` is `7a420ddeac6f538eb3939bb4a242d136` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.Cabin.Seat.Row1.Pos1](pos1/) (All seats.) 61 | - [Vehicle.Cabin.Seat.Row1.Pos2](pos2/) (All seats.) 62 | - [Vehicle.Cabin.Seat.Row1.Pos3](pos3/) (All seats.) 63 | 64 | 65 | ## Feedback 66 | 67 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 68 | 69 | | | | 70 | |---|---| 71 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Cabin.Seat.Row1) | 72 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 73 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 74 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 75 | 76 | ## About VSS 77 | 78 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 79 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 80 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 81 | 82 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Cabin/Seat/Row2/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Row2 3 | 4 | date: 2023-06-05T12:38:55.981296 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Cabin.Seat.Row2` | 12 | | Description: | All seats. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Cabin 22 | 23 | Cabin-->Seat 24 | 25 | Seat-->Row2 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.Cabin.Seat.Row2](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Cabin.Seat.Row2/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.Cabin.Seat.Row2` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.Cabin.Seat.Row2` is `8c3aaf015ef8595cb45d9461a9c1195f` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.Cabin.Seat.Row2.Pos1](pos1/) (All seats.) 61 | - [Vehicle.Cabin.Seat.Row2.Pos2](pos2/) (All seats.) 62 | - [Vehicle.Cabin.Seat.Row2.Pos3](pos3/) (All seats.) 63 | 64 | 65 | ## Feedback 66 | 67 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 68 | 69 | | | | 70 | |---|---| 71 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Cabin.Seat.Row2) | 72 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 73 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 74 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 75 | 76 | ## About VSS 77 | 78 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 79 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 80 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 81 | 82 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Cabin/Seat/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Seat 3 | 4 | date: 2023-06-05T12:38:50.876880 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Cabin.Seat` | 12 | | Description: | All seats. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Cabin 22 | 23 | Cabin-->Seat 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Cabin.Seat](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Cabin.Seat/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Cabin.Seat` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Cabin.Seat` is `b0b253106b2851e3bb5c71ae3b09f09d` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Cabin.Seat.Row1](row1/) (All seats.) 59 | - [Vehicle.Cabin.Seat.Row2](row2/) (All seats.) 60 | 61 | 62 | ## Feedback 63 | 64 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 65 | 66 | | | | 67 | |---|---| 68 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Cabin.Seat) | 69 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 70 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 71 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 72 | 73 | ## About VSS 74 | 75 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 76 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 77 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 78 | 79 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Chassis/Accelerator/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Accelerator 3 | 4 | date: 2023-06-05T12:39:04.862923 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Chassis.Accelerator` | 12 | | Description: | Accelerator signals | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Chassis 22 | 23 | Chassis-->Accelerator 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Chassis.Accelerator](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Chassis.Accelerator/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Chassis.Accelerator` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Chassis.Accelerator` is `3b2b562086a45eb29c55186f3b710621` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Chassis.Accelerator.PedalPosition](pedalposition/) (Accelerator pedal position as percent. 0 = Not depressed. 100 = Fully depressed.) 59 | 60 | 61 | ## Feedback 62 | 63 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 64 | 65 | | | | 66 | |---|---| 67 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Chassis.Accelerator) | 68 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 69 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 70 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 71 | 72 | ## About VSS 73 | 74 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 75 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 76 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 77 | 78 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Chassis/Axle/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Axle 3 | 4 | date: 2023-06-05T12:39:02.999163 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Chassis.Axle` | 12 | | Description: | Axle signals | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Chassis 22 | 23 | Chassis-->Axle 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Chassis.Axle](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Chassis.Axle/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Chassis.Axle` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Chassis.Axle` is `0a3ebde7efa85c04ac6c29b5676fec5d` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Chassis.Axle.Row1](row1/) (Axle signals) 59 | - [Vehicle.Chassis.Axle.Row2](row2/) (Axle signals) 60 | 61 | 62 | ## Feedback 63 | 64 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 65 | 66 | | | | 67 | |---|---| 68 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Chassis.Axle) | 69 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 70 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 71 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 72 | 73 | ## About VSS 74 | 75 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 76 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 77 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 78 | 79 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Chassis/ParkingBrake/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: ParkingBrake 3 | 4 | date: 2023-06-05T12:39:04.661581 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Chassis.ParkingBrake` | 12 | | Description: | Parking brake signals | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Chassis 22 | 23 | Chassis-->ParkingBrake 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.Chassis.ParkingBrake](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Chassis.ParkingBrake/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.Chassis.ParkingBrake` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.Chassis.ParkingBrake` is `3849d42292f4551590fa4bf716fc90f7` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.Chassis.ParkingBrake.IsEngaged](isengaged/) (Parking brake status. True = Parking Brake is Engaged. False = Parking Brake is not Engaged.) 59 | 60 | 61 | ## Feedback 62 | 63 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 64 | 65 | | | | 66 | |---|---| 67 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Chassis.ParkingBrake) | 68 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 69 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 70 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 71 | 72 | ## About VSS 73 | 74 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 75 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 76 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 77 | 78 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Connectivity/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Connectivity 3 | 4 | date: 2023-06-05T12:39:09.457411 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Connectivity` | 12 | | Description: | Connectivity data. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Connectivity 22 | 23 | ``` 24 | 25 | 26 | ## Digital Auto: Playground 27 | 28 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 29 | 30 | | Vehicle Model | Direct link to Vehicle Signal | 31 | |---|---| 32 | | ACME Car (EV) v0.1 | [Vehicle.Connectivity](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Connectivity/) | 33 | 34 | 35 | ## Signal Information 36 | 37 | 38 | 39 | 40 | The vehicle signal `Vehicle.Connectivity` is a **Branch**. 41 | 42 | 43 | 44 | 45 | 46 | ## UUID 47 | 48 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 49 | 50 | The UUID for `Vehicle.Connectivity` is `89c267fccea35f3da9871cca2b4dc4df` 51 | 52 | ## Children 53 | 54 | This vehicle signal is a branch or structure and thus has sub-pages: 55 | 56 | - [Vehicle.Connectivity.IsConnectivityAvailable](isconnectivityavailable/) (Indicates if connectivity between vehicle and cloud is available. True = Connectivity is available. False = Connectivity is not available.) 57 | 58 | 59 | ## Feedback 60 | 61 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 62 | 63 | | | | 64 | |---|---| 65 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Connectivity) | 66 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 67 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 68 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 69 | 70 | ## About VSS 71 | 72 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 73 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 74 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 75 | 76 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/Catalyst/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Catalyst 3 | 4 | date: 2023-06-05T12:39:07.854638 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.Catalyst` | 12 | | Description: | Catalyst signals | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->Catalyst 24 | 25 | ``` 26 | 27 | 28 | ## Digital Auto: Playground 29 | 30 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 31 | 32 | | Vehicle Model | Direct link to Vehicle Signal | 33 | |---|---| 34 | | ACME Car (EV) v0.1 | [Vehicle.OBD.Catalyst](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.Catalyst/) | 35 | 36 | 37 | ## Signal Information 38 | 39 | 40 | 41 | 42 | The vehicle signal `Vehicle.OBD.Catalyst` is a **Branch**. 43 | 44 | 45 | 46 | 47 | 48 | ## UUID 49 | 50 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 51 | 52 | The UUID for `Vehicle.OBD.Catalyst` is `4eb0b191d6445de081f3f3f759af31c2` 53 | 54 | ## Children 55 | 56 | This vehicle signal is a branch or structure and thus has sub-pages: 57 | 58 | - [Vehicle.OBD.Catalyst.Bank1](bank1/) (Catalyst bank 1 signals) 59 | - [Vehicle.OBD.Catalyst.Bank2](bank2/) (Catalyst bank 2 signals) 60 | 61 | 62 | ## Feedback 63 | 64 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 65 | 66 | | | | 67 | |---|---| 68 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.Catalyst) | 69 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 70 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 71 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 72 | 73 | ## About VSS 74 | 75 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 76 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 77 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 78 | 79 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor1/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor1 3 | 4 | date: 2023-06-05T12:39:05.824279 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor1` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor1 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor1](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor1/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor1` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor1` is `3aa8859203d4545083196a9690d72627` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor1.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor1.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor1) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor2/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor2 3 | 4 | date: 2023-06-05T12:39:05.889659 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor2` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor2 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor2](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor2/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor2` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor2` is `efcb337cf94056c8a724e76bcfee6765` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor2.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor2.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor2) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor3/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor3 3 | 4 | date: 2023-06-05T12:39:05.953469 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor3` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor3 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor3](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor3/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor3` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor3` is `b8c145402b7a5cffaa2699ed61b056fa` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor3.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor3.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor3) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor4/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor4 3 | 4 | date: 2023-06-05T12:39:06.013688 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor4` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor4 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor4](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor4/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor4` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor4` is `853945bce86c5c4f95081075ae32261c` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor4.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor4.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor4) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor5/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor5 3 | 4 | date: 2023-06-05T12:39:06.075508 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor5` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor5 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor5](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor5/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor5` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor5` is `f48c76c9c7ec5ddcb6838ced0bd7517b` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor5.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor5.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor5) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor6/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor6 3 | 4 | date: 2023-06-05T12:39:06.150343 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor6` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor6 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor6](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor6/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor6` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor6` is `5269c1877ded507b87d7d1d7bec10605` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor6.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor6.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor6) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/OBD/O2/Sensor7/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sensor7 3 | 4 | date: 2023-06-05T12:39:06.225409 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.OBD.O2.Sensor7` | 12 | | Description: | Oxygen sensors (PID 14 - PID 1B) | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->OBD 22 | 23 | OBD-->O2 24 | 25 | O2-->Sensor7 26 | 27 | ``` 28 | 29 | 30 | ## Digital Auto: Playground 31 | 32 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 33 | 34 | | Vehicle Model | Direct link to Vehicle Signal | 35 | |---|---| 36 | | ACME Car (EV) v0.1 | [Vehicle.OBD.O2.Sensor7](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.OBD.O2.Sensor7/) | 37 | 38 | 39 | ## Signal Information 40 | 41 | 42 | 43 | 44 | The vehicle signal `Vehicle.OBD.O2.Sensor7` is a **Branch**. 45 | 46 | 47 | 48 | 49 | 50 | ## UUID 51 | 52 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 53 | 54 | The UUID for `Vehicle.OBD.O2.Sensor7` is `4b565102e4a052aa8aa64f27dc678ce3` 55 | 56 | ## Children 57 | 58 | This vehicle signal is a branch or structure and thus has sub-pages: 59 | 60 | - [Vehicle.OBD.O2.Sensor7.ShortTermFuelTrim](shorttermfueltrim/) (PID 1x (byte B) - Short term fuel trim) 61 | - [Vehicle.OBD.O2.Sensor7.Voltage](voltage/) (PID 1x (byte A) - Sensor voltage) 62 | 63 | 64 | ## Feedback 65 | 66 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 67 | 68 | | | | 69 | |---|---| 70 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.OBD.O2.Sensor7) | 71 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 72 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 73 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 74 | 75 | ## About VSS 76 | 77 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 78 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 79 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 80 | 81 | -------------------------------------------------------------------------------- /vss/output/Vehicle/Trailer/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Trailer 3 | 4 | date: 2023-06-05T12:38:36.059750 5 | no_list: true 6 | --- 7 | 8 | 9 | | | | 10 | |---|---| 11 | | Full qualified VSS Path: | `Vehicle.Trailer` | 12 | | Description: | Trailer signals. | 13 | 14 | ## Navigation 15 | 16 | ```mermaid 17 | flowchart LR 18 | 19 | 20 | 21 | Vehicle-->Trailer 22 | 23 | ``` 24 | 25 | 26 | ## Digital Auto: Playground 27 | 28 | [playground.digital.auto](http://digital.auto) provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles. 29 | 30 | | Vehicle Model | Direct link to Vehicle Signal | 31 | |---|---| 32 | | ACME Car (EV) v0.1 | [Vehicle.Trailer](https://digitalauto.netlify.app/model/STLWzk1WyqVVLbfymb4f/cvi/list/Vehicle.Trailer/) | 33 | 34 | 35 | ## Signal Information 36 | 37 | 38 | 39 | 40 | The vehicle signal `Vehicle.Trailer` is a **Branch**. 41 | 42 | 43 | 44 | 45 | 46 | ## UUID 47 | 48 | Each vehicle signal is identified by a [Universally Unique Identifier (UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier)) 49 | 50 | The UUID for `Vehicle.Trailer` is `66206ee5c25a5817bef214c0c8ae8013` 51 | 52 | ## Children 53 | 54 | This vehicle signal is a branch or structure and thus has sub-pages: 55 | 56 | - [Vehicle.Trailer.IsConnected](isconnected/) (Signal indicating if trailer is connected or not.) 57 | 58 | 59 | ## Feedback 60 | 61 | Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community: 62 | 63 | | | | 64 | |---|---| 65 | | Enhancement request | [Create COVESA GitHub Issue](https://github.com/COVESA/vehicle_signal_specification/issues/new?body=Please+describe+your+feedback&title=Signal+feedback+Vehicle.Trailer) | 66 | | Join COVESA | [www.covesa.global](https://www.covesa.global/join?src=sidebar) | 67 | | Discuss VSS on Slack | [w3cauto.slack.com](http://w3cauto.slack.com/) | 68 | | VSS Data Experts on Google Groups | [covesa.global data-expert-group](https://groups.google.com/a/covesa.global/g/data-expert-group) | 69 | 70 | ## About VSS 71 | 72 | The [Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) 73 | is an initiative by COVESA to define a syntax and a catalog for vehicle signals. 74 | The source code and releases can be found in the [VSS github repository](https://github.com/COVESA/vehicle_signal_specification). 75 | 76 | --------------------------------------------------------------------------------