NI-SCOPE LabVIEW VIs

Content Type
Programming Language
Current manual

niScope Initialize

niScope Initialize

Performs the following initialization actions:

-Creates a new IVI instrument driver session.

-Opens a session to the device(s) that you specify in the resource name parameter.

-Queries each instrument ID and verifies that it is valid for this instrument driver.

-Resets the instrument(s) to a known state if the reset device parameter is set to TRUE; refer to niScope Reset for the default state of each digitizer.

-Sends initialization commands to set the instrument(s) to the state necessary for the operation of the instrument driver.

-Returns an instrument handle that you use to identify the instrument(s) in all subsequent instrument driver VI calls.

You can create sessions that include multiple instruments of the same model and in the same chassis. This automatically synchronizes all channels of the included instruments, simplifying your test program development and maintenance.

Related topics

niScope Initialize

cio.gif

resource name specifies the device name assigned by Measurement & Automation Explorer (MAX) to an NI-SCOPE instrument, for example, PXI1Slot3, where PXI1Slot3 is an instrument resource name.

This parameter accepts a comma-delimited list of strings in the form PXI1Slot3,PXI1Slot4, where PXI1Slot3 is one instrument resource name and PXI1Slot4 is another.

Note  You can only specify multiple instruments of identical model numbers, bus types, channel counts, and onboard memory sizes. The instruments must be in the same chassis.

Examples

Example Device Type Syntax
1 NI-DAQmx device myDAQmxDevice (myDAQmxDevice = device name)
2 NI-DAQmx device DAQ::myDAQmxDevice (myDAQmxDevice = device name)
3 NI-DAQmx device DAQ::2 (2 = device name)
4 IVI logical name or IVI virtual name myLogicalName (myLogicalName = name)

For NI-DAQmx devices, the syntax is just the device name specified in MAX, as shown in Example 1. Typical default names for NI-DAQmx devices in MAX are Dev1 or PXI1Slot1. You can rename an NI-DAQmx device by right-clicking on the name in MAX and entering a new name.

An alternative syntax for NI-DAQmx devices consists of DAQ::NI-DAQmx device name, as shown in Example 2. This naming convention allows for the use of an NI-DAQmx device in an application that was originally designed for a Traditional NI-DAQ device. For example, if the application expects DAQ::1, you can rename the NI-DAQmx device to 1 in MAX and pass in DAQ::1 for the resource name, as shown in Example 3.

You can also pass in the name of an IVI logical name or an IVI virtual name configured with the IVI Configuration utility, as shown in Example 4. A logical name identifies a particular virtual instrument. A virtual name identifies a specific device and specifies the initial settings for the session.

Note  NI-DAQmx device names are not case-sensitive. However, all IVI names, such as logical names, are case-sensitive. If you use logical names, driver session names, or virtual names in your program, you must make sure that the name you use matches the name in the IVI Configuration Store file exactly, without any variations in the case of the characters.
cbool.gif

id query verifies that the digitizer you initialize is supported by NI-SCOPE. NI-SCOPE automatically performs this query, so setting this parameter is not necessary.

cbool.gif

reset device specifies whether to reset the instrument during the initialization procedure.

Default Value: TRUE

cerrcodeclst.gif

error in describes error conditions that occur before this node runs. This input provides standard error in functionality.

iio.gif

instrument handle identifies a particular instrument session.

ierrcodeclst.gif

error out contains error information. This output provides standard error out functionality.

In This Section
Was this information helpful?