Weird c-RIO issues

[exprg:melonhead]

Today, we tried to run our robot, so I deployed the code, and hit enable. Everything seemed to be working well until our robot enabled with motors in full reverse and ran into me. We hit the stop button and did everything to stop the robot.

Our problem comes after that moment. After this incident, our developing computer cannot connect to the c-RIO. Our 2go computer seems to not have an issue, due to the green light on dashboard saying it's connected. We have tried hard wiring to the bridge and to the c-RIO but nothing makes it work any better. Has anybody else had this problem? If any body has any ideas as to what we can do, that would be greatly appreciated to know.

[Alan Anderson]

Double-check your IP addresses.

See if the cRIO Imaging Utility on the development computer can find the cRIO.

What programming language are you using? How are you telling the computer to "connect to" the cRIO?

[Cecil]

After you hit the stop button, did you physically turn off the robot and turn it back on? It takes a full reboot of the controller once the stop button has been hit to re-enable it.

[exprg:melonhead]

We did restart the robot And the computer. That did not help. I did not try checking the address due to time, but it was able to connect just before. Its worth checking out.

[mgurgol]

We were seeing a few weird issues with the c-Rio last night. When trying to run Labview, we were getting a "target in use by another..", and would not continue. The PC was, however, able to see the cRio in the cRio imaging tool.

We had been running fine up until then. We tried closing the project, closing Labview, and even rebooting the machine to no avail.

We tried the same thing on our second programming PC and received the same message. The only way we found to correct the issue was to reboot the driver station. (By process of elimination, there were only two computers involved in the process, the programming PC and the Driver station).

Has anyone else seen this type of issue

[exprg:melonhead]

Also, I'm using labview and connecting by pushing the deploy button. Probably not the technical term

[Joe Ross]

Originally Posted by mgurgol

We were seeing a few weird issues with the c-Rio last night. When trying to run Labview, we were getting a "target in use by another..", and would not continue.

We fix that by rebooting the robot.

[exprg:melonhead]

If I remember right, rebooting only works if you haven't built yet. We don't build the project on the c-Rio until it is finished. Otherwise you need to override the built project. It ended up being a mess for us

[Mark McLeod]

If you use the RUN button to execute your code on the robot, then even after you stop, LabVIEW maintains a connection to the robot for that particular project.
That will cause it to lock out other projects and other LabVIEW development machines.

Usually, the simple answer is to use Disconnect--Right-click in the Project Explorer window on "RT CompactRIO Target(10.xx.yy.02)" and choose Disconnect. If it's grayed out, then a different project or machine is the culprit.
Sometimes you also have to reboot the robot to shake the connection.
It sounds like you may have several machines/projects contending for the cRIO.

[exprg:melonhead]

After redoing the IP addresses (the computer somehow lost the robot IP address) it worked for only one run. I don't know if this offers any clues, but after the developer computer disconnected, it still had the c-RIO in it's registry. I was lost before, but this really confuses me now