Project Horus #53 Launch Announcement – 10AM Sunday 25th August

UPDATE: Launch was a complete success! A full write-up will be coming in due course…

The next Project Horus launch is currently planned to fly on Sunday the 25th of August(weather permitting), with a planned launch time of 10AM. As usual, there’s always the chance the weather for the planned launch date may not be suitable, so if necessary, the backup launch date will be Sunday the 1st of September.

The launch site will be the usual Mt Barker High School Oval. Launch crews should be on-site around 9AM. If you haven’t attended one of our launches before, this is a great opportunity to come along and see what’s involved first-hand!

WiFi Pineapple Payload

WiFi Pineapple

This flight will be the first of hopefully many more payloads proposed and developed by AREG club members under the Project Horus Member Payload Launch Program. Derek VK5TCP’s payload is a WiFi Pineapple board – a WiFi penetration testing device developed by Hak5. The payload will be ‘war-ballooning‘ throughout the flight, recording the SSID of all WiFi access points it can receive signals from. It will also be broadcasting an open WiFi access point (‘VK5ARG’) on the 2.4 GHz band. The payload will be using a ~11 dBi patch antenna pointed directly downwards.

To encourage community participation in this launch, there are two challenges associated with this payload:

  1. Get your Access Point SSID observed by the payload! – Set up a WiFi Access point connected to a high gain antenna pointed at the payload. After the flight we will publish a list of all SSID’s that were observed, and at what altitude they were spotted. For your best chance at being observed, beacon using the lower-speed 802.11b mode.
  2. Recover the secret message! – Connect to the access point on the balloon while it is in flight and retrieve a secret message from a web server running on the payload. This will be a serious challenge to achieve, and will require the use of high-gain antennas on the ground. Our link budgeting suggests that the full 4W of allowable LIPD Class License EIRP will be required to connect to the payload. Amateur radio operators with an advanced license are permitted to use any power level up to the limits of their license conditions. The web server will be running on the IP address 172.16.42.1, and clients can either accept a DHCP lease, or use a static IP address between 172.16.42.150 and 172.16.42.200.

To have the highest chance of success, stations will need to be situated directly underneath the flight path, with antennas pointing upwards to the payload. A map of the predicted flight path will be posted closer to the launch date.

Wenet Imagery Payloads

Image received via the Wenet Payload

This flight will also fly a ‘Wenet’ high-speed imagery payload, as have been flown on many previous Horus launches. The centre frequencies for this transmission will be 441.200 MHz. This payload will be downlinking HD pictures throughout the flight, which will be available at this link:

http://ssdv.habhub.org/

Reception of the Wenet signal requires a RTLSDR and a Linux PC/Laptop. Instructions on how to set up the required software are available here.

 

Telemetry Payloads

As always, we’ll be flying the usual assortment of telemetry payloads, including:

  • Our usual 100 baud 7N2 RTTY telemetry on 434.650 MHz USB. This can be decoded using dl-fldigi, with a reception guide available here. Recent testing of dl-fldigi’s decode performance has found that the auto-configured RTTY receive bandwidth is too narrow, and can detrimentally impact decode performance (by up to 3dB!).To fix this, open dl-fldigi, and in the Configure menu, select Modems, and then go to the ‘RTTY’ tab. Drag the ‘Receive filter bandwidth’ slider to 200, then click ‘Save’. Note that this setting will be reset whenever you hit the ‘Auto-Configure’ button!
  • 4FSK Telemetry decoder

    The new 4FSK Binary telemetry will be transmitting on 434.660 MHz USB. This uses a separate decoder, with setup instructions for this available here. This telemetry payload will soon become the primary method of tracking the flight – the RTTY payload is expected to be retired in a few launches time.

 

Tracking of the flight will be available on the HabHub Tracker, available at this link. (Note that other balloon launches will also be visible on this page, including the Bureau of Meteorology launches from Adelaide Airport).
Follow the #horus53 hashtag on Twitter for updates from the launch and chase teams on the launch day.
Stay tuned for updates closer to the launch date…
73
Mark VK5QI

Automatic Radiosonde Reception – AREG Style!

Thanks to Mark VK5QI, AREG is pleased to announce a new service has been added to the VK5RWN Repeater site. Mark has been developing a RadioSonde automated receive system which allows all of the Bureau of Meteorology weather balloon data to be collected and be made available on the internet. The data is available via the SondeHub instance of the HabHub High Altitude Balloon Habitat platform. You can access it here:

What can you see? Where all the active weather balloons are right now!

If you’re located in South Australia and are considering going out to recover a sonde, or have recovered one, please use the Facebook Group or the mailing list to announce your intentions! This helps avoid disappointment if others are intending to recover the same sonde.

Want to learn more? Read on…..


