Problem with LabView Update 3.2 #2
 

:yikes: We installed LabView update 3.2 and when we downloaded our code which was working with 3.0 the digital side car did not put out any pwm signals??? The rest of the digital side car worked. We had DIO inputs from the line sensors and compressor switch working. And the relay outputs to the compressor worked as well. Only the PWM signals were not functioning. I didn't have a scope to check the pwm signals but the Jaguars and the victors didn't see any. Is this a problem with the FPGA crio load?? Help.
Thanks
Tom

Re: Problem with LabView Update 3.2 #2
 

I just installed LabView Update 3.2 #2, and now LabView won't run at all. When I try to launch it, it says "Unable to open resource files." This is a horrible time to have no LabView! Suggestions anyone?

Re: Problem with LabView Update 3.2 #2
 

when did first give out the 3.2 update?
Last i got, it was 3.1.

Re: Problem with LabView Update 3.2 #2
 

It looks like it was released yesterday.

Re: Problem with LabView Update 3.2 #2
 

The FPGA did not change with 3.2, only NetConsole changed.

Re: Problem with LabView Update 3.2 #2
 

That seems to mean you tried to run the update from within the .zip file.

Uncompress everything and run it again.

Re: Problem with LabView Update 3.2 #2
 

We've heard of this happening when Windows decides to update in the middle of your FRC install. Usually running the FRC update again fixes it. I'm curious how you run the FRC update. Do you unzip it to a folder, and then run the installer?

Re: Problem with LabView Update 3.2 #2
 

I'm having this same problem and the same error message pops up every time I try to install the 3.2 update. I also cannot roll back to 3.1

Re: Problem with LabView Update 3.2 #2
 

Exactly how are you installing it?

Re: Problem with LabView Update 3.2 #2
 

By extracting everything from the .zip archive and running Autorun.

I'll just reinstall LabVIEW.

Re: Problem with LabView Update 3.2 #2
 

Problem wasn't with the update at all. Learned about the DriveSafteyUpDate.VI. The TeleOp.VI wasn't running fast enough.::rtm::

Re: Problem with LabView Update 3.2 #2
 

How did you solve the problem?

Re: Problem with LabView Update 3.2 #2
 

I'm sorry to say this, but we had the same problem and the way we fixed it is to reinstall labview. also remember to extract the update before running it.

Re: Problem with LabView Update 3.2 #2
 

We had to remove some code that was measuring a Potentiometer in a while loop inside the teleop.vi The code wasn't running fast enough for the WPI_RobotDriveSafetyUpdate.vi to get the update signal that resets it so it disables all PWM signals. Then the Jag's/Victors see no control and disable their oututs. I think...

Re: Problem with LabView Update 3.2 #2
 

Can you post your code? In general, it is a bad practice to put while loops in the Teleop.vi for the reason you mentioned. When we implement sensors we normally put these in a "Sensors" While Loop in Periodic Tasks, with about a 20-40 ms wait.