This document contains known issues for the LabVIEW 2014 Robotics Module. 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 2014 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
Each Issue appears as a row in the table and
includes these fields:
Legacy ID - The issue's legacy
ID from NI's deprecated bug reporting database (if applicable)
Reported Version - the earliest version of LabVIEW in which the
issue was reported
Resolved Version - version the issue was resolved or was no
Date Added - the date the issue was added to the document
(not reported date)
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. If you have feedback on this document, please contact NI on this NI Developer Zone post.
Performance of AD* VI slows over time
If significant changes occur to the map the AD* VI operates on and the VI is configured to mange the epsilon value automatically, the VI runs significantly slower over time.
Workaround: Try one of the following:
Set the 'overhaul' Boolean input to TRUE periodically to discard old state data that might no longer be relevant and to increase epsilon again.
Use the 'epsilon' input to directly control the value of epsilon and balance the speed of the VI versus the quality of the path that the VI calculates.
Starter Kit will reboot constantly if LabVIEW 2009 is not installed and no DHCP server is available
If the Starter Kit is configured to obtain an IP address via DHCP and there is no DHCP server available then its behaviour is as follows:
If LabVIEW 2009 is installed on the sbRIO: the network uses a private IP in 169.254.x.x range
If LabVIEW 2009 is not installed on the sbRIO: the network fails to obtain an IP address and reboots
Workaround: Setting the IP reset dip switch and rebooting will force the IP address to 0.0.0.0. Allow at least 15 seconds for the network to be initialized before switching the IP reset switch off. Then use the Hardware Setup Wizard or MAX as usual.
Error -2147220308 in Hardware Setup Wizard when Connecting to Zynq Target
Zynq targets require all web features to be installed to be recognized by the Hardware Setup Wizard. If a Zynq target has been reformatted these features will removed, and error -2147220308 will be thrown in the Hardware Setup Wizard
Workaround: In NI MAX install all web features and then restart the target.
NI MAX Does Not Detect Starter Kit 2.0 when Hardware Setup Wizard has Found Target
Hardware Setup Wizard locks target when it is discovered in step 3. NI MAX will not be able to discover the locked target if it has not already discovered the target in the past.
Workaround: Do not connect to target with NI MAX and Hardware Setup Wizard at the same time.