I was at a local hamfest looking for a cheap radio to sit on the workbench to work a few of the local repeaters - especially the ones where you want a little more power than a 5 watt handheld. Locating an Icom 3200A, I purchased it. 25 watts on 2 and 70, and as many as 8 memory channels!
Yes it’s a little on the “vintage” side but not much has exactly changed about FM Phone in 30 years…
Even if I had the space to put up an HF antenna where I live, the noise floor being a constant S9+20 would make actually using it quite difficult. But you can always drive out to a far away place, set up an antenna and get on the air…
The inverted-V dipole is a good choice for this - you need a pole, a balun and a lot of wire.
(more guy ropes will make it less bendy when the wind blows…)
It started when Mark Jessop sent me a message notifying me that there was a sonde down not far from where I work. The ill-fated RS41 launch RS_N3940146 reached an altitude of only 2083m before descending again. Unlike all the other sondes launched that day that ended up in far eastern Victoria this one came down comparatively close to the launch site.
An opportunity too good to pass up, I decided, after some encouragement from my colleagues, to “go out and get a coffee”. I grabbed my bike and went for a short ride to the landing zone. But a not so infrequent problem occurred…
The story starts much like any other chase. The landing location looks good, “only” 45km out of suburbia this time. We grab our stuff, get in the car and watch it ascend from the ground station while driving out to somewhere near the landing zone. We’re eager to catch it, hoping it will be our first recovery of a Melbourne-launched RS41 - up until quite recently they were still launching RS92 sondes.
This was only made a little more interesting by the fact that I was working on the receiver code to allow two concurrent instances to run - under the impression that I could always git stash in the event that I needed it running right now. Turns out that was wrong, as some un-committed local changes had been made - should have checked, but wasn’t on my machine…
That proved to be no problem as I got the feature working by the time the balloon was at about 17km altitude. The code change meant we could simultaneously run the vertical and the cross-dipole on two different rtl-sdr receivers at the same time. Mark Jessop initially suggested switching between them with a coaxial relay - however looking for a suitable candidate revealed that buying a second rtl-sdr was actually the cheaper option.
The descent was still relatively uneventful - aside from the prediction being fairly off as the weather was in the process of changing. The balloon burst and began to freefall - and thanks to the newly implemented feature, I could see exactly how much better the cross-dipole was at picking it up in this phase of flight. But something interesting happened next…
I recently purchased a Kogan 43” Smart TV (KALED43KU8000SZA), and I’m not entirely happy with it. Since the invention of the instant-on CRT in the 1960s, TVs have been able to switch on in mere seconds. Nearly 60 years on from that, I hit the power button, wait for Android to boot, and 30 seconds later, this:
It’s displaying input from my OSMC Vero 4k - and yes, then I have to use the menu controls to select the input, before it displays fullscreen - every time. It’s a small annoyance, but it’s a significant one - the TV has one job…
I wanted the “smart” features to play with, but it appears I’m being forced to. This just won’t do, so Michael Wheeler and I took a look and we fixed it. Read on to find out how.
The “normal” radiosondes are launched twice a day from capital city airports at the international standard of 45 minutes before 00Z and 12Z (midnight and noon UTC time).
However, on occasion we’ve received some interesting signals from sondes that appear to have been launched from the general area of a location in Broadmeadows - which a bit of judicious Google Street View stalking reveals to be BoM’s training facility.
These appeared to be a mixture of the old fashioned RS92s and the new, much more desirable RS41s. While RS41s are quite nice, further decoding of the RS92 signal revealed something even more interesting - it had an auxillary payload to measure ozone.
Noticing one launched early Monday afternoon (a surprise because we’d previously only seen launches from that facility on Wednesdays and Fridays), Michael Wheeler and I decided to attempt a retrieval mission. Due to work commitments, we couldn’t just drop everything and run, so we decided to head out after work and hope it was still sitting where it landed.
The signal was received down to about 1500m altitude - an encouragingly good result leaving us with a search radius of about 1km. The plan was to drive out there then drive around until we receive the signal, get GPS coordinates then find it.
We drove two hours out there, we received the signal but then there was one small problem.
I’m building a LTE to WiFi modem for the car. There are many existing devices to do this, including your mobile phone, so why build one?
I’d like something that can receive a better signal than a mobile phone - especially as our newfound hobby of radiosonde hunting takes us further afield even more than before. And most phones these days are no longer fitted with external antenna sockets. I’d also like it to be permanently fitted into the car, so it’s just “there”. Decent WiFi that extends out of the car would be a plus too.
Here are just a few of the commercially available options for doing this that I’ve collected over the years:
On the left we have the Huawei E585, one of the first such devices. On the right, the ZTE MF70. In the middle, from top to bottom, the Huawei E3872, the Netgear Aircard 785S and the Netgear AirCard AC790S. The E585, 785S and AC790S have internal batteries, and all except the E585 have external antenna sockets.
In this post, we’ll look at why I didn’t just use one of these devices (to be fair, the AC790S still gets a bit of use outside the car) and what hardware I’m planning to build my own with.
All was well, and performance seemed good. Until I decided to pull a large file from the server to my laptop. Despite being almost next to the 802.11ac access point, I was struggling to get even 5MB/sec. It appeared that the noise level on the WiFi channel was quite a bit higher than it should have been. Looking around with a SDR found what looked to be a wireless AV sender blanketing a wide chunk of spectrum in noise. Moving channel only increased performance to about 10Mbit/sec so I plugged into wired ethernet and tested with iperf.
Yeah, that’s not good. Further testing revealed it only affected traffic being switched from a 10Gbit to 1Gbit port.
Tried putting the “stable” and “latest beta” RouterOS on the CRS317, no change. Tried SwOS too in latest and older varieties - although I couldn’t get 2.3 to boot at all (known bug that crashes it on boot if you have any SFPs plugged in (!) but it seems worse than that for me).
I opened a thread on the Mikrotik forums, apparently it’s a “known problem”. I see that the patch notes mention a similar issue on the CRS326…
I’ve changed the network layout to route between two separate subnets, one for 10Gbit and one for 1Gbit. Performance is actually better - in the same configuration, about 950mbit throughput.
Hoping this is fixed soon, because until then I can’t really recommend the CRS317 on a “mixed” network.