Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

[Paul Randall]

PLS QSY to PM for any chat or popcorn you must have; I believe this channel 
already in use for software development.
TKS 73s

From: jbozell via wsjt-devel 
Sent: 19 August 2020 22:44
To: WSJT software development 
Cc: jbozell 
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX


Well! This seemingly innocuous (but useful) thread has suddenly gotten much 
more interesting. Popcorn please...who has the square for the first person to 
say “if you don’t like it, scroll down”? 



73,



WB0CDY



From: Paul Randall 
Reply-To: WSJT software development 
Date: Wednesday, August 19, 2020 at 3:17 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX



[External Email]

Actually, NO.

I've asked stupid questions on here, been pointed at the answer elsewhere and 
regretted my lack of "go find it".

What I can say is I didn't make my questions into a boxed set, to be enjoyed 
for a whole season.

If you've nothing better to do it may be a distraction but this forum is 
purposed for "WSJT Software development"

WSJT software allows us all to use some extremely clever turnkey signal 
processing software to make contacts on almost every band with potentially 
minimal equipment. It does however still require operators to have a tad more 
than minimal "pizzaz!"



A while back I saw CQs from (bogus) T3ST (bogus) - I'm sure I could have 
complained here "why did I see this?" and who could have known this was BOGUS 
(bogus callsign) BOGUS.  T3ST? who could have guessed? BOGUS



So, if you are operating CW or SSB or AM or FM or RTTY or anything else, and 
you hear a BOGUS (bogus) callsign, please don't expect your morse key, or 
electronic keyer, or balanced modulator, or any other modulator, to remove from 
you the need to identify the callsign as BOGUS (bogus) or prevent you from 
replying.



WSJT software in conjunction with PSKReporter has revolutionised our view of 
LF, VHF and UHF propagation. I worked Falklands on top band! My neighbour was 
able to record transmissions from D4VHF Cape Verde on 2M for almost every day 
in June, a path length equivalent to Europe - North America. I personally 
worked D4VHF on 70cm twice in July. Transatlantic path length on 70cm??? Really?



Let's keep this channel open and clear for input to the software development 
team for that purpose - software development, also keep in mind WSJT software 
has a specific purpose and is not intended to be a "go everywhere, do 
everything" answer for every possible scenario you might experience. Licensed 
operator is still required.



Maybe a lot of these posts might be better sent to a WSJT user forum, where 
operators can exchange experiences and gain understanding.



So,  I echo the OMs intention, let's rejoice in asking questions, but please 
re-consider the bandwidth you are occupying, is it appropriate or perhaps 
better elsewhere?



My 2p worth



Paul G3NJV













From: Carey Fisher 
Sent: 19 August 2020 20:36
To: WSJT software development 
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX



I find the discussion interesting.

73, Carey, WB4HXE



On Wed, Aug 19, 2020 at 2:42 PM Gary McDuffie 
mailto:mcduf...@ag0n.net>> wrote:

> On Aug 19, 2020, at 02:21, Stephen VK3SIR 
> mailto:vk3...@hotmail.com>> wrote:
>
>
> --
>
> Why has the stream been decoded (good) and the logic allowed it to be 
> identified – displayed - as coming from Morocco (bad)? The station should not 
> display that it has come from Morocco in the first place as the call violates 
> the rules of callsign structures for that DXCC entity. That is the real point 
> I am making here !
>
> —
>

Good grief!  Can this thread not die?  If you don’t know the call and it looks 
bogus (yes it does) why are you even looking at it?  Dimiss it and move on.  
There is supposed to be an operator at the keyboard to interpret these things.

Gary - AG0N

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




--

Carey Fisher

careyfis...@gmail.com<mailto:careyfis...@gmail.com>


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

[Paul Randall]

Actually, NO.
I've asked stupid questions on here, been pointed at the answer elsewhere and 
regretted my lack of "go find it".
What I can say is I didn't make my questions into a boxed set, to be enjoyed 
for a whole season.
If you've nothing better to do it may be a distraction but this forum is 
purposed for "WSJT Software development"
WSJT software allows us all to use some extremely clever turnkey signal 
processing software to make contacts on almost every band with potentially 
minimal equipment. It does however still require operators to have a tad more 
than minimal "pizzaz!"

A while back I saw CQs from (bogus) T3ST (bogus) - I'm sure I could have 
complained here "why did I see this?" and who could have known this was BOGUS 
(bogus callsign) BOGUS.  T3ST? who could have guessed? BOGUS

So, if you are operating CW or SSB or AM or FM or RTTY or anything else, and 
you hear a BOGUS (bogus) callsign, please don't expect your morse key, or 
electronic keyer, or balanced modulator, or any other modulator, to remove from 
you the need to identify the callsign as BOGUS (bogus) or prevent you from 
replying.

WSJT software in conjunction with PSKReporter has revolutionised our view of 
LF, VHF and UHF propagation. I worked Falklands on top band! My neighbour was 
able to record transmissions from D4VHF Cape Verde on 2M for almost every day 
in June, a path length equivalent to Europe - North America. I personally 
worked D4VHF on 70cm twice in July. Transatlantic path length on 70cm??? Really?

Let's keep this channel open and clear for input to the software development 
team for that purpose - software development, also keep in mind WSJT software 
has a specific purpose and is not intended to be a "go everywhere, do 
everything" answer for every possible scenario you might experience. Licensed 
operator is still required.

Maybe a lot of these posts might be better sent to a WSJT user forum, where 
operators can exchange experiences and gain understanding.

So,  I echo the OMs intention, let's rejoice in asking questions, but please 
re-consider the bandwidth you are occupying, is it appropriate or perhaps 
better elsewhere?

My 2p worth

Paul G3NJV






From: Carey Fisher 
Sent: 19 August 2020 20:36
To: WSJT software development 
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

I find the discussion interesting.
73, Carey, WB4HXE

On Wed, Aug 19, 2020 at 2:42 PM Gary McDuffie 
mailto:mcduf...@ag0n.net>> wrote:

> On Aug 19, 2020, at 02:21, Stephen VK3SIR 
> mailto:vk3...@hotmail.com>> wrote:
>
>
> --
>
> Why has the stream been decoded (good) and the logic allowed it to be 
> identified – displayed - as coming from Morocco (bad)? The station should not 
> display that it has come from Morocco in the first place as the call violates 
> the rules of callsign structures for that DXCC entity. That is the real point 
> I am making here !
>
> —
>

Good grief!  Can this thread not die?  If you don’t know the call and it looks 
bogus (yes it does) why are you even looking at it?  Dimiss it and move on.  
There is supposed to be an operator at the keyboard to interpret these things.

Gary - AG0N

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Carey Fisher
careyfis...@gmail.com

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Suggestion

[Paul Randall]

'morning Bill,  sun baked down here in Cornwall.  Thanks for responding.
The app I was looking at is called WSJT Monitor. It's setup instruction tells 
me to change the normal address for psk reporter,  so it's one or the other.
Pity as it would be really useful. It's Es season plus openings down to D4 but 
blink and you miss them.

