FIRST Robotics Competition Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW error for subvi and watch dog after update 2.1 and 1.1 for DS

ok I have installed both updates and now ALL of my subvi DO NOT work at all.

1. I noticed when LabVIEW was up after going through Measurment & automation that it could not find my previous projects and I have to manually point to it. THIS WAS THE START OF THE PROBLEMS

2. Subvi is unresponsive to probe

3. Watchdog causes robot code light to cycle between no code and having code

4. Watchdog complains about a NI_FPGA VI not found.

5. The pause button is gone

my older build works when I flash it to the bot just fine

the CRIO has been image to v20

I wish I NEVER PUT THESE UP DATES IN. EVERYTHING WAS WORKING UNTIL THESE UPDATES.

0 Kudos
Message 1 of 5
(7,764 Views)

I'm the software mentor for the team that's enduring this issue.  We seem to have only two courses of action:

(1) Uninstall Labview and then reinstall without these latest updates.  However, how does that effect our ability to connect to the arena network?

(2) Create a new project and move everything over, file by file and see if this works.

It would have been helpful if NI had a late night response capability, especially this weekend.

Another SW mentor was surfing CD without finding a similar thread.  If any thread exisits, Please post ! !

0 Kudos
Message 2 of 5
(3,290 Views)

Can you elaborate on the errors you're seeing, by posting the actual error text?  I work with several teams and none have seen any problems with the upgrade.  Is it possible you, or one of your teammates, changed something else in the code at the same time that happened to cause some of your problems?  Did you modify any of the VIs that were provided by FIRST/NI?  If so, those may have been overwritten during the upgrade.  Your issues "SubVI is unresponsive to probe" and "The pause button is gone" sound like the VI execution properties were changed - maybe it was changed to subroutine priority, or set to run reentrant.  I assume it's only some of your VIs that exhibit this behavior, not all of them - which ones?

I don't understand your issue 1) at all.  Why are you opening Measurement and Automation Explorer?  It shouldn't be necessary, and it's definitely not responsible for loading your LabVIEW projects.

Note that according to the documentation, you do need all updates installed in order to compete.

0 Kudos
Message 3 of 5
(3,290 Views)

We have decided to reconstruct the code from scratch with a new project.  We are proceeding with small increments to return our code to the previous levels of operation.  Hopefully, we do not require ANY OTHER updates before the season really begins.

0 Kudos
Message 4 of 5
(3,290 Views)

I'm sorry to hear the updates are giving you trouble.  But let me explain a couple of things.  First, we don't do updates just for the fun of it.  We only do them if we have to - typically to fix a bug that is either causing everyone grief, or is a safety error.  There is a lot of work and testing that has to happen for an update.  We would much rather just explain a work around if we can.

For this update I tested many installation scenarios, and everything worked.

When you ask for help, we need details.  What type of watchdog errors are you getting?  If they are System, it means your classmate can't send data fast enough.  This was typical before the update - it should not be a problem after the update unless you have installed extra software and are overextending the bandwidth of the system.  If you are getting User watchdog errors, it is likely something you are doing in your code that is causing you to not feed the watchdog often enough.  Please add details about your trouble.

0 Kudos
Message 5 of 5
(3,290 Views)