| |
CX2SA > SATDIG 12.10.15 15:28l 703 Lines 26629 Bytes #999 (0) @ WW
BID : AMSATBB10309
Read: GUEST
Subj: AMSAT-BB-digest V10 309
Path: IW8PGT<IZ3LSV<IR1UAW<IK1NHL<CX2SA
Sent: 151012/1325Z @:CX2SA.SAL.URY.SOAM #:29284 [Salto] FBB7.00e $:AMSATBB10309
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Chesapeake Waterway Festival Oct 10 -11 (Rich/wa4bue)
2. Just Checking... (AO-85) (Loon -)
3. Fox @ ISS (Nader Omer)
4. Re: Saturday evening @ WD9EWK - two AO-85 passes... (George Henry)
5. Any luck decoding AO-85 Telem with Icom IC-9100 USB
Interface? (Bob)
6. Re: Murphy (Alan)
7. Sunday afternoon AMSAT demonstration in Phoenix, including
new satellites! (Patrick STODDARD (WD9EWK/VA7EWK))
8. Re: Eimac Moonbounce - I8CVS (Phil Karn)
9. AO-85 Center frequency (David G0MRF)
10. AMSAT-UK Colloquium - 2016 Dates (Jim Heck)
11. EM15 and EM48 (Glenn Miller - AA5PK)
12. FM xpndr up again? (10/13 0913Z) (Jeff A. Boyd)
13. Re: FM xpndr up again? (10/13 0913Z) (Joe Fitzgerald)
14. Re: FM xpndr up again? (10/13 0913Z) (Jeff A. Boyd)
----------------------------------------------------------------------
Message: 1
Date: Sun, 11 Oct 2015 22:10:33 -0400
From: "Rich/wa4bue" <richard.siff@xxxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Chesapeake Waterway Festival Oct 10 -11
Message-ID: <F23B983B94624FFABC13724F6BA0C748@xxxxxxx>
Content-Type: text/plain; format=flowed; charset=utf-8;
reply-type=response
Hi all
This week end K4AMG MARC (K4AMG.org) operated from Chesapeake, Heritage and
Waterway Festival in the Historic Great Bridge boro of the city.
For all of you that want QSLs from K4AMG please send them to:
K4AMG
5001 Garner Ave.
Portsmouth, VA 23703.
Our new adr has not been changed in the FCC data base.
Thank you for all of the contacts on FO 29 and SO 50.
God Bless
R
W4BUE
------------------------------
Message: 2
Date: Sun, 11 Oct 2015 23:30:35 -0400
From: Loon - <w3mat@xxxxxxx.xxx>
To: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Just Checking... (AO-85)
Message-ID: <SNT150-W72C155D565FA2B28168E73E0310@xxx.xxx>
Content-Type: text/plain; charset="iso-8859-1"
This is how I have both of my FT-60's programmed...
(Mem.1) 435.170 MHz 145.980 MHz (AOS)(Mem.2) 435.175 MHz 145.980 MHz
(Approach)(Mem.3) 435.180 MHz 145.980 MHz (Max El)(Mem.4) 435.185 MHz
145.980 MHz (Depart)(Mem.5) 435.190 MHz 145.980 MHz (LOS)
I work two FT-60's on an Arrow Antenna where the Duplexer has been removed
and RG-8X cables. VHF to thereceive HT, and the UHF cable to the transmit
HT. I've noticed that when AO-85 comes above the horizon andI can hear it
on RX, I am not hearing myself through the receive HT. I've tried switching
between Mem 1 and Mem 2 on the approach and nothing. What I am doing wrong?
Do I need to start at a higher input, say 437.180,or do I need lower inputs
at the start, i.e. 437.160 or 437.165. On the passes I have heard AO-85,
there seem toalways be three of four real strong stations, but yet I seem to
be having difficulty reaching the bird. Any help wouldbe greatly
appreciated. Oh, I am transmitting in FM Narrow if that has anything to do
with it.
PLEASE.... I posted something similar, seeking assistance, to the Facebook
AMSAT group and basically received no help,but rather immature replies with
the exception of one or two. I certainly hope that is not the result here.
Thanks,
Loon W3MAT
------------------------------
Message: 3
Date: Mon, 12 Oct 2015 04:06:03 +0000 (UTC)
From: Nader Omer <st2nh@xxxxx.xxx>
To: Amsat Bb Bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Fox @ ISS
Message-ID:
<1594574645.2194930.1444622763316.JavaMail.yahoo@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
??
?1:Fm RS0ISS-1 To HZ1NH [23:58:12R]
CMD(B/H/J/K/KM/L/M/R/S/SB/SP/ST/SR/V/?)>
s amsat
Subject:
congratulation fox-1a
Message:
thank amsat na
for new satellite
1:Fm RS0ISS-1 To HZ1NH [23:59:13R]
Message saved as Msg # 238
Pse avoid working BBS at continents with APRS Traffic .
73's Nader omer
------------------------------
Message: 4
Date: Sun, 11 Oct 2015 23:56:47 -0500
From: "George Henry" <ka3hsw@xxx.xxx>
To: <amsat-bb@xxxxxx.xxx>, <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Saturday evening @ WD9EWK - two AO-85
passes...
Message-ID: <D5A45180E680418B93BE10F956EBD60D@xxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
So, from Patrick's experience, it sounds like the uplink is about 10kHz
lower than the published frequency? Has this been everyone else's
experience?
George, KA3HSW
----- Original Message -----
From: "Patrick STODDARD (WD9EWK/VA7EWK)" <amsat-bb@xxxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Sent: Sunday, October 11, 2015 9:17 AM
Subject: [amsat-bb] Saturday evening @ WD9EWK - two AO-85 passes...
<snip>
> For the uplink, I was able to get through using 435.165 MHz for my two
> QSOs with the KG-UV8D. Downlink... I started on 145.9825 MHz, then tuned
> down to 145.980 MHz, and later I tuned down to 145.9775 MHz. Just like I
> saw when I used my KG-UV9D Friday evening, the sharper receive filters in
> the Chinese-made radios made using the smaller tuning step (2.5 kHz)
> useful.
>
> After this pass, I played the HDSDR RF recording into FoxTelem, and
> uploaded 9 packets to the AMSAT server. Had I used the Elk with the SDR
> setup, I am sure I would have collected many more packets from that pass.
>
> The second pass I worked, around 0400 UTC, was a shallow pass. AO-85 was
> only up to a maximum elevation of just over 11 degrees. I used only my
> Icom IC-2820H for this pass. I had used the IC-2820H as the uplink radio
> for a pass I worked Friday evening with my SDRplay receiver and HDSDR
> handling the downlink, but wanted to try the mobile radio by itself this
> time. it had no problems hearing the downlink, once AO-85 rose above the
> nearby mountains and houses.
>
> I started the radio on 435.160 MHz for the uplink (with 67.0 Hz tone
> activated for this VFO), and 145.980 MHz for the downlink. Both with
> narrow FM, a suggestion that had been tweeted earlier by Peter 2E0SQL. I
> was not able to get through using 435.160 MHz, but was able to when I
> tuned my uplink to 435.165 MHz. Later in the pass, I could get through
> when transmitting on 435.170 and 435.175 MHz. I had to use 15W, and at
> times 50W, to get through. The pass was too shallow for me to get through
> at 5W. Around the midpoint of the pass, possibly just after that, I had
> to tune my receive VFO down to 145.975 MHz to hear the rest of the pass.
> I mostly heard stations in California, along with W7JPI in southern
> Arizona and WQ3U in Oregon, and logging a total of 5 QSOs (working all I
> heard, except for WQ3U).
<snip>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------
Message: 5
Date: Sun, 11 Oct 2015 20:08:26 -0400
From: Bob <WB4SON@xxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] Any luck decoding AO-85 Telem with Icom IC-9100
USB Interface?
Message-ID:
<CAPonRZ93LLMGaPhiBQuqxe_Khn9uM+FuqUFy-0J5BxkBEuTTyw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Hi all,
I've tried my IC-9100 a couple of times for DUV decoding and I've had no
luck. My first concern is that the USB interface may include filtering
that restricts the bandwidth of the receive audio.
Still hoping it mostly due to using an EggBeater with preamp vs a tracking
beam, but I thought I would ask. Signals are generally pretty good --
fully quiteing for 4-5 minutes around the point of closest approach.
73, Bob, WB4SON
------------------------------
Message: 6
Date: Mon, 12 Oct 2015 00:19:45 -0500
From: Alan <wa4sca@xxxxx.xxx>
To: "'Jerry Buxton'" <n0jy@xxxxx.xxx>, "'AMSAT-BB'"
<amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Murphy
Message-ID: <002d01d104ad$9bbd41e0$d337c5a0$@xxxxx.xxx>
Jerry,
This is the ham equivalent of Charlie Brown's kite eating tree. Somehow no
matter what you do, a tree
limb (which hopefully you do not have in the attic), cable, or control cable
will reach out and snag
someone.
73s,
Alan
WA4SCA
<-----Original Message-----
<From: AMSAT-BB [mailto:amsat-bb-bounces@xxxxx.xxxx On Behalf Of Jerry Buxton
<Sent: Sunday, October 11, 2015 9:03 PM
<To: AMSAT-BB <amsat-bb@xxxxx.xxx>
<Subject: [amsat-bb] Murphy
<
<Well, the launch and deploy went without an apparent hitch and given the
<presence of Murphy throughout the Fox-1A project up through delivery I
<thought that was pretty amazing if not downright spooky.
<
<My qualms were settled tonight when Murphy was back, this time on the
<first pass that I have had an opportunity to copy AO-85 on my own. I
<set up at home to do just telemetry, and when she rose the signal was
<horrible to say the least. It did get a little better as things went on
<and pretty good at 30+ degrees of elevation but still pretty weak.
<
<Having read reports that ranged from "outstanding" to "disappointed" I
<thought I was finally finding out for sure what we had done.
<
<So I tried manually moving the antennas thinking that if the keps are a
<little off that might help.
<
<That's when I noticed that the antennas weren't moving. Still pointed
<southwest, maybe 45 degrees elevation, even though the satellite was
<passing up high to the west.
<I ran up to the attic and lo, the very dual band Diamond vertical
<antenna that I had borrowed from the Hood County Club and placed in the
<attic for testing Fox-1Cliff/D on the air, was caught in the elements of
<my 70 cm antenna! The antenna was pointed north-northeast at 45 degrees
<elevation and the rotator had been turning the mast within the tripod so
<it thought it was pointing southwest/west. I guess I've been off the
<birds long enough that it never occurred to me that where I placed it
<was duh, not a good location when you start swinging long beams around.
<
<How's that for comedy? Fox-1D (current configuration in the Labs
<running on that Diamond antenna) takes down my Fox-1A pass out of sheer
<jealousy! :-D
<
<The good news was, I was copying telemetry even though the satellite was
<generally off the back or 90 degrees above the beam of the antenna. And
<when it came into the beam, it was loud and clear as I had expected,
<although it faded as it set and I could not track it but lowering the
<elevation since azimuth was hosed.
<
<It's good to be back in the realm of ham radio where anything that can
<go wrong, will!
<
<--
<Jerry Buxton, N?JY
<
<_______________________________________________
<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: Mon, 12 Oct 2015 05:53:36 +0000
From: "Patrick STODDARD (WD9EWK/VA7EWK)" <amsat-bb@xxxxxx.xxx>
To: "amsat-bb@xxxxx.xxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Sunday afternoon AMSAT demonstration in Phoenix,
including new satellites!
Message-ID:
<CAN6TEUcuF_5M=q7carJNBTbn0BzV02GiFntEXyXnA-DUhC1jtQ@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8
Hi!
I received an e-mail asking about a demonstration of satellite operating,
possibly this afternoon if I had the time. It is still warm here in the
Phoenix area, but not over 100F/38C today, so I went to a city park in the
southeast corner of Phoenix in grid DM43ah. I was out here a couple of
months ago, and this time the plan was to try focusing on the satellites
from AMSAT and China that had been recently launched. I worked SO-50,
FO-29, the ISS, XW-2E, and AO-85 from the park. While working AO-85,
XW-2F was passing by at the same time. I was able to hear both of these
satellites, as I focused on working AO-85.
The demonstration started in the mid-afternoon, with an SO-50 pass just
after 2pm/2100 UTC. I did a simple demonstration, using my Kenwood TH-D72A
HT and Elk log periodic, working a few stations. Around 2140 UTC, there
was a very nice FO-29 pass, and I worked it using one of my FT-817NDs and
the Elk log periodic. This was only the second time I tried working FO-29
half-duplex, and I was able to chat with Tom WA0POD for a couple of minutes
for my only QSO on that satellite.
The ISS passed by around 2200 UTC, and I was unsuccessful in sending my
packets through the digipeater. When I got home tonight, I think I figured
out the issue - wrong packet path on 145.825 MHz. Oops. We heard a bit of
activity from around the western USA, including KG7NXH (not far to the
east of this park, in another Phoenix-area suburb). Then a break for lunch,
and talking about the new satellites and other topics like using SDR
receivers, before the fun really started...
For passes of XW-2E, XW-2F, and AO-85 around 0100 UTC, I went back to that
city park and set up a couple of stations. One I used for my operating:
Yaesu FT-817ND for SSB transmit
Icom IC-2820H for FM transmit
SDRplay SDR receiver
8-inch HP Windows 10 tablet with HDSDR (making RF recordings of the passes)
Elk 2m/70cm log periodic antenna
and another station for receiving:
FUNcube Dongle Pro+
10-inch Winbook Windows 10 tablet with HDSDR
AMSAT-UK (Winkler) VHF crossed dipole
XW-2E came first. I heard a couple of stations on, tried to get a clear
spot to call CQ, and ended up making 4 QSOs while keeping an eye on the
clock. I saw that XW-2F and AO-85 were passing by our location around the
same time. I had worked XW-2E in SSB, so I suggested I try AO-85 in FM.
This was an interesting experience...
For the first few minutes of the pass, I saw - and occasionally heard -
the XW-2F CW beacon that was just below the AO-85 FM/data downlink. I was
using narrow FM, about 14 kHz in HDSDR, and I raised the audio filter for
the low side of the audio passband to eliminate any part of the slow-speed
data from reaching my ears. Did I mention I am really enjoying SDR for my
satellite work? :-) This is something that made the audio more pleasing to
hear. Not stereo quality, of course, but no buzzing from remnants of the
telemetry making it into the audio we hear on our radios when working the
FM repeater.
About 10 kHz or so above the AO-85 downlink, I saw an SSB signal pop up in
the XW-2F transponder. When I played the HDSDR RF recording back at home, I
found it was Leo W7JPI calling CQ on the XW-2F transponder. Not much on
that transponder, but a larger crowd on AO-85. I was able to make 5 QSOs on
AO-85, and - later - upload some data to the AMSAT server.
The second station had some issues I will need to investigate, especially
with the XW-2E pass. It is possible I should have brought out my second Elk
log periodic, instead of relying on the crossed dipole. Even with the
receive issues at the second station, it was still a good illustration of
using SDR receivers for satellite work, and showing that the inexpensive
Windows tablets are capable of running HDSDR and the Fox telemetry software
packages.
As I write this e-mail, my uploads to Dropbox have completed. I put the RF
recordings from the XW-2E and AO-85/XW-2F passes, along with some photos of
my setup for the later passes and other screengrabs in separate folders
there. You can go to http://dropbox.wd9ewk.net/ (hit F5 a few times, if the
folder/file listing doesn't immediately show in your browser) to see those
files. I didn't make a separate MP3 recording of the AO-85 pass, relying on
the RF recording for my logging when I returned home this evening.
I really don't have many new observations for AO-85 tonight. I worked it on
the premise that the uplink frequency is 10 kHz below what was originally
published. That worked again tonight. I used narrow FM on the uplink radio,
and narrowed the receive bandwidth and adjusted the audio filtering in
HDSDR so I wouldn't hear any buzzing or other noises from the telemetry on
the downlink. Normally HDSDR's AFC works very well with AO-85's downlink,
but for several minutes the AFC kept sliding my receive frequency down to
the XW-2F CW beacon just below the AO-85 downlink. I had to turn off the
AFC until the two signals had more separation between them. Once the XW-2F
CW beacon went lower in frequency, away from the AO-85 downlink, I resumed
using AFC. I had no AFC-related problems for the remainder of the pass.
The nominal frequency of the AO-85 downlink seemed to be closer to 145.978
MHz tonight. This may complicate working this satellite for some, who may
not want to adjust the downlink frequency. The Chinese-made HTs I have used
would definitely need to have the downlink frequency adjusted during AO-85
passes. Some non-Chinese radios may be able to start passes on 145.980 MHz,
but have to be adjusted down to 145.975 MHz for the last part of the pass.
This may not be a hard-and-fast rule for all non-Chinese radios, depending
on how sharp or forgiving the front-end filtering happens to be on these
radios. When I worked earlier AO-85 passes with the Wouxun HTs, and the
Icom IC-2820H last night, I just use the VFOs. No memory channels. I set
both VFOs for narrow FM, set the 67.0 Hz CTCSS tone in the transmit VFO,
5 kHz tuning step in the transmit VFO, and the smallest possible FM tuning
step in the receive VFO (5 kHz for the IC-2820H, 2.5 kHz for the Wouxun
HTs).
Since I was not home for these passes, I did not try a different radio (or
radio combination) for AO-85. If time permits in the next couple of days,
and if the transponder is on in the evenings for western US passes, I might
be able to try another radio or two before leaving for the AMSAT Symposium.
Otherwise, trying different radios on AO-85 will resume after I return from
Dayton, later this month.
Again, thanks to AMSAT for making the AO-85 transponder available over this
weekend! It has been fun to work a satellite that's only been in orbit now
for just over 3 days. I hope the telemetry and other tests are showing the
satellite in good working order. And thanks to all of the stations that
called or worked WD9EWK during this afternoon and early evening. :-)
73!
Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/
Twitter: @xxxxxx
------------------------------
Message: 8
Date: Sun, 11 Oct 2015 23:50:20 -0700
From: Phil Karn <karn@xxxx.xxx>
To: Thomas Doyle <tomdoyle1948@xxxxx.xxx>
Cc: AMSAT <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Eimac Moonbounce - I8CVS
Message-ID: <561B582C.9090605@xxxx.xxx>
Content-Type: text/plain; charset=utf-8
On 10/11/15 08:30, Thomas Doyle wrote:
> Phil,
>
> Thanks for the post. Since I8CVS passed I had wanted to bring up a
> subject but was a bit hesitant. I8CVS had a mountain of information. He
> helped me with many things. It may seem a bit selfish but I regret that
> not only is he a SK but all that information is lost. It probably became
> a victim of the same 'paper eradication campaign' you described that
> will destroy your docs.
I hear you. And I'm more than willing to let other people "mirror" the
stuff that I scan. I'm only concerned about possible copyright issues,
but if AMSAT (or whoever) doesn't care, then I'm all for it.
I occasionally hear thoughtful comments (e.g., from Vint Cerf, one of
the "fathers" of TCP/IP) that we may be setting ourselves up for a
digital dark ages in which our distant descendants can't figure out how
we lived or what we created because they can't read our digital formats.
I think that may be a *bit* too pessimistic, but it's certainly
something to think about. (Ever see "Forbidden Planet"?)
Years ago I came to the conclusion that the best way to preserve digital
information is to "keep it spinning", i.e., to run a server with
everything online, ideally in RAID arrays, and to use it regularly so
you can catch and fix problems before they become unfixable. As
technology improves and/or your old equipment wears out, you copy
everything over. This is much more effective than keeping stuff offline
on media that may silently become unreadable either through degradation
or simple obsolescence.
This was fairly easy as hard drives rapidly got more capacious (I won't
say "bigger) and cheaper, but as you've probably noticed improvements
seem to have slowed down over the past few years. The most recent
improvements in storage density seem to be increasingly hard fought,
e.g., with helium-atmosphere drives and "shingled" recording. But at
least communications keeps improving, and it's not at all unreasonable
for individuals to mirror large archives to each other over the Internet.
Perhaps we should make it a project to collect and digitally archive as
much AMSAT and AMSAT-related information as we can and replicate it as
widely as possible for safekeeping. This may require a bit of rethinking
on the part of AMSAT's leadership, specifically whether it's more
important to make whatever it currently makes selling books and such or
to preserve all this information for posterity, because I see a bit of
tension between these two goals. Personally I think AMSAT would be
better off in the long run if it simply distributed all its publications
online in non-DRM digital formats and relied on wider exposure and the
honor system and donations for its income. At the very least, they'd
save a lot of money printing and mailing paper journals and proceedings.
And I wouldn't have to cut them up and scan them to keep this place from
filling up.
--Phil
------------------------------
Message: 9
Date: Mon, 12 Oct 2015 05:38:48 -0400
From: David G0MRF <g0mrf@xxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] AO-85 Center frequency
Message-ID: <1505b6aab78-55b9-6@xxxxxxxxxx.xxxx.xxx.xxx>
Content-Type: text/plain; charset=utf-8
Hi all.
I've just looked at the FOX1 TLM graph for frequency for 6 passes of AO-85
which included illuminated and eclipsed orbits.
The graph shows the frequency ranging from nominal +1 kHz to nominal -5kHz
which suggests that the frequency of the telemetry is around 2k low at
145.978 MHz.
Is that the general consensus or have I made an error? - I did check the
FC dongle, it's 82Hz off when used with a calibrated source and foxtlm
73
David
------------------------------
Message: 10
Date: Mon, 12 Oct 2015 10:48:45 +0100
From: Jim Heck <jimlist@xxxx.xxx>
Cc: AMSAT <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] AMSAT-UK Colloquium - 2016 Dates
Message-ID: <561B81FD.9070505@xxxx.xxx>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi Folks,
The dates for the next Colloquium have now been confirmed as Fri 29
Jul to Sun 31 July 2016. It will be held in the same location as in
2015, ie the Holiday Inn, Guildford, UK
73s Jim G3WGM
Hon Sec AMSAT-UK
------------------------------
Message: 11
Date: Mon, 12 Oct 2015 05:10:41 -0500
From: "Glenn Miller - AA5PK" <aa5pk@xxxxxxxxxx.xxx>
To: "AMSAT BBS" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] EM15 and EM48
Message-ID: <27A26327158543049110FA1C7E8FB620@xxxxxxx>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
En route to the AMSAT Symposium in Dayton, I plan to operate from EM15 on
Wednesday and EM48 on Thursday. If I can get to it
easily, I'll operate from the EM48/EM58 grid line Thursday evening.
I'll be on the evening passes (around 0000Z) of XW-2E and -2F as well as
AO-85 and LilacSat-2 (if they're on).
73
Glenn AA5PK
------------------------------
Message: 12
Date: Mon, 12 Oct 2015 20:49:58 +0900
From: "Jeff A. Boyd" <the2belo@xxx.xxxxxxx.xx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] FM xpndr up again? (10/13 0913Z)
Message-ID: <20151012204958.99A2.63087B45@xxx.xxxxxxx.xx.xx>
Content-Type: text/plain; charset="US-ASCII"
I tracked a pass off the east coast of Japan monitoring the FM downlink just
in case it was up, and lo and behold, it was.
https://soundcloud.com/minus2c/ao-85-pass-oct-12-2015-1813-jst
I didn't expect it to be up, only to hear the test recording. Was this an
unannounced activation, or were there just people
hitting it unscheduled?
J. Boyd (JR2TTS)
--
J. Boyd, JR2TTS/NI3B
the2belo@xxx.xxxxxxx.xx.xx
http://www.flickr.com/photos/the2belo/
http://www.qrz.com/db/JR2TTS
Twitter: @xxxxxxxx
------------------------------
Message: 13
Date: Mon, 12 Oct 2015 08:45:14 -0400
From: Joe Fitzgerald <jfitzgerald@xxxx.xxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] FM xpndr up again? (10/13 0913Z)
Message-ID: <561BAB5A.4030800@xxxx.xxx.xxx>
Content-Type: text/plain; charset=windows-1252
On 10/12/2015 7:49 AM, Jeff A. Boyd wrote:
> I didn't expect it to be up, only to hear the test recording. Was this an
unannounced activation, or were there just people
> hitting it unscheduled?
>
The spacecraft is still in the testing phase and not considered
operational. If you find the transponder on, please feel free to use
it, but it may be changed to high speed data or safe mode at any time.
See:
http://amsat.org/pipermail/amsat-bb/2015-October/055429.html
-Joe KM1P
------------------------------
Message: 14
Date: Mon, 12 Oct 2015 22:24:03 +0900
From: "Jeff A. Boyd" <the2belo@xxx.xxxxxxx.xx.xx>
To: amsat-bb@xxxxx.xxx
Subject: Re: [amsat-bb] FM xpndr up again? (10/13 0913Z)
Message-ID: <20151012222403.99A6.63087B45@xxx.xxxxxxx.xx.xx>
Content-Type: text/plain; charset="US-ASCII"
On Mon, 12 Oct 2015 08:45:14 -0400, Joe Fitzgerald
<jfitzgerald@xxxx.xxx.xxx> wrote:
>
> On 10/12/2015 7:49 AM, Jeff A. Boyd wrote:
> > I didn't expect it to be up, only to hear the test recording. Was this
an unannounced activation, or were there just people
> > hitting it unscheduled?
> >
>
> The spacecraft is still in the testing phase and not considered
> operational. If you find the transponder on, please feel free to use
> it, but it may be changed to high speed data or safe mode at any time.
>
> See:
>
> http://amsat.org/pipermail/amsat-bb/2015-October/055429.html
Okay, thanks for the clarification -- I didn't want to transmit to it
without knowing for sure whether or not it's officially
sanctioned.
73!
--
J. Boyd, JR2TTS/NI3B
the2belo@xxx.xxxxxxx.xx.xx
http://www.flickr.com/photos/the2belo/
http://www.qrz.com/db/JR2TTS
Twitter: @xxxxxxxx
------------------------------
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 309
*****************************************
Read previous mail | Read next mail
| |
