Connection problem

[whcirobotics]

Hi CD, we are having some connection problems...again. I have once came to resolve the problem as seen in this thread: http://www.chiefdelphi.com/forums/sh...ad.php?t=87873, but we upgraded everything to 2011 and using the old router, (will connect the new router tomorrow) and we got the same connection problems as posted below in the picutre. Please help, this is causing a lot of trouble because we are unable to deploy the code. We are trying to deploy the basic code they have provided. With a little change of things with, the aracde drive changed to holonomic cartestian drive.

Please help
Whcirobotics

[Mark McLeod]

The first error could be similar to the problem you experienced before. Use the System Manager to see what your CPU usage is on the cRIO.

That second error just means LabVIEW already has the connection to the cRIO locked up usually by another project. Even though you stop a Run or even reboot the cRIO, a record of the connection is preserved by the project.

You can fix that by right-clicking in the Project Explorer window on "RT CompactRIO Target(10.xx.yy.02)" and choosing Disconnect.

You can also clear that up by closing the project. When you close the project that had the connection locked up you'll get a message asking if you really want to disconnect. That way you'll know which one was doing it.

[MrForbes]

We were able to get our robot driving with the new software and the new bridge, no router needed. But we plugged in the tether cable to load the robot code onto the robot.

I don't know if that's how it's supposed to be...but it seems to work.

[jhersh]

Originally Posted by squirrel

We were able to get our robot driving with the new software and the new bridge, no router needed. But we plugged in the tether cable to load the robot code onto the robot.

I don't know if that's how it's supposed to be...but it seems to work.

That perfectly acceptable, but it's not necessary.

[MrForbes]

From my experiences with networks over the years, it makes sense to me that you'd want to do something like loading code with a wired network. And you usually want to operate the robot with the wireless network.

But I'm weird.

[whcirobotics]

@Mark
It is the direct code that comes with the default framework in Labview, so i doubt it is the same problem as before, but i will do the usuage thing and check after school at 3:05 and reply back

@squirrel
It makes sense to do it wired but the wire goes only so long. Althought both are good, wired or wireless, i cannot deploy the code using either way. :S

[Mark McLeod]

Check the CPU usage first so you know what's happening there.

I assume that after you reimaged the cRIO with the 2011 v25 that you didn't download any robot code?
So there shouldn't be anything running on the cRIO and the CPU usage should be close to the bottom.

Does the timeout message stay up for a long time? It's normal to see it occasionally and it'll usually go away within 20 seconds or so.

Here is something else to try after school for the timeout error you're seeing:

• Flip the NO-APP DIP switch on the cRIO and reboot it (reset button or cycle the power), then turn the NO-APP switch off again.
• Then try the Run button.