connectivity problems?

[AgataSays]

I'm not sure if there has been a forum topic on this yet or not, but team 3553 has been having a connectivity problem with our cRIO, basically: we've been having sporadic connectivity problems with the cRIO both wirelessly and through ethernet.

The ways we've tried to download the code (Labview) have included using the crossover directly from the CM to the cRIO, as well as wirelessly through the settings directions given through the FIRST website.

Troubleshooting:
1. re-imaging the cRIO- same problems- but it was sporadically connecting when connecting with the crossover, that is sometimes it worked and sometimes it didn't - that is, we tried all combinations of resetting the cRIO, powering off, restarting the comp, etc..
2. resetting the dlink- could not configure to new settings- it froze whenever we tried to save settings when set to AP- and when set to Bridge it didn't show us the full menu.
3. changing computers- tried using a different PC to save the settings on the dlink, same problem- wouldn't save.
4. re-imaging the Classmate- after re-imaged, we had the same problems with not being able to communicate.

what else can we try? is it something with the dlink?

[rsisk]

do you have 2.27.11 on your computer and v28 or v29 on the cRIO?

Power connections tight on the cRIO?

All other network connections turned off on the computer?

Those are some things I can think of off the top of my head.

[WizenedEE]

Many of our connectivity problems were due to an unrestricted while loop. Try uploading some blank code (the default stuff), and if that works check for loops that don't have any delay inside them.

Also remember that after reimaging the classmate you have to reinstall the driver station, utility, and labview updates (available on usfirst.org/frc/kitofparts). Is your version of labview on update 3.2?

[Mark McLeod]

Originally Posted by AgataSays

resetting the dlink- could not configure to new settings- it froze whenever we tried to save settings when set to AP- and when set to Bridge it didn't show us the full menu.

By this surface description it sounds like what you'd normally experience.

Whenever you browse to the DLink, then change the DLink IP address it will appear to freeze and be unreachable.
That's only because the browser is still trying to browse to the old IP address and in addition your PC and the DLink suddenly no longer share common network addresses.

After the DLink address is changed, ignore what the browser is doing, it will never come back. Change your PC IP address to be compatible with the new DLink IP address, then browse to the new DLink IP address.


A separate problem is when browsing to the DLink doesn't show the full menu expected. That's usually due to the browser you attempted to use. Only IE works fully with the DLink, not Firefox or some others. The symptom is when you see the outer frame, but the central menu is only white space.

There is also a less common issue when the DLink firmware gets reset when improperly using the reset button on the DLink, but there's a particular error message for that.