Hi,
I noted that in the EU VHF contest logging a wrong information is logged
into database, when AP decoding and automatic logging is activated. If the
confirmation message that initiates logging happens to be decoded with AP,
then the AP level (a2) will be logged instead of the report and 6 digit
Reino,
Matt's query is abut WSPR mode, there are no CQ calls and the structured
messages are much simpler since they are beacon transmissions. The
handling of non-standard calls is also different from QSO modes.
73
Bill
G4WJS.
On 21/02/2020 06:39, Reino Talarmo wrote:
Hi Matt,
You should
Isn't there an ITU standard for callsigns?
AFAIK the Australian Foundation call complies with that standard.
--
finger painting on glass is an inexact art - apologies for any errors in
this scra^Hibble
()/)/)() ..ASCII for Onno..
On Fri., 21 Feb. 2020, 18:02 Bill Somerville, wrote:
> Reino,
>
Thanks to a fellow amateur for this information.
ITU document:
https://www.itu.int/en/ITU-R/terrestrial/fmd/Documents/fxm-art19-sec3.pdf
See also:
https://www.itu.int/en/ITU-R/terrestrial/fmd/Pages/identifications.aspx
19.67 Amateur and experimental stations
19.68 § 30 1)
– one character (provi
On 21/02/2020 10:57, Onno Benschop wrote:
Isn't there an ITU standard for callsigns?
AFAIK the Australian Foundation call complies with that standard.
Hi Onno,
where I say non-standard I mean within the constraints of the digital
source encoding used by the various modes in the WSJT suite of
Bill,
Thanks, for sure. I should have read more carefully, hi!
73, Reino oh3mA
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: 21. helmikuuta 2020 11:59
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 7 Digit Callsigns
Reino,
Matt's query is abut WSPR mode,
Hi Martin and all,
Bill has already given you the correct answer. In FT4 and FT8 there are
only about 2 seconds for decoding before the nominal start of the next
sequence. If you are using deep decoding, perhaps with AP, and/or have
a slow computer, some decodes may take place after the sequ
Just a heads up:
Error: (occurs twice)
/builddir/build/BUILD/js8call-2.1.1/lib/ft8/filt8.f90:32:14:
12 | call four2a(x,NFFT,1,-1,0) !r2c
| 2
..
32 | call four2a(cx,nfft,1,1,-1) !c2r
| 1
Error: Type mismatch between a
Tnx Richard.
As I'm sure you know, this is not an error; rather the message is the
result of a fussy compiler. However, we will comply.
In line 12, just replace the first line with the second:
- call four2a(x,NFFT,1,-1,0) !r2c
+ call four2a(cx,NFFT,1,-1,0) !r2c
On 21 Feb 2020 at 9:40, Joe Taylor wrote:
> Hi Martin and all,
>
> Bill has already given you the correct answer. In FT4 and FT8 there are
> only about 2 seconds for decoding before the nominal start of the next
> sequence. If you are using deep decoding, perhaps with AP, and/or have
> a slo
Hi
I am running my rigblaster blue via a bluetooth 4.0 dongle on a WinXP
-Notebook as well as on a win7-netbook in both the latest Versions of
wsjt-X and jtdx 147 without any problems in ft8 and ft4 and for sure with
fldigi as well.
But both my rigblasters, the -blue and the advantage I could neve
Reino,
Respectfully -- that is not a good answer. You addressed the WSJT-X issue
while WSPR was the problem. Having said that - constructively, WSJT-X must
accept what are now called non-standard calls. They are non-standard only to
the WSJT-X programmers and not the ham radio world. They a
12 matches
Mail list logo