The combination of the WSJT teams software plus the PSKreporter site has 
revolutionised understanding of long distance paths on vhf/uhf. Many thanks
PS if your interested I can post a map from couple of days ago - biggest Es 
event since the 80s plus a duct to D4

Best wishes Paul




Sent from my Samsung Galaxy smartphone.



 Original message 
From: Bill Somerville 
Date: 31/05/2020 12:02 (GMT+00:00)
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Feature Suggestion

Hi Paul,

WSJT-X sends copious information via it's UDP Message Protocol, you should use 
that.

73
Bill
G4WJS.

On 31/05/2020 07:50, Paul Randall wrote:
Another feature suggestion.

Would it be possible to add the capability for WSJTx to report to a second 
external program in addition to PSKreporter? I have an Android app that lets me 
keep tabs on what the radio is seeing whilst I am around the house or garden 
but to use it means I must disconnect from PSKreporter. It would be great if 
both were connected.  I monitor VHF activity and a close eye is required to 
catch brief openings however I also have a life so cannot sit in front of the 
radio all the time.

Thanks for all the work, looking forward to the new release.
73 Paul




Sent from my Samsung Galaxy smartphone.



 Original message 
From: Jon Anhold <mailto:j...@anhold.com>
Date: 30/05/2020 16:26 (GMT+00:00)
To: WSJT software development 
<mailto:wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] Feature Suggestion

Add some indicator to the separator line in the band activity window to show if 
it was "even/1st" or "odd/2nd".

Also, possibly, add an option to display the separator line even if no stations 
are decoded.

73 de KM8V

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Suggestion

[Paul Randall]

Another feature suggestion.

Would it be possible to add the capability for WSJTx to report to a second 
external program in addition to PSKreporter? I have an Android app that lets me 
keep tabs on what the radio is seeing whilst I am around the house or garden 
but to use it means I must disconnect from PSKreporter. It would be great if 
both were connected.  I monitor VHF activity and a close eye is required to 
catch brief openings however I also have a life so cannot sit in front of the 
radio all the time.

Thanks for all the work, looking forward to the new release.
73 Paul




Sent from my Samsung Galaxy smartphone.



 Original message 
From: Jon Anhold 
Date: 30/05/2020 16:26 (GMT+00:00)
To: WSJT software development 
Subject: [wsjt-devel] Feature Suggestion

Add some indicator to the separator line in the band activity window to show if 
it was "even/1st" or "odd/2nd".

Also, possibly, add an option to display the separator line even if no stations 
are decoded.

73 de KM8V
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Seeing calls from myself

[Paul Randall]

Yes, I have experienced receiving my own cq calls decoded as though they were 
another station, complete with waterfall trace. Every instance, 100%  
associated with watchdog timeout, which occurs part way through a TX period.

I appreciate a watchdog timeout needs to be far removed from normal 
communication activity of WSJT but surely, with such a time based system, there 
should be a way to synchronise start of watchdog to start of the communication 
TX sequence, so that a watchdog shutdown occurs at the end of a RX period, not 
part way through a TX period.

Thanks for all the work guys, looking forward to upgrading to the new release.
Paul

Sent from Mail for Windows 10

From: Christoph Berg
Sent: 26 May 2020 17:07
To: WSJT software development
Subject: Re: [wsjt-devel] Seeing calls from myself

Re: Chris Sullivan
> I've seen this a couple of times before on RC1, Windows 10-64.
>
> I responded to a CQ from VE3VN (Hold TX set, also auto seq & call 1st). Just
> after my transmission began I halted tx because I noticed he had called CQ
> WC, which I guess isn't me. Then I saw, in red in the band activity window,
> VE3VN VE3NRT FN03. I think WSJT-X must have received my signal through from
> the monitor (K3 here) while I was transmitting.

I've seen it a few times during the final cycle when the tx timeout
timer was hitting. It's not reproducible, though.

Is there a way to run wsjtx in full-duplex mode? That would be awesome
for QO-100 satellite operation where operators are actually supposed
to be listening to their own signals.

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT4 and FT8 Contesting

[Paul Randall]

Reino, Haha Yes, but no, but yes, but no ...
For QSO purposes, I think RRR and RR73 are identical, reception of either means 
QSO complete, LOG THE QSO.

R R R 73 de Paul G3NJV

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


From: Reino Talarmo 
Sent: Thursday, February 27, 2020 9:13:08 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] FT4 and FT8 Contesting


Hi Paul

I agree your comment on RRR or RR73 being confirmation of reception ”R” ack.
There is a minor difference though RR73 is “I am fully happy and don’t expect 
any further response from you”, while RRR is usually taken to mean “I received 
you confirmation, but I want to be sure that you received my confirmation as 
well (before logging this QSO)” and then 73 from you is that confirmation of 
confirmation. Some even want a 73 to that 73 as confirmation of the 
confirmation of the confirmation!

73, Reino oh3mA



From: Paul Randall [mailto:paulfrand...@hotmail.com]
Sent: 27. helmikuuta 2020 22:46
To: k...@arrl.net; WSJT software development 
Subject: Re: [wsjt-devel] FT4 and FT8 Contesting



”..And when one QSO partner repeats either R-10 or RRR or RR73, it is
his indication that he didn't copy the ack,”



Surely that statement is wrong.

You only send RRR or RR73 to CONFIRM receiving the other stations “R” ack, 
never to indicate no copy.

Sending R -10 means you copied the other stations report, you keep sending it 
until you get RRR or RR73. Once you get it, that’s the end of the QSO. Nothing 
else required. If you don’t get it, it isn’t a QSO.

I think the WSJT message exchange protocol is based on decades old moonbounce 
and MS procedures where 73 is simply a luxury that often isn’t affordable.



Best regards Paul



Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10





From: Jim Brown mailto:k...@audiosystemsgroup.com>>
Sent: Thursday, February 27, 2020 8:25:10 PM
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] FT4 and FT8 Contesting



On 2/27/2020 7:56 AM, Ron WV4P wrote:
> RR73 is not part of the exchange.

Wrong. The definition of a QSO is the exchange of callsign and one piece
of info by each party, and the acknowledgement of receipt by by each.
Each station must receive acknowledgement of the other's exchange. If
that "information" is the signal report, The first ack is the R in R-10,
the second, by the other station, is RRR or RR73. What is NOT required
is 73. But it IS required for each station to have copied the other's
ack. And when one QSO partner repeats either R-10 or RRR or RR73, it is
his indication that he didn't copy the ack, and the other station should
repeat the ack.

73, Jim K9YC




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT4 and FT8 Contesting

[Paul Randall]

”..And when one QSO partner repeats either R-10 or RRR or RR73, it is
his indication that he didn't copy the ack,”

