AmateurRadio.com

I have an Icom IC-910H 144MHz/432MHz multimode transceiver for sale. I will only ship to the UK (or certain other European countries if the buyer agrees to the cost of an insured courier.) More details are on the Equipment for sale page of my website.

Back in the early QRP days of Elecraft, there were some K2 owners who were such CW diehards they were uncomfortable with having a radio that possessed a microphone socket. One or two of them described to the Elecraft email reflector how they had blanked off the offending socket. Despite the evidence in the picture on the right, I have not joined this fraternity. I have simply started using the rear microphone and PTT connector on my K3. I have thought for some time that the front panel connector is an accident waiting to happen, and I finally decided to make the move before it did. (And before anyone comments about the dust in the photo let me just say that one of the few benefits of deteriorating eyesight as you get older is that you don’t notice it!)

Front panel microphone sockets are pretty much the norm in ham radios. However in most radios they are secured directly to the metal front panel or, in the case of radios with a plastic fascia to the metal chassis behind it, using a locking nut which tightens the chassis against the ring cast into the socket so that it is rock solid. You could tug at the microphone cable all you want or bash the connector with a hammer and you would be unlikely to cause any damage to the radio itself.

In the K3, the microphone connector comes soldered to the front panel board. There is no possibility of securing it to the metal front panel. The ring that would normally sit on the outside of the mounting hole actually slips through the hole in the front panel so all the rigidity is provided by the PCB. The front panel hole limits movement up and down or side to side to a certain extent. But it does not provide any protection from movements fore and aft. I wonder about the effects of constant small side to side movements on the soldered joints connecting the pins to the board. And I feel sure that if I accidentally leant on the microphone plug, supporting my weight as I tried to make some connection round the back, I could damage the front panel PCB by snapping the microphone socket right off.

As the outer body of the microphone connector is not physically attached to the radio itself it is not electrically grounded. Whilst installing the K144XV transverter board I noticed that grounding is provided by a piece of bare wire that loops round the threaded part of the connector and is soldered to the front panel board. This may have been a modification that I did myself when I assembed my K3 three years ago. What this wire loop does not do is prevent the outer metal part of the microphone connector from turning relative to the insulated centre bearing the 8 pins that are soldered to the PCB.

Because of the perceived risk of damaging the front panel board by accidentally putting my weight on the microphone plug I have been in the habit of disconnecting the microphone whenever I need to lean over the K3 to grope round the back. So the microphone connector has been on and off rather a lot. Recently I observed a tendency for nothing to happen when I pressed the PTT on my desk mic after reconnection. It then became apparent that the outer metal part of the plug has become slightly loose and can be twisted several degrees relative to the centre. I’m pretty sure this is due to the plug body not being secured to the chassis of the radio so there is nothing to take the strain of tightening and untightening the microphone plug. Hence my decision to give up using the front panel socket and move round to the back before the problem got any worse.

My shack is very cramped so I had shortened the cable on my Heil desk mic to eliminate unnecessary length when plugged in to the front of the K3. Consequently it would not reach round to the back. Rather than rewire the microphone I decided to make an extension cable using a line 8-pin socket, retaining the option of using the front connector if I want. I purchased the line connector quite inexpensively from an eBay seller (where else?)

These connectors are much easier to work with than the mini-DIN connectors I have recently been using rather a lot. The pin numbers are clearly visible, but it’s a good job I checked: in the connector I had the pins had been installed in the metal socket offset by one pin position so pin 1 was labelled pin 7 etc! This could easily have been confusing and so my brain cells got a bit more exercise than expected making sure I got the connections right.

I changed the microphone configuration in the menu to use the rear mic socket and so my microphone is now plugged in round the back. It would be interesting to know whether any other K3 users have had problems with this front panel socket. Once, I would have posted about it on the Elecraft email reflector, but that would only result in several replies from kool-aid drinkers saying that it hasn’t happened to them so it must be my fault.

The FCC has called a hearing to determine whether the license of K 1 M A N should be renewed.  If you’re not familar with the ongoing saga, you can read the FCC order which gives the Reader’s Digest version.  It’s both entertaining and sad at the same time, like watching angry women smack each other up on daytime TV talk shows.

Periodically this ongoing fiascocase is in the news, and it seems each time the topic of ARRL one-way transmissions (a.k.a. “broadcasting”) invariably comes up in the conversation.  Technically the term broadcasting in the FCC amateur radio rules means one-way transmissions to the general public, however most folks appear to use the term broadcasting to refer to one-way transmissions to amateurs, like ARRL’s daily transmissions.  I’ve heard arguments that what ARRL does isn’t much different than what K 1 M A N does.  They both do one-way transmissions which is allowed by the FCC, but that’s where the similarity ends.  K 1 M A N was cited by the FCC for control operator issues, interference, and broadcasting inappropriate content.  Broadcasts in previous years often included rants and just plain off-the-wall content.  The broadcasts certainly didn’t showcase the best in amateur radio.

