Re: [wsjt-devel] r8603 power at qso start

[Black Michael via wsjt-devel]

Your picture didn't come through.  But I did another collection using Audacity 
via WASAPI and don't see it now.The reason I looked was an apparent power jump 
on my wattmeter at the start of the transmission.Now that I'm watching via 
WASAPI I don't see the power jump anymore.  Quit Audacity and the power jump 
comes back.Getting very irregular behavior.  That starting amplitude sometimes 
come in at 0.5V, sometimes at 0.1, sometimes at 1.0 -- can't quite find a 
repeatable pattern.  I guess I'd like to record directly from WSJT-X to see if 
there's a comparison to be had.
And a friend of mine with an IC7300 was seeing the same thing on his rig too.  
Plus others have now chimed in and said they see the power jump too.  Could it 
be random?  What determines the level of the preamble?





 

On Thursday, April 5, 2018, 9:08:53 PM CDT, Steven Franke 
 wrote:  
 
 Hi Mike, 
I don’t see any evidence of problems when I look at the WSJT-X Tx audio 
directly. I’ve attached a screen shot showing my recording of the Tx audio. I 
captured this audio by routing the WSJT-X TX audio through SoundFlower (an 
audio loopback device) and into the Audacity sound editor on my OS X machine. 
This plot shows about 700ms of audio.  
Steve k9an


On Apr 5, 2018, at 10:43 PM, Black Michael via wsjt-devel 
 wrote:
I found that this is related to the Tx delay settings.
The lower the Tx delay setting (< 0.2) the more max amplitude at the  beginning 
of the audio.
At 0.2 there's just a small portion but this may help explain why many people 
have RF problems when Tx starts.
<1522968118900blob.jpg>
de Mike W9MDB

 

<1522968118900blob.jpg>--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] About upcoming test

[jarmo]

Seems, that propagation might not be gently.
But IF can copy, would like to know FOX's TX power...
Just for compare signals... At the moment from
southern EU and from some eastern stations gives +19dB
readings...

Jarmo

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Gene Marsh]

WSJT-X or your sound card?  

73 de W8NET Gene
3905 Century Club Master #47
Portage County Amateur Radio Service (PCARS) since 2008
ARRL A-1 Op

> On Apr 5, 2018, at 11:37 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> I captured the output from WSJT-X via the VoiceMeter Banana port to my SDR 
> (ANAN 100).
> So it's an exact digital copy of what WSJT-X is producing.
> 
> Mike
> 
> 
> 
> 
> 
> On Thursday, April 5, 2018, 6:11:58 PM CDT, Bill Somerville 
>  wrote:
> 
> 
>> On 05/04/2018 23:43, Black Michael via wsjt-devel wrote:
>> I found that this is related to the Tx delay settings.
>> 
>> The lower the Tx delay setting (< 0.2) the more max amplitude at the  
>> beginning of the audio.
>> 
>> At 0.2 there's just a small portion but this may help explain why many 
>> people have RF problems when Tx starts.
>> 
>> 
>> de Mike W9MDB
>> 
> 
> Hi Mike,
> 
> what are we looking at here, how did you capture the audio you showed a plot 
> of?
> 
> 73
> Bill
> G4WJS.
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Black Michael via wsjt-devel]

I captured the output from WSJT-X via the VoiceMeter Banana port to my SDR 
(ANAN 100).So it's an exact digital copy of what WSJT-X is producing.
Mike



 

On Thursday, April 5, 2018, 6:11:58 PM CDT, Bill Somerville 
 wrote:  
 
  On 05/04/2018 23:43, Black Michael via wsjt-devel wrote:
  
  I found that this is related to the Tx delay settings. 
  The lower the Tx delay setting (< 0.2) the more max amplitude at the  
beginning of the audio. 
  At 0.2 there's just a small portion but this may help explain why many people 
have RF problems when Tx starts. 
  
  de Mike W9MDB
   

 
Hi Mike,
 
what are we looking at here, how did you capture the audio you showed a plot of?
 
73
 Bill
 G4WJS.
 
 --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Steven Franke]

Hi Mike, 

I don’t see any evidence of problems when I look at the WSJT-X Tx audio 
directly. I’ve attached a screen shot showing my recording of the Tx audio. I 
captured this audio by routing the WSJT-X TX audio through SoundFlower (an 
audio loopback device) and into the Audacity sound editor on my OS X machine. 
This plot shows about 700ms of audio.  

Steve k9an


> On Apr 5, 2018, at 10:43 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> I found that this is related to the Tx delay settings.
> 
> The lower the Tx delay setting (< 0.2) the more max amplitude at the  
> beginning of the audio.
> 
> At 0.2 there's just a small portion but this may help explain why many people 
> have RF problems when Tx starts.
> 
> <1522968118900blob.jpg>
> de Mike W9MDB
> 
> 
> 
> <1522968118900blob.jpg>--
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Ed Wilson via wsjt-devel]

I guess this is why I did not see a power increase since I have never changed 
the default delay of 0.2 sec. I also used the “eyeball” method of observing the 
signal in the time domain rather than an oscilloscope, so I probably missed the 
initial spike in power.

> On Apr 5, 2018, at 6:43 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> I found that this is related to the Tx delay settings.
> 
> The lower the Tx delay setting (< 0.2) the more max amplitude at the  
> beginning of the audio.
> 
> At 0.2 there's just a small portion but this may help explain why many people 
> have RF problems when Tx starts.
> 
> <1522968118900blob.jpg>
> de Mike W9MDB
> 
> 
> 
> <1522968118900blob.jpg>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Bill Somerville]

On 05/04/2018 23:43, Black Michael via wsjt-devel wrote:

I found that this is related to the Tx delay settings.

The lower the Tx delay setting (< 0.2) the more max amplitude at the  
beginning of the audio.


At 0.2 there's just a small portion but this may help explain why many 
people have RF problems when Tx starts.


Inline image
de Mike W9MDB


Hi Mike,

what are we looking at here, how did you capture the audio you showed a 
plot of?


73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Black Michael via wsjt-devel]

I found that this is related to the Tx delay settings.
The lower the Tx delay setting (< 0.2) the more max amplitude at the  beginning 
of the audio.
At 0.2 there's just a small portion but this may help explain why many people 
have RF problems when Tx starts.

de Mike W9MDB

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] possible bugs in WSJT-X 1.9.0-rc3

[dgb]

While I'm not running the same hardware, and running win 10, I've had 
the same two things happen to me several times. In addition I've had 
Halt Tx not halt.


tnx 73 Dwight NS9I


On 4/5/2018 1:37 AM, Scott Davis wrote:

Hi.

I just joined this list.  I'm enjoying using FT8 on HF bands.  Many thanks to 
Joe Taylor and Steve Franke.  I'd like to report what I think is buggy behavior 
in the FT8 auto-sequencing state machine.  In future I hope to contribute to 
development of this very cool software.

Environment

My radio is a Flex 6300.  My computer is a MacBook Pro running macOS 10.12.6.  I'm using 
VMware Fusion Pro 8.5.10 to run a Windows 8.1 VM, which is up-to-date with 
"important" patches.  I'm using SmartSDR 1.11.12 and WSJT-X 1.9.0-rc3.

Example 1

In the following QSO, I responded to his CQ but didn't hear back right away and 
disabled transmission.  A minute later I received a -19 signal report from him 
(A) and double-clicked on it.  The software sent a -20 signal report to him 
(B).  I think it should have sent R-20, with an R.  (Nonetheless, the QSO 
proceeded to a successful conclusion.)

015730 -20 -0.2 1378 ~  CQ N0GOS DN70
015747  Tx  2258 ~  N0GOS W6SDD DN70
015815  Tx  2258 ~  N0GOS W6SDD DN70
...
015930 -20 -0.2 1377 ~  W6SDD N0GOS -19  <<-- (A)
015946  Tx  2258 ~  N0GOS W6SDD -20  <<-- (B)
020015  Tx  2258 ~  N0GOS W6SDD -20
020030 -22 -0.3 1377 ~  W6SDD N0GOS R-22
020046  Tx  2258 ~  N0GOS W6SDD RRR
020100 -20 -0.3 1377 ~  W6SDD N0GOS 73
020115  Tx  2258 ~  N0GOS W6SDD 73

Example 2

This next QSO proceeded normally up to the point where he sent RRR and I sent 
73.  I have the software configured to disable transmission once I have sent 
73.  A minute later he sent RRR again (C).  I double-clicked on it.  The 
software sent him an R-18 signal report (D).  I think it should have sent 73.  
I selected 73 from the list of messages and the software sent 73 on my next 
turn.

041145 -17  0.4 1433 ~  CQ KK4EUN EM60
041201  Tx  2228 ~  KK4EUN W6SDD DN70
041215 -15  0.4 1433 ~  W6SDD KK4EUN -23
041230  Tx  2228 ~  KK4EUN W6SDD R-15
041245 -20  0.4 1433 ~  W6SDD KK4EUN RRR
041300  Tx  2228 ~  KK4EUN W6SDD 73
041315 -10  0.4 1423 ~  F8NHF KE8EF R-04
041415  -7  0.4 1423 ~  F8NHF KE8EF 73
041415 -18  0.3 1433 ~  W6SDD KK4EUN RRR   <<-- (C)
041432  Tx  2228 ~  KK4EUN W6SDD R-18  <<-- (D)
041500  Tx  2228 ~  KK4EUN W6SDD 73

I hope this is helpful.

Best regards,

Scott Davis
W6SDD


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel






--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[Ed Wilson via wsjt-devel]

I built r8603 this morning and in a limited amount of operating FT8 on 80 and 
30 meters, the output power seems to be rock solid. I run a Flex-6700 but that, 
of course, should not matter..
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/ 

On Thursday, April 5, 2018, 1:09:29 PM EDT, rjai...@gmail.com 
 wrote:  
 
 I thought it was just me, but yes I also see this.
RiaN2RJ
On Thu, Apr 5, 2018 at 1:01 PM, Black Michael via wsjt-devel 
 wrote:

Running R8603 and seeing a power level that seems too high at start of 
transmission (both Tune and standard messages on FT8).This is about 50% more 
power than the rest of the signal being transmitted.Is this intentional?




de Mike W9MDB


-- -- --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
__ _
wsjt-devel mailing list
wsjt-devel@lists.sourceforge. net
https://lists.sourceforge.net/ lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] possible bugs in WSJT-X 1.9.0-rc3

[Scott Davis]

Hi.

I just joined this list.  I'm enjoying using FT8 on HF bands.  Many thanks to 
Joe Taylor and Steve Franke.  I'd like to report what I think is buggy behavior 
in the FT8 auto-sequencing state machine.  In future I hope to contribute to 
development of this very cool software.

Environment

My radio is a Flex 6300.  My computer is a MacBook Pro running macOS 10.12.6.  
I'm using VMware Fusion Pro 8.5.10 to run a Windows 8.1 VM, which is up-to-date 
with "important" patches.  I'm using SmartSDR 1.11.12 and WSJT-X 1.9.0-rc3.

Example 1

In the following QSO, I responded to his CQ but didn't hear back right away and 
disabled transmission.  A minute later I received a -19 signal report from him 
(A) and double-clicked on it.  The software sent a -20 signal report to him 
(B).  I think it should have sent R-20, with an R.  (Nonetheless, the QSO 
proceeded to a successful conclusion.)

015730 -20 -0.2 1378 ~  CQ N0GOS DN70
015747  Tx  2258 ~  N0GOS W6SDD DN70
015815  Tx  2258 ~  N0GOS W6SDD DN70
...
015930 -20 -0.2 1377 ~  W6SDD N0GOS -19  <<-- (A)
015946  Tx  2258 ~  N0GOS W6SDD -20  <<-- (B)
020015  Tx  2258 ~  N0GOS W6SDD -20
020030 -22 -0.3 1377 ~  W6SDD N0GOS R-22
020046  Tx  2258 ~  N0GOS W6SDD RRR
020100 -20 -0.3 1377 ~  W6SDD N0GOS 73
020115  Tx  2258 ~  N0GOS W6SDD 73

Example 2

This next QSO proceeded normally up to the point where he sent RRR and I sent 
73.  I have the software configured to disable transmission once I have sent 
73.  A minute later he sent RRR again (C).  I double-clicked on it.  The 
software sent him an R-18 signal report (D).  I think it should have sent 73.  
I selected 73 from the list of messages and the software sent 73 on my next 
turn.

041145 -17  0.4 1433 ~  CQ KK4EUN EM60
041201  Tx  2228 ~  KK4EUN W6SDD DN70
041215 -15  0.4 1433 ~  W6SDD KK4EUN -23
041230  Tx  2228 ~  KK4EUN W6SDD R-15
041245 -20  0.4 1433 ~  W6SDD KK4EUN RRR
041300  Tx  2228 ~  KK4EUN W6SDD 73
041315 -10  0.4 1423 ~  F8NHF KE8EF R-04
041415  -7  0.4 1423 ~  F8NHF KE8EF 73
041415 -18  0.3 1433 ~  W6SDD KK4EUN RRR   <<-- (C)
041432  Tx  2228 ~  KK4EUN W6SDD R-18  <<-- (D)
041500  Tx  2228 ~  KK4EUN W6SDD 73

I hope this is helpful.

Best regards,

Scott Davis
W6SDD


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r8603 power at qso start

[rjai...@gmail.com]

I thought it was just me, but yes I also see this.

Ria
N2RJ

On Thu, Apr 5, 2018 at 1:01 PM, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Running R8603 and seeing a power level that seems too high at start of
> transmission (both Tune and standard messages on FT8).
> This is about 50% more power than the rest of the signal being transmitted.
> Is this intentional?
>
> [image: Inline image]
>
>
> de Mike W9MDB
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] r8603 power at qso start

[Black Michael via wsjt-devel]

Running R8603 and seeing a power level that seems too high at start of 
transmission (both Tune and standard messages on FT8).This is about 50% more 
power than the rest of the signal being transmitted.Is this intentional?




de Mike W9MDB

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Second Public Test of FT8 DXpedition Mode: April 7, 1400-1600 UTC

[Joe Taylor]

Hi all,

I write to remind you of the second public test of *FT8 DXpedition Mode* 
scheduled for Saturday, April 7, 1400-1600 UTC.  You are cordially 
invited to participate -- the more participants, the better!


Our main goal is to simulate pileups in which many "Hounds" call and 
attempt to work a desirable rare DX station, the "Fox".  The test will 
help us to improve our software so as to maximize the practical QSO rate 
in such situations.  We hope you can be there and try to work both Foxes.


Here's the detailed schedule:

Date  UTC   FrequencyFox Callsign  Operator
---
April 7  1400   14.105 MHzW1/KH7Z   N1DG
April 7  1500   14.105W7/KH7Z   AA7A

All participating stations must use program version WSJT-X v1.9.0-rc3. 
If you don't yet have it, download links are available near the bottom 
of the page here:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

[If you are compiling the program for yourself, be sure to use code 
revision r8576 or later, taken from the repository's WSJT-X development 
branch.  All revisions since r8576 will perform identically in FT8 
DXpedition Mode.]


Detailed instructions for both Fox and Hound are posted here:
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
Some details in these instructions have changed, so be sure to read and 
follow the latest instructions carefully!  Don't just try to wing it.


As you will know after reading the instructions, Fox can conduct up to 5 
QSOs simultaneously, using frequency slots spaced by 60 Hz.  Fox 
transmissions always occur in the frequency range 300-900 Hz above dial 
frequency.


If you (as a Hound) can legitimately use more than one callsign -- your 
spouse's call, club call, etc. -- feel free to work each Fox multiple 
times.  No dupe QSOs with the same call, though.


Real-time liaison will be available on the "Ping Jockey Relief" chat 
page (PJB), https://www.pingjockey.net/cgi-bin/pingtalkB .  Everyone 
should monitor this page for possible last-minute announcements of a 
frequency change, etc.  To ensure that announcements from Fox stations 
are easily visible, Hounds should monitor PJB but not post messages 
there during the test.


The deepest pileups will help us tune the final-release software version 
for optimum performance on both Fox and Hound sides.  After the test, 
please post any comments you feel will be helpful to one of our two 
email forums, wsjtgr...@yahoogroups.com or 
wsjt-devel@lists.sourceforge.net .  You will need to be subscribed to 
the list in order to post there.


We sincerely hope you can join us for this test, and that you will work 
both Foxes!


-- 73, Joe, K1JT (for the WSJT Development Group)


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Request for publication of modified version of wsjtx

[Joe Taylor]

Dear Nobu-san,

On 4/4/2018 3:54 AM, ja2bqx wrote:

Dear Joe Taylor, K1JT,

I am JA2BQX nobu. I think that logging software used by
many amateur radio operators in Japan is
[Turbo HAMLOG for Windows] (called Hamlog or THW).
http://www.hamlog.com/

I modified the source code of WSJT-X and
incorporated the function to
transfer QSO data directly from wsjtx to THW.

May I publish this on my website below?
http://www.geocities.jp/ja2bqx/

de JA2BQX nobu


WSJT-X already provides a UDP protocol that delivers information to 
another program such as a logger.  It includes two ways of accessing 
logged QSO data: ADIF format, or binary log records.  By using this 
feature you would decouple the task of transferring log information from 
WSJT-X itself, and you would avoid the very significant burden of 
maintaining a forked version of WSJT-X.


If THW is not open to modification to accept UDP traffic from WSJT-X, 
then a bridging application would be needed.  However, that is a route 
already taken by several developers. Maintenance of such a "glue" 
application that interfaces between two others is much easier and 
enhancements to WSJT-X and the target logging application come for free 
rather than having to merge them into a fork.



If you choose to create a fork of WSJT-X you must give it a new program 
name and maintain it and document it yourself.  You must honor our 
copyrights: except where otherwise noted, all algorithms, protocol 
designs, source code, and supporting files contained in the WSJT-X 
package are the intellectual property of their authors. The authors 
assert copyright ownership of this material, whether or not such 
copyright notice appears in each individual file. If you make fair use 
of our work under terms of the GNU General Public License (GPL v3) you 
must display our copyright notice prominently in your program, and you 
must fully comply with the licensing terms of WSJT-X, Version 3 of the GPL.


The essential terms and conditions of GPL v3 include (but are not 
limited to) the following:


1. A copy of the license (GPL v3) should accompany the program distribution.

2. Any licensee who adheres to the terms and conditions is given 
permission to modify the work, as well as to copy and redistribute the 
work or any derivative version.  However, the same GPL v3 must apply to 
the copied or modified work.


3. Programs distributed as pre-compiled binaries must be accompanied by 
a copy of the source code, or instructions on how to obtain it.


-- 73, Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel