What are the headings for the data fields (columns) in the refspec.dat file
that is generated by the Reference Spectrum tool?
Robert Rearden
ae...@att.net
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists
Suggestion regarding colors.
I really love what was done in 2.0. Finally a great logger, many thanks!
I miss one enhancement though. When I see a message from one station to another
(without CQ or my call), it is in white. It will be very nice if the second
call in this message was highlighted,
Aloha David:
Ooops, that was just a key stroke error on my part. It really is 8192.
I copy/pasted everything, except the last line (by accident), noticed the
omission, and then keyed in the remainder, with the last two numbers reversed.
Sorry for the confusion, and thanks for finding my error.
> On Dec 21, 2018, at 09:44, DX Jami via wsjt-devel
> wrote:
>
> can extra bits be obtained by omitting the worked station's call sign?
This can really cause problems when trying to confirm that the report is from
the station you think it is from. The idea is to make sure you don’t get a
b
On 12/21/2018 8:44 AM, DX Jami via wsjt-devel wrote:
nonstandard call signs such as mine - W4/AH6FX ... or AH6FX/W4
Hi Danny,
US callsigns, with no / identifiers, are valid anywhere in the US. While
using one is legal, it is completely un-necessary. Your call is AH6FX
anywhere in the US, and
> On Dec 21, 2018, at 10:27, Bill Somerville wrote:
>
> nevertheless sending a grid without the /W4 suffix may still be the best
> option if it is legal to do so.
And, as others have done, sending free text occasionally with the added info
for those who bother to read would help.
Gary - AG
On 21/12/2018 16:57, Bill Somerville wrote:
I am not fully up to date on FCC regulations but I believe you don't
need to sign /W4 with your call.
Hi Danny,
having read your bio on QRZ.COM I do see that my suggestion may not be
such a good idea with Jim, AD1C's, CTY.DAT database as you do ope
On 21/12/2018 16:57, Bill Somerville wrote:
(there are already several already which I include a sample of below).
Hi Danny,
I should have added that those sample overrides locate the calls
specified in the lower 48 and define their CQ and ITU Zones.
73
Bill
G4WJS.
__
On 21/12/2018 16:44, DX Jami via wsjt-devel wrote:
Joe, you and I corresponded a few months ago about a similar
nonstandard call sign problem - which was overcome. I recently
encountered and researched my problem of grids not showing in the new
WSJT-X ver 2 for nonstandard call signs such as m
Hello,
Joe, you and I corresponded a few months ago about a similar nonstandard call
sign problem - which was overcome. I recently encountered and researched my
problem of grids not showing in the new WSJT-X ver 2 for nonstandard call signs
such as mine - W4/AH6FX ... or AH6FX/W4.
Got dangerous
My values are exactly the same as yours except for that last one, so if the
config tests don't solve your issue you might give changing that to 8192 a
shot.
> On Dec 20, 2018, at 23:01, David Tiller wrote:
>
>
>> kern.sysv.shmall: 8129
>
> For what it's worth, that value looks like a typo -
Shouldn't your grid and frequency be the log QSO popup?Seems to me all the
information.that goes int the ADIF log should be in the popup.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/list
12 matches
Mail list logo
