Amateur Radio – Page 16 – Kev's Development Toolbox

August 10, 2016

Windows 10 Anniversary Update – not as smooth as it could have been

There’s been a lot of stories in the news the past few days since the Windows 10 Anniversary Update went live of people running into issues with unexpected hangs and blue screen crashes after the update (for example). Even the update itself does not seem to be as smooth as it could have been.

On my HP desktop, I went through the first few reboots during the upgrade and then got stuck at a gray screen with the rotating progress balls. There was some disk activity every couple of seconds so I left it running, checking back on it every hour or so, but it stayed at this point for a whole day. Thinking it had just hung, I rebooted it and got a ‘Recovering your installation’ message, and then it seemed to pick up again at the “Working on Updates” progress screen. After about another 15mins and sitting at 91% complete, there’s a ton of disk activity so I’ll leave it running and check back on it later today.

If you’ve run into other issues during the upgrade, there’s a list of commonly seen issues so far in this article that might be useful.

July 5, 2016

Amateur Radio related uses for the Raspberry Pi (slides)

I presented a topic on Amateur Radio related uses for the Raspberry Pi this evening at my local club, the River City Amateur Radio Communications Society. Here’s a copy of my slides from the presentation on Slideshare:

Raspberry Pi and Amateur Radio from Kevin Hooke

June 11, 2016

Tuning Direwolf packet parameters for use with HT radios

Direwolf has a number of tuneable properties – by default after installing and configuring the basics, your callsign etc, it normally ‘just works’. I’ve been experimenting setting up Direwolf and PiLinBPQ as a BBS on a Raspberry Pi, and using axcall or LinPac on another Pi with Direwolf to call into the BBS. I have a Rigblaster and Yaesu FT60 HT on one Pi, and a SignaLink and Wouxun HT on the other radio.

The problem I ran into was that either Pi seems to work ok to call into a Packet node nearby, but calling from one Pi to the other was pretty unreliable in terms of not decoding packets, and the number of retries before a packet would get received and decoded. I tried a number of options, and feedback in the Yahoo Groups Direwolf group give me some suggestions to try. The tuning parameters are all covered in the excellent Direwolf docs.

Possible problems with using HTs for packet could include a combination of these factors:

Receive audio too loud into Direwolf (aim for around 50)
Receive audio not loud enough – adjust soundcard volume (Rigblaster/Signalink) and alsamixer levels
The radio doesn’t transition quick enough between transmit and receive (can be fixed by adding DWAIT)
Latency from the soundcard audio either in receive or transmit – can be fixed by adding TXDELAY for delay at the start of the transmission, and/or TXTAIL for a delay at the end

The settings I finally wound up with on both Pis that worked for me are:

DWAIT 20

TXDELAY 60

TXTAIL 60

May 30, 2016

Making a Raspberry Pi based Amateur Radio WSPR Go-Kit

A couple of weeks back I got a Raspberry Pi setup with TAPR’s QRPi low pass/band pass filter board, running WsprryPi, providing a low-cost, low power, WSPR transmitter. For my first attempt everything was hooked together temporarily. I wanted to see if I could get the Pi and a USB battery pack packaged in a weatherproof box with connectors for an antenna so I can take it out and leave it outside in the yard transmitting for a day (or at least as long as my USB battery pack will last for – I currently have 10000mAh USB pack that seems to last at least 8 hrs or so with a 1/4 charge remaining).

This is what my second attempt looks like:

10″ Tactical Weatherproof Equipment Case, from MCM
on the sides of the case I drilled through and added banana jacks to connect each side of the wire dipole on the outside of the case. On the inside I soldered a short wire from each jack which connects into the QRPi board connector
the battery is a 10000mAh Anker USB battery pack (hard to see in the photo but it’s at the back of the case)
battery and the Pi are velcro’d into the case

There’s plenty of free space on the inside of this case, I probably could have gone with a smaller one. I have some other Pi related projects in mind though, so will probably use this size case again for another Pi + Packet radio related project.

So, the results, how does it perform. Well the first couple of weekends I ran this I didn’t get any spots, so I suspected something was up with my antenna connections. I had already run with the same wire dipole connected directly to the board, so I knew it would radiate a signal. The first test I roughly cut the wire dipole using the 468/MHz formula but I didn’t bother to check it on an antenna analyzer. So next step, where is the resonant point of this antenna?

Hooking up my YouKits analyzer, the center line is showing 14.1 MHz, but the low point is clearly to the left, so the wire is too long:

Trimming off about 6 inches from each side got us more in the ballpark – now we’re looking good:

Getting the Pi back out in the yard, I hung the antenna from a couple of bushes at approx 5ft off the ground. This is very low for a dipole on 20m, but I know from previously running with this antenna at the same height that I still got spots all the way out to the East coast, so I’m not too worried about getting it up higher.

To keep things in perspective, remember we’ve only running 100mW, so we’re running low power, definitely QRP by any definition. At this low power, any spot is a good spot for me.

So, what about the spots? I didn’t get anything all afternoon, but then I got a number of spots from Texas, so if anything, there was a good propagation path between California and Texas early evening, but the spots dropped out shortly after sunset:

Since every day on HF is different, this is definitely an ongoing experiment 🙂 So far, this works pretty good and I’m happy with the setup!

NOTE: to transmit on Amateur Radio frequencies requires an Amateur Radio license, with the appropriate privileges for the frequency/band you are using. Also, per recommendations for the WsprryPi software, ensure you are using appropriate low pass/band pass filters so the Pi is not generating unexpected harmonics on other frequencies.

For future reference, current solar conditions (from http://www.hamqsl.com/solar3.html ):

SFI=86, SN=25, A11, K=2. 20m day/night was fair