For quite a while now I’ve been interested in tracking and recovering radiosondes. These are meteorological instruments regularly launched by weather balloon from many locations around the world. Here in South Australia the Bureau of Meteorology launches them from Adelaide Airport twice daily (2315 and 1115Z), along with a few other locations around the state.

A Vaisala RS41 radiosonde found with the help of the radiosonde_auto_rx tracking network!

Radiosondes transmit in the 400-403 MHz band (usually on either 400.5/401.5/402.5 MHz), and there is a range of software, both closed and open source available to decode their telemetry. Not being entirely happy with the existing offerings, I started work on my own software, which became radiosonde_auto_rx (or ‘auto_rx’ for short).

auto_rx runs on a Raspberry Pi (or any other Linux machine) and automatically scans for and decodes radiosonde signals. Telemetry is uploaded to APRS-IS and the Habhub tracker for mapping purposes, and can also be viewed locally via a web interface. Most of the common radiosonde models are supported, including the Vaisala RS41 which is launched here in Adelaide. There are currently 147 auto_rx stations in operation worldwide (16 here in VK5), and so far (as of 2019-05-25 10Z) 19415 individual radiosondes have been logged.

So why do I bother doing this? Many radiosondes are (in part..) highly recyclable! The Vaisala RS41 contains a good quality GPS receiver, a micro-controller, and a radio transmitter – perfect for re-programming for use as a high-altitude balloon payload, as we have been doing on many recent Project Horus flights. In fact, the RS41 is the ‘reference platform’ for the new high-performance balloon telemetry system developed by David Rowe and I.

Chasing and recovering radiosondes is also great practice for Project Horus launches, with a few of the new Horus regulars starting out tracking radiosondes, and many others around VK5 regularly out chasing the BOM’s radiosonde launches. We use the same mapping software for both radiosonde and Horus chases.

To help improve tracking coverage, I proposed to install an auto_rx receiver station at one of AREG’s premier repeater sites, overlooking the Adelaide plains. Thanks to the generosity of AREG members in approving this proposal, the receiver was installed over the easter break. A big thanks to Ben VK5BB for assistance in fabricating an antenna bracket, and helping with the installation!

Hardware Details

The auto_rx receiver station installed in a rack at the site.

The auto_rx receiver hardware consists of a Raspberry Pi 3, with two RTLSDR v3 dongles attached, allowing simultaneous reception of 2 sondes. The incoming RF from the antenna is filtered through an interdigital filter (passband 400-403 MHz, stop-band attenuation > 90 dB) before being going through a preamplifier and splitter to the two dongles. The estimated system noise figure is about 5dB, mostly from the insertion loss of the filter. Given this is a very RF-noisy site (co-located DSTAR repeaters, and many commercial services on a tower a few hundred metres away), the higher noise figure is an acceptable tradeoff – without the filter the receivers would immediately overload!

All the equipment is mounted within a 2RU rack-mount chassis, with all power and network inputs heavily filtered to avoid coupling in unwanted RF. The total power draw of the unit is ~10W.

View from the antenna!

The antenna is an AEA co-linear (kindly donated to the project by Ivan VK5HS) mounted to the side of the repeater hut. Being ~450m above sea level, the antenna has direct line-of-sight to the Adelaide airport, and essentially anywhere to the west of Adelaide.

Receiver Performance

Receiving a radiosonde on the ground at Adelaide Airport

With such excellent line-of-sight, the station regularly receives signals from the Adelaide Airport radiosondes before they launch, and often even during the ground-test and calibration activities performed on the radiosonde within the Bureau of Meteorology building at the airport.

Also often visible are radiosonde launches from the Ceduna and Woomera receiving stations, which typically rise above the horizon when they reach ~10km altitude. Coverage to the east is not quite as good, being blocked by the Adelaide Hills, however radiosondes are regularly tracked down to ~1 degree elevation.

Would you like to know more?

  • More information on the radiosonde reception software is available on github at https://github.com/projecthorus/radiosonde_auto_rx .
  • A conference presentation delivered by myself and Michael Wheeler (VK3FUR) where we discuss the re-use of the Vaisala RS41 radiosondes is also available (see below)
  • You can track radiosondes launched from Adelaide Airport (and many other launch sites around the globe!) by visiting the Habitat Tracker at this link.

Thanks again to all those who helped make this possible!

73 Mark VK5QI

 

Horus 52 – On track for Saturday 9th Feb Launch

AREG is once again involved with the University of South Australia’s Southern Hemisphere Space Studies Program this year, which is run by UniSA on behalf of the International Space University. The launch, which was scrubbed last week due to the predicted landing zone is now planned for this coming Saturday 9th Feburary, with liftoff planned for ~11AM. The weather is looking much better!

The current predictions look as follows:

