Amateur Radio

svxlink status

Well, I’ve been meaning to get around to fixing up svxlink in Gentoo for a long time now. For those who don’t know, svxlink is a client and server for the EchoLink amateur radio linking system.

We had to stop releasing the Qtel client, as it relied on Qt3 which we no longer ship in Gentoo.  On top of this, the ebuild installed non-Gentoo init scripts, fails to build with gcc-4.6 and fails due to underlinking.  (My thanks go to Diego for pointing these flaws out.)

At the moment I’m working on the first problem, which is that the builds that were in-tree are crusty and old.  svxlink did release version 11.05 not long back, and ohh yes, they’ve changed their versioning scheme too to match Ubuntu.  However, their trunk branch is still dependent on Qt3 if you want Qtel.  There is an experimental Qt4 branch, which is what I’ve been working with.

One irritation I had was trying to make it possible to install the client component or the server component.  svxlink has its own, very custom, build system based on recursive makefiles.  (Yes, I know, considered harmful and all that.)  The build system first builds the core libraries, then it starts looking at Qtel and svxlink’s server components.  The first thing was to try and split these up.

The new ebuilds will introduce a svxlink-libs package.  This is relatively straightforward, and it just builds & installs the libasync, libechlib and liblocationinfo libraries.  The catch is when building qtel and svxlink, the build system looks for the built binaries inside the source tree.

I have submitted a patch upstream that remedies this.  Eventually I’ll look at how we can fix some of the other flaws in the build system.  So far I’m still battling svxlink itself, but I soon will have svxlink-libs and qtel packages available for testing in the Portage tree.  svxlink itself will also need to wait until I can set up a test node on simplex somewhere… my O2 looks like a likely possibility.

I’ll keep you all informed as this progresses.  Qtel appears to be working (although I’m battling some funnies with the sound device on the Apple MacBook)… just a matter of fixing some issues with the build system for svxlink and I should be able to have svxlink back in the tree once again.

PSA: Omni WEP-910D

If you live in Australia, do not purchase or operate this headset.

This is what the offending article looks like:This headset radiates a carrier on the 2m amateur band.  Specifically around 147.000MHz.  In some parts of the world, the 2m amateur band extends from 144.000MHz to 146.000MHz.  Here in Australia however, it goes all the way up to 148MHz, meaning these headsets are effectively pirate stations smack bang in the middle of the FM portion of the 2m band.  They are probably quite legal in the country where they were originally sold, but they are not legal here.

There are a lot of repeaters that operate around 147MHz, particularly in Brisbane.  VK4RBN at Mt. Glorious is one of the most heavily used repeaters in Brisbane, and so you can guarantee there are people listening on that frequency that will hear your transmissions, and will likely complain.  We’re also getting good at direction finding.

So far the importers have gotten little more than a slap over the wrist for the illegal C-tick approval of these devices.  I think the ACMA need to grow some teeth here if we expect to get on top of this problem.  The last offenders were lucky, they got the choice of stopping the use of the headset, or copping a $400 fine … the article was not confiscated.  The importers got a $1500 fine… nowhere near enough, and the devices continue to be sold by distributors.

The end user may not have been technical enough to understand what was going on, but the importers almost certainly should have if they were slapping C-ticks on equipment.

More information:

Things I learned at the horse endurance rides at Donnybrook

  1. The BP servo on the way to Donnybrook is bad when it comes to caravans… the one heading back to Brisbane is even worse.
  2. Horses have an aversion to orange and red coloured clothing (pity the organisers handed out red caps and orange shirts… also good thing we’re not the SES).
  3. Do not shine a torch in the eyes of a horse, especially not a 3W LED torch!
  4. Be prepared for organisers to give you information at the last possible minute, and not consider the needs of the radio communications people.
  5. Sometimes a short-cut, isn’t.

World IPv6 Day

Well… has anyone noticed anything different about the ‘net?

