Hi Saku,
may I propose to take part in CQ WW DX VHF Contest next month?
We have done it last year.
Check those results!
gl de ha6nn
Andras
On Sun, Jun 3, 2018 at 4:08 PM, Saku <oh...@sral.fi> wrote:
> OK !
>
> That seems now to be that "na vhf contest" was checked at the other end
> of qso.
> Because I canceled suggestion of setting contest mode I started to get
> "strange locator" instead of R-report
>
>
>
> A bit confusing as at this side of globe it is very seldom to see someone
> running "na vhf contest". First time for me.
>
> Next time I know...
>
> --
> Saku
> OH1KH
>
>
>
> Saku kirjoitti 02.06.2018 klo 08:33:
>
> Hi!
>
> On friday evening we got first strong, long lasting, ES opening to middle
> EU. I was able to work 92 qsos on that day with 1.9.1 r8733-dirty.
> The last qso was quite interesting and I do not know what made it happen.
>
> Here are the corresponding lines from my ALL.TXT:
>
> 180601_202630 Transmitting 50.313 MHz FT8: CQ OH1KH KP01
> 202645 1 -0.1 1072 ~ OH1KH DJ3JD JO52
> 180601_202700 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
>
> (here I got a splash saying should I use vhf contest mode? Canceled that
> and started to get strange locator instead of R-report. Again and again)
> 202715 -2 -0.1 1072 ~ OH1KH DJ3JD AD57
> 180601_202730 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
> 202745 -2 -0.1 1072 ~ OH1KH DJ3JD AD57
> 180601_202800 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
> 202815 -2 -0.1 1071 ~ OH1KH DJ3JD AD57
> 180601_202830 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
> 202845 -9 -0.1 1071 ~ OH1KH DJ3JD AD57
> 180601_202900 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
> 202915 -11 -0.1 1646 ~ OH1KH DJ3JD AD57
> 180601_202930 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
> 202945 -1 -0.1 1647 ~ OH1KH DJ3JD AD57
> 180601_203000 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
> 203015 -7 -0.1 1648 ~ OH1KH DJ3JD AD57
> 180601_203030 Transmitting 50.313 MHz FT8: DJ3JD OH1KH +01
>
> (here I switched manually to RR73. received immediately 73)
> 180601_203030 Transmitting 50.313 MHz FT8: DJ3JD OH1KH RR73
> 203045 -10 -0.1 1648 ~ OH1KH DJ3JD 73
>
> When grep:ing ALL.TXT I noticed that DJ3JD had more similar events:
> 195300 -10 0.4 1132 ~ YL2AO DJ3JD JO52
> 195330 -3 0.3 1131 ~ YL2AO DJ3JD JO52
> 195400 -5 0.3 1132 ~ YL2AO DJ3JD AD57
> 195430 -2 0.3 1131 ~ YL2AO DJ3JD AD57
> 195500 -3 0.3 1095 ~ YL2AO DJ3JD AD57
> 195530 -3 0.3 1095 ~ YL2AO DJ3JD AD57
> 195600 -1 0.3 1094 ~ YL2AO DJ3JD AD57
> 195630 -3 0.3 1094 ~ YL2AO DJ3JD AD57
> 195700 -1 0.3 1094 ~ YL2AO DJ3JD AD57
>
>
> 203330 8 -0.1 1648 ~ SM0MLZ DJ3JD JO52
> 203400 8 -0.1 1649 ~ SM0MLZ DJ3JD JO52
> 203430 14 -0.1 1648 ~ SM0MLZ DJ3JD AD57
> 203500 14 -0.1 1648 ~ SM0MLZ DJ3JD AD57
> 203530 14 -0.1 1571 ~ SM0MLZ DJ3JD AD57
> 203600 12 -0.1 1571 ~ SM0MLZ DJ3JD AD57
> 203630 15 -0.1 1571 ~ SM0MLZ DJ3JD AD57
> 203645 -11 -0.6 1355 ~ DJ3JD SM0MLZ +14
> 203700 14 -0.1 1570 ~ SM0MLZ DJ3JD AD57
> 203715 -13 -0.6 1355 ~ DJ3JD SM0MLZ +13
> 203730 17 -0.1 1570 ~ SM0MLZ DJ3JD AD57
>
> So I guess the problem is not at my side (canceling the vhf contest popup
> splash).
> I have mailed to DJ3JD if he could sent his part of our qso from ALL.TXT
> and tell what version of wsjt-x he was using.
>
> Have any other of you ever seen something similar happen?
>
> --
> Saku
>
>
>
> ------------------------------------------------------------
> ------------------
> 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
