EchoIRLP Pi

This is my Raspberry Pi EchoIRLP project page
I no longer use this setup but I am keeping the page up to help those who might.
11/2018   Some info may be out of date,  For Reference Only
 
 
The basic instructions come from VE7LTD via the IRLP Yahoo group,and/or the new
Wiki page. I added my additional information.
THIS WAS ON THE ORIGINAL RASPBERRY PI NOT THE PI2 B+ BUT SHOULD BE SIMILAR
As of June 2016 there is a new repository for the EchoIRLP code
 
Hardware required:
– IRLP Ver 3.0 board
– Raspberry Pi Model B (any Revision SHOULD work, tested on a Rev 2)
– DB-25 to IDC 26 parallel cable (or similar)1 source
– USB sound card (I used a Syba SD-CM-UAUD, based on Cmedia CM119.)
– 2G (min) SD card (larger is better, but not required) I used a Kingston 8GB card
– USB keyboard (for initial boot only)
 
 
You can also order a complete kit from IRLP.net
 
 
Modifications required:
– Please prepare the IRLP board/parallel cable as shown at: http://www.irlp.net/R_Pi/
You will need to make some slight modifications to the
IRLP Ver.3.0 board. 
 
The modification consists of removing 1 diode, and adding
a jumper wire so the board will work off of 3.3 volts.
The other modification I did was to add 2 jumper wires
between the IRLP board and the USB sound card.
 

Some things I encountered along the way….

SPECIAL NOTE ABOUT THE PI – Do not “hotplug” USB devices, as the unit tends to reset without warning when USB devices are plugged in. So if you are going to run an irlp-reinstall, I would suggest plugging your USB key with the backup file in before you boot the PC.
 
The IRLP Help documents are available at http://irlp.net/new-install/
 
In the /home/irlp/custom/environment file I need to uncomment 1 line.
# If you are using a GPIO interface instead of a parallel port
# uncomment the following.
export USE_GPIO=YES
 
and I had to add
 
#To enable connections to experimental nodes add
export ALLOW_EXPERIMENTAL_NODES=YES
 
This is so I can access the Newsline experimental reflector 0016.
 
 
 
 
ADJUSTING AUDIO LEVELS:
 
I needed to modify the environment file and the rc.mixer file
ENVIRONMENT FILE
# Points to the script used to load your mixer settings
# You should use either ALSAMIXER or AUMIX, but not both
#export MIXER_LOAD=”/usr/bin/aumix -L”
export MIXER_LOAD=”/usr/sbin/alsactl restore”
 
RC.MIXER
#!/bin/bash
#aumix -L
alsactl store
 
comment out the aumix -L and add      alsactl store
 
Otherwise your system will load the aumix settings when a call is
started/stopped.
The audio levels (both receive and transmit) are adjusted using the mixer
program (as user root) :    alsamixer
             and then     alsactl store     to save the config.
As of June 2016 there is a new repository for the EchoIRLP code
ECHOIRLP:
Once IRLP was up and operational I just had to install Echolink on the node.
  If you wish to install Echolink to your node, be sure you already have a
  validated callsign from Echolink and you know your password.
CRONS:
If you choose to run certain scripts as cron jobs, you will need to create
a custom.crons file in the /home/irlp/custom folder.
I had a problem with the custom.crons
and needed to modify the .profile and the .profile_bash by creating a symlink.
There is a thread about this on the IRLP Yahoo Group   Message 66326
Here was the Step by Step that worked for my situation…
As repeater:
mv .profile .profile.orig
ln -s /home/irlp/.bash_profile /home/irlp/.profile
update files
crontab -l
shutdown -r nowI had to do this for things to take effect.
ADDITIONAL SCRIPTS:
I also installed the ctone script and the speaktime script, which are available in the
IRLP Yahoo groups FILE section.
I also changed my SSH port from the standard 22.  I highly recommended you do the same.
once again Gary’s site will walk you through it,
This may help too
Changing the SSH Port
Log in as root
cd /etc/ssh
nano sshd_config
Change to the desired port number
Use Control-O to save the file and then Control-X to exit the nano editor.
I then issued the shutdown -r now command for changes to take effect.
Don’t forget to change the port forwarding in your router to reflect the new port that
needs to be forwarded to your node computer.
THE NODE HAS BEEN UP FOR MANY YEARS NOW WITHOUT ANY PROBLEMS
 
So far so good  🙂