| |
CX2SA > SATDIG 18.04.17 16:24l 1012 Lines 39272 Bytes #999 (0) @ WW
BID : AMSATBB12107
Read: GUEST
Subj: AMSAT-BB-digest V12 107
Path: IW8PGT<IZ3LSV<I0OJJ<N6RME<CX2SA
Sent: 170418/1414Z @:CX2SA.SAL.URY.SOAM #:5312 [Salto] FBB7.00e $:AMSATBB12107
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: Thoughts on ISS packet switch back to 145.825 MHz (long)
(Scott)
2. Re: Thoughts on ISS packet switch back to 145.825 MHz (long)
(Mike Diehl)
3. PSAT APRS (Mark Lunday)
4. My apologies (Kevin M)
5. Re: AO-73/FUNcube Mode switch (Jim Heck G3WGM)
6. Re: PSAT APRS (Mike Rupprecht)
7. Re: Thoughts on ISS packet switch back to 145.825 MHz(long)
(Dave L PhD)
----------------------------------------------------------------------
Message: 1
Date: Mon, 17 Apr 2017 20:17:10 -0700
From: Scott <ka7fvv@xxxxx.xxx>
To: Stefan Wagener <wageners@xxxxx.xxx>
Cc: AMSAT Mailing List <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Thoughts on ISS packet switch back to 145.825
MHz (long)
Message-ID: <78CE77CB-98D1-4FAA-BBAF-FCE7558CE85A@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
I am really not sure what the heartburn is here now that ISS is back on VHF.
Nothing is taking place any differently than would have been happening
before October. I have digipeated through ISS with my FT1DR to show up on
the ISS Heard list. That is obviously what some of the station on the log
provided were doing as well. That is totally acceptable. If you see a
response from ISS there should be no need to try further. The key of course
is to manually transmit and not setup the beacon. The FT1DR is not
conducive for easy messaging. I have done successful messaging with an
APRSIS32/TNC setup in the past. I will be trying APRSDroid to do the same
in the near future.
73. Scott, KA7FVV
President - KBARA
http://www.ka7fvv.net
Co-Owner 443.525 System Fusion Digital/Analog Repeater, Spokane WA
> On Apr 17, 2017, at 19:51, Stefan Wagener <wageners@xxxxx.xxx> wrote:
>
> Thanks Mike,
>
> I appreciate your open, thoughtful and constructive discussion. Since you
> don't even seem to have read the log, and the timestamp stations are
> digipeating, I leave you to your beliefs.
>
> I will stay to the facts and exit this discussion. :-) :-) :-)
>
> 73, Stefan VE4NSA
>
>
>> On Mon, Apr 17, 2017 at 8:22 PM, Mike Diehl <diehl.mike.a@xxxxx.xxx> wrote:
>>
>> Congrats Stefan, you still have no idea what ISS heard, only what it
>> digipeated. Please also prove me wrong that a simplex channel can support
>> more than 50% utilization. The fact only 5% of the pass had the ISS radio
>> transmitting can either prove nothing or support the fact that there is so
>> much QRM AT THE ISS that very few complete packets were heard and
>> digipeated.
>>
>> As far as black listing goes the FCC has no authority over what data a
>> site decides to exclude from showing. Sorry but you're reading and not
>> comprehending what I stated.
>>
>> 73,
>>
>> Mike Diehl
>> AI6GS
>>
>> On Apr 17, 2017, at 5:30 PM, Stefan Wagener <wageners@xxxxx.xxx> wrote:
>>
>> Well Mike,
>>
>> Here is my log from the last pass. It shows 29 digipeats (~75% decoding
>> success at my station) for 8+ minutes. Each packet is barely 1 1/2 seconds!
>> That is a utilization of less then 5% assuming my math is correct.
>>
>> In addition, asking for "blacklisting of licensed operators" is something
>> I certainly will not support and fortunately neither does the FCC.
>>
>> 73, Stefan, VE4NSA
>>
>>
>> ..........................................
>>
>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:46:17] >ARISS - International
>> Space Station
>>
>> Fm KE7ZXE-4 To CQ Via RS0ISS <UI pid=F0 Len=28 >[18:47:17]
>>
>> N7UWX DE KE7ZXE from CN86 me
>>
>> Fm VE6PW To U1PSWQ Via RS0ISS,ARISS <UI pid=F0 Len=32 >[18:47:59] `*Zvl
>> _-/` Hello via ISS _%
>>
>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:48:18] >ARISS - International
>> Space Station
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:49:51]`p0Kl p[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:01]`p0Kl }[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:11]`p0Kl j[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:17] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:50:18] >ARISS - International
>> Space Station
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:24] `p0Kl O[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:28] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:35] :KD0KZE :599
>> Via ISS de W8LR Jerry{62
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:39] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:50:49]
>> 'u&Bl _-/]CQ via ARISS,EN56jd,Paul=
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:55] :KD0KZE :599
>> Via ISS de W8LR Jerry{62
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:58] :N7EKY-6 :599
>> Via ISS de W8LR Jerry{63
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:51:01] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:11] `p0Kl w[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:21] `p0Kl"F[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2U Via RS0ISS <UI pid=F0 Len=47 >[18:51:38] `p0Kl!%[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:52:07] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:10] :KD0KZE :599
>> Via ISS de W8LR Jerry{62
>>
>> Fm W0BSH-3 To S8SW6R Via RS0ISS <UI pid=F0 Len=16 >[18:52:10] `v06l
>> _>/]"5v}=
>>
>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:52:16]
>> 'u&Bl _-/]CQ via ARISS,EN56jd,Paul=
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:27] :N7EKY-6 :599
>> Via ISS de W8LR Jerry{63
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:30] :N7EKY-6 :599
>> Via ISS de W8LR Jerry{64
>>
>> Fm W8LR To APK003 Via TS0ISS <UI pid=F0 Len=40 >[18:53:13] :N7EKY-6# :599
>> Via QSS de W8LR Jerry{07
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:53:15] :W0BSH-3 :599
>> Via ISS de W8LR Jerry{65
>>
>>
>>
>> On Mon, Apr 17, 2017 at 4:51 PM, Mike Diehl <diehl.mike.a@xxxxx.xxx>
>> wrote:
>>
>>> Greg,
>>>
>>> You make a good point about the complications of dropped packets. I have
>>> some good recordings of voice stations getting a call back when as little
>>> as a single letter of their call was heard. It's amazing how well we can
>>> learn the voices of other ops when you're on regularly. This simply
doesn't
>>> happen on packet.
>>>
>>> Another complication is that it is on simplex. That means on a 10 minute
>>> pass the maximum amount of time possible to digipeat is 5 minutes if the
>>> channel is fully saturated. Subtract out the ISS beacons we end up with
>>> less than 50% of the pass available for ISS to hear you.
>>>
>>> I'm not sure what the best solution is. You do bring up an interesting
>>> point about APRS-IS. Maybe it's possible to have them black list fixed
>>> beacon stations and remove the vanity aspect like you mentioned.
>>>
>>> 73,
>>>
>>> Mike Diehl
>>> AI6GS
>>>
>>>> On Apr 17, 2017, at 1:26 PM, Greg D <ko6th.greg@xxxxx.xxx> wrote:
>>>>
>>>> Gabriel Zeifman wrote:
>>>>> It's not complicated. However much it may be insisted ISS packet is not
>>>>> SO-50, it is practically the same thing (single channel operating on
>>> FM).
>>>> Actually, the ISS digi is worse.
>>>>
>>>> With voice communication, one can sometimes pick up the start or tail of
>>>> a call sign, as the astronaut demonstrated, and use that to filter a
>>>> second try. With digital, any bits that get corrupted result in no
>>>> reception at all.
>>>>
>>>> I hate to suggest this, and admit I am assuming a cause without
>>>> supporting evidence, but it might be necessary to remove the "vanity"
>>>> aspect of ISS digipeating, and take down or hide from general view the
>>>> reporting sites that support it. While a useful tool for
>>>> troubleshooting, I suspect the vanity aspect of seeing your call in a
>>>> public list day after day from an unattended station may be too strong a
>>>> draw for some, resulting in the clogged channel. The SatGates that
>>>> monitor for ISS and other APRS satellite traffic are still important
>>>> part of the infrastructure, so that the information can be datamined
>>>> from APRS-IS if you need it for troubleshooting. But the consolidated
>>>> lists of who has been seen digipeating through the ISS, I think, may be
>>>> contributing more trouble than they are worth.
>>>>
>>>> Greg KO6TH
>>>>
>>>> _______________________________________________
>>>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>> _______________________________________________
>>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>>
>>
>>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 2
Date: Mon, 17 Apr 2017 20:27:23 -0700
From: Mike Diehl <diehl.mike.a@xxxxx.xxx>
To: Greg D <ko6th.greg@xxxxx.xxx>
Cc: AMSAT Mailing List <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Thoughts on ISS packet switch back to 145.825
MHz (long)
Message-ID: <709BD2A5-E8AE-4703-8A9E-D99305906841@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Greg,
Thanks for the read. My point was just general simplex leaving protocols and
other factors out just to keep it simple. Like you point out, adding in
overhead we loose even more time.
The major problem though is that the terrestrial stations can't hear each
other so the door is wide open for collisions. Which is why unmanned beacons
are trouble.
I think what is being lost here is what is happening at the bird. It's not
like a linear or FM transponder on full duplex where we can hear what is
happening. We all know when we have a dead carrier on voice because the bird
is instantly transmitting what it hears. Now in the case of simplex if a
dead carrier was thrown at ISS for the whole pass then how exactly would we
know? One could assume nobody was on.
Lots of packets heard from the station can prove a lot were heard and
decoded properly. A lack of packets can indicate two things, either it
wasn't receiving a lot or there were too many. That's the point I've been
trying to make this whole time. Beacons should be seen for what they are,
stations just simply increasing the odds of collisions at the ISS receiver.
73,
Mike Diehl
AI6GS
> On Apr 17, 2017, at 7:45 PM, Greg D <ko6th.greg@xxxxx.xxx> wrote:
>
> I believe APRS Packet is basically an Aloha network. See
https://en.wikipedia.org/wiki/ALOHAnet
>
> 18.4% is the theoretical limit... Yes, surprisingly low. See the article
for the math behind it.
>
> Greg KO6TH
>
>
> Mike Diehl wrote:
>> Congrats Stefan, you still have no idea what ISS heard, only what it
digipeated. Please also prove me wrong that a simplex channel can support
more than 50% utilization. The fact only 5% of the pass had the ISS radio
transmitting can either prove nothing or support the fact that there is so
much QRM AT THE ISS that very few complete packets were heard and digipeated.
>>
>> As far as black listing goes the FCC has no authority over what data a
site decides to exclude from showing. Sorry but you're reading and not
comprehending what I stated.
>>
>> 73,
>>
>> Mike Diehl
>> AI6GS
>>
>> On Apr 17, 2017, at 5:30 PM, Stefan Wagener <wageners@xxxxx.xxx> wrote:
>>
>>> Well Mike,
>>>
>>> Here is my log from the last pass. It shows 29 digipeats (~75% decoding
success at my station) for 8+ minutes. Each packet is barely 1 1/2 seconds!
That is a utilization of less then 5% assuming my math is correct.
>>>
>>> In addition, asking for "blacklisting of licensed operators" is
something I certainly will not support and fortunately neither does the FCC.
>>>
>>> 73, Stefan, VE4NSA
>>>
>>>
>>> ..........................................
>>>
>>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:46:17] >ARISS - International
Space Station
>>> Fm KE7ZXE-4 To CQ Via RS0ISS <UI pid=F0 Len=28 >[18:47:17]
>>> N7UWX DE KE7ZXE from CN86 me
>>> Fm VE6PW To U1PSWQ Via RS0ISS,ARISS <UI pid=F0 Len=32 >[18:47:59] `*Zvl
_-/` Hello via ISS _%
>>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:48:18] >ARISS - International
Space Station
>>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:49:51]`p0Kl p[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:01]`p0Kl }[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:11]`p0Kl j[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:17] `yaHl _-/
Greetings via ISS from Circle Pines MN
>>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:50:18] >ARISS - International
Space Station
>>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:24] `p0Kl O[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:28] `yaHl _-/
Greetings via ISS from Circle Pines MN
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:35] :KD0KZE
:599 Via ISS de W8LR Jerry{62
>>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:39] `yaHl _-/
Greetings via ISS from Circle Pines MN
>>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:50:49]
'u&Bl _-/]CQ via ARISS,EN56jd,Paul=
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:55] :KD0KZE
:599 Via ISS de W8LR Jerry{62
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:58] :N7EKY-6
:599 Via ISS de W8LR Jerry{63
>>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:51:01] `yaHl _-/
Greetings via ISS from Circle Pines MN
>>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:11] `p0Kl w[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:21] `p0Kl"F[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm W8LR To S9SR2U Via RS0ISS <UI pid=F0 Len=47 >[18:51:38] `p0Kl!%[/>CQ:
Via ISS de W8LR Middletown Ohio=
>>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:52:07] `yaHl _-/
Greetings via ISS from Circle Pines MN
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:10] :KD0KZE
:599 Via ISS de W8LR Jerry{62
>>> Fm W0BSH-3 To S8SW6R Via RS0ISS <UI pid=F0 Len=16 >[18:52:10] `v06l
_>/]"5v}=
>>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:52:16]
'u&Bl _-/]CQ via ARISS,EN56jd,Paul=
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:27] :N7EKY-6
:599 Via ISS de W8LR Jerry{63
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:30] :N7EKY-6
:599 Via ISS de W8LR Jerry{64
>>> Fm W8LR To APK003 Via TS0ISS <UI pid=F0 Len=40 >[18:53:13] :N7EKY-6#
:599 Via QSS de W8LR Jerry{07
>>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:53:15] :W0BSH-3
:599 Via ISS de W8LR Jerry{65
>>>
>>>
>>>> On Mon, Apr 17, 2017 at 4:51 PM, Mike Diehl <diehl.mike.a@xxxxx.xxx>
wrote:
>>>> Greg,
>>>>
>>>> You make a good point about the complications of dropped packets. I
have some good recordings of voice stations getting a call back when as
little as a single letter of their call was heard. It's amazing how well we
can learn the voices of other ops when you're on regularly. This simply
doesn't happen on packet.
>>>>
>>>> Another complication is that it is on simplex. That means on a 10
minute pass the maximum amount of time possible to digipeat is 5 minutes if
the channel is fully saturated. Subtract out the ISS beacons we end up with
less than 50% of the pass available for ISS to hear you.
>>>>
>>>> I'm not sure what the best solution is. You do bring up an interesting
point about APRS-IS. Maybe it's possible to have them black list fixed
beacon stations and remove the vanity aspect like you mentioned.
>>>>
>>>> 73,
>>>>
>>>> Mike Diehl
>>>> AI6GS
>>>>
>>>> > On Apr 17, 2017, at 1:26 PM, Greg D <ko6th.greg@xxxxx.xxx> wrote:
>>>> >
>>>> > Gabriel Zeifman wrote:
>>>> >> It's not complicated. However much it may be insisted ISS packet is
not
>>>> >> SO-50, it is practically the same thing (single channel operating on
FM).
>>>> > Actually, the ISS digi is worse.
>>>> >
>>>> > With voice communication, one can sometimes pick up the start or tail
of
>>>> > a call sign, as the astronaut demonstrated, and use that to filter a
>>>> > second try. With digital, any bits that get corrupted result in no
>>>> > reception at all.
>>>> >
>>>> > I hate to suggest this, and admit I am assuming a cause without
>>>> > supporting evidence, but it might be necessary to remove the "vanity"
>>>> > aspect of ISS digipeating, and take down or hide from general view the
>>>> > reporting sites that support it. While a useful tool for
>>>> > troubleshooting, I suspect the vanity aspect of seeing your call in a
>>>> > public list day after day from an unattended station may be too
strong a
>>>> > draw for some, resulting in the clogged channel. The SatGates that
>>>> > monitor for ISS and other APRS satellite traffic
are still important
>>>> > part of the infrastructure, so that the information can be datamined
>>>> > from APRS-IS if you need it for troubleshooting. But the consolidated
>>>> > lists of who has been seen digipeating through the ISS, I think, may be
>>>> > contributing more trouble than they are worth.
>>>> >
>>>> > Greg KO6TH
>>>> >
>>>> > _______________________________________________
>>>> > Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>>> _______________________________________________
>>>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>>
>
------------------------------
Message: 3
Date: Mon, 17 Apr 2017 13:18:27 +0000
From: Mark Lunday <wd4elg@xxxxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] PSAT APRS
Message-ID:
<CO2PR06MB4916E8346B2DD6E587EF22795060@xxxxxxxxxxxx.xxxxxxxx.xxxx.xxxxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
What is the logic for the digipeater on/off? Is it illumination? Both
passes were off (PSAT-1 callsign)
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[23:46:20]
T#578,789,347,885,889,789,00011100
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[07:57:38]
T#062,813,074,957,550,803,00011100
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=15 >[07:58:21]
s#005459,0z001
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[07:58:39]
T#063,814,072,955,543,803,00011100
Mark Lunday, WD4ELG
Greensboro, NC FM06be
wd4elg@xxxx.xxx
http://wd4elg.blogspot.com
SKCC #16439 FISTS #17972
------------------------------
Message: 4
Date: Tue, 18 Apr 2017 07:34:34 +0000 (UTC)
From: Kevin M <n4ufo@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] My apologies
Message-ID: <1095680313.2483277.1492500874648@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
There was a recent exchange on the BB here, where there were a lot of long
e-mails that I somehow manged to read a few of out of order, missed a few
words here and there that changed the meaning, etc. And in an attempt to
'help' I jumped in with my two cents trying to clear up what I thought was a
simple misunderstanding which met with less than spectacular results. I also
injected a bit of sarcasm in an attempt to insert some humor, when the
situation was most likely beyond the point of such an attempt. In the end, I
may have done nothing more than to upset folks on both sides.
I simply want to say... my apologies to anyone that 'I' offended, and my
apologies for proverbially 'butting my nose in' when it wasn't warranted.
And if I created or 'enhanced' any existing hard feelings, again, my
apologies.
Ham radio... it's for fun. Life is too short. (Some disclaimers may apply.)
Sincerely,? Kevin Manzer N4UFO
------------------------------
Message: 5
Date: Tue, 18 Apr 2017 08:42:03 +0100
From: "Jim Heck G3WGM" <jimlist@xxxx.xxx>
To: "Jim Heck G3WGM" <jim@xxxxxx.xx.xxx>, <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] AO-73/FUNcube Mode switch
Message-ID: <E85247E9C7B14C22A6B23DD22D7CC630@xxxxxx>
Content-Type: text/plain; format=flowed; charset="UTF-8";
reply-type=response
Hi Folks,
This is to let you know that I have just switched AO-73/FUNcube back into
autonomous mode, ie Educational mode when in sunlight, and amateur mode (low
power beacon with transponder ON) when in eclipse.
This switch was done later than normal (normally done Sunday evenings UTC)
due to the Easter Holidays.
73s Jim G3WGM and the FUNcube Team
++++++++++++++++++++++++++++++++++
FUNcube frequencies and other details
++++++++++++++++++++++++++++++++++
AO-73 FUNcube-1
The transponder is normally operational only when the satellite is in
eclipse, ie the solar panels are NOT being illuminated. During weekends
(from pm Fridays UTC to PM Sundays UTC) the transponder is operational 24/7.
When the transponder is switched off, the telemetry beacon is on full power,
when the transponder is on the beacon it is on low power. During holidays,
eg Christmas, New Year, Easter, etc, the transponder maybe activated for
extended periods. Watch AMSAT-BB for announcements which are usually made on
Friday evenings (UTC)
The nominal transponder frequencies are:
Uplink: 435.150 - 435.130 MHz LSB (Inverting)
Downlink: 145.950 - 145.970 MHz USB
Telemetry Tx: 145.935 MHz BPSK
(The passband may be up to 15kHz higher depending on on-board temps. Low
temperatures give higher freqs!)
FUNcube-2 aka FUNcube on UKube
The FUNcube-2 sub-system continues to operate autonomously and, almost
continuously, in amateur mode. The transponder is operational and the
telemetry downlink is functioning with about 70mW output. The FUNcube-1
Dashboard does not correctly display the telemetry but it does correctly
decode the data and uploads it to the FUNcube Data Warehouse from where it
can be examined. Most of the real time data channels are operational and
these include battery voltages, temperatures and ADCS data coming via the
main On Board Computer (OBC).
The transponder is interrupted for a few seconds every 2 minutes when the
other transmitter sends its CW beacon and, occasionally, for a few seconds
when the main OBC reboots (approx seven times each orbit).
The nominal transponder frequencies are:
Uplink: 435.080 - 435.060 MHz LSB (Inverting)
Downlink: 145.930 - 145.950 MHz USB
Telemetry Tx: 145.915 MHz BPSK
(The passband may be up to 10kHz higher depending on on-board temps. Low
temperatures give higher freqs!)
EO79 FUNcube-3
Due to power budget constraints the transponder cannot be operational 24/7
and an orbit specific schedule has been developed. The transponder will
commence operation 27 minutes after the spacecraft enters sunlight and will
stay on for a period of 25 minutes. This schedule may be modified in future
months as a result of experience.
The nominal transponder frequencies are:
Uplink: 435.0723-435.0473 MHz LSB (Inverting)
Downlink: 145.946-145.971 MHz USB
Further detailed info on EO79 transponder frequencies is at:
https://amsat-uk.org/2016/11/10/eo79-funcube-3-transponder-commences-regular-o
peration/EO88
Nayif-1 FUNcube-5EO88 is presently operating in autonomous mode. The
transponder isoperational when the satellite is in eclipse, ie the solar
panels are NOTbeing illuminated.When the transponder is switched off, the
telemetry beacon is on full power,when the transponder is on the beacon it
is on low power.The transponder frequencies are:Uplink: 435.045 ? 435.015
MHz LSB (inverting)Downlink: 145.960-145.990 MHz USBTelemetry Tx:
145.940MHzAll FUNcube transponders are sponsored by AMSAT-UK and AMSAT-NL.
We are verygrateful for the assistance given by Innovative Solution In Space
Bv, TheNetherlands.
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 6
Date: Tue, 18 Apr 2017 10:19:56 +0200
From: "Mike Rupprecht" <mail@xxxxxxxxxxxxxx.xx>
To: "'Mark Lunday'" <wd4elg@xxxxxxx.xxx>
Cc: 'AMSAT BB' <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] PSAT APRS
Message-ID: <000801d2b81c$90727160$b1575420$@xx>
Content-Type: text/plain; charset="iso-8859-1"
Hi Mark,
There was a reset due to low battery voltage some days ago. The default
setting after an reset is transponder off.
At the moment all European passes are at night. This is unfavorable for
commanding ;-)
73 Mike
DK3WN
-----Urspr?ngliche Nachricht-----
Von: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx Im Auftrag von Mark Lunday
Gesendet: 17 April 2017 15:18
An: AMSAT BB
Betreff: [amsat-bb] PSAT APRS
What is the logic for the digipeater on/off? Is it illumination? Both
passes were off (PSAT-1 callsign)
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[23:46:20]
T#578,789,347,885,889,789,00011100
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[07:57:38]
T#062,813,074,957,550,803,00011100
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=15 >[07:58:21]
s#005459,0z001
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[07:58:39]
T#063,814,072,955,543,803,00011100
Mark Lunday, WD4ELG
Greensboro, NC FM06be
wd4elg@xxxx.xxx
http://wd4elg.blogspot.com
SKCC #16439 FISTS #17972
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 7
Date: Tue, 18 Apr 2017 06:32:24 -0700
From: "Dave L PhD" <doc@xxxxxxx.xxx>
To: "Scott" <ka7fvv@xxxxx.xxx>, "Stefan Wagener" <wageners@xxxxx.xxx>
Cc: AMSAT Mailing List <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Thoughts on ISS packet switch back to 145.825
MHz(long)
Message-ID: <83F2F5ADD38B45ED86B9972D62B2B164@xxxx>
Content-Type: text/plain; charset="iso-8859-1"
Everything that has been said in these post's has been going on for 26
years -- ever
sence MIR had a digi. There has been experiments with MIR with split freq's
. etc
It ALL comes down to everyone have fun, have respect for others and enjoy
the
hobby and if you do not like whats happening, there are other birds up there
Dave
N6CO
----- Original Message -----
From: "Scott via AMSAT-BB" <amsat-bb@xxxxx.xxx>
To: "Stefan Wagener" <wageners@xxxxx.xxx>
Cc: "AMSAT Mailing List" <amsat-bb@xxxxx.xxx>
Sent: Monday, April 17, 2017 8:17 PM
Subject: Re: [amsat-bb] Thoughts on ISS packet switch back to 145.825
MHz(long)
I am really not sure what the heartburn is here now that ISS is back on VHF.
Nothing is taking place any differently than would have been happening
before October. I have digipeated through ISS with my FT1DR to show up on
the ISS Heard list. That is obviously what some of the station on the log
provided were doing as well. That is totally acceptable. If you see a
response from ISS there should be no need to try further. The key of course
is to manually transmit and not setup the beacon. The FT1DR is not
conducive for easy messaging. I have done successful messaging with an
APRSIS32/TNC setup in the past. I will be trying APRSDroid to do the same
in the near future.
73. Scott, KA7FVV
President - KBARA
http://www.ka7fvv.net
Co-Owner 443.525 System Fusion Digital/Analog Repeater, Spokane WA
> On Apr 17, 2017, at 19:51, Stefan Wagener <wageners@xxxxx.xxx> wrote:
>
> Thanks Mike,
>
> I appreciate your open, thoughtful and constructive discussion. Since you
> don't even seem to have read the log, and the timestamp stations are
> digipeating, I leave you to your beliefs.
>
> I will stay to the facts and exit this discussion. :-) :-) :-)
>
> 73, Stefan VE4NSA
>
>
>> On Mon, Apr 17, 2017 at 8:22 PM, Mike Diehl <diehl.mike.a@xxxxx.xxx>
>> wrote:
>>
>> Congrats Stefan, you still have no idea what ISS heard, only what it
>> digipeated. Please also prove me wrong that a simplex channel can support
>> more than 50% utilization. The fact only 5% of the pass had the ISS radio
>> transmitting can either prove nothing or support the fact that there is
>> so
>> much QRM AT THE ISS that very few complete packets were heard and
>> digipeated.
>>
>> As far as black listing goes the FCC has no authority over what data a
>> site decides to exclude from showing. Sorry but you're reading and not
>> comprehending what I stated.
>>
>> 73,
>>
>> Mike Diehl
>> AI6GS
>>
>> On Apr 17, 2017, at 5:30 PM, Stefan Wagener <wageners@xxxxx.xxx> wrote:
>>
>> Well Mike,
>>
>> Here is my log from the last pass. It shows 29 digipeats (~75% decoding
>> success at my station) for 8+ minutes. Each packet is barely 1 1/2
>> seconds!
>> That is a utilization of less then 5% assuming my math is correct.
>>
>> In addition, asking for "blacklisting of licensed operators" is something
>> I certainly will not support and fortunately neither does the FCC.
>>
>> 73, Stefan, VE4NSA
>>
>>
>> ..........................................
>>
>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:46:17] >ARISS - International
>> Space Station
>>
>> Fm KE7ZXE-4 To CQ Via RS0ISS <UI pid=F0 Len=28 >[18:47:17]
>>
>> N7UWX DE KE7ZXE from CN86 me
>>
>> Fm VE6PW To U1PSWQ Via RS0ISS,ARISS <UI pid=F0 Len=32 >[18:47:59] `*Zvl
>> _-/` Hello via ISS _%
>>
>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:48:18] >ARISS - International
>> Space Station
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:49:51]`p0Kl p[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:01]`p0Kl }[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:11]`p0Kl j[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:17] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm RS0ISS To CQ <UI pid=F0 Len=36 >[18:50:18] >ARISS - International
>> Space Station
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:50:24] `p0Kl O[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:28] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:35] :KD0KZE :599
>> Via ISS de W8LR Jerry{62
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:50:39] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:50:49]
>> 'u&Bl _-/]CQ via ARISS,EN56jd,Paul=
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:55] :KD0KZE :599
>> Via ISS de W8LR Jerry{62
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:50:58] :N7EKY-6 :599
>> Via ISS de W8LR Jerry{63
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:51:01] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:11] `p0Kl w[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2V Via RS0ISS <UI pid=F0 Len=47 >[18:51:21] `p0Kl"F[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm W8LR To S9SR2U Via RS0ISS <UI pid=F0 Len=47 >[18:51:38] `p0Kl!%[/>CQ:
>> Via ISS de W8LR Middletown Ohio=
>>
>> Fm KD0KZE To TUPX8Y Via RS0ISS <UI pid=F0 Len=49 >[18:52:07] `yaHl _-/
>> Greetings via ISS from Circle Pines MN
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:10] :KD0KZE :599
>> Via ISS de W8LR Jerry{62
>>
>> Fm W0BSH-3 To S8SW6R Via RS0ISS <UI pid=F0 Len=16 >[18:52:10] `v06l
>> _>/]"5v}=
>>
>> Fm N7EKY-6 To T6PY2T Via RS0ISS,WIDE2-1 <UI pid=F0 Len=36 >[18:52:16]
>> 'u&Bl _-/]CQ via ARISS,EN56jd,Paul=
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:27] :N7EKY-6 :599
>> Via ISS de W8LR Jerry{63
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:52:30] :N7EKY-6 :599
>> Via ISS de W8LR Jerry{64
>>
>> Fm W8LR To APK003 Via TS0ISS <UI pid=F0 Len=40 >[18:53:13] :N7EKY-6# :599
>> Via QSS de W8LR Jerry{07
>>
>> Fm W8LR To APK003 Via RS0ISS <UI pid=F0 Len=40 >[18:53:15] :W0BSH-3 :599
>> Via ISS de W8LR Jerry{65
>>
>>
>>
>> On Mon, Apr 17, 2017 at 4:51 PM, Mike Diehl <diehl.mike.a@xxxxx.xxx>
>> wrote:
>>
>>> Greg,
>>>
>>> You make a good point about the complications of dropped packets. I have
>>> some good recordings of voice stations getting a call back when as
>>> little
>>> as a single letter of their call was heard. It's amazing how well we can
>>> learn the voices of other ops when you're on regularly. This simply
>>> doesn't
>>> happen on packet.
>>>
>>> Another complication is that it is on simplex. That means on a 10 minute
>>> pass the maximum amount of time possible to digipeat is 5 minutes if the
>>> channel is fully saturated. Subtract out the ISS beacons we end up with
>>> less than 50% of the pass available for ISS to hear you.
>>>
>>> I'm not sure what the best solution is. You do bring up an interesting
>>> point about APRS-IS. Maybe it's possible to have them black list fixed
>>> beacon stations and remove the vanity aspect like you mentioned.
>>>
>>> 73,
>>>
>>> Mike Diehl
>>> AI6GS
>>>
>>>> On Apr 17, 2017, at 1:26 PM, Greg D <ko6th.greg@xxxxx.xxx> wrote:
>>>>
>>>> Gabriel Zeifman wrote:
>>>>> It's not complicated. However much it may be insisted ISS packet is
>>>>> not
>>>>> SO-50, it is practically the same thing (single channel operating on
>>> FM).
>>>> Actually, the ISS digi is worse.
>>>>
>>>> With voice communication, one can sometimes pick up the start or tail
>>>> of
>>>> a call sign, as the astronaut demonstrated, and use that to filter a
>>>> second try. With digital, any bits that get corrupted result in no
>>>> reception at all.
>>>>
>>>> I hate to suggest this, and admit I am assuming a cause without
>>>> supporting evidence, but it might be necessary to remove the "vanity"
>>>> aspect of ISS digipeating, and take down or hide from general view the
>>>> reporting sites that support it. While a useful tool for
>>>> troubleshooting, I suspect the vanity aspect of seeing your call in a
>>>> public list day after day from an unattended station may be too strong
>>>> a
>>>> draw for some, resulting in the clogged channel. The SatGates that
>>>> monitor for ISS and other APRS satellite traffic are still important
>>>> part of the infrastructure, so that the information can be datamined
>>>> from APRS-IS if you need it for troubleshooting. But the consolidated
>>>> lists of who has been seen digipeating through the ISS, I think, may be
>>>> contributing more trouble than they are worth.
>>>>
>>>> Greg KO6TH
>>>>
>>>> _______________________________________________
>>>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>> _______________________________________________
>>> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>>
>>
>>
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@xxxxx.xxx.
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!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 12, Issue 107
*****************************************
Read previous mail | Read next mail
| |
