The following items are notable issues fixed between the release of NI-SWITCH 2023 Q4 and NI-SWITCH 2024 Q4, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI-SWITCH.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1024555 |
No device names appear when initializing a session with NI-SWITCH on LinuxRTWhen selecting a resource name with niSwitch Initialize With Topology.vi in LabVIEW with a LabVIEW version prior to 21.0 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: NI-SWITCH 21.3 Added: Sep 7, 2020 |
|
1113818 |
Errors reported in English instead of Japanese on LinuxRT for NI-SWITCH driverOn 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: NI-SWITCH 21.3 Added: Sep 7, 2020 |
|
1504995 |
NI Switch Health Center shows wrong relay countsWorkaround:
|
Reported Version: NI-SWITCH 19.5 Resolved Version: NI-SWITCH 21.3 Added: Oct 20, 2021 |
|
1024555 |
No device names appear when initializing a session with NI-SWITCH on Linux DesktopWhen selecting a resource name with niSwitch Initialize With Topology.vi in LabVIEW on Linux Desktop, 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 the Hardware Configuration Utility or NI System Configuration software to retrieve the resource name for any devices in the system.
|
Reported Version: NI-SWITCH 20.1 Resolved Version: NI-SWITCH 21.3 Added: Apr 19, 2022 |
|
1860393 |
NI-SWITCH Fails to Install on Linux Kernel 5.13 or Later with Fatal ErrorWhen installing certain NI drivers onto a Linux system using kernel version 5.13 or later, the installation fails with an error about not finding all the dependencies it needs such as: /var/lib/dkms/nikal/21.5.0f129/build/nikal.c:32:16: fatal error: config/modversions.h: No such file or directory Workaround: Reattempt the installation after adding modversions.h to the kernel headers for your current system kernel. For example: sudo touch /usr/src/linux-headers-$(uname -r)/include/config/modversions.h |
Reported Version: NI-SWITCH 21.3 Resolved Version: NI-SWITCH 2022 Q3 Added: May 10, 2022 |
|
2209410 |
NI-SWITCH Windows symbols are exported without ordinalsThe exported symbols of the niswitch.lib library are exported only by name, not by ordinal. As a result, any libraries built against an older version's import library (that use /delayload) use the wrong symbols because the ordinals have now changed.
Workaround: Rebuild any impacted library with the version of NI-SWITCH being used or load symbols by name instead of ordinal.
|
Reported Version: NI-SWITCH 2022 Q4 Resolved Version: NI-SWITCH 2023 Q1 Added: N/A |
|
2857306 |
Opening an NI Switch Executive session crashes the application when not using LabVIEWOpening a NI Switch
Executive session to an NI-SWITCH instrument (physical or simulated) causes an
exception with the description "labviewv.lib was not called from a LabVIEW process",
unless calling from the LabVIEW environment or with the LabVIEW Runtime
Engine loaded into the process. Workaround: Load the LabVIEW Runtime Engine into the process prior to opening an NI Switch Executive session. |
Reported Version: NI-SWITCH 2023 Q3 | Switch Executive 2023 Q4 Resolved Version: NI-SWITCH 2024 Q4 Patch 1 Added: Oct 4, 2024 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.