On 24 Dec 2018 at 9:13, John Becker wrote:

> I'm running WSJT-X v2.0 on a Windows 10 Pro (1803 update) computer.
> 
> On Saturday, HV0A was running F/H mode on 3567 with a large number of 
> callers. I noticed strange behavior as follows with annotated excerpts 
> from my all.txt file:
 
[Snipped]

> If desired, I can send the entire 377 line session from my all.txt file.
> 
> The fact that re-starting the program temporarily fixed this problem 
> indicates to me that this was not a case of MI0KOA also running F/H mode 
> as Fox on the same frequency. Note that it started right after MI0KOA 
> made his QSO. Strange!
> 
> Was anyone else seeing this?
> 
> 73,
> John, K9MM

Yes, I noticed it too around the time (232315z on 2018-12-22) I worked HV0A on 
80m 
although I didn't try restarting WSJT-X to see if the 'issue' disappeared; I 
just assumed it was 
MI0KOA also running as a Fox in F & H mode.

Here's an extract from my ALL.TXT:

181222_232315  Transmitting 3.567 MHz  FT8:  HV0A G0HDB IO82                    
  
232330  -6  0.2  296 ~  9A1AD RR73; RI1ANL <HV0A> -12
232330 -10  0.2  356 ~  K9ZO RR73; JG1IGX <HV0A> -16
232330  -9  0.2  416 ~  IZ7QFN HV0A +03
232330  -6  0.2  477 ~  G0HDB HV0A +02
181222_232345  Transmitting 3.567 MHz  FT8:  HV0A G0HDB R-06                    
  
