Startup behvavoir

Wayne

I have made an observation:

This is without an Internet connection to the LAN.

My 6400M when starting up attempts to startup in the same way it was last running. In other words if I was running Standalone  it attempts to startup standalone (going directly to the panadapter/slice display not asking for version), and if I was running SmartSdr for Windows by a computer connected via the LAN when I shut down it attempts to startup by looking for the computer it was previously connected to prior to being shutdown.

A second observation (which only occurs if I was last running smartsdr for windows on my computer) is that if this startup fails to find the previous way it was operating(for example my computer running smartsdr this time is Off) then it shows a Please Wait .... on the display while it tries to startup in the same situation it was shutdown last, and appears to be blind to any other way to startup (at least for over 5 minutes)

A shutdown and restart after this Please Wait ... display causes the 6400M to realize hey maybe the last successful startup is not the way I need to startup this time, so now I will look and ask the loose nut (me) behind the touch screen how I should start this time. (So I press connect and we do the Standalone startup thing)

Additional Detail Added:

The second observation is if the last successful startup was completed standalone and this time I have my computer and smartsdr for windows running when the 6400M was powered up then it connects to Smartsdr for windows.

This is an observation only not a criticism and I am looking merely to understand and for confirmation from Tim that indeed this is the behavior the M series is meant to exhibit.

Eric-KE5DTO

Thanks for bringing this up.  There are several issues that we have found in the startup process for the M models.  The net result is that the startup behavior is unpredictable in v2.1.32 and v2.1.33.  We have a fix in Alpha test now that should help to address this behavior and make it more predictable.

Specifically, if the radio is not in use and there are no new versions available, an M model should always start up and go straight to the Panadapter screen (no connect screen).  If it is in use, it should start at the Connect screen showing the radio as in use (and give the option to disconnect the current user).  Look for these changes in an upcoming public release.  For reference, this is being tracked as #5994.

Wayne

I didn't mean to bring this to a spotlight. My intention was only to understand how the startup sequenced consistently so I could establish set startup procedures based upon how I wanted to operate and connect with the 6400M.

When the Please Wait... screen appeared due to my computer background I knew it was related to the unit seeking some type of network connectivity. Network connectivity slows or stops any hardware when it is actively seeking a connection and for whatever reason the cable is connected but the connection activity is not.

The startup in my view does not have to change, what has to happen is transparency in that the flowchart of the startup sequence be published in the documentation for access by all owners and users. Once that is done and if the flowchart sequence is properly detailed then owners and operators can taylor their individual interface and hardware startup to solicit the correct startup desired based upon the startup flowchart sequence.

You cannot please all the people all the time, and continuing to throw money and time at something that may have no issues but just needs to be understood due the vast differences in the end users desires and equipment application are non-productive, when transparency of startup may resolve the confusion and comments.

Sorry, I'll get off my soapbox ....

I will continue to try to figure out what the consistent startup sequence is for now, at least until it gets changed and I have to figure it out again.