You will notice that a number of ﬁelds in the System Properties in Property Editor window (bottom left) are now editable, i.e., the text is no longer grey and italic. On the model level you can change a number of settings like common model properties, descriptions, linked objects, target parameters as well as set the default values for parameters.
Select the model instance Ramp#1 in the Model Editor window with a single mouseclick. Notice the Instance Properties tab becomes active in Property Editor window showing the settable parameters value and step of the model instance Ramp#1. A double click on the model instance opens the primitive at its original location. The title bar of the primitive Model Editor window shows where the primitive is physically saved.
Notice that it is not possible to edit any property in the Primitive Properties tab of the built-in primitive. Click on the input port to see the port properties. The type of data consumed by the primitive is determined by the port type. You cannot change the characteristics of the built-in primitive, but only the way the primitive behaves when the simulation is run.
Close the primitive Model Editor window and click the background of the testPacket system in the Model Editor window. Click on the Switch to Simulation Mode button on the toolbar.
To run the simulation using the default settings click the Go button. The system is compiled and executed and an XMgraph titled “Packetized signal output” displays showing the original signal compared to the packetized signal. The total RunLength is set to 50 with a Step Increment of 1. Click on each model instance and look at the parameters that inﬂuence the output of this system.
The model instance Packetize#1 waits until it has 5 events (maxLength) before ﬁring. Notice that the model instance VarServer#1 with serviceTime set to 1.0, can process 50 samples in packages of 5 deﬁned by the Packetize#1 model instance parameter maxLength.
We now want to change some parameters and run the simulation again.
Notice the difference in server time as a proportion of the total simulation time of the original unpacketized output.
There are a few simulation control buttons on the toolbar that are not used because the simulation is very quick. These icons are useful for longer simulation runs.