Order Tray | Contact Us | Home | SIG Lists

[aprssig] Blue Horizon Balloon info

Steve Daniels steve at daniels270.eclipse.co.uk
Sun Mar 25 22:33:44 UTC 2012


That's great news Greg on the path switching, And for balloons like the
current one swapping from 144.390 to 144.800 after a certain longitude, that
would save the scramble to alert the Azores and Europe of the need to
monitor 144.390.

Of course 145.825 mid atlantic for a possible digi though the ISS would be
good also.

Will be updating my firmware tomorrow

 

Steve Daniels

G6UIM

Torbay Freecycle Moderator

  _____  

From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of Greg Clark
Sent: 25 March 2012 22:50
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Blue Horizon Balloon info

 


I do have altitude based path switching in the current release, but as far
as I know, no one has used it.

 

I have talked with some about longitude based frequency switching, and would
be willing to create some custom firmware that implements it.

 

Greg Clark

K7RKT

 

On Sun, Mar 25, 2012 at 2:32 PM, Steve Daniels
<steve at daniels270.eclipse.co.uk> wrote:


I would love Greg K7RKT whose tracker is in use (I have one) to include
altitude based path switching, as it's handy for retrieval to have a path
set to hit digi's when on the ground, and for transatlantic crossings
longitude based frequency switching.

Steve Daniels
G6UIM


-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
Of Bob Bruninga
Sent: 25 March 2012 22:06
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Blue Horizon Balloon info

Well,

Please pass back to the Blue Horizon team that I find their web page to be
pretty useless.  Maybe I am not seeing something bccause I have an old
browser, but there is no practical or educational information one would
expect to see.

Further, it is amazing that a group with such ambitions and background of
multiple balloon launches over several years would launch an APRS payload
that ignores nearly two decades of recommendations on how to configure an
APRS device for balloon operation.

Now I will be the first to admit, that mistakes happen, and believe me, I
have made them all...  but, otherwise, we need to get in touch with these
folks and ask them to put up a less fancy web page that focuses more on
substance.... one with more useful information.  And to use the proper
callsign and symbol for a balloon, and most importantly, to use an
appropriate APRS path at altitude.

Just some backseat kibitzing.

Bob, WB4APR

>   Yikes!  Looks like information is all over the
>   place.  My browser is not letting me get any useful
>   info from the  Blue Horizon site (or it just isn't
>   there).  All I heard last night on 30 M was "N2XE MT
>   MT"  and "N2XE ME MT" at random, but frequent
>   intervals.
>
>
>
>   I have been in email contact with John, N3XE and
>   here's what he says a few minutes ago, Steve, K9DCI:
>
>
>
>   Thanks for the note, we really need an updated
>   status for the balloon which is now somewhere over
>   the Atlantic Ocean.  The website is
>   www.projectbluehorizon.com and you can get a bunch
>   of info there as well as report and telemetry you
>   recieve.  The 30 meter beacon transimits at 10, 30
>   and 50 minutes after the hour on 10.1465 +/- 500 Hz
>   depending on the payload temperature.  If you could
>   copy the beacon we would be eternally greatful since
>   we are not getting it here in New York.  IF you
>   could spread the word, even better!
>
>
>
>   Yes the telemetry callsign is N2XE
>
>   The format is
>   Lat
>   Long
>   Altitude in meters (divided by 100)
>   Battery voltage (Divide by 10)
>
>
>
>   From John C. N2XE himself.  We ... from his
>   BlackBerry, that is. Typos and all.
>
>
>
>
>
>   - - - - - - - - - - - - - - - - - - - - - - - - - -
>   -
>
>   Other posts here include:
>
>   APRS on 144.39.
>
>   HF info: CW mode, transmitting morse code lat ,
>   long, altitude, battery voltage.
>
>   30m at 10.14658 05, 25, 45 minute of every hour.
>   40m at 7.10231 MHz  10, 30, 50 minute of every hour.
>
>
>
>   From twitter:
>
>   The 30m beacon reports on the 00, 20, 40 min every
>   hour, 40m beacon on the 10, 30, 50 every hour, 30m
>   has been easier to rx .
>
>       Apparently, the 30 meter schedule info published
>   at http://www.projectbluehorizon.com/#input was
>   incorrect at 5, 25, 45 minutes.  arghhhh, been
>   listening at wrong times.
>
>       Also hearing a non position beacon at odd
>   intervals on 30m.
>
>
>
>
>
>   Sent from my Knight-Kit Crystal Set.
>   --
>   73, Steve, K9DCI USN (Vet) MOT (Ret) Ham (Yet)
>________________
>_______________________________________________
>aprssig mailing list
>aprssig at tapr.org
>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig

_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20120325/374036ba/attachment.htm>


More information about the aprssig mailing list