On Sep 18, 2020, at 3:56 PM, Frank W2YK <W2YK@...> wrote:

When my PC turns the screen off (not sleep mode), and then wakes up again, WSJT receives OK. But when I try to transmit, the CAT/PTT stuff works OK, but no audio is sent to the rig. I have to restart WSJT to actually transmit a signal. I just changes PCs, and this didn't happen with my previous PC. Both were running Win10 through a microKeyerIII to a Yaesu FTDX101. This may be more of a PC question... I just don't know where to look...

Thanks, Frank W2YK

Ya know, 

 

After reading hundreds of these types of issues during the past 6+ months, it really make one wonder what the real problem is...!

 

Ask yourselves, why in the hell are these computers going to sleep at all?

 

The affected components are obviously being used; as proven by the fact that wsjtx quits working when those various components (audio, video, usb, etc.) go off into never, never land. Since wsjtx is constantly running & using resources - nothing should be timing out! 

 

Given, ms sucks and they have made a crappy system that doesn't work well most of the time.

 

Is there perhaps some coding that wsjtx can use to send more robust signals thru the the computer system, so that it can't go to sleep?  

73 - John - N7GHZ

On Wed, Oct 28, 2020, 1:50 PM Steven Rutledge <steven.t.rutledge@...> wrote:

I was just about to follow up on a post I made earlier, actually several.  My receive was locking up after a period of time with new Windows 10 computer.  I'm not an IT guy so I was confounded.  I finally discovered it was the sleep mode on Winows 10.  I don't think I never had my Windows 7 desktop or laptops go into sleep mode.  In fact, I'm not sure I knew it existed.  I leave them on all the time.  Anyway, I started fooling around with sleep mode and it appears that was the problem, I hope.  Just actually came to that conclusion this morning.  Thanks to all who tried to help me out earlier. 

73,

Steve, N4JQQ

Windows makes its decisions on power-saving actions like sleep mode based on keyboard and mouse activity. It does not know about activity on serial ports, sound cards, etc.

There are settings that can and should be changed to prevent Windows from putting USB devices to sleep unexpectedly. There is a nice summary at <http://www.dxlabsuite.com/dxlabwiki/PreventUSBPortPowerDown>. These settings changes should be applied on any Windows computer that is being used for real-time amateur radio activities.

73,
Rich VE3KI


On Wed, Oct 28, 2020 at 06:03 PM, JP Tucson, AZ wrote:

Ya know, 

 

After reading hundreds of these types of issues during the past 6+ months, it really make one wonder what the real problem is...!

 

Ask yourselves, why in the hell are these computers going to sleep at all?

 

The affected components are obviously being used; as proven by the fact that wsjtx quits working when those various components (audio, video, usb, etc.) go off into never, never land. Since wsjtx is constantly running & using resources - nothing should be timing out! 

 

Given, ms sucks and they have made a crappy system that doesn't work well most of the time.

 

Is there perhaps some coding that wsjtx can use to send more robust signals thru the the computer system, so that it can't go to sleep?  

73 - John - N7GHZ

On Wed, Oct 28, 2020, 1:50 PM Steven Rutledge <steven.t.rutledge@...> wrote:

I was just about to follow up on a post I made earlier, actually several.  My receive was locking up after a period of time with new Windows 10 computer.  I'm not an IT guy so I was confounded.  I finally discovered it was the sleep mode on Winows 10.  I don't think I never had my Windows 7 desktop or laptops go into sleep mode.  In fact, I'm not sure I knew it existed.  I leave them on all the time.  Anyway, I started fooling around with sleep mode and it appears that was the problem, I hope.  Just actually came to that conclusion this morning.  Thanks to all who tried to help me out earlier. 

73,

Steve, N4JQQ

On Wed, Oct 28, 2020 at 10:26 PM, ve3ki wrote:

Windows makes its decisions on power-saving actions like sleep mode based on keyboard and mouse activity. It does not know about activity on serial ports, sound cards, etc.

There are settings that can and should be changed to prevent Windows from putting USB devices to sleep unexpectedly. There is a nice summary at <http://www.dxlabsuite.com/dxlabwiki/PreventUSBPortPowerDown>. These settings changes should be applied on any Windows computer that is being used for real-time amateur radio activities.

Just to add to the above...

I'm in the process of setting up  a new PC to be used for my amateur radio apps including WSJT-X; the PC has a 3GHz i7-9700 8-core CPU with 16G RAM, a 500G SSD and is running Win 10 Pro.  I'd configured the PC to access one of my NAS devices via the Ethernet LAN and began to notice that even though the PC was set to never go to sleep it was losing its connection to the NAS.

I then twigged that the PC's Ethernet network adaptor's properties had the option to allow Windows to turn off the adaptor to save power checked; disabling that option seems to have cured the problem of the loss of access to the NAS.  All I need to do now is sort out all the other aspects of Win 10 that have been frustrating me...  :-)

--
Martin G0HDB