OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
CX2SA  > SATDIG   23.08.14 03:46l 686 Lines 23731 Bytes #999 (0) @ WW
BID : AMSATBB9290
Read: GUEST
Subj: AMSAT-BB-digest V9 290
Path: IW8PGT<IZ3LSV<IQ5KG<IK1NHL<CX2SA
Sent: 140823/0143Z @:CX2SA.SAL.URY.SOAM #:9569 [Salto] FBB7.00e $:AMSATBB9290
From: CX2SA@CX2SA.SAL.URY.SOAM
To  : SATDIG@WW

Today's Topics:

   1. AmsatDroid Error (David Johnson)
   2. more from the Satpc32 aggravation file (Lizeth Norman)
   3. Hello Europe? Florida calling on the 1715z AO-7 pass!
      (Lizeth Norman)
   4. Re: more from the Satpc32 aggravation file (Alan)
   5. Re: more from the Satpc32 aggravation file (Thomas Doyle)
   6. W1AW/7 on satellites starting Wednesday (UTC time)
      (Patrick STODDARD (WD9EWK/VA7EWK))
   7. Re: more from the Satpc32 aggravation file (Thomas Doyle)
   8. Galileo 1260-1300 MHz - Protection Radius (M5AKA)
   9. FUNcube/AO-73 Mode change (Jim Heck)
  10. Re: Galileo 1260-1300 MHz - Protection Radius (Alessio Sacchi)
  11. Finally! (Martha)
  12. EM60-70-80, EL89 25-27AUG (Andrew Glasbrenner)
  13. (no subject) (B J)
  14. SpaceX Test Vehicle Explodes (B J)
  15. Decoding 9K6baud telemetry via SDR help (larry)
  16. Re: SpaceX Test Vehicle Explodes (Brenton Salmi)


----------------------------------------------------------------------

Message: 1
Date: Fri, 22 Aug 2014 15:35:57 +0100
From: David Johnson <dave@xxxxx.xx.xx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] AmsatDroid Error
Message-ID: <53F7554D.8080003@xxxxx.xx.xx>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,

It has been reported that there is a problem on the SkyMap in the latest
version that shows an incorrect IARU locator.

I have replicated the problem and will be fixing it in the next few hours.

I will let you know when it's available in the Google Play store.

My apologies for any inconvenience caused.

73

- Dave, G4DPZ


------------------------------

Message: 2
Date: Fri, 22 Aug 2014 12:03:46 -0400
From: Lizeth Norman <normanlizeth@xxxxx.xxx>
To: "<,amsat-bb@xxxxx.xxxxxxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] more from the Satpc32 aggravation file
Message-ID:
<CAJUhCTNDkmqG+qumjfDfwsWGvtMC2KvMTDzhSSR69BxDDwqX+A@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Why would altering the doppler.sqf file not work with direct
modification via Windows Notepad?
The symptom is that the frequency is not recognized, although the line
in the doppler.sqf file is apparently correct.
Going over to the .tle file to check the spelling, spacing and so
forth on the satellite name, the bright idea overcame me to find out
what happens when I copy and paste the name (obviously the same to the
EYE!!!) from the .tle file to the doppler.sqf file.
Low and behold, it worked. Nothing in the rest of the line in the
doppler.sqf file was altered.
I surmise that even though the displayed characters are the same,
somehow they are not.
What is the formatting issue that I'm running into? This has happened
before AND I have not, until today found out why.
How do I fix this? I have spent a fair amount of headbanging here.
This is just the latest episode.
If I looked at the file in a hex editor, I am sure I would not know
what to look for. Probably break more than I fix.
Norm n3ykf


------------------------------

Message: 3
Date: Fri, 22 Aug 2014 13:28:56 -0400
From: Lizeth Norman <normanlizeth@xxxxx.xxx>
To: "<,amsat-bb@xxxxx.xxxxxxxx <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Hello Europe? Florida calling on the 1715z AO-7
pass!
Message-ID:
<CAJUhCTP_th3ePtLDJqSi=ukZS4U5F1yfiRJZ4PcXfDxfy5V86g@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Listened to the early pass this am 0730 UTC and copied ei5v fb with
the fcd. Could even hear myself on the downlink with no desense and no
cavity filter. Max elevation:1.7 degrees. Not bad for a 10' tower.
Took just a little too long to go from passive listening mode to
finding myself and answering. Don't want to plug the square connector
into the round hole and apply power.
Never worked Europe, period. Next time just keeps me going..


------------------------------

