Panadapter with No info

We have a defect entered for this behavior.  What we suspect is happening is that when a client connects to a radio, one of the processes it goes through is to restore the previous radio operating state.  This process takes into account any band persistence and any previously loaded profiles to recreate the pandapter and slice configurations. There are a lot of things happening the forst time a client connects to the radio and what we suspect is a race condition occurs where a dependent process has not finished before the software tries to create the slice receiver(s).  Since the dependency does not yet exist, the creation of the slice receiver(s) fails.

As has been noted, slow connections between the radio and the client can exacerbate the race condition.  And simply reloading a new profile once the initial restoration of the previous radio state fails will succeed.

Hopefully, we'll be able to identify exactly what is responsible for the race condition and add the appropriate wait states in the start-up logic to prevent this from happening in the future.