FPGA Bit File Error -44085 when deploying using LabVIEW run button

[LabViewEnthusiast]

When using LabVIEW and trying to run a program with the Run button, we have sometimes recieved an error which has been causing us problems.

Right after we press the run button, before a progress bar window opens up showing that the cRIO is recieving the download and that LabVIEW is deploying, we get this error message in a small window that pops up:

"Error -44085 occured at FPGA Bit File has incorrect version or revision.

This error code is undefined. No one has provided a discription for this code, or you might have wired a number that is not an error code to the error code input."

(there are buttons for "Continue", "Stop", and "Why not found". This is what the error is word for word.)

This seems to be the "root" error that always comes up first. Sometimes various amounts of other errors come up right afterwards, each of which opens up the internal vi that has the problem. One of them is usually one that says that there has been a problem with connecting with the camera. A couple other ones that sometimes come up say that there has been communication errors connecting to the cRIO. We have hit continue on all of these errors an typically more errors and VIs come up. If we press stop though, sometimes the same amount of errors and VIs come. We have recently experienced where with one Basic Framework main VI, everything had run smoothly. But with another one that we were doing something else with, it would bring up these VIs. Sometimes we would shut off everything for a long time (a day inbetween meetings) and when we came back it worked. It would typically resurface elswhere some other time. It would usually happen the first time we wanted to run the VI and then go away later sometimes.

Any first impressions or further questions to ask me? Help would be appreciated. Thanks!

[sciencewhiz]

Are you running the latest cRIO image?

[LabViewEnthusiast]

Yes, I'm pretty sure that we're using an updated image. I haven't checked and we have never re-imaged the cRIO to try and solve this problem, though. We updated and all that without a hitch on Dec. 18, one week before the kickoff. (we signed up to get the control system early). I have never heard that there has been a new one released since then and I usually stay on top of those things.

[sciencewhiz]

There's been one LabVIEW update since then, which included a new image. I'd definetly try installing that and imaging and seeing if you still have a problem.

[sciencewhiz]

Is this still an issue? Note that update 3 has come out.

One more thing that can cause this is if you are deploying anything other then your Robot Main VI.

[LabViewEnthusiast]

Hi everyone, thanks for the help. Sorry that I haven't replied in a while.

We have not installed a new update yet, which I think might be it. We were using some vis, subvis, and copied block diagram from the Two Color Servo Control VI and other examples, so maybe those were using some code that was an update ahead of what we have. I think that we have update 2 from NI, don't know about the other stuff. So far everything is going fine, we haven't been using the vi that just recently got that problem, but we will be in a pickle if that happens to our main robot project!

EDIT: Now I see that there was a new one released. Ok, I never knew that there was a new update. I will check that out.

Thanks! I'll post with results soon, hopefully.

[Adria]

I am experiencing the same error....did you get any resolution? One of the application engineers told me that the error was due to loading a project that created before an update was installed and the processor reimaged. But I loaded update 3a last night, reimaged my processor at that time and created a new project this morning....so I'm not following that.

Anyone know anything about this?

THanks!!!

[LabViewEnthusiast]

No, we haven't installed update 3 yet. (sorry!) We haven't had any problem with this error right now actually because (thankfully) our main program isn't getting the error. But if we ran that one program that does, I'm sure it would still have that issue.

[#9]

Do try installing the update and post back. That way if it still doesn't work we will look into further!!

[LabViewEnthusiast]

Alright, we've got a reasonably strong solution to the error that kept comming up when deploying!

We got the update and put that all on and updated everything. Seperate problems arose because sometimes we did the sequence out of order or missed a step. Remember to follow the steps whenever you do that! But, actually, the update did not solve the problem. It might have helped a little bit, but after it was updated the error still came (by the way, our main program started getting this error so we were really in a pickle).

Here's the deal: we suspect the problem was with how the VIs and projects were opened and saved. Doing it the wrong way will mess up something in the VI/project and it will then get this error.

Here's what you should do:

1. Open up the project by going to its file location and double clicking on it

2. Open up the Main VI/whatever one you want by double clicking in the project window

Here's what you should not do:

-Open up the Main VI/whatever by double clicking on the file location on your computer (instead of the project window), or

-Open up the project/Main VI/whatever from the Getting Started screen in LabVIEW, or

-Save the VI/project after doing these "no-no" actions (I think that this is true. It might still be messed up if you just open it up wrong, even if you don't save it.*)

Doing any of these wrong actions seems to screw up the framework or something deep within the programming. *I don't know if a "corrupted" VI/project will still work if you open it up in the correct way, but ours works now. We actually have not tried it out in full yet, but when we click on the run button, we don't get the "Death Error" (which we have nicknamed it) and the normal progress bar comes up. It actually tries to get a connection with the cRIO after that, as it wasn't connected, but the Death Error didn't come when it would have, so we consider it good to go. I will ask the lead programmer of our team that figured out the solution what specifically he did to solve it. If I remember correctly, he didn't do anything; he just opened it up in the correct way.

Also, one other side note: we were having problems with the update when we tried to run a program and later realized that we had forgotten to set the team number. We set the team number, but then we were not able to switch from disabled to enabled. The fix to this reqired updating the driver station all over again and setting the team number right after we updated the driver station. So just to let people know, even though it doesn't really relate.

Hope that helps! Thanks for everyone's advice!