Surely that statement is wrong.
You only send RRR or RR73 to CONFIRM receiving the other stations “R” ack, 
never to indicate no copy.
Sending R -10 means you copied the other stations report, you keep sending it 
until you get RRR or RR73. Once you get it, that’s the end of the QSO. Nothing 
else required. If you don’t get it, it isn’t a QSO.
I think the WSJT message exchange protocol is based on decades old moonbounce 
and MS procedures where 73 is simply a luxury that often isn’t affordable.

Best regards Paul

Sent from Mail for Windows 10


From: Jim Brown 
Sent: Thursday, February 27, 2020 8:25:10 PM
To: wsjt-devel@lists.sourceforge.net 
Subject: Re: [wsjt-devel] FT4 and FT8 Contesting

On 2/27/2020 7:56 AM, Ron WV4P wrote:
> RR73 is not part of the exchange.

Wrong. The definition of a QSO is the exchange of callsign and one piece
of info by each party, and the acknowledgement of receipt by by each.
Each station must receive acknowledgement of the other's exchange. If
that "information" is the signal report, The first ack is the R in R-10,
the second, by the other station, is RRR or RR73. What is NOT required
is 73. But it IS required for each station to have copied the other's
ack. And when one QSO partner repeats either R-10 or RRR or RR73, it is
his indication that he didn't copy the ack, and the other station should
repeat the ack.

73, Jim K9YC




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem with radio's audio input

[Paul Randall]

It may be unrelated but a station very local to me on 2m transmits a huge 
wideband splat of noise at the start of his FT8 transmissions. I think what I 
am hearing is all the noise in his shack, the fan in his qro linear etc, all 
picked up by his microphone which presumably is still plugged in. With speech 
compression this can make a lot of power before the FT8 tones start and 
suppress it.

Paul G3NJV


From: Reino Talarmo 
Sent: 02 December 2019 14:40
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] Problem with radio's audio input

The original mail stated:
"I'm seeing a kind of noise at the beginning of many of my transmission.
Anyone knows how I could verify if it is a problem with my radio, the sound
card (which is embedded in the radio I think) or the WSJT-X software?"
The video shows some kind of instability, perhaps a low frequency pulse
train generating a wide spectrum. Perhaps audio actually goes to the radio,
but causes some unwanted transient before normal operation. It even could be
an ALC issue, if the audio level is too high hitting ALC. I would not rule
out RF problems either.
73, Reino oh3mA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Callsign lockout

[Paul Randall]

When calling CQ dx on 80m at dusk (my loop is regularly heard in VK) there are 
local EU stations that give me just a single call then disappear, presumably 
just to be a PITA by triggering the "call 1st" feature on my rig. My answer is 
to switch it off. It means I have to sit in front of the radio and actually 
operate it but that is no different from any other mode.  It is easy to get 
reliant on the automation. The downside of my manual system means if i do 
respond to a caller my reaction time does usually mean a missed 30 second cycle 
and that isn't like other modes.
73 Paul.



Sent from my Samsung Galaxy smartphone.



 Original message 
From: Ron WV4P 
Date: 01/12/2019 00:18 (GMT+00:00)
To: Black Michael , WSJT software development 

Subject: Re: [wsjt-devel] Callsign lockout

This function has Desperately been needed for a long time. Ron, WV4P

On Sat, Nov 30, 2019, 4:21 PM Black Michael via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net>> 
wrote:
Was just communicating with an Alaskan operator who was complaining about 
operators calling him in the blind.  And when you have Call First checked the 
blind callers become a PITA.

What is needed is the ability to block a callsign for an adjustable time out 
period defaulting perhaps to 15 minutes. (don't even show them in the band 
activity).  Maybe it could be done with a ctrl-click on TX 1 or some other 
better method.  Turn off Enable, clear the DXCall box and then the next valid 
decode would be able to start up.

de Mike W9MDB


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

[Paul Randall]

Anyone who experiences peculiar behaviour from their station on some 
band/frequency/antenna/rig upon activating the transmitter should firstly 
perform this most basic test.

STEP 1A1A1 - Try to reproduce the problem with the transmitter directly 
connected to a dummy load. This test should virtually eliminate the possibility 
that simple EMI is the culprit (which it is in most cases).

Having suffered the problem myself, I know first hand that the above is 
excellent advice.

Kind regards and good DX to all,
Paul G3NJV




From: Jim Jennings 
Sent: 20 November 2019 16:55
To: WSJT software development 
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

The symptoms suggest to me RF getting into a USB cable between computer and the 
rig’s CI-V USB port.  My cousin had a similar situation with his FTDX-3000 on 
40 and 30M FT8, where the rig would abruptly quit transmitting if he tried to 
exceed about 25 watts.  The problem was solved by winding some of the “spare” 
length of the computer to CAT USB cable on a ferrite toroid (FT240-43 used in 
this case).  He can now increase to full output power of the rig (100W) without 
anything “flinching.”  Just a thought.  73,

Jim, W7XZ

From: Christopher Diederich via wsjt-devel
Sent: Wednesday, November 20, 2019 05:01
To: Paul Randall ; WSJT software development ; 
wsjt-devel-ow...@lists.sourceforge.net
Cc: Christopher Diederich
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

I will run it into a dummy load to check though. Thanks for the suggestion.

Chris

Get Outlook for iOS<https://aka.ms/o0ukef>



On Wed, Nov 20, 2019 at 7:53 AM -0500, "Christopher Diederich" 
 wrote:

I have not tested with a dummy load.  Other digital modes and phone don’t have 
the same issue, and SWR is 2.5:1 into OCF 80 meter dipole, which is tuned 
easily with my LDG.

Get Outlook for iOS<https://aka.ms/o0ukef>



On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall" 
 wrote:

Does it do it when the rig is running into a dummy load?



Sent from my Samsung Galaxy smartphone.


 Original message 
From: Christopher Diederich via wsjt-devel 
Date: 20/11/2019 01:59 (GMT+00:00)
To: wsjt-devel@lists.sourceforge.net, wsjt-devel-ow...@lists.sourceforge.net
Cc: Christopher Diederich 
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue


Get Outlook for iOS<https://aka.ms/o0ukef>

From: Christopher Diederich 
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue

Good evening,

I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes from USB-D to USB when keying. Any ideas?

IC-7300
Win 10 Pro 64 bit
HRD version 6.7.0.244
WSJT-X version 2.1.0

73
Chris Diederich K1LDO






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

[Paul Randall]

Does it do it when the rig is running into a dummy load?



Sent from my Samsung Galaxy smartphone.


 Original message 
From: Christopher Diederich via wsjt-devel 
Date: 20/11/2019 01:59 (GMT+00:00)
To: wsjt-devel@lists.sourceforge.net, wsjt-devel-ow...@lists.sourceforge.net
Cc: Christopher Diederich 
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue


Get Outlook for iOS

From: Christopher Diederich 
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue

Good evening,

I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes from USB-D to USB when keying. Any ideas?

IC-7300
Win 10 Pro 64 bit
HRD version 6.7.0.244
WSJT-X version 2.1.0