stuartl@atomos ~ $ host www.google.com.au
www.google.com.au is an alias for www.google.com.
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 74.125.237.52
www.l.google.com has address 74.125.237.48
www.l.google.com has address 74.125.237.49
www.l.google.com has address 74.125.237.50
www.l.google.com has address 74.125.237.51
www.l.google.com has IPv6 address 2404:6800:4006:802::1011

I knew World IPv6 day was coming up, but it seems it snuck up on me and I barely noticed. Likely a testament to the fact we run a dual-stack network here, and so everything magically Just Worked™ as it should. Indeed, a lot of websites are now dual-stack, as is much of the gentoo.org infrastructure, Google (as seen above), FaceBook, and numerous other sites.

Sadly, a lot of ISPs here in Australia did the demented ostrich act when it came to IPv6. I wonder how many technical support calls they received, with users complaining about websites being slow to load up or failing to connect.

iTel, formerly “Global Info-Links”, now calling themselves “South East Community Telco“… were one of the masses that drove their RFC791-only heads in the sand and pretended that the entire Internet can be compressed into 32-bits of address space. We’ve been waiting to hear back from them on their plans for addressing since January as we’d like to upgrade the 512/128kbps ADSL link we use here. (Anyone noticed this site tends to load up a bit slow? That 128kbps figure is the reason why.)

We’ve been with this ISP since 1996. That’s quite a long innings… We’ve stayed put because until now we’ve been happy with the service. 512kbps was quite fast when we upgraded from 56kbps PSTN dialup (14.4kbps dialup when we first started… still have that modem too!). These days it plods along, but the 128kbps uplink is a notable thorn in my side with my telecommuting. So we’re looking at ADSL2+.

However, there’s one hitch. iTel is only a fairly small ISP. At the moment they do the noble thing of providing static public addresses on IPv4 for all fixed-broadband customers, but how long will that last? The last thing I want, is to sign up a contract for 12 months, then find out that in 6 months they need to move us behind CGN (Carrier grade NAT) to squeeze in some more customers. That won’t fly for us. I’d ideally like to ditch the 6-in-4 tunnel I have with AARNet and go native, or at the very least, swap it with one terminated at the ISP, but that doesn’t seem to be happening anytime soon.

At the moment there is only one ISP I know of that offers any sort of IPv6 connectivity. Internode. Kudos to them for taking the pioneering step! I’m seriously looking in their direction. I’m also hoping the NBN that we keep hearing about, is IPv6 enabled… and I’m holding out with the hope that our little suburb might soon be getting the long strands of glass laid down our street. If it’s only another year or so, it may be worth just hanging on with ADSL1 until then.

Thankfully, we do have the 6-in-4 tunnel through AARNet (and my greatest gratitude to them for providing it). There is a growing community on this newer protocol… I’m also happy to report absolutely 0 spam via IPv6… any spam or malware thus far has been via IPv4 … although I know this won’t last. The good news there is that with one unique address per computer (instead of per customer, or worse, per 100+ customers), it should be easier to track down the guilty party causing such Internet shenanigans. CGN by comparison is likely to be a spammer’s playground.

What am I doing about IPv6 deployment? Aside from my small-time tinkering with the network here… any socket programming I do today is at the very least dual-stack. One of my hobby projects is a digital mode stack for amateur radio… if I get my way it’ll be IPv6-only when used on a computer network.

One of my work projects involves interfacing some proprietary software to some power meters using RS-232 and RS-485 to Ethernet bridging devices. Even though the devices themselves are IPv4 only (and will be for the foreseeable future), I’m designing the software to handle IPv6. Doing this, future proofs the software. Surprisingly, I’m finding it easier to just design for dual-stack than it is to develop a IPv4-only application. If you’re building an application today, dual-stack IMHO must be part of the strategy if the application is going to work beyond this decade.

