开云体育

On 29/01/2025 20:38, Carl Willis (KF4KIG) via groups.io wrote:

Whenever I reboot the mini PC, with the QMX+ remaining powered, I lose USB connectivity to the QMX+.

Carl,

Unfortunately this is normal.
The QDX/QMX will only enumerate once then require a power cycle.
Hans knows this but does not know how to correct it.

A possibility is to trigger a relay when the computer starts up. I'm sure it could be done but to my knowledge this has not been discussed.

73 Alan G4ZFQ

On 29/01/2025 22:34, Carl Willis (KF4KIG) via groups.io wrote:

Regarding the relay idea, how would this work?? Interrupting supply power to the QMX+ probably just turns it off, in which state it remains unless the power button is pressed (is this correct?).

Carl,

I was thinking of a QDX which does come up instantly.
I'm not sure about the QDM. Does it just need the power button press?

As I said, I've not thought about the details. A little routine run at startup could trigger some circuitry, maybe from a COM port.

Jon,

I had thought it was a problem with Windows but I'm sure Linux users have reported it as well.
I have it with a QDX and a RPi.

73 Alan G4ZFQ

On 29/01/2025 21:34, Alan G4ZFQ via groups.io wrote:

Hans knows this but does not know how to correct it.

It's all to do with how one of the registers is programmed that is used to detect connections/disconnections and the fact the Windows and Linux handle these differently.

On the QDX, device firmware update mode correctly works without power cycles and it's normal mode that fails. I did work on diagnosing some the issues for Hans, there's a QDX he sent me here.

The problem was not how to fix the code but that Hans told me the area of Flash memory that held the code was really just about full so changing the code would be a really challenging job. There will also be an issue of job priorities as well as I'm sure everyone screaming for SSB would be happy and prepared for that to pushed back so this minor irritation can be addressed.

Andy

On 30/01/2025 09:00, Andy via groups.io wrote:

The problem was not how to fix the code

OK, Thanks for the update Andy.

But is it a Windows-only problem?

My QDX on my RPi needed a power cycle today.

73 Alan G4ZFQ

On 30/01/2025 16:00, Alan G4ZFQ via groups.io wrote:

But is it a Windows-only problem?

Yes, as Linux and QDX et al. happily work under the same sequences of events that do not work for Windows. And it's repeatable time after time.

My QDX on my RPi needed a power cycle today.

A single unexplainable event. Are you sure it wasn't an extraneous cosmic ray that flipped a few bits in the QDX and / or Pi guts?

On 30/01/2025 22:09, Andy via groups.io wrote:

A single unexplainable event. Are you sure it wasn't an extraneous cosmic ray that flipped a few bits in the QDX and / or Pi guts?

Andy,

Looks like I was jumping to a wrong conclusion.

The QDX sits on the untidy bench of my "workshop" 100% RXTX on 6m WSPR.
From time to time, it can be weeks, I realise it has stopped and see the WSJT-X " Do you want to configure?"
It does not see the QDX until I power cycle it.

However, as you say the simple pull/ replace USB test shows no problem.
It looks like something else I do in the workshop triggers the cosmic ray.
Or, maybe RF gets in the USB when I do something..

73 Alan G4ZFQ

On 31/01/2025 10:08, Alan G4ZFQ via groups.io wrote:

Looks like I was jumping to a wrong conclusion.

I thought as much ;-)

There could be lots of things but RF getting in where it shouldn't would be the first thing I check for.

Andy