232400  -7  0.2  297 ~  G0HDB RR73; JG1IGX <HV0A> -16
232400  -9  0.2  357 ~  RI1ANL RR73; IZ7QFN <HV0A> +02
232400  -9  0.2  417 ~  EA1DFP HV0A +00
232400  -6  0.2  477 ~  BH7PFH HV0A -13
232415   2  0.4  417 ~  HV0A EA1DFP IN53
232430  -7  0.2  296 ~  IZ7QFN HV0A +03
232430 -10  0.2  356 ~  EA1DFP HV0A +00
232430 -10  0.2  417 ~  BH7PFH HV0A -13
232430 -10  0.2  477 ~  KE9ET HV0A -12
232430  -8  0.2  537 ~  WR4K HV0A -11
232445   1  0.4  357 ~  HV0A EA1DFP R-04
232500  -7  0.2  297 ~  EA1DFP RR73; BH7PFH <HV0A> -14
232500 -10  0.2  357 ~  WR4K RR73; KE9ET <HV0A> -12
232500  -8  0.2  417 ~  BG3UPA HV0A -10
232515 -17  0.2  357 ~  HV0A KE9ET R-07
232515 -20  0.2  438 ~  MI0KOA JA4DND PM65
232515 -19  0.3  916 ~  HV0A WD8KND EN91
232530  -7  0.2  296 ~  KE9ET RR73; BG3UPA <MI0KOA> -10
232530  -9  0.2  357 ~  RQ3A HV0A -08
232530  -7  0.2  417 ~  DD5ZZ HV0A +07
232545  -2 -0.8  296 ~  HV0A IZ7QFN R-09
232545  -8  0.1  356 ~  HV0A RQ3A R-05
232600  -8  0.2  297 ~  DD5ZZ RR73; BG3UPA <MI0KOA> -10
232600 -10  0.2  357 ~  RQ3A RR73; DM5EM <MI0KOA> +04
232600  -8  0.2  417 ~  SV1CKZ HV0A -07
232615   5  0.1  356 ~  HV0A DM5EM JN59
232615 -17  0.2  417 ~  HV0A SV1CKZ KM18
232630  -5  0.2  297 ~  DM5EM HV0A +04
232630  -9  0.2  357 ~  SV1CKZ HV0A -07
232630  -9  0.2  417 ~  JE4URN HV0A -15
232630  -7  0.2  477 ~  US5EOI HV0A -16
232645   6  0.1  296 ~  HV0A DM5EM R+13
232645 -24  0.3  417 ~  HV0A SV1CKZ R-09
232645 -11  0.1  477 ~  HV0A US5EOI R-03
232700  -9  0.2  297 ~  DM5EM RR73; JE4URN <MI0KOA> -16
232700 -11  0.2  357 ~  SV1CKZ RR73; N5ZM <MI0KOA> -16
232700  -8  0.2  417 ~  US5EOI HV0A RR73
232730  -6 -0.0  297 ~  JE4URN HV0A -15
232730  -9 -0.0  357 ~  N5ZM HV0A -16
232730  -9 -0.0  417 ~  WX0V HV0A -17
232730  -6 -0.0  477 ~  WP4G HV0A -17
232745 -19  0.2  356 ~  HV0A N5ZM R-08
232800  -8  0.2  296 ~  N5ZM RR73; WX0V <MI0KOA> -18
232800 -11  0.2  357 ~  WP4G HV0A -17
232800  -8  0.2  417 ~  E72AD HV0A +03
232815 -10 -0.2  357 ~  HV0A WP4G R-09
232815  -1  0.3  417 ~  HV0A E72AD R+02
232830  -7  0.2  296 ~  E72AD RR73; WX0V <MI0KOA> -18
232830  -8  0.2  357 ~  WP4G RR73; SV1LK <MI0KOA> +00
232830  -6  0.2  417 ~  IK7LJZ HV0A -09
232845   0  1.4  418 ~  HV0A IK7LJZ R-10
232845 -20  0.2  656 ~  HV0A N5ZM R-08
2018-12-22 23:29  3.567 MHz  FT8
2018-12-22 23:29  3.567 MHz  FT8
232915 -11  0.1  357 ~  HV0A N4II R+00
232915   6  0.1 1193 ~  HV0A DL7UVO JO62
232915  -9  0.0 1501 ~  HV0A RA4P LO64
232915   8  0.1 1556 ~  HV0A RU3UR R-03
232915 -15  0.2 1693 ~  HV0A BG3UPA -20
232915   7 -0.0 1746 ~  HV0A ON4FG JO20
232915  -4  0.1 1918 ~  HV0A SP5GDY KO02
232915 -16  0.1 1100 ~  HV0A W8WEJ EM99
232915 -17  0.5 1133 ~  HV0A PY7RP HI22
232930  -3  0.2  296 ~  N4II RR73; SV1LK <HV0A> +00
232930  -2  0.2  357 ~  W8WEJ HV0A -16
232930   0  0.2  417 ~  ON4FG HV0A +09
232930   3  0.2  477 ~  DL7UVO HV0A -03
232945  13 -0.0  417 ~  HV0A ON4FG R+06
232945  11  0.1  477 ~  HV0A DL7UVO JO62
232945 -19  0.3 1360 ~  HV0A AG2J FM29
232945  14  0.0 1556 ~  HV0A RU3UR R-03
232945 -11  0.2 1693 ~  HV0A BG3UPA -20
232945 -17  0.1 1854 ~  HV0A BG2AUE -10
232945  -2  0.1 1918 ~  HV0A SP5GDY KO02
232945 -17  0.2 2001 ~  HV0A VE3XN R-07
232945 -14  0.1 2090 ~  HV0A AA1QD FN43
232945 -18  0.1 2169 ~  HV0A K5RK EL29
232945 -19  0.1 2220 ~  HV0A K3JGJ FM29
232945 -21  0.2 2346 ~  MI0KOA JA4DND PM65
232945 -21  0.2 2617 ~  HV0A NY0V EN33
232945 -13  0.1 1440 ~  HV0A BH7PFH OL72
232945  -6  0.0 1501 ~  HV0A RA4P LO64
232945 -16  0.1 1954 ~  HV0A WD8JJA EM68
233000  -4  0.2  296 ~  ON4FG RR73; DL7UVO <MI0KOA> -04
233000  -1  0.2  357 ~  W8WEJ RR73; SP5GDY <MI0KOA> -06
233015   3  0.1  296 ~  HV0A DL7UVO R-09
233015   0  0.1  357 ~  HV0A SP5GDY R+09
233015 -23  0.8  417 ~  HV0A K4JDF FM19
233015 -17  0.7 1133 ~  HV0A PY7RP HI22
233015 -15  0.3 1360 ~  HV0A AG2J FM29
233015 -18  0.1 1439 ~  HV0A BH7PFH OL72
233015  -7  0.0 1501 ~  HV0A RA4P LO64
233015  13  0.1 1556 ~  HV0A RU3UR R-03
233015 -11  0.2 1694 ~  HV0A BG3UPA -20
233015  -5  0.1 1806 ~  HV0A SV1LK KM17
233015 -18  0.1 2013 ~  HV0A W9OA EN61
233015 -10  0.1 2090 ~  HV0A AA1QD FN43
233015 -18  0.1 2168 ~  HV0A K5RK EL29
233015 -18  0.1 2220 ~  HV0A K3JGJ FM29
233015 -20  0.2 2347 ~  MI0KOA JA4DND PM65
233015 -14  0.1 1853 ~  HV0A BG2AUE -10
233015 -17  0.1 1955 ~  HV0A WD8JJA EM68
233030  -2  0.2  297 ~  DL7UVO RR73; K5RK <MI0KOA> -10

The first appearance of the MI0KOA callsign is at 232515z, when JA4DND was 
calling him - 
there's no evidence of that JA callsign previously having called HV0A.  At 
232500 HV0A was 
calling BG3UPA on 417Hz , then BG3UPA was subsequently called by MI0KOA at 
232530 
on 296Hz.

I wonder if MI0KOA really was QRV in F & H mode at the same time and on the 
same 80m 
frequency as HV0A and the two sets of QSOs just got completely intermixed and 
tangled up, 
or perhaps it's another instance of identical hash values for the HV0A and 
MI0KOA callsigns 
which got cleared by restarting the app.

--
73, Martin G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to