Some have asked about IPv6 on packet… sadly AX.25 packet does not go anywhere near fast enough to make IPv6 (or indeed, IPv4) networking a viable option on packet radio using existing TNCs… however I think IPv6 will, and should, play a much bigger part in amateur radio communications than it presently does… we can’t expect to hold on to the 44.0.0.0/8 subnet for much longer.

To the ISPs that are lagging behind, I say get moving! IPv4 is older than I am! This is especially true of the smaller ISPs… if you don’t move, you will get squeezed out of the future Internet connection market as address space gets consumed. To the nay-sayers who keep telling us that something else will replace IPv4, to you I say get moving… you haven’t got long to invent this magical silver bullet, in fact I say you’ve left it too late.

Do’s and Don’ts of hand-held radios

During the International Rally of Queensland, it was interesting to observe how people made use of the radios provided for the event. In fact, watching peoples’ behaviour to me, made it clear that none of them had any training in how to use one of these devices. And they all struggled, mostly as a result of each others’ bad habits.

This isn’t an isolated case… my mother who works at the Brisbane International airport, often complains about the radio etiquette of her fellow colleagues. A lot of people have a radio thrust into their hands, and haven’t a clue how to use them. In trying to figure it out, they often fall trap to the same bad habits.

I myself have found a lot of this by mistake, and by observing others. A lot of this is also applicable to using regular telephones … I found the tip of standing still when talking helpful when I needed to make a call to emergency services on my mobile phone — the particular spot where I was at the time, the phone would drop out if I moved more than 6 inches in any direction. Learning not to talk too close, or too loudly into a microphone, also helps.

The following is a little chart I came up with. No, the stick figures are not XKCD grade, they’re not meant to be. Click on the image below for a copy as a PDF, or get the SVG source here.  File is provided in the public domain, but attribution would be appreciated.  If you use radios in your workplace, and observe this kind of behaviour in your colleagues, you might like to print this out and stick it on a wall somewhere.

 

Experiments with AX.25

This weekend just gone I was at Imbil helping out with the International Rally of Queensland, reporting scores for the car rally there.  This was my first look at packet radio in action.  Prior to this I had enabled the amateur radio options in the kernels I built, but never tried actually hooking radio to computer.  I shall be posting some notes on how I got this working…

zhouman ~ # uname -a
Linux zhouman 2.6.35.7-lm2f-nb #2 Wed Oct 13 00:42:58 EST 2010 mips64 ICT Loongson-2 V0.3 FPU V0.1 lemote-yeeloong-2f-8.9inches GNU/Linux
zhouman ~ # ifconfig sm0
sm0 Link encap:AMPR AX.25 HWaddr VK4MSL
inet addr:172.31.32.1 Bcast:172.31.32.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:256 Metric:1
RX packets:365 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:24236 (23.6 KiB) TX bytes:6850 (6.6 KiB)

zhouman ~ # mheard
Callsign Port Packets Last Heard
VK4EA-9 sm0 6 Mon May 16 17:59:12
VK4NRL-9 sm0 1 Mon May 16 17:58:40
VK4VP-1 sm0 8 Mon May 16 17:58:38
VK4RAI-3 sm0 9 Mon May 16 17:57:58
VK4TIM-9 sm0 14 Mon May 16 17:57:56
VK4TDI-1 sm0 2 Mon May 16 17:57:39
VK4DC-1 sm0 15 Mon May 16 17:57:07
VK4TEC-9 sm0 120 Mon May 16 17:56:08
VK4FY-1 sm0 18 Mon May 16 17:54:38
VK4RMO-3 sm0 1 Mon May 16 17:54:33
VK4RGC-3 sm0 3 Mon May 16 17:52:48
VK4RC-1 sm0 8 Mon May 16 17:51:29
VK4FIL-1 sm0 4 Mon May 16 17:46:44
VK4RIL-13 sm0 4 Mon May 16 17:45:43
VK4RBR-3 sm0 5 Mon May 16 17:42:59
VK2RDO-3 sm0 2 Mon May 16 17:41:19
VK4RRC-13 sm0 3 Mon May 16 17:36:39
VK2JUB-1 sm0 2 Mon May 16 17:34:44
VK4BNQ-1 sm0 1 Mon May 16 17:26:58
VK4LDA-9 sm0 2 Mon May 16 17:24:59
VK2POO-9 sm0 9 Mon May 16 17:21:24
VK2XFL-9 sm0 1 Mon May 16 17:21:09
VK4RSR-3 sm0 1 Mon May 16 17:20:04
VK4IE sm0 1 Mon May 16 17:15:04
VK4ALJ-3 sm0 1 Mon May 16 17:15:00
VK4HPW-9 sm0 5 Mon May 16 17:13:23
zhouman ~ #