Payload Plans

While some details are still to be worked out, it’s looking like the following payloads will be flying:

  • RTTY – 434.650 MHz
  • 4FSK – 434.640 MHz
  • Wenet – 441.200 MHz  (downward facing images)
  • Wenet #2 – 443.5 MHz (horizon-facing images)

There is still a chance the second Wenet payload will be dropped from the launch due to weight restrictions, so if you don’t see any signal on 443.5 MHz, that’s what’s happened!

As always, amateurs from across the state are encouraged to take part, by collecting the telemetry data and relaying it to HabHub on the Internet. This data is used to help fill in any missing data the chase teams fail to capture, which they can use to help maximize their landing zone prediction accuracy. In that way, everyone taking part is adding to the success of the mission.

Tracking details will be provided closer to the launch. Keep watching the AREG website for details!

 

UniSA: Southern Hemisphere Space Studies Program – Horus 52 – POSTPONED TO 9th FEB

AREG will be launching a high-altitude balloon for the International Space University’s South Hemisphere Space Studies program, conducted by the University of South Australia again this year. The planned launch date is Saturday the 2nd of February, with liftoff around 10-10:30AM. The launch site will be the usual Mt Barker High School Oval location.

UPDATE 2019-01-31: Due to poor launch-day weather, this launch has been re-scheduled to 11AM on Saturday the 9th of February.

Payload Plans

While some details are still to be worked out, it’s looking like the following payloads will be flying:

  • RTTY – 434.650 MHz
  • 4FSK – 434.640 MHz
  • Wenet – 441.200 MHz  (downward facing images)

There may be a second Wenet payload on 443.5 MHz capturing outward-facing imagery, though this is yet to be confirmed.

As always, amateurs from across the state are encouraged to take part, by collecting the telemetry data and relaying it to HabHub on the Internet. This data is used to help fill in any missing data the chase teams fail to capture, which they can use to help maximize their landing zone prediction accuracy. In that way, everyone taking part is adding to the success of the mission.

WENET PAYLOAD NEWS

There have been some updates made to the Wenet HD imaging payload and receiver software, however all changes are backwards compatible. If you have a functioning Wenet receiver system, you *do not need to update for this launch*.

However, if you’re a bit more adventurous, the latest updates are on Github here: https://github.com/projecthorus/wenet

You will likely need to wipe your existing Wenet directory and follow the setup instructions from the start.

Stay tuned for further updates as we get closer towards the launch date…

73  Mark VK5QI

AREG 20th Anniversary – Horus 50 Flight Report

Introduction

The Amateur Radio Experimenters Group was formed in July 1998 with the aim of promoting experimentation and self learning using Amateur Radio. 20 years on, the group is a vibrant and active body that has brought together people from many walks of life, all with the common interest of experimenting and learning about radio and electronics.

One of the founding project ideas conceived by Adrian VK5ZBR, Ben VK5BB and Rod VK5UDX that drove the creation of AREG was project “Skyhook“. The aim, back then, was to fly an amateur radio payload under a weather balloon. For various reasons that goal was never achieved. However, through Project Horus (which joined AREG several years ago under the then stewardship of Terry VK5VZI), that original dream became a reality.

The view from Horus 50 – River Murray in the foreground with Adelaide in the top left of shot

This flight marks Project Horus’s own milestone, having now launched 50 “heavy – 30km plus” balloons over 8 years. In that time it has become one of the most active amateur high altitude balloon projects in Australia.

To commemorate both the 50th flight and the 20th anniversary, AREG and Project Horus have decided to fly an all Amateur Radio oriented payload, promoting our core experimentation theme. The aim was to maximise involvement of the amateur radio community in the project. Here is the story of that flight.


Horus 50 – Launch Preparations

The launch crew arrived on site at Mt Barker High School by 8.30am ready to prepare the payloads and the balloon. Mark VK5QI who was flight lead was assisted by a number of AREG members including Will VK5AHV, Andrew VK5AKH, Theo VK5IR (first time Horus hunter), Kim VK5FJ, Marcus VK5WTF, Oly VK5XDX, John VK5BJE and Grant VK5GR with a number of other visitors and members who came along to watch as well. Assembly of the balloon train went to plan and, with relatively calm conditions prevailing, the filling of the balloon went smoothly too.

Liftoff

After the obligatory calls to Air Traffic Control, the team was set and the balloon took to the skies on schedule at 10.00am ACDT.

Ground Tracking & Control Stations

In support of the flight, another AREG team had set up camp approximately 50km away at Bear Rock Lookout, up above Palmer on the eastern edge of the Mt Lofty ranges. Manned by Peter VK5KX and Matthew VK5ZM, this ground station provides a vital backup telemetry link, gathering all of the signals from all of the payloads and uplinking them to the internet for the chase teams to use.

