Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   NI LabVIEW (http://www.chiefdelphi.com/forums/forumdisplay.php?f=182)
-   -   Errors on LabVIEW (http://www.chiefdelphi.com/forums/showthread.php?t=73626)

PHSRobotics 04-02-2009 20:54

Errors on LabVIEW
 
Alright our team is trying to program the shooter that erin's brother designed and said that we needed. We keep getting errors and no matter what we change or move, the error remains.
Error -44085 occurred at Loaded FPGA has incorrect version or revision. Library expecting Version 2009, Revision 1.0.0.
That is the error.
HELP!! :cool:
p.s. Erin's our Captain

Mark McLeod 04-02-2009 21:33

Re: Errors on LabVIEW
 
You need to update the firmware on the cRIO with the latest Update 3.
Use the FRC cRIO Imaging Tool and format the controller with v11.

PHSRobotics 04-02-2009 22:08

Re: Errors on LabVIEW
 
We already did. When we run it, we are only running the program on the laptop, without the cRIO connected. Is that a problem? :cool:

Mark McLeod 04-02-2009 22:36

Re: Errors on LabVIEW
 
Quote:

Originally Posted by PHSRobotics (Post 814374)
Is that a problem? :cool:

Yep, there's no FPGA on your PC. :ahh:

intellec7 05-02-2009 14:03

Re: Errors on LabVIEW
 
Here is the issue, I think:

the cRIO has the latest image, (v11). LabVIEW, though, is not upgraded to version 3.0a. You need to install http://joule.ni.com/nidu/cds/view/p/lang/en/id/1180 . There is another 3.0 installation, but that is to update WindRiver.

Edit: Oh, never mind that won't help you if you're trying to run it on the PC. But if anyone else receives that error while trying to run the program on a cRIO, chances are the FPGA image and LabVIEW are not on the same update.

FRC2476 10-02-2009 13:31

Re: Errors on LabVIEW
 
We are also getting error 44085--it appeared seemingly spontaneously and we can no longer run any programs. :(

We have version 3.0A of Crio and v11 of the controller. Any ideas as to what we can do specifically??

any response would be much appreciated.

Alan Anderson 10-02-2009 13:44

Re: Errors on LabVIEW
 
Quote:

Originally Posted by FRC2476 (Post 817950)
We have version 3.0A of Crio and v11 of the controller. Any ideas as to what we can do specifically??

Specifically, you can help us figure out what you're referring to. I'd usually consider the cRIO and "the controller" to be the same thing.

There are three or four things that you need to keep updated properly. First is the LabVIEW environment on your programming computer (that should be Update 3.0a). Second is the cRIO image (v11), which gets installed along with the LabVIEW update. Third is the Driver Station firmware (2009-01-22c1). I'm not keeping track of the the WindRiver libraries myself, since I'm focusing on LabVIEW, but you need to keep it up-to-date as well if you intend to use C++ for programming.

Jon236 10-02-2009 22:11

Re: Errors on LabVIEW
 
When re-imaging with 3.0a and ver 11, I keep getting an 'error 56'. Any idea of what that is?

It had been running well up to this point.

Greg McKaskle 10-02-2009 23:00

Re: Errors on LabVIEW
 
56 is a timeout on a network operation. Simplify the network connection and see if that helps.

To get quick explanation of errors, you can use Help>>Explain Error, or you can usually right click on an error control and Explain...

Greg McKaskle

Jon236 10-02-2009 23:03

Re: Errors on LabVIEW
 
Quote:

Originally Posted by Greg McKaskle (Post 818321)
56 is a timeout on a network operation. Simplify the network connection and see if that helps.


Greg McKaskle

All I had was a crossover cable from the laptop to the cRio

Mark McLeod 10-02-2009 23:55

Re: Errors on LabVIEW
 
Try running through the DS, using it as a switch. e.g., PC to DS to cRIO wired directly. Sometimes using a switch as an intermediary smooths communications.

Greg McKaskle 11-02-2009 09:34

Re: Errors on LabVIEW
 
Make sure to disable firewalls, and perhaps try on a different computer.

Greg McKaskle

Alan Anderson 11-02-2009 10:00

Re: Errors on LabVIEW
 
Quote:

Originally Posted by Greg McKaskle (Post 818321)
56 is a timeout on a network operation.

One thing that might point to is a mismatch in the network addressing. Make sure your computer's IP address and mask are what they should be (10.2.36.6/255.255.255.0), and that the cRIO Imaging Tool is being told the correct team number (236). You could also get away with using 255.0.0.0 for the network mask.


All times are GMT -5. The time now is 08:38.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi