The Echolink Node DB0BUL
DB0BUL - my SVXLink EchoLink system. Since there is not really a good link in the region of Burglengenfeld, and since I always wanted to do experiments with EchoLink, I started off and developed my own little system. The license has been officially granted by the Bundesnetzagentur according to § 13 AFuV as an autonomously operating radio station.
- QRG: 144.975 KHz
- QTH: R. Strauss Str. 2, 93133 Burglengenfeld
- Modulation: F3E
- Power: 5W
- Hamnet / amprnet IP: 220.127.116.11
- Hostname: db0bul.ampr.org
Click HERE to hear my greeting.
It is not the best QTH I could imagine, but that was not so important for me. I just wanted to conduct my experiments and be able to contact my local buddies.
2 Notes and Help
3 Status: Online
- 2009-08-10 Transceiver control works fine, so all the connections are right. Yet there is a problem in the coax cable towards the antenna, so the system itself is not yet really usable. I have to check the cable next time.
- 2009-09-19 SWR seems OK. It's 1:2 now. That's not optimal, but I'm content with it. The reduced TX power of 5 watts will not cook my PA right in the next moment anyway.
- 2010-01-05 Node is OFFLINE. Reason: A switch is broken, so there's no connectivity between the DSL gateway and the node computer. I will repair it in abt. 1 week.
- 2010-01-16 Node is running again. I exchanged the LAN switches.
- 2010-03-18 Network connectivity problems again. The Node is not available.
- 2010-04-05 Node is running again. Dyndns configuration was missing on updated hardware.
- 2010-06-30 We had a problem because of some misconfiguration due to mixed up device numbers. Since I had a GSM backdoor server as an additional module to the machine the tty serial devices were mixed up which was the cause that the transceiver could no more be made to transmit for some time. Issue is fixed.
- 2010-09-17 Redeployment outside and connection to the Diamond X-50.
- 2019-04-17 Please look at....: Redesign of DB0BUL in 2019
The development goal was to create a machine that consumes as little power as possible. I started off with some very small platforms like the
- MIPS (Linksys WRT54G*, ASUS WL500gP, Fonera)
- Intel ATOM (which is the current platform)
- TexasInstruments ARM (which may be the future platform)
I don't want to accept that such an installation needs to consume the awful amount of 200 or more watts just to forward an audio stream with very limited capacity to the sound subsystem. Using regular PC hardware with Windows on it is really like shooting sparrows with cannonballs.
So here are the links to the development projects:
As always I am using Linux because Windows just sucks for this purpose. Well, Windows sucks almost anywhere, so there's not really a need to explain why I am using Linux :-)
The Echolink subsystem I am using is SVXLink.
There is no Ubuntu deb package yet, but the compilation instruction works quite well. Yet, the init file that comes with the code tarball is crap. I had to write my own.
For more detailed information on the Echolink system itself, please have a look at the pages of DF2NU: http://www.df2nu.de/
My reliable Kenwood TR-7625 does this job. It is a very reliable, easy to repair mobile transmitter with not so many switches and no menus at all and will do this job just perfectly fine.
The Antenna is still a Diamond X6000. Since I have been using it as my main antenna for VHF/UHF/SHF, I will provide another one. It will be a Diamond X-50, which is just perfectly fine for this experimental station.
- 2010-09-17 I have now redeployed the system, it is now the X-50 as announced.
- test of the BeagleBoard platform as Echolink / SVXLink control machine
- deployment of one such a board / system as a gift to the Georgian Amateur Radio Club in Tbilissi, Georgia.