73
Chris Diederich K1LDO


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul Kube)

[Paul Randall]

Jim, your recommendation that all shack equipment uses a single source and 
green wire, like the high quality distribution illustrated in your PDF is spot 
on, thank you. I guess weather in the UK is pretty benign, although we do have 
our moments. I remember working in Poland; in February I was surprised to see 
the lightning protection. In August I understood why.



Kind regards

Paul G3NJV



Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10




From: Jim Brown 
Sent: Wednesday, August 14, 2019 8:12:05 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul 
Kube)

I would certainly hope that you would want it for your personal safety,
and for the non-destruction of your home and your equipment! It also
happens that proper bonding of equipment, and obtaining power for all
interconnected equipment from outlets that share the same green wire,
minimizes hum, buzz, and RFI. That is the focus of my advice.

Another observation. The prevalence of lightning varies widely around
the world, as shown on this map. Those of living in high frequency
strike areas pay a lot more attention to it than do others.

https://geology.com/articles/lightning-map.shtml
http://lightningsafety.com/nlsi_info/lightningmaps/US_FD_Lightning.pdf
http://lightningsafety.com/nlsi_info/lightningmaps/worldlightning.html

73, Jim K9YC

On 8/14/2019 4:52 AM, Paul Randall wrote:
> There is no requirement for lightning protection in all buildings in the
> UK although there are laws which govern businesses separately. As a
> result, the lightning protection in the average domestic UK home
> approximates to “none at all”,



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul Kube)

[Paul Randall]

Jim

There is no requirement for lightning protection in all buildings in the UK 
although there are laws which govern businesses separately. As a result, the 
lightning protection in the average domestic UK home approximates to “none at 
all”, as Douglas Adams would say.

Even with the open invitation of overhead power wire, telephone wire, satellite 
or TV aerial, installers bring the wires direct into the property with no 
ground or ground bonding. Most people get away with it and insurance companies 
make no requirements.

There are strict requirements for certification of electrical installers and 
installations and as a plain resident the general rule is “don’t mess with the 
power wiring Paul”. If I do my property may not pass the electrical inspection 
needed before it can be sold. This is apart from any other consequence and 
sadly I could find nothing in the Laws of Physics to make my trip work again if 
I bypass it.



73 Paul G3NJV



Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10




From: Jim Brown 
Sent: Tuesday, August 13, 2019 9:13:18 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul 
Kube)

Last I looked, the Laws of Physics still govern what happens when
lightning strikes. We have a similar issue with common practice by wired
telephone installers here in the former colonies failing to properly
bond their installations.

My recommendations are in line with those laws and the National Electric
Code, which has been adopted by local authorities through nearly all of
North America, and thus carries the force of law. If you find conflict
with my recommendations, I suggest that you may not fully understand them.

73, Jim K9YC

On 8/12/2019 7:26 PM, Paul Randall wrote:
> The advice is written and in the UK would render you liable to
> litigation in the event of an accident. That is why I say it is unwise.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul Kube)

[Paul Randall]

Jim, the PDF you attached has a huge amount of information thank you. However 
what I see is pages of illustrations of ground loops and how to short them out 
with big bonding straps. Does this prove they don't exist? For me it highlights 
them. Perhaps I missed something important in the language?


When utilities provide power to domestic premises their only concern is profit 
whilst complying with local safety regulations. They don't give a hoot for EMI 
or lightning protection. This is in contrast to the good engineering practice 
universally employed in professional equipment installations where all factors 
are taken into account and bonding reigns supreme.


Giving blanket advice to retrospectively interfere with domestic AC wiring and 
grounding IS risky unless you are completely appraised of all the relevant 
regulations and codes of practice that apply in every country and locality 
where people may be reading your advice. You also need to be aware of the 
requirements for certification in every country and locality that are needed to 
perform such modifications legally.


Jim, I thought your blanket ground bonding ideas in a domestic situation were 
unwise.  The advice given in the PDF on “Home Power Wiring, the green wire”  is 
clearly wrong and can be outright dangerous. Why? I checked my house wiring. 
All of the ground wires (green wires) in my house lead back to the 
switch/fuse/breaker panel where they connect to the primary safety device, a 
ground leakage circuit breaker, the other side of which goes to a PME bonded 
“ground” connection. The bonding recommended in the PDF (house ground to a 
"real" ground rod) bypasses this circuit breaker, rendering it inoperative and 
leaving the building occupants vulnerable to lethal electric shock. The advice 
is written and in the UK would render you liable to litigation in the event of 
an accident. That is why I say it is unwise.


In a professional installation the requirements for electrical safety, EMI, 
efficient RF grounding and lightning protection do not conflict. In a domestic 
situation they do. There may be no blanket solutions that apply everywhere, in 
all circumstances, in the domestic environment. This is not about good 
engineering practice, it is about how to work within electrical safety 
regulations and get as close as possible to what is needed in a good ham 
station.


My friend would turn up at locations all around the world, sometimes only 
minutes before a broadcast, armed with a battery of equipment designed to 
combat the hum and noise inducing ground loops he would surely encounter, 
without the luxury of time to re-engineer all the wiring in the vicinity.



Claude, I completely agree, a desktop will be much quieter at audio and RF and 
of course has a very obvious ground. The setup I describe had to be airline 
transportable for operating as VK2/G3NJV so I must use the (Lenovo) laptop. 
This has neither an internal chassis or a “D” connector. The only “grounded” 
metalwork visible are the HDMI and USB sockets, neither of which are accessible 
for bonding and which, upon inspection, connect to exactly the same internal 
PCB ground plane as the ground in the audio socket. Bond to a USB shell or the 
audio pin? Difference? Three inch wide copper strip to a USB or headphone on a 
laptop? Let's get real.



Let us not lose sight of the point of this discussion which is to try to 
transmit a nice clean signal without added hum and noise. In my case there was 
a simple solution to the problem I unexpectedly encountered with the isolated 
cable which was to link the gound from laptop to rig. Spectrum analyser 
software run on the computer can check for hum and noise on receive, asking a 
local ham to listen to your transmission is good on transmit.



One last point, how many people remember to disable their microphone when the 
PC is plugged to the accessory socket running WSJT-X? Listening in the FT8 
band, clearly lots of people don't.



Best regards Paul G3NJV



From: Jim Brown 
Sent: 11 August 2019 08:43
To: wsjt-devel@lists.sourceforge.net 
Subject: Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul 
Kube)

On 8/10/2019 6:09 PM, Paul Randall wrote:
> Jim
>
> Double insulated equipment like a laptop charger doesn’t have any
> physical access to a metal part that can be bonded to ground. That’s
> what double insulated means. Even if the charger has a 3 pin (hot,
> neutral and ground) AC connector there is little likelihood that the dc
> output side is connected to the ground pin.

That does not change the fact that chassis-to-chassis bonding is good
engineering practice, and audio interconnects should never be depended
on for bonding. One of the reasons that proper bonding is critical to
solve RFI and hum/buzz issies is the Pin One Problem. See my website for
a lot of detail on that, and point your broadcast engineer friend to
that, an

Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul Kube)

