Tracks!

Total distance: 42.8 mi
Total climbing: 2139 ft
Download file: 20180101.gpx

Braaapppp

Total distance: 100.09 mi
Total climbing: 9287 ft
Download file: 20180106.gpx

Sailing Long Beach

Images and video stolen from Instagram users @suppagaraffe @revmook

Total distance: 34.03 mi
Total climbing: 2154 ft
Download file: 20171007.gpx
Total distance: 16.34 mi
Total climbing: 911 ft
Download file: 20171111.gpx
Total distance: 31.24 mi
Total climbing: 1751 ft
Download file: 20171119.gpx

Server uptime

This Linux machine has been up for quite a bit of time.  It’s going down soon for a complete refit.  If this post is here in a few days, it means I didn’t break the SQL database!  Whoohoo!

$ uptime

15:16:27 up 858 days,  5:02,  2 users,  load average: 1.43, 1.65, 1.65

 

California Small Loop

Kel and I did a quick loop around the lower half of California in September.  We didn’t take many photos for some reason and I was stressed out the entire time because of work obligations the following week.  Photos and tracks for reference below.

screen-shot-2016-11-15-at-8-19-17-am screen-shot-2016-11-15-at-8-19-39-am screen-shot-2016-11-15-at-8-20-12-am

Total distance: 966.56 mi
Total climbing: 81204 ft
Download file: Cal_Small_loop.gpx

LA -> NV -> MEX

Los Angeles, to the middle of Nevada, to Mexico and back.  Missing a lot of photos, but you get the point.  Tracks below…

IMG_0128 IMG_0134 IMG_0135 IMG_0143 IMG_0145 IMG_0198 IMG_0195 IMG_0191 IMG_0189 IMG_0170 IMG_0161 IMG_0157 IMG_0151

 

 

 

$ gpsbabel -t -i gpx -f 20160528.gpx -i gpx -f 20160
529.gpx -i gpx -f 20160530.gpx -i gpx -f 20160531.gpx -i gpx -f 20160601.gpx -i gpx
-f 20160603.gpx -i gpx -f 20160606.gpx -x track,merge,title=”COMBINED LOG” -o gpx
-F LA_AZ_MEX.gpx

Total distance: 2129.84 mi
Total climbing: 86223 ft
Download file: LA_NV_MEX.gpx

 

 

Ocotillo Wells

Tracks for Ocotillo Wells state OHV area.

Total distance: 55.43 mi
Total climbing: 2348 ft
Download file: 20160328123757-78010-data.gpx

SVXlink Part 2

This is just notes for myself really, but part one can be found here.

Default path for sound files in Debian.  This path depends on your distro;
/usr/local/share/svxlink/sounds/en_US

What I have done to build custom modules into SVXlink is to use DTMF tones to trigger external scripts.  Those scripts are written in Bash or Python.

Drop a file in the following path, copy and paste below, edit as needed.  As you can see, toggling a DTMF tone will run a script and send me an eMail.
/usr/local/share/svxlink/events.d/local/Logic.tcl

###############################################################################
#
# Generic Logic event handlers (local extension)
#
###############################################################################
# This is the namespace in which all functions and variables below will exist.
#
namespace eval Logic {
# Executed when a DTMF command has been received
# cmd - The command
#
# Return 1 to hide the command from further processing is SvxLink or
# return 0 to make SvxLink continue processing as normal.
#
proc dtmf_cmd_received {cmd} {
global active_module
if {$active_module != "" && [string index $cmd 0] != "*"} {
return 0
}
if {[string index $cmd 0] == "*"} {
set cmd [string range $cmd 1 end]
}
if {$cmd == "99"} {
puts "Executing external command 99"
playMsg "Core" "relay4"
exec mail -a /home/revmook/test.text -s "DTMF command test 99" revmook at echoparklake dot clam < /dev/null &
return 1
}
if {$cmd == "98"} {
puts "Executing external command 98"
playMsg "Core" "relay3"
exec mail -a /home/revmook/test.text -s "DTMF command test 98" revmook at echoparklake dot clam < /dev/null &
return 1
}
if {$cmd == "97"} {
puts "Executing external command 97"
playMsg "Core" "relay2"
exec mail -a /home/revmook/test.text -s "DTMF command test 97" revmook at echoparklake dot clam < /dev/null &
return 1
}
if {$cmd == "96"} {
puts "Executing external command 96"
playMsg "Core" "relay1"
exec mail -a /home/revmook/test.text -s "DTMF command test 96" revmook at echoparklake dot clam < /dev/null &
return 1
}
return 0

External sounds for the above script go in this path.  Please note SVXlink is picky about the file format. I can’t recall what it is (mono 16 bit I think) but it will error out if things are not right.
/usr/local/share/svxlink/sounds/en_US/Core