NI-SWITCH 20.5 Known Issues

Panoramica

This document contains the NI-SWITCH known issues that were discovered before and since the release of NI-SWITCH 20.5. 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

393016 284305

SCXI-1127 (Rev D and earlier) continuously drives the TTL1 trigger line on the SCXI backplane

Continuously driving the TTL1 trigger line on the SCXI backplane does not allow bus sharing of TTL1 with other SCXI modules. NI-SWITCH returns an error if an SCXI-1127 is in the chassis and if TTL1 is being used for scanning. If using the NI-DAQmx driver for your SCXI system, you get a resource reservation error if you try to perform a switching or signal conditioning operation that requires use of TTL1.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-Switch 1.6

Resolved Version:

N/A

Added:

Feb 7, 2011

393021 284308

There are known DLL collision issues with the Microsoft Visual Basic debugger and a National Instruments device driver using Traditional NI-DAQ (Legacy)

A support DLL used by NI-SWITCH fails to load if Visual Basic has already loaded another DLL into the same address space.

Workaround:

To change the default address that is used to load the driver DLL, create the following registry key: \\HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\NI-PAL\CurrentVersion\palConfig\Memory\ sharedFixedAddress where the value is a DWORD (0x44000000 generally works). For the change to take effect, you must close and restart all applications after adding the registry key.

Reported Version:

NI-Switch 2.5

Resolved Version:

N/A

Added:

Feb 7, 2011

1024555

No device names appear when initializing a session with NI-SWITCH on LinuxRT

When selecting a resource name with niSwitch Initialize With Topology.vi in LabVIEW on an NI Linux Real-Time target, the drop-down menu for selecting resources appears empty and you cannot select a device that is in your system.


Workaround:

Manually enter the resource name for the device you want to use. Use MAX or NI System Configuration software to retrieve the resource name for any devices in the system.

Reported Version:

NI-SWITCH 20.5

Resolved Version:

N/A

Added:

Sep 7, 2020

1056439

Test Panels in MAX do not work for NI-SWITCH devices on RTOS target systems

For NI-SWITCH devices on a NI Linux Real-Time or PharLap target system, the Test Panel button in MAX opens Instrument Studio instead of a test panel.

Workaround:

Use an example VI or a similar VI and deploy it to the target to exercise functionality instead of a test panel.

Reported Version:

NI-SWITCH 20.5

Resolved Version:

N/A

Added:

Sep 7, 2020

1113818

Errors reported in English instead of Japanese on LinuxRT for NI-SWITCH driver

On a Linux Real-Time target with the language set to Japanese, the NI-SWITCH driver returns errors in English instead of Japanese.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-SWITCH 20.5

Resolved Version:

N/A

Added:

Sep 7, 2020

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

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

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).