SLSC Known Issues

Publish Date: Nov 27, 2018 | 0 Ratings | 0.00 out of 5 | Print

Overview

This document contains the Switch,Load & Signal Conditioning (SLSC) Module Development known issues that were discovered before and since the release of SLSC. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Each Issue appears as a row in the table and includes these fields:

  • Issue ID - the number at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
  • Legacy ID (optional) -  If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
  • Issue Title: in italics - it describes the issue in one sentence or less
  • Problem Description - a few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
  • Workaround - possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
  • Reported Version - the earliest version of NI-SLSC the issue was reported in. If you discover the issue appears in an earlier version of NI-SLSC than is reported in this field, you can report that to NI (contact information below) to have the field updated.
  • Resolved Version - version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
  • Date Added - the date the issue was added to the document (not necessarily the reported date)

Table of Contents

  1. Document Organization:
  2. Contacting NI

1. Document Organization:

The following document displays the Switch,Load & Signal Conditioning (SLSC) Module Development issues by date.

Back to Top

2. Contacting NI

Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). 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 consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

Known Issues by Date

The following items are known issues in SLSC sorted by Date.

610897 SLSC examples do not show up in Example Finder
587733 Property range checking in API does not use implied min/max based on bitfield type and size.
599292 SLSC API does not update cached module information when the module is reset.
600095 NVMEM Write can have pending changes for same NVMEM address in both raw and named area.
603675 Users cannot rename device to a new name differing only by case.
605416 The SLSC API does not expose firmware and hardware versions for devices.
607330 SLSC API calls cannot be aborted during the mDNS browse timeout
614832 On Phar Lap ETS, communication between SLSC and mDNSResponder may hang.
614992 Get NVMEM Bytes example sometimes takes several seconds on Phar Lap ETS
616229 Chassis time not preserved after reset or power cycle
617680 SLSC cannot resolve mDNS hostnames on an IPv6-only network.
619452 LabVIEW exit may be delayed if chassis have become inaccessible.
619948 SLSC API does not regenerate deleted configuration file.
636334 Initialize Session with Devices may return an error prior to the specified timeout.
640739 Changes to the network link speed for the SLSC-12001 are not persistent after boot.
695448 NI-SLSC Initialize Session prevents execution when opening a large number of sessions on Pharlap RT



ID Known Issue
610897

Return
SLSC examples do not show up in Example Finder

Workaround: Locate SLSC examples in \examples\SLSC

Reported Version: 1.0    Resolved Version: 17.0    Added: 12/09/2016
587733

Return
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: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 12/10/2016
599292

Return
SLSC API does not update cached module information when the module is reset.
The SLSC API caches module information when module is reserved, which typically happens when a session is initialized. When resetting a module, this cached information is not updated. If the module NVMEM was changed before the reset, the changes will not be visible to the session immediately.

Workaround: Close and re-initialize the SLSC session to cache updated information about the module.

Reported Version: 1.0    Resolved Version: 17.0    Added: 12/10/2016
600095

Return
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: 1.0    Resolved Version: N/A    Added: 12/10/2016
603675

Return
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: 1.0    Resolved Version: N/A    Added: 12/10/2016
605416

Return
The SLSC API does not expose firmware and hardware versions for devices.
The SLSC API does not expose firmware and hardware versions for devices.

Workaround: The SLSC chassis firmware version may be retrieved through the NI System Configuration API or web interface. In driver versions 17.0 or later, information about modules is accessible through the SLSC API session property node.

Reported Version: 1.0    Resolved Version: 17.0    Added: 12/10/2016
607330

Return
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: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 12/10/2016
614832

Return
On Phar Lap ETS, communication between SLSC and mDNSResponder may hang.
Repeatedly connecting to an SLSC Chassis thousands of times in rapid succession using a .local hostname on Phar Lap may temporarily exhaust the available TCP ports. This may cause NI-SLSC API calls to hang when interacting with mDNSResponder.

Workaround: Add Chassis to the target configuration file using either IP Address or fully qualified network name (not mDNS .local name).
When using .local names, avoid repeatedly opening/closing short-lived connections.

Reported Version: 1.0    Resolved Version: N/A    Added: 12/10/2016
614992

Return
Get NVMEM Bytes example sometimes takes several seconds on Phar Lap ETS
On Phar Lap ETS, if you use Get NVMEM Bytes to read the entire "raw" area, the call usually takes around 200ms but sometimes can spike above 10s.

Workaround: New examples introduced in 17.0

Reported Version: 1.0    Resolved Version: 17.0    Added: 12/10/2016
616229

Return
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: 1.0    Resolved Version: N/A    Added: 12/10/2016
617680

Return
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: 1.0    Resolved Version: N/A    Added: 12/10/2016
619452

Return
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: 1.0    Resolved Version: N/A    Added: 12/10/2016
619948

Return
SLSC API does not regenerate deleted configuration file.
If the configuration file (C:\ProgramData\National Instruments\nislsc\nislsc.json) is deleted, the API will return errors when any communication with a device is attempted. Error -250825 is the most common error received.

Workaround (prior to 18.0): Create an empty configuration file at C:\ProgramData\National Instruments\nislsc\nislsc.json. The NI-SLSC API will regenerate the contents as needed.

Reported Version: 1.0    Resolved Version: 18.0    Added: 12/10/2016
636334

Return
Initialize Session with Devices may return an error prior to the specified timeout.
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: 17.0    Resolved Version: N/A    Added: 5/4/2017
640739

Return
Changes to the network link speed for the SLSC-12001 are not persistent after boot.
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: N/A

Reported Version: 17.0    Resolved Version: N/A    Added: 5/4/2017
695448

Return
NI-SLSC Initialize Session prevents execution when opening a large number of sessions on Pharlap RT.
When opening a large number of sessions, SLSC Initialize will block execution, and the application may become nonresponsive or hang, while waiting for the three required sockets for a session to become available, if the maximum default number of sockets is reached. On Pharlap, the maximum number of sockets by default is 256.

Workaround: Increase the maximum number of sockets on Pharlap by editing the ni-rt.ini file.  See KB for more details.

Reported Version: 1.0    Resolved Version: N/A    Added: 5/30/2018

Document last updated on 5/30/2018

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit