Log in

View Full Version : Failed comms to cRIO

Zuelu562
13-01-2012, 10:46
So here's our situation. CRIO is fully imaged, DS is updated to version 11.30.11. We have attempted to connect via the port 1 on the cRIO and through our D-Link.

Crazy Part begins here:
We are able to ping both the cRIO and the D-Link, but we are not getting Robot comms (although the "Robot" light is on in the driver station).

We are thinking it's the D-Link (when I reset the D-Link, wireless setup page is blank, and there is option to set it up manually either). Have we missed a firmware update?

Also, last years robot (which for the time being, our control board has not changed) was driving the week of Christmas.
bdbayes
13-01-2012, 11:03
What programming language are you using?

Are you saying that it says that the robot is connected via the driver station?
If so, does it show that you have code loaded?

After last year at competition, we found that the abilities to edit the configuration on the D-LINK were limited. We have yet to solve this problem.
Zuelu562
13-01-2012, 12:06
We are coding in C++ via Windriver. The main part of the driver station says we have no comms (and therefore, the robot code light can't light up) yet, we can ping the robot and the D-Link.
bdbayes
13-01-2012, 14:54
Can you try wiring directly into the cRIO and then deploying your code?

Can you then try to connect with the driver station application?
RufflesRidge
13-01-2012, 14:57
Also, last years robot (which for the time being, our control board has not changed) was driving the week of Christmas.

It needs to. The module order has been shuffled around. See page 23 of the C++ Getting Started Guide.
Mark McLeod
13-01-2012, 15:12
(when I reset the D-Link, wireless setup page is blank, and there is option to set it up manually either). Have we missed a firmware update?

You are using an incompatible web browser. That's what gives a blank wireless page.
Try it with IE.
bdbayes
13-01-2012, 17:34
Since the cRIO II is now among the valid options this year, they have changed the order of the modules to accommodate fewer modules. Even if you are using original cRIO, you need to correct the order of the modules before reimaging the cRIO.

It needs to. The module order has been shuffled around. See page 23 of the C++ Getting Started Guide.