Date   

Re: WSJT-X hamlib error

alex
 

Hi,
did you try other communication speeds? 
I had this problem with my CAT firmware for uSDX and only one speed was 95% successful. On debugging I found communication in a high pace the radio couldn't understand.

73's Alex PE1EVX


Re: W10 Heads UP

JP Tucson, AZ <samcat88az@...>
 

Hi Hank,

Thanks for again showing how ms updates ARE THE MALWARE!

NOT JUST for ham radio either! Seems like every few days another tech media outlet tells of horror stories of bricked computers, lost data, etc.

I am still surprised that there has been a major class action lawsuit with a cease & desist order - making ms fully test their "fixes" that only make things much worse.   

The simple fix is to turn off & not accept ms's malware "updates"! 

As I have stated before & others have concurred,  dedicate a computer for ham radio, disallow updates & don't connect that computer to the internet! 

No updates, no internet, no headaches!  Simple - straight forward!




73 - John - N7GHZ


On Thu, Oct 29, 2020, 12:11 AM Hank Pfizenmayer <pfizenmayer@q.com> wrote:
Just a heads  if all of a sudden WSJT audio settings go to pot.  YMMV


This evening I updated to the latest N1MM  file - and a few minutes later - the  WSJT quit working and was reporting audio issues . So I went back one version of N1MM . No difference - WSJT still hosed. SO NOT N!MM.

I also  have a stand alone WSJT  install I use without N1MM -that was hosed as well. An hour of W10 twiddling of the USB codec selections for my K3S and WSJT settings etc resulted in nothing. THEN I looked at latest W10 updates. Found an entire page of so called "successful" KB4023057 updates - one a day from 9/30 thru 10/28 every day !!!!!!! (EVEN THOUGH I HAVE UPDATES ALWAYS DELAYED 7 DAYS ) . Anyhow  after some sleuthing which I wont go into now -I found a way to delete that update (the normal uninstall would not work ) I deleted that update and everything immediately returned to normal .W10 VER 1909

If you Google KB4023057 there are many other issues  that show up in many other ways.  Again YMMV - just  a possibility. I have a second W!0  VER 1909 computer that has this update  (only shows one time instead of a page full ) and it works OK...

Hank K7HP

FWIW Below are also some more error messages that N1MM/WSJT  combo version was showing-I would stil get this error after closing WSJT then N1MM and rebooting computer and re starting N1MM then WSJT




Re: Transmit light comes on but no tones being transmitted

alex
 

Funny, with me it happens most of the time after a frequency change. When I see a nice station I push TX, the radio is on TX but no audio. To solve this....

I push tune shortly and after that all works fine, also the first TX after that.

73's Alex PE1EVX


Re: Receive Locking Up With Windows 10

alex
 

Unfortunately I encounter the same problems. On Windows 10, no screen or any other energy savings enabled. I keep my system turned or for spotting during the night and 24/24. Sometimes WSJT-X v2.2.2 stalls after just an hour, other moments it stops after 48 hours. The only thing I can find (as I added and debugged CAT to the uSDX firmware) is that there is an issue with the CAT communication. Some commands are repeated in a very high pace before the radio is able respond. These command are not only during ham's interaction with the radio, but also autonomous (e.g. checking frequency etc). Maybe this is something to check.

73's Alex, PE1EVX


W10 Heads UP

Hank Pfizenmayer
 

Just a heads  if all of a sudden WSJT audio settings go to pot.  YMMV


This evening I updated to the latest N1MM  file - and a few minutes later - the  WSJT quit working and was reporting audio issues . So I went back one version of N1MM . No difference - WSJT still hosed. SO NOT N!MM.

