|
locked
Re: 2.1.2 not decoding “high” frequencies
Louis Alexander
completely false from my observation. You do not even have to have the waterfall on to decode signals. Not quite sure what you are doing there.
|
|
|
|
locked
Re: second program
Brian Farleigh
John,
You can select Configurations > Default > Clone and create another radio by changing the clones setting to what you need. I do this for my Kenwood TS-590S and my TS-590SG and can toggle between the two by going to Configurations and selecting the radio that I want. Thus I don't have to run a second wsjt-x.
73,
Brian N0LNK
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
Bob McGraw - K4TAX <rmcgraw@...>
I seem to recall that V2.1.2 has a tighter time accuracy
requirement. Although I would think a time error would apply
across the audio spectrum. You may be "hearing" signals but what
does the WSJT-X level indicator on the left show? It should be
consistent across the frequency spectrum. Re-check all cables to
assure they are firmly and correctly seated. 73 Bob, K4TAX
On 1/6/2020 5:54 PM, Tom Read wrote:
Yes, sorry Bill. I do of course mean "not decoding high frequencies".
|
|
|
|
locked
Looking for photos from the 2019 WW Digi DX Contest
We (the contest committee) are looking for photos from anyone who took part
in the inaugural World Wide Digi DX Contest that took place in August 2019. We are mainly looking for photos of you or your team (if you were multi-op) located in the shack or in the case of multi-op, it doesn't have to be in the shack. A few photos will be included in the results article that will be posted on the WW Digi DX Contest website soon. Please send any photos directly to me aa5au@... Thank you! Don AA5AU
|
|
|
|
locked
Re: TU; messages in RTTY RU
Reino Talarmo
Steve,
I agree that generally your cannot be absolutely sure, if no 73 to your RR73. On the other hand, if you see (decode) all messages from that station to whom you sent RR73 and there is no sending or especially a CQ from that station in the next timeslot, then he is following the 'Rule' that you have logged the QSO and there is no need to resent R... The TU; would be fine in that situation. I got a feeling that it is generated, if you have logged the previous call before your start to send a reply to somebody else. The use of automatic logging may be very relevant in that respect. I noted that you should not reply to somebody else before logging the previous QSO as that seems to generate the answer using the same serial number as the not yet logged QSO. Of course situation is less clear, if he is replying to somebody else in the next timeslot (without TU;...) especially when there has been already some repetitions or you don't decode that message. If it is question of an important (rare) multiplier, then you may choose to spend potentially many additional timeslots to get a 73 back. You may try RRR instead as that should tell a not yet logged situation. 73, Reino oh3mA
|
|
|
|
locked
Re: TU; messages in RTTY RU
Steve Kavanagh
That's true Reino. A QSL is valid without the final acknowledgement, since callsigns and some additional information have been confirmed by that point. But you can't be sure until you receive a QSL card or equivalent. Indeed, I have received many QSLs on LOTW now from the RTTY RU for QSOs with the minimum information exchange as you mentioned.
However, in a contest, you need to be able to know (almost) for sure if you have worked someone or if you should call them again later to ensure you get the points/multiplier. WSJT-X contest modes do not yet meet that requirement in the standard sequence, with this rare exception of the TU; messages. 73, Steve VE3SMA
|
|
|
|
locked
Re: 2.1.2 not decoding “high” frequencies
Reino Talarmo
Tom,
WSJT-X decodes only frequencies that are shown on the Waterfall. The feature may be used to kill unwanted stations or make decoding faster for the wanted stations.
73, Reino oh3mA
|
|
|
|
locked
Re: 2.1.2 not decoding “high” frequencies
Solved it! It was a stupid thing.
i just needed to drag the waterfall window out to its full width. The radio could hear the signals, but if they weren’t in the waterfall, WSJT ignored them for decoding! I’m not sure if 2.0 did this - never come across it before anyway. Thanks for the suggestions - the one to inspect the waterfall was the one to unlock the mystery!
|
|
|
|
locked
Re: TU; messages in RTTY RU
Reino Talarmo
Hi Jim,
On the other hand Joe has defined that sending an RR73 means that the QSO is logged. It also means 'I am not expecting any more messages from you, except a repetition of your previous R...., if you did not received my RR73'. Taking that into account the sending of 73 is not mandatory especially in a contest and many serious contesters never sent it in RTTY RU. 73, Reino oh3mA after sending RR73 several times one is never sure if the other station gotthe last one or just went off to make other contacts .... however, a few compassionate ops were nice to send back a 73 when they finally got my RR73, which I appreciated.
|
|
|
|
locked
Summary only
Walt Baldree <waltbaldree@...>
Correct
Sent from my iPhone
|
|
|
|
locked
Re: second program
Randy Lake
1 Google search: Good luck Randy N1KWF
On Mon, Jan 6, 2020 at 9:19 PM John Kjos <john@...> wrote: Hi, can I download a second WSJTX to run with other radio, so I don't --
Randy Lake N1KWF 73 Gunn Rd. Keene,NH
|
|
|
|
locked
second program
John Kjos
Hi, can I download a second WSJTX to run with other radio, so I don't have to change setting each time? Thanks
73 John W9PRM -- EMAIL: john@... WEBPAGE: http://www.w9rpm.com/ DX CLUB: http://www.tcdxa.org/
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
iain macdonnell - N6ML <ar@...>
Ahh, yeah - I thought of Fox mode, but that only decodes messages
toggle quoted messageShow quoted text
directed to your callsign ... but I forgot that there's also a "Rx All Freqs" option in Hound mode - disabling that would cause the symptom described! 73, ~iain / N6ML
On Mon, Jan 6, 2020 at 4:50 PM ve3ki <ve3iay@...> wrote:
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
ve3ki
Or do you somehow have Fox/Hounds mode turned on?
toggle quoted messageShow quoted text
73, Rich VE3KI
On Mon, Jan 6, 2020 at 07:01 PM, Tom Read wrote: I'll have to check that and let you know tomorrow.
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
I'll have to check that and let you know tomorrow.
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
iain macdonnell - N6ML <ar@...>
Do you see the strong signals above 1100Hz on the waterfall/scope in
toggle quoted messageShow quoted text
the "Wide Graph" window? 73, ~iain / N6ML
On Mon, Jan 6, 2020 at 3:55 PM Tom Read <tommyread@...> wrote:
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
Interesting. My problem is worse. I am decoding everything, even very weak. Nobody seems to decode me on 40 and 30 when I decode weaker than say - 16 or so. I guess I need a better antenna {not possible here unless I win the lottery) or to turn on the linear 😊
Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb
-----Original Message-----
On 06/01/2020 21:45, Tom Read wrote: > I updated my WSJT-X to v2.1.2 today. I run it on a Windows 10 tablet > for portable operating. > When I started to use it I noticed that I was receiving and hearing > some strong signals, but nothing decoded. Some stations then moved > down in frequency to around 500Hz-1000Hz. I was then able to decode > them, but nothing above 1100Hz was decoded even though signals were > strong. > Up to yesterday, everything worked perfectly on v2.0. The only thing > that has changed in my set up is the update to v2.1.2. Any ideas? > Tom M1EYP
HI Tom,
your subject line is confusing, I will assume you meant "2.1.2 not decoding "high" frequencies". The issue sounds like a problem with your rig's Rx filter settings.
73 Bill G4WJS.
-- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
Yes, sorry Bill. I do of course mean "not decoding high frequencies".
I thought about the rig's filters too - but I'm still hearing the audio of the strong signals above 1100Hz on the waterfall, and nothing has changed on my rig settings since yesterday when I was decoding everything perfectly on v2.0. The only change in the system has been moving from v2.0 to v2.1.2.
|
|
|
|
locked
Re: 2.1.2 not decoding “low” frequencies
On 06/01/2020 21:45, Tom Read wrote:
I updated my WSJT-X to v2.1.2 today. I run it on a Windows 10 tablet for portable operating.HI Tom, your subject line is confusing, I will assume you meant "2.1.2 not decoding "high" frequencies". The issue sounds like a problem with your rig's Rx filter settings. 73 Bill G4WJS.
|
|
|
|
locked
2.1.2 not decoding “low” frequencies
I updated my WSJT-X to v2.1.2 today. I run it on a Windows 10 tablet for portable operating.
When I started to use it I noticed that I was receiving and hearing some strong signals, but nothing decoded. Some stations then moved down in frequency to around 500Hz-1000Hz. I was then able to decode them, but nothing above 1100Hz was decoded even though signals were strong.
Up to yesterday, everything worked perfectly on v2.0. The only thing that has changed in my set up is the update to v2.1.2. Any ideas?
Tom M1EYP
|
|
|