Update!

Technical NI LabVIEW
1

Dont know if it’s really even worth mentioning but the LV update has been updated to 3.1
not sure what the differences are just thought i’d let you guys know

2

That was released January 8, almost a month ago. Old news ?

**

3

Update 3.0 was released January 8, Update 3.1 was released yesterday. NI didn’t update the release date on their website

Inside the zip file is a readme that says what they changed.

Make sure you install the v27 cRIO image that was included with the update.

4

According to http://joule.ni.com/nidu/cds/view/p/id/2261 the FRC LabVIEW update was 3.1 back on January 8th… and I don’t see any new information on the Software Updates page: http://www.usfirst.org/roboticsprograms/frc/content.aspx?id=18758

5

Was this officially announced somewhere? I thought I was paying close attention to the information flood :ahh:

6

If you are connected to the internet when you start LabVIEW, There’s a release announcement in the upper right hand corner. Updates for all three languages were released yesterday.

I’d guess it will probably be mentioned in today’s team update.

7

That is a bit unsettling.

**

8

It’s up there now.

9

It was up there before.

But they didn’t update the release date.

It still says

Available Downloads:
Standard Download: FRCLabVIEWUpdate3.1for2011.zip (100 MB)

Download Language: English
Product Line: Academic
Version: 2011
Release date: 01-08-2011
Software type: Application Software
Operating system: Windows

**

10

Bug Fixes and Updates

The 3.1 update includes the following bug fixes and updates:

* Allows your robot to communicate with the FRC Field Management System.
* Allows you to build applications using the licensed IMAQ VIs.
* Enables the Data Entry page of numeric controls to update properly in LabVIEW 8.6.1.
* The NI Example Finder includes examples for Vision and for the linear encoder sensor.
* The default value of the LED toggle rate global variable in the Robot Global Data VI changed to a 10 millisecond loop delay.
* The Begin VI in the FRC cRIO Robot project includes the DIO Open VIs so that IR sensors work as expected.

Known Issues

The 3.1 update includes the following known issues. This list might not include all known issues for this update.

* When you use more than one encoder, the rate indicator does not update for all encoders. To avoid this behavior, write your own encoder rate code.
* LabVIEW hangs if the CONSOLE OUT switch on the CompactRIO device is on while you use the black Jaguars motor controllers with the CAN bus.
* The LabVIEW Help does not contain detailed help for the CAN API, the MotorControl Enable VI, and the MotorControl Disable VI. Visit the NI FRC Community Web site to access available FRC training material.
* The GetSpeed VI on the MotorControl VIs palette changed to the GetOutput VI, but the LabVIEW Help does not reflect this change.
11

Bug Fixes and Updates

The 3.1 update includes the following bug fixes and updates:

  • Allows your robot to communicate with the FRC Field Management System.
  • Allows you to build applications using the licensed IMAQ VIs.
  • Enables the Data Entry page of numeric controls to update properly in LabVIEW 8.6.1.
  • The NI Example Finder includes examples for Vision and for the linear encoder sensor.
  • The default value of the LED toggle rate global variable in the Robot Global Data VI changed to a 10 millisecond loop delay.
  • The Begin VI in the FRC cRIO Robot project includes the DIO Open VIs so that IR sensors work as expected.

Known Issues

The 3.1 update includes the following known issues. This list might not include all known issues for this update.

  • When you use more than one encoder, the rate indicator does not update for all encoders. To avoid this behavior, write your own encoder rate code.
  • LabVIEW hangs if the CONSOLE OUT switch on the CompactRIO device is on while you use the black Jaguars motor controllers with the CAN bus.
  • The LabVIEW Help does not contain detailed help for the CAN API, the MotorControl Enable VI, and the MotorControl Disable VI. Visit the NI FRC Community Web site to access available FRC training material.
  • The GetSpeed VI on the MotorControl VIs palette changed to the GetOutput VI, but the LabVIEW Help does not reflect this change.

But all of this stuff includes the 3.0 update not the differences between 3.0 and 3.1 which is in the file

12

Do we need to create a new FRC cRIO Robot Project after applying this update or are we still good?

13

No, all of what you quoted is new to the 3.1 update. The only thing wrong in the readme is that this one item:

“LabVIEW hangs if the CONSOLE OUT switch on the CompactRIO device is on while you use the black Jaguars motor controllers with the CAN bus.”

has actually been fixed.

14

No, your existing project will work. But you do need to reimage the cRIO first.

15

Sorry about the release date not being changed. We’ll fix that. This is a required update that you need.

16

I’m sure the official email from FIRST has announced this by now. But as Joe Ross mentioned, you would see a message on the Getting Started Window of LabVIEW. It’s not uncommon to see this message before the official email. I added this hook to the Getting Started Window, so LabVIEW users get reminded. It pings ni.com once a day for new updates, so you find out about them almost as soon as we post them. One day we aspire to post updates and have the release dates correct too:)

17

The updated labVIEW File caused my labVIEW to not work anymore. When I open it up and hit launch it says unable to open resource files and then closes.
What happened and how do I fix it?

18

I did the install on 2 laptops…LV comes up on one, not the other. The same error! ‘Unable to open resource files’

19

I updated my copy on the one laptop I have with me and it worked – meaning I have little to debug with.

John, can you compare the procedure on the two laptops? Do you think it was a difference in the laptop or in the install steps?

Can you easily compare the results? Inside Program Files/National Instruments/LabVIEW 8.6/resource, there should be 95 items according to my installation. Do you see something obviously wrong?

Thanks in advance.
Greg McKaskle

20

I copied the entire resource subdirectory over to the afflicted laptop and got a Win7 “Program Has stopped working” with the following details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: LabVIEW.exe
Application Version: 8.6.0.4002
Application Timestamp: 4cb70867
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdbdf
Exception Code: c06d007e
Exception Offset: 0000b727
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: cba5
Additional Information 2: cba57985d4dfc600ca12eaab7140e875
Additional Information 3: 7cb7
Additional Information 4: 7cb7f00025d289dc6d0ac96eb597182c