Message: 4
Date: Fri, 22 Aug 2014 12:36:23 -0500
From: Alan <wa4sca@xxxxx.xxx>
To: "AMSAT-BB" <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] more from the Satpc32 aggravation file
Message-ID: <000c01cfbe2f$98501840$c8f048c0$@xxxxx.xxx>
Content-Type: text/plain;	charset="us-ascii"

Hi Norm,

I regularly edit the DOPPLER.SQF file using Notepad.  Whenever there is an
issue such as you mention,
I always find that there is some subtle difference between the actual
satellite name and that which I
typed.  Sometimes a space, for instance.  You might well find that with a
hex editor.   Using the
AMSATNAMES.TXT file is a good way to make certain the satellite name is
exactly what you want it to
be.

You do needed to close and restart SatPC32 for the change to be recognized. 
Also, if you are adding a
new entry at the end of the DOPPLER.SQF file, make certain you hit return at
the end before saving.  I
have noticed in some places that if you don't to that, the last line is not
parsed.

Good luck,

Alan
WA4SCA


<-----Original Message-----
<From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
Behalf Of Lizeth Norman
<Sent: Friday, August 22, 2014 11:04 AM
<To: <,amsat-bb@xxxxx.xxxxxxx
<Subject: [amsat-bb] more from the Satpc32 aggravation file
<
<Why would altering the doppler.sqf file not work with direct
<modification via Windows Notepad?
<The symptom is that the frequency is not recognized, although the line
<in the doppler.sqf file is apparently correct.
<Going over to the .tle file to check the spelling, spacing and so
<forth on the satellite name, the bright idea overcame me to find out
<what happens when I copy and paste the name (obviously the same to the
<EYE!!!) from the .tle file to the doppler.sqf file.
<Low and behold, it worked. Nothing in the rest of the line in the
<doppler.sqf file was altered.
<I surmise that even though the displayed characters are the same,
<somehow they are not.
<What is the formatting issue that I'm running into? This has happened
<before AND I have not, until today found out why.
<How do I fix this? I have spent a fair amount of headbanging here.
<This is just the latest episode.
<If I looked at the file in a hex editor, I am sure I would not know
<what to look for. Probably break more than I fix.
<Norm n3ykf
<_______________________________________________
<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://amsat.org/mailman/listinfo/amsat-bb



------------------------------

Message: 5
Date: Fri, 22 Aug 2014 12:38:40 -0500
From: Thomas Doyle <tomdoyle1948@xxxxx.xxx>
To: Lizeth Norman <normanlizeth@xxxxx.xxx>
Cc: "<,amsat-bb@xxxxx.xxxxxxxx <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] more from the Satpc32 aggravation file
Message-ID:
<CAHnRQRLJA1mbd+9ohkfqfcuerfTOt7jwstLTfs7sD4jOp0SR6w@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Give this a try. It works for me and might do what you want.

http://www.tomdoyle.org/dopplersqfeditor/DopplerSqfEditor.html

73 W9KE Tom Doyle


On Fri, Aug 22, 2014 at 11:03 AM, Lizeth Norman <normanlizeth@xxxxx.xxx>
wrote:

> Why would altering the doppler.sqf file not work with direct
> modification via Windows Notepad?
> The symptom is that the frequency is not recognized, although the line
> in the doppler.sqf file is apparently correct.
> Going over to the .tle file to check the spelling, spacing and so
> forth on the satellite name, the bright idea overcame me to find out
> what happens when I copy and paste the name (obviously the same to the
> EYE!!!) from the .tle file to the doppler.sqf file.
> Low and behold, it worked. Nothing in the rest of the line in the
> doppler.sqf file was altered.
> I surmise that even though the displayed characters are the same,
> somehow they are not.
> What is the formatting issue that I'm running into? This has happened
> before AND I have not, until today found out why.
> How do I fix this? I have spent a fair amount of headbanging here.
> This is just the latest episode.
> If I looked at the file in a hex editor, I am sure I would not know
> what to look for. Probably break more than I fix.
> Norm n3ykf
> _______________________________________________
> 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://amsat.org/mailman/listinfo/amsat-bb
>



--

Sent from my computer.

tom ...


------------------------------

Message: 6
Date: Fri, 22 Aug 2014 10:43:18 -0700
From: "Patrick STODDARD \(WD9EWK/VA7EWK\)" <amsat-bb@xxxxxx.xxx>
To: amsat-bb@xxxxx.xxx
Subject: [amsat-bb] W1AW/7 on satellites starting Wednesday (UTC time)
Message-ID:
<1408729398.3181.YahooMailBasic@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=us-ascii

Hi!

