Problem connecting to the CRIO

[silas13579]

Originally Posted by Zmarken

Looking further through the that website, under "Diagnostics Tab", it says

So, a couple of things I can think of... Does the 44002 warning change between and anything else?

The radio signal flashes between good and bad. Also when we try to deploy code without rebooting the crio since the last attempt we get this error: Access denied: Another project is using this target. You must disconnect the existing project from the target or restart the target before establishing a new connection. Note: The existing project may be running on a different host computer.

[silas13579]

So far, connecting directly to the CRIO actually has been working, so we're just going off of that right now. The bridge config utility isn't working on our radio. It says login failed.

[Zmarken]

Originally Posted by silas13579

So far, connecting directly to the CRIO actually has been working, so we're just going off of that right now. The bridge config utility isn't working on our radio. It says login failed.

If deploying directly through the cRIO is working, then I'm pretty sure it's a router issue.

I'd say you should do a factory reset of the router, then go through the Bridge Configuration tool again. If you're using the router in the KoP, reset it by holding down the reset button in the back of the router for ~10 seconds.

Try that, and see what your results are.

[Invictus3593]

Originally Posted by silas13579

...When we try to deploy code without rebooting the crio since the last attempt we get this error: Access denied: Another project is using this target.

Rebooting the crio should work, but you'll have to redeploy your code. Are you trying to use more than one computer or robot project?

The bridge config utility isn't working on our radio. It says login failed.

Have you tried resetting the radio fron the button in the back?

[silas13579]

We have tried the reset button, however it is not working. Also, connecting to the CRIO directly failed yesterday. Towards the end of deploy, when it's mostly through our global variables library, it stops.

[Greg McKaskle]

When it stops, there is typically a dialog on the screen explaining what succeeded and what failed. Can you copy/paste or take a screenshot so that we can help interpret what failed?

Greg McKaskle

[silas13579]

The only response we get is when we are trying to connect, it will say Waiting for response from Real time Target (I forget the exact wording). When we reimage the Crio, or at the beginning of meetings, is when it seems to work the most often. Our head mentor (we don't have any actual programming mentors) said that maybe our code bugs up the CRIO image when it deploys? Also, though our electrical team said it should be irrelevant, the analog card(I think. It's whatever shows the voltage) is not in the CRIO.

[Greg McKaskle]

The HW team is correct. The DS voltage will be incorrect, and you will need the module and breakout and jumper in order to pass inspection, but you don't need it right now.

My suspicion is that you have a great deal of Diagnostic errors being reported at the DS. If you can change the mode of the robot at the DS, you may find that one of the modes produces less errors and will have a better shot of deploying. If you fix the code issues that are causing the errors, the deploy issue will go away.

Also, you do not need to reimage the cRIO -- almost ever. Teams do this all the time, and I'm not sure why. The file system is very robust, and if not corrupt, why do it? You may sometimes need to turn on a setting such as the no-app switch or change the CAN or other settings.

Greg McKaskle

[silas13579]

Well the reimaging of the CRIO seemed to help. We just tried deploying a default robot project, and the CRIO was still not accepting it. Then we switched to our practice bot, with a different CRIO and a different ethernet and tried deploying our code, which didn't work, and then tried deploying a default project onto that, and that too did not work. They both were stuck in the same "waiting for the target (RT CompactRIO target) to respond."

[Mark McLeod]

Reimaging the cRIO works (in a brute force kind of way), because as a side effect it wipes out your user code that is responsible for the problem.

The No App switch (a DIP switch on the 8-slot or for the 4-slot virtual through the cRIO Imaging Tool) disables your user code when the cRIO is reset and is quicker.

[Greg McKaskle]

Exactly. And once the errors on the diagnostic screen are fixed, neither will be necessary. Until they are fixed, don't Run as Startup, use the run button instead.

Greg McKaskle

[silas13579]

Alright so I'm getting confused now. What is the diagnostics screen? The part of the driver station? Because I'm not sure how it may be in our code, seeing as the default robot project didn't deploy either.

[Mark McLeod]

It's not the code you are deploying. It's the code already running on the cRIO from the previous deploy.

The Diagnostics tab on the Driver Station has a message window.
There are a lot of warnings that can obscure the real error messages, so copying and pasting all of them into a text file makes them a lot easier to look through.

You can also look at the Driver Station log from the Charts tab, in the lower right is "Launch Viewer."
You have to pick the latest log or two by date, then look at the Event List tab for error messages.

[silas13579]

I'm pretty sure I found the error. We were kind of recycling last years code, and last year they had nothing in finish.vi, so this year we assumed that we could go the same. Would this have been causing the problem? I'm in the middle of fixing it right now, so I can update with whether it works.

[silas13579]

Nope never mind it's still not working. We have tested deploying quite a bit today, and it seems to work after we flash it until the first time we perma deploy onto the robot, which then causes every attempt after that first perma deploy to fail, until we flash it again. It also occasionally gives this error: Access denied: Another project is using this target. You must disconnect the existing project from the target or restart the target before establishing a new connection. Note: The existing project may be running on a different host computer.