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.
The Known Issues document is divided into two separate tables. The following section displays the 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.
The following items are known issues in LabVIEW 2013 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
| |||||
| 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.
| |||||
| 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 | ||||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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. Timestamping on the WSN target VIs does not support millisecond 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 | ||||||
| 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 When a LabVIEW WSN project is closed, the LabVIEW WSN VI is not closed automatically. 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.
| |||||
The following items are known issues in LabVIEW 2013 Wireless Sensor Network Module Pioneer sorted by Date.
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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. Timestamping on the WSN target VIs does not support millisecond 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 11/7/2014