LabVIEW Update 3?

[dqmot17]

The title of the site says THIRD MANDATORY UPDATE, yet the file says 2.0 and the description says second update. Anyone try this, compare it to the other one?
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1180

[dqmot17]

The title of the page says THIRD MANDATORY UPDATE, but the download says 2.0, and the description says second update. Anyone test it out, see if it's different?
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1180

[MattD]

I saw that page and have been wondering that myself. The FRC Software Updates page at WPI has Update 3 there now too, but it requires FRC_2009_v11d.zip, which I assume is in the LabVIEW Update 3.

If you change the 2.0 to 3.0 in the FRCLabVIEWUpdate download URL, it works, but I'd really not want to try to install it until the link is actually posted somewhere.

Edit:

Looks like NI actually has updated that page with the 3.0 download. I'm downloading it now, and I'll try it out tonight if it's not too late.

[leftylink]

Downloaded and installed. The about screen tells me it's Version 3. Noticing a slight discrepancy in the cRIO image name (v11 instead of v11d), but I'll hope this isn't a problem unless we find out otherwise when we re-image the robot tomorrow...

[Joe Ross]

It's been fixed

[nathanww]

What exactly does it do? And is it mandatory if we're using windriver?

[TDohse]

Originally Posted by leftylink

Noticing a slight discrepancy in the cRIO image name (v11 instead of v11d), but I'll hope this isn't a problem unless we find out otherwise when we re-image the robot tomorrow...

Whoops. v11 and v11d are actually the same file. v11d was the internal name of the final incremental update to public release v11. NI renamed it to "v11" but WPI kept "v11d".

[ebmonon36]

Here are the bug fixes from the read me file:

Fixed an issue in which the FRC robot project uses up to 10% of CPU overhead to communicate with the camera even when the camera is not in use. The Update Camera Status subVI in the FRC robot project corrects this issue. If you create a new FRC robot project, the Update Camera Status subVI appears either in the Image Processing While Loop of the Basic Robot Main VI or in the Vision Processing VI of the Robot Main VI. If you continue working in a project you created in an earlier version of the FRC software, the project does not contain the Update Camera Status subVI. If you want to use the Update Camera Status subVI in an existing project to correct the CPU overhead issue, copy the subVI from a new FRC robot project, then paste and wire the subVI in the existing project similar to how it is used in the new project.

Fixed an issue in which running the CompactRIO Imaging Tool on Windows Vista returns unexpected error 60.

Fixed an issue in which if you perform 4x decoding, the Rate output of the Get VI on the Encoder palette returns half the correct rate although the value of the Distance output is correct.

The update also includes a new cRio image.

[dqmot17]

Do we need to update the image when we get a new update?

[ebmonon36]

If we do update the cRio with the new image, is there a DS update to go with that?

[dqmot17]

Originally Posted by ebmonon36

If we do update the cRio with the new image, is there a DS update to go with that?

On the update page, check if the DS update is the same as the one you used when you updated.

[Alan Anderson]

Originally Posted by dqmot17

Do we need to update the image when we get a new update?

Yes. Run the image update tool and you'll see the new V11 image available.

[RyanN]

Not sure if this is a bug, but after the update, LabView could not find the GyroDevRefToAnalogChannelDevRef.vi. This happened to me, and a member on Team Fusion.

If your team runs into this problem, the file can be located at:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Robotics Library\WPI\Gyro

[Bryan Herbst]

I also thought I should mention-

Update 3 includes a new "Get Alliance" VI which can return both the alliance, and the position of the alliance (not entirely sure what that is).

This helps eliminate one more switch from the robot.