Horus 55: Digital ATV Flight an outstanding success!

It is late and we are still processing telemetry and video streams but we thought we would post a quick note to say that Horus 55 was an absolute success. Stories are coming in from across the region from people who successfully watched the Amateur TV signal live over 80-90km away.

Reports also of the primary 434MHz 4FSK telemetry beacon being received 700km away in Melbourne plus the LoraWAN Things Network gateways over 560km away reporting packets from the experimental LoraWAN payload on 923MHz ISM.

We will post a long form story in the next day, but here is one of the amazing frame grabs from the TV transmitter just after burst. As the TV payload started to tumble it sent back this frame showing all of the telemetry transmitters and the parachute in one shot!

Finally here was the moment the chase and recovery crew picked up the payload.

Horus 55 Balloon Flight: D-ATV Launch Tracking & Live-Stream Details


The DVB-S high-altitude balloon launch (hopefully the first of many!) has now been locked in for 10AM ACDT Sunday the 7th of March (2330z Saturday 6th), from the Auburn Oval. The launch team is expected to arrive on site starting 9AM, and spectators are welcome!

Tracking of the flight will be available on the Habhub tracker or should be visible here on our website!

powered by Advanced iFrame

For those without D-ATV receiving equipment, AREG is going to attempt to stream the received ATV pictures via Hayden VK7HH’s HamRadioDX YouTube channel at the same time. You will find the link to the YouTube broadcast here:

Tracking Details – Primary Telemetry – 434.200 MHz

The primary tracking telemetry will be transmitted on 434.200 MHz using the Horus Binary 4FSK data mode. Amateurs in the Adelaide and Central SA region are also encouraged to get involved with the flight through receiving and uploading flight telemetry from our 70cm band tracking beacons. Every piece of telemetry data is valuable to the flight tracking and recovery teams so if you can help join the distributed receiver network to collect that data you will be making an important contribution to the project!

If you try receiving the telemetry from this flight, you’ll need a SSB-capable 70cm receiver (or a SDR), and the Horus-GUI telemetry decoder software. A brief guide on setting this up is available here: https://github.com/projecthorus/horusdemodlib/wiki/1.1-Horus-GUI-Reception-Guide-(Windows-Linux-OSX)

Note that you will need to use a ‘dial’ frequency of 434.199 MHz for the 4FSK signal to be centred in your receiver passband and hence be decodable.

Tracking Details – DVB-S Video – 445 MHz

If you want to get involved through receiving the D-ATV signal direct from the balloon on 445 MHz take a look at the How-To Guide being maintained by Mark VK5QI, available here: docs.google.com/D-ATV_Setup_Guide

The DVB-S transmission parameters are as follows:

  • Frequency: 445 MHz
  • Polarisation: Vertical
  • Mode: DVB-S
  • Symbol Rate: 1 Msps
  • FEC: 1/2

Project Horus Balloon Project: Digital ATV DVB-T Terrestrial Testing – Success!

Today Mark VK5QI took the Balloon ATV transmitter out for a terrestrial test. He carried out line-of-sight testing of the DVB-S payload from BlackTop Hill to the AREG remote site near Tarlee – a distance of 54km!

First test – could he see the signal on the SDR up at the site (RTLSDR, Diamond X-50, no preamp)… yes!

Next, Mark dumped some samples with rtl_sdr, then transferred them back to his laptop. He processed them through leandvb – and got video!!! A bit of fading, but for an omni receiver with no preamp, this is a pretty damn good result!

… and here’s some of the raw video

The MER as reported by leandvb was around 8-11 dB, right on the edge of what is decodable. Still, with such a basic system, a good result!

Based on the path, it is estimated to give us a working range of about 150km from the balloon given a receiving station with 15dBi gain and a good low noise preamplifier.

Stay tuned for more information on how to receive and decode the Digital ATV signal and save the date – we hope to launch the transmitter into the stratosphere on Sunday March 7th. (We also plan on streaming the event on Youtube).


For those who missed it late last year here is a bit more information about the Balloon ATV payload and some minimum signal testing that was carried out.

Reminder: AREG Meeting this Friday – D-ATV from a Balloon 30km up!

This is a reminder that this Friday’s AREG meeting will be held at the Fulham Community Centre, Phelps Court, Fulham. Doors open at 7.15pm Central summer time with the presentation planned to start at 7.45pm.

Our guest speaker will be Mark VK5QI. He will introduce you to the new Digital ATV payload and what you need to be able to receive and decode it. More information on the presentation is available (here).

Members who can’t attend in person will be able to access the meeting via Zoom (a link will be sent on the members mailing list on Thursday). Non members will be able to watch the Youtube Livestream thanks to Hayden VK7HH and his HamRadio DX channel.

The times are:

  • 7.45pm ACDT (SA)
  • 8.15pm AEDT (NSW, ACT, VIC, TAS)
  • 7.15pm AEST (Queensland)
  • 6.45pm ACST (NT)
  • 6.15pm AWST (WA)
  • 0915Hrs UTC

We hope to see you there!

Next Meeting: 19th February: Live ATV from 30km+ altitude! How to get involved?