Set-up consisted of:
Linux kernel on Lemote Yeeloong, latest soundmodem driver, Yaesu FT-897D, homebrew interface cable plugged into Yeeloong’s onboard sound card, USB serial driving BC547 in interface cable for PTT.

zhouman ~ # cat /etc/ax25/soundmodem.conf
<?xml version="1.0"?>
<modem>
<configuration name="FT897-D">
<chaccess txdelay="150" slottime="100" ppersist="40" fulldup="0" txtail="10"/>
<audio type="alsa" device="plughw:0,0" halfdup="0" capturechannelmode="Mono"/>
<ptt file="/dev/ttyUSB0"/>
<channel name="Channel 0">
<mod mode="afsk" bps="1200" f0="1200" f1="2200" diffenc="1"/>
<demod mode="afsk" bps="1200" f0="1200" f1="2200" diffdec="1"/>
<pkt mode="MKISS" ifname="sm0" hwaddr="VK4MSL" ip="172.31.32.1" netmask="255.255.255.0" broadcast="172.31.32.255"/>
</channel>
</configuration>
</modem>
zhouman ~ #

I’ve shut it down for now, but I’ll give it a bit more work on 145.175MHz tomorrow. Once I get something working, I might set something up using the O2 or one of the Fulongs (probably the latter) and see about getting soundmodem back into Gentoo.

Update: After hand-editing the ebuild to enable APRS support, I can successfully report that not only is soundmodem working, but so is Xastir on my Yeeloong, as can be seen on aprs.fi.

VK4MSL/BM: Stationary test on 15m

Well, this afternoon I decided to fix a couple of problems with the bicycle mobile… firstly, the mounting of one noisy headlamp.  I’ve re-done the mount using a more solid piece of plastic this time, so we shall see how it goes.  No noise on HF so things are looking up there.  I also fixed the headset connection which was causing speakers to drop out… the problem turned out to be in the headset connection on the bike, rather than in the helmet.

It was approaching 2PM and thus nearly time for the daily Travellers net on 21.185MHz USB.  I’ve never made a contact on 15m before, but knew the antenna did tune up there, so I gave it a shot.  Ross VK5KMH popped up with a 58 signal out of Adelaide listening… after a prolonged silence, I decided to throw a call out.  Ross responded, reporting my signal into his station was also a 58 signal.

This was from the driveway at my home location, using 100W transmit power (not far from where I reached VK100WIA on 20m with a CB whip).  So evidently this home brew whip works quite well on 15m.  I have since brought the FT-897D inside and plugged it into my G5RV-like antenna, and after moving off frequency to tune, I notice Ross is still a 58 signal, so evidently my HF antenna doesn’t do much better than the whip does.

VK4MSL/BM: HF contact on 80m

Well, the antenna I tuned up in my last post, I can say, while it doesn’t work that great on 80m, it did get a contact into Victoria this evening on the AWNOI net.  Terry VK2TEZ near Coffs Harbour gave me a 4-3 signal report, so still lots of room for improvement… part of that was due to static crashes from storms in NSW, but I think with a better tuned antenna, we should be able to get towards having a workable antenna.  At the moment the autotransformer I use has ~95 turns, with output taps at 0, 25, 50 and 75 turns.  I think one somewhere between 0 and 25, and/or some extra turns might help… so I might wind a new one and see where that gets us.

