Quote:
Originally Posted by Greg McKaskle
Can you go through what does work on the dlink and when things don't work, what are the errors or diagnostics.
|
When we tried using the DLink in bridge mode after replacing the cRIO (which had experienced "the event") it was unable to communicate to the laptop or to the driverstation. Driverstation indicated no communication.
Quote:
Originally Posted by Greg McKaskle
For example, it sounds like the cRIO wired to the dlink and laptops wired to the dlink will be able to program and enable, correct?
|
YES! well... to clarify, we have not done any programming, etc. directly plugged in because it was working using the old bridge so we have been using that configuration to continue our programming, testing, driving, etc. However, when we are directly plugged into the DLink we are able to both ping and use the netconsole to communicate the cRIO.
Quote:
Originally Posted by Greg McKaskle
Next, describe the configuration of the dlink wifi and the config of the laptop trying to communicate with it. Finally, can you ping the cRIO, the dlink?
|
Using the laptop we tried using the netconsole display to see if we could talk to the cRIO with no response. We also tried pinging both the DLink (10.x.x.1) and the cRIO (10.x.x.2) from the command prompt on the laptop (going through our wireless router) and we were able to ping the DLink but not the cRIO. We also tried pinging the cRIO from our wireless router diagnostics with out success.
As far as configuration:
- DLink: we followed the instructions on the "How to configure your Radio"; IP address= 10.2.30.1, mask= 255.0.0.0, gateway= 10.2.30.4. It was also tried as programmed from the competition kiosk with the WPA-key removed.
- Laptop: is configured without any security on the wireless; IP address= 10.2.30.6, mask=255.0.0.0, gateway= 10.2.30.4
- Router: IP address = 10.2.30.4, mask=255.0.0.0
- driverstation: IP address = 10.2.30.5
Just to reiterate... we were able to run the system from end to end (ie. laptop and driverstation to router to bridge to cRIO) successfully using last year's bridge. Also we have been trying to test using the 2 DLinks, one as an access point and one as a bridge...with the same results. Using this configuration we were able to get 2 laptops on each end of the setup (ie. laptop-accesspoint-bridge-laptop) to see eachother, but when one laptop was replaced with the cRIO the laptop could not see it. [Note that the removed laptop had been configured to have the same IP address as the cRIO, 10.2.30.2]
Any thoughts on whether upgrading the firmware on the DLink (from 1.2.1 to 1.3.1) might be helpful?