Quote:
Originally Posted by Mike Wittman
The simple answer is after you set up your network ip addresses power cycle everything in order. I don't know why but sometimes the IP address doesn't take until you power cycle the router and bridge.
This is the power cycle order
1 Router
2 Driver station (wait until it boots up) then go to step 3
3 cRIO
4 power up the wireless bridge
|
Our team has similar issues with the driver station getting stuck in No-Comm mode. We have the router and the driver station on the same power strip.
So we do a similar power cycle if stuck in the No-Comm loop.
1 Router/DS (power strip)
2 cRIO / wireless bridge (main battery switch)
Most of the time the communication works slowly but surely. The No-comm failures are small but it could be annoying if teams have to wait a minute for the system to startup and then possibly have to power cycle.
We are using Update 2.0 default code with 802.11b/g (because we don't have N laptops )