The headlight still continues to give me grief.  An interesting discovery though this evening.  Since the battery is no good, I’ve permanently mounted it to the bicycle frame.  This was achieved by removing the plastic bracket which is used to mount the headlight on the handlebars or on the helmet mount (using a rubber O-ring), and replacing this with a bracket bent out of a short piece of aluminium.  It fastens to the bicycle frame at the front right above the front wheel, using a bolt hole normally used for mounting rim brakes (my bike has disc brakes).

The upshot is that the headlight’s casing has a pretty good electrical connection to the bicycle frame.  Turns out this is a big no no with these lights.  Kiss goodbye HF if you do… you’ll get crap everywhere from 400kHz right up into the VHF.  I’ll have to do some further investigation, but I found that if I insulated the case from the frame, it helped on the 400kHz and HF emissions.  I think something parasitic is causing the 2m grief as this continues (that, or it’s less critical on the case being earthed).

For a while I thought it might’ve been something lurking around 415kHz… the standard IF frequency of most superhetrodyne receivers, but alas, can’t see anything there.  Otherwise it’d explain why it appears to be everywhere.  I definitely suspect it’s not supposed to be oscillating there though, so I think parasitic oscillations are the cause here.  I’m slowly researching my own power supply for the LED in this headlamp, so its days are numbered.

The insulation was achieved by breaking a cheap plastic picnic knife, drilling a couple of mounting holes, and mounting the headlight on that.  That quelled the HF interference quite a bit, and I was able to listen to the HF bands on my way into Brisbane.  At least it was nice to listen to something other than that sodding wedding in the UK.  (C’mon fellas, yes, great and all but can’t we just confine it to one station?)

I was concerned about the longevity of this arrangement however.  And as it turned out, I was right to be concerned.  It broke as I approached the Normanby Fiveways.  I went over a bump, heard a crack, and noticed the headlight dangling by the power lead.  I pulled over, threw it in the basket and grabbed the backup headlight.  At least there was one on the helmet, a 1W LED, so I still complied with local laws for night riding.  I didn’t have a mounting for the backup light, I just pointed it forward sitting in the bottom of the front basket, with it on flash as a warning to drivers.

Once at the destination, I reverted the headlight back to being directly mounted on the bicycle frame.  Interference was intermittent, but when it was acting up, it did wipe out 80m with S6 noise.  Not good when most stations are barely making S6 as it is.  I wound up turning off the main headlamp as for the most part I could see where I was going, and I knew the route.  As I got out of town this was less of an issue due to the lack of traffic, and of course I was on bicycle paths or the footpath for 90% of it.  That at least allowed me to hear what was going on with the net.

The other flaw I had was that the helmet’s speaker connections were acting up… wound up unplugging the earpiece side of the headset adaptor and using the internal speaker.  Thankfully I could still use the helmet’s microphone and the rest of the wiring harness… just not the speakers in the helmet.  I noticed this as I pulled out of my street, in fact I was aware there was a problem, but now I know where the problem is now.  I’ll get onto it tomorrow.  And I’ll look at a better way to mount this headlamp in an insulated fashion as an interim solution to a power supply replacement.

A headlight to avoid

If you ever decide to put any kind of sensitive receiver on a bicycle, you’ll want to avoid this ugly duckling of the bicycle lighting world:

Nitelights Illuminator 900

Nitelights Illuminator 900

These lights are great from the illumination point of view, and they’re not badly priced either.  However, from an EMC viewpoint, they stink.  I was given one as a present some time ago.  The first night I got it, I mounted it on the helmet, charged up its battery, then went to work the next day.  That evening, tried using the radio on the bicycle as I rode home.  The interference rendered the radio totally useless.

At first I couldn’t figure out why the signals sounded so bad on receive.  I was stuggling to hear repeaters that were normally quite strong.  The only thing that was new was the headlight.  I got home, switched on the set in my room and tuned to 2m sideband, then put the headlight on flash.  The tell-tale static from the radio gave away the headlight as being the culprit.  Worst of all, the emissions weren’t conducted, they were radiated.

Since then I’ve spent the last few months trying to figure out ways to make this headlight less noisy.  The following page serves as a notepad, and I’ll keep adding to this as time goes on.

Initially when I used it I kept the battery in my shirt pocket.  This proved to be a fatal mistake, since the roughly ¼? power cable proved to be a very effective radiator of this interference.  I found winding the power lead up into a tight coil and moving the battery to the top of the helmet right behind the headlight helped things a bit.  Adding a 2.2mF capacitor in parallel to the headlight further reduced emissions to make it barely tollerable.

Then the battery pack died.  After a few weeks of non-usage, the cells collapsed.  So for a while the problem solved itself, I could no longer use the headlight.  The headlight’s battery pack runs at a nominal 7.2V (typical 8V).  Since I run a 12V supply on the bicycle, I set about making a step-down power supply that could drop my 12V supply down to 8V approximate to run the headlight.

Initially I tried using a LM7808 linear reg.  This worked, with one major drawback: the linear reg got bloody hot.  Turns out this headlight draws about 1A of current when at full brightness.  That means in order to drop 4V, the reg was dissipating 4W of power.  Ooops!  Poor thing.

I designed a crude switchmode power supply to do the work.  Using a voltage divider to provide a voltage reference, I used a LM311 comparator to detect when we were under voltage.  The output signal from this would pull down on the gate of a IRF9540N MOSFET which acted as the main switch.  Hysteresis was used to fine-tune the switching behaviour.  Capacitors at both sides would smooth the waveform.  470µF was used on the input side, 330µF on the output (we still have that 2.2mF capacitor not far away).  I also made liberal use of 100nF decoupling capacitors to try and control the rate of switching.

On the breadboard with a dummy load, my circuit performed pretty well.  A fairly smooth output with a bit of ripple at high load.  I mounted it in a box and tested it with the headlight, and presto, the headlight was back in service.  I mounted both on the bicycle directly, so as to minimise cable length and therefore radiation.

Since now the radio shared a power rail with the light, I knew there was potential for conducted emissions to cause problems as well as radiated.  The next evening I tried it out… 2m was lousy with the headlight turned on.  The good news is that it wasn’t much worse than before, but it still rendered the radio useless at times, particularly if the signal was weak from the repeater.

Recently, I added some 470µH inductors in series with the headlight and my switchmode power supply.  I also tried common-mode chokes to no avail.  A 1mF capacitor has been added in parallel to the 470µF capacitor in my power supply to further try and reduce the noise.

Low-pass filtering on headlight

Low-pass filtering on headlight: 2.2mF capacitor in parallel, 470µH inductor in series

Part of the problem was that I was shooting blind to try and find the interference.  Today, whilst tuning up the HF antenna, I decided to experiment and see what bands this headlight had an influence on.  To my (unpleasant) surprise, interference was severe right down to 80m.  I used the spectrum analyser built into the FT-897D to hunt for the culprit, and found it lurking at around 400kHz.  When the power supply initially starts up, it’ll be up around there, then it sinks down to 392kHz as the case warms up:

Noise from the headlamp detected around 400kHz

Noise from the headlamp detected around 400kHz

This appears to be the fundamental frequency for the switchmode power supply built into the headlamp.  It would appear to have a fairly sharp square-wave type pulse, as it contains very strong odd-order harmonics.  The same interference can be observed at around 1260kHz (3rd harmonic).

The fact that this frequency is so low, probably suggests it is being intermodulated with a parasitic oscillation at some higher frequency.  This I have not yet found, the CRO showed some other hash over the signal, but I will need to do some further investigation, probably with a more sophisticated spectrum analyser than the primitive one found in my transceiver.