This data, when mixed with the rest of the information being received by amateurs across the state, is used by the chase teams to help fill in any packets they miss from the balloon, improving the accuracy of their landing predictions and providing a safeguard for the landing positioning data.

Meanwhile the second ground team, consisting of Grant VK5GR and Oly VK5XDX, went to the top of the ranges above Brukunga to establish VK5ARG net control for this flight’s voice repeater. We weren’t able to collocate these teams as the UHF high power up-link would have overwhelmed the tracking data down-links.

The Chase Teams

Once the balloon took off, the Mt Barker based chase teams packed up the launch site and prepared to head out. Meanwhile Darin VK5IX also started the chase, in his case also from the Bear Rock lookout. There were a few new chase teams this time which was great to see! The teams were:

  • Mark VK5QI: Mark VK5QI, Will VK5AHV, Theo VK5MTM (his first Horus chase)
  • Liam VK5LJG: (Just Liam, his first Horus launch, though not his first balloon chase)
  • Kim VK5FJ: (Just Kim in the car)
  • Marcus VK5WTF: Marcus and family
  • Darin VK5IX: Darin, Glenys, Cam, Greg.

It was great to see more people getting out chasing!

 

Tracking and Telemetry Data Processing

There were many ways to track the flight. The usual balloon telemetry collection site was in full swing at habhub.org where all four payloads were being tracked. Amateur Radio operators and the general public could also track this flight via the Amateur Position Reporting System (APRS) on websites like aprs.fi

APRS Tracking from aprs.fi

habhub.org tracking and telemety hub

The other very important aspect of the flights is the data collected by the distributed listener network of amateur radio enthusiasts spread across the state. This adds a huge level of reliability and redundancy to the system that the project team really appreciates. It also gives everyone an opportunity to contribute to the project, even if only from their own radio shacks.

The interest in this flight was very high and there were many first time listeners as well as many regulars tune in and gather the telemetry off one of the RTTY or 4FSK payloads, as well as through the APRS Internet Gateway network.

In all of these a special mention goes to Andrew VK3BQ who takes the prize for the most distant telemetry decoding station at over 600km away in Melbourne.

Here are the results of how much telemetry each station was able to contribute (Note – This is per-callsign used when uploading, so some stations may have duplicate entries):

100 Baud RTTY Beacon 434.650

CallsignPackets Received% of Flight Received
VK5NG85076.2%
VK5ZRL84575.7%
VK5AKK78270.1%
VK5EU77769.6%
VK5KX-264157.4%
VK5APR42738.3%
VK5DJ40836.6%
VK5ALX32829.4%
VK5KX-0232128.8%
VK5ST17415.6%
VK5KX-816214.5%
VK5KX-0813912.5%
VK5DMC13311.9%
vk5st736.5%
VK5NEX373.3%
VK5KIK322.9%
VK5QI-9292.6%
VK3BQ191.7%

4FSK Binary Beacon 434.640

CallsignPackets Received% of Flight Received
VK5QI-9169388.2%
VK5KJP166686.8%
VK5WTF123964.6%
VK5NEX119362.2%
VK5LJG-9117661.3%
VK5ST-9105655.0%
VK5LJG88946.3%
VK5FJ-987745.7%
VK5TRM84243.9%
VK5DSP62732.7%
VK5FAAP32416.9%
VK5ST623.2%

A huge thank you to everyone who collected the telemetry!

This telemetry stream also allows us to analyse the path the balloon took and to confirm the flight’s vital statistics:

Not all plain sailing for the telemetry

The flight was not without it’s gremlins either. The 4FSK binary telemetry payload, which was a recovered Vaisala RS41 Radiosonde that has been re-programmed for use on 70cm, lost PLL lock at 13km on descent, and regained it at 9km altitude (about 6 minutes later). The air temperature at 13km was <-60 degrees C according to the morning BOM radiosonde launch, and -40 degrees C at 9km. The team suspects that the payload froze for a period due to it running lower power than it would for a normal sonde launch, thus not generating enough internal heat to keep from freezing. It is hoped to test this out sometime in the towards the end of the month with a small test launch carrying the same payload but running 3dB more TX power along side another RS41 PCB in a custom foam box (similar to our RTTY payload boxes).

The LoRa tele-command payload also had a fault where it lost GPS lock for the second half of the flight just after burst, likely due to it getting knocked around due to the huge dynamic shock that ripples through the payloads when the balloon bursts. This time, the GPS unit took 20 minutes to regain lock, probably because it was falling so fast (~20-60m/s). The team will be investigating some better AA battery holders, and possibly putting a big capacitor across the power input to hold up the GPS through that very dynamic part of the flight.

It goes to show, every flight is an experiment and that the team learns something new every flight!

