TestDrive’s graphical user interfaces, or GUIs for short, offer a particular and useful option: Customizability. Indeed, your own GUI can be easily created with LabVIEW. This document covers the case of the Virtual Scope Manager VI. This VI is used in conjunction with the OpVirtualScope Simulink block.

To see how the Virtual Scope Manager’s VI can be used, open a GUI in <TestDriveX.Y root>\Panels\VirtualScope\GUI\<GUI>.vi. You just must put the ‘Virtual Scope Manager’ in the block diagram of your GUI and set its I/O as follows:

Input: ID

This ID is a string that must correspond to the ‘ID’ parameter of the Simulink block.

Input: Scope Elements

• Cluster (typedef) of references to controls and indicators that are part of the Display
• Named typedefs make it easy to link the correct control to the correct
• If you do not link a reference, the corresponding functionality will not be See the list of Required Controls.

Input: File Management

• Cluster (typedef) of references to controls and indicators that are part of the data logging options.
• Named typedefs make it easy to link the correct control to the correct
• If you do not link a reference, the corresponding functionality will not be See the list of Required Controls.

Output: Waveform Graph

Before you can use your brand-new GUI in TestDrive, you must first initialize your Waveform Graph. This will allow the Virtual Scope Manager to send data to it. Simply wire the output of the ‘VirtualScopeManager’ VI to your Waveform Graph. Once connected (the graph icon should be brown), feel free to remove the wire. Do not forget to save your VI.

Required Controls

There are a few required controls:

• A Waveform Graph
• An Arm switch to enable data acquisition
• An array of Booleans corresponding to the Active Channels