NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in this document. If you have feedback on this specific document, please contact NI on this NI Developer Zone post.
The following items are known issues in LabVIEW Wireless Sensor Network Module Pioneer sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Building and Distributing LabVIEW Applications | ||||||
| 174173 Return | LabVIEW WSN projects cannot be built and deployed from network locations UNC paths are not supported when building and deploying the LabVIEW WSN target VI. UNC paths point to network locations and usually start with "\\" instead of a local drive letter like "C:". Workaround: Map the network location to a local drive.
| |||||
| Documentation | ||||||
| 170692 Return | Error message from the LabVIEW WSN Host API is not very helpful When the WSN Open Gateway VI fails to connect to a NI WSN-9791 Gateway device it displays the following error message to the user: Error -35024 occurred at Invoke Node in WSN Open Gateway.vi->Simple Monitor.vi Possible reason(s): LabVIEW WSN: Connection disconnected by peer. The message implies that the Gateway could not be found or could not be connected to. Workaround: N/A
| |||||
| Functions, VIs, and Express VIs | ||||||
| 168370 Return | Get Date/Time function returns incorrect value after the Node is reset WSN nodes do not have real time clocks. They can only synchronize their clocks with the WSN gateway. Until the node connects to the gateway, the Get Date/Time function will return its default output, January 1, 1904. Workaround: N/A
| |||||
| 163360 Return | Scan From String function does not update its error out output when used in the LabVIEW WSN Target VI When used on the LabVIEW WSN target VI, the error out output on the Scan From String function does not indicate if the operation was unsuccessful. The output works as expected. Workaround: N/A
| |||||
| 177306 Return | The WSN Host API Palette shows sub-palettes for unrelated toolkits/modules For a VI in the My Computer context, the WSN Host API palette shows sub-palettes for all installed toolkits and modules. Workaround: N/A
| |||||
| 156537 Return | Link Quality IO Variable and the WSN Get Node Info VI return inconsistent results The Link Quality IO Node returns link quality as a percentage from 0 - 100 while the WSN Get Node Info VI returns link quality as an enumeration with values: No Signal, Poor, Fair, Good, Excellent. Workaround: N/A
| |||||
| 160845 Return | Wiring an input of type double to the data in input of Write to Sector Single VI causes the build to fail The Write to Sector Single VI can only accept an input of type single on its data input. Wiring a double to data does not break the Run arrow but the VI cannot be built or deployed. Workaround: N/A
| |||||
| 162179 Return | Resizing the RadioMessages.xnode breaks existing wires Resizing the RadioMessage.xnode breaks existing wires and removes previously connected terminals. Workaround: N/A
| |||||
| 163359 Return | Using the %x format specifier with the Format to String function truncates 64-bit unsigned integers to 32-bit unsigned integers Using the "%x" format specifier yields different results on a LabVIEW WSN target VI when compared to the results on a VI running on Windows. Workaround: N/A
| |||||
| 169915 Return | The Number To Exponential String function leaves the result in floating point format The Number To Exponential String function should format the number to scientific notation but it keaves the reault in the floating point format. Workaround: N/A
| |||||
| 174830 Return | In the RadioMessages.xnode, changing the terminal from Send User Message to Send Debug Message breaks the existing wire The Send User Message and Send Debug Message terminals of the RadioMessages.xnode both accept a string input. However when the Send User Message is changed to Send Debug Message, the input wire breaks. Workaround: N/A
| |||||
| LabVIEW Project | ||||||
| 142865 Return | Renaming an IO Variable does not change the name of the corresponding Radio Message Node Every IO Variable has a corresponding Radio Message Node that lets the user update the IO Variable from the LabVIEW WSN target VI. Renaming an IO Variable through the project does not change the name of the Radio Message Node associated with it. The renamed IO Variable however maintains its binding to the Radio Message Node. Workaround: N/A
| |||||
| 175726 Return | Deployment of LabVIEW WSN Target VI cannot be cancelled through the LabVIEW Project Deployment of the LabVIEW WSN target VI cannot be cancelled or aborted if it fails midway. Workaround: The deployment can be cancelled in MAX by selecting the right node and clicking the Cancel button.
| |||||
| 156486 Return | Closing the LabVIEW Project does not close the Node Monitor window Workaround: N/A
| |||||
| 177272 Return | Closing a LabVIEW WSN project does not close the LabVIEW WSN Target VI N/A Workaround: N/A
| |||||
| Performance | ||||||
| 141771 Return | Changes to sample interval are not applied instantaneously When the Sample Interval is changed in any state other than the Sample state, the changes are applied after the next scheduled Sample state is executed. Changes to Sample Interval are only applied in the Sample state so if changes are made in other states, at least one Sample case needs to run before the changes are applied. Workaround: N/A
| |||||
| 148709 Return | Maximum sample rate of the NI WSN-3202 Voltage Node is only 20 S/sec using the LabVIEW WSN Target VI Workaround: N/A
| |||||
| Shared Variables | ||||||
| 142865 Return | Renaming an IO Variable does not change the name of the corresponding Radio Message Node Every IO Variable has a corresponding Radio Message Node that lets the user update the IO Variable from the LabVIEW WSN Target VI. Renaming an IO Variable through the project does not change the name of the Radio Message Node associated with it. The renamed IO Variable however maintains its binding to the Radio Message Node. Workaround: N/A
| |||||
Document last updated on 7/29/2009