[Paul Randall]

Jim
Double insulated equipment like a laptop charger doesn’t have any physical 
access to a metal part that can be bonded to ground. That’s what double 
insulated means. Even if the charger has a 3 pin (hot, neutral and ground) AC 
connector there is little likelihood that the dc output side is connected to 
the ground pin. In this case using the laptop for WSJT relies on the connecting 
wire running from the laptop to the rig to provide a ground. If that wire is 
deliberately built to be isolated then it CAUSES a hum problem rather than 
avoids one. This is counter-intuitive and so even though it has nothing to do 
with software development, I felt it was worth contributing to the “bad signal” 
discussion going on in this forum.

As an aside, I think it very unwise to make a blanket statement that bonding 
everything together is good engineering practice. Someone reading that may 
unwittingly bypass a safety ground leakage circuit breaker by bonding the 
building’s safety ground to a radio antenna ground rod. Worse, large AC 
currents may flow in this connection if the power utility company uses one of a 
number of different PME (protective multiple earth) supply systems where the 
building’s safety ground is actually bonded to the neutral supply wire and only 
to “real” ground back at the supply transformer.

Finally, my friend gave a big grin when he read that “The concept of a 
so-called "ground loop" is completely false”. He is a professional sound and 
television broadcast engineer.
Cheers Paul G3NJV



Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Jim Brown<mailto:k...@audiosystemsgroup.com>
Sent: 08 August 2019 19:20
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals? (Paul 
Kube)

The concept of a so-called "ground loop" is completely false. It has no
basis in physics. The "buzz" we hear when equipment is not properly
bonded consists of triplen harmonics of the mains frequency, 50 or 60
Hz, depending on where you live. What DOES couple this trash is the
failure to follow proper engineering practice, which is to bond together
the chassis of every piece of equipment in a system, to bond all grounds
in a building, and to bond that combination of equipment to the
combination of building grounds. (my friends in the UK substitute the
word "earth" for "ground.") A second important part of good practice is
to get power for all interconnected equipment from mains (power) outlets
that have the same Green Wire (protected earth conductor), or whose
green wires are bonded together.

When all of this done, the station is safe for lightning, and no
"isolation" is needed.

Details of proper practice is at http://k9yc.com/GroundingAndAudio.pdf

73, Jim K9YC

On 8/8/2019 3:43 AM, Paul Randall wrote:
> The point of the isolated interface is to prevent noise/hum caused by
> ground loops but if there is no ground at all, it is not only useless
> but actually causes a big problem. I can only assume that if I saw lots
> of 50Hz spurs on receive, there was a good chance they were there on
> transmit as well.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lid operators or bad design?

[Paul Randall]

whoosh  - sharp intake of breath
Rich you are Sooo... picky,
73 = best regards
73s = more than one best regards
73's = 73, his best regards.

As I understand, 's is possesive, so "Richard's email" is shorthand for 
"Richard, his email". I'd love to be corrected.
Nice to see the new world is equally saddled with medieval language structures.
..But in a software forum, punctuation is crucial.
So you are forgiven.

My two cents worth is;-
Before I transmit I listen a lot and use the spectrum display to select slots 
that are "empty" on both time periods. I have the magic "hold tx freq" box 
checked most always. Sending CQ I use one of these frequencies and after a few 
cycles rest and check both time slots again. If I get no replies I use another 
frequency.

On every band each receiving station has an individual spectrum to deal with, 
close-in vs dx. It's impossible to know what the station on the other end is 
receiving. The only feedback is "is he replying to me?"

So, If I am calling a DX station on what I think is a clear frequency and 
getting no replies, I try another, and another. If still no success I think to 
myself, maybe he thinks like me, maybe I don't have to look for a clear 
frequency, the DX station has already done that and is CQ'ing on it, so I call 
on his frequency, unchecking the magic "hold tx freq" box. Not easy going 
forward as the software switches you off if it detects the DX is involved in 
another QSO. But sometimes it works immediately. The clever bit is to remember 
the magic box is unchecked as you go on your way afterward. At age 70 I don't 
think of myself as a LID, I have 50 years of operating experience in there 
somewhere but my usual memory addressing algorithm seems to have changed, maybe 
i missed the update, so ... I make mistakes.

Summary - I never have any expectation that this is "my" frequency, it is too 
dynamic. I run 100W to wire antennae so getting good dx QSOs without kW+ to a 
beam means being very flexible and frequency/time hopping, not just frequency 
warming. It is S done biologically hihi.

Regarding time slots, in Europe we try to obey a rule that stations beaming 
east use the odd slot (Tx even/1st check box UNCHECKED) and vice versa. I think 
this tallies with your convention.

Huge thanks to the WSJT software team

Regards,
Paul G3NJV



From: Rich Zwirko - K1HTV 
Sent: 29 July 2019 16:37
To: Mike - W9MDB Black ; WSJT 

Subject: Re: [wsjt-devel] Lid operators or bad design?

Hi Mike,
  Good on the note, but I'd correct the last line "73's".

73 means 'Best Regards'.
73's translates to "Best Regards's" (Regardses)  8-).
I know, picky, picky.

Regarding emailing 'educational' notes, I regularly do so to loud locals who 
call CQ on 6 Meter FT8 during the 1st & 3rd 15 second sequences when the band 
is open to Europe and Africa.

A TX sequencing convention for openings to Europe/Africa, has been agreed upon 
by the majority of 6M DXers. NA stations call CQ only during the 2nd & 4th 
sequences (Tx even/1st check box UNCHECKED). Very strong out of sequence 
stations cause the receiver's AGC to push very weak DX further into the noise. 
When all 6M DXers in the region are all using the same Tx sequence, we all have 
a better chance to decode weak DX signals.

Later in the day, when it looks like we have possible SSSP propagation to 
Japan, the sequencing convention is reversed. North American stations call CQ 
during the 1st & 3rd (Even) sequence. JA DXers religiously adhere to 
transmitting 2&4 to NA and 1&3 (Even) to Europe.

73,
Rich - K1HTV

= = =
On 7/28/2019 11:01 AM, Black Michael via wsjt-devel wrote:
Attribute it to inexperienceyou should contact them and help to politely 
educate them.

Something like
 Hi there OM,
Saw you in a QSO with  and after the QSO was complete you called CQ on the 
same offset.
You should consider working people in split by choosing a Tx offset that is 
clear of other signals (shift click will do that) in the waterfall and checking 
"Hold Tx Freq" to keep your offset constant.
Of course I'm sure you know that calling CQ on somebody else's frequency is a 
no-no.
73's
..

de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each transmission?

[Paul Randall]

Hi James, point taken, my comments were really aimed at traditional alc systems 
that are so prone to producing power spikes.

