Fiddling with APRS

I had heard of VARA HF but not done anything about it because the Windows machine is not connected to the HF rig. That was cured yesterday by something I should have got ages ago - a USB switch. This switch has two USB connections aimed at connection to two PCs, and then four USB sockets for devices. So the SignalLink and the USB adapter for CAT control are now plugged into this switch which shares these between the Linux and Windows PCs. It all seems to work fine with USB devices connecting and disconnecting and, fortunately for Windows anyway appearing in the same place. It took me a whole to figure out that the CAT control, ends up as COM6 on the Windows box but so far it has not decided to change when reconnected. Now the Windows box can see the FT450D I tried WSJT-X - no issues there, and it provided a good end to end test. I downloaded VarAC and the VARA HF modem. Installation went fine and almost straight away it decoded a beacon on 14.105. Since then it has been decoding numerous other beacons and a few CQ calls but I have yet to…

I've had a Yaesu FTM100DE for a while now and for all that while it has had a USB adapter plugged in and doing nothing. The adapter, SCU-20 came with the transceiver. Anyway, I wondered what it could be use for. The handbook discusses it being used to extract GPS data and packet data and a quick search found some software, APRSIS32 for Windows (see http://aprsisce.wikidot.com ) that talks to various transceivers. So, software loaded, I needed a driver from Yaesu. Here's where it begins to get a little tedious as those of you who have had to go looking for drivers will no doubt know. First port of call was the Yaesu site and a search for FTM100. Ok, found that. Now 'files' and ... a driver for a SCU-19. Searches for SCU-20 found a PDF which contained the filename of the driver but not the source. I eventually found it... under the files for the FTM400. And that was the hardest part. Driver in, USB lead connected, APRSIS32 loaded and a few parameters configured and there is it. The software will also send messages etc. but apparently Yaesu do not allow their kit, or at least the kit…

After finding the dead LCD screen that was to be a 5.6GHz ATV receiver it also turned out that the 7" Pi screen on my Portsdown setup had similarly died - just white lines on the screen. No amount of stripping, reassembling and general fiddling fixed it. A new screen did. Anyway, I now have a Winterhill receiver. This came from a fellow ham and saved me building one. As is usual with any new box one absolutely must try it right away, which is how I discovered the bust screen on the Portsdown. After that was replaced I successfully sent a test card 40 inches across the desk! Small steps... and at least the Winterhill is in a nice box unlike my Portsdown which is still waiting for a suitably sized case - why is it all the nice metal boxes are a few mm lower than the 7" display needs. Huh.