I’d be interested to hear from others who have had issues with these headlamps.  In particular, interference to AM/FM radio reception or transceiver operation would be quite useful if the need to persue this with the ACMA ever comes up.  The manufacturer of the headlights has so far been unresponsive to my queries, so in the meantime I can only recommend that people avoid using these headlights if they intend to use any kind of radio receiver whilst riding at night.

In the meantime, I’ll be chucking further notes here as I find more on this issue.

VK4MSL/BM: New HF antenna

Well, I figured I better post up pics and notes on the improved antenna design for my HF bicycle mobile station.  I spent some time tuning it up today, and without resorting to the autotuner, I’ve successfully managed to tune up all bands available to me from 40m through to 6m.  80m still remains ellusive however.

The new design incorporates a version of the autotransformer used in the earlier attempt, using more turns of wire on the same size former, and multiple output tap points.  This allows me to accomodate a very wide turns ratio to match the antenna to various bands.

VK4MSL/BM HF: The autotransformer

VK4MSL/BM HF: The autotransformer

 

Band Test Frequency Primary turns Secondary turns Approximate SWR Comments
80m 3.590MHz 1 90 Too high to measure This seems to get the strongest signals. Autotuner is able to tune from here.
40m 7.120MHz 26 48 ~2:1 +/- a turn on the secondary to cover the entire 40m band.
20m 14.210MHz 26 1 ~1.2:1
15m 21.200MHz 26 27 ~1.4:1 Slightly out, there is probably a better one.
10m 29.200MHz 26 27 ~1.1:1
6m 53.000MHz 26 52 ~1.2:1 +/- a turn on the secondary, able to hit VK4RBX with 10W from the driveway

 

On the top of the autotransformer are for selecting the secondary tap; one of 0 turns, 25 turns, 50 turns or 75 turns (caveat; I might be slightly out with my counts here).  Having done this I think in hindsight I’d have been better off moving the 0t one down to maybe 10t instead, as there aren’t too many bands that seem to work on the 0t setting.  The primary side is selected by means of a wire soldered on to a thumbtac.  The wire wraps around the tube with a piece of balsa wood for the pin to stick into.  You select the turn by piercing the insulation as you push the thumbtac through the wire and into the balsa wood behind.  Crude, but it works.

VK4MSL/BM HF: Primary tap

VK4MSL/BM HF: Primary tap

In place of the CB whip, I have taken a fibreglass whip and cut it down, stripped the winding, and used it as a support with a base-load spring to take any shock loads.  In place of the original antenna winding, is two sections of brass tubing which telescope out.  This allows for an antenna that can be partially dismantled and reassembled on the run, unlike the other antenna which was permanently fixed at 6′ length.

VK4MSL/BM HF: Mark II

VK4MSL/BM HF: Mark II

I have a third solid section I can insert in there too, which would further extend the antenna to 2.5m, but it becomes very top heavy when I do this.  The antenna can extend to 1.6m length, or for portable use I can throw a wire up into a tree, or support it using a squid pole and connect that wire to the autotransformer output taps.

I didn’t make any contacts while tuning the thing up, although I was hearing New Zealand on 20m quite strongly, and on 10m I could hear the VK8 (Northern Territory) beacon going quite well.  I tried a few calls on 28.390MHz, but had no contacts.

 

I’ve also re-inforced the antenna bracket.  Prior to doing this the antenna would sway wildly from side to side.  Yes, it meant the cars gave me a wide birth (something I greatly appreciate) but I fear had adverse affects on the signal, and probably was asking for trouble in the long run.  Putting a brace between the two brackets seems to steady things up just a little bit, and now I can rock the bike side-to-side quite violently without the antenna swinging too far.

I’m yet to go mobile with the new improved station.  Weather permitting, I shall give it a try Monday evening.  I have a meeting with Brisbane area WICEN.  Due to headlight QRM I may or may not be active while mobile, we’ll give it a shot, but I should be able to work portable once I get there.