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.
|
I hadn't taken that into account, mine was from when the robot stops moving to when the DS can move it successfully. Just for the sake of clarity, my total seems a bit larger, though roughly similar to the numbers you've seen. I wasn't exactly counting, it was during me watching a match I saw it happen and got my numbers, so take it with a grain of salt.
Though this is just my two cents, but if the device prioritized services (DHCP & Routing) above the webGUI, it'd help boot times, though this might be totally contrary to the way OpenMesh has the device configured.