Quote:
Originally Posted by Alan Anderson
I don't think I ever saw one take more than 60 seconds. 45-50 seconds was more typical. The rest of the delay some people are noticing is from the Driver Station sometimes taking upwards of 20 seconds to establish communication once the network connection is there. That appears to be a Windows networking thing.
It's my understanding that the bulk of the OM5-AP bootup time is in loading and initializing the built-in web server interface to the device settings. If that were removed from the firmware package, it could probably boot in less than 30 seconds. It would also take away a lot of flexibility for teams to tweak their network setup.
Given a couple of years with the same radio, I expect that the bootup time could be drastically slashed while providing teams with the appropriate tools to configure the device. That's probably not going to happen this year, though.
|
Correct me if I'm wrong, but doesn't the competition image use different firmware than the home use version? In that case, why don't you include the web UI on the home versions, but not a competition ready version? I don't believe you're legally allowed to change the competition firmware. I also don't believe anyone's complaining about the speed at home.