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:
The following document displays the Switch,Load & Signal Conditioning (SLSC) Module Development issues by date.
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.
The following items are known issues in SLSC sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 610897 Return | SLSC examples do not show up in Example Finder Workaround: Locate SLSC examples in \examples\SLSC
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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"
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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. Error Reporting was added in NI-SLSC 19.0.
| |||||
| 734737 Return | 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.
|
Document last updated on 5/30/2018