NI-SLSC 20.0 Known Issues

Überblick

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

168644 734737

Applications built in NI-SLSC 17.5 or earlier including NI-SLSC Initialize Session will crash when used with NI-SLSC 18.0 or higher

When attempting to run a built application that was created using NI-SLSC 17.5 or earlier after upgrading the driver to NI-SLSC 18.0 or newer, the application will crash.

Workaround:

Rebuild the application using NI-SLSC 18.0 or newer.

Reported Version:

NI-SLSC 18.0

Resolved Version:

N/A

Added:

May 14, 2020

169975 600095

NVMEM Write can have pending changes for same NVMEM address in both raw and named area.

Conflicting pending changes for an NVMEM address may exist if the NVMEM address is written both through a named area and the raw area. The behavior when committing these changes is undefined.

Workaround:

When possible, all NVMEM changes should be done through double-buffered named areas. When accessing the raw area, no changes should be made to named areas before committing the raw changes.

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

169999 619452

LabVIEW exit may be delayed if chassis have become inaccessible.

The NI-SLSC API automatically retrieves information about chassis in the configuration file, and chassis detected on the local network. If chassis become inaccessible before this operation completes, exiting LabVIEW will block waiting for the update to time out.

Workaround:

The LabVIEW process may be killed to abort the blocking operations. The effects of this may be reduced by removing inaccessible chassis from the configuration file. Cached information about inaccessible chassis may be cleared from niMdnsResponder by rebooting the PC.

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

169955 607330

SLSC API calls cannot be aborted during the mDNS browse timeout

If the abort button in a VI is pressed during an mDNS Browse Timeout, it is going to wait for the timeout to expire before the abort happens.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

170001 616229

Chassis time not preserved after reset or power cycle

The chassis will not preserve an updated time if the reset button is pressed or if the chassis is power cycled prior to doing a restart through System Configuration API or the web interface.

Workaround:

Use the Get and Set Chassis Time.vi example installed with the driver at \examples\SLSC to update the time. This example includes the reset to ensure time is preserved.

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

169958 587733

Property range checking in API does not use implied min/max based on bitfield type and size.

The SLSC API detects property range errors during the Set Property call if the vendor has supplied a min and/or max value for the property. If no min/max is supplied, and the supplied value cannot fit in the hardware bitfield, the Set Property call will not report an error. The error will instead be reported when the properties are committed, either through Commit Properties or Execute Command.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

170004 617680

SLSC cannot resolve mDNS hostnames on an IPv6-only network.

NI-SLSC 1.0 restricts mDNS hostname resolution to IPv4 only, preventing access to .local hostnames on IPv6-only networks.

Workaround:

If mDNS hostname resolution is required, enable IPv4 on the network. If the network is IPv6 only, the chassis may be added using the IP address or a fully-qualified domain name.

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

170006 640739

If changing the network link speed for the SLSC-12001 using the web interface, it does not remain after reboot.

When changing the network link speed through the web interface, it is applied immediately (even though you are prompted to reboot), but is not applied correctly on reboot. The chassis always auto-negotiates the highest possible speed after reboot.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-SLSC 17.0

Resolved Version:

N/A

Added:

May 4, 2017

444479 636334

Initialize Session with Devices may return an error prior to the specified timeout when attempting to connect to a chassis before the chassis ready LED is green.

The SLSC chassis is visible on the network for several seconds before it is ready to receive inbound SLSC connections. During this time, connection attempts will be rejected by the chassis. The SLSC API treats this as an error, and aborts the connection without retrying until the timeout expires.

Workaround:

Wait to initialize connections until the chassis ready LED is green, or initialize the session in a loop until it succeeds.

Reported Version:

NI-SLSC 17.0

Resolved Version:

N/A

Added:

May 4, 2017

444285 603675

Users cannot rename device to a new name differing only by case.

If trying to rename a device to change case only (e.g. "abc123" to "ABC123"), the rename will not occur.

Workaround:

If wanting to change device name by case, perform 2 renames using a temporary name for the first one:

1. Rename to "temp"
2. Rename to "New case"

Reported Version:

NI-SLSC 1.0

Resolved Version:

N/A

Added:

Dec 9, 2016

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).