The gotWifi check in the WD FSW seems to pass even if wifi is not connected (though it seems like it might work when booting directly into MISSION / EnteringMission from persistence...
Low priority b/c this doesn't really affect any mission parameters directly or indirectly (since Herc no longer cares if it comes up after the Radio). That said, don't just blindly remove this 25s delay since we've only tested wifi with it present (so it might matter that currently Herc is coming up after the Radio - though it shouldn't...). Basically, any config changes are bad at this stage (post-RC6).
NOTE: A fix for this isn't very important. This Issue is mainly just for documentation of a non-conformance.
The
gotWifi
check in the WD FSW seems to pass even if wifi is not connected (though it seems like it might work when booting directly intoMISSION
/EnteringMission
from persistence...Low priority b/c this doesn't really affect any mission parameters directly or indirectly (since Herc no longer cares if it comes up after the Radio). That said, don't just blindly remove this 25s delay since we've only tested wifi with it present (so it might matter that currently Herc is coming up after the Radio - though it shouldn't...). Basically, any config changes are bad at this stage (post-RC6).
NOTE: A fix for this isn't very important. This Issue is mainly just for documentation of a non-conformance.