This document contains the InstrumentStudio known issues that were discovered before and since the release of InstrumentStudio 2021 Q4. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 388174 | 692303 |
Devices Are Duplicated When Putting the Chassis to Sleep After Selecting Auto-Create LayoutIf 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: There is currently no known workaround for this issue. |
Reported Version: InstrumentStudio 2018 Resolved Version: N/A Added: Jun 3, 2018 |
| 388162 | 691516 |
Devices Go Missing After Waking the Host From Sleep When InstrumentStudio Is RunningIf you put the host into sleep mode while InstrumentStudio is running, devices sometimes go missing in InstrumentStudio when you wake the computer. Workaround: There is currently no known workaround for this issue. |
Reported Version: InstrumentStudio 2018 Resolved Version: N/A Added: May 27, 2018 |
| 1176443 |
Installing a Previous Version of InstrumentStudio Causes All Project Files to Open With the Most Recently Installed VersionProject files will open with the most recently installed version of InstrumentStudio. For example, if you install InstrumentStudio 2020, create and save projects in that version, and then install InstrumentStudio 2019, the project files created in InstrumentStudio 2020 will open by default with InstrumentStudio 2019. InstrumentStudio projects and documents are not backward-compatible, so the project will give an error saying that it failed to load.
Workaround: Change the Windows file association for .instudioproj files to the latest version or repair the InstrumentStudio installation with the desired default project version.
|
Reported Version: InstrumentStudio 2018 SP2 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1154387 |
Digital Trigger Sources Do Not Update After Renaming a Device in MAXIf you rename an Oscilloscope device in MAX, the new name will not automatically appear in the list of digital trigger sources in the InstrumentStudio Oscilloscope panel. After renaming one or more devices, errors occur when attempting to use those digital trigger sources.
Workaround: Select a different trigger type in the InstrumentStudio Oscilloscope panel and then select Digital triggering again. This will force the list of trigger sources to refresh.
|
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1109913 |
Capture Screenshot Does Not Capture Whole Panel When DPI Scaling Is Greater Than 100%If your PC display settings are configured to use a DPI scaling greater than 100%, the capture screenshot and capture data (when configured to include a screenshot) functions in InstrumentStudio will not capture an image of the whole panel.
Workaround: In the Windows Display settings, change the scaling to 100% before using InstrumentStudio's Capture Screenshot function or including the screenshot with the Capture Data function. You can also use built-in Windows or third-party tools to capture a screenshot instead.
|
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1167363 |
InstrumentStudio Crashes on Launch When an Administrator Leaves InstrumentStudio Open and Another User Logs in and Tries to Start ItIf InstrumentStudio is running on an administrator account, and you log out and log in with a different, non-administrator user account, InstrumentStudio crashes on launch.
Workaround: There is currently no known workaround for this issue. |
Reported Version: InstrumentStudio 2019 Resolved Version: InstrumentStudio 2022 Q1 Added: Oct 22, 2021 |
|
| 992871 |
Pins Using Multiplexed Connections Are Not Shown Under the Correct Site in InstrumentStudioInstrumentStudio does not currently support multiplexed connections in pin maps. If the site filter is set to a specific site, pins under that site will not appear in the panel if they are mapped in the pin map using multiplexed connections. The channels using multiplexed connections will appear under Unmapped channels if the Site filter is set to All sites, but will not display the pin names from the pin map. Workaround: There is currently no known workaround for this issue.
|
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1067929 |
SMU Waveform Mode May Not Graph Data for All Selected Channels With High Capture TimesWhen multiple channels are enabled in SMU Waveform mode and selected for display on the graph, InstrumentStudio may fail to acquire waveform data for all of the selected channels when you increase the capture time, depending on the channel count and capture time used.
Workaround: Reduce the capture time or limit the number of channels you are acquiring data from
|
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1197451 |
Oscilloscopes Fails to Auto-Monitor When the Devices in the Panel Are Different From the Devices in the External SessionIf you are using an Oscilloscope panel with multiple oscilloscopes, and then run test code which has separate sessions for one or more of the same devices, then InstrumentStudio will get stuck in a running/stopped loop and will be unable to monitor or acquire data from any of the devices. Similarly, if you are using a single oscilloscope in a standalone panel in InstrumentStudio and then run test code that uses channel expansion to open a single session to more than one device, including the one used in InstrumentStudio, then the panel will be unable to monitor the session and will enter an unusable state.
Workaround: To monitor the external session, use Manual layout to create a panel containing the same devices that are used in the external session. |
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1379795 |
FGEN Channels will stop outputting when entering Control mode in a debug panelIf
you have an FGEN session running and open a panel in debug mode for monitoring,
going into control mode will stop the FGEN output, and will not change
even if you go back into monitor mode.
Workaround: There is currently no known workaround for this issue. |
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
|
| 1371988 |
SMU/Power "Export To TestStand" Measure When property in exported IO Configuration is different before and after running the panelThe IO Configuration generated when clicking on "Export to TestStand" in an SMU/Power Supply panel will be different before and after running the panel. Specifically, the "Measure When" (NIDCPOWER_ATTR_MEASURE_WHEN) property will have different values:
Workaround: There is currently no known workaround for this issue. |
Reported Version: InstrumentStudio 2019 Resolved Version: N/A Added: Oct 22, 2021 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country