|
Re: cRIO requires independent restart from the robot to connect
This should be resolved in the latest DS update.
The root issue is that the cIO and other robot devices are booting in parallel and may bring up their network communications at different times. When the cRIO finishes booting before the wifi bridge does, the bridge doesn't know how to route the DS control packets to the cRIO. The updated DS detects that the robot is not responding and send out an arp reset. This causes the router to rebuild its tables and learn how to route to the cRIO.
The update was just recently made available on the ni.com/first site. I assume an official announcement will go out early next week.
Greg McKaskle
|