Open Trunk Extern Application#

Note

Start instance:
sdv_control STARTUP –instance3005
Connect to this instance:
open_trunk_example 3005

Note

  • A Complex Service offers an Interface to open the trunk.

  • Before the command is forwarded to the Basic Service the vehicle speed is checked and denied accordingly.

  • Therefore the Complex Service can be seen as an ASIL A component.

  • The Basic Service must offer its Interface over the process border: That’s why the Proxy & Stub code is required.

  • If there is a second VAPI instance which represent a QM instance the connection to the Basic Service can be prevented in general for QM Function s.

  • In that case opening the trunk can not be triggered when the vehicle is moving.

../../../_images/open_trunk_screenshot_3005.png

The Speed signal is coming via CAN bus by using the VAPI Component can_com_sim.sdv from the framework. The VAPI Component reads the CAN messages from a text file and sends these messages to the Data Link The Data Link component is created from a dbc file with the help of the helper tool sdv_bcd_util.

Attention

To prevent the bypassing of the Complex Service we need Mixed-Criticality. That can be done when we run two Instances, one in QM Mode, the other in Safety Mode. The connection from The QM instance to the Basic Service can be prevented.

In the example we still run only one instance, that’s why we still have direct access to the Basic Service.

../../../_images/open_trunk_mixed-critical.png

See also

Mixed-Criticality