I’m travelling through the end of the month and don’t have W10 with me, but I have W11 and Digirig with Attenuator not activated. With nothing connected and sensitivity at 75 I get nothing on the level indicator. With sensitivity 100 it picks up single decibels.
Here’s driver info:
Well, when I posted this screenshot previously, you said it was fine. Windows update does not find a newer driver but clearly yours is newer/different
The second one is my W11 machine
Sorry - I forgot you said W11. But it is newer than my W11 and mine has the same problem.
I didn’t do anything special for the driver. That’s what my system (Dell XPS15) came with.
You can attempt windows update to see if newer version of the driver is offered.
OK. I finally beat on the W11 machine and got it to update to the same driver as yours. That’s the good news.
The bad news is there’s no change. With the input at 0, there’s still about 5 db of noise with nothing connected, and with the AF from the radio connected, it’s about 60 db.
The v1.6 is unchanged as well.
Are any of your Windows computers portable? Would be interested to see the level/waterfall with no input to the interface while on the battery power. You can also try running Linux on one of the Windows machines to see if the problem follows the computer or OS.
No change. The radio is running on battery and the PC is a Panasonic Toughpad on it’s internal battery. It is essentially the same on two W10 and one W11. It behaves as I expected on a RadpberryPi where I have a full range of adjustment all the way down to zero and the correct setting up from that (I didn’t not the value but at least 25-30%).
It just doesn’t sit well with me that with no antenna and the gain control at 0 that I should have around 60 db on WSJT-X. I would expect the gain to be at about 30 - 50% for that reading - approximately how it is on a Rpi. The DR is just way too sensitive under Windows.
I compared it with a QDX connected to the same antenna. The QDX was decoding 2 to 3 times more stations.
Back from a trip so looking at this again. I just don’t understand how I could have the same issue with 2 different W10 machines and a new W11 yet you don’t. It just doesn’t make sense.
I agree that something doesn’t add up. You are welcome to mail a minimum required kit demonstrating the issue and I’ll do the troubleshooting. Please PM for arrangements if you want to give that a go.
