OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
CX2SA  > SATDIG   01.05.20 16:19l 971 Lines 34400 Bytes #999 (0) @ WW
BID : AMSATBB15129
Read: GUEST
Subj: AMSAT-BB-digest V15 129
Path: IW8PGT<IU4DTL<HB9CSR<IK6IHL<IZ3LSV<IR2UBX<DB0RES<ON0AR<OZ5BBS<CX2SA
Sent: 200428/1417Z @:CX2SA.SAL.URY.SOAM #:30027 [Salto] FBB7.00e $:AMSATBB15129
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. Re: Repeater interference on AO-92 (Brian Wilkins KO4AQF)
   2. Re: Repeater interference on AO-92 (tjschuessler@???????.????
   3. Re: Repeater interference on AO-92 (Mike Diehl)
   4. Re: Repeater interference on AO-92 (Brian Wilkins KO4AQF)
   5. Re: Repeater interference on AO-92 (Mike Diehl)
   6. Re: Repeater interference on AO-92 (nathanjwhite)
   7. Re: Repeater interference on AO-92 (Stephen DeVience)
   8. Re: Repeater interference on AO-92 (Brian Wilkins KO4AQF)
   9. Re: Repeater interference on AO-92 (Burns Fisher)
  10. Re: Repeater interference on AO-92 (Stephen DeVience)


----------------------------------------------------------------------

Message: 1
Date: Mon, 27 Apr 2020 22:05:15 -0400
From: Brian Wilkins KO4AQF <bwilkins@?????.???>
To: Stephen DeVience <sjdevience@?????.???>
Cc: amsat-bb@?????.???
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CAO_Eq306XWRL+nWykcxhddxaoiZz=PFyZ7Y3670NzOfjwMQcqA@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

I heard it too at the same time-ish maybe about 1532z though from Florida
on a 4/26 pass from the North to South. Hopefully AMSAT can sort this one
out

On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
amsat-bb@?????.???> wrote:

> 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
> _______________________________________________
> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> expressed
> are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>
--
Brian Wilkins
KO4AQF


------------------------------

Message: 2
Date: Mon, 27 Apr 2020 21:15:03 -0500
From: <tjschuessler@???????.???>
To: <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID: <019b01d61d02$d41feb10$7c5fc130$@???????.???>
Content-Type: text/plain;	charset="us-ascii"

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@?????.??? <mailto:sjdevience@?????.???> >

To: amsat-bb@?????.??? <mailto:amsat-bb@?????.???>

Subject: [amsat-bb] Repeater interference on AO-92

Message-ID:


<CAMPfQQD4qBy7HOEC29rqjwVsWf7f=yoPfQY4gjibqqHtmPsajQ@????.?????.???
<mailto:CAMPfQQD4qBy7HOEC29rqjwVsWf7f=yoPfQY4gjibqqHtmPsajQ@????.?????.???>
>

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









------------------------------

Message: 3
Date: Mon, 27 Apr 2020 22:32:04 -0400
From: Mike Diehl <diehl.mike.a@?????.???>
To: Brian Wilkins KO4AQF <bwilkins@?????.???>
Cc: amsat-bb@?????.???? Stephen DeVience <sjdevience@?????.???>
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID: <A4494A46-0053-426B-9E3E-E232D7C69C9F@?????.???>
Content-Type: text/plain; charset=utf-8

AMSAT can only sort it out with the help from users, they have no magic
wand. Through a process of elimination the region the offender is located in
can be narrowed down by figuring out a common footprint. Continued
monitoring can also reveal a repeater or user ID. This process has been used
in the past to track down offenders. Keep listening and forward any call
signs you hear, AMSAT will definitely reach out to them. Also, recordings
help.

73,
Mike Diehl
W8LID/VE6LID

> On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB
<amsat-bb@?????.???> wrote:
>
> ?I heard it too at the same time-ish maybe about 1532z though from Florida
> on a 4/26 pass from the North to South. Hopefully AMSAT can sort this one
> out
>
>> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
>> amsat-bb@?????.???> wrote:
>>
>> 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
>> _______________________________________________
>> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> to all interested persons worldwide without requiring membership. Opinions
>> expressed
>> are solely those of the author, and do not reflect the official views of
>> AMSAT-NA.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>>
> --
> Brian Wilkins
> KO4AQF
> _______________________________________________
> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
expressed
> are solely those of the author, and do not reflect the official views of
AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb


------------------------------

Message: 4
Date: Mon, 27 Apr 2020 22:36:54 -0400
From: Brian Wilkins KO4AQF <bwilkins@?????.???>
To: Mike Diehl <diehl.mike.a@?????.???>
Cc: amsat-bb@?????.???? Stephen DeVience <sjdevience@?????.???>
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CAO_Eq303vNBL9Lv7xehhiZd8p2GWbSdndEkkJkQLdvEN0amEGw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

That?s what I meant. Thanks Mike. Already been communicating with
Glasbrenner

On Mon, Apr 27, 2020 at 10:32 PM Mike Diehl <diehl.mike.a@?????.???> wrote:

> AMSAT can only sort it out with the help from users, they have no magic
> wand. Through a process of elimination the region the offender is located
> in can be narrowed down by figuring out a common footprint. Continued
> monitoring can also reveal a repeater or user ID. This process has been
> used in the past to track down offenders. Keep listening and forward any
> call signs you hear, AMSAT will definitely reach out to them. Also,
> recordings help.
>
> 73,
> Mike Diehl
> W8LID/VE6LID
>
> > On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB <
> amsat-bb@?????.???> wrote:
> >
> > ?I heard it too at the same time-ish maybe about 1532z though from
> Florida
> > on a 4/26 pass from the North to South. Hopefully AMSAT can sort this one
> > out
> >
> >> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
> >> amsat-bb@?????.???> wrote:
> >>
> >> 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
> >> _______________________________________________
> >> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
> >> to all interested persons worldwide without requiring membership.
> Opinions
> >> expressed
> >> are solely those of the author, and do not reflect the official views of
> >> AMSAT-NA.
> >> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> >> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
> >>
> > --
> > Brian Wilkins
> > KO4AQF
> > _______________________________________________
> > Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
> > to all interested persons worldwide without requiring membership.
> Opinions expressed
> > are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> > Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> > Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>
--
Brian Wilkins
KO4AQF


------------------------------

Message: 5
Date: Mon, 27 Apr 2020 22:42:37 -0400
From: Mike Diehl <diehl.mike.a@?????.???>
To: Brian Wilkins KO4AQF <bwilkins@?????.???>
Cc: amsat-bb@?????.???? Stephen DeVience <sjdevience@?????.???>
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID: <F12AAA21-DCE6-4604-9B8F-0B99BA8AEF6B@?????.???>
Content-Type: text/plain;	charset=utf-8

Cool, it?s challenging because the length of passes aren?t much longer than
the interval to ID. It?s frustrating but perseverance pays off.

73,
Mike Diehl
W8LID/VE6LID

> On Apr 27, 2020, at 22:37, Brian Wilkins KO4AQF <bwilkins@?????.???> wrote:
>
> ?
> That?s what I meant. Thanks Mike. Already been communicating with
Glasbrenner
>
>> On Mon, Apr 27, 2020 at 10:32 PM Mike Diehl <diehl.mike.a@?????.???> wrote:
>> AMSAT can only sort it out with the help from users, they have no magic
wand. Through a process of elimination the region the offender is located in
can be narrowed down by figuring out a common footprint. Continued
monitoring can also reveal a repeater or user ID. This process has been used
in the past to track down offenders. Keep listening and forward any call
signs you hear, AMSAT will definitely reach out to them. Also, recordings
help.
>>
>> 73,
>> Mike Diehl
>> W8LID/VE6LID
>>
>> > On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB
<amsat-bb@?????.???> wrote:
>> >
>> > ?I heard it too at the same time-ish maybe about 1532z though from
Florida
>> > on a 4/26 pass from the North to South. Hopefully AMSAT can sort this one
>> > out
>> >
>> >> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
>> >> amsat-bb@?????.???> wrote:
>> >>
>> >> 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
>> >> _______________________________________________
>> >> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> >> to all interested persons worldwide without requiring membership.
Opinions
>> >> expressed
>> >> are solely those of the author, and do not reflect the official views of
>> >> AMSAT-NA.
>> >> Not an AMSAT-NA member? Join now to support the amateur satellite
program!
>> >> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>> >>
>> > --
>> > Brian Wilkins
>> > KO4AQF
>> > _______________________________________________
>> > Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> > to all interested persons worldwide without requiring membership.
Opinions expressed
>> > are solely those of the author, and do not reflect the official views
of AMSAT-NA.
>> > Not an AMSAT-NA member? Join now to support the amateur satellite
program!
>> > Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
> --
> Brian Wilkins
> KO4AQF


------------------------------

Message: 6
Date: Tue, 28 Apr 2020 03:05:40 +0000 (UTC)
From: nathanjwhite <nathanjwhite@????????.???>
To: Mike Diehl <diehl.mike.a@?????.???>, 	Brian Wilkins KO4AQF
<bwilkins@?????.???>
Cc: amsat-bb@?????.???? Stephen DeVience <sjdevience@?????.???>
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID: <1240407378.1386473.1588043140508@????.?????.???>
Content-Type: text/plain; charset=UTF-8

A couple of weeks ago we identified 2 stations overheard on AO-92?with
apparent Boston area QTH (Waltham and Harvard)?but still no indication of a
repeater.AMSAT has a recording of the pass.
NateN5LEX


On Monday, April 27, 2020, 10:44 PM, Mike Diehl via AMSAT-BB
<amsat-bb@?????.???> wrote:

Cool, it?s challenging because the length of passes aren?t much longer than
the interval to ID. It?s frustrating but perseverance pays off.

73,
Mike Diehl
W8LID/VE6LID

> On Apr 27, 2020, at 22:37, Brian Wilkins KO4AQF <bwilkins@?????.???> wrote:
>
> ?
> That?s what I meant. Thanks Mike. Already been communicating with
Glasbrenner
>
>> On Mon, Apr 27, 2020 at 10:32 PM Mike Diehl <diehl.mike.a@?????.???> wrote:
>> AMSAT can only sort it out with the help from users, they have no magic
wand. Through a process of elimination the region the offender is located in
can be narrowed down by figuring out a common footprint. Continued
monitoring can also reveal a repeater or user ID. This process has been used
in the past to track down offenders. Keep listening and forward any call
signs you hear, AMSAT will definitely reach out to them. Also, recordings
help.
>>
>> 73,
>> Mike Diehl
>> W8LID/VE6LID
>>
>> > On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB
<amsat-bb@?????.???> wrote:
>> >
>> > ?I heard it too at the same time-ish maybe about 1532z though from
Florida
>> > on a 4/26 pass from the North to South. Hopefully AMSAT can sort this one
>> > out
>> >
>> >> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
>> >> amsat-bb@?????.???> wrote:
>> >>
>> >> 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
>> >> _______________________________________________
>> >> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> >> to all interested persons worldwide without requiring membership.
Opinions
>> >> expressed
>> >> are solely those of the author, and do not reflect the official views of
>> >> AMSAT-NA.
>> >> Not an AMSAT-NA member? Join now to support the amateur satellite
program!
>> >> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>> >>
>> > --
>> > Brian Wilkins
>> > KO4AQF
>> > _______________________________________________
>> > Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> > to all interested persons worldwide without requiring membership.
Opinions expressed
>> > are solely those of the author, and do not reflect the official views
of AMSAT-NA.
>> > Not an AMSAT-NA member? Join now to support the amateur satellite
program!
>> > Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
> --
> Brian Wilkins
> KO4AQF
_______________________________________________
Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
to all interested persons worldwide without requiring membership. Opinions
expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb





------------------------------

Message: 7
Date: Tue, 28 Apr 2020 08:47:57 -0400
From: Stephen DeVience <sjdevience@?????.???>
To: nathanjwhite <nathanjwhite@????????.???>
Cc: amsat-bb@?????.???
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CAMPfQQCainF7D8LFuNTCY_6bEzEL+JV2gj9AUyHtAeO-2_LoDg@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

I listened to that Satnogs recording again, and I hear a single beep
courtesy tone between transmissions from each person, so I think it's a
repeater. It has some points where the repeater conversation stops and then
appears to bring up the satellite again, so I would think it needs to match
the tone. Maybe someone here can better explain how the Fox tone squelch
works, for example how long it stays on after hearing a tone.

The repeater that I suspect has echolink, so maybe I can get on it during a
pass and get a recording.

-Stephen, N8URE

On Mon, Apr 27, 2020 at 11:05 PM nathanjwhite <nathanjwhite@????????.???>
wrote:

> A couple of weeks ago we identified 2 stations overheard on AO-92 with
> apparent Boston area QTH (Waltham and Harvard) but still no indication of a
> repeater.
> AMSAT has a recording of the pass.
>
> Nate
> N5LEX
>
> On Monday, April 27, 2020, 10:44 PM, Mike Diehl via AMSAT-BB <
> amsat-bb@?????.???> wrote:
>
> Cool, it?s challenging because the length of passes aren?t much longer
> than the interval to ID. It?s frustrating but perseverance pays off.
>
> 73,
> Mike Diehl
> W8LID/VE6LID
>
> > On Apr 27, 2020, at 22:37, Brian Wilkins KO4AQF <bwilkins@?????.???>
> wrote:
> >
> > ?
> > That?s what I meant. Thanks Mike. Already been communicating with
> Glasbrenner
> >
> >> On Mon, Apr 27, 2020 at 10:32 PM Mike Diehl <diehl.mike.a@?????.???>
> wrote:
> >> AMSAT can only sort it out with the help from users, they have no magic
> wand. Through a process of elimination the region the offender is located
> in can be narrowed down by figuring out a common footprint. Continued
> monitoring can also reveal a repeater or user ID. This process has been
> used in the past to track down offenders. Keep listening and forward any
> call signs you hear, AMSAT will definitely reach out to them. Also,
> recordings help.
> >>
> >> 73,
> >> Mike Diehl
> >> W8LID/VE6LID
> >>
> >> > On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB <
> amsat-bb@?????.???> wrote:
> >> >
> >> > ?I heard it too at the same time-ish maybe about 1532z though from
> Florida
> >> > on a 4/26 pass from the North to South. Hopefully AMSAT can sort this
> one
> >> > out
> >> >
> >> >> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
> >> >> amsat-bb@?????.???> wrote:
> >> >>
> >> >> 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
> >> >> _______________________________________________
> >> >> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum
> available
> >> >> to all interested persons worldwide without requiring membership.
> Opinions
> >> >> expressed
> >> >> are solely those of the author, and do not reflect the official
> views of
> >> >> AMSAT-NA.
> >> >> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> >> >> Subscription settings:
> https://www.amsat.org/mailman/listinfo/amsat-bb
> >> >>
> >> > --
> >> > Brian Wilkins
> >> > KO4AQF
> >> > _______________________________________________
> >> > Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
> >> > to all interested persons worldwide without requiring membership.
> Opinions expressed
> >> > are solely those of the author, and do not reflect the official views
> of AMSAT-NA.
> >> > Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> >> > Subscription settings:
> https://www.amsat.org/mailman/listinfo/amsat-bb
> > --
> > Brian Wilkins
> > KO4AQF
> _______________________________________________
> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> expressed
> are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>
>


------------------------------

Message: 8
Date: Tue, 28 Apr 2020 09:03:18 -0400
From: Brian Wilkins KO4AQF <bwilkins@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CAO_Eq30+kuGAxxiPUt1wozVotYjBb7qZSTfMFqDnKaWF9UDf9Q@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Maybe it?s a coincidence however at one point I was chatting with some guys
earlier this year on EchoLink in the Northeast and there was suggestion on
connecting his EchoLink setup to AMSAT. I had forgotten about it until you
mentioned it. I don?t have any hard evidence it was done so I am not going
to out anyone here

On Tue, Apr 28, 2020 at 8:48 AM Stephen DeVience <sjdevience@?????.???>
wrote:

> I listened to that Satnogs recording again, and I hear a single beep
> courtesy tone between transmissions from each person, so I think it's a
> repeater. It has some points where the repeater conversation stops and then
> appears to bring up the satellite again, so I would think it needs to match
> the tone. Maybe someone here can better explain how the Fox tone squelch
> works, for example how long it stays on after hearing a tone.
>
> The repeater that I suspect has echolink, so maybe I can get on it during
> a pass and get a recording.
>
> -Stephen, N8URE
>
> On Mon, Apr 27, 2020 at 11:05 PM nathanjwhite <nathanjwhite@????????.???>
> wrote:
>
>> A couple of weeks ago we identified 2 stations overheard on AO-92 with
>> apparent Boston area QTH (Waltham and Harvard) but still no indication of a
>> repeater.
>> AMSAT has a recording of the pass.
>>
>> Nate
>> N5LEX
>>
>> On Monday, April 27, 2020, 10:44 PM, Mike Diehl via AMSAT-BB <
>> amsat-bb@?????.???> wrote:
>>
>> Cool, it?s challenging because the length of passes aren?t much longer
>> than the interval to ID. It?s frustrating but perseverance pays off.
>>
>> 73,
>> Mike Diehl
>> W8LID/VE6LID
>>
>> > On Apr 27, 2020, at 22:37, Brian Wilkins KO4AQF <bwilkins@?????.???>
>> wrote:
>> >
>> > ?
>> > That?s what I meant. Thanks Mike. Already been communicating with
>> Glasbrenner
>> >
>> >> On Mon, Apr 27, 2020 at 10:32 PM Mike Diehl <diehl.mike.a@?????.???>
>> wrote:
>> >> AMSAT can only sort it out with the help from users, they have no
>> magic wand. Through a process of elimination the region the offender is
>> located in can be narrowed down by figuring out a common footprint.
>> Continued monitoring can also reveal a repeater or user ID. This process
>> has been used in the past to track down offenders. Keep listening and
>> forward any call signs you hear, AMSAT will definitely reach out to them.
>> Also, recordings help.
>> >>
>> >> 73,
>> >> Mike Diehl
>> >> W8LID/VE6LID
>> >>
>> >> > On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB <
>> amsat-bb@?????.???> wrote:
>> >> >
>> >> > ?I heard it too at the same time-ish maybe about 1532z though from
>> Florida
>> >> > on a 4/26 pass from the North to South. Hopefully AMSAT can sort
>> this one
>> >> > out
>> >> >
>> >> >> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
>> >> >> amsat-bb@?????.???> wrote:
>> >> >>
>> >> >> 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
>> >> >> _______________________________________________
>> >> >> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum
>> available
>> >> >> to all interested persons worldwide without requiring membership.
>> Opinions
>> >> >> expressed
>> >> >> are solely those of the author, and do not reflect the official
>> views of
>> >> >> AMSAT-NA.
>> >> >> Not an AMSAT-NA member? Join now to support the amateur satellite
>> program!
>> >> >> Subscription settings:
>> https://www.amsat.org/mailman/listinfo/amsat-bb
>> >> >>
>> >> > --
>> >> > Brian Wilkins
>> >> > KO4AQF
>> >> > _______________________________________________
>> >> > Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum
>> available
>> >> > to all interested persons worldwide without requiring membership.
>> Opinions expressed
>> >> > are solely those of the author, and do not reflect the official
>> views of AMSAT-NA.
>> >> > Not an AMSAT-NA member? Join now to support the amateur satellite
>> program!
>> >> > Subscription settings:
>> https://www.amsat.org/mailman/listinfo/amsat-bb
>> > --
>> > Brian Wilkins
>> > KO4AQF
>> _______________________________________________
>> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> to all interested persons worldwide without requiring membership.
>> Opinions expressed
>> are solely those of the author, and do not reflect the official views of
>> AMSAT-NA.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>>
>> --
Brian Wilkins
KO4AQF


------------------------------

Message: 9
Date: Tue, 28 Apr 2020 09:36:34 -0400
From: Burns Fisher <wb1fj-bb@??????.??>
To: Brian Wilkins KO4AQF <bwilkins@?????.???>
Cc: AMSAT BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CABX7KxV5Whric4G1E-rDtAJYtsJusYu_bFXZOENKzJPqyRiDbQ@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

>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

>
>


------------------------------

Message: 10
Date: Tue, 28 Apr 2020 10:06:08 -0400
From: Stephen DeVience <sjdevience@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] Repeater interference on AO-92
Message-ID:
<CAMPfQQD9E1MH1Fv9+NZg+zt9vx+xhAEZb5fF1rxq3Jxb2=p6Tg@????.?????.???>
Content-Type: text/plain; charset="UTF-8"

Thanks Burns, that's a great explanation of the tones. In that case it
could be any of the 145.11 repeaters in that region on a third harmonic, or
someone who picked the uplink frequency for an uncoordinated repeater, as
has been mentioned.

-Stephen

On Tue, Apr 28, 2020 at 8:47 AM Stephen DeVience <sjdevience@?????.???>
wrote:

> I listened to that Satnogs recording again, and I hear a single beep
> courtesy tone between transmissions from each person, so I think it's a
> repeater. It has some points where the repeater conversation stops and then
> appears to bring up the satellite again, so I would think it needs to match
> the tone. Maybe someone here can better explain how the Fox tone squelch
> works, for example how long it stays on after hearing a tone.
>
> The repeater that I suspect has echolink, so maybe I can get on it during
> a pass and get a recording.
>
> -Stephen, N8URE
>
> On Mon, Apr 27, 2020 at 11:05 PM nathanjwhite <nathanjwhite@????????.???>
> wrote:
>
>> A couple of weeks ago we identified 2 stations overheard on AO-92 with
>> apparent Boston area QTH (Waltham and Harvard) but still no indication of a
>> repeater.
>> AMSAT has a recording of the pass.
>>
>> Nate
>> N5LEX
>>
>> On Monday, April 27, 2020, 10:44 PM, Mike Diehl via AMSAT-BB <
>> amsat-bb@?????.???> wrote:
>>
>> Cool, it?s challenging because the length of passes aren?t much longer
>> than the interval to ID. It?s frustrating but perseverance pays off.
>>
>> 73,
>> Mike Diehl
>> W8LID/VE6LID
>>
>> > On Apr 27, 2020, at 22:37, Brian Wilkins KO4AQF <bwilkins@?????.???>
>> wrote:
>> >
>> > ?
>> > That?s what I meant. Thanks Mike. Already been communicating with
>> Glasbrenner
>> >
>> >> On Mon, Apr 27, 2020 at 10:32 PM Mike Diehl <diehl.mike.a@?????.???>
>> wrote:
>> >> AMSAT can only sort it out with the help from users, they have no
>> magic wand. Through a process of elimination the region the offender is
>> located in can be narrowed down by figuring out a common footprint.
>> Continued monitoring can also reveal a repeater or user ID. This process
>> has been used in the past to track down offenders. Keep listening and
>> forward any call signs you hear, AMSAT will definitely reach out to them.
>> Also, recordings help.
>> >>
>> >> 73,
>> >> Mike Diehl
>> >> W8LID/VE6LID
>> >>
>> >> > On Apr 27, 2020, at 22:07, Brian Wilkins KO4AQF via AMSAT-BB <
>> amsat-bb@?????.???> wrote:
>> >> >
>> >> > ?I heard it too at the same time-ish maybe about 1532z though from
>> Florida
>> >> > on a 4/26 pass from the North to South. Hopefully AMSAT can sort
>> this one
>> >> > out
>> >> >
>> >> >> On Mon, Apr 27, 2020 at 9:22 AM Stephen DeVience via AMSAT-BB <
>> >> >> amsat-bb@?????.???> wrote:
>> >> >>
>> >> >> 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
>> >> >> _______________________________________________
>> >> >> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum
>> available
>> >> >> to all interested persons worldwide without requiring membership.
>> Opinions
>> >> >> expressed
>> >> >> are solely those of the author, and do not reflect the official
>> views of
>> >> >> AMSAT-NA.
>> >> >> Not an AMSAT-NA member? Join now to support the amateur satellite
>> program!
>> >> >> Subscription settings:
>> https://www.amsat.org/mailman/listinfo/amsat-bb
>> >> >>
>> >> > --
>> >> > Brian Wilkins
>> >> > KO4AQF
>> >> > _______________________________________________
>> >> > Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum
>> available
>> >> > to all interested persons worldwide without requiring membership.
>> Opinions expressed
>> >> > are solely those of the author, and do not reflect the official
>> views of AMSAT-NA.
>> >> > Not an AMSAT-NA member? Join now to support the amateur satellite
>> program!
>> >> > Subscription settings:
>> https://www.amsat.org/mailman/listinfo/amsat-bb
>> > --
>> > Brian Wilkins
>> > KO4AQF
>> _______________________________________________
>> Sent via AMSAT-BB@?????.???. AMSAT-NA makes this open forum available
>> to all interested persons worldwide without requiring membership.
>> Opinions expressed
>> are solely those of the author, and do not reflect the official views of
>> AMSAT-NA.
>> Not an AMSAT-NA member? Join now to support the amateur satellite program!
>> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>>
>>


------------------------------

Subject: Digest Footer

_______________________________________________
Sent via amsat-bb@?????.???.
AMSAT-NA makes this open forum available to all interested persons worldwide
without requiring membership.  Opinions expressed
are solely those of the author, and do not reflect the official views of
AMSAT-NA.
Not an AMSAT member? Join now to support the amateur satellite program!
https://www.amsat.org/mailman/listinfo/amsat-bb

------------------------------

End of AMSAT-BB Digest, Vol 15, Issue 129
*****************************************


Read previous mail | Read next mail


 11.05.2024 11:47:02lGo back Go up