Troubles with the ID51

M0RVB

I wanted to get a programmer for the ID51. So, off to RT Systems as I have some of their programmers already. Got the Mac version of the package for the ID51 but it does not allow programming via SD card. That caught me out because their package for the FT2D does and I wrongly assumed this would too.

Of course, it needs a cable! Off to eBay… an allegedly suitable cable arrived today but the RT Systems program will not find it. Typical, it needs one of their enfangled cables that are incompatible with the rest of the world. No way that will arrive in time for our trip.

So… Chirp then. Downloaded the Mac version but it, too will not see the eBay cable. I know the Mac sees it so why won’t the software? RT Systems has no option to select a USB port, Chirp does but offers no help as to what it is.

Try Linux? Hmmm…  I’m really not into fiddling with flatpack or any other enfangled package managers - apt is enough, no apt, no use.

Windows then! Got Chirp, and it can find the cable, and Chirp will see it and will download from the ID51. All good then? Nope!

This exercise was to enable me to program up all the foreign repeaters ready for the trip and also to figure out why our local repeater was in the list incorrectly. So let’s take a step backwards now…

I had tried to update the list of repeaters by downloading from Icom. This method works fine by loading the relevant file onto an SD card and telling the radio to load it. RT Systems take note - why does your FT2D software allow this but the ID51 software does not? This should be standard!

But the resultant list was missing the local repeater. I tried to add it but then the radio tells me there are no repeaters at all. I tried downloading the file from repeaterbook which at least knows about the local repeater. No joy. I tried editing the files already on the radio but each time it somehow messed up. After many attempts and permutations I had to give up which is why I though getting an actual programmer would help.

Enter Chirp (on Windows, yuk…). It downloaded from the radio fine but when I looked at the repeater list it seemed broken - all it had was a list of callsigns and no other information. Ugh! But then I remembered that the radio had whinged that there were no repeaters. So, I loaded a known good repeater list file already omitted the SD card, checked the radio would see repeaters when DR is pressed, and downloaded that from the radio into Chirp. The repeater list is just as broken.

Ok… so I exported everything from Chirp as CSV and opened in LibreOffice. But it does not export the repeater list so I am no further towards understanding how the data works. Time to hit the ‘net. Meanwhile, I checked the current repeater list to see if the ‘Near Repeater’ option was working… nope… 20 minutes in and the radio still has not got a GPS location, just like the FT2D!

Fiddling further with Chirp I found someone had kindly created a list of repeaters that does include our local one. I downloaded this and tried to load it into Chirp but it just says the file format is invalid. I copied it to the SD card and tried to import it into the ID51 - data error. Ok, this has gone far enough, this is not rocket science but it seems that it is made so.

Let’s try Icom’s own software, apparently called cs-51plus2. This is called cloning software and, of course is for Windows. After installing the software it read the ID51 ok. I found the repeater list under ‘Digital’ and, indeed, the local repeater is missing. The big question is, can I add it? Ok, I added the  local repeater to the end of the list of repeaters, adding the frequency and offset, plus coordinates. Coordinates are degrees, minutes and seconds but I had digital so had to convert - not a biggie. Wrote the data back to the radio and rebooted. And… the repeater is there! And it keys! Just had to wait for the radio to find the GPS - I reckon it does this by carrier pigeon - but finally the ‘Near Repeater’ function works and also finds the newly-added local repeater. Now to add the foreign ones…

So what is the takeaway from all of this? I wasted money on RT Systems software by assuming it would work the same as the FT2D software i.e. use the SD card. Never mind. I tried Chirp but that just confused the issue. And the manufacturer’s own software, generally looked down on, worked fine! (Apparently the software comes with the radio, I don’t remember it having a CD and there is no sign of it but I downloaded it from Icom just fine). I must remind myself if I ever get another radio to first try the manufacturer’s software as my needs are generally lightweight, otherwise try Chirp, and last get the RT Systems software after making sure (by which I mean email them as it is very muddled reading the literature) whether it needs their special cable - and, personally, if it does then I won’t buy the software. I mean, come on, I pay for the software and I am forced to buy a lead I’ll probably only use once or twice?

You should also read:

M0RVB

Flying with radios...

We just had a short trip to Europe and then Japan and so I took a couple of handheld radios along. For Europe the CEPT licence was fine but for Japan I arranged a short term one via JARL who were very helpful. So, licences and HTs in hand, or, rather, in carry-on bag, off we went. I had broken the radios down into battery, radio and antenna and put each in a plastic bag to keep everything clean. Big mistake! My bag was searched at the UK airport and in Schiphol. The bags were causing confusion, especially as, at Schiphol they asked how the battery related to whatever the Mouser code was on the old plastic bag I had used. Very quick though, it only added a couple of minutes each time and they were happy. So I left the radios intact for the onward trip from Schiphol and into Japan. No issues at all at either end or on the return. So... note to self, leave the radios intact.

Continue reading...
M0RVB

More stuff to fiddle with

Armed with the LF converter I have been experimenting with antennas for the low side of things. There is far too much electronic hash in the house for any hope of receiving things so I now have a couple of antenna options to try outdoors. Given the radios are all upstairs and there is no easy cable route to the workshop where the antennas can go this means a remote SDR. There is already Ethernet in the garage where the QO100 transceiver was so experiments can begin. Anyway, here are the new fiddleables... an IP35 mini whip from eBay seller radio.el32 complete with bias tee: This comes as the two PCBs - antenna and bias tee - plus 3 BNC sockets. The metal box was sourced from eBay and the waterproof plastic housing from Amazon. It's a lot bigger than is needed but should be fine. And a 'loop antenna amplifier' (LAA++) and bias tee from Cross Country Wireless: All being well the first test will be of the IP35 antenna once mounted on a wooden pole. The LAA++ will take me a little longer as I need to make a loop for it.

Continue reading...
M0RVB

Fiddling with APRS

I've been fiddling recently with trying to receive satellites but without all the going outside and waving yagi antennas around... I've heard a few QSOs on DIWATA 2 and there is a very good pass in a day or so where I may be able to get a call in. This is using the Trio TR-9130 as receiver as it has a horizontal dipole connected, and the FTM100DE as transmitter, though so far without success on transmit. Anyway, I remembered the FTM100 has APRS built in and the ISS often sends and receives this in 145.825 and so I've been leaving the radio switched on. Today I noticed it did indeed receive packets from the ISS. I also downloaded UISS by ON6MU which seems to 'just work' - nice that, I downloaded it and ran it and it found the sound card and returned an APRS message on a later ISS pass. Oddly, the FTM100D did not decode that message (the squelch is set to 0). It comes with a module called SoundModem by UZ7HO which seems pretty comprehensive. Another package to play with...

Continue reading...