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
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
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:
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
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
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
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
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
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
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
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
>
> --
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
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!
On link: http://www.sp9kaj.com/downloads.php?cat_id=9_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
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
15 matches
Mail list logo