Following the schedule for W1AW/x portable activity during 2014, next
week will start the second of the two weeks W1AW/7 will air from
Arizona. The first W1AW/7 Arizona satellite activity in March was
successful (thanks, John K8YSE, for making good use of the K8YSE/7
station in Arizona that week), and I'm hoping for another successful week
starting at 0000 UTC Wednesday, 27 August (2000 EDT/1700 PDT on
Tuesday, 26 August).

I will be operating as W1AW/7 on weeknights, and plan on more activity
during the Labor Day weekend (30 August-1 September) that falls within
this one-week period. I am working on having additional operators for the
weekday passes, when I won't be able to get on the radio myself. As with
any of the W1AW/x activities, ARRL will handle the QSLing. ARRL will
upload all W1AW/7 logs to Logbook of the World, in addition to the paper
QSL cards that will be available later.

If you also work other bands and want to work W1AW/7 from Arizona
next week, the W1AW/7 Arizona activity coordinator, Ned Stearns AA7A,
has a schedule showing when the other stations operating as W1AW/7 will
be on - and on what band/mode combinations. This schedule is still being
assembled, so more slots will be filled in as we get closer to next week.
You can see that schedule at:

http://aa7a.net/W1AW/W1AW_7_AZ_1September.htm

Satellite operating times will not appear on Ned's schedule, as I am
coordinating that part of the W1AW/7 effort.  I'll use the AMSAT-BB list
and my Twitter @xxxxxx feed (http://twitter.com/WD9EWK ) to send
out updates for the W1AW/7 satellite activity.

Good luck, and 73!





Patrick WD9EWK/VA7EWK
http://www.wd9ewk.net/





------------------------------

Message: 7
Date: Fri, 22 Aug 2014 13:26:29 -0500
From: Thomas Doyle <tomdoyle1948@xxxxx.xxx>
To: Alan Biddle <APBIDDLE@xxxxxxx.xxx>
Cc: AMSAT-BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] more from the Satpc32 aggravation file
Message-ID:
<CAHnRQR+vSLkHFO=gLfJXknzU4scorXZe-3A+bKD17TwJjd1XMg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Norm,

Alan is correct, ignore my previous post and stick with Notepad. Just be
very careful, do everything right and you will not have any problems.

73 W9KE Tom Doyle




On Fri, Aug 22, 2014 at 12:36 PM, Alan <wa4sca@xxxxx.xxx> wrote:

> Hi Norm,
>
> I regularly edit the DOPPLER.SQF file using Notepad.  Whenever there is an
> issue such as you mention,
> I always find that there is some subtle difference between the actual
> satellite name and that which I
> typed.  Sometimes a space, for instance.  You might well find that with a
> hex editor.   Using the
> AMSATNAMES.TXT file is a good way to make certain the satellite name is
> exactly what you want it to
> be.
>
> You do needed to close and restart SatPC32 for the change to be
> recognized.  Also, if you are adding a
> new entry at the end of the DOPPLER.SQF file, make certain you hit return
> at the end before saving.  I
> have noticed in some places that if you don't to that, the last line is
> not parsed.
>
> Good luck,
>
> Alan
> WA4SCA
>
>
> <-----Original Message-----
> <From: amsat-bb-bounces@xxxxx.xxx [mailto:amsat-bb-bounces@xxxxx.xxxx On
> Behalf Of Lizeth Norman
> <Sent: Friday, August 22, 2014 11:04 AM
> <To: <,amsat-bb@xxxxx.xxxxxxx
> <Subject: [amsat-bb] more from the Satpc32 aggravation file
> <
> <Why would altering the doppler.sqf file not work with direct
> <modification via Windows Notepad?
> <The symptom is that the frequency is not recognized, although the line
> <in the doppler.sqf file is apparently correct.
> <Going over to the .tle file to check the spelling, spacing and so
> <forth on the satellite name, the bright idea overcame me to find out
> <what happens when I copy and paste the name (obviously the same to the
> <EYE!!!) from the .tle file to the doppler.sqf file.
> <Low and behold, it worked. Nothing in the rest of the line in the
> <doppler.sqf file was altered.
> <I surmise that even though the displayed characters are the same,
> <somehow they are not.
> <What is the formatting issue that I'm running into? This has happened
> <before AND I have not, until today found out why.
> <How do I fix this? I have spent a fair amount of headbanging here.
> <This is just the latest episode.
> <If I looked at the file in a hex editor, I am sure I would not know
> <what to look for. Probably break more than I fix.
> <Norm n3ykf
> <_______________________________________________
> <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://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://amsat.org/mailman/listinfo/amsat-bb
>



--

Sent from my computer.

tom ...


------------------------------

Message: 8
Date: Fri, 22 Aug 2014 20:29:55 +0100
From: M5AKA <m5aka@xxxxx.xx.xx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Galileo 1260-1300 MHz - Protection Radius
Message-ID:
<1408735795.17457.YahooMailNeo@xxxxxxxxx.xxxx.xxx.xxxxx.xxx>
Content-Type: text/plain; charset=iso-8859-1

In a previous post I mentioned a paper written in 2006 which indicated a 700
watt ERP amateur station might knock out a users 1260-1300 MHz Galileo
receiver at a distance of 18 km.?
http://www.southgatearc.org/articles/galileo.htm


This may be a considerable underestimate.

Two German ATV repeaters were shut down due to interference to a user's
Galileo receiver which was being used to evaluate the initial 4 test
satellites, the repeaters were:

DB0QI which was 18 km from the receiver

and
DB0ITV which was 55 km from the receiver

My understanding is that both repeaters were running an ERP of just 15
watts, but I've been unable to confirm that figure.

The first two satellites of the operational Galileo GPS constellation were
launched today to be followed by the rest over the next 3 years.

Given the substantial investment in these satellites it seems to me likely
that more European countries will follow the example of Germany and Austria
and seek to protect the 1260-1300 MHz downlink.

73 Trevor M5AKA

------------------------------

Message: 9
Date: Fri, 22 Aug 2014 21:09:11 +0100
From: "Jim Heck" <jimlist@xxxx.xxx>
To: "'AMSAT BB'" <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] FUNcube/AO-73 Mode change
Message-ID: <008101cfbe44$f2418ef0$d6c4acd0$@xxx>
Content-Type: text/plain;	charset="us-ascii"

      Hi Folks,

        FUNcube/AO-73 is now in continuous transponder mode with low
 power  beacon, as at approx 20:05 UTC. Change back to Auto eclipse mode
 planned for Sunday PM UTC.

      Enjoy the transponder

      73s Jim G3WGM




------------------------------

Message: 10
Date: Fri, 22 Aug 2014 22:26:41 +0200
From: Alessio Sacchi <iz4efn@xxxxx.xxx>
To: AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] Galileo 1260-1300 MHz - Protection Radius
Message-ID:
<CAN8hhrbZV_Vdi5EE6+Vs0smJUROOChVdzfp7ZLnkR44GMZ8SNg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Interesting. Few weeks back I spoke with a member of the Italian CC, as our
club was going to add a 1296MHz port to a local repeater. He said Alenia Space
has submitted strong warnings regarding possible interference with Galileo
and he anticipated it could be hard to get a frequency assigned in that
portion of the spectrum in the near future.

Alessio IZ4EFN


On Fri, Aug 22, 2014 at 9:29 PM, M5AKA <m5aka@xxxxx.xx.xx> wrote:

> In a previous post I mentioned a paper written in 2006 which indicated a
> 700 watt ERP amateur station might knock out a users 1260-1300 MHz Galileo
> receiver at a distance of 18 km.
> http://www.southgatearc.org/articles/galileo.htm
>
>
> This may be a considerable underestimate.
>
> Two German ATV repeaters were shut down due to interference to a user's
> Galileo receiver which was being used to evaluate the initial 4 test
> satellites, the repeaters were:
>
> DB0QI which was 18 km from the receiver
>
> and
> DB0ITV which was 55 km from the receiver
>
> My understanding is that both repeaters were running an ERP of just 15
> watts, but I've been unable to confirm that figure.
>
> The first two satellites of the operational Galileo GPS constellation were
> launched today to be followed by the rest over the next 3 years.
>
> Given the substantial investment in these satellites it seems to me likely
> that more European countries will follow the example of Germany and Austria
> and seek to protect the 1260-1300 MHz downlink.
>
> 73 Trevor M5AKA
> _______________________________________________
> 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://amsat.org/mailman/listinfo/amsat-bb
>


------------------------------

Message: 11
Date: Fri, 22 Aug 2014 16:58:24 -0400
From: Martha <martha@xxxxx.xxx>
To: Board of Directors <bod@xxxxx.xxx>,	senior-officers
<senior-officers@xxxxx.xxx>, AMSAT BB <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Finally!
Message-ID:
<CAPk0USy9H26mJk8zO+n9X=ZgjgcZzZTjDJdk4H-PH_9nA_JOQw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Yes, I am going on vacation!  The office will be closed through Monday,
Sept 1.  We will reopen on Tuesday, Sept 2nd at 10:00AM

--
73- Martha


------------------------------

Message: 12
Date: Fri, 22 Aug 2014 19:12:56 -0400
From: Andrew Glasbrenner <glasbrenner@xxxxxxxxxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] EM60-70-80, EL89 25-27AUG
Message-ID: <B2A1F95D-004C-4529-B162-4571502F9019@xxxxxxxxxx.xxx>
Content-Type: text/plain;	charset=us-ascii

I'll be on the road to and from Pensacola through these grids
Monday-Wednesday next week. Let me know if you need a QSO for a new grid
along the way.

73, Drew KO4MA

Sent from my iPhone

------------------------------

Message: 13
Date: Sat, 23 Aug 2014 01:28:35 +0000
From: B J <va6bmj@xxxxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] (no subject)
Message-ID:
<CAP7QzkP_HBU_DUgizWj+bNNJhNu0B5UW4eLbdio_bsPpNW0GEg@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8




------------------------------

Message: 14
Date: Sat, 23 Aug 2014 01:32:10 +0000
From: B J <va6bmj@xxxxx.xxx>
To: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] SpaceX Test Vehicle Explodes
Message-ID:
<CAP7QzkNSONg6HebvTnOcKT_zRTf8AFE2o-n6bgLahu15-eXHBw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

Sorry about the earlier empty post.  I was a bit fumble-fingered when
I started writing .

http://www.parabolicarc.com/2014/08/22/spacex-bad-day-mcgregor/
http://www.parabolicarc.com/2014/08/22/spacex-statement-mcgregor-rocket-explos
ion/
http://www.parabolicarc.com/2014/08/22/video-spacex-rocket-explosion-mcgregor/

This reminds everyone that spaceflight is hard.

73s

Bernhard VA6BMJ @ DO33FL


------------------------------

Message: 15
Date: Fri, 22 Aug 2014 21:35:53 -0400
From: "larry" <zm1267@xxxxx.xxx>
To: <amsat-bb@xxxxx.xxx>
Subject: [amsat-bb] Decoding 9K6baud telemetry via SDR help
Message-ID: <0b1301cfbe72$9442f900$0301a8c0@xxxxxxxx>
Content-Type: text/plain;	charset="iso-8859-1"

   Good day all, I am wondering if (m)any of you are decoding telemetry from
the CubeSats. If so, how are you doing it? I've tried using my FunCube with
a Virtual Audio Cable and AGWPE, and just can't seem to decode any packets.
The satellite I've tried so far is STRaND-1 and although there's a
noticeable trace on the waterfall, it's only a lighter color blue and not a
yellow, red, or white like I see from my TM-D700. As a matter of fact, I
can't decode that radio either. I don't expect it to be a redish color on
the WF since that would mead a really strong signal, but at this point I
think I have some sort of a configuration issue. Can anyone assist please?

Thanks,
Larry
N1MIW

------------------------------

Message: 16
Date: Fri, 22 Aug 2014 18:41:35 -0700
From: Brenton Salmi <kb1lqd@xxxxx.xxx>
To: B J <va6bmj@xxxxx.xxx>
Cc: amsat-bb <amsat-bb@xxxxx.xxx>
Subject: Re: [amsat-bb] SpaceX Test Vehicle Explodes
Message-ID:
<CA+7Uq1jZ2gdGsran3mtniA4XPiZdLw87MsjzbedkuszybLCOKw@xxxx.xxxxx.xxx>
Content-Type: text/plain; charset=UTF-8

F9R was a dedicated test vehicle for vertical takeoff vertical landing and
had many successes under its belt. It was pushed to extreme today to test
capabilities flying quite the mission!

Thanks for the link! Lots to be learned in the name of
advancing spaceflight!

Brent, KB1LQD

On Friday, August 22, 2014, B J <va6bmj@xxxxx.xxx> wrote:

> Sorry about the earlier empty post.  I was a bit fumble-fingered when
> I started writing .
>
> http://www.parabolicarc.com/2014/08/22/spacex-bad-day-mcgregor/
>
>
http://www.parabolicarc.com/2014/08/22/spacex-statement-mcgregor-rocket-explos
ion/
>
>
http://www.parabolicarc.com/2014/08/22/video-spacex-rocket-explosion-mcgregor/
>
> This reminds everyone that spaceflight is hard.
>
> 73s
>
> Bernhard VA6BMJ @ DO33FL
> _______________________________________________
> Sent via AMSAT-BB@xxxxx.xxx <javascript:;>. 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://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 member? Join now to support the amateur satellite program!
http://amsat.org/mailman/listinfo/amsat-bb

End of AMSAT-BB Digest, Vol 9, Issue 290
****************************************


Read previous mail | Read next mail


 11.05.2024 07:29:51lGo back Go up