.

Here's a start :

Disable the Dell Support assist from running on startup also disable anything that is DELL pre installed software on the system

You should be able to disable it from running using the msconfig.exe command then go to startup items in that list disable them

also I would look for spefic DEEl serivces ( not so much device driver services) but application services like tyhe Dell Support assit and disable it from the Services tab- then after doing the above restart and give V3 a try

my guess is Dells CRAPY ASS preloaded system support and bloatware- I hate Dells the only dells that run decent are those FDisked, formatted and just loaded with the damn operating system and non of there bloatware bullshit!
I'd put any of my prebuilds up against there systems with same CPUs and video and it blow them away at half the cost- the best Dell is a dead dell then you don't have to worry about it anylonger!

Both of my Dell's are under warranty so I'm reluctant to de-task them. I think there are others running non-Dells that have the same issue. Being a consumer rather than a builder I like Dell because of the support I get from any Dell computer. But I'm sure you are correct about Dell's Bloatware as is Microsoft Bloatware.

I did check startup.txt and Dell is not listed as a startup program. However when in Task Manager I de-task Dell Diagnostics, it reactivates after a delay as though I never de_tasked it.

Okay here are some more data points:

Nine Dell Programs running in processes Dell Data Manager, Dell Data Vault Data Collector, Dell Data Vault Rules Processor, Dell Diagnostics,
Dell instrumentation, Dell User Session Agent, Dell.D3WinSvc, Dell.DCF.UA.Bradbury.APSub..., And Dell TechHub.
The most active while I transmit is the Dell Diagnostics at an intermittent .2% CPU.

I tried a new VOX delay parameter of 1 sec to capture and hold the RF dropout. I was able, while speaking a fully detailed description of my HAM setup, to capture and hold the RF output dropout while inspecting the complete Dell APPs CPU usage, but there were no changes before the RF dropout and after the dropout while VOX was active. I did a second run and when the dropout occurred, I scanned the remaining processes CPU activity with nothing apparently different than a non-dropout as far as CPU usage. However with the VOX delay set at 1 sec I was able to capture the RF dropout within a couple to three minutes of talking! AND when the RF dropped out so did the Monitor signal!! Yet the meter showed 0 RF output AND it showed the the Mic signal going up to 0 dbm and the red spectrum for the RF! was normal!!

Thanks again for your time. I'm looking for the root cause so I can continue to use this fine piece of hardware and software!

I did msconfig services and disabled Dell Support Assistance and rebooted. I then retested and I'm still getting RF dropouts. I verified that Dell Suppiort Assistance is not running. No Dell programs are in the Startup file.

I have now de-serviced all Dell bloatware found in msconfig system. I rebooted and relaunched V3 and I still am having RF Dropouts. It is not the Dell Bloatware. This happens whether I use Ethernet direct to PC or via router from SDR2DX.

Thanks for your input. I'm still looking for a path to solve this problem. It may occur in other SDR2DX but yet detected by the user.

There has been considerable situation that the Dell Optiflex may be the problem, with resources, bloatware, etc. So I purchased another computer and the following are the specs.

Processor ‎4 GHz ryzen_5
RAM ‎16 GB DDR4
Memory Speed ‎3200 MHz
Hard Drive ‎500 GB
Chipset Brand ‎AMD
Card Description ‎Integrated
Wireless Type ‎802.11ax
Number of USB 2.0 Ports ‎2
Number of USB 3.0 Ports ‎2
Other Technical Details
Brand ‎Beelink
Series ‎SER5
Item model number ‎SEI
Hardware Platform ‎PC
Operating System ‎11 Pro
Item Weight ‎1.04 pounds
Product Dimensions ‎5 x 4.4 x 1.6 inches
Item Dimensions LxWxH ‎5 x 4.4 x 1.6 inches
Processor Brand ‎AMD
Number of Processors ‎1
Computer Memory Type ‎SODIMM
Hard Drive Interface ‎Serial ATA-300

Did not fix the problem. Therefore the conclusion is that the problem is with the software changes that happened prior to BETA.

Nate NA6TE

Hello Nate.
Please make a video of the issue, as descriptive as possible, how everything is interconnected with each other, upload it on some cloud server and send us the link.

Unfortunately, I haven't found a CLOUD site that will upload the 484mb files.

Nate

Try Google Drive

Never used this before so lets find out.


drive.google.com/file/d/1X0lkleIqrqeRXvniH2f2tVKymEX_-IaI/view?usp=sharing

Lets see if this works.
Incident happens towards the end of the video. Last few minutes.

Nate NA6TE

Could this be related to my thread at eesdr.com/en/forum-en/hardware-dx/10395-output-power-fluctuating-in-digimodes ? I too saw the output signal on the scope but almost no power, it was like there were only little spurts of up to 20W. In my case tuning always worked fine, and switching to 20m and transmitting there fixed the problem for me apparently...

Sounds like the same problem. Since I normally use only 40 and 75, that's where I notice it.

Meter that shows audio and power goes dead, yet the waterfall is still showing audio out. People I'm talking with confirm that I cut out. I unkey and key again and it's back to normal.

Nate NA6TE

Hi Nate
Just che3cking with you and others do they get AUDIO from your uploaded file I just looked and the video work's but NO audio ???

Might be better doing a YOUTUBE video
it might be just me unless others can not hear the audio either
73's

I have the same problem with the SunSDR2 PRO Power Output that you described.
Intel I7-4600, 8GB, direct connection to SunSDR2 PRO, EESDR V3 1.0.4