I also  have a stand alone WSJT  install I use without N1MM -that was hosed as well. An hour of W10 twiddling of the USB codec selections for my K3S and WSJT settings etc resulted in nothing. THEN I looked at latest W10 updates. Found an entire page of so called "successful" KB4023057 updates - one a day from 9/30 thru 10/28 every day !!!!!!! (EVEN THOUGH I HAVE UPDATES ALWAYS DELAYED 7 DAYS ) . Anyhow  after some sleuthing which I wont go into now -I found a way to delete that update (the normal uninstall would not work ) I deleted that update and everything immediately returned to normal .W10 VER 1909

If you Google KB4023057 there are many other issues  that show up in many other ways.  Again YMMV - just  a possibility. I have a second W!0  VER 1909 computer that has this update  (only shows one time instead of a page full ) and it works OK...

Hank K7HP

FWIW Below are also some more error messages that N1MM/WSJT  combo version was showing-I would stil get this error after closing WSJT then N1MM and rebooting computer and re starting N1MM then WSJT


Re: F/H Decodes

Reino Talarmo
 

Hi Chuck,

I am glad to help. Actually it was no secret as it is clearly described in

http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chuck Schloss
Sent: 29. lokakuuta 2020 0:11
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] F/H Decodes

 

Thanks, Reino, you nailed it – all is OK now.

73,  Chuck

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Chuck Schloss
Sent: Tuesday, October 27, 2020 4:36 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] F/H Decodes

 

Thank you, Reino.

I did not have that checked.  I do now.

Now need to find a signal to check this out.

73, Chuck

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Reino Talarmo
Sent: Tuesday, October 27, 2020 9:56 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] F/H Decodes

 

Hi Chuck,

In case you mean that you see strong signal above 1000 Hz, but no decodes of those, then have you ‘Rx All Freqs’ unticked (above Hound red sign).

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chuck Schloss
Sent: 27. lokakuuta 2020 16:46
To: main@WSJTX.groups.io
Subject: [WSJTX] F/H Decodes

 

Guys,

 

I rarely get a decode even though there are several strong signals on the waterfall.

Time is right-on.  Been working regular FT8 all morning.
Now up frequency trying to work JX2US.  Several strong signals, no decodes.

Windows 10, WSJTX 2.2.2.  Yaesu FTDX101MP, Ham Radio Delux.

 

Chuck AG0W


moderated Re: Continuing problem, WSJT-X fails to decode

Russ Ravella
 

Hi Bill,

Again, thanks for the response.

No, that’s not the issue here.  I have seem that come up on the forum many times.  I’ve never used that function so never checked it and just to be complete verified again that it’s still unchecked before posting this.  This is something different, like several others have reported, and has been going on for a long long time.  After grabbing the .wav files this time I restarted WSJT-X and it’s unfrozen now but if there’s something else you’d like me to collect and send please let me know.

Thanks,
Russ KR6W


On Oct 28, 2020, at 2:45 PM, Bill Somerville <g4wjs@...> wrote:

Russ,

there is a known defect in WSJT-X where the Band Activity window stops scrolling down to show them latest decodes, the defect only occurs when "Settings->General->Start new period decodes at top" is checked. It occurs after a large number of decodes are printed. You can check if this is the issue you are suffering by manually scrolling down the Band Activity window to reveal the apparently missing decodes.

You can work around this issue either by unchecking the "Settings->General->Start new period decodes at top" option or by erasing the Band Activity window periodically (right-click and select "Erase").

73
Bill
G4WJS.

On 28/10/2020 21:40, Russ Ravella via groups.io wrote:
Hi Bill,

Thanks for the response.

Yeah, that’s what I was saying in my post.  Yet WSJT-X was frozen when I collected them.  This thread is asking why that’s happening.  You asked its originator to provide .wav files so I have also.  As I mentioned in my post, I also took a video which I can provide if you think it might be helpful.  The question remains, why is WSJT-X freezing ?

Thanks,
Russ KR6W



On Oct 28, 2020, at 9:05 AM, Bill Somerville <g4wjs@...> wrote:

On 28/10/2020 04:52, Russ Ravella via groups.io wrote:
HI Bill,

