it takes time to recive communication after rebooting .. why ?????????
 

hi
i just was wondering if i should restart the classmate whenever i reboot the roboot in order to get communication .. because if i don't i don't get anything .. which doesn't seem resonable since it takes too much time concediring that we don't have the time to do it everytime at the competition .. right ????????

Re: it takes time to recive communication after rebooting .. why ?????????
 

You dont need to reboot the classmate when rebooting the cRIO. The cRIO will reboot and re-initiate communications with the classmate automatically. It takes time. If you powered off the robot, then the bridge (WGA600N/WET610N) has to reboot too, and takes around 30 seconds to authenticate with the network and so on, and the cRIO takes another 30 seconds or so to come online once the bridge is up.

Re: it takes time to recive communication after rebooting .. why ?????????
 

or do it faster by pushing the reset button on the crio (between dip switches and serial port) or clicking reboot robot in the lower right corner of the diagnostic tab of the DS

Re: it takes time to recive communication after rebooting .. why ?????????
 

be careful pushing the reset switch on the crio, we had one break on us last year

Re: it takes time to recive communication after rebooting .. why ?????????
 

If you're doing a "cold" boot of the robot, there's a condition where the DS/cRIO link may not work(Essentially the bridge doesn't boot fast enough to pick up the cRio's announcement that it is online, and as a result, refuses to relay messages to the cRio because it doesn't think anything is connected).

Rebooting your Classmate will solve the problem, because it will cause the classmate to ask the cRio to re-send its announcement. However, a quicker way to accomplish the same thing is to reset the cRio without powering down the bridge. The bridge will then be able to discover the cRio and connect it to the DS.

Re: it takes time to recive communication after rebooting .. why ?????????
 

Actually, the newest update resolves this problem.

It is mandatory to have the latest updates on both the DS and the cRIO, so make sure you visit that page if you haven't already.

Re: it takes time to recive communication after rebooting .. why ?????????
 

I'm confused by what you mean here. If you mean out on the field during the matches, there's ample time while they're setting up the course for your match to make sure that your robot is turned on, booted up, and has good comms. In fact, they don't start the match until this is true for all six teams in the match.

If you mean in the pits while debugging, 30 seconds isn't that awful. You can always run debug mode if you need to test things faster.

Re: it takes time to recive communication after rebooting .. why ?????????
 

In the pits its irrelevant and almost instantaneous, thanks to wired lan and taking the bridge out of the equation.

Re: it takes time to recive communication after rebooting .. why ?????????
 

You definitely don't need to power cycle the robot every time you want to update your code. Just press the reset button on the cRIO. If you power cycle, it'll take about 60 seconds for you to get comm back. If you just reset the cRIO, it shouldn't take more than 15 or 20 seconds.
EDIT: And if you restart the Classmate every time you update, it'll probably take closer to two or three minutes by the time it shuts down, reboots, and gets comm back.

Re: it takes time to recive communication after rebooting .. why ?????????
 

Each team should set their own procedure, but within the lab, we leave classmates going for weeks connected in various ways to cRIOs. A restart should not be necessary under normal use. It may be necessary to restart the DS, particularly when leaving a field after a competition, but it is just a program. Exit, and log back into the DS.

Greg McKaskle

Re: it takes time to recive communication after rebooting .. why ?????????
 

I reset the crio and that takes around 15 seconds