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
 
Thanks to all who contributed information to help me along the way.
 
This is how I got my Pi node up and running.      Maybe it can help you too.
 
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
I started out with a working EchoIRLP node that was running CentOS.
 
I used the backup for reinstall script that is provided by IRLP, and
saved the backup file to a USB Flash stick.
As root:
/home/irlp/scripts/backup_for_reinstall
 
I then began getting the necessary hardware in order.
 
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.
 
 
 
Software Required:
– The official Raspbian release from the Raspberry Pi Foundation:
(no support will be offered for this, besides what buttons to press)
Follow the directions on the RPi site for creating the card.
 
Note, I used the Win32DiscImager to create my file
AND I use SD Formatter program to format my SD cards
 
 
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.
 
Boot your Pi, and perform the following steps in the config:
1) expand_rootfs Expand root partition to fill SD card
2) change_pass Change password for ‘pi’ user
3) change_locale Set locale (as required)
4) change_timezone Set timezone
5) memory_split Change memory split (set to 16)
6) ssh Enable ssh server
7) boot_behaviour DO NOT BOOT INTO DESKTOP
       Then click Finish.
 
 
 
On initial boot, log in using user pi, and the password set above. The pi user is essentially a root user, and we want to create a root password, and carry on. That makes this more like other IRLP nodes…
 
At the prompt, type:
sudo su –
passwd root (set a password)
 
Now in the future, you can log in as root, or you can also choose to remove the pi user (optional):
userdel -r pi
 
NOTE: AT THIS POINT I REBOOTED THE Pi AND UNPLUGGED THE USB KEYBOARD.
      I THEN INSERTED THE USB FLASH DRIVE WITH MY BACKUP FILES ON THEM.
      I THEN USED PUTTY ON A SPARE COMPUTER TO FINISH THE IRLP INSTALL.
      THIS WAS BECAUSE I WANTED THE SOUND CARD TO BE DETECTED WHILE INSTALLING
      IRLP, AND DIDN’T WANT TO HOT PLUG THE FLASH DRIVE.
THE Pi ONLY HAS THE 2 USB PORTS.    YMMV
 
INSTALLING THE IRLP SOFTWARE
 
Now we download the IRLP “get-irlp-files” script, which will carry us through the rest of the install.
wget ftp://ftp.irlp.net/get-irlp-files
chmod +x get-irlp-files
./get-irlp-files
(This process will take several minutes (up to 20, but mine took closer to 45), as it basically strips the default install of about 200 unneeded packages, and configures your Pi for the packages it needs for IRLP to run).
Lets be honest – the Pi is not the fastest beast on the block…. so this process takes time.
 
Then progress with your install as usual. All of the commands are the same as a normal node, and the installer automatically picks up the special binary files for the ARM processor.
 
 
One nice thing now when restoring from a backup file, you have 2 options.
One is a regular back up install, and the second is a Fresh basic install.
I chose a Fresh Basic reinstall, so it was like I was starting over with an unmodified node.
 
 
The IRLP Help documents are available at http://irlp.net/new-install/
 
Your node should work at this point.
 
The last step we will do is update the firmware on your Pi. This will help keep everyone on a “level” playing field, and will help instructions work for all users.
 
Follow the directions at:
 
EXCEPT, as you are already logged in as root, you can remove the “sudo” in the front of all of the commands. So the command string is:
wget http://goo.gl/1BOfJ -O /usr/bin/rpi-update && sudo chmod +x /usr/bin/rpi-update
rpi-update
 
Then reboot, and enjoy your new PiRLP node.         shutdown -r now
Some things I encountered along the way….
 
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.
 
Those steps are as follows:
 
1. login as root
 
 
3. chmod +x ./echo-install-debian
 
4. ./echo-install-debian        (Don’t forget the leading period)
 
5. Answer the prompts.
 
6. Restart IRLP by running /home/irlp/custom/rc.irlp
 
Test by connecting to the EchoLink *ECHOTEST* server,
EchoLink node 9999.
NOTES:  After initial EchoIRLP installation I was getting a FAIL 99 code when
trying to make a connection.
It took a little digging, but found in the echo_call scripts where the
script was attempting to find tbd running via “/sbin/pidof” and was failing
with file not found. I found pidof residing in “/bin” so made a symlink in
the /sbin directory and now everything is happy.
THIS SHOULD HAVE CORRECTED IN THE NEW DEBIAN VERSION AND SHOULD NOT BE NEEDED but…incase
ln -s /bin/pidof /sbin/pidof    This worked to created the symlink
 
 
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  🙂