Hi,
Indeed this refers to placing Signal Outport blocks from the PLECS (Standalone) component library in your top-level schematic, not in the same way for use within a subsystem block (or to connect to Simulink since PLECS Blockset doesn’t use this internal scripting concept). Have you seen the demo model included in PLECS called “Buck Converter with Parameter Sweep” (this is the model that the example script in the documentation is based on)? See the attached screenshot from that model showing how the Outport block is connected to a Probe block, such that any probed signals will be saved as part of the resultant simulation struct.
By the way, if you added another Outport to the top-level schematic it would extend the length of the simulation struct with new Value data (e.g., if Outport 1 was connected to a bus of width 2 and Outport 2 was connected to a bus of width 1 then Out.Values(1:2,
is associated with the first Outport and Out.Values(3, is associated with the second Outport.
Let me know if this is clear.
Kris