Payloads – Slow Scan TV

The main attractions of this flight, of course, was the flying voice repeater and the first flight of the Slow Scan TV transmitter.

The live pictures broadcast over Slow Scan TV were a spectacular success, with amateurs across VK5 and VK3 able to receive them using all manner of tools and systems. The SSTV signal, running 250mW used what is known as Scottie 2 format (commonly used on HF).  For the first time these images were accessible to almost everyone without any special software (which the previous high definition Wenet SSDV picture system does require). This helped generated an unprecedented interest in the flight.

We had clubs and individuals from the Riverland, South Coast, across Adelaide, and in one case from as far away as Melbourne all receiving the SSTV transmitter.

Rick Kearsley (from the South Coast ARC) received SSTV images from Horus 50 from Normanville SA with  by VK5LEX/P and VK5VCR/P.

This slideshow requires JavaScript.

In the Riverland, Peter VK5PE and Ivan VK5HS joined in the fun.

AREG also received copies of the pictures received by Steve VK5SFA and Liam VK5LJG and know of several others in Adelaide who also successfully received the images live from the balloon (including our primary ground station at VK5KX/P, who received one only 500ft off the ground).

Last SSTV Image before landing captured by VK5KX

The best effort award however must go to Alan, VK3DXE who from the eastern side of Melbourne was able to receive the SSTV transmitter at apogee using his EME station. Not a bad effort for a 250mW FM transmission on 145.1MHz at over 630km range.

VK3DXE Receiving Horus 50 SSTV from Melbourne over 600km away

This slideshow requires JavaScript.

This was the array Alan was using.

Photo thanks to VK3DXE

From the balloon’s perspective we also kept a copy of the images on the SD card. This is what they looked like prior to broadcast.

This slideshow requires JavaScript.

Payloads – Voice Repeater

The other amateur radio related payload flown was a cross band voice repeater. This machine had a receiver on 438.900MHz (with a 123Hz CTCSS tone) and a transmitter on 147.500MHz running approximately 1 Watt. This was a return to the original voice repeater flown back on Horus 9 and 23 after the problems with narrow band FM on the more recent repeater flights.

During the flight, it became clear that this old machine still had some problems. Unfortunately the faults didn’t reveal themselves until after lift off. The repeater was de-sensitising its own receiver (a suspected 3rd harmonic problem), and with the rather windy flight aloft, there was also a lot of swinging around of the antennas (TV Ribbon J-Pole antennas) which made contact very difficult to achieve through the balloon. None the less, 32 contacts were logged through the repeater by stations from as far as Millicent in the SE, Renmark in the NE and Whyalla / Port Pirie in the Iron Triangle to the NW.

Contact Map (created using tools.adventureradio.de/analyzer/)

The following is the full log of the contacts made through the balloon with net control.

VK5ARG Log

CallQSO_Begin_DateQSO_Begin_TimeFreqModeQTH
VK5QI2018-11-032338Z147.5FMGlenelg
VK5GR2018-11-032338Z147.5FM
VK5PET2018-11-032339Z147.5FMStrathalbyn
VK5XB2018-11-032341Z147.5FM
VK5IR2018-11-032341Z147.5FMMansfield Park
VK5BJE2018-11-032341Z147.5FMMaurice
VK5WTF2018-11-032344Z147.5FMMunno Para
VK5APR2018-11-032345Z147.5FMFlinders Park
VK5KX2018-11-032345Z147.5FMSalisbury Park
VK5ZM/P2018-11-032346Z147.5FM
VK5ZAR2018-11-032347Z147.5FMBroadview
VK5BB2018-11-032351Z147.5FMRedwood Park
VK5IX2018-11-032352Z147.5FMFreeling
VK5YX2018-11-032356Z147.5FMHallett Cove
VK5PE2018-11-040013Z147.5FMRenmark
VK5DJ2018-11-040014Z147.5FMMillicent
VK5HS2018-11-040015Z147.5FMRenmark
VK5ST2018-11-040019Z147.5FMAngaston
VK5ZRK2018-11-040020Z147.5FMRidgehaven
VK5DMC2018-11-040023Z147.5FMPort Pirie
VK5ALX2018-11-040024Z147.5FMWhyalla Playford
VK5XB2018-11-040029Z147.5FM
VK5SFA2018-11-040053Z147.5FMWoodforde
VK5AKK2018-11-040100Z147.5FMCrafers
VK5WU2018-11-040108Z147.5FMHope Valley
VK5TEC2018-11-040115Z147.5FM
VK5HS2018-11-040118Z147.5FMRenmark
VK5CV/MOB2018-11-040120Z147.5FM
VK5EU2018-11-040122Z147.5FMHilton
VK5KBJ2018-11-040126Z147.5FMAldinga Beach
VK5ZM/P2018-11-040128Z147.5FM
VK5JP2018-11-040142Z147.5FMNorth Haven

