Print
PDFOverview
This document contains the LabVIEW 2012 Wireless Sensor Network Module Pioneer known issues that were discovered before and since the release of LabVIEW 2012 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.
The LabVIEW 2012 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 issue 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.
For those who wish to locate the newly reported issues, we have also published a section of the known issues table sorted by the date the issue was added to the document.
Contacting NI
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
Known Issues by Category
The following items are known issues in LabVIEW 2012 WSN Module sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Building and Distributing LabVIEW Applications | ||||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 310618 Return |
WSN Target VIs cannot read time below 1 second resolution. Workaround: N/A
|
|||||
| 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
|
|||||
| LabVIEW Project | ||||||
| 177272 Return |
Closing a LabVIEW WSN project does not close the LabVIEW WSN VI Workaround: Close the WSN VI manually.
|
|||||
| 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.
|
|||||
Known Issues by Date
The following items are known issues in LabVIEW 2012 WSN Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 177272 Return |
Closing a LabVIEW WSN project does not close the LabVIEW WSN VI Workaround: Close the WSN VI manually.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 310618 Return |
WSN Target VIs cannot read time below 1 second resolution. Workaround: N/A
|
|||||
| 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
|
Document last updated on 12/10/2012
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).