We had that problem here on our 15m position. One of the ops noted
that our spots were going out on the wrong frequency. The same one
consistantly. They stopped sending spots until I found the problem.
Someone had accidentally hit one of the memory buttons on the MP
and the indicator said "VMEM". I reset it to VFO and that curred the
problem. I have not tried to recreate the symptom, but it IS vfo related.
I have also seen this happen on 940's when the interface stops reading
the vfo. The CT memory then just repeats the last known frequency
when using alt-F3. Bottom line, it was probably cockpit trouble. In the
heat of battle, this goes un noticed until someone sends you a kind packet
note, or another op sees the outgoing spots.
73 Dallas W3PP
----- Original Message -----
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: Scott Pederson <spederson@yahoo.com>; <cq-contest@contesting.com>
Cc: David B. Tucker, KA6BIM <dtucker@inreach.com>
Sent: Monday, October 28, 2002 7:16 PM
Subject: Re: [CQ-Contest] Packet Spots in CQWW
> At 01:17 PM 10/28/2002 -0800, Scott Pederson KI5DR wrote:
>
> >I noticed that there were a few instances where there were several DX
> >spots for exactly the same frequency - apparently the running station was
> >sending packet spots for stations that worked him. I'm sure this was
> >un-intentional, but would explain why you follow a packet spot and it
> >turns out to be someone else....
>
> Well, it wasn't us! :-)
>
> On Saturday afternoon, KA6BIM put out a number of spots using the KC1XX 10
> meter run frequency (data from http://oh2aq.kolumbus.com/dxs/)
>
> KA6BIM 28574.7 PY2BT 1933 26 Oct 2002
> KA6BIM 28574.7 LU3HIP 1934 26 Oct 2002
> KA6BIM 28574.7 VA3SK 1936 26 Oct 2002
> KA6BIM 28574.7 CK6SV 1937 26 Oct 2002
> KA6BIM 28574.7 KC1XX 1938 26 Oct 2002
> KA6BIM 28574.7 LP7H 1939 26 Oct 2002
> KA6BIM 28574.7 CE3N 1940 26 Oct 2002
> KA6BIM 28574.7 KD7GGZ 1941 26 Oct 2002
> KA6BIM 28574.7 WP2Z 1943 26 Oct 2002
> KA6BIM 28574.7 LT5H 1944 26 Oct 2002
> KA6BIM 28574.7 HI9X 1946 26 Oct 2002
> KA6BIM 28574.7 PP2RON 1947 26 Oct 2002
> KA6BIM 28574.7 CX5BW 1952 26 Oct 2002
> KA6BIM 28574.7 J69AZ 1953 26 Oct 2002
> KA6BIM 28574.7 CJ5DX 1954 26 Oct 2002
> KA6BIM 28574.7 LU7PT 1956 26 Oct 2002
>
> We were not working these stations, and I have no idea where they were on
> the band. However, it did result in an inordinately large number of
> 0-point stateside callers, as you can see from the log extract below:
>
> 26-Oct-02 1937 895 28574 VE6FI 59 04 2
> 26-Oct-02 1941 899 28574 KM9Z 59 04 0
> 26-Oct-02 1942 900 28574 N3CY 59 05 0
> 26-Oct-02 1942 901 28574 K6DRK 59 03 0
> 26-Oct-02 1942 902 28574 WP4Z 59 08 2
> 26-Oct-02 1942 903 28574 K2NG 59 05 0
> 26-Oct-02 1944 904 28536 CE3N 59 12 3
> 26-Oct-02 1946 906 28574 W1NG 59 05 0
> 26-Oct-02 1946 907 28574 T2DX 59 31 T2 3
> 26-Oct-02 1947 908 28574 K8LN 59 04 0
> 26-Oct-02 1947 909 28574 N6GL 59 03 0
> 26-Oct-02 1949 910 28574 KC0IEE 59 04 0
> 26-Oct-02 1949 911 28574 K6GU 59 03 0
> 26-Oct-02 1949 912 28574 NK7U 59 03 0
> 26-Oct-02 1950 913 28574 VE9XA 59 05 2
> 26-Oct-02 1950 914 28574 PY2TSM 59 11 3
> 26-Oct-02 1950 915 28574 K5GPA 59 04 0
> 26-Oct-02 1951 916 28574 XE2LV 59 06 2
> 26-Oct-02 1953 918 28468 PV2M 59 11 3
> 26-Oct-02 1954 919 28570 HR8/YN4SU 59 07 2
> 26-Oct-02 1954 920 28574 VY2SS 59 05 2
>
> Perhaps the VFO that was being read for spotting was different than the
one
> he actually tuned with. Note that he did actually spot KC1XX once, but
the
> VFO problem occurred before that spot, and continued afterwards.
>
> 73 - Jim AD1C (one of 10 meter ops at KC1XX)
>
>
> --
> Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
> USA +978-251-9933, <jjreisert@alum.mit.edu>, http://www.ad1c.com
> PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
|