Minor tweaks to dw-start.sh and documentation.

This commit is contained in:
WB2OSZ 2017-04-22 11:24:14 -04:00
parent 433b283b0f
commit 9d2fbdd3f7
4 changed files with 26 additions and 7 deletions

View File

@ -586,7 +586,7 @@ install : $(APPS) direwolf.conf tocalls.txt symbols-new.txt symbolsX.txt dw-icon
# the home directory or other desired location. # the home directory or other desired location.
# #
$(INSTALL) -D --mode=644 direwolf.conf $(INSTALLDIR)/share/doc/direwolf/examples/direwolf.conf $(INSTALL) -D --mode=644 direwolf.conf $(INSTALLDIR)/share/doc/direwolf/examples/direwolf.conf
$(INSTALL) -D --mode=644 dw-start.sh $(INSTALLDIR)/share/doc/direwolf/examples/dw-start.sh $(INSTALL) -D --mode=755 dw-start.sh $(INSTALLDIR)/share/doc/direwolf/examples/dw-start.sh
$(INSTALL) -D --mode=644 sdr.conf $(INSTALLDIR)/share/doc/direwolf/examples/sdr.conf $(INSTALL) -D --mode=644 sdr.conf $(INSTALLDIR)/share/doc/direwolf/examples/sdr.conf
$(INSTALL) -D --mode=644 telemetry-toolkit/telem-m0xer-3.txt $(INSTALLDIR)/share/doc/direwolf/examples/telem-m0xer-3.txt $(INSTALL) -D --mode=644 telemetry-toolkit/telem-m0xer-3.txt $(INSTALLDIR)/share/doc/direwolf/examples/telem-m0xer-3.txt
$(INSTALL) -D --mode=644 telemetry-toolkit/telem-balloon.conf $(INSTALLDIR)/share/doc/direwolf/examples/telem-balloon.conf $(INSTALL) -D --mode=644 telemetry-toolkit/telem-balloon.conf $(INSTALLDIR)/share/doc/direwolf/examples/telem-balloon.conf
@ -637,6 +637,7 @@ endif
.PHONY: install-rpi .PHONY: install-rpi
install-rpi : dw-start.sh install-rpi : dw-start.sh
chmod +x dw-start.sh
cp dw-start.sh ~ cp dw-start.sh ~
ln -f -s /usr/share/applications/direwolf.desktop ~/Desktop/direwolf.desktop ln -f -s /usr/share/applications/direwolf.desktop ~/Desktop/direwolf.desktop

View File

@ -41,6 +41,10 @@ These dive into more detail for specialized topics or typical usage scenarios.
Dont have your own QIKCOM-2 Satellite Transponder? No Problem. You can do the same thing with an ordinary computer and the APRStt gateway built into Dire Wolf. Heres how. Dont have your own QIKCOM-2 Satellite Transponder? No Problem. You can do the same thing with an ordinary computer and the APRStt gateway built into Dire Wolf. Heres how.
- [**Raspberry Pi APRS Tracker**](Raspberry-Pi-APRS-Tracker.pdf) [ [*download*](../../../raw/dev/doc/Raspberry-Pi-APRS-Tracker.pdf) ]
Build a tracking device which transmits position from a GPS receiver.
- [**Raspberry Pi SDR IGate**](Raspberry-Pi-SDR-IGate.pdf) [ [*download*](../../../raw/dev/doc/Raspberry-Pi-SDR-IGate.pdf) ] - [**Raspberry Pi SDR IGate**](Raspberry-Pi-SDR-IGate.pdf) [ [*download*](../../../raw/dev/doc/Raspberry-Pi-SDR-IGate.pdf) ]
It's easy to build a receive-only APRS Internet Gateway (IGate) with only a Raspberry Pi and a software defined radio (RTL-SDR) dongle. Heres how. It's easy to build a receive-only APRS Internet Gateway (IGate) with only a Raspberry Pi and a software defined radio (RTL-SDR) dongle. Heres how.

Binary file not shown.

View File

@ -3,8 +3,14 @@
# Run this from crontab periodically to start up # Run this from crontab periodically to start up
# Dire Wolf automatically. # Dire Wolf automatically.
# Versioning # See User Guide for more discussion.
# For release 1.4 it is section 5.7 "Automatic Start Up After Reboot"
# but it could change in the future as more information is added.
# Versioning (this file, not direwolf version)
#----------- #-----------
# v1.3 - KI6ZHD - added variable support for direwolf binary location
# v1.2 - KI6ZHD - support different versions of VNC # v1.2 - KI6ZHD - support different versions of VNC
# v1.1 - KI6ZHD - expanded version to support running on text-only displays with # v1.1 - KI6ZHD - expanded version to support running on text-only displays with
# auto support; log placement change # auto support; log placement change
@ -25,18 +31,26 @@
RUNMODE=AUTO RUNMODE=AUTO
# Location of the direwolf binary. Depends on $PATH as shown.
# change this if you want to use some other specific location.
# e.g. DIREWOLF="/usr/local/bin/direwolf"
DIREWOLF="direwolf"
#Direwolf start up command :: two examples where example one is enabled #Direwolf start up command :: two examples where example one is enabled
# #
# 1. For normal operation as TNC, digipeater, IGate, etc. # 1. For normal operation as TNC, digipeater, IGate, etc.
# Print audio statistics each 100 seconds for troubleshooting. # Print audio statistics each 100 seconds for troubleshooting.
# Change this command to however you wish to start Direwolf # Change this command to however you wish to start Direwolf
DWCMD="direwolf -a 100"
DWCMD="$DIREWOLF -a 100"
#--------------------------------------------------------------- #---------------------------------------------------------------
# #
# 2. Alternative for running with SDR receiver. # 2. Alternative for running with SDR receiver.
# Piping one application into another makes it a little more complicated. # Piping one application into another makes it a little more complicated.
# We need to use bash for the | to be recognized. # We need to use bash for the | to be recognized.
#DWCMD="bash -c 'rtl_fm -f 144.39M - | direwolf -c sdr.conf -r 24000 -D 1 -'" #DWCMD="bash -c 'rtl_fm -f 144.39M - | direwolf -c sdr.conf -r 24000 -D 1 -'"
@ -64,11 +78,11 @@ function CLI {
# Screen commands # Screen commands
# -d m :: starts the command in detached mode # -d m :: starts the command in detached mode
# -S :: name the session # -S :: name the session
$SCREEN -d -m -S direwolf $DWCMD $SCREEN -d -m -S direwolf $DWCMD >> $LOGFILE
SUCCESS=1 SUCCESS=1
screen -list direwolf $SCREEN -list direwolf
screen -list direwolf >> $LOGFILE $SCREEN -list direwolf >> $LOGFILE
echo "-----------------------" echo "-----------------------"
echo "-----------------------" >> $LOGFILE echo "-----------------------" >> $LOGFILE