vehicle_signal_specification
vehicle_signal_specification copied to clipboard
COVESA
Vehicle Signal Specification - standardized way to describe automotive data
This is a PR for cherry-picking items from vss/vss-tools master to 4.X_branch. This PR shall not be merged "as is" but rather be added by a push directly to 4.X....
This PR introduces signals like `Vehicle.Driver.HeadPosition.X` and `Vehicle.Driver.MidEyeGaze.Azimuth`. They can be useful in driver monitoring system to detect what the driver is looking at, and/or to monitor that the driver...
This PR is rework of PR #699 . The type of SmartphoneScreenMirroring.Resolution is changed to 'sensor'. The differences of smartphone screen mirroring with smartphone projection as follow: Screen Mirroring, such...
Hi, I'd like to update Driver.vspec. The updates include: Introduction & FatigueLevel
- Regarding the specification for Vehicle.Timeincurrentrip, could you please clarify if it's possible to utilize the variables x and y defined in the parameters section to perform a mathematical operation...
I have noticed that the documentation and tools are not consistent in using terminology to describe the elements that define the meta data for a node (such as type, datatype,...
I found something really interesting in vspec 3.0 there is a typo ``` Actuator ``` instead of ```actuator``` https://github.com/COVESA/vehicle_signal_specification/blob/525e2bd00ddf061851bdc75e849178e5d3ad5833/spec/Powertrain/Battery.vspec#L229C9-L229C17 and this makes load_tree impossible for vspec definiton 3.0 Suggested fix...
the code generated through vss for francaidl (.fidl) is not recognized and give too many syntactical errors . 
# Connectivity Enhancements This is my first draft for enhancements to the rather barebones connectivity spec. **Important note:** This spec uses units defined in https://github.com/COVESA/vss-tools/pull/207. ## Design Fundamentally, I decided...
