This is a bit of a problem. The first time this is run there is a race condition where the board hasn't been registered before the ActuatorSettings UAVO is written. So this check leads to a situation where the spin box maximum values are not correctly set. 

Short of adding a signal to the board manager to emit when the board is detected, are there any better ways of dealing with this problem?