Project Horus began in 2010 as the brain child of a group of radio Amateurs here in Adelaide. Now, 11 years later, one of the ideas that has been discussed many times within the group is finally going to be attempted. A flight is tentatively planned for Sunday March 7th that will carry aloft our first ever digital ATV transmitter.

Live ATV from 30km+ altitude!

Adelaide from 100,000ft – Horus 12

How can you get involved?

So that as many people as possible can participate or at least attempt to receive the ATV pictures, the next meeting of AREG on Friday February 19th will feature a presentation and Q&A session with Mark VK5QI. He will take you though everything you need to know about how to receive and decode the ATV signal.

What system are we using?

For the first launch, we are going to use the following transmitter settings:

  • Transmit Frequency: 445 MHz
  • Modulation: DVB-S, QPSK, r=½ FEC
  • Symbol Rate: 1Msps
  • Video Resolution: 704×400

This will produce fairly low quality video, but will give the best chance for the payload to be received. Once we understand what the achievable signal-to-noise ratio (SNR) is for a typical flight, the symbol rate (and image quality) can be increased on future launches.

Receiving DVB-S Signals – Hardware

The most ideal way to receive signals from this payload is with a dedicated DVB-S receiver like the Minitiouner Express ( https://www.datv-express.com/ ), however it’s also very possible to receive it with Software Defined Radio receiver setups, such as the ubiquitous RTLSDR devices. You will also need a 70cm antenna with some gain, and a low-noise pre-amplifier.

While some DVB-S set-top boxes may tune down to 445 MHz, the very low bit-rates that we will be transmitting from the payload will likely be incompatible with them.

Suggested Software-Defined Radio Receivers

There’s a huge range of SDRs available which are fit-for-purpose in this application, provided you put a low-noise-figure preamp in front of them – ideally one with band-pass filtering. Examples include:

Mark testing the ATV receive across the bench

More detailed instructions and information will be posted to our website in coming days. Stay tuned!


Meeting Details

The main meeting will be held at the clubrooms, 1 Phelps Court, Fulham at the Fulham Community Centre. Doors will open from 7.15pm (ACDT) with proceedings starting at 7.45pm (ACDT) (0915z). For those unable to attend in person, we will have online options available too!

The meeting on February 19th will also be live streamed on YouTube thanks again to Hayden VK7HH and his HamRadioDX Channel.

For members unable to attend in meeting hall in person, there will be a members only Zoom channel available as well.

Links to these will be posted closer to the date!

Project Horus: Test flight towards VK3 – SUCCESS!

UPDATE: Flight a success! 

Thanks to all that helped track the flight today! The tiny payload travelled over 550km from the launch site in Adelaide, to land near a piggery just outside Bendigo. Hopefully it gets recovered soon!
RS41 PowerSave Test Flight PAth
I recorded the following callsigns decoding telemetry:
AXB2035 (SWL), VK3AGD, VK3BQ, VK3EEK, VK3GP, VK3JED, VK3KZM, VK3NCC, VK3OF, VK3OHM, VK3TPM, VK3TWC, VK3WRE, VK3ZPF, VK5DJ, VK5EI, VK5HS, VK5IS, VK5KX, VK5LJG, VK5MAS, VK5MCA, VK5NTM, VK5PE, VK5QI, VK5RK, VK5ST, VK5TRM
… also a special mention to N0CALL, who received 154 packets.
RS41 PowerSave Test Flight
Thanks to all that setup the decoding software – one of the aims of this flight was to get more people setup to decode telemetry from these payloads, and get feedback from users to help improve it. There are a few groups in Melbourne that are planning on using the same kind of telemetry, so more listeners in VK3 able to decode will make their flights even safer.
73 and cheers,
Mark VK5QI

Tomorrow at ~9AM ACDT VK5QI is going to launch a lightweight (<40g) balloon with a 70cm 4FSK transmitter onboard. This is a test of some software updates to the 4FSK transmitter payload (a reprogrammed RS41) to improve the battery life. There will be ~30 second gaps between telemetry transmissions, with short ‘pips’ every 5 seconds so you know you are on the right frequency!

The transmit frequency is still subject to change but will most likely be 434.200 MHz. (Note that this is different to our usual Horus 4FSK frequency of 434.660 MHz – this is because there are a few 70cm repeaters in Melbourne with inputs near this range).

With a bit of luck this one should make it into VK3, and reach an altitude of ~23km or so. This should make it receivable from western Victoria, and likely from Melbourne too.

If you want to have a go receiving the telemetry from this flight, you’ll need a SSB-capable 70cm receiver (or a SDR), and my horus-GUI telemetry decoder software ( https://github.com/projecthorus/horus-gui ).

A brief guide on setting this up is available here: https://github.com/projecthorus/horusdemodlib/wiki/1.1-Horus-GUI-Reception-Guide-(Windows-Linux-OSX)

Note that this flight is going to head east *very* quickly, and may go out of range of Adelaide receivers during the flight. If you know anyone in VK3 who might be able to receive this please forward on this information!

Tracking of the flight is available via the following link: https://tracker.sondehub.org/?sondehub=1#!mt=osm&mz=8&qm=6_hours&mc=-35.40036,140.03814&f=HORUSBINARY&q=HORUSBINARY

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