Problems running Default LabView Code Version 3.0
 

We are trying to program our robot in Labview and are not having much success:
In earlier versions we were getting motors/sensors to run fine, but when we upgraded to version 3.0, we cannot get any pwm output, even with the default code. LabView seems to deploy fine and we get no errors in the cRio and the Driver Station, but there is no apparent signal from PWMs 1 and 2 (with joystick connected to USB 1).
We applied the firmware upgrade and everything, still with no luck.
Anyone else have similar problems?

Re: Problems running Default LabView Code Version 3.0
 

Did you re-image your CRio after you updated labview?

Re: Problems running Default LabView Code Version 3.0
 

Even though you've updated the cRIO with the latest v11, I'd suggest reformatting it one more time.

Re: Problems running Default LabView Code Version 3.0
 

I upgraded my vista laptop to version 3 and now the Gyro - Get Angle vi is broken (see screenshot). Is this a problem everyone has, or should I re-install?

When going from version 2 to 3 should we be able to use the same projects without modifying anything or re-inserting the WPI sub-vis?

Thanks!

Re: Problems running Default LabView Code Version 3.0
 

There is a problem in 3.0 and 3.0a with the Gyros.
See this thread on the First forum:
http://forums.usfirst.org/showthread.php?t=11660

Re: Problems running Default LabView Code Version 3.0
 

I am also having the same problem as the original poster. The code downloads successfully and the Driver Station says it has code, but the Jaguar's lights do not become constant and no pwm output occurs.

One of our mentors laptops can load the code and have it work though. I have checked that all our build settings and code are the same, but nothing seems to be wrong.

Re: Problems running Default LabView Code Version 3.0
 

We had similar problems until we carefully read the "readme" file. You have to re-image the CRIO to the latest version included with the update 3/

Rob