Some radio amateurs argue against broadcasting in general (including ARRL broadcasts) because it interferes with QSOs.  This undoubtedly does happen, and reading the FCC order, this was certainly the case with K 1 M A N.  But the FCC text makes the case that interference was deliberate.  ARRL broadcasts have interfered with ongoing QSOs in the past, but ARRL broadcasts on published schedules and frequencies, and ARRL has been doing it for six decades.  Broadcasting on six or seven HF bands, it’s just not practical to have to seek a clear frequency on each band before each broadcast.

While there is nothing in the rules about the content of broadcasts, I think one also has to take into account just what is being broadcast and who, if anyone, is benefiting from it.  I copy ARRL CW bulletins once in awhile just to brush up on my CW.  The bulletins have news value and general appeal to most radio amateurs.  The same could not be said of K 1 M A N broadcasts.

Playing devil’s advocate for a moment, I can argue that amateur radio broadcasting is no longer necessary.  In the past the only way to get late-breaking amateur radio news was over the air, but today the Internet can provide news bulletins and code practice, and much more efficiently and conveniently.   While this is technical true, I think it would send the wrong message to the public who (wrongly I think) often compares amateur radio and the Internet.  Furthermore, with modes like CW, Hellschreiber, and RTTY, amateur radio is known for preserving old technical traditions.  Eliminating broadcasting in favor of newer technology ironically (and perhaps sadly) would be antithetical to amateur radio.

Overall, I think abuses of one-way broadcasting in amateur radio are few and far between and the benefits of broadcasting outweigh the interference issues.  QSOs undoubtedly will continue to occasionally get stepped on by ARRL bulletins and code practice.  I’m sure we’ll have another egomaniac abuse the one-way transmission privilege in the future, but we can deal with that when it happens.

One final note on the K 1 M A N hearing; judging by past rants and broadcasts, I expect the defendant’s closing summation will sound something like this song (make sure you get into the first 40 seconds or so)….

Introduction:

• Intro from Pete, VE2XPL, host of the wAVEgUIDES pODcAST.
• Promo for the GNU World Order podcast.

Announcements:

• Hello to the new folks in the chat room.
• The Mintcast podcast is either going to stop or will have new hosts after the next episode. If you’re interested in hosting a podcast, contact the folks over there.
• Please spread the word about MAGNetcon, the Mid-America GNU/Linux Networkers Conference, to be held May 6-7, 2011 at the St. Louis Union Station Marriott. If you know anyone that might be a sponsor, exhibitor, or speaker, please let us know. Application forms are available on the web site.
• Check out the new website for Resonant Frequency.
• Also mentioned, the Going Linux podcast and Computer America, “America’s longest-running nationally syndicated radio talk show about computers.”

Feedback:

• Richard, KR4EY, writes about CW… wait, we did this one in Episode 52.
• John, KC8DAX, weighs in on the Windows vs. Linux debate: there are hams that will buy a wire antenna and there are others that will build one. He thinks it’s the same thing with operating systems. Would you want a radio you couldn’t open? Our hosts discuss.
• We received a donation from Charles to help send Linux in the Ham Shack to the 2011 Dayton Hamvention. Thank you, Charles!
• Joe, K1RBY, recently discovered the podcast and is catching up, but is having a problem using gpodder to retrieve episodes. Yes, Joe, there is a bug in one of the WordPress plugins on the web site that contributed to the problem (see lhspodcast.info for a description of the problem.) It has been corrected.
• John, K7JM, also had the problem with gpodder and sends his appreciation for the fix.
• Richard, KJ4VGV, tells us that he is a new amateur radio operator since May and has published an article: Antenna Restrictions: Are They a Catastrophe Waiting to Happen? Good job, Richard!
• James, N2ENN, comments about our episode 52 when we discussed Unity, and offers his thoughts on Wayland, Debian and Ubuntu. Our hosts discuss, and digress to a discussion of browsers, plugins, drivers, ALSA and PulseAudio on Debian vs. LinuxMint Debian Edition. They also commment on Bill Meara’s (of SolderSmoke fame) efforts to get WSPR running under WINE in Ubuntu.
• Paul, KE5WMA, writes “PIC micro controllers are getting more popular in HAM projects. Any suggestions on programming software and boards?” Well, Paul, Linux does still support serial ports, but this may be a good topic for another show. You might find something useful in the many hits returned by a Google search on “Linux PIC programmer”.
• B.B., KC5PIY, asks for help with getting Windows programs for programming radios, such as the Icom IC-2820H and IC-706 MkIIg, running under Linux. He’d also like an APRS client. Richard recommends UIView as an APRS client for Windows, and Xastir for Linux. Russ suggests that most of the radio programming applications will run under WINE in Linux. Also, check out CHIRP, free Linux software for programming a variety of D-STAR radios. You may also want to explore the D-RATS mailing list. It’s not likely you’ll be able to dual-boot Windows and Linux on that netbook, but you can install Ubuntu Linux using WUBI, which would allow you to run Linux within Windows, or install Linux to a USB flash drive using Pen Drive Linux.
• Craig, KB5UEJ, writes about learning IPv6: “I went through the Hurricane Electric certification program and really learned lots about IPv6. I’m now running IPv6 on my home using HEs IPv6 tunnelbroker service. It’s no longer the big bad scary thing that it used to be.” Russ also talked about IPv6 on episode 6 of his QSK podcast.
• Matt shares his thoughts about building “simple” projects from junk box parts and the similarity to running Linux.

Contact Info:

• Contact Richard at [email protected], Russ at [email protected], or both at the same time at [email protected].
• Listen to the live stream every other Tuesday at 8:00pm Central time. Check the LHS web site for dates.
• Leave us a voice mail at 417-200-4811, or record an introduction to the podcast.
• Sign up for the LHS mailing list.
• Sign up for the MAGNetcon mailing list.
• LHS merchandise is available at the SHOP! link on Web site. Check out the Badgerwear or buy one of the other LHS-branded items at PrintFection.com/lhs or Cafe Press. Thanks!
• Thanks to Dave from Gamma Leonis for the theme music.

Music:

• “Balboa” by Ness from the album Fiesta, courtesy of Jamendo.
• “Crawling Back In” by Deathalizer from the album It Dwells Within, courtesy of Jamendo.

Hi, folks. Episode #054 of Linux in the Ham Shack is an all-feedback episode. We cover a lot of ground in this one, from how to run Linux using WUBI, via dual boot, from a flash drive and more. There’s a bit about PIC controllers, feed problems, sticks in the mud, a sprinkling of badgers and a whole lot more. Keep that feedback coming. We love it!

73 de The LHS Guys

A week or so ago my application to operate a part time attended EchoLink node on the 2m band was granted. I didn’t receive any notification of this, I just happened to check the relevant page of the RSGB Data Communications Committee website and noticed that my entry had turned black and an expiry date had been added.

G4ILO-L is EchoLink node number 3098 and operates on 145.2125MHz with a CTCSS Tone of 77.0Hz. As stated the authorization only allows the node to operate when I am on the premises. It uses the non-APRS side of my Kenwood TM-D710 so in practise it will also only operate when I don’t want to operate on 2 metres myself. Therefore it is more likely to be on during the evening UK time than during the day.

The license only allows me to use 5W ERP. Due to my location in the RF black hole of Cockermouth the range will only be a few miles so the number of stations able to access it can probably be counted on the fingers of one hand. Most of the time I will be monitoring the node myself on one of my handhelds so if you call me after connecting there is a good chance I will reply.

I do intend to post a page on my website explaining to other stations in the area how to use it if they want to, but at the moment the number of things to do exceed the available time.

I have developed a script to post the status of the node to the APRS network so an easy way to see whether my node is running or not would be to look up EL-3098 at aprs.fi.

When I got the 70MHz PMR set installed again just before Christmas, I remembered the MB7FM ‘simplex’ repeater on 70.4375MHz. The way it works is that you transmit a message, which it stores and then forwards when you stop transmitting. It will store a maximum of 120 seconds of audio. I tried to access the repeater, colloquially known as the parrot, as it repeats what you say. No luck! I assumed at the time that this was because my aerial had degraded and my signals weren’t reaching Tring! Actually, it would appear that the parrot was, er, sick and off-air.

Yesterday I was tuning around 70MHz and noticed a signal on 70.4375MHz. I was delighted to find that it was the parrot and that I could hear it. I had a couple of QSOs through it, one with Andy, 2E0VPX in Leighton Buzzard and with David, G8JGO/P near Peterborough.

Interestingly, I could hear fragments of both stations directly, though it would have been impossible to make a QSO without the parrot.

Apparently the parrot was restored to service early in the New Year. If you’re in the South East of the UK and have 70MHz FM, give it a go – hopefully you will make some interesting contacts through it that you wouldn’t ordinarily be able to make on simplex.