Archived: LabVIEW Wireless Sensor Network Module Beta Known Issues

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.

Aperçu

This document has been archived and is no longer updated by National Instruments.

This document contains the known issues that were discovered before and since the release of LabVIEW Wireless Sensor Network Module Beta. 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
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)

Document Organization

The Known Issues Document displays the issues by issue category.

Known Issues by Category

Please refer to Developer Zone Article " LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.

Contacting NI

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.

Known Issues by Category

The following items are known issues in LabVIEW Wireless Sensor Network Module Beta sorted by Category.

Building and Distributing LabVIEW Applications
174173 LabVIEW WSN projects cannot be built and deployed from network locations
Documentation
170692 Error message from the LabVIEW WSN Host API is not very helpful
177271 The list of possible values for the message status returned by WSN Message Status VI do not match the Help
Functions, VIs, and Express VIs
168370 Get Date/Time function returns incorrect value after the Node is reset
163360 Scan From String function does not update its error out output when used in the LabVIEW WSN Target VI
177306 The WSN Host API Palette shows sub-palettes for unrelated toolkits/modules
156537 Link Quality IO Variable and the WSN Get Node Info VI return inconsistent results
160845 Wiring an input of type double to the data in input of Write to Sector Single VI causes the build to fail
162179 Resizing the RadioMessages.xnode breaks existing wires
163359 Using the %x format specifier with the Format to String function truncates 64-bit unsigned integers to 32-bit unsigned integers
169915 The Number To Exponential String function leaves the result in floating point format
174830 In the RadioMessages.xnode, changing the terminal from Send User Message to Send Debug Message breaks the existing wire
LabVIEW Project
142865 Renaming an IO Variable does not change the name of the corresponding Radio Message Node
175726 Deployment of LabVIEW WSN Target VI cannot be cancelled through the LabVIEW Project
Operating System Specific
176233 The LabVIEW WSN Module does not work with the Japanese language version of Windows XP
Performance
141771 Changes to sample interval are not applied instantaneously
148709 Maximum sample rate of the NI WSN-3202 Voltage Node is only 20 S/sec using the LabVIEW WSN Target VI
Shared Variables
142865 Renaming an IO Variable does not change the name of the corresponding Radio Message Node



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.

Reported Version: 1    Resolved Version: N/A    Added: 07/15/2009
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 Ethernet Gateway, LabVIEW displays the following error message: Error -25224 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

Reported Version: 1    Resolved Version: N/A    Added: 07/15/2009
177271

Return
The list of possible values for the message status returned by WSN Message Status VI do not match the Help
The possible values for message status are: Waiting to Send, Sent to node, Failed, Cancelled The documentation lists the possible values as: Cancelled, Completed, Failed, Waiting for acknowledge, and Waiting to send

Workaround: N/A

Reported Version: 1    Resolved Version: 1    Added: 07/15/2009
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. Then 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

Reported Version: 1    Resolved Version: N/A    Added: 07/07/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/15/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/15/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/17/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/17/2009
162179

Return
Resizing the RadioMessages.xnode breaks existing wires
Resizing the RadioMessage.xnode breaks existing wires and removes previously connected terminals.

Workaround: N/A

Reported Version: 1    Resolved Version: N/A    Added: 07/17/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/17/2009
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 leaves the result in the floating point format.

Workaround: N/A

Reported Version: 1    Resolved Version: N/A    Added: 07/17/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/17/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/13/2009
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.

Reported Version: 1    Resolved Version: N/A    Added: 07/16/20096
Operating System Specific
176233

Return
The LabVIEW WSN Module does not work with the Japanese language version of Windows XP
The LabVIEW Wireless Sensor Network Module is not completely compatible with the Japanese language version of Windows XP. Specifically, the following issues are seen: 1. The LabVIEW WSN Target VI is not added to the project 2. Elemental I/O is broken 3. Rename option does not work

Workaround: N/A

Reported Version: 1    Resolved Version: N/A    Added: 07/15/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/13/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/15/2009
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

Reported Version: 1    Resolved Version: N/A    Added: 07/13/2009

Document last updated on 7/20/2009

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).