Labview Update 3.2

[Mark McLeod]

Skip the 3.1 Update and go right to the latest 3.2 Update.
There is a bug in the 3.1 image that can cause problems.

You must Build your code again after every FIRST Update.

[Team1908]

Do you really have to rebuild your code after every update? Why can't you just use the same code as before?

Going back a few posts, we had a similar problem connecting to our cRIO via tether but could connect wirelessly. Are you using an ethernet cord or a crossover cord? Try them both and see if you can see a difference.

[Mark McLeod]

You don't have to write your code all over again, just "Build" & "Run as startup" to pull in new library changes and match the new cRIO image you just downloaded.

[rwood359]

Originally Posted by Mark McLeod

Skip the 3.1 Update and go right to the latest 3.2 Update.
There is a bug in the 3.1 image that can cause problems.

You must Build your code again after every FIRST Update.

Do the Utilities and Drivers Station updates have to be re-run after each LV update or only after the first time the DVD version is updated?

[Mark McLeod]

Originally Posted by rwood359

Do the Utilities and Drivers Station updates have to be re-run after each LV update or only after the first time the DVD version is updated?

No worries.

You don't have to reapply any of the other software Updates (unless they someday have little updates of their own).
The LabVIEW update stands alone.