Payload Recovery

As sure as the laws of gravity go, what goes up must come down! The balloon climbed to over 35km before bursting and returning to earth. The following are the vital statistics of this flight:

MetricResult
Flight Designation:Horus 50 - AREG 20th Birthday
Launch Date:2018-10-03 23:14 UTC
Landing Date:2018-10-04 01:59 UTC
Flight Duration:2 Hours 45 Minutes
Launch Site:-35.07568, 138.85701
Landing Site:-35.184284, 139.755216
Distance Traveled:82.6 km
Maximum Altitude:35,861 m

The chase teams themselves were in an excellent position to recover the payloads and indeed watched them land from about 1km away. After contacting the land owner (to seek permission to enter and collect them), all of the payloads were successfully recovered, ready to fly another day.

Recovery Team – L-R VK5IR, VK5LJG, Greg, Cam, VK5WTF, VK5IX, VK5AHV, VK5QI

Conclusion

At the end of the day the team was very happy with the results. What was even better were the number of people who participated in the event, either on site or from home with tracking, SSTV, FM voice, or just tuning in on social media and following along via the Internet. It truly represents the aims of AREG in promoting experimentation in Amateur Radio to see all of the people who joined in. To each and everyone of you, thank you for your participating!

To the teams that built and flew the balloon, a special thank you to you as well. May there be many more!

73 de Grant VK5GR

UPDATE: Horus 50 High Altitude Balloon Flight this SUNDAY!

Preparations continue for the Horus 50 high altitude balloon flight celebrating the 20th Anniversary of AREG. This radio experimenters flight is planned for launch this Sunday, the 4th of November at 10am CDST (2330Z). The latest flight path prediction is shown below. Full details of the flight can be found (here)

UPDATE: 3rd November 2018 – Predictions still looking good!

Tracking will be available via habhub.org

As a quick reference, the flight will have the following transmitters:

  • 147.500MHz Downlink / 438.900MHz Uplink (with 123Hz CTCSS) Repeater
  • 145.100MHz Slow Scan TV Downlink
  • 145.175MHz APRS Tracking Beacon
  • 434.650MHz 100baud RTTY Telemetry
  • 434.640MHz 4FSK Binary Telemetry (uses the latest FreeDV software to decode)

