How to modify virtual vehicle composer(VVC)

Hello, I have some inquiries regarding the usage of Virtual Vehicle Composer (VVC).

1. It seems that when building vehicle models through VVC, values cannot be confirmed via Scope blocks or log selected signals in the Simulink model "ConfiguredVirtualVehicleModel." Do I have to rely solely on VVC's Simulation Data Inspector? Using "To workspace" for values also feels inconvenient. Is there a way to activate Scope blocks within VVC?
2. I want to use my own controller in the VVC, but changing the controller seems quite challenging. For instance, I simply want to input the steering angle and throttle as outputs of the controller to the Vehicle model. I wonder if all signals that the ConfiguredVirtualVehicleModel/Vehicle/Plant Models(Figure) receive as inputs need to be defined. It seems difficult to verify all signals, so is there a more concise way to design the controller? Do I need to define all signals that were previously connected when modifying the Simulink model?

Answer 1

[Mike Sasena]

Thanks for your questions about the VVC. I'll answer them separately.

1. If you want to view signals that are not available in the list shown in the "Logging" tab of the app, then the recommendation is to just work directly in the ConfiguredVehicleModel after you generate it. You can log any signals you want in that model by simply clicking on the signal line and turning on logging. No need to add "To Workspace" blocks or scopes, which can quickly make the model quite messy. You can even do that programmatically if you prefer. For more info, check out this help page.
2. The short answer is 'no', you don't need to reference every single input signal defined in the interface for your custom controller. You can use a subset of them. For more a more detailed discussion on variants in Simulink, check out this help page.

[JGP]

Thanks, I'll give it a try.