| ID | Known Issue |
|---|
218656
| An error can occur after disconnecting and reconnecting NI USB-5681.
Occasionally when you disconnect the power meter and reconnect it to the same port the Initialize with Options VI fails with error - 1073807298.
Workaround: Choose from the following workarounds:
- Connect the power meter to a different port.
- Close LabVIEW and the Soft Front Panel (any applications using the power meter), disconnect the power meter, pause, and reconnect the device.
| Reported Version: 1.1 | | Resolved Version: N/A | | Added: 09/28/2010 |
|
238457
| Power meters do not appear in NI Measurement & Automation Explorer (MAX) after installing the NI-568x driver.
NI-568x 1.1 and later added support for displaying the USB power meters in MAX. However, if a power meter was connected to the system during NI-568x driver installation, the power meter does not appear in MAX.
Workaround: To display the power meter in MAX, disconnect and reconnect the power meter after a pause.
| Reported Version: 1.1 | | Resolved Version: N/A | | Added: 09/28/2010 |
|
240557
| The Scope mode acquisition example returns an error when you use a small capture time.
NI-568x returns error 1074118649 when you enable a gate, but gate parameters are not within the limits of the capture time. This issue is not limited to the example VI. For NI-568x 1.2, an error occurs only when the capture time is set to less than 1.37ms.
Workaround: When you unable a gate, set gate parameters as follows:
- Gate start must be positive.
- Gate end must be greater than gate start.
- Gate start and gate end must both be less than the capture time.
| Reported Version: 1.1 | | Resolved Version: N/A | | Added: 09/28/2010 |
|
258340
| Closing a session to an NI 568x device takes a long time if the device is still waiting on a trigger.
If you attempt to close a session to the NI 568x device while the device is waiting to receive a trigger, the call to close can take up to 2 minutes to execute.
Workaround: Send the trigger before closing the session.
| Reported Version: 1.1 | | Resolved Version: N/A | | Added: 11/16/2010 |
|
412196
| Disconnecting an NI 5681 device while a measurement is in progress causes unexpected behavior.
When you disconnect the NI 5681 while it is executing a measurement operation, such as averaging, subsequent calls to the Is Measurement Complete VI/function returns measurement status unknown without an error. If Is Measurement Complete is called within a loop, the code could hang because it is waiting for measurement complete or an error to be returned. In LabVIEW, if you abort the VI after encountering this issue, initialization will take a long time to run and returns error -1073807345, even after you reconnect the device.
Workaround: Abort the executing code and reconnect the device to a different USB port.
| Reported Version: 1.2 | | Resolved Version: N/A | | Added: 06/10/2013 |
|
412319
| In Windows 8, an error occurs when you attempt to initialize the NI 568x device with high memory addressing enabled.
In Windows 8, the following error occurs when you attempt to initialize the NI 568x device with high memory addressing enabled: ni568x Initialize With Options.vi ni568x Initialize With Options.vi Driver Status: (Hex 0xBFFA0060) COM4
Workaround: Disable high memory addressing in Windows 8 systems.
| Reported Version: 1.2 | | Resolved Version: N/A | | Added: 06/10/2013 |
|
413281
| When the computer wakes from standby mode, the NI-568x Soft Front Panel (SFP) crashes.
If you put the computer on standby with the NI-568x SFP open, when you wake the computer, the SFP crashes.
Workaround: Close the SFP and any other application that has an open session to a power meter before going into standby mode.
| Reported Version: 1.2 | | Resolved Version: N/A | | Added: 06/17/2013 |
|
411345
| When you reconnect the power meter with the NI-568x SFP, the device cannot be connected to
When you disconnect and then reconnect the power meter with the NI-568x SFP before the SFP can release the handle (before "No Sensor" is displayed), the device enters a state in which it cannot be connected either through the SFP or any other development environment. When you attempt to open a session to the device, the system returns an error of BFFF0011 (-1073807343).
Workaround: The two workarounds for this issue are as follows: 1) If the device was running at the time of disconnection, wait until "No Sensor" is shown in the SFP when you unplug the device from the system. 2) Unplug and then reconnect the device to the system while the SFP is running. This causes the SFP to reconnect properly to the device and to continue with normal operation.
| Reported Version: 1.2 | | Resolved Version: N/A | | Added: 09/17/2013 |
|