Stay tuned for more details and refer to the main news story (herefor information on how you can participate in this event!

AREG’s 20th Anniversary Event – Horus 50 Balloon Launch – 4th November 2018

2018 marks 20 years since the Amateur Radio Experimenters Group was formed. To celebrate this milestone, the club is planning to fly a special Amateur Radio focused high altitude balloon in what will be the 50th Project Horus Mission.

The Project Horus team itself is also celebrating 8 years in the air! Project Horus was founded by Terry Baume and continues to perform regular high-altitude balloon launches from locations around South Australia under the auspices of the Amateur Radio Experimenters Group.

When will this be happening? Currently it is planned to fly on Sunday the 4th of November (weather permitting). Liftoff is planned for 10AM ACDT. We are going for altitude so coverage will hopefully extend as far as Melbourne at the peak of the flight.

The goal is to engage with amateur radio in as many ways as possible. We want you to talk through the balloon, see the world from the balloon’s perspective and know where the balloon is during the flight! How can you do all this you might ask? The Project Horus team have specifically tailored this flight to include:

  • a 2m (down) / 70cm (up) Cross-band FM repeater. Amateurs within the repeater footprint will be able to make live QSOs with the club station VK5ARG and each other via the FM repeater using relatively modest stations.
  • a 2m SSTV beacon transmitting images from the balloon live during the flight. You will be able to see the world from the balloon’s perspective using a 2m receiver and simple software (you can even use an app on your phone).
  • Track the balloon via a 2m APRS beacon during the flight!

The launch site will be the usual Mt Barker High School Oval. Launch crews should be on-site around 8:30-9AM. If you haven’t attended one of our launches before, this is a great opportunity to come along and see what’s involved first-hand!

As usual, there’s always the chance the weather for the planned launch date may not be suitable, so a backup launch date of Sunday the 18th of November has been tentatively penciled in (the 11th being the AHARS buy & sell weekend).

Cross-band FM Repeater

Likely suspects operating the cross-band repeater on Horus 23

The cross-band repeater will be using the following frequencies:

  • Uplink: 438.900 MHz, with a 123 Hz CTCSS tone required for activation.
  • Downlink: 147.500 MHz  (~1.4W output power).

To transmit to the balloon at the maximum range of 700km (once the balloon reaches >30km) you will need approximately 10-30W and an 10dBi gain antenna and a clear takeoff towards the balloon. Those stations closer to the launch site will be able to get away with much less.

PLEASE MAKE SURE YOU can hear the repeater before transmitting
and remember to make sure you SET YOUR CTCSS TO 123Hz
or you will not access the repeater.

As with previous flights, the repeater will be run as a controlled net. Listen for VK5ARG acting as net control and please follow their instructions so that as many people as possible can share the repeater.

FM-SSTV Imagery Payload

Instead of the usual Wenet imagery payload this launch will have a new SSTV transmitter operating on 145.100 MHz FM. It will run approximately 250mW transmit power. The transmitter will have 30 second gaps between image transmissions to avoid overheating the transmitter.

Scottie 2 SSTV Imagery Example

The payload will be transmitting images using the Scottie 2 SSTV mode throughout the flight, and can be decoded using any SSTV software capable of decoding this mode (pretty much all of them!). This is a mode that typically is used on HF but is equally adapted to VHF FM work. (Note it is not the same as the PD120 transmissions from ISS).

Examples of suitable software you can use to decode the SSTV pictures include:

Any FM receiver (including handhelds) should be capable of receiving this payload, though as with the cross-band repeater, a Yagi antenna may be necessary for reliable reception at the edges of the transmitter footprint.

If you do receive images, please post them to Social Media and on Twitter include the #horus50 hashtag so everyone can see them!

Telemetry Payloads

As always, we’ll be flying the usual assortment of telemetry payloads, including:

  • Our usual 100 baud 7N2 RTTY telemetry on 434.650 MHz USB. This can be decoded using dl-fldigi, with a reception guide available hereNOTE: There is a known issue with dl-fldigi where it does not upload any received telemetry until about 10 minutes after the software is started. Any telemetry received in this time period will be queued and uploaded after the startup period has completed (i.e. no telemetry will be lost).
  • 4FSK Telemetry decoder

    The new 4FSK Binary telemetry will be transmitting on 434.640 MHz USB. This uses a separate decoder, with setup instructions for this available here. (Previous listeners note that there have been updates to the software – please re-download the latest version!). We would love reports of how the 4FSK signal compares to standard RTTY!

  • If weight permits, there will be an APRS beacon operating on 145.175 MHz with the callsign VK5ARG-12. This will be received automatically by the APRS network.
Tracking of the flight will be available on the HabHub Tracker, available at this link. (Note that other balloon launches will also be visible on this page, including the Bureau of Meteorology launches from Adelaide Airport).
Follow the #horus50 hashtag on Twitter for updates from the launch and chase teams on the launch day.
Stay tuned for updates closer to the launch date…
73
Mark VK5QI

Horus 49 – Anstey in Space v2.0 – Success!

On Sunday the 8th July, the Tea Tree Gully Library’s echidna mascot, Anstey, rose into the sky to an altitude of 36,374 metres under a High-Altitude Balloon. This was Anstey’s second flight into the stratosphere, and Project Horus’s 49th balloon launch.

Originally planned for the 30th of June, Horus 49 had to be delayed a week due to very poor weather conditions. Even still, this flight was a a long one for the chase teams! Fortunately we had the assistance of a team from the Riverland Radio Club who mobilized from their home base (much closer to the LZ) and who then played a big part in tracking and retrieving Anstey at the end of his flight. You can read about their adventure on the RRC Blog.

Launch Activities

As usual, the launch was from the Mt Barker High School oval – thanks must go to the school for allow us to use their oval for so many launches! A good number of AREG club members came along to help out with the launch. Also present at the launch were members of Anstey’s Space Club, there to watch the launch and see Anstey off into the stratosphere!

Filling the balloon.

Payloads were laid out, turned on and tested, and the balloon was filled with somewhat more gas than usual. The flight path predictions had a possible risk of landing close to Loxton, so additional gas was used to give a higher ascent rate (as it turned out, a *very* high ascent rate). Wind gusts made filling the balloon a bit of a challenge, but there were no lack of hands to help keep things from getting out of control.

At just after 10AM, the wind died down and we had a perfect launch!

Launch of Horus 49

The Flight

On board Anstey had two cameras recording things. The first was a GoPro miniature video camera! The second was a still camera that was sending photos live to ground as the flight progressed.

Chase & Recovery

Right after the launch, Mark VK5QI and Will VK5AHV quickly headed off towards the expected landing area to the South-West of Loxton – a long drive away! Marcus VK5WTF and partner were also following not far behind.

The ascent rate ended up being much higher than intended – ascent rates as high as 9m/s were observed at some points in the flight, resulting in a shorter than expected flight. Even still, the Hwoyee 1600g balloon used made it to a very respectable 36374 metres altitude before bursting.

With the original flight path prediction due to land near Loxton, it was looking pretty unlikely that the chase teams departing from Mt Barker would make it there before landing. Luckily, a group of Riverland Radio Club members were on the case! Ivan VK5HS, Peter VK5PE, Danny VK5DW and Andy VK5LA also headed out to chase, starting from the Loxton area. Rob VK5TRM was also out for the chase. Ivan & co had been practicing by hunting the Bureau of Meteorology radiosondes, so were well experienced in chasing balloons – so much so that they were able to get into position to watch the balloon land in an area of scrubland near the locality of Mantung (40km SW of Loxton).

Mark and Will were not far behind, arriving at the landing site a few minutes later. A short walk later and Anstey was sighted… about 8 metres up a gum tree!

With some persuasion from a SpiderBeam pole, Anstey was recovered. Many thanks to all those who came along for the chase!

Horus 49 Recovery Team

Live Wenet Imagery

Throughout the flight Anstey was imaged via a version of Project Horus’s ‘Wenet’ imagery payload, which transmits images down to the ground via a 115kbps 70cm transmitter. As expected the images of Anstey were amazing, and were viewable live via HabHub’s SSDV webpage.

This live imagery is only possible through volunteers running ground-stations. Thanks go to VK5APR, VK5EU, and VK5KX who ran stationary receivers. Mark VK5QI was also running a mobile Wenet receiver in his chase car.

CallsignPackets ReceivedTotal Data Received (MB)
VK5KX23846058.22
VK5QI (Mobile)21801253.23
VK5APR21304552.01
VK5EU15317537.40

Telemetry – RTTY & Horus Binary

As with all previous Project Hours flights, a RTTY payload was flown. Many listeners contributed to tracking this payload:

CallsignPackets HeardPercentage of Flight HeardPayload Alt at First RX (metres)Payload Alt at Last RX (metres)
VK5EI103393.4%3962695
VK5EU101792.0%7012780
VK5FAAP98288.8%16373203
VK5FJGM73966.8%11229329
VK5FLJG62656.6%22117751
VK5KX95586.3%1680193
VK5NEX91282.5%26335108
VK5ST83375.3%28783897
VK5ZAR79371.7%12055551

New to this flight was an experimental ‘Horus Binary’ payload, which was transmitting a MFSK telemetry mode developed by David Rowe VK5DGR and Mark Jessop VK5QI. This new mode has significant performance advantages over RTTY, and will hopefully become the new default telemetry system for Project Horus flights. David VK5DGR also has an overview of the payload and how it performed on the flight on his blog. Many stations were able to run the new decoding software and track the flight using this mode:

CallsignPackets HeardPercentage of Flight HeardPayload Alt at First RX (metres)Payload Alt at Last RX (metres)
VK5AKH/KX/ZM (Portable)151182.4%6970101
VK5APR154184.0%26314850
VK5FJGM123467.3%76925875
VK5FLJG157786.0%6755217
VK5FTAZ83245.4%91466484
VK5IX149181.3%818661
VK5KJP147180.2%27484404
VK5RR28815.7%33826400
VK5ST166390.7%24351286
VK5TRM171993.7%1854139
VK5QI (Mobile)156085.1%34364
VK5WTF (Mobile)103956.7%2776139

The new mode provides position updates twice as fast as the 100 baud RTTY payload, and with 6dB better decoding performance (meaning double the range!). The update rate may have been too fast it seems – while about 2600 packets were transmitted during the flight (confirmed as received on VK5QI’s mobile station), only ~1800 of these made it into the Habitat tracking database! This is likely a result of upload timeouts – some changes will be made to the software prior to the next Horus Binary flight so this issue can be further debugged. Still, the new mode performed incredibly well in the chase cars, providing  rapid and regular updates to the chase car mapping systems.

Thanks again to all who helped track the flight using both Wenet, RTTY, and the new modem. Expect the Horus Binary mode to make appearances on more flights in the future!

Upcoming Launches

To give more listeners an opportunity to decode the new Horus Binary mode (and to use up some leftover gas from Horus 49!), a small balloon launch will take place sometime in Late July. This will be a ‘small’ balloon launch (as per the CASR Part 101.E definition), flying a re-purposed RS41 radiosonde clocking in at just over 40 grams. A new version of the Horus Binary decoder will be released prior to this launch to allow better analysis of the upload issue encountered on Horus 49.

Also coming up is the 20th anniversary of AREG – as part of the celebrations, we will be performing Project Horus’s 50th launch! On this flight we expect to fly:

  • A 2m/70cm Cross-Band repeater, similar to what was flown at the WIA AGM launch.
  • A SSTV transmitter, sending images in the PD120 SSTV mode.
  • An APRS beacon (depending on weight budget)

.. along with the usual telemetry and cutdown payloads. Stay tuned!