Archived: LabVIEW 2011 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.

Aperçu

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

This document contains the LabVIEW 2011 Wireless Sensor Network Module Pioneer known issues that were discovered before and since the release of LabVIEW 2011 Wireless Sensor Network Module Pioneer. 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.

Known Issues by Category

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

Analysis and Math
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
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
304873 Unwired User RAM Property Node shows "No Properties".
308934 Feedback node ignores refnum initializer.
308938 Uninitialized refnum shift register causes 3214 to reboot.
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
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
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
245294

Return
WSN Target VIs with long disk paths fail to build.

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
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
308934

Return
Feedback node ignores refnum initializer.
When using a feedback node in a WSN Target VI with the refnum data type the initilizer terminal value is ignored.

Workaround: Use Global Variables to store User RAM References.

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

Return
Uninitialized refnum shift register causes 3214 to reboot.
Including an uninitialized shift register of type refnum on a WSN Target VI causes the 3214 to reboot.

Workaround: Initialize Shift Register with User RAM Reference constant. Or Use Global Variables to store User RAM References.

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

Return
WSN Target VIs cannot read time below 1 second 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
177272

Return
Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
N/A

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 2011 Wireless Sensor Network Module Pioneer sorted by Date.

174173 LabVIEW WSN projects cannot be built and deployed from network locations
177272 Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
232868 Use of Subnormal numbers can cause compiler errors
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".
308934 Feedback node ignores refnum initializer.
308938 Uninitialized refnum shift register causes 3214 to reboot.
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
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
177272

Return
Closing a LabVIEW WSN project does not close the LabVIEW WSN VI
N/A

Workaround: Close the WSN VI manually.

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

Return
WSN Target VIs with long disk paths fail to build.

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
308934

Return
Feedback node ignores refnum initializer.
When using a feedback node in a WSN Target VI with the refnum data type the initilizer terminal value is ignored.

Workaround: Use Global Variables to store User RAM References.

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

Return
Uninitialized refnum shift register causes 3214 to reboot.
Including an uninitialized shift register of type refnum on a WSN Target VI causes the 3214 to reboot.

Workaround: Initialize Shift Register with User RAM Reference constant. Or Use Global Variables to store User RAM References.

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.

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 12/6/2011

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