Creates and configures simulation tests. Although initial conditions and test sessions are properly a part of a test’s configuration, these aspects of a test are dealt with in their own forms. See Initial Conditions... and Test Sessions....
Once a test is created and saved to the real-time host, most settings cannot be changed: only the settings on the individual models and the condition sets (including selecting the default one) can be changed on a saved test. This prevents invalidating archived log files. To run a variation of a test, use the Copy button to create an editable copy.
Replaces the simple list of tests on the left side of the form with a detailed list of tests at the top of the form:
Filter Tests
Displays in the test lists only tests whose name matches the regular expression. See Regular Expressions.
Demonstrate
Opens a short video clip that demonstrates the basic workflow of this form.
Help
Opens this section of the manual.
Delete
Deletes the selected test.
Copy
Creates a copy of the selected test. Since saved tests cannot be edited, the alternative is to create a copy of the saved test and make the desired changes to the copy. The copy will be assigned a unique name based on the original test’s name. Until the test is saved to the real-time host, the name and other settings can be edited.
New
Creates a new test. The new test will be assigned a unique name. Until the test is saved to the real-time host, the name and other settings can be edited.
Current RTDB
Shows the name of the real-time database currently loaded for editing. See New/Select RTDB....
Apply
Commits all pending edits to the real-time host. See Apply .
Cancel
Discards all pending edits.
Test List
Simple list of tests on the left side of the form, or a detailed list of tests at the top of the form, depending on the Detailed List option. Select a test from the list by clicking on it. This will show that test’s settings and enable the editing buttons at the bottom left corner of the form.
Test Name
Name of the selected test. The name of copied and new tests may be edited until they are saved to the real-time host by pressing the Apply button.
Conditions
Default initial conditions set of the selected test. New tests have an initial conditions set called Default-models-RTDB by default. Initial conditions sets may be created and edited in the Initial Conditions form, but only after the test has been saved to the server. The default initial conditions set can be changed on a saved test. See Initial Conditions....
Test Script
Optional script that is run during stage 2 of the test cycle of the selected test. This setting cannot be changed on a saved test. Create a copy of test with a different script instead. See Scripts... and Test Script.
RTDB
Real-time database used by the selected test. This setting cannot be changed on a saved test. Create a copy of the test with a different RTDB instead. See Mapping I/O Points to Hardware.
Description
Description of the selected test for documentation purposes. This setting cannot be changed on a saved test. Create a copy of the test with a different description instead.
Group
Group that the selected test belongs to. See Group Table.
Fixed Step
Duration of a test cycle of the selected test. This setting can only be set on tests with no Simulink models. Simulink models define the test cycle duration themselves. This setting cannot be changed on a saved test. Create a copy of the test with a different fixed step instead.
The unit in which fixed step is presented and entered is selectable. Click on the units after the field to cycle through microseconds, milliseconds, and seconds. All fields presenting the fixed step value throughout the Control Center will use the same unit and the unit choice is preserved across invocations of the Control Center.
Model Region
Contains models that will be run during stage 3 of the test cycle and the models’ settings. Models are located in the region at the bottom of the form. Models cannot be added, removed, replaced, or have their dependencies changed on a saved test: create a copy of the test with different models or different dependencies instead. Settings on the individual models (set in the frames located in the model region) can be changed on a saved test.
The arrows drawn between models indicate dependency. A model must finish running before models it points to may begin running. See Scheduler Period Run.
To add a model, right click in an empty area in the model field and select a model from the context menu that appears.
To delete a model click on the (close) button in the upper right corner.
To toggle a dependency between two models, position the mouse on an empty area in the model’s frame, then click and drag from that model’s frame to the frame of a model that depends on the first model and release the mouse button. An arrow will be drawn between the two model’s frames, or erased if there was one already.
Settings may be made in the frames located in the model region, even if the test is saved to the real-time host. Multirate Simulink models have an additional table to allow setting the CPU on each thread.
CPU
CPU on which the model will run during a test run. This setting can be changed on a saved test. The Real-Time Viewer can change the CPU assignment of a model dynamically while the test is running. See Synchronous Tab.
Priority
Scheduling priority at which that the model will run during a test run. This setting can be changed on a saved test.
Policy
Scheduling policy with which that the model will run during a test run. This setting can be changed on a saved test. See Scheduling Parameters.
Other
Non-real-time, interactive scheduling policy.
Round Robin
Real-time scheduling policy where a process whose time quantum has expired can be preempted by another process of the same priority.
FIFO
Real-time scheduling policy where a process can not preempted by another process of the same priority.
Frq Div
Sets the frequency in terms of the test cycle’s duration (Fixed Step) at which the model will be run. Setting the first number to N will cause the model to only run once every N test cycles. The second number specifies which of those N test cycles the model will run on.
For example, if two models both set the first number to 2, but one sets the second number to 0 and the other one sets the second number to 1, then the first model will execute on even test cycles, and the second one on odd test cycles.
Tid Column
Multirate Simulink models have some number of threads that run at rates that are whole multiples of the model’s base rate. These threads are numbered from 1.
Rate (sec) Column
Displays the rate (in seconds) that each thread runs at. This is set when the Simulink model is created and built and cannot be modified here.
CPU Column
The CPU assigned to each thread. This may be edited here by double-clicking on the cell and typing in a new CPU number.