To do this, you’ll need the following (if you’re not making your own cables):

• Icom IC-2820 D-STAR radio
• Kenwood RC-D710 TNC/data terminal/control panel
• Kenwood PG-5J interface kit for RC-D710
• Kenwood PG-5G programming cable (to connect to a PC running Windows)
• Kenwood MCP-2A, “Memory Control Program” software (a free download)
• A PC running Windows for the MCP-2A software
• 6-pin mini-DIN cable that comes with the PG-5J
• A data cable with 2 mini-stereo jack plugs (the RC-D710 came with such a cable, but with only one jack plug)

After the usual preparation (checking items, installing powerpole connectors on the power cable, etc.) I powered off the radio and TNC, and connected the 6-pin mini-DIN cable from the main unit of the 2820 to the “data” socket on the PG-5J interface unit. I then connected the RJ-45 cable between the PG-5J and the RC-D710 panel. Finally, I had to connect the mini-stereo jack cable from the RC-D710 panel to the main unit of the 2820. I assumed that there would be a mini-jack at each end of the cable, but, no! Fortunately, I had two of these cables and I chose to connect them together. It’s a very small cable, with what seems like 3 strands of very thin copper in 3 cores (it’s a stereo cable). My soldering ability wasn’t up to the job, so I gave up and used a terminal block, which works nicely for testing (I’ve ordered a 10ft ready-made cable from Monoprice).

Next, I connected the RC-D710 to my PC and upgraded the firmware (it was v1.x and v2.01 is current), and then used the MCP-2A software to read the default config. This software is the only way to change the configuration elements on the RC-D710. I upped the levels as described in this article, viewed the other configuration items and set my callsign info, as well as some custom messages, setup smartbeaconing, etc. and on the IC_2820 I made sure in the data function that “G-D” was on (this sends GPS data via the stereo data cable to the D710), and in the menus (GPS sentence) I set RMA and GGA to on. In the packet menu, I set the packet operation band to “left” so the APRS data will only transmit on the band I have set to 144.39 MHz.

I feel I’ve only just scratched the surface, and will experiment a little more to optimize the configuration, but my first impression is that this will prove to be a great setup.

Anyway, I got an email from them saying that they’ve registered the device for me and they also threw in a free upgrade to City Navigator North America NT 2010, which is great, and that’s what started this thing in the first place.

So, while a little slower than usual, Garmin support came through again. Thank-you Garmin, I shall continue to recommend your products!

I’m a fan of Garmin GPS receivers, particularly devices like the GPSMap 478, a wonderful chart-plotting GPS. I also have a StreetPilot 7500, a nice large-screen GPS that I use in the truck. I’ve spend thousands on Garmin hardware and maps since my first Garmin device, a GPS 12, back in 1995. If you count the devices I’ve bought for others and my referrals that total is well north of $10,000.

A while ago, maybe in mid-late 2007, Garmin updated their internal systems at my.garmin.com. I had multiple GPSes registered with them, including the StreetPilot 7500. The old system was never brilliant, I blame the DRM they have around the mapping data, but that’s another subject…

Anyway, I want to upgrade the 7500 to the latest version of City Navigator North America NT, the 2009 update. To unlock the maps, you have to have a registered device. During Garmins update to my.garmin.com my previously registered 7500 disappeared. Now, when I try to register it again my.garmin.com rejects my serial number.

I’ve been extremely happy with Garmin support through the years, in fact they managed to next day me a replacement mapping CDROM when I was out of the country, starting trans-Sahara trip, to replace a damaged disk. They have been pretty responsive so far with my registration problem, until I received this today (the issue had been passed to their IT department)

We have contacted our IT department and requested another update. To answer your questions:

We have stressed the importance of getting this matter resolved and I am hopeful that we can get this matter resolved quickly. Thank you for your patience in this matter.

As this issue has been outstanding for 3 weeks, I’d love to know what the “IT Department” are doing. The very phrase makes my blood run cold, and I’m in IT guy! Some transparency would be greatly appreciated.

Ideally, I’d like to know what IT have done in the 2 weeks since they received this ticket from their support guys, what they are planning to do and why they can’t escalate it.

Remember, all I want to do is give them about $100 for new maps. All I need is a valid serial number.

I hope I don’t have to start buying and recommending other brands if they can’t resolve this. If anyone from Garmin feels like helping, the case number is KMM12787676I15977L0KM. Thanks!

I came across an article via Tristan Gooley’s blog (Tristan runs the Natural Navigation school in the UK) , which mentioned the 1974 article by Clinton Bailey, “Bedouin Star-Lore in Sinai and the Negev” (PDF link). 

It’s a wonderful article, clearly a precursor to his book “A Culture of Desert Survival“, and full of navigation and climatic information in the poetry of the Bedouin.

My favorite is

In tila’ Suhayl-Id tdmin is-sarjl—law kdn ‘aqdb il-layl

Or in English

If Canopus rises, don’t trust the flood

And finally the practical application:

Don’t camp in the wadi!

Canopus was frequently used as a Southern Pole Star by those in the Northern Hemisphere until it fell out of usage when the magnetic compass became popular. The Bedouin also saw Canopus as a coward, as it would dip seasonally below the horizon – unlike Polaris, the steadfast. 

It’s particularly moving to remember that these traditions have persisted until the 21st century through an oral history that pre-dates Islam.