Archived: LabVIEW 2013 Wireless Sensor Network Module Pioneer 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.

Overview



This document contains the LabVIEW 2013 Wireless Sensor Network Module Pioneer known issues that were discovered before and since the release of LabVIEW 2013 Wireless Sensor Network Pioneer. Not every issue known to NI will appear on this list; it is intended to only show common and severe issues that can be encountered.
The LabVIEW 2013 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Document Organization

The Known Issues document is divided into two separate tables. The following section displays the issues by category.

Known Issues by Category

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

For those who wish to locate newly reported issues, we have also published a section of the known issues table sorted by the date each item was added to the document.

Known Issues by Date

Known Issues by Category

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

Analysis and Math
162792 WSN Nodes only support single precision numbers
232868 Use of Subnormal numbers can cause compiler errors
Building and Distributing LabVIEW Applications
174173 LabVIEW WSN projects cannot be built and deployed from network locations
178162 Closing the Project Explorer does not close the WSN System Monitor
245294 WSN Target VIs with long disk paths fail to build.
275744 Unable to build WSN Target VIs contained within a library (.lvlib).
Functions, VIs, and Express VIs
162179 Resizing the RadioMessages.xnode breaks existing wires
174830 In the RadioMessages.xnode, changing the terminal from Send User Message to Send Debug Message breaks the existing wire
204567 If you have VIs named device config.vi and radio message.vi in your Project, their contents might be dropped from the application
209601 Input constants for WSN Config Nodes created in LabVIEW 2009 might appear faded in LabVIEW 2009 SP1 and later
211423 Sending User Messages in a loop might cause NI 9792 gateway to run out of memory
304873 Unwired User RAM Property Node shows "No Properties".
310618 WSN Target VIs cannot read time below 1 second resolution.
316141 Shared Variable Write function with User RAM Reference can cause WSN Node to crash.
LabVIEW Project
142865 Renaming an IO Variable does not change the name of the corresponding Radio Message Node
177272 Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
310530 LabVIEW Sound and Vibration Palette Show Up In LabVIEW WSN Palette

 

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

Reported Version: 1.0    Resolved Version: N/A    Added: 08/16/2010
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

Reported Version: 2010    Resolved Version: N/A    Added: 08/16/2010
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.0    Resolved Version: N/A    Added: 07/15/2009
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

Reported Version: Orion    Resolved Version: N/A    Added: 08/16/2010
245294

Return
WSN Target VIs with long disk paths fail to build.
Long disk paths may cause the build process for WSN target VIs to fail.

Workaround: Move the WSN Target VI to a location with a shorter path and rebuild the WSN application.

Reported Version: 2010    Resolved Version: N/A    Added: 12/02/2011
275744

Return
Unable to build WSN Target VIs contained within a library (.lvlib).
Placing a WSN Target VI inside a library (.lvlib) causes the VI to generate build errors.

Workaround: Move the WSN Target VI outside of the library and rebuild the WSN Application.

Reported Version: 2010    Resolved Version: N/A    Added: 12/02/2011
Functions, VIs, and Express VIs
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.0    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.0    Resolved Version: N/A    Added: 07/17/2009
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

Reported Version: 2009 SP1    Resolved Version: N/A    Added: 08/16/2010
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.

Reported Version: 2009 SP1    Resolved Version: N/A    Added: 08/17/2010
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.

Reported Version: 2009 SP1    Resolved Version: N/A    Added: 11/12/2010
304873

Return
Unwired User RAM Property Node shows "No Properties".
When using a User RAM Property Node configured for WSN User RAM reference type but with no User RAM Reference wired to it the node does not display any available properties.

Workaround: Connect a User RAM Reference to the User RAM Property Node

Reported Version: 2011    Resolved Version: N/A    Added: 12/02/2011
310618

Return
WSN Target VIs cannot read time below 1 second resolution.
Timestamping on the WSN target VIs does not support millisecond resolution

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 12/02/2011
316141

Return
Shared Variable Write function with User RAM Reference can cause WSN Node to crash.
In a WSN target VI using a Shared Variable Write function with User RAM Reference can cause the WSN Node to crash if the reference has become invalid.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 12/02/2011
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.0    Resolved Version: N/A    Added: 07/13/2009
177272

Return
Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
When a LabVIEW WSN project is closed, the LabVIEW WSN VI is not closed automatically.

Workaround: Close the WSN VI manually.

Reported Version: 1.0    Resolved Version: N/A    Added: 07/29/2009
310530