I have noticed many comments on this thread from people looking for software 
solutions to what look at first sight to be RFI issues. I'm not sure if it has 
been said before but a very simple test that could be recommended to anyone 
whose station is failing or performing strangely is to operate it into a dummy 
load. If the observed problem goes away this removes doubts about the software 
and the fickle finger would point directly at RFI as the culprit. Knowing this 
enables the sufferer to quickly get on the right road towards a solution.

Cheers Paul G3NJV

Sent from my Samsung Galaxy smartphone.


 Original message 
From: James Shaver 
Date: 12/04/2019 19:19 (GMT+00:00)
To: WSJT software development 
Subject: Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each 
transmission?

Hi Paul,

Good info (and similar to my own line of thinking in the response I just sent 
on ALC Overshoot) but I’d recommend one minor change:

Your statement “The best way to avoid spikes in any rig using FT8...” - I’d be 
cautious with the “any rig” generalization.  Some of the popular radios on the 
market with a closed loop power system like the Elecraft K-line and KX-line 
will actually “power hunt” if the ALC meter is not showing 3-4 bars of activity 
on the ALC meter.  The first 4 bars of the ALC meter on the K/KX-line radios 
function like a vu meter and not necessarily indicate ALC action.  The radio 
itself may actually overmodulate the signal in order to get the power output 
set by the power output control and cause a transmitted signal to be quite 
poor.  I was able to test this using my K3 and KX3 into a dummy load and 
viewing the signal output with a spectrum analyzer and the term for the signal 
produced with “0” bars of “ALC” showing was “icky” at best (very technical, I 
know :) ).

Just a word of caution for anyone following this thread.

73,

Jim S.
N2ADV

On Apr 12, 2019, at 2:06 PM, Paul Randall 
mailto:paulfrand...@hotmail.com>> wrote:

Start-of- transmission power spikes will almost certainly occur on any radio 
which is using traditional alc to control output power. Spike severity is 
directly linked to the amount of gain reduction the alc is giving. For example, 
 a 100w rig with power output reduced to 5w using a power control which 
operates via the alc system can be almost relied upon to produce 100w spikes at 
start of transmission. No brainer.

The best way to avoid spikes in any rig using FT8 is to carefully adjust audio 
drive level in the software until desired power output is obtained without the 
rig applying any alc at all. In this way overall system gain is only sufficient 
to produce desired power and no more - so spikes are eliminated and you get a 
cleaner transmission.

That said, I say again that I can exactly  reproduce this problem at will on 
160m where my antenna system clearly puts large voltage onto the cable between 
the pc and the rig. My interface uses industrial quality logic isolators for 
civ and ptt together with audio isolation transformers and dozens of ferrite 
rings on tuner - rig - pc cables.  RFI still gets through and kills the usb 
connection on 160m.  To cure this I will rethink the 160m antenna which I 
suspect is the easiest way.

Regards Paul G3NJV

Sent from my Samsung Galaxy smartphone.


 Original message 
From: Bill Barrett mailto:w2pky...@gmail.com>>
Date: 12/04/2019 18:11 (GMT+00:00)
To: fr...@fkirschner.net<mailto:fr...@fkirschner.net>, WSJT software 
development 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each 
transmission?

>From W8JI.com<http://W8JI.com>, maybe 5000 has similar adjustments. If the IF 
>Transmit Gain was too high the 1000 would exhibit huge power spikes on key 
>down or pressing the mike PTT button.

Transmit Gain Menus

The FT-1000 MK V  has hidden transmit gain menus. They are accessed by pushing 
and holding FAST and LOCK while turning the POWER switch on. Both of my MK V's  
and every MK V serviced here has had the TX IF gain set too high. This causes 
first character clicks on CW and spits and splatter on SSB.  Here is how to 
correct the IF gain to prevent ALC clipping on leading edges of CW and voice:

Press and hold FAST and LOCK before and during initial POWER on.

Press FAST and ENT at the same time. You are now in the MENU's and the display 
should say "0-1 GrPI-cH".

Turn the VRF/MEM CH counter-clockwise to 9-2. The display should say "t iF - GA 
in" This is the transmit IF gain menu.

Turn the SUB VFO knob clockwise one position to  " t iF - 018". This is the 
1.8MHz transmit IF gain.

Press the ALC/COMP meter selector until the bar graph says "ALC".  Set RF PWR 
knob to full power.

With the radio 

Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each transmission?

[Paul Randall]

Start-of- transmission power spikes will almost certainly occur on any radio 
which is using traditional alc to control output power. Spike severity is 
directly linked to the amount of gain reduction the alc is giving. For example, 
 a 100w rig with power output reduced to 5w using a power control which 
operates via the alc system can be almost relied upon to produce 100w spikes at 
start of transmission. No brainer.

The best way to avoid spikes in any rig using FT8 is to carefully adjust audio 
drive level in the software until desired power output is obtained without the 
rig applying any alc at all. In this way overall system gain is only sufficient 
to produce desired power and no more - so spikes are eliminated and you get a 
cleaner transmission.

That said, I say again that I can exactly  reproduce this problem at will on 
160m where my antenna system clearly puts large voltage onto the cable between 
the pc and the rig. My interface uses industrial quality logic isolators for 
civ and ptt together with audio isolation transformers and dozens of ferrite 
rings on tuner - rig - pc cables.  RFI still gets through and kills the usb 
connection on 160m.  To cure this I will rethink the 160m antenna which I 
suspect is the easiest way.

Regards Paul G3NJV

Sent from my Samsung Galaxy smartphone.


 Original message 
From: Bill Barrett 
Date: 12/04/2019 18:11 (GMT+00:00)
To: fr...@fkirschner.net, WSJT software development 

Subject: Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each 
transmission?

>From W8JI.com, maybe 5000 has similar adjustments. If the IF Transmit Gain was 
>too high the 1000 would exhibit huge power spikes on key down or pressing the 
>mike PTT button.

Transmit Gain Menus

The FT-1000 MK V  has hidden transmit gain menus. They are accessed by pushing 
and holding FAST and LOCK while turning the POWER switch on. Both of my MK V's  
and every MK V serviced here has had the TX IF gain set too high. This causes 
first character clicks on CW and spits and splatter on SSB.  Here is how to 
correct the IF gain to prevent ALC clipping on leading edges of CW and voice:

Press and hold FAST and LOCK before and during initial POWER on.

Press FAST and ENT at the same time. You are now in the MENU's and the display 
should say "0-1 GrPI-cH".

Turn the VRF/MEM CH counter-clockwise to 9-2. The display should say "t iF - GA 
in" This is the transmit IF gain menu.

Turn the SUB VFO knob clockwise one position to  " t iF - 018". This is the 
1.8MHz transmit IF gain.

Press the ALC/COMP meter selector until the bar graph says "ALC".  Set RF PWR 
knob to full power.

With the radio on CW and a 50 ohm dummy load connected, close the key and 
adjust the MAIN VFO-A knob until the ALC display is about 75-85% of full scale 
on the illuminated bar marked "ALC".

