Radio, railways, stuff...

M0RVB

ADS-B woes

I have been running an ADS-B decoder here for many years now and feeding flightradar24. However, yesterday I got an email alert that the decoder was offline. it seemed ok locally as the status said it was connected but it was no seeing any aircraft. This was last night but there were plenty of aircraft near enough. On further checking via the flightradar24 website it seemed the maximum distance seen was just 2 miles. One aircraft took off from the local airport and the decoder did see it, but only for a short while. So, off into the loft. I swapped the dbv dongle. No change. I took the preamp out of curcuit. No change. I installed the latest fr24feed. No change. Hmmm. Then it was time for bed... This morning I checked the collinear using the TinyVNA and it showed it was fine. I swapped the antenna lead that came with the dongle for an adapter type. No change! Back to the software then. I have not changed the setup for ages, in fact not since I migrated the decoder from a Pi to a Linux box. And it was always fine until now. Shutting fr24feed and dump1090-mutability down I tested the dongle via rtl_adsb. it saw lots of data. Ok... so the hardware is fine, the software is not. I ran dump1090-mutability --interactive and it showed many aircraft, so that's ok. But on running fr24feed it somehow knobbles dump1090 and sees no aircraft again. Next, I purged both fr24feed and dump1090-mutability and reinstalled each. Same thing, no aircraft. So I purged them again and purged lighttpd as well for good measure. And started from scratch. apt install lighttpd apt install dump1090-mutability - and select Yes to run at boot lightly-enable-mod dump1090 service lighttpd force-reload dpkg-reconfigure dump1090-mutability - and set the latitude and longitude and other options, mostly choosing the defaults Then I installed fr24feed from the .deb again and enabled it. Editing /etc/fr24feed.ini I changed this to use the beast local port - previously it just used dvbd: receiver="beast-tcp" host="127.0.0.1:30005" fr24key="..." bs="no" raw="no" mlat="yes" mlat-without-gps="yes" Then running fr24feed made it all work again. I am waiting for the stats on the flightradar24 status page to update but it is seeing aircraft out to 150 miles. The preamp is not yet back in circuit so that will get better. Why the software decided to fail is unknown. Note that it took a bit of searching to figure all of the above out, in particular information found at https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/12105-how-to-set-up-a-feeder-using-64-bit-ubuntu-linux-on-intel-platform/page4

Continue reading...
M0RVB

New SDR

The latest addition is a KiwiSDR (see http://kiwisdr.com for details). This comes basically as a black box which just plugs into an RF antenna, a GPS antenna (puck-type supplied), a 5V PSU (I purchased their recommended one) and an Ethernet port. It boots, acquires an IP via DHCP and announces itself to the world. And I mean that literally - well, ok it doesn't shout, but it does gain a proxy address which is accessible from the Internet, not just locally. The kit I have came from Martin Lynch who had them in stock and it arrived next day. The setup instructions (http://kiwisdr.com/quickstart/) are easy to follow. Of course, the very first thing to do is change the admin password. Other than that I configured it to use my own URL as well as the proxy they provide, setting the relevant rule in the broadband router to allow access to port 8073. I am still customising it and as yet the antenna connected is a YouLoop which fairs better when connected to the Airspy HF+ Discovery. I have a Cross Country Wireless loop to set up which should provide for a better reception across HF. The KiwiSDR works from 0 to 30MHz. As mentioned access is via a web browser and there are a number of options including different display modes as shown below. In additon there are extensions which provide for decoders, for example the following screenshot is a decode of the 60kHz time signal... ...and a decode of FT8 signals on 40m. With the decoders and given the always-on nature it is very handy locally to see if it is actually worth turning the transceivers on, especially given what the sun is up to these days! I can see this being a very useful addition here in the shack. As yet I have only scratched the surface of what the kit can do. Already someone has accessed it from the big wide world, ok, the UK and I have yet to advertise it. It does show on the map (https://rx.skywavelinux.com/) and the list of other receivers (http://kiwisdr.com/public/). otherwise, feel free, it can be accessed directly via http://m0rvb.net:8073/ - there will be a security warning as there is no SSL - something else to investigate. There is one issue I have noticed though. It takes a good few seconds between accessing the web page to displaying the information via Safari - it seems ok with the Duck browser. Brave will not connect, probably due to my configuration as it insists on only allowing https. After engaging the old grey matter I turned off Apple's private relay and the display is then instant.

Continue reading...
M0RVB

Opera

One of my interests, of which there are far too many for me to ever get anything done, is VLF. I regularly receive the broadcasts from SAQ and having a bit of time after the Christmas holidays and before having to get to grips with the garden ready for spring I downloaded Opera v1.6.5 by EA5HVK of VARA etc. fame. It can be found via https://rosmodem.wordpress.com/ I didn't (yet) find a lot of information but there has been a bit of chatter on the VLF email groups of late and the software basically needed very little setting up - however I am receive only yet so time will tell. Anyway, it installed under Wine on one of the Linux boxes and only offered me the internal soundcard for audio, which is what I needed anyway. The only antenna I have which is suitable for VLF reception is the YouLoop in the loft. This works well with the Airspy HF+ Discovery and SDR++ on the Mac for reception of SAQ and the plethora of 'interesting' signals down there. So I questioned that Opera would work if I simply piped the audio from SDR++ into the Linux PC - it works with wsjt-x and SSTV programs so why not? Now I must admit I had no idea if this would even work. Running Opera on the Linux box and setting it to 477kHz with SDR++ on the Mac set similarly to 477kHz, USB I waited. Fortunately someone fairly local started sending beacons. I noticed a trace of slow Morse... the mode Op8 takes 8 minutes to send the beacon and after this up popped the reception details! The screenshot above does not show the Morse trace so the one below is taken from another beacon reception. Nice. I will leave it running now to see what it picks up overnight. Given my usual modus operandi is to throw stuff together and read about it some weeks later (!) I have a least this time written some notes for myself. The software reports via pskreporter too.

Continue reading...