Software Update Issues to newest release versions

[MarkBlack]

RandySteiner wrote:

The other thing I tried was a different laptop with a fresh install of labview with the updates.  This worked and solved the no code issue.  If I go back to the other laptop, running the same version of labview and updates it doesn't work.  This other laptop worked before trying the upgrade.  So I am very puzzled.  If I have time I will try to do a file compare of the installed labview instances between the two machines.  I may try applying the update to another laptop to see if it has the same issue.

We have seen this issue most often caused by the image on the cRIO not corresponding to the latest update in LabVIEW. Is it possible that this or another setting has been over looked?

[Randy_Steiner]

I don't think it is the image directly due to the fact I went through these steps on the laptop with the issue.

Downloaded all updates to a flash drive from a machine that had internet access.

Copied the updates over.

Updated the Windriver insalation first.

Updated Labview second.

(the one thing I did not do right away was reboot the laptop and I wonder if htis had something to do with it somehow)

I updated the drivers station.

Fixed the team number on the DS.

I then flashed (formated) the cRIO with the imaging tool.

Open and reloaded our code.  This is when we saw there was an issue.

I backed up and tried a brand new advanced robot project, same issue.  We reimages the dRIO and saw the default program at least talked to the drivers station.

At that point we had to get things done so we rolled back to a previous version.

Then we went through the steps in a previous email to get to a similar point.

The important thing to note is that when I switch to the other laptop I did not change the image on the cRIO.  it was still the one installed from the bad computer, but it works on the new laptop.

the difference for the new laptop is it had a fresh install of labview (no other updates applied) and then the updates were installed in the same order AND I rebooted after the install.

I hope that helps.  So I think it is one of two things.  On the bad laptop either the single upgrade did not take right without the reboot, or the fact we had installed the updates along the way.  We installed the second update when on a resh install as this laptop was put to use later in the year (which fixed the one template issue for the build for deploy on the basic framework), then we installed the last update.  I wonder if the cumulative updates are causing an issue.

I can also try upgrading our other working laptop and reboot it and see if it works.  I am not too worried about doing that now that the new laptop is working with the new code.  I can keep another laptop on the older version incase we ned to flash back for testing purposes.

Thanks!

[Randy_Steiner]

OK two notes of update.

First, I tried updating the labview instance on the bad laptop again, but this time with a different download.  It appears that we have updated the WPI libraries (which I blieve is where the cRIO image is from) but the labview update was the wrong version.  This expains the No Code on the drivers station.

After upgrading with the correct vesion of labview everything seems to be working fine.

Second note, the strange DS behavior where it would disable in atonomous seems to have gone away.  I am not sure if it is related to the code issue ot not, I will see if I can recreate it.

Thank you!

Randy