My reviews are a little delayed this year (thanks, government shutdown for turning October and November into scheduling train wrecks) and I didn’t get to take every submission on a test drive, but the silver lining is that I can just fire off my comments without worrying about influencing anyone else’s reviews. My comments will be short, as I just jotted a few notes about each work, and now a few weeks after playing them, I tend to only remember the points that really struck me. I didn’t use my scoring rubric from previous years, but I had the same criteria in mind. I would usually rate games according to five categories on a first pass and then adjust the scores before voting based on gestalt after playing all of them. This year, I went with my initial gut rating and used the overall history of IF Comp as a baseline.
These reviews are in the random order of play, up to the point that I hit the November 15th voting deadline. Here’s the pseudo-obligatory line break for propriety and etiquette:
I was in Chile this week for a conference on clinical trials in Latin America. I delivered about five talks in three days, but also managed to carve out a few hours to meet with the Radio Club of Chile — more about that in a subsequent post. Today, I had a few hours free before the flight out and decided to explore the city a little before the taxi to the airport would arrive at the hotel.
I had charged the QRP gear during the conference, and I even had an external 2Ah lead acid battery. This time, TSA had decided that it was permitted to take it on the plane. Maybe it helped to label everything I was carrying as “sealed, unspillable, non-spillable, absorbed glass mat, lead-acid battery” and “not lithium”. I even went so far as to write “this is a wheelchair” on my bag, since I know that lead-acid batteries are explicitly permitted in the cabin when the are “part of a wheelchair.”
I headed for the metro system and took the red line from Los Leones to Banqueda, which is just south of the furnicular that runs up the side of Santiago Hill to Santiago Municipal Park. The furnicular has a plaque that advertises that it is the same train that Pope John Paul II took to the top during his trip here. Well, if it’s good enough for the pope…
The furnicular ran smoothly, and we passed the zoological park on the way up. The top of the line is a plaza, which was full of bicyclers, who were taking advantage of the great Spring weather. I exercised some restraint and did not follow the signs pointing “this way to the virgin”, but continued along the trail, towards the antennas that run along the ridge. The biking trail run along the side of the mountain, and followed it for a bit, then turned towards higher ground on dirt trails. I walked to the very top and checked out the antennas, but decided I really didn’t want to pitch my wire antenna anywhere near them.
I continued on a bit more to the East and found a nice place to plunk down on the side of a hill.
I decided to go with a 15m antenna plus my SLT+ tuner. I pitched the wire into a tree and threw the counterpoise down the hill on the pine needles. I got everything else set up, turned on the radio, and didn’t hear much. The background was just not right. I tried tuning the antenna starting with the suggested inductor setting, but the little red light didn’t change at all. I gave the SLT+ a couple knocks to see if anything was loose, and heard an occasional burst of static.
Of course, I didn’t have tools with me. I almost threw some into the bag, but recalling previous run-ins with TSA, I decided against it. I was, however, able to rip the pocket clip off my pen and use that as a screw driver to open the SLT+. I had suspected that the toroids might have come loose, but when I opened it, I saw that I had already addressed that after the last incident — all were firmly anchored with hot glue. What had happened was that the red antenna banana terminal’s solder lug had rotated and was grounded. I twisted it around, and the noise level went up. As I tuned around, I started hearing signals.
But, my troubles with the SLT+ weren’t over. When I tried to run the antenna this time, the capacitor knob spun freely. If I recall, it had been attached to the underlying polyvaricon shaft with either glue or nail polish. I tried to turn the capacitor from the side using the jaws of an alligator clip, but found it very difficult to do so. I had little choice but to settle for the best match I could get using the inductors, although the loudest settings didn’t correspond well to the suggested settings. I decided to go by the SWR reading on the radio itself. My “feedline” was a piece of BNC-terminated coax only about a half meter long, so as long as the radio could tolerate the impedance mismatch, I figured I’d be okay. I did push the radio when it read “high vSWR”, but was willing to transmit with a few bars on the swr meter. Being less picky let me transmit on both 10m and 15m; it seemed to work on both. The moral of this story: always throw a leatherman into the checked baggage. It may get stolen, but most of the time it won’t.
I was extremely relieved when I heard PY1XM, Tom, come back to me on 10m. Up to that point, I thought that I might be skunked on this outing, with nothing to show for hauling my equipment half a world away and up a mountain. Tom was operating from Rio, which is about 3000 km from Santiago. Right after working him, I talked with Paulo, PR2W operating from Brasilia. Paulo gave me a 579, so I was glad that my signal was not entirely in the mud, although I’m sure his antenna did the heavy lifting.
While listening down the band, I heard an Italian station calling — he was pretty faint, so I though I would have no chance, but I could hear another station calling nearby. The more I spun the dial, the louder it became. It was slow but sure, and I had to hear it a few times because I was not familiar with the structure of the call sign: CD6792. After one exchange, I found out that it was Álvaro, a member of the Radio Club of Chile that I had met the previous day. ¡Fine business, Álvaro!
I had two more contacts: LU8WX in Argentina was rapid-firing DX contacts, and he got didn’t miss a beat in replying to my unusually long call. I also found that I could also get a reasonable match on 15m, so my final contact was with Rei, PY2VJ in Brazil.
So, five contacts isn’t anything to gloat about, but considering that Murphy accompanied me up the mountain, I was happy to have had even one. It seemed that conditions were getting better as the day went along, so propagation may also have played some role. I’ll note that the previous day, the K index had gone up to 4, and when I was operating it, it was declining, but still about 2.
A couple quick notes on ARRL CW Sweepstakes 2013 before the memories evaporate: I was keen to work this contest because although I’ve focused on and off on DX stations, I hadn’t worked all states by CW according to logbook of the world. Sure, I had, in fact, worked all states over the last couple years by CW, but for a number of states I have a QSL card rather than an entry in LOTW. I was concerned that we’d be moving this summer and I might not have a chance to get some of the less populated states into the record. I’m happy to report after the contest that CW contacts with all states are now documented in my LOTW account. I can now rest easy.
I don’t have a lot of experience in sweepstakes, and had to look up the exchange of serial number, precedence, my call, check value (the year I was licensed), and my state. My sent exchange was of the form “001 A AI4SV 84 VA”. It took quite a while to get used to sending that string, and more to get used to receiving it and getting it into N1MM.
I began at the starting time of the contest and was instantly barraged frantic 30+ wpm exchanges. Everyone was feeling the pressure at the start, and maybe this strategy pays off, but by the second day, the same stations had slowed way down. It’s not the end of the world to ask for fills and repeats, and in the worst case, you can always hear the station on their next reply and back-fill anything that you missed out on, but coming into the contest cold left me shaken up a bit. A few hours of contesting fixed that, and by the time I left to see “Gravity”, I had a flow going.
The next day, I was only on for a few hours in the middle of the day and a couple at the end. I made a dumb mistake in the last hour. Daylight savings time had changed in the US that weekend, and I hadn’t taken that into account — I thought the contest ended at 11 pm local time, but it ended at 10. I’d been working 40m and had just switched to 80m when the contest stopped, so I didn’t get to fully plunder the 80m crowd, and so came up short on some local areas, such as parts of New York and Massachusetts.
At the end of the event, here’s the breakdown of my score. I was a long way from a clean sweep, but I was very pleased to have worked Yukon Territory – I think that was a first for me.
This is how I looked this evening at 8 pm, at the conclusion of the CQ WW SSB contest. I didn’t work the whole contest in “iron butt” mode, but I my throat was sore and my ears were ringing at the end of the event anyhow — I think I’m out of practice (particularly on voice), as I’ve been more focused on projects than operating lately.
I started early on Saturday morning, rather than the night before and took a few breaks during the day. In the evening, I hung up the earphones around 7 pm and went out for dinner and to see the movie “Gravity”. I didn’t get back on the radio until Sunday morning around 11 am, but then worked more or less straight through to the end of the contest at 8 pm.
The notable feature of this year’s CQ WW SSB was the highly energized state of the ionosphere, with solar flux above 160 for the entire contest, and no solar events to spoil the fun. Ten meters was an endless ocean of signals, with stations dotting the landscape up to around 29.6 Mhz. The flip side of this was that atmospheric absorption and noise were elevated on the lower bands, but the trade off seemed very reasonable to me.
By category, I was a single operator, low power (95W), all band station. My ulterior motive during the contest was to find some new ones, so I was “assisted” in that I kept an eye occasionally on the DX cluster and checked my signal on the reverse beacon network. Most of the time, I cruised the bands, just listening for callers, though. As a “little gun”, I didn’t go a lot of calling myself.
The rig was the K3 and my antennas consisted of my attic antennas: a DX-CC covering 10, 15, 20, and 40m (shortened) and a fan dipole for the lower portion of 10m and 17m (the 17m portion wasn’t used). In addition, I had a chance to use the 80m vertical that I had recently modified. Unfortunately, both 40m and 80m were very noisy, both due to atmospheric noise and local QRM. I had anticipated that 80m would be my secret weapon for working the Caribbean an perhaps Europe, but not so much. The conditions were poor on 80m, and those stations were already doing good business on the upper bands.
The contest was enjoyable for the variety of stations worked, as well as the number: 254. I did log one entirely new DXCC entity: Trinidad and Tobago, and worked a number of countries for the first time on phone, including three consecutive voice contacts with Japan. My final score was 123,467 according to N1MM, which I suppose is good, since I didn’t really have a goal. After caressing the data, here is the list of countries worked: Aland Island, Alaska, Antigua & Barbuda, Argentina, Aruba, Austria, Barbados, Belgium, Bonaire, Brazil, Canada, Canary Islands, Cape Verde, Chile, Colombia, Costa Rica, Croatia, Curacao, Czech Republic, Denmark, Dominican Republic, Ecuador, England, Estonia, European Russia, France, French Guiana, Germany, Hawaii, Honduras, Hungary, Iceland, Ireland, Italy, Jamaica, Japan, Jersey, Latvia, Lithuania, Madeira Island, Martinique, Mexico, Morocco, Netherlands, Nicaragua, Norway, Poland, Portugal, Puerto Rico, Scotland, Serbia, Slovak Republic, Slovenia, Spain, St. Maarten, Saba, St. Eustatius, Sweden, Trinidad & Tobago, Tunisia, Turks & Caicos Islands, Ukraine, Uruguay, USA, Venezuela, Virgin Islands, Wales.
As usual, after the contest, I uploaded logs to Lord-Of-The-Web server, and of course, even one else did the same. I checked back and hour later, and my log had not been processed — it must take a lot of computing power to crunch and correlate that many records. Being the patient type, I checked back another 20 minutes later, and sure enough, I saw a familiar post-contest sight:
In addition to the CQ WW SSB, I shambled-on-out for the 2013 Zombie Shuffle on Friday night. I joined in late because of a Vienna Wireless meeting on Friday night, so I only caught about two hours, from ten to midnight. Twenty meters was dead by the time I got there, and 40 and 80 meters were really noisy. I had six tortured QSOs in all, but I’m glad I had a chance to take part in the QRP event.
As the days grow shorter with the approach of winter and activity shifts towards longer wavelengths, I took stock of my log and noticed that while I have racked up a reasonable number of contacts on 15, 20 and 40 meters, 80 meters lags far behind. I anticipate moving overseas in about six months, but before I go, I’d like to even up the score on 80 meters for this QTH.
My lack of contacts on 80m is a function of my antenna limitations — where I live, I can’t put a lot of metal in the sky. I have one outdoor antenna, a 43-foot vertical; the rest of my antennas are in my attic. My vertical antenna is, intentionally, not much to look at: a single, black wire that runs from the ground up into the top of a tree and is almost impossible to see from a few feet away. However, under the gravel of my backyard, there is a DX-Engineering radial plate. Eight radials spike out underground from that point under my property and into the adjoining forest. The antenna is fed by a coax line that runs underground from the house to that plate, where the center conductor feeds right into the antenna. The antenna was never very well tuned on any specific band, but it managed pretty well on 30 and 40 meters with either built-in or external tuners in the shack. With difficulty, it could tune 15 and 17 meters, and my LDG tuner could force it to work on 80 meters, but the amount of energy actually going out the antenna was pitifully small.
So, I decided that for this winter, the vertical would become a dedicated 80m antenna. The attic antennas can handle the other bands. My first thought was to make an inverted L for 80m, but the far end would extend off my property and would increase visibility of the antenna, particularly in the winter when there are fewer leaves for cover. I decided to work with the vertical radiating wire that was already in position, but to interpose a loading coil at the base.
Pete, K6BFA, lent me his MFJ antenna analyzer, and I measured the impedance of the antenna at the point where I anticipated the matching coil would be located. I measured at 3.7 Mhz, a bit higher in frequency than where I intended to operate and the complex component of impedance measured 278j. Since the antenna is a shortened radiator, this would be capacitive reactance, so -278j. I calculated the inductive reactance needed to null it out as xL = Xc/2*pi*freq, or 11.9 uH.
I had made a coil form from Schedule 40 PVC labeled “one and a half” inches, but measured its outer diameter as 1.9 inches. I wanted to wind a coil big enough for the about 12 uH needed above, plus extra so I would have some for shunt inductance (which I guessed would be around 2-5 uH). I figured 18 uH would be enough to have room to spare. Using the formula of n-turns = sqrt(inductance((18 * coil diameter)(40 * coil length)))/coil diameter, all values in inches, I came up with a three inch long coil with about 28 turns. This fit nicely inside the box that I had, so I went with it. Note that the coil shown in the box in the picture was my first attempt, and the coil turned out to be too small. There is a learning curve for this sort of thing, you know.
The coil was mounted on nylon screws and coils were made rigid with epoxy. The coil wire itself was some 18 gauge hook up wire that turned out to be too large for my protoboard, so I am glad it found a good home in the matching coil. The top of the coil goes to the antenna. The coax comes in the side of the box, and initially, I probed the coil to find a good matching point tuning at 3.7Mhz, intentionally above the CW portion of the band, where I wanted to operate. I found the optimal spot to bring the complex portion of the impedance to zero, and then played with the ground lead, trying to find a point lower on the coil that would yield lowest SWR at 3.560 Mhz, the QRP CW watering hole frequency. After playing with the placement of these two leads for a while, I was satisfied with the resulting SWR curve, which is shown below.
I could have shifted the curve higher in frequency, but I really don’t operate much voice, so I made the decision to optimize the antenna for CW and digital mode transmission at the lower frequency end of the band.
Back in the shack, I verified that I got the same measurements and switched the antenna through to my K3. The rig read the antenna as SWR near 1:1, so I made a couple test transmissions and worked stations in Hungary, Italy and Jamaica. I then turned power to 5W and worked a station in NY. It’s anecdotal, but the antenna seemed to be working fine. After calling CQ at 5W, I checked the reverse beacon network and noted that I was greater than 10 dB above noise as reported by stations in W1, W2, W3, W4, W5 and W7, which seems much better than previously.
While working on a new project, I had a choice of either plugging in the output of a free-standing CW keyer or embedding one into the project. I decided to go with the embedded keyer, but then had to either find or write one. K3NG has written a top-notch keyer based on the arduino platform. Its strengths are its modular design and extensive feature list; it can be compiled to run on a number of chips, with features only limited by the flash memory capacity of the targeted chip. However, it does have a certain minimal size, even when the number of features is stripped down to bare essentials. It would have been a reasonable choice if I could have used the same microcontroller for other functions, with a sizeable portion given over to the K3NG keyer, but in this case, I just want a dead-simple CW keyer.
I’ve used K1EL‘s K12 keyer in the past, as well as the N0XAS picokeyer, and this was more what I had in mind — a low power, small chip. After a quick search, I turned up the YACK (yet another CW keyer) project by Jan Lategahn, DK3LJ. He developed it for the ATtiny45, which has only 4k of flash and even less RAM and EEPROM storage. The project was not developed on the arduino platform, so the code has a much, much smaller footprint. Jan deposited the source code in a svn repository at Source Forge: http://sourceforge.net/projects/yack/. And, this isn’t a matter of trading off features, the YACK supports a number of keying modes, has many configurable features, a beacon mode and even does code practice. Pretty feature-rich, actually.
On that site, it is possible to download not only the source, but the compiled intel hex files for flash and eeprom. Naturally, I went for instant gratification, downloaded these, and flashed them onto the ATtiny using my arduino duemilanove as an in system programmer as previously (but this time, not having to mess with the fuse settings).
I stuck the programmed chip on a protoboard and tried it out. At first I wasn’t sure if it was working at all because it make no sound when powered up, but this was the way it was designed. Next, I tried closing the dit and dah paddles, and heard the expected tone on the piezo buzzer. Holding down either paddle resulted in tones of the correct duration, and holding both resulted in iambic mode B keying. So far, so good.
However, I could not get the keyer to work in command mode. Holding the command key just resulted in rapid clicking on the piezo, perhaps meaning that it was going into and coming out of command mode immediately since it sends an “e” when it exits command mode. Holding the button and closing one or the other paddles resulted in correct behavior: increasing or decreasing the sending speed.
I also noticed that a quick (less than a dit or dah length) tap on the paddles resulted in a shortened dit or dah being sent. This is not the expected behavior for keyers like this. Even if the paddle is released early, the generated tone should be of the correct length, one or three elements long.
Both these issues made the keyer unusable, but it seemed like at least the duration issue had been addressed in an earlier changelog entry, so I thought that perhaps the compiled file might not reflect the most recent and presumably most polished version of the project.
I recompiled the project from source (version 0.7) and noted that the resulting hex file was a bit different in size that the one I had previously used. I loaded both the flash and eep files onto the ATtiny and stuck it back in my prototyped keyer circuit. This time, it worked exactly as described in its documentation. Paddle clicks yielded dits and dahs of the right duration and the command button was fully functional. I ran through all the available commands, and each performed as advertised. I ran the keyer output to my FT817, which I had set to make a tone but not transmit when keyed. I had no problems using the keyer to send at various speeds. All good.
I made some minor tweaks to the code and revised the version to 0.75. This shouldn’t be taken as any sort of official version number, but I needed some way of setting this revision apart from DK3LJ’s original code. I didn’t fix any bugs or make any real improvements, I just optimized the configuration for my purposes. Mostly, this is a matter of taste, and of being used to certain conventions from other keyers. I left most of the user interface alone, though, since I thought Jan had made some very reasonable choices in how he set it up.
Here is a list of what I changed:
Power up message: Now, when powered on, the keyer sends a “73” to let you know that it is alive. This is tone-only, no keying. This provides a quick check that the battery is okay and that everything is hooked up right, which could be helpful to anyone building this circuit, or someone who is on their way out the door for field operation and wants to make sure their keyer is healthy.
Positive Transmit keying default: In most cases, people will want to positively key their rigs, but the default formerly was that the transmit line would go low to key and remain pulled up to VCC otherwise. I flipped this around, which let me use a cheap NPN circuit with open collector to key.
Side tone: For the project that I’m using, a 700Hz side tone is optimal — the keyer is followed by a filter with a 700Hz center frequency, so I changed it in the default settings. I actually prefer 800Hz, but the tone can be changed on the fly, so this isn’t really an issue.
Keying mode: This is entirely personal preference – I made the default keying mode iambic A rather than B, because I think it is easier for someone accustomed to Iambic B to send A rather that the reverse. People who are used to iambic A are thrown by the “extra” character that B generates.
Speed: I bumped the default speed to 15 wpm. Maybe 12 wpm is more inclusive, but 15 wpm works better. Also, anyone can increase or decrease the speed by holding the command button and pressing one paddle or the other. It is not necessary to send a character correctly to change the speed, so I think I haven’t really excluded slower operators.
Exiting command mode sound: Previously, the keyer sent an “e” to indicate that someone intentionally exited command mode by tapping the command button a second time or that the command mode had timed out due to inactivity. I found the “e” a bit short and thought it could be missed. Also, at times I forgot I was in command mode, and whatever else I was doing, it just sounded like an extra dit got in there, without making much sense. I changed the exit sound to “sk”, similar to the picokeyer, because it has a more characteristic sound and would not be expected in the audio stream except at the end of a QSO, so it is more noticeable.
Acknowledgment sound : After a valid command is given, the keyer used to acknowledge it with an “OK”. I changed this to “R” because it is shorter and “R” connotes “Roger, received.” This borrows a bit from the K1EL keyers. I only steal from the best.
After testing out my minor revision, I uploaded the project to a repository at google code. The project files include a schematic in Eagle format as well as a picture of the schematic as a *.png file. For those who would rather not compile from source, I’ve uploaded the compiled intel hex files on this server: main.hex and main.eep. I loaded the files into a stock ATtiny45, right out of the box. No need to mess with any of the fuses — the chip is factory configured to run on its internal 8Mhz clock, scaled to 1Mhz.
The last time I checked on mouser, these chips were a bit over a dollar each and the even more spacious ATtiny85s were a bit less — and that’s unit pricing — buy a bunch and the price falls off considerably. The rest of the components in the keyer are dirt cheap and easily substituted. Making a first-rate keyer these days is not an expensive proposition.
[Update 17 May 2016]
Unfortunately, the Google Code repository no longer exists, but before it went down, I migrated everything over to github, so project files are now over there: https://github.com/dhakajack/jackyack.
Arguably, the crossed bananas display (CBD) was not the next most needed accessory in my shack. I mean, who needs a crossed bananas display, anyhow? Nonetheless, I built one, and it seems to be working.
The CBD is a tuning aid for frequency-shift keyed modes. At one time, these displays were particularly in vogue among RTTY operators. The original version made use of an XY-mode analogue oscilloscope. The demodulated sound from the radio was filtered at the mark and space frequencies and each signal was then fed to either the X or Y input of the scope. Ideally, the tones would be sine waves, and when one tone would be sent, the other would be off. Each tone corresponds to a “banana” or oval on the XY display. The oval is horizontal for one tone and vertical for the other. When the radio is perfectly tuned, the two tones are located right on the two filter center frequencies. When a RTTY signal is sent, or even while it is idling, there is rapid alternation between the two tones, so the vertical and horizontal ovals appear so quickly that they appear to overlap, hence crossed bananas. When the radio is a bit off frequency, the phase relationship changes and the traced ovals rotate and distort. When only noise is present, the tracing is a random jumble. It’s easier to see this in action than to describe it, so I made a video of how it looks on an oscilloscope and how it looks on my newly minted digital CBD.
I got thinking about RTTY and some other similar modes after working on the PK232 mentioned in earlier posts. The PK232 has a little bar graph that indicates when a signal is centered such that the mark and space tones fall where they should, be it for RTTY, AMTOR, PACTOR I, etc. A lot of the circuitry in the PK232 is dedicated to producing and sensing these tones and telling them apart from noise. The bar graph tuning indicator is usable, but let’s face it, nowhere as cool looking as the old style crossed bananas displays on an oscilloscope.
My operating position is already cramped enough, though, without tossing an oscilloscope on the pile, plus I need my scope for bench work and don’t have an extra one that can just relax in a corner until it is needed for RTTY. No, what I needed was a small, modern version of the crossed bananas display. This sounded like a good arduino project. The limiting factors would be timing of the audio samples and speed of updating the display.
My first thought for the display was an LED matrix, preferably one with minimal translational overhead. If the microcontroller could drive it directly or through a shift registers, that seemed like it would be lightning fast, and indeed it probably would be. Unfortunately, to get reasonable resolution, I’d probably need a pretty big array. 8×8 is chunky, but we’re already talking 64 LEDs.
So, with some concern about the data transfer and display/buffer update speeds, I took a look at some LCD displays. I found the ST7735R display at Adafruit. It’s 1.8 inches diagonally, with square pixels arranged in a 128 x 160 array. The display comes on a breakout board that makes it easy to work with, taking care of voltage conversion and making it an SPI device. The display includes a video buffer and Adafruit provides a library that abstracts most of the lower level functions. Adafruit also provides a general graphics library that provided methods for most of the things I wanted to do like drawing a pixel, erasing a pixel, writing text, blanking the screen, etc.
The sound coming out of the PK232 turned out to be biased around 7.5V, with swings of +/- 1.25 and 1.5 volts depending on whether it was being driven by the ACC output of my Yaesu FT-817 or Kenwood TS-450, which must output different levels. Each tone was capacitively coupled to an op-amp channel set up as an inverted amplifier with variable gain. A ganged potentiometer sets the gain between unity and 2x. I used an MC33204PG quad op amp. Of the op-amps I had on hand, it was the best single voltage nearly rail-to-rail chip. I used the third section of the op amp configured as a voltage follower to set the bias voltage at 2.5V for the mark and space op amp sections, so only one out of the four op amp sections was left to twiddle its thumbs. With that bias and input range, the output of the op amp would stay in a reasonable range, nearly 0-5V, consistent with the requirements for analog input on the ATmega328.
In principle, the XY display plots a point defined by an X-input and Y-input at a single instant, so one concern I had was that there had to be minimal separation between the mark and space voltage reads. I minimized this interval by setting the ADC prescaler to 16, trading off some accuracy for faster acquisition time. Without this tweak, the display was distorted due to delay artifact in the phase relationship of the two inputs.
Front and back view of the innards of the crossed-banana display
After displaying the self-congratulatory splash screen, the main activity is to read an XY pair, scale it, and plot it. Given the speed of this process, more than one pixel needs to be displayed at a time to create a reasonably bright display. The solution is to use a circular buffer and to draw one pixel, erase the next pixel in the queue, and crank the index forward by one. This only gets complicated if the size of the queue varies arbitrarily, which is exactly what happens if you twist the brightness potentiometer. The brightness pot is polled every now and then, and when its value changes enough, the size of the queue is modified up or down, resulting in more or less pixels displayed at any one time, and giving the impression of brighter or darker display. When this happens, the size of the queue changes, so there is some housekeeping to do to make sure that all the pixels are taken care of.
The design has one more control, but it’s inside the box in the finished project. The LCD display has a huge range of colors, but having a rainbow XY display was not appealing. I incorporated a dip-switch on the control board, with three bits dedicated to color selection and one to choosing black versus white background. I didn’t think color would be adjusted frequently, so I though it would be okay to leave this control off the front panel. I set my CBD to green dots on a black background, as close as I could get to the appearance of a classic oscilloscope.
The aluminum box, before painting, decals, etc.
My metal working facilities are limited, so this project went into the same sort of enclosure as the NEScafe filter, a cast-aluminum bud box. I bought these in bulk to save shipping at one point, so I suppose we’ll be seeing more of them in future projects as well. At first, it seemed that this box was way too large for this project, but when I started thinking about all the items in the project (LCD panel, control board, two pots, two RCA jacks, a switch, power pole connectors), I became concerned that it all might not fit.
Since I don’t have the patience to send away to an offshore fab facility for a one-off PC board (and since it would likely take more more than one to get it right), I laid the project out on vector board, with some forethought to how it would mount in the bud box and where the screen, controls, and various connectors would emerge. To fit everything in, I had to pack components tightly and cut out two notches in the board to clear wiring runs. Once again, small nylon spacers from Ace Hardware were my friend, providing stand-offs for the screen and for the control board. A layer of clear plastic provides some protection for the glass LCD display. The plastic is pinned at four corners by the control board stand-off screws, but also held in place with some double-face tape.
Contents stuffed into the box.
Since every project justifies one hardware purchase, my purchase for this project was a manual screw countersink from Carr-McMaster. It allowed me to use screws on the front panel, but have them flush with the surface of the panel.
The square window for the LCD was roughly cut out with a dremel rotary tool and then carefully finished with a flat file. The rest of the holes were made with a stepped drill bit, except the power pole hole on the back which I made by pin-holing the metal with a bunch of drill holes, widening with a nibbler, and finishing off with a small file.
I followed the instructions to set up a breadboard as a platform to burn bootloaders onto some factory-fresh ATmega328 chips, according to instructions. Specifically, I set up the breadboard with a 16Mhz crystal rather than using the chip’s onboard clock.
I uploaded the ArduinoISP sketch my Duemilanove, made all the right cross connections to the breadboard, changed the “programmer” setting from AVR-ISP mkII to “Arduino as ISP” and made sure that the target was still set to Duemilanove at 16Mhz. Then, I hit “burn bootloader”. There was a pause of a few seconds, followed by the following error message in the IDE:
I found some similar issues and suggestions on the forums, and it seems the problem is the autoreset on the Duemilanove. The solution: before trying to burn the bootloader, connect the Arduino’s reset to 5V through a 120 ohm resistor. Now, when you select “burn bootloader” lights immediately start flashing on the host arduino and after a few moments, the IDE displays a confirmatory message that the operation was successful. Now the target ATmega328 can be popped off the breadboard and another one can be burnt. After burning bootloaders onto as many chips as desired, the whole assembly can be taken down and the 120 ohm resistor removed from the host arduino board.
I am strongly in favor of having a standard connector for powering everything in the shack, not only for the sake of EMCOMM deployment, but also to avoid having a rat’s nest of proprietary connectors strewn behind the operating desk. Consequently, whenever I build something, I include power pole connectors (see, for example, the NESCAF filter project). The quick and dirty way is to poke a hole in the box and run a power cable out for some length and then crimp on the power pole shells. This works okay, but is not all that neat. What I’d really like to do is mount the connector right on the box. That way, any power pole patch cord could run between the device and a power distribution strip.
Unfortunately, there is no reasonable way to mount a single power pole connector on a panel. There is a nice snap-in connector for two pairs of power poles, but if you want just one pair, which surely must be the most common configuration, there is no ready-made piece that will snap into a hole.
The only option offered commercially is slightly insane: a pair of aluminum brackets that trap the connectors above and below. Each bracket is held in place by a single screw hole, which gives them some tendency to rotate on the screw, although the plastic shells themselves more or less wedge everything into position when both screws are tightened down. To make this solution work, a rectangular hole must be machined into the panel and then screw holes must be drilled at the right spot. Worst of all, these little clips sell for an insulting $2.49 per pair.
As mentioned in the user comments on the powerwerx website, it’s crazy that no one, much less the primary retailer, has offered a product to make this easier. The obvious product would inset the pair of connectors into a round holder, so that the pair could be installed and perhaps screwed into place by drilling one large hole for the assembly. If ever there were a product that needed 3D printing, it would be a panel mount adapter for power pole connectors.
Alas, having no 3D printer, nor for that matter any tools that were really appropriate for the job, I went the primitive route and made my own power pole brackets out of aluminum. I had recently built a couple projects in plastic Radio Shack project boxes that come with both an aluminum and plastic cover. I had opted to use the plastic cover, which left me with a spare aluminum one, which measured out as 19 gauge. I don’t have a sheer, and this is a bit much for my aviation snips, so I made some measurements, scratched out the lines with an awl, and traced over the lines with a cutting wheel mounted on a dremel. I didn’t cut all the way through, but scored the aluminum deeply enough that it snapped on the lines with a bend back and forth. I then went over the edges with a sanding wheel to take off the burrs and smoothen the corners.
Working from one of the real brackets, I measured the dimensions to the neared 64th of an inch. I’d prefer metric, but I have the impression that it was originally laid out in imperial units, so I stuck to those. Luckily, the two cut-outs for the power pole shells are 1/4″ each, which is exactly the size of my nibbler. Two nibbles were enough to make the cut-outs deep enough, and nicely square.
Finally, I drilled a hole for the mounting screw and made sure that the brackets would actually fit correctly over a pair of power pole plugs. The brackets are not as uniform as those rolling off an assembly line, but the price (and availability) are right. Since they are all a bit different, when making an actual project, I’d drill and file the rectangle for power pole pair and then fit the brackets around them into final position in order to mark the exact location of each drill hole.
I had two projects this weekend, one involving microwave and the other involving HF. The microwave project is now firmly attached to the kitchen cabinet and works fine at reheating pizzas. The HF project took more doing. My goal was to set up my Softrock Lite II as a 30m reporting station for the reverse beacon network. I’ve found the RBN useful, and wanted a chance to participate in it from the server rather than the client end.
Last year, I put together a Softrock Lite II, a less than $20 kit that could be built for a single band. I built mine for the 30 meter band. I tried it out with a laptop and could resolve cw signals, but I realized that with a mono input, I would not be able to get any image rejection. The whole value of resolving the signal into quadrature components was lost. I tried using a Mac, which I knew had stereo input, but it was too much to expect this time-critical application to work well in emulation. In these attempts, I noted that there was a lot of noise around the local oscillator frequency, but I didn’t make much of it because there were so many competing issues. I did note that the noise was much better when the unit was run on battery, though.
In the interest of running more advanced sound modes on my aging laptops, I thought it would be helpful to buy an external sound card that would not load down the CPU. In searching for the sound card, I had in mind both the Soft Rock Lite II project and the future construction of a SoftRock Ensemble Transceiver that I had purchased as a kit last year.
I purchased an EMU 0204, an external USB “sound card” ADC/DAC that can take a left and right input and sample at up to 192 kHz. The card has been around for a while and is known to work well under WinXP with system requirements commensurate with the state of the art about five years ago. The laptop I had in mind was the nc6000 that I had salvaged a few months back. The machine has a Pentium M CPU clocked at 1.8 Ghz, 1.5 gigabytes of memory, and is running XP SP3. The machine came with USB 2.0 ports, which are required by the EMU 0204.
I plugged in the EMU 0204, loaded up the drivers, and downloaded updates from Creative Labs. The rear of the EMU 0204 has two inputs: the left input is a hybrid XLR microphone and quarter-inch TRS jack, the other is a quarter-inch TRS jack. The asymmetry of the ports looks odd, but the primary market is musicians, who are more likely to want to plug in a microphone and an instrument rather than the I and Q channel of an SDR radio.
There is a standard 1/4″ jack on the front for headphones, two line out jacks on the back for left and right out, and a 3.5mm stereo jack on the back for external speakers. I plugged some old powered computer speakers into that jack.
The Softrock was built with a stereo 3.5mm jack as output, so I put together a Y-cable that took the tip and ring and distributed it to the tip of a left channel and right channel quarter-inch plug. I had 3-terminal jacks and plugs on hand, so that is what I used. I expected everything to work right off, and of course, it didn’t.
I fired up the SDR program “Rocky” and set the input to the EMU 0204, with sample rate 48 kHz. What I saw was a huge bump in the middle of the spectrum, at the local oscillator frequency. Clicking on it produced horrible feedback. I did see some cw signals buried, but everything was mirrored around the center frequency, meaning I had no image reject, just as if I had only one signal going in. I recalled that running on battery had made things better the first time, and that did clear up some of the noise, but the image reject problem remained.
There is an LED for each channel on front of the EMU 0204, and it is green when the sound source is in a good range for sampling, red when there is too much overdrive and the signal is going into clip. Even with the EMU-0204 dialed up all the way, the signal was never strong enough to turn on the green lights. I thought this was strange, but maybe the Softrock just didn’t have a lot of output, or perhaps the band was legitimately quiet, and there wasn’t any signal in the first place.
I closed Rocky and fired up audacity, which showed some signal on the left channel, but low level on the right channel. Plugging into another source (like my ipad playing music) showed that the cabling was intact. I wondered if perhaps one of the channels was out on the softrock board. I was able to confirm that the local oscillator was working and that the divider was supplying clock pulses with the correct phasing to the mixer. All the voltages on ICs checked out, so I became suspicious of the transformer that takes an input signal at the antenna and picks up signal to feed to the I and Q channels. I pulled the transformer, rewound it, and stuck it back in. No change. I traced the signal as best I could, made sure all the surface mount capacitors were passing signal, and came to the conclusion that the softrock seemed to be fine.
Then it occurred to me that the EMU0204 is meant for professional sound work and that it was expected balanced inputs by default. But surely, a typical electric guitar isn’t a balanced input. Then I realized that the EMU must detect an unbalanced line by seeing continuity between sleeve and ring. I revised my Y-cable, and now everything worked fine: solid audio levels on both I and Q inputs, barely detectable signal artifact at the LO frequency on the spectral dislplay, and strong image rejection. I made sure that I got the right/left side matched up with I/Q by sending a test signal with the K3 on a dummy load, and saw the signal detected at approximately the right frequency. I saw only a hint of the signal on the other side of the LO, which was reasonable considering how strong the signal was.
Connecting the softrock to a power supply created hash, particularly near the center frequency. Not unexpectedly, it was worse on the SS30 switched power supply than the Astron RS-30 linear supply, but I was surprised it was an issue at all on the Astron. I wondered if the problem could related to a ground-loop (the softrock’s antenna is isolated, but audio out ground has continuity with power), but playing with the EMU ground pull-ups did not fix it. I may play around a bit more with the power input and see if some line filtering fixes it. I’m not sure what effect adding isolation transformers on the audio out would have in terms of increased impedance at higher frequencies needed for SDR decoding. Meanwhile, since the softrock pulls less than 30mA, I can run it off one of the rechargeable batteries in the shack just about until the heat death of the universe (rounding up).
Even with this set-up, I was not able to run with Rocky set to 96 kHz sampling. Trying to do so resulted in some stuttering. I also managed to crash rocky by going beyond the band edges in the waterfall display. I had a much better experience using CW skimmer, by the same author. Presumably, it is a later iteration built on the same code base, but it works much smoother. Without changing anything else in the set up, its waterfall was much cleaner, even without cutting in the noise blanker and key click suppressor.
For both Rocky and CW skimmer, one of the set up parameters is the local oscillator frequency. I had chosen 30m because I thought I might only be able to sample at 48 kHz with my original setup, and the band is only 50 kHz wide. Softrock uses a 13. 5 Mhz oscillator, which is divided down by four, and then the third harmonic, 10.125 Mhz becomes the center frequency, so I figured that 10.125+/-24 kHz would get me all but the edges of the band. While building the softrock, I sampled the crystal output as 13.497 Mhz using a lab grade HP counter, albeit one that hadn’t been calibrated in years. Similarly, I measured the divided frequency as the expected 3374 kHz. Both readings were confirmed by my freqmite. Consequently, I calculated the center frequency as 10.122 Mhz, and I entered this into the CW skimmer.
I let the skimmer go for a while, identifying stations in order to compare its frequency read out with others on the reverse beacon network. Noting that I was a few kHz off, I aligned my center frequency to 10,123,150 Hz to bring readings into line with other stations, who I assumed were more calibrated.
CW Skimmer has an integrated telnet server, with a default port of 7300. I set up the skimmer to send its readings to that port. I then sent over to the laptop that I use for contesting and launched N1MM. N1MM can import spots from packet or telnet and add them to the bandmap. I created a new telnet shortcut to the laptop running the skimmer, opened the telnet session, and was pleased to see that N1MM began correctly importing stations identified by the skimmer.
Going back to the skimmer computer, I downloaded the Reverse Beacon Network aggregator. To run it, I also had to download the Microsoft .NET 4.0 framework, which required a reboot. I unpacked the aggregator into the cw skimmer directory, as instructed and launched the skimmer. Next, I launched the aggregator. Setting up the aggregator was mostly intuitive, putting in my name, call sign, etc., but getting the skimmer to submit hits to the RBN required going back into the skimmer and checking the “Allow SKIMMER commands” box.
The aggregator talks to the cw skimmer on the localhosts’s port 7300, but makes data available to port 7550. I was able to re-establish a telnet session from the contest computer to the aggregator using that port, and the bandmap populated correctly.
At this point, I was able to see AI4SV listed as a skimmer station on the reverse beacon network search page. After letting the skimmer run for a while, I searched for stations reported by AI4SV (i.e., I set the “DE” to AI4SV) and got a list. I noticed that there was an annotation in the aggregator that my frequency spots had been adjusted by 0.1 Khz to correct for slight skew versus the majority of reporting stations.
Here’s what it looks like to be on the *other* side of the reverse beacon network: