Each issue appears as a row in the table and includes the following fields:
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 743150 Return | The oscilloscope panel stops monitoring correctly when you start an external session with additional devices. If you monitor an external session with the oscilloscope panel in InstrumentStudio, then stop the external session and start a new session with one or more additional oscilloscope devices, InstrumentStudio doesn't detect the new session and switches between the Waiting and Stopped state. Workaround: Close the current Oscilloscope panel and open a new one.
| |||||
| 743144 Return | SMU channel generation status indicator may be incorrect if channels are changed from a non-Idle operating mode (such as Voltage) to Idle while the panel is running. If you configure an SMU channel to utput a signal, then change its operating mode to Idle, the SMU panel may incorrectly show the generation status as "Stopped" even though the channel is still generating a signal. Workaround: n/a
| |||||
| 742728 Return | Swapping names of SMU devices in NI-MAX may cause problems relinking devices. Duplicating and swapping names of enabled devices may cause problems with relinking devices to soft front panels in InstrumentStudio. Avoid duplicate names if possible.
| |||||
| 742331 Return | The overload protection error is not shown if protection limits are hit during sequences over six seconds. If an SMU or power supply enters overload protection mode after exceeding the voltage or current protection limit when running a current or voltage sequence lasting longer than six seconds, InstrumentStudio may not return an overload protection error.
| |||||
| 742279 Return | Asymmetric limits are not shown in the attribute list for an IO Configuration exported from InstrumentStudio to TestStand. If you have configured an SMU or power supply to use asymmetric limits in InstrumentStudio, those limits are not visible in the attribute list for the IO Configuration exported to TestStand. Instead, the value of Current Limit or Voltage Limit is incorrectly shown. The asymmetric limits as configured in InstrumentStudio will still be correctly applied to the session by the Create Sessions and Apply Configuration step. Workaround: To view the configured asymmetric limits, open the IO Configuration file in TestStand, navigate to the Create Sessions and Apply Configuration step, and click the InstrumentStudio icon to edit the IO Configuration file in InstrumentStudio. In InstrumentStudio, you can view the asymmetric limits in the device's channel configuration panel.
| |||||
| 741943 Return | Relinking a device in the SMU/Power Supply panel sometimes doesn't work after renaming the device while the panel is closed. This error can happen in projects where the layout of the panel was changed after its initial creation. The panel will remain in a disconnected state even after you attempt to relink the renamed device. In sweep modes, you may also see an error that says "A channel used in the task was not found." Workaround: Use one of the following options to work around this issue:
| |||||
| 739985 Return | A TestStand sequence using an IO Configuration exported from InstrumentStudio will error if the LabVIEW Adapter is configured to "auto detect the LabVIEW version using VI version" and the VIs used in the sequence are saved in a version other than the earliest installed supported version. In TestStand, if you are using the LabVIEW Adapter with a "Create Session and Apply Configuration" step with an IO Configuration exported from InstrumentStudio and the LabVIEW Adapter is configured to "auto detect the LabVIEW version using VI version," running the sequence will produce an error on any Action steps that use the session if the VI for that Action step is saved in a version of LabVIEW other than the earliest installed supported version. The LabVIEW Adaptor will choose the earliest installed supported runtime to use with the "Create Session and Apply Configuration" step when configured to auto detect the version. VISA: (Hex 0xBFFF000E) The given session or object reference is invalid. Error code: -1073807346; User-defined error code. Workaround: Select a specific version of the runtime engine by configuring the LabVIEW Adapter using Configure>>Adapters... in TestStand. Alternately, install only one supported version of the LabVIEW runtime engine.
| |||||
| 738916 Return | In the SMU panel, if the aperture time is too large, error messages may report the incorrect units. For example, if you've set the aperture time in power line cycles (PLCs), the error message may say "1.23 seconds" when it should say "1.23 PLCs". Workaround: n/a
| |||||
| 722414 Return | CSV import does not support escaping numeric separator. You cannot use quotation marks to escape the numeric separator when importing CSV data. Workaround: Remove escape characters and thousands separators from data.
| |||||
| 722275 Return | Attempting to load files with a very large number of samples in arbitrary waveform mode may cause an out-of-memory error. In a waveform generator panel, attempting to load files with a very large number of samples for arbitrary waveform mode may cause an out-of-memory error. This amount will vary based on the amount of memory installed in your machine. Workaround: n/a
| |||||
| 722141 Return | Some features are not supported with the PXIe-5622 (25MHz DDC) oscilloscope. You may not be able to save a project with this device or reference this device in multiple tabs. You may receive the following error message: "Simulation does not support the selected model and board type." Workaround: You may use this instrument if you save projects with the instrument stopped, or if you do not need to save projects using this instrument.
| |||||
| 721976 Return | Event export is not supported on some waveform generators. Event export is not supported on the following waveform generators: 5441, 5442, 5402, 5406, 5450, and 5451. Workaround: n/a
| |||||
| 719810 Return | Some actions may disrupt exported events. If you have a user-created application that has an open session to an instrument, the session is configured to use a PXI_Trig line as a trigger source, you have used InstrumentStudio to configure an event to be exported to the same PXI_Trig line, and you perform an action in InstrumentStudio or MAX that causes InstrumentStudio to close and re-open sessions without notifying the user, exported events may be reset, disrupted, or fail to trigger. Workaround: n/a
| |||||
| 716488 Return | Configuring the second channel for a two-channel oscilloscope measurement recalculates the statistics for unrelated measurements. When the oscilloscope panel is stopped, changing the second channel for a two-channel measurement in the Add/Remove Measurements window causes the other enabled measurements to take a duplicate measurement snapshot and recalculate their statistics values. Workaround: After selecting the second channel for a two-channel measurement, reset the measurement statistics to ensure the statistics values are accurate.
| |||||
| 716261 Return | You cannot load interleaved arbitrary waveforms from a 5450 or 5451 waveform generator panel. Waveform files loaded for 5450 or 5451 waveform generators must provide data in a column major format (two columns for two channels). Workaround: n/a
| |||||
| 715849 Return | Using User-Defined mode on a 5450 or 5451 waveform generator requires both channels to be set to the same mode. Using User-Defined mode on a 5450 or 5451 waveform generator requires both channels to be set to the same mode. Workaround: n/a
| |||||
| 695052 Return | Changing debug configuration for a USB device after removing it from the system may cause bad behavior. Removing a USB device from the system after opening the Configure Debug Session window may cause a crash or hang in InstrumentStudio. Workaround: n/a
| |||||
| 694863 Return | With certain devices, trigger coupling for external triggers is incorrectly missing the AC value. It is still possible to monitor a session with AC-coupled external triggering. InstrumentStudio will return the correct value. Workaround: n/a
| |||||
| 694457 Return | Enabling probe compensation on a digitizer that does not support it results in an error loop. If you enable probe compensation on a digitizer that does not support probe compensation, InstrumentStudio returns an error until you disable probe compensation or revert to a default setup. Workaround: n/a
| |||||
| 694150 Return | Moving cursor positions by dragging the cursor lines clears persistent waveforms on the graph. If you move cursor positions on a graph while you have the Persistence Mode set to "Infinite", the persistent waveforms are cleared from the graph. Workaround: n/a
| |||||
| 693838 Return | Devices named with non-English characters cannot be used in InstrumentStudio. If you attempt to use a device with non-English characters in its name, InstrumentStudio either does not display the device in the Edit Layout window or returns an error when you attempt to create a panel using the device. Workaround: n/a
| |||||
| 693733 Return | Attempting to export a configuration to a folder with non-ASCII characters causes an error and does not export configuration files. If you use Export Configuration to export a device configuration to a folder named with non-ASCII characters, InstrumentStudio returns an error and does not export the device configuration files. Workaround: Export device configurations to folders with only standard ASCII characters.
| |||||
| 693731 Return | Device names with certain characters cause InstrumentStudio to crash. If a device used by InstrumentStudio has certain characters in the device name, InstrumentStudio crashes when you try to use that device. Characters that cause the error include Japanese characters on an English OS and non-ASCII characters on a Japanese OS. Workaround: n/a
| |||||
| 693532 Return | Japanese OS: When using Export Configuration on a device or .SFP file whose filename has Japanese characters, subsequent exports overwrite the original export instead of creating a new file. If a previous export of a device configuration exists and you use Export Configuration to create a new device configuration export, the default behavior is to create a new configuration file that appends a number to the configuration file title. For example, if you had a configuration file called My Configuration.sfp, and you select Export Configuration on the same device, InstrumentStudio will create a device configuration file called "MyConfiguration1.sfp" and keep the original export as well as the new export. When running InstrumentStudio in a Japanese OS, this behavior changes if your device name or configuration file uses Japanese characters. In this case, InstrumentStudio will replace the existing configuration file with a new one without changing the name. Workaround: n/a
| |||||
| 693529 Return | Non-ASCII characters in file names do not export correctly when using Export Configuration. If you use Export Configuration on a device or .SFP file that includes non-ASCII characters in its name, the non-ASCII characters will be replaced by the ? character. Workaround: Rename the .SFP file or device to remove non-ASCII characters.
| |||||
| 692941 Return | In the oscilloscope panel, any waveform that is rendered as points while persistence is enabled may disappear when time per division is changed. Turn off persistence to prevent the points from disappearing. Workaround: n/a
| |||||
| 692466 Return | When using multiple DMMs in InstrumentStudio, setting the Digits of Resolution to 6.5 or higher causes a slow measurement rate in the other instruments in the layout. If you launch an InstrumentStudio layout with digital multimeters and set one of the DMM's digits of resolution to 6.5 or above, both devices will take slower measurements than they are configured to take. Workaround: n/a
| |||||
| 692321 Return | Export Configuration doesn't generate configuration files for SMU devices if debugging is disabled and the SMU is running in an external session. If you create a layout with an SMU device, disable debugging for the SMU, begin an external session with the SMU, and then select Export Configuration from the instrument header menu, the SMU configuration will not be exported. Workaround: n/a
| |||||
| 692303 Return | Devices are duplicated when putting the chassis to sleep after selecting Auto-Create Layout. If you create an Auto Layout then put the chassis to sleep while InstrumentStudio is running, InstrumentStudio creates duplicate instances of each device when you wake the chassis up from sleep. Workaround: n/a
| |||||
| 691516 Return | Devices go missing after waking the host from sleep when InstrumentStudio is running. If you put the host into sleep mode while InstrumentStudio is running, devices sometimes go missing in InstrumentStudio when you wake the computer. Workaround: n/a
| |||||
| 691347 Return | InstrumentStudio returns errors when launching automatic layouts from different users. If you create and run an InstrumentStudio automatic layout, log out and log in as a different, non-administrative user, then create and run a new InstrumentStudio automatic layout, the new automatic layout returns errors for all panels. Workaround: n/a
| |||||
| 690758 Return | FGEN channels fall out of phase with each other if the channel frequencies are changed during operation. If you generate multiple FGEN channels at the same time and change the channel frequencies at different times during device operation, the FGEN channels will fall out of phase. Workaround: Restart generation.
| |||||
| 681717 Return | In debug mode, Digital Multimeter (DMM) panels can return the cached AutoRange value instead of the current AutoRange value from the driver. When controlling a DMM device being used by an external application, the AutoRange property always displays the "OFF" status, regardless of the AutoRange status in the external application. Workaround: n/a
| |||||
| 680900 Return | When measuring an FGEN-generated frequency from a Digital Multimeter (DMM) panel, the DMM panel returns an under range message regardless of whether the measurement is under or over range. Workaround: n/a
| |||||
| 680205 Return | Oscilloscope waveforms update slowly when monitoring an auto-triggering session. If you are using InstrumentStudio to monitor an oscilloscope in an external application that uses auto-triggering, the oscilloscope waveform updates slowly in InstrumentStudio. Configuration modifications and measurements do not appear in the InstrumentStudio panel for a longer amount of time than they should. InstrumentStudio also responds slowly to UI commands in this state. Workaround: n/a
| |||||
| 679795 Return | Cursors used in an oscilloscope panel are reset when the project is saved and reloaded or if the panel is launched in a new tab. When using an oscilloscope in InstrumentStudio, the oscilloscope panel's cursor locations reset to the 1 and -1 graticule divisions when you reload the project or launch the oscilloscope panel in a new tab. Workaround: n/a
| |||||
| 678489 Return | PXI-5421/5422 devices return an erroneous sample rate configuration error when transitioning from a standard waveform function to a user-defined standard waveform. When using a PXI-6521 or PXI-6522 device, if a user changes from a standard waveform function (i.e. Sine, Square, etc.) operating with a lower frequency of less than 150kHz to a user-defined standard waveform, InstrumentStudio returns an error stating that the value set for Sample Rate is incorrect. This error is erroneous; transitioning from a standard waveform to a user-defined standard waveform does not configure the Sample Rate. Workaround: n/a
| |||||
| 624387 Return | Putting the host machine to sleep causes all Source Measure Unit (SMU) channels to be removed from the InstrumentStudio layout. This issue occurs when a chassis is connected with a MXI cable. This issue does not occur on controllers, since they do not support sleep. Workaround: n/a
|
Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.