Grid tab on the pattern document toolbar to launch the pattern grid view. Use this view to see components of the binary pattern
file, including time sets, labels, opcodes, vector numbers, pin state data that indicates drives and compares, comments for
each vector, exported labels, and comments from the top of the file. Use the pattern waveform view for a graph-based representation of the pattern. You can select and right-click vectors in the pattern grid view and select
Show Vectors in Waveform View from the context menu to launch the pattern waveform view. You can also click the
Waveform tab on the pattern document toolbar to launch the pattern waveform view. An asterisk (*) next to a filename in the Project Explorer window and in the document tab indicates that the file has been modified but
Configuring the Pattern
The grid view includes the following components:
Pattern Name — Specifies the pattern name as defined in the pattern declaration of the pattern file. If you change the pattern name, you
must manually update any other references to the pattern name. Names must begin with an ASCII letter or underscore (_) and are limited to
The pattern name is independent from the filename of the pattern file.
You must explicitly export the pattern name as a global label to use it as the target of an opcode from another pattern.
Loaded/Not Loaded/Out of Sync — Indicates whether the pattern is loaded on the digital pattern instrument.
Out of Sync indicates that the pattern loaded on the instrument does not match the pattern file opened in the document.
Keep Alive Pattern — Indicates that the pattern is a keep alive pattern. The toolbar includes only buttons relevant to keep alive patterns.
To burst a keep alive pattern, first load the keep alive pattern and then burst a standard pattern that jumps to a keep alive
Passed/Failed/Disabled — Indicates the status of compares in the last burst of the pattern or indicates that the site was disabled for the last
burst of the pattern. The editor briefly highlights the Passed/Failed status icon to indicate that the pattern finished bursting.
Total Failures — Displays the number of failures in the pattern.
Burst Complete — Displays the timestamp of the last pattern burst.
Comments, Exports, and Time Sets — Displays comments, exported labels, and time sets used. Use the expander
buttons to expand or collapse this section.
Comments — Specifies the comments at the top of the text pattern file.
By default, importing or compiling a text pattern file (.digipatsrc) into a binary version of the pattern file (.digipat) preserves comments. To remove comments when you create a compiled, binary version of the pattern file, use the
-no-comments command-line option in the Digital Pattern Compiler.
Export Labels — Specifies the labels the pattern exports for other patterns to use as opcode targets. You must manually update all references
to the export labels when you make changes in the pattern document. You must explicitly export the pattern name as a global label to use it as the target of an opcode from another pattern.
The first vector in a pattern file is automatically assigned a label that matches the pattern name.
Time Sets Used — Displays the time sets used in the pattern.
Time Set — Specifies an existing, defined time set to use for the vector. You can add and modify time sets directly in the pattern,
but if the time set does not exist on the instrument, the Digital Pattern Editor returns an error at pattern load or run time.
Do not use a dash (-) for the time set on the first vector of a pattern file unless the file is used only as a target of a jump or call operation.
Refer to the
Related reference section at the end of this topic for a link to more information about timing. Refer to the specifications document for the digital pattern instrument for more information about the number of supported
Label — Specifies a vector label. If you rename or delete a label, you must manually update any other references to that label to avoid run-time errors. Names must begin with an ASCII letter or underscore (_) and are limited to
_ characters. The Digital Pattern Editor assumes that any label you reference but do not specify in a pattern is an imported label.
Opcode — Specifies the opcodes the pattern sequencer executes on the vector. You can combine certain opcodes on a single vector by separating the opcodes with a comma. Refer to the
Related reference section at the end of this topic for a link to more information about opcodes.
Pin or Pin Group Data — Specifies the pin state data that indicates drives and compares for pins and pin groups for the vector. Pins or pin groups
you reference in the pattern must be defined in the pin and channel map.
For pin groups, click the format specifier
in the column heading to change the numeric representation of the pin state data. Click the Expand
button to view or hide the individual pins in a pin group. This column uses the following symbols:
Currently, the Digital Pattern Editor does not support using system pins in patterns. To burst from a pin that spans all sites,
configure a pin with a shared pin connection in the Pin Map Editor to share a channel across multiple sites and use that pin
in your pattern instead.
0 — Drive zero.
1 — Drive one.
L — Compare low.
H — Compare high.
X — Do not drive; mask compare.
M — Compare midband, not high or low.
V — Compare high or low, not midband; store results from capture functionality if configured.
D — Drive data from source functionality if configured.
E — Expect data from source functionality if configured.
- — Repeat previous cycle. Do not use a dash (-) for the pin state on the first vector of a pattern file unless the file is used only as a target of a jump or call operation.
On power-up, pins are in a high impedance state. To avoid unexpected results for DUTs that are sensitive to the initial state of a pattern burst, programmatically specify
the initial pin state by using the niDigital Write Static VI, the DigitalPinSet.WriteStatic .NET method, or the niDigital_WriteStatic
C function. You can interactively set the initial state for a pin by selecting the corresponding driver symbol in the Drive
section of the Pin View pane of the Digital Pattern Editor.
After each pattern burst, the ending state of the last executed vector persists until the start of the next pattern burst
or until you programmatically or interactively change the pin state or pin function.
When using the edge multiplier feature, not all pins will require all the available cells if a vector contains a mixture of
edge multiplier values. The unused cells will display as blank cells. Adding pin state data to these blank cells will change
the edge multiplier value for that pin on that vector.
Comment — Specifies multiple lines of text as comments.
This field does not accept the <Enter> or <Tab> keys. You can use Ctrl+<Enter> to start a new line in this field. The editor displays multi-line comments in a tooltip when you
hover over a comment cell that contains multiple lines.
Keyboard Shortcuts within the Pattern Grid View
|Start a new line inside a cell in the comments column
|Start in-place editing
|Find next occurrence of current selection
|Find previous occurrence of current selection
|Expand selected scan vector
Use the Add Sign (+) on the numeric keyboard.
|Collapse selected scan vector
Use the Minus Sign (-) on the numeric keyboard.