Following up on this, I’ve been off the air for a few days but fired up WSJT-X today and got another freeze.  I’m sending you the last three .wav files that were saved consistent with your request below.  To me they just sound like normal audio and seem to terminate normally.  WSJT-X was up and frozen when I grabbed them and after I did, and closed WSJT-X, I checked and no more .wav files had been written.  I also took a short video showing WSJT-X with the waterfall frozen but the 15-sec timer still running and Flex DAX showing audio still being generated by the radio (that is, the radio and audio connection weren't frozen).  Being a video file, I won’t attach it here in case you’d rather I sent it via another means.

I’ve been getting these freezes since at least the first V2 and maybe before.  I can’t correlate them to anything.  During that time I’ve had four different Flex radios (quality is not a Flex Radio attribute - software or hardware) and several revisions of SSDR, CAT, DAX and Windows 10 software (I’m on 2004 now) running on three different fast laptops each set up from scratch.  I don’t use any third party AV software as they’re all basically malware themselves. The freezes seem to just “happen”.  Sometimes closing and restarting WSJT-X fixes it and sometimes I have to restart the whole computer.  I’ve lost at least one potential ATNO due to this.

Thanks for helping as always !
Russ KR6W

Hi Russ,

those three .WAV files look fine to me, I get the following decodes from them:

------------------------------------ 20m
230330 10 0.4 1847 ~ YS1GMV VE7XT R-18
230330 0 0.3 1331 ~ N2MSF AG5VE R+03
230330 7 0.3 2144 ~ JA9IFF W3MMM -08
230330 5 0.4 445 ~ CQ KF5TVG EM26  CQ Zone 4
230330 -3 0.3 900 ~ CQ KQ1S EM94  U.S.A.
230330 2 0.3 2199 ~ PP5DE K0HMZ R-16
230330 21 0.3 672 ~ YS1GMV WB0TAX EM32
230330 -8 0.3 1594 ~ KM6KJI W3DJS EM83
230330 -12 0.4 1102 ~ XL3T K4TT FN44
230330 -12 0.3 2550 ~ CQ LU5CAT GF05  SA
230330 -6 0.4 1791 ~ WA8QNN KC5TT -02
230330 -10 0.4 360 ~ YS1GMV KE0ELU -19
230330 -1 1.3 734 ~ CQ AF5DE EM25  CQ Zone 4
230330 -6 0.8 2324 ~ BU2BV KJ7OTZ CN87
230330 -8 0.3 833 ~ W7SWB WD9IQN -16
230330 -5 0.1 1642 ~ NN2T WA5VXI EM25
230330 -8 0.3 778 ~ CQ KC9VW EL29  CQ Zone 4
230330 -19 0.3 2086 ~ CQ KD9KCK EN61  CQ Zone 4
230330 -10 0.4 2332 ~ KJ4SRY VA6KL -06
230330 -6 0.4 1822 ~ KE3VV W6ASO R+01
230330 -15 0.4 1313 ~ JA0ARF KR7X R-14
230330 -9 0.5 1639 ~ NN2T AC0FS EN34
230330 -18 0.3 983 ~ BH4TVU K9RR R-16
230330 -18 0.5 1976 ~ VE2JI LW8DHX -13
230330 -18 0.5 2016 ~ KI5KSE KB4DPH EL88
230330 -24 0.1 1084 ~ W5FHW WB9MSM EN53
230330 -23 0.7 2000 ~ CQ KF0AQK EN21  CQ Zone 4
230330 -14 0.4 1648 ~ VA3TPS KD9MKR RR73
230330 -13 0.1 1608 ~ CQ KF9KV EN52  CQ Zone 4
------------------------------------ 20m
230345 -17 -0.1 1492 ~ VY1MB KN4GGH EM91
230345 -3 -1.6 1415 ~ CQ AI4QT EM74  U.S.A.
230345 -10 0.5 2275 ~ CQ W7OK CN86  CQ Zone 3
230345 -7 0.3 888 ~ KB7THX AI4VV RRR
230345 8 0.4 1638 ~ AC0FS NN2T +01
230345 0 0.6 1208 ~ WB9MSM W5FHW EM02
230345 -3 0.3 1942 ~ KB4DPH KI5KSE +06
230345 -13 0.3 2051 ~ W5CRN KB7SAT 73
230345 9 0.3 1695 ~ CQ W0WND DM97  CQ Zone 4
230345 17 0.3 530 ~ AB1WG N5LDO 73
230345 -13 0.3 2206 ~ JE3BMU N7CTB CN85
230345 6 0.4 424 ~ CO8AFG W8KEN -14
230345 -14 0.4 1890 ~ VA6KL KJ4SRY R-17
230345 -6 0.3 2795 ~ AG5VE N2MSF RR73
230345 -15 0.4 1553 ~ XP3A N4AN R-19
230345 -14 0.5 744 ~ EA5IYK VE6ATS R-11
230345 -2 0.3 575 ~ KN6ITP K4BWM FM14
230345 -4 0.4 1667 ~ J88DCP/R WB4KTF EM10
230345 -12 0.2 852 ~ KN6ITP KB4RRN EM90
230345 -17 0.3 1958 ~ KR7X JA0ARF RR73
230345 -16 0.3 900 ~ CQ KK4OMJ EM78  U.S.A.
230345 -24 0.3 1777 ~ KC4VKG N8FRI EN81
230345 -22 0.3 2054 ~ CQ N2OO FM29  U.S.A.
230345 -10 0.4 1072 ~ KD9KCK N3CKI FM03
230345 -14 0.4 1717 ~ WA2EPI <...> -08
230345 -1 0.4 628 ~ JE3BMU WA7VIZ CN92
230345 -9 0.3 1624 ~ KC9VW W0BLE EN31
230345 -10 0.4 1605 ~ KN6ITP KB8SRX 73
230345 -24 -0.1 1365 ~ CQ K3ADU FN10  a1 U.S.A.
230345 -20 0.6 1649 ~ KD9MKR VA3TPS 73
------------------------------------ 20m
230400 -18 1.0 1488 ~ HC5EG PY7YZ 73
230400 8 0.3 1331 ~ N2MSF AG5VE 73
230400 -5 0.3 900 ~ CQ KQ1S EM94  U.S.A.
230400 -1 0.1 1966 ~ N5AQM WA5VXI EM25
230400 4 0.4 445 ~ VE3XTF KF5TVG -16
230400 7 0.3 2144 ~ JA9IFF W3MMM RR73
230400 0 0.3 778 ~ CQ KC9VW EL29  CQ Zone 4
230400 1 0.3 2199 ~ PP5DE K0HMZ 73
230400 -8 0.4 360 ~ YS1GMV KE0ELU -19
230400 -12 0.3 1051 ~ N2OO KE5GXX EL17
230400 -4 0.5 1639 ~ NN2T AC0FS R+07
230400 -8 0.4 1102 ~ XL3T K4TT FN44
230400 -9 0.3 2548 ~ CQ LU5CAT GF05  SA
230400 -5 0.8 2324 ~ BU2BV KJ7OTZ CN87
230400 -15 0.3 983 ~ BH4TVU K9RR R-16
230400 5 0.4 1847 ~ YS1GMV VE7XT R-18
230400 6 0.4 1823 ~ KE3VV W6ASO R+01
230400 -13 0.3 833 ~ W7SWB WD9IQN -16
230400 -12 0.5 2015 ~ KI5KSE KB4DPH R+01
230400 -7 0.3 1313 ~ JA0ARF KR7X 73
230400 2 0.1 1791 ~ WA8QNN KC5TT -14
230400 -9 0.4 2333 ~ KJ4SRY VA6KL RR73
230400 -19 0.3 2088 ~ CQ KD9KCK EN61  CQ Zone 4
230400 -15 0.7 2000 ~ CQ KF0AQK EN21  CQ Zone 4
230400 -8 0.3 1794 ~ LU9HCO W3DJS EM83
230400 -16 0.5 1977 ~ VE2JI LW8DHX -13
230400 -15 0.2 1608 ~ CQ KF9KV EN52  CQ Zone 4
230400 -12 0.4 1649 ~ VA3TPS KD9MKR RR73

73
Bill
G4WJS.







Re: Odd message

Gary - AG0N
 

On Oct 28, 2020, at 18:57, W1EL Eric <elowell@loonrd.com> wrote:

Anyone know what this is?

005000 -21 0.5 1737 ~ W1EL 2U7DVD/R RA70
Looks like a false decode. Not unheard of, especially if you use deep decode and/or have Enable AP turned on.

I never use AP, but always have Deep turned on and get them now and then. Just ignore them.

Gary - AG0N


Re: F/H not working, Mac+MLDX+7300

Randy Cook
 

Per K7GQ suggestion, I didn't use my pre-defined F/H config, but set up in Prefer -> Advanced -> Special Operating. It seems to work, no error message. 


Odd message

W1EL Eric
 

Anyone know what this is?

 

005000 -21  0.5 1737 ~  W1EL 2U7DVD/R RA70

 

I get one every once in a while.

 

Thanks!

 

73 de W1EL

 

Eric Lowell

48 Loon Rd

Wesley, ME 04686

207-255-6476

Mobile 207-210-7469

 


Re: Few decodes after working just fine 30 minutes ago... duh!

Gary - AG0N
 

On Oct 28, 2020, at 17:48, JP Tucson, AZ <samcat88az@gmail.com> wrote:

I having hearing loss & tinnitus, so sitting there listening to that thing squeal just gives me a headache, so I turn down the volume all the way, sound just isn't needed!
As do I. However, there is much information to be had by keeping a close ear to the frequency on receive. Just run it at a very low level. Same for transmit audio if your rig has the capability. Keep the monitor on at a very low level to keep tabs on whether you are transmitting garbage with your signal or not. That’s a sore subject, as if you monitor 40 meters, you’ll likely see multiple signals that are very dirty. There are also any number of stations that transmit a chime or chord EVERY TIME THEIR TRANSMITTER KEYS! So every transmit cycle, they are sending musical notes before any data content is even attempted.

No one says you need to monitor with the audio blasting the speaker. It’s just good operational practice to pay attention to what you are transmitting. Personally, I wear headphones for the purpose. I’m always listening to the transmitted signal, no matter what mode I’m on.

73, Gary - AG0N


Re: Few decodes after working just fine 30 minutes ago... duh!

JP Tucson, AZ <samcat88az@...>
 

Gary,

You would be right, IF I ran wsjtx with the audio up - I don't!

I having hearing loss & tinnitus, so sitting there listening to that thing squeal just gives me a headache, so I turn down the volume all the way, sound just isn't needed!

Yet another reason why wsjtx is good for ham radio; so that folks like me or ones who are mostly, or totally deaf can enjoy amateur radio too!



73 - John - N7GHZ


On Wed, Oct 28, 2020, 3:42 PM Gary - AG0N <mcduffie@...> wrote:


> On Oct 28, 2020, at 16:33, JP Tucson, AZ <samcat88az@...> wrote:
>
> I had been playing with CW for a bit, & while I returned the radio to usb... I had forgotten to re-select the wide ssb audio filter setting (instead of the very narrow cw filter)!


I’m not sure how you missed it!  You should have been able to hear the fact that you were on the wrong filter, if nothing else.  The waterfall would have shown it also, as you finally discovered.

Gary - AG0N



Re: Receive Locking Up With Windows 10

Steven Rutledge
 

Belay my last.  It went for about eight hours with sleep and screensaver disabled.  Locked up again.  Back to the drawing board.

Steve, N4JQQ


Re: Few decodes after working just fine 30 minutes ago... duh!

Gary - AG0N
 

On Oct 28, 2020, at 16:33, JP Tucson, AZ <samcat88az@gmail.com> wrote:

I had been playing with CW for a bit, & while I returned the radio to usb... I had forgotten to re-select the wide ssb audio filter setting (instead of the very narrow cw filter)!

I’m not sure how you missed it! You should have been able to hear the fact that you were on the wrong filter, if nothing else. The waterfall would have shown it also, as you finally discovered.

Gary - AG0N


locked Re: Windows audio and sleep mode #AudioIssues

Bill Somerville
 

Hi Rich and John,

that is partially right. For connected devices like serial ports the power save options are not in play as having a connection open is enough to stop power saving. For audio streams there is no connection as such, an application requests or subscribes to a device stream. Those streams source or sink data to a shared resource and Windows will power that device down without regard for any application using it. Applications are not notified when audio streams are shut off by power saving.

73
Bill
G4WJS.

On 28/10/2020 22:26, 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.

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



locked Re: Windows audio and sleep mode #AudioIssues

JP Tucson, AZ <samcat88az@...>
 

Hi Rich,

The kb & mouse activity is true, but since you need to move & click the mouse to log, & select new stations to operate...  the system still isn't picking that up.



73 - John - N7GHZ


On Wed, Oct 28, 2020, 3:27 PM ve3ki <ve3iay@...> 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.

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






Few decodes after working just fine 30 minutes ago... duh!

JP Tucson, AZ <samcat88az@...>
 

I'm big enough to admit when I do dumb stuff...

So early this morning, I worked a bunch of FT4 & FT8 & everything worked fine.

I then did some experimenting for about half an hour, & after that I went back to working FT8 - or rather tried to!

Something wasn't right, for try I as I did, I now couldn't seem to 'hear' or decode hardly anyone!  Where I had been decoding a couple dozen signals on 40m, I was now seeing only a few. 

It took me about 5 minutes to realize that I had minimized the wide-graph & after I brought it back up, I saw the issue in that I was only seeing a small portion of spectrum, it took another min. Or so to recheck my frequency, check, usb, check...

Scratching my head, it suddenly dawned on me the cause... I had been playing with CW for a bit, & while I returned the radio to usb... I had forgotten to re-select the wide ssb audio filter setting (instead of the very narrow cw filter)!  Which is why I was only seeing a few signals in that small region.

Duh!  It helps to run in upper sideband with the wide audio filter to match.

Recheck & double-check all of your setting after changing operating modes...


locked Re: Windows audio and sleep mode #AudioIssues

ve3ki
 

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



Re: F/H Decodes

Chuck Schloss
 

Thanks, Reino, you nailed it – all is OK now.

73,  Chuck

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Chuck Schloss
Sent: Tuesday, October 27, 2020 4:36 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] F/H Decodes

 

Thank you, Reino.

I did not have that checked.  I do now.

Now need to find a signal to check this out.

73, Chuck

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Reino Talarmo
Sent: Tuesday, October 27, 2020 9:56 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] F/H Decodes

 

Hi Chuck,

In case you mean that you see strong signal above 1000 Hz, but no decodes of those, then have you ‘Rx All Freqs’ unticked (above Hound red sign).

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chuck Schloss
Sent: 27. lokakuuta 2020 16:46
To: main@WSJTX.groups.io
Subject: [WSJTX] F/H Decodes

 

Guys,

 

I rarely get a decode even though there are several strong signals on the waterfall.

Time is right-on.  Been working regular FT8 all morning.
Now up frequency trying to work JX2US.  Several strong signals, no decodes.

Windows 10, WSJTX 2.2.2.  Yaesu FTDX101MP, Ham Radio Delux.

 

Chuck AG0W


locked Re: Windows audio and sleep mode #AudioIssues

JP Tucson, AZ <samcat88az@...>
 

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


11741 - 11760 of 29456