Bill, G4WJS & Steve, K9AN,
Thanks for your explanation in your previous messages regarding why some FT8
contesters are seeing what appear to be bogus grids being sent.
So if I understand correctly, when a user checks the box for the NA contest,
his grid is converted to its equivalent antipo
1.8 rc2 was working fine using FT8 with Windows 7 Pro 64. My rig is a Hermes
SDR.
In trying to set up for possibly working FT8 with a N3JFP VHF contest logging
program I got a "hamlib error". At first it said the serial port was in use by
another program. Nothing seemed to help, so I selected
On 10/09/2017 01:50, Laurie, VK3AMA wrote:
n 9/09/2017 10:32 PM, Bill Somerville wrote:
If it is just for testing purposes I am tempted to only offer some
way of enabling it externally, perhaps via an environment variable or
command line option.
Bill,
A Command Line option would work for me
On 9/09/2017 10:32 PM, Bill Somerville wrote:
If it is just for testing purposes I am tempted to only offer some way
of enabling it externally, perhaps via an environment variable or
command line option.
Bill,
A Command Line option would work for me as I already use custom
shortcuts for man
On 10/09/2017 00:49, w...@frontier.com wrote:
there is still a but in the program I am running wsjt 1.8.rc2-8089
will not go out of 73 just still run 73 over and over until you stop
it...WW8O
Hi OM,
that is expected behaviour and commonly used where signals are weak or
on MS where repeats
there is still a but in the program I am running wsjt 1.8.rc2-8089 will not
go out of 73 just still run 73 over and over until you stop it...WW8O
On Saturday, September 9, 2017 9:01 AM, Black Michael via wsjt-devel
wrote:
I just started running FT8 today and on the 2nd QSO had this
Rich,
> He sent me a report, a Tx2 message, “K1HTV W3ARO OE28”, a bogus grid number,
> apparently mis-formated by the software version that he was using.
>
As explained in the user guide reference that I sent earlier, he was sending a
correctly formatted contest-mode message. His software transl
On 09/09/2017 23:41, Rich - K1HTV wrote:
He responded with an apparent free form text message of “K1HTV W3ARO R
FN20” which is a properly formatted Tx3 message.
Hi Rich,
that's not a free text message, it's too long. Maybe I was wrong in
saying WSJT-X does not detect the antipodal grid trick
OK, while running WSJT-X Version 1.8.0-rc 8069, I too now have see a bogus
grid report being sent.
I answered a CQ by W3ARO .
He sent me a report, a Tx2 message, “K1HTV W3ARO OE28”, a bogus grid number,
apparently mis-formated by the software version that he was using.
.
I had switched ba
On 09/09/2017 22:54, Rich - K1HTV wrote:
unexpected OF10, OF11, OE39, OE39 initial FT8 exchanges some stations
(you, K3AJ, N2NT, W3IP, WA3VNV) were sending.
Hi Rich,
these are the actual grids embedded in the contest mode exchanges. The
contest mode as is has been hacked into the existing pro
Hi Rich,
The user guide, paragraph 5 of section 17.1, describes how North American VHF
contest mode is implemented. This should explain the “bogus” grids that some
stations are reporting.
Steve k9an
> On Sep 9, 2017, at 9:54 PM, Rich - K1HTV wrote:
>
> While operating in this weekend's ARRL
While operating in this weekend's ARRL VHF contest using FT8, two major
problems have appeared.
1) Not all stations are using the CONTEST MODE (File, Settings, Advanced tab).
As a result, stations using differing "Contest mode" check box settings can
not complete FT8 QSOs. The reports being
On 09/09/2017 14:00, Black Michael via wsjt-devel wrote:
I just started running FT8 today and on the 2nd QSO had this problem.
Runng r8072 When WW80 sent me 73 my side decided to send a sig report.
The first QSO I did was OK. The only difference I see here is he
repeated the RRR whereas the 1s
r8072
Checking the option for Full Call in Tx5 only produces the wrong thing in
Tx5.The other two options for Tx1 and Tx3 are OK.
It's this section of code -- should the else clause be removed?
case Configuration::type_2_msg_5_only: msgtype(t00 + my_grid,
ui->tx1); if (!eme_s
On 9/09/2017 10:32 PM, Bill Somerville wrote:
HI Laurie,
I wasn't aware that this had changed but I had not tested it either.
I wonder if the new behaviour is actually better? What is your use
case for having UDP decode notifications when replaying .WAV files? If
it is just for testing pur
I just started running FT8 today and on the 2nd QSO had this problem.
Runng r8072 When WW80 sent me 73 my side decided to send a sig report.The
first QSO I did was OK. The only difference I see here is he repeated the RRR
whereas the 1st QSO was "normal".
Did that confuse the state machine?
d
On 09/09/2017 06:29, Laurie, VK3AMA wrote:
Not sure if this is intentional or a defect with RC2 (r8069)
When replaying previously saved decode wave files, which I do
frequently for JTAlert testing. I am not getting any UDP decode
packets. I get the two status packets indicating that decoding h
17 matches
Mail list logo