Press the next band button (3.5), make sure the radio is still  on CW, and turn 
the SUB VFO-B knob clockwise one band to "t iF - 035".

Again adjust MAIN VFO-A until ALC is at 75-85% of full scale.

Repeat this process through all bands.

Most radios I have tested require a setting of 2 to 4 on TX IF gain, with 3 
being the most common setting.

This change will reduce SSB bandwidth and distortion. It will also reduce 
keyclicks and annoying thumps on the leading edge of each Morse character.

 Hope this helps;

Bill W2PKY

On Fri, Apr 12, 2019 at 12:38 PM Frank Kirschner 
mailto:frank.kirsch...@gmail.com>> wrote:
Some rigs, even high-end rigs including the FTdx5000, exhibit a spike on 
initial transmit. I noticed it mostly with the amp. The power would surge 
briefly, and then return to the dial value.

I suspect the combination of the surge and a bit of RFI is causing the problem. 
I suggest an opto-isolator on both ends of your CAT cable. They are available 
for RS-232 and USB. That, plus some ferrites along the run should help with the 
problem. Also, if you're using a desktop, try running several ground straps to 
the case of the computer. Consumer-grade computers aren't very resistant to 
RFI, and there is no bonding between the pieces of sheet metal.

73,
Frank
KF6E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Does the FT8 signal spike at the beginning of each transmission?

[Paul Randall]

Ed

I can reproduce this on my setup where my antenna is not good for 160m - 
causing bad RFI which crashes the USB audio link to the PC. If I start 
transmission on 160m with very low power and ease it up I get almost to full 
power before the link fails.



I’ve seen no evidence of a spike, actually my observation suggests the 
commencement of audio seems to be shaped to avoid one.



My guess is that you have RF feedback problems.



Kind regards

Paul G3NJV



Sent from Mail for Windows 10




From: Ed Stokes 
Sent: Friday, April 12, 2019 7:05:54 AM
To: WSJT software development
Subject: [wsjt-devel] Does the FT8 signal spike at the beginning of each 
transmission?

I’m curious about something I observe about the FT8 signal modulation.

It appears to produce a pronounced spike in the audio at the beginning of each 
15 second transmission.

When I operate on 160, 80 and 40 meters especially this spike will cause the 
program to stop producing audio.  My computer, a mac mini, is relatively close 
to the 160m dipole being used on these bands, about 50 feet.

If I throttle back to -41 dB or so I can make the transmission begin without 
stopping the audio, although the spike is still evident.

If I then gradually increase the “Pwr” slider I can increase the power without 
causing the audio to crash.

If I leave the power increased the audio will crash immediately after the next 
transmission period begins.

Is this a known problem?

73, Ed
W1KOK

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Error in Sound Output Message

[Paul Randall]

Hi, as others have suggested, almost certain reason for this is during the 1 – 
2 seconds of transmit that you got, your RF took out the USB link between sound 
card and PC.

I can generate this problem on demand just by trying to operate on 160m where 
my loop antenna is extreme high impedance and the rig gets “hot” to RF.

Quit WSJT, unplug the USB interface and replug after a few moments, restart 
WSJT and if necessary use “menu-settings-audio” to direct audio connections 
back to the USB interface should get everything working on Rx.

Of course the RFI problem on TX still needs to be fixed. Check all your 
grounding and run an antenna analyser to see if anything changed out there. As 
suggested, moving stuff around, a bad ground connection, even wind and rain can 
push a marginal system over the edge. Working portable as VK2/G3NJV with a 
simple wire antenna, the dog used to run over and move the tuned radial wires 
lying on the grass and up would pop this problem even though everything worked 
fine just before.

Cheers
73s Paul G3NJV


From: Richard Solomon 
Sent: Saturday, April 6, 2019 3:30:32 PM
To: wsjt-devel
Subject: [wsjt-devel] Error in Sound Output Message

Everything was working fine yesterday, turned the rig on tday, tried to call
a station, Transmit was aborted about 1-2 seconds into the call.

This error message popped up:

[cid:b5548389-7bda-4cc5-8ef8-073d197cddd3]

Any idea on the cause ?

Tnx, Dick, W1KSZ

Sent from Outlook
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sudden call replacement

[Paul Randall]

Hi Phil, this happens to me 2 or 3 times in a session.
To be specific, all message boxes are always correctly filled with the my own 
and my qso partners callsigns. When the problem occurs, the message appears in 
the "rx frequency" window with the qso partners callsign replaced with someone 
elses.  Sometimes this completely prevents calling a particular station as the 
"wrong" callsign goes out right from the start in message 1. Other times the 
switch occurs mid qso and usually causes the qso to get stuck in an endless 
exchange of messages. It is what I described as "callsign hijacking" in my 
email of 24th January this year.
I have found the only reliable way to escape the condition is abandon the qso 
and stop trying to work that station as the condition recurs if you come back 
some time later for another try. On one occasion I was able to complete the qso 
by editing the outgoing message 5 box to swap the angle brackets <> from the 
affected callsign to the other.



73 Paul VK2/G3NJV



Sent from my Samsung Galaxy smartphone.
 Original message 
From: t...@gmx.fr
Date: 07/02/2019 03:53 (GMT+10:00)
To: wsjt devel list 
Subject: [wsjt-devel] Sudden call replacement

Hi,

I was having QSO with 3G3G.

All of a sudden the call 3G3G was replaced by IV3ONZ on the same frequency.

I tried to restore the proper call sign by clicking on the call sign in the Rx 
Frequency box. No ways!

Strangely, just after I did it, <3G3G>  ZS1/F5FDV RRR appeared in the Tx4 box 
but it was  ZS1/F5FDV RRR that was displayed in the Rx Frequency box.

Screen copy attached.

73
Phil F5FDV

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Reporting to PSK Reporter

[Paul Randall]

Bill, many thanks for providing the link to that information, your suggestion 
works thank you.

I’m not sure what you mean by “ ..not bother reading..” as following the link 
you gave in your email allowed me to see your message for the first time.

My experience of trying to send own messages either by using the second tab or 
in message 5 is not good. I find juggling the drop down box, correcting the 
“enable tx” button, disabling auto sequence and retyping when the program 
overwrites what I typed before, all in 15 seconds results in lots of incorrect 
standard messages along with truncated and garbage own messages being 
transmitted.  Trying out your suggestion today I found another complication, 
after selecting my own tx macro in message 5, using the mouse to select “File – 
Settings – any tab do nothing - click OK” switches on the auto-sequence box and 
resets message 5.

Many thanks for taking the time to answer my query, my time here in Australia 
is coming to an end so with a standard callsign hopefully I will not need so 
many workarounds in future.

Best 73, Paul G3NJV




Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


From: Bill Somerville 
Sent: Thursday, January 31, 2019 10:34:59 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT Reporting to PSK Reporter

On 30/01/2019 23:23, Paul Randall wrote:
Bill, in one of your messages to Phil you wrote “...You can be spotted on PSK 
Reporter using a non-standard callsign by using one of the mechanisms I stated 
above” Where can I see those mechanisms please?

