I am using N3FJP's logging program to upload contacts to LoTW. It has been working very good on all satellites. However when I try and upload PO-101 it gets rejected by LoTW. Does anybody know what LoTW wants for this satellites name? I get a message back that says "invalid satellite name on line 41".
Bob
WA8FXQ
Yes, I am also listening to the uplink freq. Next pass is in about 1 hour.
73 Eric KV1J
(I use digest mode for this list so pardon the not including the string of
messages)
-----Original Message-----
From: Eric Williams [mailto:[email protected]]
Sent: Tuesday, April 28, 2020 10:51 AM
To: 'amsat-bb(a)amsat.org' <amsat-bb(a)amsat.org>
Subject: RE: Repeater interference on AO-92
I am in the area of a suspected repeater. Also in the area of the towns
mentioned to could be that machine. I'll watch for the next AO-92 pass and
announce my call of the repeater a few times and listen to AO-92. So if you
hear "KV1J" it is me testing for the interference. I have not looked at the
pass schedule yet but I can try a couple passes.
73, Eric KV1J FN42
>
> Yes, I am also listening to the uplink freq. Next pass is in about 1 hour.
> 73 Eric KV1J
Keep in mind that somebody may be commanding it into picture mode.
--Roy
K3RLD
I am in the area of a suspected repeater. Also in the area of the towns
mentioned to could be that machine. I'll watch for the next AO-92 pass and
announce my call of the repeater a few times and listen to AO-92. So if you
hear "KV1J" it is me testing for the interference. I have not looked at the
pass schedule yet but I can try a couple passes.
73, Eric KV1J FN42
>Maybe someone here can better explain how the Fox tone squelch
>works, for example how long it stays on after hearing a tone.
The Fox FM satellites (now AO-91 and AO-92) have their receivers on all the
time and listen for the 67Hz tone. If they do not hear it they turn on the
Tx every 2 minutes for about 10 seconds for a couple frames of telemetry
and a voice ID (without the repeater enabled). If they do hear a tone,
they turn on the repeater for 1 minute (extended each time they hear the
tone).
The tone detector is not too sharp so it might trigger on 69.3 or 71.9 Hz
as well. It does require that the tone be heard for a bit of time (I don't
remember exactly how long--in the hundreds of ms, I think), so it is not
too likely to be triggered by random noise that has some components in that
frequency range. Of course it is not impossible.
Unlike many terrestrial repeaters, the Fox repeaters do not transmit a tone
squelch on the downlink. Those frequencies are right where we stick the
telemetry.
I hope that is helpful...
Burns WB1FJ
AMSAT Fox Flight Software
>
>
Do be aware that the repeater that might be causing the interference may
actually not be running 67Hz tone. The Fox satellites do need to hear 67 Hz
to wake the transponder, but after that it is a bent pipe. Thus, as long as
it got woke up, it would pass whatever FM it hears.
Like the apparent DMR interference we dealt with several months ago, it's
folks who think that it is "Clear air" down there and do their own thing.
Hopefully someone with a scanner can locate and politely pass along some
education.
Tom Schuessler, N5HYP
EM12ms
_______
Date: Mon, 27 Apr 2020 08:55:51 -0400
From: Stephen DeVience <sjdevience(a)gmail.com <mailto:[email protected]> >
To: amsat-bb(a)amsat.org <mailto:[email protected]>
Subject: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CAMPfQQD4qBy7HOEC29rqjwVsWf7f=yoPfQY4gjibqqHtmPsajQ(a)mail.gmail.com
<mailto:[email protected]om>
>
Content-Type: text/plain; charset="UTF-8"
Following up on the previous discussion, I too heard a ragchew on AO-92
during the 4/26 15:20 pass, and others heard it on the 4/27 02:00 pass. I
checked for repeaters in New England with a 67 Hz CTCSS tone, and W1RJC in
New Bedford comes up. Its output at 145.110 MHz also uses a 67 Hz tone and
would have a third harmonic at 435.330 MHz, just about right for AO-92
considering doppler. It is also consistent with hearing a NH callsign and
discussions about sea vessels :)
-Stephen, N8URE
