-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSS / VSC integration of operations and signals for the same function #83
Comments
I think this is quite aligned with what we discussed recently, that VSC can be used for more advanced control of execution. Something like the seat service can be good example. Theoretically you can control e.g. horizontal position and recline directly by VSS-signals. But then you do not really get any feedback if the requested change could not be executed. And the movement may not be optimal or even unsafe for the driver. So it might be so that only e.g. the vehicle computer is allowed to set the VSS actuators, others must change them through services. VSC services could be a way to encapsulate business logic. Like in the hypothetical example below. Recline and position are depending on each other, and a service could control conditions and movement to give a good user example. The service implementation itself may use VSS, but even if we would standardize "move_seat" the implementation shall most likely not be standardized, as it would be very vehicle specific.
|
Since this is a question for the definition of the language/interface-model that is now IFEX project, the issue will be transferred from Vehicle Service Catalog project to IFEX project. |
while VSS signals behavior is defined in VSS (e.g. that writing to an actuator is seen as a target-value, and reading is current-value)
Consider also:
Go through some examples to figure out how to do this.
The text was updated successfully, but these errors were encountered: