[wsjt-devel] Splash patch

[Black Michael via wsjt-devel]

Moves the devel/rc warning to the splash page.  Was interfering with proper 
startup from JTAlert.
https://www.dropbox.com/s/wx64861sf8kzk0n/splash.patch?dl=1
This is my 3rd attempt to send this to the list.  The others are getting 
swallowed somewhere...hopefully cleared up now.
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] extended CALL, FT8 spare bit

[Iztok Saje]

Hi Bill,

Z6 is not (yet) on the list of 330 valid prefixes (prefixes.txt), as it is 
rather new.

For numeric: Indeed. As numeric length is reasonable long,
we might say "replace last numeric characters", then G4 becomes G250,
and S52D becomes S5000D if needed.
Using two bits for position is another approach, similar to alphabetic part.

Ugly hack, that solves most of the problems with CALLs, but not all.

For all, maybe additional beacons:
72 bits are split into regular 28 "JT65" call, one A/B bit and 43 data bits.
With A/B and 43+43 bits we can really encode any call.
WSJTX might keep list of heard beacons (transmitted once in 10 minutes) to 
translate
any "JT65" call to any real call.
If they are valid for one hour, and a list is maintained by, say, PSK reporter, 
it might work.
Unfortunately, it calls for misuse, and I would not be happy if S52D translates 
to QRMQRM for a while.

Adding such message to every QSO (to block misuse) is too much overhead.


73 gl
Iztok, s52d



From: Bill Somerville g4wjs:

On 18/02/2018 21:16, Iztok Saje wrote:

Z6/S56A had some nice stories, I guess some people who managed QSO do
not even know they have Z6 worked.


Hi Iztok,

your proposal looks interesting and using one or more of the extra FT8
payload bits for better exotic callsign handling has been considered. I
am confused about what he issue with the above Z6/S56A callsign is as
that is a valid type 2 prefix compound callsign and should be handled
reasonably well by the existing source encoding.

I do have some doubt about your proposed extension mechanism as it seems
to sometimes rely on a regular base base callsign being present in the
exotic form which may not always be the case, in fact the contraction to
a regular base callsign may be some other operators callsign. For
example you suggest that if I were allowed to use, say G250WJS for some
250th special celebration. But contracting this callsign to G2WJS plus
50 encoded in the grid word would be incorrect as my call is G4WJS.

73
Bill
G4WJS.



On 02/18/2018 10:16 PM, Iztok Saje wrote:

Hello!

With FT8 avalanche on shortwave, we are facing more and more problems with 
CALLs that can not be encoded in JT65/FT8 etc.
Z6/S56A had some nice stories, I guess some people who managed QSO do not even 
know they have Z6 worked.
I am not sure have I worked RI1ANO or RI150ANO? I put both into LotW, just to 
be safe.

One spare bit can be used to indicate FT8-EXTENDED call: when used, locator 
square 15 bits are replaced by additional information.
Users can define classic "JT65" call and "FT8 extended call", like S56A and 
Z6/S56A, RI1ANO and RI150ANO,
DA0WRT and DA0WRTC, OH2YOT and  OH2YOTA etc.

Out of 15 bits, one indicates NUMBER_only. If set, then additional number 
(encoded in remaining 14 bits) is appended
after last numeric character in the CALL.
Example: RI150ANO is coded as RI1ANO + extended 50, thus producing RI150ANO.

This is common problem for special calls targeting WPX award. For example, 
several S5 stations added numbers.
I can imagine S5242D for Towel Day, or S52356D to celebrate 356 days long year, 
or so.


If not numeric, then remaining 14 bits are split into:
- two bits for position (prefix, after first alpfabetic character, after first 
numeric character, append to the end)
- one bit to add "/", either Z6/S56A or S%6A/Z6 depending on position bits
- 11 bits are used to encode two characters from NULL, A-Z, 0-9
(as there are some more possibilities, some two character combinations might be 
added).

Stations using extended calls use extended CALL, other answering (and old WSJTX users) 
call them with "JT65" CALL.
SO, extended call bit, when set, refers to sender only. When two stations with 
extended calls have QSO, they
use own extended call and others JT65 call.
Extended call serves purpose to provide proper identification according to 
license, while short JT65 call is used
for QSO, but has no legal impact. We use same approach with compound calls 
today.


JT65/MSK144 community is smaller and it can handle exceptions better.
One possibility is to add comment line (TX4 freetext) to map JT65/classic calls 
to FT8-extended call.
Maybe beacon every 10 minutes, and clients can keep map?



There are calls that can not be encoded with proposed scheme: for example 
DR5LUTHER, VK100ANZAC.
But, they are really rare, and probably even some logging programs might object.


Best 73, gd DX
Iztok, S52D


p.s.

With more and more people coming to FT8, congestion is severe. KN spare bit as 
well as random delayed repetitions on CQ answer
would help us make more QSOs.





On 10/17/2017 08:07 AM, Iztok Saje wrote:

Hello!

In order to lower QRM, increase QSO rate and speed up user education, there are 
several proposals, all
efectivelly blocking QRM transmission in different conditions.


1. one spare FT8 bit is used as KN bit (Do not transmit unless invited)

2. When there are several responses to CQ, implement Aloha principle (repeated 
retransmissions are

Re: [wsjt-devel] USB protocolo

[John Nogatch]

On Sat, Feb 17, 2018 at 10:36 AM, José Aparecido Pereira
 wrote:
...
> ... the information received by the UDP / ip protocol port WSJT-x
> could someone please forward this information to me?

The format of the UDP messages is documented here:
https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/wsjtx/NetworkMessage.hpp#l38

-John AC6SL

--
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] channel description

[Steven Franke]

Don,

> It seems that by assuming a correct decode (and a time-invariant transmitter) 
> each user could store enough information (already supported by the SW) to 
> describe the channel statistics.  I see hints that you are trying to provide 
> the capability to describe the transmitter, but what about the larger 
> question of the channel?  Is there a behavior whereby a large body of users 
> could help describe the channel in a cooperative manner? 

The FT8, JT65, and WSPR demodulator/decoders estimate the channel for each and 
every decode. Given the decoded message we regenerate the transmitted waveform 
and use that as a reference to derive the time-varying, complex, gain function 
that describes the channel. We use this to reconstruct a (nearly) noiseless 
version of the received signal’s waveform that includes the channel-induced 
amplitude fading and phase-variation. The reconstructed signal is subtracted 
from the received data, enabling us to uncover weaker signals that occupy the 
same frequency slot as the subtracted strong signal. These weaker signals can 
often be decoded on a second decoding pass, after the stronger signals have 
been subtracted.

Steve K9AN
--
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] USB protocolo

[José Aparecido Pereira]

Hello friends,
I'm developing help software that works together with WSJT
it makes me many things, it brings me several instant information like
cq zone itu zone dxcc sends log in real time, check my data bank info
B4, etc.
although I was still listening to some things I could not figure out
in the information received by the UDP / ip protocol port WSJT-x
could someone please forward this information to me?


Grato




Livre
de vírus. www.avast.com
.
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
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] Test

[G8DQX (WSJT developers on SF)]

Mike,

it is working, but for some reason the mail was seriously delayed within 
SourceForge, according to the timestamps. You sent it at



Date: Sat, 17 Feb 2018 20:50:41 + (UTC)

and it was processed at SourceForge (1st server)


Sat, 17 Feb 2018 20:50:44 +

and then

Received: from localhost ([127.0.0.1] helo=sfs-ml-1.v29.lw.sourceforge.com)
by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.89)
(envelope-from )
id 1enStK-0002my-TL; Sun, 18 Feb 2018 17:36:46 +


and final delivery from SourceForge to my email provider was


Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7])
by spool.mail.<> (Postfix) with ESMTPS id E320719F373
for ; Tue, 20 Feb 2018 00:21:49 +0100 (CET)
One imagines that the email had been printed and sent as a blue Airmail 
flimsy!


"It's working, Jim, but not as we know it!"

73,

Robin, G8DQX


On 17/02/18 20:50, Black Michael via wsjt-devel wrote:

Testing if email group is working yet.

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

Re: [wsjt-devel] extended CALL, FT8 spare bit

[Bill Somerville]

On 20/02/2018 00:38, Laurie, VK3AMA wrote:

On 19/02/2018 8:35 AM, Bill Somerville wrote:
I am confused about what he issue with the above Z6/S56A callsign is 
as that is a valid type 2 prefix compound callsign and should be 
handled reasonably well by the existing source encoding. 


Bill,

I wonder if the OP was referring JTDX rather than WSJT-X. There were 
recent reports of Z6 Calls being incorrectly logged as ZA coming from 
JTDX


From the latest JTDX release notes...
Discarded all changes done to Z6 prefix support: it has been 
supported in all versions 18.1 and new changes violated WSJT-X protocol.


de Laurie VK3AMA


Hi Laurie,

maybe. We are well aware of the JTDX issues with unwise changes adding 
new type 1 prefixes. After discussion with Igor he has reverted his 
changes so that JTDX's type 1 prefix and suffix list matches those of 
WSJT-X, WSJT, JT65-HF and MSHV again. Type 1 prefixes are fixed and only 
really present to maintain backwards compatibility with the original 
JT65 v1 protocol. Type 2 prefixes were introduced several years ago and 
use a more generic source encoding that caters for all prefixes so long 
as they fit a particular pattern, this includes ES, KC4 and Z6 which 
were unnecessarily added to the type 1 prefix lists in JTDX.


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] extended CALL, FT8 spare bit

[Laurie, VK3AMA]

On 19/02/2018 8:35 AM, Bill Somerville wrote:
I am confused about what he issue with the above Z6/S56A callsign is 
as that is a valid type 2 prefix compound callsign and should be 
handled reasonably well by the existing source encoding. 


Bill,

I wonder if the OP was referring JTDX rather than WSJT-X. There were 
recent reports of Z6 Calls being incorrectly logged as ZA coming from JTDX


From the latest JTDX release notes...
Discarded all changes done to Z6 prefix support: it has been supported 
in all versions 18.1 and new changes violated WSJT-X protocol.


de Laurie VK3AMA

--
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] extended CALL, FT8 spare bit

[Bill Somerville]

On 18/02/2018 21:16, Iztok Saje wrote:
Z6/S56A had some nice stories, I guess some people who managed QSO do 
not even know they have Z6 worked.


Hi Iztok,

your proposal looks interesting and using one or more of the extra FT8 
payload bits for better exotic callsign handling has been considered. I 
am confused about what he issue with the above Z6/S56A callsign is as 
that is a valid type 2 prefix compound callsign and should be handled 
reasonably well by the existing source encoding.


I do have some doubt about your proposed extension mechanism as it seems 
to sometimes rely on a regular base base callsign being present in the 
exotic form which may not always be the case, in fact the contraction to 
a regular base callsign may be some other operators callsign. For 
example you suggest that if I were allowed to use, say G250WJS for some 
250th special celebration. But contracting this callsign to G2WJS plus 
50 encoded in the grid word would be incorrect as my call is G4WJS.


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] Test

[Laurie, VK3AMA]

On 18/02/2018 7:50 AM, Black Michael via wsjt-devel wrote:

Testing if email group is working yet.

de Mike W9MDB

Took 2 days (based on your posting date/Time) for it to appear in my inbox.

de Laurie VK3AMA


--
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] Test

[Earle]

Working. 

Earle KM4ISN 

Sent from my iPhone

> On Feb 17, 2018, at 3:50 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Testing if email group is working yet.
> 
> 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

Re: [wsjt-devel] Test

[James Shaver (N2ADV)]

I got the note, Mike. 

> On Feb 17, 2018, at 3:50 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Testing if email group is working yet.
> 
> 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] Test

[Black Michael via wsjt-devel]

Testing if email group is working yet.
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] Polish translation of WSJT-X User Guide (Version 1.8.0) by Ryszard Gala SP9GR WSJT-X Przewodnik użytkownika

[sp9gr]

On link: http://www.sp9kaj.com/downloads.php?cat_id=9&download_id=18
can be downloaded zipped hypertext packet : Polish translation of WSJT-X User 
Guide (Version 1.8.0) by Ryszard Gała SP9GR "WSJT-X Przewodnik użytkownika".
It can be used as menu item  'Help->Local User Guide' in running app WSJT-X (if 
it's been expanded and installed locally in ..wsjtx\share\doc\WSJT-X folder) or 
immediately from web browser.

Vy73
Dick, SP9GR

--
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] Email test

[Kim gross]

got it


On 2/16/2018 7:46 AM, Black Michael via wsjt-devel wrote:

Seeing if the devel list is back up after the sourceforge move

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