| |
CX2SA > SATDIG 11.05.10 20:08l 450 Lines 13412 Bytes #999 (0) @ WW
BID : AMSATBB5216
Read: GUEST
Subj: AMSAT-BB-digest V5 216
Path: IZ3LSV<IK2XDE<DB0RES<ON0AR<HS1LMV<CX2SA
Sent: 100511/1905Z @:CX2SA.LAV.URY.SA #:59056 [Minas] FBB7.00e $:AMSATBB5216
From: CX2SA@CX2SA.LAV.URY.SA
To : SATDIG@WW
Today's Topics:
1. Re: K5GNA Parts (Alan)
2. ISS digipeater path? (Gordon JC Pearce)
3. Re: ISS digipeater path? (Kai Gunter Brandt)
4. Re: ISS digipeater path? (Gordon JC Pearce)
5. Re: PC clock (Greg D.)
6. Packet on AO-27 (Tom)
7. Re: Packet on AO-27 (Mike Rupprecht)
8. Re: AO-51 S schedule loaded (Clare Fowler)
9. SSTV From ISS on May 13-14 (JoAnne Maenpaa)
10. Re: PC clock (Larry Gerhardstein)
----------------------------------------------------------------------
Message: 1
Date: Mon, 10 May 2010 14:04:52 -0500
From: "Alan" <ve4yz@xxxxxxx.xxx>
Subject: [amsat-bb] Re: K5GNA Parts
To: "'George Henry'" <ka3hsw@xxx.xxx>, "'Angelo Glorioso'"
<n5uxt@xxxxxxx.xxx>, "'AMSATBBS'" <amsat-bb@xxxxx.xxx>
Message-ID: <BAY110-DS155EB3DF277070E100E87FEBF90@xxx.xxx>
Content-Type: text/plain; charset="iso-8859-1"
George, if you don't have one I have a couple left over from converting 3 of
mine to helical and I'll mail one to Angelo.
-----Original Message-----
From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of George Henry
Sent: Monday, May 10, 2010 1:22 PM
To: Angelo Glorioso; AMSATBBS
Subject: [amsat-bb] Re: K5GNA Parts
I might have one left over from some conversions I did a few years back...?
I'll check when I get home tonight.
George, KA3HSW
----- Original Message ----
> From: Angelo Glorioso <n5uxt@xxxxxxx.xxx>
> To: AMSATBBS <amsat-bb@xxxxx.xxx>
> Sent: Mon, May 10, 2010 8:44:50 AM
> Subject: [amsat-bb] K5GNA Parts
>
> Hi All,
If anyone has a bad/junk K5GNA, I am looking for the dipole (
> white piece in a cross configuration). A fellow ham has K5GNA with a
> diople that is broken.
Angelo
>
_______________________________________________
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: 2
Date: Mon, 10 May 2010 20:20:56 +0100
From: Gordon JC Pearce <gordonjcp@xxxx.xxx>
Subject: [amsat-bb] ISS digipeater path?
To: Amsat-bb <amsat-bb@xxxxx.xxx>
Message-ID: <1273519256.25318.46.camel@xxxxx.xxxx>
Content-Type: text/plain; charset="UTF-8"
Hi there,
I've finally got to a point where I have a working 2m rig in the
house, with a working sound interface and working soundmodem *and* the
ISS has packet turned on.
I've been able to wake up the BBS on RS0ISS-14, so the radio on the ISS
can hear me and talk to me. I'm not seeing any APRS packets being
digipeated, though.
Currently I have Xastir set up with the unproto path set to
ARISS,SGATE,WIDE2-2 which is derived by consensus from several (possibly
out-of-date) websites. Is this right? If it isn't, what should it be?
Gordon MM0YEQ
------------------------------
Message: 3
Date: Mon, 10 May 2010 22:25:37 +0200
From: Kai Gunter Brandt <kai.brandt@xxx.xxx.xx>
Subject: [amsat-bb] Re: ISS digipeater path?
To: Gordon JC Pearce <gordonjcp@xxxx.xxx>
Cc: Amsat-bb <amsat-bb@xxxxx.xxx>
Message-ID: <4BE86BC1.6060401@xxx.xxx.xx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 05/10/2010 09:20 PM, Gordon JC Pearce wrote:
>
> Currently I have Xastir set up with the unproto path set to
> ARISS,SGATE,WIDE2-2 which is derived by consensus from several (possibly
> out-of-date) websites. Is this right? If it isn't, what should it be?
>
> Gordon MM0YEQ
>
This path is correct. You probably don't need anything more than
ARISS,SGATE but i don't think the extra characters is occupying much
"airtime"
Kai Gunter
LA3QMA
------------------------------
Message: 4
Date: Mon, 10 May 2010 21:35:18 +0100
From: Gordon JC Pearce <gordonjcp@xxxx.xxx>
Subject: [amsat-bb] Re: ISS digipeater path?
To: Amsat-bb <amsat-bb@xxxxx.xxx>
Message-ID: <1273523718.25318.52.camel@xxxxx.xxxx>
Content-Type: text/plain; charset="UTF-8"
On Mon, 2010-05-10 at 22:25 +0200, Kai Gunter Brandt wrote:
> On 05/10/2010 09:20 PM, Gordon JC Pearce wrote:
> >
> > Currently I have Xastir set up with the unproto path set to
> > ARISS,SGATE,WIDE2-2 which is derived by consensus from several (possibly
> > out-of-date) websites. Is this right? If it isn't, what should it be?
> >
> > Gordon MM0YEQ
> >
> This path is correct. You probably don't need anything more than
> ARISS,SGATE but i don't think the extra characters is occupying much
> "airtime"
>
> Kai Gunter
> LA3QMA
>
Thanks to all for the advice. It looks like packet has been turned off
again, so I'll keep a note of the thread to remind me when I try again
in a couple of months ;-)
Gordon MM0YEQ
------------------------------
Message: 5
Date: Mon, 10 May 2010 22:47:23 -0700
From: "Greg D." <ko6th_greg@xxxxxxx.xxx>
Subject: [amsat-bb] Re: PC clock
To: <w7in@xxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Message-ID: <BLU133-W13E28D9B84C40DAB74B50EA9FA0@xxx.xxx>
Content-Type: text/plain; charset="iso-8859-1"
Hi Larry,
Ok, I understand the need for an accurate clock, though I believe you're
expectations for being able to track an overhead pass is pushing the limits
of orbital prediction pretty hard. Another ham I know locally tried this,
and ultimately gave up. His issue was not one of clock accuracy, but of
Keps and the mathematics behind them.
But, you've still got a PC that isn't working right, and that bugs me. I
just checked my PC, and it was spot on with WWV (clock changed at the
chime). So, a question... Did the clock drift before the serial port was
installed? Perhaps what you need is a new driver or a different type of
serial port, if you haven't exhausted that route already.
Greg KO6TH
Date: Sun, 9 May 2010 21:23:58 -0600
From: W7IN@xxxxxxx.xxx
To: ko6th_greg@xxxxxxx.xxx
CC: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Re: PC clock
Greg,
During the process of getting a serial port interface that worked
properly with W7-64b, I experienced a myriad of system crashes. This
is possibly why my clock got off by about +30 seconds. I often check
my PC's clock against the WWV clock on my wall, especially when
tracking birds. It's now on to within a second. If it got off by more
than 2 or 3, I'd want to corrected it; the problem is not Doppler, it's
a near overhead pass (that's when I discovered the PC time error).
Plus, I want correction automatic and not have to mess with it for a
long time. I believe the once-a-week default in Win7 for syncing PC
time with Internet server time is too loose. Once a day or even once
an hour seems better to me.
73, Larry W7IN
On 5/9/2010 7:05 PM, Greg D. wrote:
Hi
Larry,
I know PC clocks are not all that accurate, but we're talking seconds
per month. Needing to update a clock more often than that probably
isn't due to the PC hardware. I've never had one be off this much
unless the clock battery was dead, and any PC new enough to run Win-7
isn't going to have that issue. I would suspect that there is a some
software you are running that is messing it up. Back in the DOS days,
this was a common occurrence, and I'm surprised to hear about it under
something more modern, but my gut feel tells me that is what is
happening.
Maybe a device driver or something else low-level. Try booting
something else (a "Live" CD of Linux, for example) to prove the
hardware is good. Go back to Windows piece by piece. If you can
figure out which it is, then this whole idea of applying bandaids can
go away.
Just a thought,
Greg KO6TH
<snip>
_________________________________________________________________
The New Busy is not the too busy. Combine all your e-mail accounts with
Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326
::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
------------------------------
Message: 6
Date: Mon, 10 May 2010 14:18:09 -0700
From: "Tom" <k0tw@xxx.xxx>
Subject: [amsat-bb] Packet on AO-27
To: <amsat-bb@xxxxx.xxx>
Message-ID: <A792E9ACEAD84D05A51E5FE78A410A37@xxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
At the end of the AO-27 pass at about 2023 UTC today I heard a strong packet
signal on the downlink. It lasted for about 30 seconds and wiped out the end
of the pass for me. I think I've heard that before but can't remember if it
was on AO-27. Is this just someone creating QRM or is the packet signal
there for a reason?
Tom - K?TW
------------------------------
Message: 7
Date: Tue, 11 May 2010 08:41:50 +0200
From: "Mike Rupprecht" <mail@xxxxxxxxxxxxxx.xx>
Subject: [amsat-bb] Re: Packet on AO-27
To: <k0tw@xxx.xxx>, <amsat-bb@xxxxx.xxx>
Message-ID: <000b01caf0d5$09019780$1b04c680$@xx>
Content-Type: text/plain; charset="iso-8859-1"
Hi Tom,
AO-27 is sending 1k2 AFSK telemetry (raw, no UI-frames). You need a TNC in
KISS mode to get the data.
See here: http://www.ao27.org/AO27/tlm.shtml
73, Mike
DK3WN
-----Urspr?ngliche Nachricht-----
Von: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx Im
Auftrag von Tom
Gesendet: Montag, 10. Mai 2010 23:18
An: amsat-bb@xxxxx.xxx
Betreff: [amsat-bb] Packet on AO-27
At the end of the AO-27 pass at about 2023 UTC today I heard a strong packet
signal on the downlink. It lasted for about 30 seconds and wiped out the end
of the pass for me. I think I've heard that before but can't remember if it
was on AO-27. Is this just someone creating QRM or is the packet signal
there for a reason?
Tom - K?TW
_______________________________________________
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: 8
Date: Tue, 11 May 2010 06:55:26 -0400
From: "Clare Fowler" <clarefowler@xxxxxx.xxx>
Subject: [amsat-bb] Re: AO-51 S schedule loaded
To: "Andrew Glasbrenner" <glasbrenner@xxxxxxxxxx.xxx>, "Amsat-BB"
<amsat-bb@xxxxx.xxx>
Message-ID: <C88421BE49B64976A45902F8D8FA65E5@xxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Mode V/S working well on orbit 30820 on 10:20 UTC pass.
Full quieting for whole pass with only one small fade..
Only KB2M and myself on.
Clare VE3NPC
----- Original Message -----
From: "Andrew Glasbrenner" <glasbrenner@xxxxxxxxxx.xxx>
To: "Amsat-BB" <amsat-bb@xxxxx.xxx>
Sent: Monday, May 10, 2010 5:35 AM
Subject: [amsat-bb] AO-51 S schedule loaded
> At 0930Z I loaded a schedule that should turn V/S on just after emerging
> from each eclipse, beginning at 1010Z today through 0930Z tomorrow.
> Reception reports would be appreciated.
>
> 73, Drew KO4MA
------------------------------
Message: 9
Date: Tue, 11 May 2010 08:13:59 -0500
From: "JoAnne Maenpaa" <k9jkm@xxxxxxx.xxx>
Subject: [amsat-bb] SSTV From ISS on May 13-14
To: <amsat-bb@xxxxx.xxx>
Message-ID: <000601caf10b$d21e5d20$765b1760$@xxx>
Content-Type: text/plain; charset="us-ascii"
Hello everyone,
This news was in the Amateur Radio on the International Space Station
(ARISS) Status Report for May 10, 2010. If we wait for the weekend AMSAT
News Service cycle this opportunity will have passed.
MAI-75 Experiments Planned
MAI-75 (Moscow Aviation Institute) experiments are planned for May 13 from
10:00 - 17:00 UTC and May 14 from 12:45 - 16:00 UTC. The VC-H1 in Robot-36
mode will be used to transmit Slow Scan Television images on May 13 and the
computer will be used on May 14.
--
73 de JoAnne K9JKM
k9jkm@xxxxx.xxx
Editor, AMSAT News Service
Copy Editor, AMSAT Journal
------------------------------
Message: 10
Date: Tue, 11 May 2010 07:26:45 -0600
From: Larry Gerhardstein <gerhardstein@xxxxxxx.xxx>
Subject: [amsat-bb] Re: PC clock
To: "Greg D." <ko6th_greg@xxxxxxx.xxx>
Cc: amsat-bb@xxxxx.xxx
Message-ID: <4BE95B15.40601@xxxxxxx.xxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I've done several checks against WWV and the PC's clock is now spot on.
Yes, I was having driver problems. I explained that. But I'm no longer
attempting to use those and have what I believe is a stable driver for
my PCI serial ports I just acquired. I'll continue checks against WWV,
but as long as it check ok, I'm not going to fix what is now working ok.
Larry W7IN
On 5/10/2010 11:47 PM, Greg D. wrote:
> Hi Larry,
>
> Ok, I understand the need for an accurate clock, though I believe you're
expectations for being able to track an overhead pass is pushing the limits
of orbital prediction pretty hard. Another ham I know locally tried this,
and ultimately gave up. His issue was not one of clock accuracy, but of
Keps and the mathematics behind them.
>
> But, you've still got a PC that isn't working right, and that bugs me. I
just checked my PC, and it was spot on with WWV (clock changed at the
chime). So, a question... Did the clock drift before the serial port was
installed? Perhaps what you need is a new driver or a different type of
serial port, if you haven't exhausted that route already.
>
> Greg KO6TH
>
>
> <snip>
>
>
------------------------------
_______________________________________________
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 5, Issue 216
****************************************
Read previous mail | Read next mail
| |