Return
LabVIEW Sound and Vibration Palette Show Up In LabVIEW WSN Palette
On a system with both LabVIEW WSN and LabVIEW Sound and Vibration installed the LabVIEW Sound and Vibration palette shows up in the LabVIEW WSN Palette, but the LabVIEW Sound and Vibration functions are not supported on LabVIEW WSN.

Workaround: LabVIEW Sound and Vibration VIs are not supported by LabVIEW WSN. Do not use Sound and Vibration VIs in a WSN Node Target VI.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 12/02/2011

Known Issues by Date

The following items are known issues in LabVIEW 2013 Wireless Sensor Network Module Pioneer sorted by Date.

142865 Renaming an IO Variable does not change the name of the corresponding Radio Message Node
174173 LabVIEW WSN projects cannot be built and deployed from network locations
162179 Resizing the RadioMessages.xnode breaks existing wires
174830 In the RadioMessages.xnode, changing the terminal from Send User Message to Send Debug Message breaks the existing wire
177272 Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
162792 WSN Nodes only support single precision numbers
178162 Closing the Project Explorer does not close the WSN System Monitor
204567 If you have VIs named device config.vi and radio message.vi in your Project, their contents might be dropped from the application
232868 Use of Subnormal numbers can cause compiler errors
209601 Input constants for WSN Config Nodes created in LabVIEW 2009 might appear faded in LabVIEW 2009 SP1 and later
211423 Sending User Messages in a loop might cause NI 9792 gateway to run out of memory
245294 WSN Target VIs with long disk paths fail to build.
275744 Unable to build WSN Target VIs contained within a library (.lvlib).
304873 Unwired User RAM Property Node shows "No Properties".
310530 LabVIEW Sound and Vibration Palette Show Up In LabVIEW WSN Palette
310618 WSN Target VIs cannot read time below 1 second resolution.
316141 Shared Variable Write function with User RAM Reference can cause WSN Node to crash.

 

ID Known Issue
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.0    Resolved Version: N/A    Added: 07/13/2009
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.0    Resolved Version: N/A    Added: 07/15/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.0    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.0    Resolved Version: N/A    Added: 07/17/2009
177272

Return
Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
When a LabVIEW WSN project is closed, the LabVIEW WSN VI is not closed automatically.

Workaround: Close the WSN VI manually.

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

Reported Version: 1.0    Resolved Version: N/A    Added: 08/16/2010
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

Reported Version: Orion    Resolved Version: N/A    Added: 08/16/2010
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

Reported Version: 2009 SP1    Resolved Version: N/A    Added: 08/16/2010
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

Reported Version: 2010    Resolved Version: N/A    Added: 08/16/2010
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.

Reported Version: 2009 SP1    Resolved Version: N/A    Added: 08/17/2010
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.

Reported Version: 2009 SP1    Resolved Version: N/A    Added: 11/12/2010
245294

Return
WSN Target VIs with long disk paths fail to build.
Long disk paths may cause the build process for WSN target VIs to fail.

Workaround: Move the WSN Target VI to a location with a shorter path and rebuild the WSN application.

Reported Version: 2010    Resolved Version: N/A    Added: 12/02/2011
275744

Return
Unable to build WSN Target VIs contained within a library (.lvlib).
Placing a WSN Target VI inside a library (.lvlib) causes the VI to generate build errors.

Workaround: Move the WSN Target VI outside of the library and rebuild the WSN Application.

Reported Version: 2010    Resolved Version: N/A    Added: 12/02/2011
304873

Return
Unwired User RAM Property Node shows "No Properties".
When using a User RAM Property Node configured for WSN User RAM reference type but with no User RAM Reference wired to it the node does not display any available properties.

Workaround: Connect a User RAM Reference to the User RAM Property Node

Reported Version: 2011    Resolved Version: N/A    Added: 12/02/2011
310530

Return
LabVIEW Sound and Vibration Palette Show Up In LabVIEW WSN Palette
On a system with both LabVIEW WSN and LabVIEW Sound and Vibration installed the LabVIEW Sound and Vibration palette shows up in the LabVIEW WSN Palette, but the LabVIEW Sound and Vibration functions are not supported on LabVIEW WSN.

Workaround: LabVIEW Sound and Vibration VIs are not supported by LabVIEW WSN. Do not use Sound and Vibration VIs in a WSN Node Target VI.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 12/02/2011
310618

Return
WSN Target VIs cannot read time below 1 second resolution.
Timestamping on the WSN target VIs does not support millisecond resolution

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 12/02/2011
316141

Return
Shared Variable Write function with User RAM Reference can cause WSN Node to crash.
In a WSN target VI using a Shared Variable Write function with User RAM Reference can cause the WSN Node to crash if the reference has become invalid.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 12/02/2011

Document last updated on 11/7/2014

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).