| |
CX2SA > SATDIG 18.08.11 03:02l 874 Lines 32313 Bytes #999 (0) @ WW
BID : AMSATBB6472
Read: GUEST
Subj: AMSAT-BB-digest V6 472
Path: IZ3LSV<IK2XDE<DB0RES<ON0AR<HS1LMV<CX2SA
Sent: 110818/0148Z @:CX2SA.LAV.URY.SA #:22484 [Minas] FBB7.00e $:AMSATBB6472
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Today's Topics:
1. Beaconers (Kevin Deane)
2. Re: ARISSat-1 telemetry top submitters (Alan Cresswell)
3. Re: Turn off AGC when receiving BPSK-1000 (Mark L. Hammond)
4. Edusat and Kentucky (charlie Cantrill)
5. ARRISSat-1 Heard Passing Over Cuba (Mike Schaffer)
6. Re: Turn off AGC when receiving BPSK-1000 (Alan Cresswell)
7. ARISSat clock and TLM records (Richard Ferryman)
8. ISS School QSO (James Luhn)
9. Official Word for the 70cm Antenna? (Mike Schaffer)
10. Re: Decoding wideband recordings (Tom Azlin N4ZPT)
11. Re: ARISSat-1 telemetry top submitters (Colin Hurst)
12. Re: Turn off AGC when receiving BPSK-1000 (Phil Karn)
13. Re: ARISSat-1 telemetry top submitters (Alan Cresswell)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Aug 2011 13:12:52 -0700
From: Kevin Deane <summit496@xxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Beaconers
Message-ID: <COL107-W54301387F9D63CDF795E9583280@xxx.xxx>
Content-Type: text/plain; charset="iso-8859-1"
Bob is absolutely right, the people beaconing on 145.825 are ruining it for
others. Which reminds me of the spanking I got for using FM on the SSB
birds, I am sure there would be a lot bigger stink if people were affecting
those satellites and not just the poor forgotten and obviously abused NO-44,
and the countless people trying to talk to beacons on the ISS...
I like my call showing up on the ISS/NO-44 page just as much as the next
guy, but I do it myself not while I am at work or sleeping. Thanks by the
way for the recent fun contacts on the ISS, I am sure the beacon comments
were just as well veiwed as the Qso's...
Kevin
KF7MYK
------------------------------
Message: 2
Date: Wed, 17 Aug 2011 20:18:50 -0000
From: "Alan Cresswell" <alancresswell@xxxx.xx.xx>
To: "'Ben Bishop'" <leorex@xxxxx.xxx>, "'AMSAT'" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: ARISSat-1 telemetry top submitters
Message-ID: <EE1E0CDB59894C8C88E65A2070AFF0ED@xxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hi all,
According to my logs the last Kursk frame I received on the 0405UT pass on
12 August was 720206. The first Kursk frame on the 12 August 2035UT pass
was 944. The interesting thing was that it apparently treated this as a
valid frame. i.e it accumulated and combined all five parts. All Kursk
frames from that point onward have been treated as "exists" and ignored.
2011/08/12-20:36:44 Received Kursk frame 5 with MET=944 len=48. Do we have
<C:\ARISSatTLM\Kursk\KURSK-944.5>?
2011/08/12-20:36:44 No. Saving to <C:\ARISSatTLM\Kursk\KURSK-944.5>.
2011/08/12-20:36:44 Checking for all five parts.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.1>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.2>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.3>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.4>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.5>: OK.
2011/08/12-20:36:44 Combining KURSK parts into
<C:\ARISSatTLM\Kursk\KURSK-944.EXP>.
2011/08/12-20:36:44 Done combining.
2011/08/12-20:36:44 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type E
2011/08/12-20:36:50 Received telemetry frame with MET=1589 Len=371
2011/08/12-20:36:50 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type T
2011/08/12-20:36:58 Received Kursk frame 1 with MET=944 len=516. Do we have
<C:\\ARISSatTLM\Kursk\KURSK-944.1>?
2011/08/12-20:36:58 Yes. <C:\ARISSatTLM\Kursk\KURSK-944.1> exists.
2011/08/12-20:36:58 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type E
73
Alan
ZL2BX
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Ben Bishop
Sent: Wednesday, 17 August 2011 14:36
To: AMSAT
Cc: n0jy@xxxxxxx.xxx
Subject: [amsat-bb] Re:ARISSat-1 ??? telemetry top submitters
G'day Jerry,
I don't think there's anything wrong with your ARISSatTLM, as I've
only been getting KURSK-944s since the 13th.
My last 'proper good' experiment frame was:
2011/08/11-08:12:48 Received Kursk frame 2 with MET=650105 len=516.
Satellite MET around then was:
2011/08/11-08:12:54 Received telemetry frame with MET=653412 Len=371
I missed the 12th, and on the 13th the telemetry and experiment MET had reset:
2011/08/13-04:34:16 Received telemetry frame with MET=2514 Len=371
....
2011/08/13-04:34:24 Received Kursk frame 3 with MET=944 len=516. Do we
have <C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.3>?
2011/08/13-04:34:24 No. Saving to
<C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.3>.
And from that point on, I have only received KURSK-944 frames (which
are still auto-forwarding).
2011/08/17-05:30:04 Received Kursk frame 5 with MET=944 len=48. Do we
have <C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.5>?
2011/08/17-05:30:04 Yes.
<C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.5> exists.
73,
Ben VK2FBRB
On Wed, Aug 17, 2011 at 11:08 PM, <n0jy@xxxxxxx.xxx> wrote:
> A question for all, for a few days now my ARISSatTLM has been reporting
> the Kursk as being (I believe, I'm not at home to check right now)
> something like Kursk-944.x or perhaps it was Kursk-444.x (some real low
> perhaps hung up on that and needs a restart? Anyone else, what are the
> latest Kursk frames that you are seeing?
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3840 - Release Date: 08/17/11
------------------------------
Message: 3
Date: Wed, 17 Aug 2011 16:36:09 -0400
From: "Mark L. Hammond" <marklhammond@xxxxx.xxx>
To: Phil Karn <karn@xxxxxxxx.xxx>, Amsat - BBs <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Turn off AGC when receiving BPSK-1000
Message-ID: <MYcH1h00456cfur05YcHoa@xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
Hi Phil,
This is a great reminder. Thus far, my data has been collected with the
TS-2000x using a "mid" setting for AGC; and with the HDSDR software set to
"AGC Med" when using/playing back Funcube Dongle data. I've set both to
OFF now, since it's possible
I wonder if anybody has experimented with AGC settings and the HDSDR
decoding? Might be worth running a recording through a few times at various
settings..hrm.
In any event, Phil...THANK YOU for making this code real. I have seen it
print data when the signal was visibly "in the dirt" which is impressive and
fun to see.
73!
Mark N8MH
At 02:31 PM 8/16/2011 -0700, Phil Karn wrote:
>I forgot to offer some advice when receiving the ARISSat-1 BPSK-1000
>telemetry beacon: turn off your receiver AGC if at all possible. If you
>can only choose between fast and slow, pick slow. If this causes a large
>variation in audio level, reduce the gain to avoid clipping on the
>peaks. A sound card A/D is 16 bits so you have plenty of dynamic range;
>don't be afraid to use it.
>
>Ideally the background noise level should be constant with the signal
>going up and down.
>
>This greatly helps the demodulator and decoder to distinguish signal
>from noise. The error correction uses the Viterbi algorithm, and one of
>its big features is the ability to distinguish between "strong" and
>"weak" bits; a strong '1' or '0' is considered less likely to be in
>error than a weak '1' or '0'. The decoder can even accept "I don't know"
>for a limited number of bits.
>
>The decoder can still fix errors in strong bits. But it can fix more of
>them in the weak bits and still more in the "I don't knows" (known
>technically as "erasures").
>
>This is especially important when the signal fades deeply, as it often
>does with ARISSat-1. With the AGC off, the audio signal level falls
>during a fade and the decoder can recognize it as a burst of erasures or
>near-erasures.
>
>As with many questions in life, "I don't know" or "I think it's X but
>I'm not sure" are better answers than being sure of the wrong answer.
>
>73, Phil
>_______________________________________________
>Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
>Not an AMSAT-NA member? Join now to support the amateur satellite program!
>Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 4
Date: Wed, 17 Aug 2011 15:50:22 -0700 (PDT)
From: charlie Cantrill <ki4rdt@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Edusat and Kentucky
Message-ID:
<1313621422.74236.YahooMailNeo@xxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1
Looks like Edusat will be partially controlled here from the U.S., right
down the road in Kentucky.
This is Dr. Ben Malphrus KJ4HJV of the Morehead Space Science program.Sounds
like they are preparing to test a Femtosat deployment system. I should point
out, this is where Bob Twiggs is currently teaching.?
http://www.youtube.com/watch?v=ljnK2LVi9hw
Charlie Cantrill
KI4RDT
------------------------------
Message: 5
Date: Wed, 17 Aug 2011 16:16:56 -0700 (PDT)
From: Mike Schaffer <daetsort@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] ARRISSat-1 Heard Passing Over Cuba
Message-ID:
<1313623016.21846.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1
On Wednesday, August 17 heard a very weak ARISSat-1 on 2M 145.950 FM pass
over northeast
Camaguey, Cuba?for less than thirty seconds?in SSTV mode.
?
Minutes later it was tracking northeast?towards northern Cat island, The
Bahamas at 2242 UTC.
?
Azimuth 139, Elevation +22 according to my satellite tracking program.
?
?
73's
?
Mike Schaffer
KA3JAW
Tampa, Florida
EL87
------------------------------
Message: 6
Date: Wed, 17 Aug 2011 23:24:14 -0000
From: "Alan Cresswell" <alancresswell@xxxx.xx.xx>
To: "'Mark L. Hammond'" <marklhammond@xxxxx.xxx>, "'Phil Karn'"
<karn@xxxxxxxx.xxx>, "'Amsat - BBs'" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Turn off AGC when receiving BPSK-1000
Message-ID: <DDABDF4D61AC4DC7A282C07E46E6A5F1@xxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hi Mark, Phil,
That's interesting. I have collected all my passes on the TS2000 with the
AGC on and set to the longest setting. This is mainly because I often
record the signal level every 0.5 seconds during a pass which requires the
AGC to be on and the longest setting irons out any short fades. I will turn
the AGC off and look at the statistics over a few passes but given that with
the AGC on I get almost all the available frames I don't expect to see much
difference. It will be interesting to see.
73
Alan
ZL2BX
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Mark L. Hammond
Sent: Wednesday, 17 August 2011 20:36
To: Phil Karn; Amsat - BBs
Subject: [amsat-bb] Re: Turn off AGC when receiving BPSK-1000
Hi Phil,
This is a great reminder. Thus far, my data has been collected with the
TS-2000x using a "mid" setting for AGC; and with the HDSDR software set to
"AGC Med" when using/playing back Funcube Dongle data. I've set both to
OFF now, since it's possible
I wonder if anybody has experimented with AGC settings and the HDSDR
decoding? Might be worth running a recording through a few times at various
settings..hrm.
In any event, Phil...THANK YOU for making this code real. I have seen it
print data when the signal was visibly "in the dirt" which is impressive and
fun to see.
73!
Mark N8MH
At 02:31 PM 8/16/2011 -0700, Phil Karn wrote:
>I forgot to offer some advice when receiving the ARISSat-1 BPSK-1000
>telemetry beacon: turn off your receiver AGC if at all possible. If you
>can only choose between fast and slow, pick slow. If this causes a large
>variation in audio level, reduce the gain to avoid clipping on the
>peaks. A sound card A/D is 16 bits so you have plenty of dynamic range;
>don't be afraid to use it.
>
>Ideally the background noise level should be constant with the signal
>going up and down.
>
>This greatly helps the demodulator and decoder to distinguish signal
>from noise. The error correction uses the Viterbi algorithm, and one of
>its big features is the ability to distinguish between "strong" and
>"weak" bits; a strong '1' or '0' is considered less likely to be in
>error than a weak '1' or '0'. The decoder can even accept "I don't know"
>for a limited number of bits.
>
>The decoder can still fix errors in strong bits. But it can fix more of
>them in the weak bits and still more in the "I don't knows" (known
>technically as "erasures").
>
>This is especially important when the signal fades deeply, as it often
>does with ARISSat-1. With the AGC off, the audio signal level falls
>during a fade and the decoder can recognize it as a burst of erasures or
>near-erasures.
>
>As with many questions in life, "I don't know" or "I think it's X but
>I'm not sure" are better answers than being sure of the wrong answer.
>
>73, Phil
>_______________________________________________
>Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
>Not an AMSAT-NA member? Join now to support the amateur satellite program!
>Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3841 - Release Date: 08/17/11
------------------------------
Message: 7
Date: Thu, 18 Aug 2011 00:37:27 +0100
From: "Richard Ferryman" <g4bbh@xxxxxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] ARISSat clock and TLM records
Message-ID: <1B0BB8741ADC47EF8A52DF9D4E7D377D@xxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Now that the ARISSat clock seems to be resetting on a regular basis I am
wondering how this will affect the TLM and Kursk data which I am capturing
and uploading. It seems to me that the only way of collating the data is by
the time of upload to telemetry.arissattlm.org
Dick G4BBH
------------------------------
Message: 8
Date: Wed, 17 Aug 2011 18:57:56 -0500
From: James Luhn <luhn@xx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] ISS School QSO
Message-ID: <F876EEBF-A786-479F-9C18-AAA47CE6F804@xx.xxx>
Content-Type: text/plain; charset=us-ascii
I am portable in Alabama and do not have access to my past e-mail. A post a
day or so ago had information about a school that had a scheduled QSO with
the ISS on August 18. I am at a camp in Alabama and would love to at least
monitor the conversation coming from the ISS. Would someone repost the info
or contact me directly with a copy of the post.
73,
James
W5AOO
luhn@xx.xxx
------------------------------
Message: 9
Date: Wed, 17 Aug 2011 17:29:26 -0700 (PDT)
From: Mike Schaffer <daetsort@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Official Word for the 70cm Antenna?
Message-ID:
<1313627366.90794.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1
Mike Schaffer
KA3JAW
Tampa, Florida
EL87
What is the official AMSAT/ARISSat1?team?finding?on the ARISSat-1 70cm
quarter-wave
receive antenna on the bottom of the satellite? I have not heard?updated
news about?that
since the jettison occurred.
Was it the dummy load or was the dummy load taken off and the flight antenna
installed to
deployment while in the ISS?,but later accidentally?broken?off when the
cosmonauts hand
carried?it through the Pirus hatch?
------------------------------
Message: 10
Date: Wed, 17 Aug 2011 21:20:32 -0400
From: Tom Azlin N4ZPT <tom@xxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Re: Decoding wideband recordings
Message-ID: <4E4C68E0.9080704@xxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks Bruce.
I think I need to go get a preamp and filter! And try again.
73, tom n4zpt
On 8/14/2011 12:06 PM, Bruce Robertson wrote:
> On Sat, Aug 13, 2011 at 7:07 PM, Phil Karn<karn@xxxxxxxx.xxx> wrote:
>> On 8/10/11 8:24 PM, Tom Azlin N4ZPT wrote:
>>> I have a Fun Cube Dongle so I would Phil. Thanks and 73, Tom n4zpt
>>
>> Okay, everybody make and keep your wideband I/Q recordings and I'll work
>> on an enhancement to my demodulation/decoding software to process them.
>> It may not run in real time on slower machines because of the need to
>> search a wider frequency range, but this won't matter if it can work on
>> a recording.
>>
>> I can probably speed things up by including an orbit model in the modem
>> to predict Doppler open-loop, but this will take time to implement and
>> it will still be vulnerable to small errors in the elements and/or your
>> clock, especially around closest approach. So record the date and time
>> of your recordings and the current eleset at that time.
>
>
> For those who have not noted this feature, HDSDR will open a recording
> scheduler if you right click on the 'record' button. It saves files
> with UTC time appended. The tricky part is that you have to set the
> scheduler manually in local time.
>
> I've been thinking it would be a nifty hack to make a FCD recorder for
> a set of satellites using a very small computer, like the BeagleBoard.
> It seems to me that a daily cron job with 'Predict' would just about
> do what was necessary, especially now that we have a commandline tool
> for the FCD. The only part that would take some fiddling would be
> piping the USB sound card into a file with the proper headers for
> HDSDR.
>
> 73, Bruce VE9QRP
>
>
------------------------------
Message: 11
Date: Thu, 18 Aug 2011 10:50:52 +0930
From: "Colin Hurst" <cjhurst@xxxxxxx.xxx.xx>
To: "'Alan Cresswell'" <alancresswell@xxxx.xx.xx>, "'Ben Bishop'"
<leorex@xxxxx.xxx>, "'AMSAT'" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: ARISSat-1 telemetry top submitters
Message-ID: <005701cc5d45$121a93c0$364fbb40$@xxx.xx>
Content-Type: text/plain; charset="utf-8"
Alan,
The last KURSK segment I received were 741858 on the 12th August.
My educated guess is that because ARISSAT1 is resetting during every eclipse
the KURSK experiment is not able to obtain the MET and use it as a file name.
Hence it is defaulting to 944.
73
Colin VK5HI
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Alan Cresswell
Sent: Thursday, 18 August 2011 05:49
To: 'Ben Bishop'; 'AMSAT'
Subject: [amsat-bb] Re: ARISSat-1 telemetry top submitters
Hi all,
According to my logs the last Kursk frame I received on the 0405UT pass on
12 August was 720206. The first Kursk frame on the 12 August 2035UT pass
was 944. The interesting thing was that it apparently treated this as a
valid frame. i.e it accumulated and combined all five parts. All Kursk
frames from that point onward have been treated as "exists" and ignored.
2011/08/12-20:36:44 Received Kursk frame 5 with MET=944 len=48. Do we have
<C:\ARISSatTLM\Kursk\KURSK-944.5>?
2011/08/12-20:36:44 No. Saving to <C:\ARISSatTLM\Kursk\KURSK-944.5>.
2011/08/12-20:36:44 Checking for all five parts.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.1>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.2>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.3>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.4>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.5>: OK.
2011/08/12-20:36:44 Combining KURSK parts into
<C:\ARISSatTLM\Kursk\KURSK-944.EXP>.
2011/08/12-20:36:44 Done combining.
2011/08/12-20:36:44 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type E
2011/08/12-20:36:50 Received telemetry frame with MET=1589 Len=371
2011/08/12-20:36:50 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type T
2011/08/12-20:36:58 Received Kursk frame 1 with MET=944 len=516. Do we have
<C:\\ARISSatTLM\Kursk\KURSK-944.1>?
2011/08/12-20:36:58 Yes. <C:\ARISSatTLM\Kursk\KURSK-944.1> exists.
2011/08/12-20:36:58 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type E
73
Alan
ZL2BX
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Ben Bishop
Sent: Wednesday, 17 August 2011 14:36
To: AMSAT
Cc: n0jy@xxxxxxx.xxx
Subject: [amsat-bb] Re:ARISSat-1 ??? telemetry top submitters
G'day Jerry,
I don't think there's anything wrong with your ARISSatTLM, as I've
only been getting KURSK-944s since the 13th.
My last 'proper good' experiment frame was:
2011/08/11-08:12:48 Received Kursk frame 2 with MET=650105 len=516.
Satellite MET around then was:
2011/08/11-08:12:54 Received telemetry frame with MET=653412 Len=371
I missed the 12th, and on the 13th the telemetry and experiment MET had reset:
2011/08/13-04:34:16 Received telemetry frame with MET=2514 Len=371
....
2011/08/13-04:34:24 Received Kursk frame 3 with MET=944 len=516. Do we
have <C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.3>?
2011/08/13-04:34:24 No. Saving to
<C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.3>.
And from that point on, I have only received KURSK-944 frames (which
are still auto-forwarding).
2011/08/17-05:30:04 Received Kursk frame 5 with MET=944 len=48. Do we
have <C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.5>?
2011/08/17-05:30:04 Yes.
<C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.5> exists.
73,
Ben VK2FBRB
On Wed, Aug 17, 2011 at 11:08 PM, <n0jy@xxxxxxx.xxx> wrote:
> A question for all, for a few days now my ARISSatTLM has been reporting
> the Kursk as being (I believe, I'm not at home to check right now)
> something like Kursk-944.x or perhaps it was Kursk-444.x (some real low
> perhaps hung up on that and needs a restart? Anyone else, what are the
> latest Kursk frames that you are seeing?
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3840 - Release Date: 08/17/11
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 12
Date: Wed, 17 Aug 2011 18:32:43 -0700
From: Phil Karn <karn@xxxxxxxx.xxx>
To: "Mark L. Hammond" <marklhammond@xxxxx.xxx>
Cc: Amsat - BBs <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: Turn off AGC when receiving BPSK-1000
Message-ID: <4E4C6BBB.9070803@xxxxxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
On 8/17/11 1:36 PM, Mark L. Hammond wrote:
> In any event, Phil...THANK YOU for making this code real. I have
> seen it print data when the signal was visibly "in the dirt" which is
> impressive and fun to see.
You're most welcome. It was a lot of work mainly because there were so
many options in the design that were hard to nail down. Nobody really
knew how fast the fading would be, or how long the data frames should or
would be, or how fast the telemetry values would change, or the
frequency and phase response of all the SSB receivers people would use
to receive the telemetry, or the accuracy of the A/D clocks in their
computers, or the type and speed of their CPUs, or the experience level
of the operators and whether they'd used automatic or manual tuning.
I did know that there would be fading, probably very deep. I knew the
orbit would be that of the ISS so I knew the passes would be short with
fierce Doppler. I knew that the beacon would operate in a broadcast mode
so latency wasn't a major concern.
So I went for a conservative, robust design. I didn't try to maximize
the data rate or minimize latency as I might have on a Pacsat being used
for interactive and store-and-forward user communications. Those things
might have made the signal much less robust especially by impairing its
fade resistance.
I think my emphasis on fade resistance has definitely paid off, but I'm
less happy with its tolerance (or lack thereof) of various frequency
errors, from Doppler correction to off-frequency A/D clocks in computer
sound interfaces. But that's one of the reason we fly these things, to
get that kind of experience for the next time.
Another thing this mission (and many previous amateur satellites) shows
is that the one thing we really, really need on our small satellites is
a good attitude determination and control system. One would make *so*
many problems just go away:
We could mount microwave antennas on a nadir-facing surface and provide
consistent, predictable, strong, wideband signals to ground stations
during a pass.
We could mount our solar panels on rotating booms to track the sun and
generate far more power from a given number of (very expensive) cells
than we now get by hedging our bets and covering every outside surface.
We could predict and control spacecraft heat flows and temperatures far
more easily.
We'd know where our cameras are pointing and we could take pictures of
predetermined targets.
The problem consists of two parts: attitude determination and attitude
control. For determination I keep thinking that we should be able to do
a lot with small, light and inexpensive CCD cameras. With proper light
baffling it should be possible to see stars even in the daytime, and
onboard software with a star chart could figure out which they are.
For attitude control, I think control moment gyros are the way to go.
(They're somewhat different from momentum wheels in that they operate at
constant speed.) This is largely a mechanical problem: designing
flywheels and motors that are small, lightweight, can store a lot of
angular momentum, draw minimal power, and be precisely moved around to
control the direction and magnitude of the overall spacecraft angular
momentum vector. We'd still need magnetorquing coils to dump excess
momentum, but the cm gyros would provide quick and accurate control of
spacecraft attitude.
-Phil
------------------------------
Message: 13
Date: Thu, 18 Aug 2011 01:45:54 -0000
From: "Alan Cresswell" <alancresswell@xxxx.xx.xx>
To: "'Colin Hurst'" <cjhurst@xxxxxxx.xxx.xx>, "'Ben Bishop'"
<leorex@xxxxx.xxx>, "'AMSAT'" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Re: ARISSat-1 telemetry top submitters
Message-ID: <0A07C8E681E44C779492034A93F3D893@xxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hi Colin,
Yes, the other interesting thing is that recently ARISsat has been coming
out of eclipse not too long before the start of my morning passes. On those
occasions I have received anything up to 19 consecutive data frames (or
about 3 minutes) before I receive the first Kursk frame.
73
Alan
ZL2BX
-----Original Message-----
From: Colin Hurst [mailto:cjhurst@xxxxxxx.xxx.xxx
Sent: Thursday, 18 August 2011 01:21
To: 'Alan Cresswell'; 'Ben Bishop'; 'AMSAT'
Subject: RE: [amsat-bb] Re: ARISSat-1 telemetry top submitters
Alan,
The last KURSK segment I received were 741858 on the 12th August.
My educated guess is that because ARISSAT1 is resetting during every eclipse
the KURSK experiment is not able to obtain the MET and use it as a file name.
Hence it is defaulting to 944.
73
Colin VK5HI
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Alan Cresswell
Sent: Thursday, 18 August 2011 05:49
To: 'Ben Bishop'; 'AMSAT'
Subject: [amsat-bb] Re: ARISSat-1 telemetry top submitters
Hi all,
According to my logs the last Kursk frame I received on the 0405UT pass on
12 August was 720206. The first Kursk frame on the 12 August 2035UT pass
was 944. The interesting thing was that it apparently treated this as a
valid frame. i.e it accumulated and combined all five parts. All Kursk
frames from that point onward have been treated as "exists" and ignored.
2011/08/12-20:36:44 Received Kursk frame 5 with MET=944 len=48. Do we have
<C:\ARISSatTLM\Kursk\KURSK-944.5>?
2011/08/12-20:36:44 No. Saving to <C:\ARISSatTLM\Kursk\KURSK-944.5>.
2011/08/12-20:36:44 Checking for all five parts.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.1>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.2>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.3>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.4>: OK.
2011/08/12-20:36:44 <C:\ARISSatTLM\Kursk\KURSK-944.5>: OK.
2011/08/12-20:36:44 Combining KURSK parts into
<C:\ARISSatTLM\Kursk\KURSK-944.EXP>.
2011/08/12-20:36:44 Done combining.
2011/08/12-20:36:44 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type E
2011/08/12-20:36:50 Received telemetry frame with MET=1589 Len=371
2011/08/12-20:36:50 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type T
2011/08/12-20:36:58 Received Kursk frame 1 with MET=944 len=516. Do we have
<C:\\ARISSatTLM\Kursk\KURSK-944.1>?
2011/08/12-20:36:58 Yes. <C:\ARISSatTLM\Kursk\KURSK-944.1> exists.
2011/08/12-20:36:58 Forwarding from ZL2BX to telemetry.arissattlm.org frame
type E
73
Alan
ZL2BX
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Ben Bishop
Sent: Wednesday, 17 August 2011 14:36
To: AMSAT
Cc: n0jy@xxxxxxx.xxx
Subject: [amsat-bb] Re:ARISSat-1 ??? telemetry top submitters
G'day Jerry,
I don't think there's anything wrong with your ARISSatTLM, as I've
only been getting KURSK-944s since the 13th.
My last 'proper good' experiment frame was:
2011/08/11-08:12:48 Received Kursk frame 2 with MET=650105 len=516.
Satellite MET around then was:
2011/08/11-08:12:54 Received telemetry frame with MET=653412 Len=371
I missed the 12th, and on the 13th the telemetry and experiment MET had reset:
2011/08/13-04:34:16 Received telemetry frame with MET=2514 Len=371
.....
2011/08/13-04:34:24 Received Kursk frame 3 with MET=944 len=516. Do we
have <C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.3>?
2011/08/13-04:34:24 No. Saving to
<C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.3>.
And from that point on, I have only received KURSK-944 frames (which
are still auto-forwarding).
2011/08/17-05:30:04 Received Kursk frame 5 with MET=944 len=48. Do we
have <C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.5>?
2011/08/17-05:30:04 Yes.
<C:\Users\Ben\Desktop\ARISSatTLM\Kursk\KURSK-944.5> exists.
73,
Ben VK2FBRB
On Wed, Aug 17, 2011 at 11:08 PM, <n0jy@xxxxxxx.xxx> wrote:
> A question for all, for a few days now my ARISSatTLM has been reporting
> the Kursk as being (I believe, I'm not at home to check right now)
> something like Kursk-944.x or perhaps it was Kursk-444.x (some real low
> perhaps hung up on that and needs a restart? Anyone else, what are the
> latest Kursk frames that you are seeing?
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3840 - Release Date: 08/17/11
_______________________________________________
Sent via AMSAT-BB@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3841 - Release Date: 08/17/11
------------------------------
_______________________________________________
Sent via amsat-bb@xxxxx.xxx. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
http://amsat.org/mailman/listinfo/amsat-bb
End of AMSAT-BB Digest, Vol 6, Issue 472
****************************************
Read previous mail | Read next mail
| |
