The next step would be to get some snapshots of what the OS thinks it has connected and probably to split it into 2 threads, 1 for Windows and 1 for Linux.
Get the QDX working OK and then capture the output of lsusb -vt to start with. Then once it starts misbehaving, run lsusb again to see if the devices have disappeared or changed enumeration.? Likewise USBTreeView can be used on WIndows to check the connected
device states and see if they change. It would be enlightening to see if when you get the state that a 1 minute power down doesn't recover the QDX, to see if the OS view of the devices matches the working state. I'm guessing it will not.
A logical approach to identifying and removing known USB snags and then observing the results before trying the next fix is the only way to resolve this kind of issue. And yes, it is a slow, boring and tedious process.
73
Andy
toggle quoted message
Show quoted text
On Tue, Nov 16, 2021 at 11:15 AM, Ben wrote:
Great tip though! I'll let JS8Call run for some time into a dummy load to see what happens.
Unfortunately disabling USB auto suspend did not solve it for me. After a while the RX audio level was zero, JS8Call was in TX mode but the QDX not. And the audio and RF filter sweep looked as below. Keep the tips coming though :)
- A 1 minute power down did not help, same weird sweep output.
- A second 1 minute power down did help! Filter sweeps looking OK now.
Besides hunting down this problem I had a nice QSO with someone in France this morning, so I'm going to have a bit of QDX fun now :-)
73, Ben
PA2ST
Audio filter sweep in the fault state
RF filter sweep in the fault state
