LabVIEW reentrant VIs

[Starwarsguy2]

I am choosing "Preallocated clone reentrant execution". I'll upload the code as soon as I can, should be late sometime tonight. I barely have enough time to post this now. Thanks!

[wt200999]

One thing to note when it comes to reentrant VIs on LabVIEW Real-Time (when deployed to roboRIO) is that none of the LabVIEW debugging tools are available, so you either need to make a copy or use a different method to debug. See the note here.

[Greg McKaskle]

There should be no problem reading the pots with the non-reentrant VI. Setting it to reentrant will have no effect on the result, but will allow for the two calls to proceed in parallel - up to the point where there may be another reason for them to take turns.

What I'd suggest you do is to drop charts on the panel of your VI and wire the output of the pot to the charts. Run the VI and see if moving pot A affects the chart. See if moving pot B affects the chart. If you are receiving 0's, they may be due to a wiring connection rather than reading the wrong pot.

While running, wiggle the wires and see if you can locate a connection issue anywhere along the cable.

Please let us know what you find.

Greg McKaskle

[Starwarsguy2]

Thank you all very much for your replies. However, the issue turned out to be much more grave. The 5V analog in rail was only supplying a maximum of .3 volts ! We tried our hardest to clean out the RoboRIO but the problem still persisted. Sadly, the mentors are thinking that this is a bad RIO. It went through two rough seasons, so it had to go eventually. (But it just had to die 2 days before a competition ) We are borrowing a RIO from another team in the meantime. Again, thanks for all the help, and if you have any suggestions to bring a RoboRIO back from the dead, they'll be greatly appreciated.

Jake

[Greg McKaskle]

The most reliable way is to contact NI for repair/replacement. AndyMark may also be a good place to start if it was purchased there.

Greg McKaskle