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 2010 Wireless Sensor Network Module Pioneer sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Analysis and Math | ||||||
| 162792 Return | WSN Nodes only support single precision numbers NI WSN nodes only support single precision numbers. However, LabVIEW does not prevent you from using double precision numbers in your Block Diagram. All such numbers are converted to single precision for actual computation. Workaround: N/A
| |||||
| 232868 Return | Use of Subnormal numbers can cause compiler errors In the LabVIEW Wireless Sensor Module, the range for a IEEE 32-bit float is (1.175 495e-38, 3.40 282 35e+38). This data type is represented as a Single in LabVIEW. Using values outside this range in your Block Diagram can cause compiler errors. Workaround: N/A
| |||||
| 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.
| |||||
| 178162 Return | Closing the Project Explorer does not close the WSN System Monitor Removing the LabVIEW WSN target from your Project Explorer or closing the Project Explorer itself does not close the WSN System Monitor. Workaround: N/A
| |||||
| 194405 Return | If the Gateway is disconnected from the network, the error says "unable to connect to the node" If the Gateway is disconnected from the network, LabVIEW will display an error that says "unable to connect to the node" even though the Gateway itself is unreachable. Workaround: N/A
| |||||
| 210116 Return | Clicking the Run button on an unsaved WSN VI might put your Build Specification in a bad state If you click the Run button on an unsaved WSN VI, LabVIEW prompts you to create a Build Specification. However, since you are using an unsaved VI, you cannot configure it as a startup VI. Workaround: Save your WSN VI before clicking the Run button.
| |||||
| 244163 Return | If you enqueue deployments for multiple nodes on a Gateway, one or more pending deployments might fail LabVIEW can only process one deployment per Gateway at a time. If you enqueue deployments for multiple nodes on a Gateway (3 or more), LabVIEW will start processing the first deployment while others are pending. Once the first deployment is complete, LabVIEW will process the second but fail all the remaining deployments. Workaround: Redeploy the remaining applications.
| |||||
| 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
| |||||
| Example Programs | ||||||
| 257449 Return | Example Finder lists non-existent examples under "Toolkits and Modules Not Installed" Example Finder continues to display non-existent examples under WSN in the "Toolkits and Modules Not Installed" section even if the LabVIEW 2010 Wireless Sensor Network Module is installed successfully. Installed examples are listed accurately under WSN in the "Toolkits and Modules" section. Workaround: Navigate to C:\Program Files\National Instruments\Shared\Example Finder\1.0\Products\LabVIEW\10.0\exbins\English\Platform and remove the "_lvembwsn.bin4" file.
| |||||
| Functions, VIs, and Express VIs | ||||||
| 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
| |||||
| 162179 Return | Resizing the RadioMessages.xnode breaks existing wires Resizing the RadioMessage.xnode breaks existing wires and removes previously connected terminals. 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
| |||||
| 236275 Return | Using the Number to Engineering String or Fract/Exp String to Number functions can cause your build to fail Using the Number to Engineering String or Fract/Exp String to Number functions in your WSN VI can cause a linker error for undefined symbol, strncasecmp. Workaround: N/A
| |||||
| 204567 Return | If you have VIs named device config.vi and radio message.vi in your Project, their contents might be dropped from the application User written VIs in the LabVIEW WSN project cannot have the same names as the Radio Message Node or the Config Node. This leads to the contents of your VIs to get dropped and cause build errors. Workaround: N/A
| |||||
| 241279 Return | Feedback nodes on WSN VIs return default data. Workaround: Use shift registers instead of feedback nodes.
| |||||
| 209601 Return | Input constants for WSN Config Nodes created in LabVIEW 2009 might appear faded in LabVIEW 2009 SP1 and later When WSN VIs created in LabVIEW 2009 or before are opened in LabVIEW 2009 SP1 or later, some dependencies could be missing, these missing constants will appear faded on the Block Diagram. Workaround: Delete missing (faded) constant and replace with a new constant.
| |||||
| 211423 Return | Sending User Messages in a loop might cause NI 9792 gateway to run out of memory If you send User Messages to your NI WSN node in a loop with a large number of iterations, your NI 9792 Programmable WSN Gateway might run out of memory. For details of the how this might happen, refer to KnowledgeBase ID 5F9GGI6V: http://digital.ni.com/public.nsf/websearch/A694C548592ACBCB862577D7007913A6?OpenDocument Workaround: Refer to linked KnowledgeBase entry.
| |||||
| 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
| |||||
| 177272 Return | Closing a LabVIEW WSN project does not close the LabVIEW WSN VI N/A Workaround: Close the WSN VI manually.
| |||||
| 243230 Return | WSN System Monitor does not update to reflect changes to your LabVIEW Project The WSN System Monitor does not automatically update to reflect changes to your project. Changes such as Adding/deleting Gateways/Nodes, changing Gateway IP/Node ID; Refreshing node serial numbers will not automatically reflect in the WSN System Monitor. Workaround: Restart the System Monitor to update its state.
| |||||
Document last updated on 12/29/2010