| |
CX2SA > SATDIG 23.05.15 17:00l 850 Lines 25912 Bytes #999 (0) @ WW
BID : AMSATBB10144
Read: GUEST
Subj: AMSAT-BB-digest V10 144
Path: IW8PGT<IZ3LSV<IW0QNL<JH4XSY<JE7YGF<7M3TJZ<CX2SA
Sent: 150523/1453Z @:CX2SA.SAL.URY.SOAM #:21277 [Salto] FBB7.00e $:AMSATBB10144
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. More PSAT frames (Timo)
2. Help with IC910 & SatPC32 PC/COM-Port (Bob KD7YZ)
3. PSAT Elements are 6 minutes early (Robert Bruninga)
4. Re: Help with IC910 & SatPC32 PC/COM-Port (Bob KD7YZ)
5. USNA Sat Status (day 3) (Robert Bruninga)
6. AO73 mode change (Jim Heck)
7. PSAT PSK31 Telemetry over Washington, DC 2130Z (Paul Stoetzer)
8. PSAT PSK31 transponder (David W0DHB)
9. Re: USNA Sat Status (day 3) (Andrew Glasbrenner)
10. Keplerians & Frequencies new satellites. (Vincenzo Mone)
11. Re: USNA Sat Status (day 3) (M5AKA)
12. PSAT (David L Warnberg)
13. Re: PSAT Elements are 6 minutes early (Nico Janssen)
14. UT1FG/MM update (John Papay)
15. KX9X/2 FN22 today 1704z (Sean Kutzko)
16. Re: PSAT Elements are 6 minutes early (Robert Bruninga)
----------------------------------------------------------------------
Message: 1
Date: Fri, 22 May 2015 18:06:04 +0200
From: Timo <timodoei@xxxxx.xxx>
To: AMSAT <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] More PSAT frames
Message-ID: <555F53EC.5050907@xxxxx.xxx>
Content-Type: text/plain; charset=utf-8; format=flowed
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=52 >[10:06:39]
s#001617,0z200,FbGDAG0BHBaHEbHCAH0AHBaHDbGCBH0AHCbH
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[10:07:09]
T#376,795,352,494,836,863,00011100
Fm PSAT-1 To APOFF Via ARISS <UI pid=F0 Len=34 >[11:45:36]
T#473,807,354,509,867,888,00011100
Timo, PE1NTN
------------------------------
Message: 2
Date: Fri, 22 May 2015 13:49:59 -0400
From: Bob KD7YZ <kd7yz@xxxxxxxxxxx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Help with IC910 & SatPC32 PC/COM-Port
Message-ID: <555F6C47.2010007@xxxxxxxxxxx.xx>
Content-Type: text/plain; charset=utf-8
Though I show COM#11 at 19200 8n2, and it's a
"Prolific USB-to-Serial Comm Port" ... SatPC32 never sees it.
For that matter, and as a test, DXLabs Commander" complains
"Invalid Porty number (8002) thePort=primary CAT port, port number=11 ...
But DevMgr shows it plain as day.
I've re-booted a couple times to see if that helped.
O/S is Win7/64bit
So anyone with an idea for me to try, please write.
List or Direct, egal
73,
--
Bob KD7YZ
http://www.qrz.com/db/kd7yz
AMSAT LM#901
------------------------------
Message: 3
Date: Fri, 22 May 2015 14:21:37 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] PSAT Elements are 6 minutes early
Message-ID: <c08e02165ef6325881588911c4ba30e0@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
I am finding that PSAT is 6 MINUTES behind the predictions of the previously
provided original Launch TLE :
ULTRASat3
1 99993U 15140.67013889 .00040043 00000-0 10235-2 0 00009
2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
So until I get new ones. Just point at AOS and wait 6 miuntes.
Also, I had said not to TX PSK31 on the 10m u plink until you heard the
downlink. Well, that was dumb advise, because the transponder does not come
up unless it hears PSK31!
So the new rule is, Listen first. If not heard, TX anyway. If not heard
then, Fix your problem, and try again?
We don?t know how the power budget will work out. So all we can do is
watch.
Bob, WB4APR
------------------------------
Message: 4
Date: Fri, 22 May 2015 14:32:06 -0400
From: Bob KD7YZ <kd7yz@xxxxxxxxxxx.xx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] Help with IC910 & SatPC32 PC/COM-Port
Message-ID: <555F7626.5060304@xxxxxxxxxxx.xx>
Content-Type: text/plain; charset=windows-1252
however, I also ran a bus-reset program I found ... this deletes added
Virtual Ports, hidden or not. After a sys reboot, suddenly my DxLabs
Commander as-well-as my SatPc32, read the IC91`0.
Go figure
now that my Az/El stuff is working, what are the current usable Sats for
comms, voice/CW/Data that we are using?
73,
--
Bob KD7YZ
http://www.qrz.com/db/kd7yz
AMSAT LM#901
------------------------------
Message: 5
Date: Fri, 22 May 2015 14:54:01 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] USNA Sat Status (day 3)
Message-ID: <2b66716d2036cb360cd884657ec4863a@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
PSAT Summary - Day 3
* PSAT packet telemetry is OK, Digipeater will be off (secondary mission)
* PSAT PSK31 transponder is ON with 28.120 MHz uplink! (primary mission)
* WOD data fixed. Spin data now available. Right now it is at 3 RPM with
+Z pointing at Sun
* Launch TLE elements (below) are 6 minutes ahead of satellite
* PCSAT.APRS.ORG web page is now also capturing PSAT telelmetry downlinks
* BRICSAT telemetry has been heard but is cycling OFF due to low power
* BRICSAT PSK31 downlink (also FM) has also been heard barely (when ON)
* USS Langley not heard
Only fault so far is the loss of the 4 day-fail-safe backup reset circuit
(1 of 3) fail safe backup RESET capabilities. The lack of WOD data was
because we had a LOW-POWER bits set that was holding it off.
BRICSAT PSK31 transponder is on identical frequencies as PSAT's. You can
tell them apart because one has PSK Telemetry on 315 Hz and the other is
on 365 Hz. Both on the UHF FM downlink 435.350 MHz
SUMMARY:
PSAT: 145.825 - 1200 baud AX.25 telemetry - digi off
PSAT PSK31#1: 435.350 FM down, 28.120 SSB PK31 uplink - Brno University
Xponder
BRICsat: 437.975 - 9600 baud telemetry downlink every 20s
BRICsat PSK31#2 - same as PSAT but PSK TLM on 375 Hz (PSAT on 315 Hz)
USS Langley - 437.975 9600 baud telemetry
ULTRASat3 <these now predicting 6 minutes ahead of actual satellite>
1 99993U 15140.67013889 .00040043 00000-0 10235-2 0 00009
2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
Bob, WB4APR
------------------------------
Message: 6
Date: Fri, 22 May 2015 22:20:54 +0100
From: Jim Heck <jimlist@xxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] AO73 mode change
Message-ID: <555F9DB6.6020704@xxxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi All,
Just to advise that FUNcube-1 AO73 has just (at approx 2120 UTC) been
commanded into continuous amateur mode. We expect to change it back to
autonomous mode on Sunday pm.
Have FUN!
73
Jim G3WGM
------------------------------
Message: 7
Date: Fri, 22 May 2015 17:49:04 -0400
From: Paul Stoetzer <n8hm@xxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>, Robert Bruninga
<bruninga@xxxx.xxx>
Subject: [amsat-bb] PSAT PSK31 Telemetry over Washington, DC 2130Z
Message-ID:
<CABzOSOoDZ-44cEG_5hahO_tagnu36y=9WLaAbN914qA7Y64ZBQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Good evening,
Nice strong signals from PSAT over southwest Washington, DC (FM18lv)
around 2130Z. I decoded several frames of telemetry from the beacon
and saw a couple of PSK31 signals in the passband, but from what I
could decode, they appear to have been terrestrial QSOs in progress.
I did not see the BRICSAT beacon at all.
I was not setup to transmit on this pass. Maybe tomorrow.
Thanks to the U. S. Naval Academy, WB4APR, and Brno University for
something different to try out. Hopefully I'll be able to make a QSO
soon!
The decoded telemetry is below. Receive setup was a Yaesu FT-817,
Arrow II, and HSM LNAA432 preamp. I had the levels screwed up when
live, so this is decoded off my recording with fldigi.
W3ADO-5 beacon B 008 90 27 780 250 +18 t5o
W3ADO-5 beacon B 009 99 29 7i 5 248 +18 a=
W3ADO-5 beacon B 010 99 32 775 248 +19 ea a
W3ADO-5 beacon B 011 28 23 775 249 +19 g ,l
W3ADO-5 beacon B 012 09 23 777 248 +19 =ce
W3ADO-5 beacon B 013 62 23 775 248 +20 eeetY
W3ADO-5 beacon B 014 53 23 771 249 +20 ve
W3ADO-5 beacon B 015 03 2e=777 248 +20 deaoo
W3ADO-5 beacon B 016 40 23 773 248 +20 e
rO
W3ADO-5 beacon B 017 56 23 773 247 +21
t
W3ADO-5 beacon B 018 56 23 772 248 +21 l tnm eo ie? mo
W3ADO-5 beacon B 019 34 26 783 248 +19 Qc
W3ADO-5 beacon B 020 06 23 773 248 +20 setT
W3ADO-5 be Lt t,t
oite.eo n)d enttpg>ty-o1oatte c leem <RS>o
C ,a abli
W3ADO-5 beacon A 000 03 23 793 8 +16 i
W3ADO-5 beacon A 001 09 23 771 248 +18 Si
W3ADO-5 beacon A 002 28 23 772 247 +20 o de
W3ADO-5 beacon A 003 09 23 769 248 +20 tamn
W3ADO-F beacon A 004 03 23 770 248 +20 Se l
W3ADO-5 beacon A 005 00 23 769 246 +20 e tt
W3ADO-5 beacon T 0.6 00 23 765 247 +21
W3ADHr5 beacon A 007 03 23 769 24ei +w
73,
Paul Stoetzer, N8HM
Washington, DC (FM18lv)
------------------------------
Message: 8
Date: Fri, 22 May 2015 16:35:37 -0600
From: "David W0DHB" <dave@xxxxx.xxx>
To: "'operator'" <psktransponder@xxxxxxx.xx>, <amsat-bb@xxxxx.xxx>
Cc: 'Peter Martinez' <peter.martinez@xxxxxxxxxx.xxx>
Subject: [amsat-bb] PSAT PSK31 transponder
Message-ID: <001301d094df$a00563b0$e0102b10$@xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"
This last pass of PSAT I was able to successfully decode myself and others
(KI4ENY, K0RJV) using DM780 and MixW.
Couple of observations:
1) MixW is the only PSK31 program I could find which can do full
duplex, 2 running copies of DM780 and fldigi work also.
2) Using SATPC32 Doppler Shifting Uplnk and Downlink, set to 10 Hz
interval with "times 10" selected kept the downlink signals fairly stable
frequency wise.
3) Probably due to TLE's, Uplink signal downlinks about 400 Hz High.
A recording of the pass can be found here:
https://www.dropbox.com/s/825x9wxwteh2273/FM%20435.358633MHz%20%5B12k%5D%205
-22-2015%2021%2020%2004.wav?dl=0
55 MB
Dave W0DHB
------------------------------
Message: 9
Date: Sat, 23 May 2015 08:46:08 -0400
From: "Andrew Glasbrenner" <glasbrenner@xxxxxxxxxx.xxx>
To: "'Robert Bruninga'" <bruninga@xxxx.xxx>, "'AMSAT BB'"
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] USNA Sat Status (day 3)
Message-ID: <000c01d09556$70c06f10$52414d30$@xxx>
Content-Type: text/plain; charset="us-ascii"
Congratulations Bob! It looks like another set of successful USNA
satellites.
I noticed Space Track isn't publishing keps for these as of yet. I know this
has happened with previous DOD launches that had secondary payloads. Do you
know if they will eventually provide them to the owners of the satellites
(like previous launches) for them to distribute? I'd like to be able to
track these automatically, and the current 6 minute difference is a bit much
error for an AO-13 class system.
73, Drew KO4MA
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Robert
Bruninga
Sent: Friday, May 22, 2015 2:54 PM
To: AMSAT BB
Subject: [amsat-bb] USNA Sat Status (day 3)
PSAT Summary - Day 3
* PSAT packet telemetry is OK, Digipeater will be off (secondary mission)
* PSAT PSK31 transponder is ON with 28.120 MHz uplink! (primary mission)
* WOD data fixed. Spin data now available. Right now it is at 3 RPM with
+Z pointing at Sun
* Launch TLE elements (below) are 6 minutes ahead of satellite
* PCSAT.APRS.ORG web page is now also capturing PSAT telelmetry downlinks
* BRICSAT telemetry has been heard but is cycling OFF due to low power
* BRICSAT PSK31 downlink (also FM) has also been heard barely (when ON)
* USS Langley not heard
Only fault so far is the loss of the 4 day-fail-safe backup reset circuit
(1 of 3) fail safe backup RESET capabilities. The lack of WOD data was
because we had a LOW-POWER bits set that was holding it off.
BRICSAT PSK31 transponder is on identical frequencies as PSAT's. You can
tell them apart because one has PSK Telemetry on 315 Hz and the other is on
365 Hz. Both on the UHF FM downlink 435.350 MHz
SUMMARY:
PSAT: 145.825 - 1200 baud AX.25 telemetry - digi off
PSAT PSK31#1: 435.350 FM down, 28.120 SSB PK31 uplink - Brno University
Xponder
BRICsat: 437.975 - 9600 baud telemetry downlink every 20s BRICsat PSK31#2 -
same as PSAT but PSK TLM on 375 Hz (PSAT on 315 Hz)
USS Langley - 437.975 9600 baud telemetry
ULTRASat3 <these now predicting 6 minutes ahead of actual satellite>
1 99993U 15140.67013889 .00040043 00000-0 10235-2 0 00009
2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
Bob, WB4APR
_______________________________________________
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: 10
Date: Sat, 23 May 2015 14:49:38 +0200
From: "Vincenzo Mone" <vimone@xxxxx.xx>
To: "Amsat - BBs" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Keplerians & Frequencies new satellites.
Message-ID:
<!&!AAAAAAAAAAAYAAAAAAAAALgqrd2N1rRAiaQvRd7pgRDCgAAAEAAAAJPyg6wM4ctJtd+0TLg40n
8BAAAAAA==@xxxxx.xx>
Content-Type: text/plain; charset="us-ascii"
Please i am looking for the Keplerians and the Frequencies for the
following satellites:
LightSail-A
PSAT
BRICsat
USS
Any help?
Thanks
Enzo.
73's de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520
**********************************
******* GSM +39 328 7110193 *******
****** SMS +39 328 7110193 ******
*** 2nd e-mail: vimone@xxx.xx ***
*********************************
------------------------------
Message: 11
Date: Sat, 23 May 2015 13:19:10 +0000 (UTC)
From: M5AKA <m5aka@xxxxx.xx.xx>
To: Andrew Glasbrenner <glasbrenner@xxxxxxxxxx.xxx>, AMSAT BB
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] USNA Sat Status (day 3)
Message-ID:
<1319131430.1361936.1432387150481.JavaMail.yahoo@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Yesterday @xxxxxxxxxxx (LightSail) tweeted:
We may not get a new TLE until Monday, and apparently these aren't posted
publicly - though I keep a TLE link at
http://sail.planetary.org/missioncontrol
73 Trevor M5AKA
On Saturday, 23 May 2015, 13:46, Andrew Glasbrenner
<glasbrenner@xxxxxxxxxx.xxx> wrote:
Congratulations Bob! It looks like another set of successful USNA
satellites.
I noticed Space Track isn't publishing keps for these as of yet. I know this
has happened with previous DOD launches that had secondary payloads. Do you
know if they will eventually provide them to the owners of the satellites
(like previous launches) for them to distribute? I'd like to be able to
track these automatically, and the current 6 minute difference is a bit much
error for an AO-13 class system.
73, Drew KO4MA
-----Original Message-----
From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Robert
Bruninga
Sent: Friday, May 22, 2015 2:54 PM
To: AMSAT BB
Subject: [amsat-bb] USNA Sat Status (day 3)
PSAT Summary - Day 3
* PSAT packet telemetry is OK, Digipeater will be off (secondary mission)
* PSAT PSK31 transponder is ON with 28.120 MHz uplink! (primary mission)
* WOD data fixed.? Spin data now available.? Right now it is at 3 RPM with
+Z pointing at Sun
* Launch TLE elements (below) are 6 minutes ahead of satellite
* PCSAT.APRS.ORG web page is now also capturing PSAT telelmetry downlinks
* BRICSAT telemetry has been heard but is cycling OFF due to low power
* BRICSAT PSK31 downlink (also FM) has also been heard barely (when ON)
* USS Langley not heard
Only fault so far is the loss of the 4 day-fail-safe backup reset circuit
(1 of 3) fail safe backup RESET capabilities.? The lack of WOD data was
because we had a LOW-POWER bits set that was holding it off.
BRICSAT PSK31 transponder is on identical frequencies as PSAT's.? You can
tell them apart because one has PSK Telemetry on 315 Hz and the other is on
365 Hz.? Both on the UHF FM downlink 435.350 MHz
SUMMARY:
PSAT:? ? ? 145.825 - 1200 baud AX.25 telemetry - digi off
PSAT PSK31#1:? 435.350 FM down, 28.120 SSB PK31 uplink - Brno University
Xponder
BRICsat:? 437.975 - 9600 baud telemetry downlink every 20s BRICsat PSK31#2 -
same as PSAT but PSK TLM on 375 Hz (PSAT on 315 Hz)
USS Langley - 437.975? 9600 baud telemetry
ULTRASat3? <these now predicting 6 minutes ahead of actual satellite>
1 99993U? ? ? ? ? 15140.67013889? .00040043? 00000-0? 10235-2 0 00009
2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
Bob, WB4APR
_______________________________________________
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: 12
Date: Sat, 23 May 2015 09:02:22 -0400
From: "David L Warnberg" <dwarnberg@xxxxxxx.xxx>
To: "'AMSAT BB'" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] PSAT
Message-ID: <003101d09558$b86df920$2949eb60$@xxx>
Content-Type: text/plain; charset="US-ASCII"
This is what I caught this morning in Florida on the12:46 UTC pass from
PSAT.
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=4 >[08:53:09]
Hi!
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=52 >[08:53:44]
S#002723,0z200,a0McbLbcL0cLAbL00LcAMdaLdbL0cL0aLaAL
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=7 >[08:54:03]
PSKoff
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=7 >[08:54:12]
PSKoff
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=6 >[08:54:21]
PSKon
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=52 >[08:54:52]
S#002724,0z200,eBLd0LdaL0aL0ALcCLeBLd0LaaL00L0CLbDL
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=34 >[08:54:57]
T#960,768,361,497,921,867,00011100
1:Fm PSAT-1 To APOFF <UI pid=F0 Len=52 >[08:55:52]
S#002725,0z200,dCLcALa0LA0LBCLAELaDLbBLa0LDaLEBLDDL
David
KK4QOE
------------------------------
Message: 13
Date: Sat, 23 May 2015 16:23:35 +0200
From: Nico Janssen <hamsat@xxxxxx.xx>
To: Robert Bruninga <bruninga@xxxx.xxx>, AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] PSAT Elements are 6 minutes early
Message-ID: <55608D67.2070800@xxxxxx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed
Bob,
Yesterday and today I performed detailed doppler measurements on high
PSAT passes,
both on 70 cm and on 2 m.
I found that yesterday the satellite was 10 seconds early and today 14
seconds early,
compared to the ULTRASat3 TLE set.
I wonder why you think it is 6 minutes late. Maybe you were confused by
the ASCII
telemetry transmissions on 145.826 MHz of UoSAT-OSCAR 11, which passed
about 6 minutes
after PSAT?
73,
Nico PA0DLO
On 2015-05-22 20:21, Robert Bruninga wrote:
> I am finding that PSAT is 6 MINUTES behind the predictions of the previously
> provided original Launch TLE :
>
> ULTRASat3
> 1 99993U 15140.67013889 .00040043 00000-0 10235-2 0 00009
> 2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
>
> So until I get new ones. Just point at AOS and wait 6 miuntes.
>
> Also, I had said not to TX PSK31 on the 10m u plink until you heard the
> downlink. Well, that was dumb advise, because the transponder does not come
> up unless it hears PSK31!
>
> So the new rule is, Listen first. If not heard, TX anyway. If not heard
> then, Fix your problem, and try again?
>
> We don?t know how the power budget will work out. So all we can do is
> watch.
>
> Bob, WB4APR
> _______________________________________________
> 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: 14
Date: Sat, 23 May 2015 10:34:35 -0400
From: John Papay <john@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] UT1FG/MM update
Message-ID: <260272.2418.bm@xxxxxxx.xxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Yuri has left Norfolk and is on his way
to Mariel Cuba. You may have seen him at
anchor out in the bay after he left the
berth. A fuel barge was next to him filling
up his tanks!
Yuri has sent mail to the following stations:
KD8CAO W5PFG W5CBF N5UXT KJ4MCZ KO4MA WA4NVM
K4FEG N2PPL K9HF K8II W1PA WN9Q. If you don't
receive something in two weeks, please let me
know. As you can imagine, it is no easy job to
confirm so many contacts with so many different
stations. He does what he can considering the
time he can spare. It is a never ending job for
him.
You may have heard that WX4TV and his family were
able to visit the ship yesterday just before it
sailed. Yuri was very busy with his agents and
last minute paperwork but one of the crew gave
them a tour of the ship. I expect that Jim will
be sharing some photos/video of that visit.
We are very fortunate to have someone like Yuri
take an interest in operating the satellites in
hundreds of water grids. It's fun to make all
of those contacts, but it is also a lot of work
to get confirmations out when you are not at home.
Yuri is an amazing operator and ambassador for
ham radio. His callsign is recognized by vhf'ers
around the world. Good luck to everyone trying to
work him. The route down to Cuba should be new for
many operators.
73,
John K8YSE
------------------------------
Message: 15
Date: Sat, 23 May 2015 10:36:49 -0400
From: Sean Kutzko <kx9x@xxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] KX9X/2 FN22 today 1704z
Message-ID: <746CD0FC-00C9-46B2-9FF0-BE3EA7DBF651@xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii
Hi all-
I'm here in Cooperstown, NY, grid FN22. I have a 75-degree pass of SO50 from
1704-1720. Will be QRV for it.
Cooperstown is in a significant valley, so I may only get on for the middle
of the pass.
Using a Handheld and Arrow antenna.
Sent from Sean's iPad
------------------------------
Message: 16
Date: Sat, 23 May 2015 10:51:42 -0400
From: Robert Bruninga <bruninga@xxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] PSAT Elements are 6 minutes early
Message-ID: <547ccce86c654dc8c4c6cbe5215e50c7@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Today, (over USA) I am finding satellite to be 8.5 minutes behind the
ULTRAsat3 TLE. And get a very good match. I am listening to the PSK31 *FM*
downlink on 435.350 +/- 5 KHz and swinging the beam and watching Doppler to
confirm I am tracking well.
But Nico (below) sees it on time in Europe. I cannot explain the
difference... I am using the elements with an EPOC of 15 140.6701389 (shown
below) which were released at separation. There have been no updates yet.
As soon as I get them I will post them.
I did just turn on 3 USA and 3 European packet bulletins. And adjusted the
MA spacecraft counter so that the right bulletins will come on over the
right continents. DIGI will remain off since PSK31 is working so well!
Bob, Wb4APR
-----Original Message-----
From: Nico Janssen
Sent: Saturday, May 23, 2015 10:24 AM
Yesterday and today I performed detailed doppler measurements on high PSAT
passes, both on 70 cm and on 2 m.
I found that yesterday the satellite was 10 seconds early and today 14
seconds early, compared to the ULTRASat3 TLE set.
I wonder why you think it is 6 minutes late. Maybe you were confused by the
ASCII telemetry transmissions on 145.826 MHz of UoSAT-OSCAR 11, which passed
about 6 minutes after PSAT?
73,
Nico PA0DLO
On 2015-05-22 20:21, Robert Bruninga wrote:
> I am finding that PSAT is 6 MINUTES behind the predictions of the
> previously provided original Launch TLE :
>
> ULTRASat3
> 1 99993U 15140.67013889 .00040043 00000-0 10235-2 0 00009
> 2 99993 055.0004 339.9238 0251027 182.3314 074.3075 15.12517086000014
>
> So until I get new ones. Just point at AOS and wait 6 miuntes.
>
> Also, I had said not to TX PSK31 on the 10m u plink until you heard
> the downlink. Well, that was dumb advise, because the transponder
> does not come up unless it hears PSK31!
>
> So the new rule is, Listen first. If not heard, TX anyway. If not
> heard then, Fix your problem, and try again?
>
> We don?t know how the power budget will work out. So all we can do is
> watch.
>
> Bob, WB4APR
> _______________________________________________
> 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 10, Issue 144
*****************************************
Read previous mail | Read next mail
| |