Paul,

it was this message a few days back:

https://sourceforge.net/p/wsjt/mailman/message/36526197/

follow the links therein, in fact one of the links is to a reply I gave to one 
of your prior queries on this issue which apparently did not bother reading.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Reporting to PSK Reporter

[Paul Randall]

Hi Phil
It says in the WSJT v2 user guide section 7.5 “WSJT-X 2.0 offers no support for 
two nonstandard callsigns to work each other” so this is a well known 
limitation.

I do not understand the logic that WSJT does not give reception reports to PSK 
reporter unless a QRA and callsign exist in a single message whereas all QSOs 
made with my type B callsign are valid without any QRA locator information 
being exchanged at all?

I wonder if anyone else has experienced what I call “callsign hijacking” where 
mid way through a QSO you start transmitting the wrong “other station” 
callsign. The message boxes are all filled correctly yet the wrong callsign 
appears to be transmitted and brings the QSO to a halt. Restarting the program 
and abandoning the QSO seems to be the only way to stop it. Presumably this is 
an unwanted result of using hash codes.

As it stands v2.0.0 does a lot for “normal” callsign holders but is really 
quite tricky if you have a type B callsign.  I have used FT8 a lot whilst 
operating from Australia with simple wire antennas and it has allowed me to 
work around the globe. However, tuning across 17m this evening the band was 
absolutely empty - until I hit 18100 and the S meter almost hit the stops. For 
a weak signal mode there are a lot of powerful stations crowded into that 3kHz 
and I felt sad the popularity of FT8 seems to have emptied the band of SSB 
stations.

Paul G3NJV

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


From: t...@gmx.fr 
Sent: Thursday, January 24, 2019 7:26:59 PM
To: wsjt-devel@lists.sourceforge.net
Cc: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT Reporting to PSK Reporter

Hi,

Paul, I have the same issue when I use the call ZS1/F5FDV.

Since december last year I was wondering why I get only few reports from 
PSKReporter.
Your post provides a very relevant the explanation, in my opinion.

Reporting went well with revisions prior to 2.0.

It seems consistent with the statement that it is now impossible to make proper 
QSO between two type B stations (see previous posts from me to the group). I 
think that there is a weakness in the coding or decoding of type B call signs. 
Decoding maybe, because reporting of these stations by WSJT-X to PSKReporter do 
no happen.

73,

Phil F5FDV

Envoyé: jeudi 24 janvier 2019 à 03:50
De: "Paul Randall" 
À: "wsjt-devel@lists.sourceforge.net" 
Objet: [wsjt-devel] WSJT Reporting to PSK Reporter
 Hi, I got this address from the WSJT website. I am new to this group 
and not sure of the protocols. I tried emailing yesterday but am unsure if this 
was received.

I am operating as VK2/G3NJV. After upgrading to v2.0.0 I found reports of my 
transmissions almost disappeared from PSK Reporter. I now get just a handful of 
reports all from stations NOT using WSJT. Most of these come from stations 
using “Red Pitaya FT8 TRX 1.0”. I spoke to Philip Gladstone about this and he 
told me that WSJT does not send reception reports to PSK Reporter unless it 
receives callsign and locator in a single message. It is impossible for me to 
transmit a message like this. Because I have a type B callsign, all that will 
fit in a single message is “CQ VK2/G3NJV”

This seems a particularly harsh outcome for type B callsign holders upgrading 
to v2.0.0. who, like me, are often operating portable stations with makeshift 
antennas where reception reports are extremely valuable. The reports from 
stations using a Red Pitaya are perfectly acceptable and I’m not sure of the 
reasoning behind the current WSJT “callsign + QRA” rule. Would it be possible 
to modify this to allow reception reports for type B callsigns received without 
a QRA?

Many thanks for your attention.
Paul Randall
G3NJV

PS After completing this email I checked the PSK Reporter website again. Sure 
enough there were just 5 reception reports, four from monitors using Red Pitaya 
but also a single report from K1HTV  using WSJT-X v2.0.0 784f75. This is the 
only WSJT reception report seen since 10 December so now I’m not sure what is 
going on!
___ wsjt-devel mailing list 
wsjt-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT Reporting to PSK Reporter

[Paul Randall]

 Hi, I got this address from the WSJT website. I am new to this group 
and not sure of the protocols. I tried emailing yesterday but am unsure if this 
was received.

I am operating as VK2/G3NJV. After upgrading to v2.0.0 I found reports of my 
transmissions almost disappeared from PSK Reporter. I now get just a handful of 
reports all from stations NOT using WSJT. Most of these come from stations 
using “Red Pitaya FT8 TRX 1.0”. I spoke to Philip Gladstone about this and he 
told me that WSJT does not send reception reports to PSK Reporter unless it 
receives callsign and locator in a single message. It is impossible for me to 
transmit a message like this. Because I have a type B callsign, all that will 
fit in a single message is “CQ VK2/G3NJV”

This seems a particularly harsh outcome for type B callsign holders upgrading 
to v2.0.0. who, like me, are often operating portable stations with makeshift 
antennas where reception reports are extremely valuable. The reports from 
stations using a Red Pitaya are perfectly acceptable and I’m not sure of the 
reasoning behind the current WSJT “callsign + QRA” rule. Would it be possible 
to modify this to allow reception reports for type B callsigns received without 
a QRA?

Many thanks for your attention.
Paul Randall
G3NJV

PS After completing this email I checked the PSK Reporter website again. Sure 
enough there were just 5 reception reports, four from monitors using Red Pitaya 
but also a single report from K1HTV  using WSJT-X v2.0.0 784f75. This is the 
only WSJT reception report seen since 10 December so now I’m not sure what is 
going on!
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FW: WSJT-X V2.0.0 WINDOWS 10 REPORT

[Paul Randall]

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


From: Paul Randall
Sent: Wednesday, January 23, 2019 9:38:41 AM
To: wsjt-devel@lists.sourceforge.net
Subject: WSJT-X V2.0.0 WINDOWS 10 REPORT

Hi, I am operating as VK2/G3NJV and discover that because I am a type B 
callsign, I cannot include my callsign and QRA locator in a single message. 
This in turn prevents anyone using WSJT-X V2.0.0 from reporting to PSK 
Reporter. I have spoken to Philip Gladstone about this and he confirms that the 
current version requires callsign and locator in a message before reporting.

Using V1.9 there was not this problem. Monitor stations using Red Pitaya 
software also do not have this problem and these are the only reception reports 
that I can get – perhaps a dozen globally.

This seems a particularly harsh outcome for type B callsign holders who, like 
me, are often operating portable stations with makeshift antennas where 
reception reports are extremely valuable. I’m sure it would only take a line or 
two of code to allow class B callsigns to be reported without the QRA 
information, as Red Pitaya does.

Many thanks for your attention.
Paul Randall
G3NJV

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986>for Windows 10

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel