Sunday, October 01, 2006

VHF and Echolink

No postings for a week or two. Well, for a start, blogger.com has been blocked from work, so I can't do a quick update at lunchtime like I used to! We've also had some busy weekends. Last weekend, for example, Julie and I did a beekeeping course, which was great fun.

There have been various strands of amateur radio activity going on, of course. I've been on 2m most mornings with Mike, G0UWU as we're both driving to work which is always enjoyable. VHF conditions generally, don't seem to have been great. I've been monitoring the F5XAM and PI7CIS beacons from home on 2m, but though they're always there, there's been nothing exceptional.

I took BT up on their offer to upgrade our internet connection. It now runs at about 7.6MBs rather than the previous 2.2MBs. The 'Home Hub' which came with the upgrade runs as a wireless broadband router. It has lots of benefits, but it IS very noisy on 50MHz. You'll perhaps remember the previous posting about different access points and noise on 50MHz. I'll have to muse about that one and see if shifting the location of the equipment makes any difference.

Although I don't use Echolink much, I find it's quite interesting and always a good way of demoing a combination of amateur radio and computing. Having installed the new Home Hub, I had to find a way to get the router to pass the traffic on the Echolink ports. That took a bit of fiddling around in the hidden menus, but it's all done and works well. If you need a pointer, you need to go into the Application Sharing menu, set Echolink up as an application passing UDP traffic on ports 5198 and 5199 (from memory) and then assign Echolink to the workstation on your LAN will run the Echolink client. This could be multiple workstations if you wish.

No comments:

LinkWithin

Related Posts with Thumbnails