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.

Re: Problem with LabView Update 3.2 #2
 

I unzip everything into another folder and I first run the AutoRun and I run the SetUp.

I have done the update for five times and Labview still doesnt run at all.

Re: Problem with LabView Update 3.2 #2
 

We extracted it out of the zip file and then ran the application. After re-imaging the cRio it should work. The update came out yesterday. :)

Re: Problem with LabView Update 3.2 #2
 

When the v28 cRIO image came out, we re-imaged our cRIO, and confirmed through the Driver Station. At the time (and currently) our classmate is at LV Update 3.1 The recent Update #12 says that Labview Update 3.2 and cRIO v28 firmware are required. We will be updating our classmate to LV 3.2.

Is there any reason for us to re-image the cRIO with the v28 image that comes with LV 3.2? I do not believe there would be, since I'm sure that the v28 images are the same. I just want to make sure, can one of the NI reps answer this?

Re: Problem with LabView Update 3.2 #2
 

I don't know what the NI reps will say, but I know when we don't install ALL updates and reimage, things don't go right. Also if the little version number is wrong when the inspectors look at your robot, you'll have to fix it at the regional. We reimaged ours yesterday, it works, it might pass inspection.

Re: Problem with LabView Update 3.2 #2
 

squirrel - Thanks for the response. To clarify, we will have everything updated (the DS and the cRIO) to the most current version at our event. My question is if it will be necessery to re-update the cRIO to v28 after we update the DS to LV 3.2, because the cRIO is already at v28 and the DS is at LV 3.1

Re: Problem with LabView Update 3.2 #2
 

what I was hinting at is, when in doubt, reimage. it's not worth the hassle of having to do it later if you can do it now.

Re: Problem with LabView Update 3.2 #2
 

The reason that I'm posting this is because we have already shipped our robot, and trying to avoid any un-needed downtime on our first day at our event. I understand that re-imaging the cRIO is not normally a time consuming process, but sometimes things happen, and I would rather avoid having things happen at an event that do not necessarily* have to happen. It's all about proper risk management. Normally, I would absolutely agree with your comment about "worth the hassle". However, there have been (very rarely) times when re-formatting the cRIO for whatever reason, including a firmware update, resulted in a series of events to happen that resulted in a significant increase in down-time. Some of these reasons include: Ethernet connection comes unplugged, battery dies, computer stops responding, etc. Obviously most of these things can (and are) mitigated as best as possible by proper procedures, communication and extreme diligence. But sometimes things happen, that you cannot control.

Necessarily is obviously the word in question, and since I was not involved with developing the changes and the documentation supplied does not imply that updating the cRIO before the Driver Station is required (as long as the cRIO is at the correct level before-hand) I feel this is a valid question.

Re: Problem with LabView Update 3.2 #2
 

v27 had real changes and a real bug in netconsole that corrupted the stack.

V28 fixed the netconsole bug. I don't know of any other changes. If it is in the bag, don't sweat it.

Greg McKaskle

Re: Problem with LabView Update 3.2 #2
 

I'm still not sure if I know what you're asking. Are you asking if the v28 image from Labview update 3.2 installed from your own computer is the same as the v28 image from LabVIEW update 3.2 installed from the classmate? Or, did you download the pre-release v28 image that Joe Hershberger posted, and want to know if that is the same image that was installed the the LabVIEW update 3.2? Or something else?

Re: Problem with LabView Update 3.2 #2
 

This is what I was asking about, although I assume that the v28 image that was released by Joe Hershberger is no different than the one that is included with LV update 3.2 We updated the cRIO to v28 before LV update 3.2 came out (due to the stack overflow issue and my (incorrect) guess that FIRST would not come out with a mandatory update a week before ship date), then updated the Classmate to LV 3.2, would it be necessary for the FMS or any other reason to re-image the cRIO to v28 (again).

I understand this is confusing, but thanks Greg for the clarification.

Re: Problem with LabView Update 3.2 #2
 

We also shipped our robot before seeing update 12. So we will have to reimage at the regional. I think there will be several teams in this predicament.

But just for clarification, the update was for LabView with a new cRIO image. I didn't see anything about a Driver Station software update. Is it necessary to update the classmate? We typically use the classmate only for the Driver Station and use a Laptop for coding and reimaging the cRIO.

Re: Problem with LabView Update 3.2 #2
 

(I believe) It is necessary (generally) if either of the following conditions are true:
-You plan on updating the cRIO firmware with the Classmate or
-You do LabView programming on the Classmate

Re: Problem with LabView Update 3.2 #2
 

I have the same problem "unable to open resource files". I ran the update from the extracted file, not the zip file. I have tried to run it two more times and I get the same error.