CRIO taking progressively longer to boot
 

We've started running into an issue recently where the reboot of the rio is taking progressively longer.

In the beginning, it would take 9-12s fairly reliably. Over the course of a few hours and many reboots/code updates, we noticed it was up to 20s, then 40s, then 90s, then over 120s.

We flashed the rio using the imager and it was right back to 9-12s, but has since been slowing down on subsequent boots again.

This is the booting time before any of our code gets a chance to run so it doesn't seem like it could be our on robot code.

Has anyone run into this before and/or has any theories on what could be doing it?

Thanks --

Re: CRIO taking progressively longer to boot
 

We started getting the exact same issue on our competition robot. I haven't tried reimaging the cRIO yet, but I'll try that to see if it works for us as well.

The strange part is that it's been working for most of the season for us on our prototype robot.
(We started doing something weird with putting lots of log files on the robot, but I doubt that would increase boot time like this.)

I'll see if I can find any settings changing on the cRIO between reboots.
Any idea if this increases each time the robot reboots, or each time the code is downloaded?

Re: CRIO taking progressively longer to boot
 

Do you have a anything saving files to the cRIO? When we leave some of our log files on the cRIO and they start to build up we notice longer boot times.

Re: CRIO taking progressively longer to boot
 

We had the exact same thing. Big log files apparently do this. Probably because of the cRIO using a cache of some sort.

Re: CRIO taking progressively longer to boot
 

We have seen this issue (long reboots) as well.

We write files to the cRIO, but we tried deleting them all once and rebooting - still had the issue.

Re: CRIO taking progressively longer to boot
 

I know of an issue with the file system performance related to having hundreds of files in the same directory. I wasn't aware of big log files causing anything like this. It may be worth moving the files around to different folders. I didn't bring a cRIO home to test.

Greg McKaskle