I have purchased, and am waiting on an svxlink card. It is a raspberry Pi powered repeater controller / echolink interface. I plan on coupling it with a UHF HT for a temporary echolink interface. There is the capability of connecting it directly to my repeater, if we can get internet access at the site.
The Raspberry Pi runs the software SVXLink, which performs all the audio handling. It also controls the functions on the svxlink card. I am going to use the Raspberry Pi 3, as it has the processing power to run the software and control the svxlink card. The software contains a web interface for changing the parameters.
I have since scrapped the APRS project and am going to use the enclosure for the interface. The enclosure already has an opening for a display. The display I was going to use for the APRS node will not work, it requires programming and specific I/O configuring. I have found an HDMI display that “should” fit in the opening without too much issue. I have another option in mind, but that’ll be a last ditch effort.
The whole project will include:
- Raspberry Pi 3
- Svxlink Card
- 12v DC power supply
- UHF HT
- HDMI Display (maybe touch interface)
The 12V power supply will provide power to the HT and theSvxlink card. The card supplies 5V power to the RasPi via the 40pin gpio header. The HDMI display is powered by USB connection to the pi (which is also the data line for the touch screen, if I use one). I can add a 12 VDC input which would make it adaptable for portable use, independent of having 120 VAC.
So far, all I have for this project is the enclosure, 12VDC power supply (re-purposed from my junk box) and a dual band VHF /UHF HT (Yaesu FT-470). I will assemble the svxlink board when it arrives before I get the RasPi 3. I have a general idea how I would like to mount everything in the enclosure. Once all the components are in my hands, a better idea of placement will be determined. I would like to keep the RF side as far away from the power as I can. I am not sure if the 470 will be happy with an estimated high duty cycle (I’m estimating 75 to 90% duty cycle), but I plan on providing additional cooling. If memory serves me correctly, that radio gets pretty warm running 5 watts for any length of time. (Maybe a chance to play with a peltier junction for added cooling, gotta look into that!). For sure I will add a fan for forced cooling of the Pi and HT, I am thinking of adding a temperature sensor to a few components, which would control one of the relays on the svxlink card to power a fan (or peltier / fan).
I have a lot of ideas for this project. I am going to try and keep it as neat and clean as I can. You’ll get to follow along with me as I build the project, from installing components on the board to software configuration to final testing here. Stay tuned, there’s more to come!
UPDATE 10/4/16
I have received confirmation and a tracking number for the 3 SVXlink boards. I have sourced the components needed to assemble the board. I will pickup some USB sound cards to experiment with. The project is slowly coming together, looks like it will be a good winter project.
UPDATE 10/8/16
The boards have arrived! The boards have arrived!
I’ve ordered one set of parts to assemble a board and test out. I am awaiting confirmation of a solution to program a Motorola mobile radio to use as the link radio. I am going with the Motorola because all the signals are available at the rear accessory jack. One cable, one connection, easy peasy.
I fired up the Pi to play around with svxlink and found out something interesting. My internet will not allow me to receive connect requests from the echolink servers. I have my router all setup to pass the needed ports, but still no success. After a quick search on the Internet for others with the same isp and same issues, I realized I was not the only one with this issue. So, now I need to look into a different isp for echolink use (which may or may not work) and see what the cost is. Sometimes, living in the country has its drawbacks.
KB0FXK 