There’s such an app on the first PC for a Logitech BT headset, but the problem existed before that was installed. The second W10 does’t have anything that I’m aware of other then Audacity that I use for creating and editing Voice Keyer files. But it’s my main desktop that’s been in use for several years and I could have something on it.
I have a spare W10 PC that I can reset W10 on to make sure nothing else is there if that’s what it takes.
So - I’ve started reseting W10 on that spare PC so we can start with a clean slate.
I remember this problem raising up when I switched from using Pi4 to W10 because the Pi4 was somewhat limited in what it could run. As such, I tried one of the v1.6(?) DR with the Rpi and it also had a full range of adjustment. It was at that point you suggested an attenuator. I forget if that before or after v1.9 was introduced.
Meanwhile, is this the right driver?
Virgin W10 build.
Only Chrome, drivers for CP210x, Flrig, Fldigi & WSJT-X installed.
703
DR 1.9
13 pin ACC DR cable.
Level control at 0, AGC Off.
With the audio cable disconnected from the DR, it shows about 5 db of noise
This all looks ok. With “listen” option enabled and routed to the default playback device, which should be your computer’s speaker, do you hear anything unusual?
As long as you get good decodes, you should be all set.
Have you tried turning down RF gain. This has worked for me.
When I took the previous shot, I did not realize the radio was in TX.
So, under the conditions previously posted, with the radio in RX 
the level is 40 with no antenna connected. There is a low level of white noise when I listen to it. Notice all the crap in the spectrum display as well. I find it hard to believe this is correct, especially when it is unique to W10 and not present on the Rpi.
You do realize that turning down the RF gain reduces the sensitivity of the receiver? That’s not a great plan for weak signal work.
If the RF gain has been inadvertently turned up too far then turning it down a bit is a good idea. My suggestion was just something to try.
I had this problem using Digirig with a Yaesu 897D. The input was showing in the red and after looking unsuccessfully at all the options in Windows 11 to try and tame it I spotted the RF gain was set very high, which on this radio isn’t obvious as it’s quite a small knob. Turning it down brought the signal back into the green zone and it worked fine.
Under normal circumstances, the RF gain control should be at maximum. You’re only masking a problem that is in the AF side by reducing the RF sensitivity of your receiver so there is less noise. The AGC should also be off or Fast if off isn’t available.
Kicking and screaming into W11, a new Mini PC arrived today. Exactly the same results. No signal ≈ 25 DB. It’s like the jumper should enable a 60 db attenuator, not 20.
I’ve seen other users add a 100k pot into the line as well… specifically for some handhelds. This might be an option for you.
Matt
Yes. I can build my own cables and add a 60 db pad.
But I would expect that when I buy a device and cables that are supposedly compatible with my radio and operating system, they should work correctly. Otherwise what’s the point of buying premade cables?
I regret all the recommendations I made for DigiRig to be used with Icom radios to inquiries on forums.
That’s a very frustrating situation. I think Denis @K0TX will work with you to get the Digirig gear working with the IC-703.
73 Constrainted
I’m not quite sure why your windows computer ignores the level settings, but I can modify your Digirig by increasing attenuation 10 or 100 times (swap R17 to 1K or 100 ohm). PM for arrangements if you want to go ahead with that.
No other ICOM operators reported unsolvable high input level condition so no changes are planned to the regular Digirig design.
It isn’t ignoring level changes. I can increase the level and it indeed changes. If it were one machine, that would be understandable. But it is 3 different PCs. A Panasonic Toughpad running W10, a generic MiniPC that I re-installed W10 on, and a brand new W11 Mini PC. All 3 are EXACTLY the same tested with 2 different radios. The v1.6 DR does exactly the same, just a higher level. I think it is a driver issue. I really don’t think having the level at 0 and 5 db of noise with nothing connected is normal.
I’ll happily send you the generic W10 PC and my v1.9 DR for you to figure it out.
To reproduce the conditions on my end I would also require the radio, but that would be a lot to move back and forth. We can just go with the modification of the attenuator for your circumstances. That will only require Digirig alone.
No - could send you my IC-703 via flat rate USPS.
But since it shows ≈ 5db of noise with nothing connected and the output level of the radio is a known value, I woulf think that unnecessary.
This shouldn’t be an issue unique to iCom since the noise is present with no input to the DR. It’s a Windows problem. It isn’t present on RaspberryPi. That’s one reason NOT to modify the DR hardware.
Show me a screenshot of a W10 PC you have with WSJT-X running and no input cables to the DR
