<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
There are a number examples of configuring a switch to the GPIOs
that will properly and safely shut down the Pi and then after that
you can have a delayed timer to properly shut down the power source.<br>
<br>
Good Luck and we anticipate info & pics as you go along.<br>
<br>
<br>
Stan, KC7EHJ<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/17/2016 2:25 PM, Andrew P. via
aprssig wrote:<br>
</div>
<blockquote
cite="mid:CO2PR16MB005977AB2FC995243D9AB824B8CF0@CO2PR16MB0059.namprd16.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>>Subject : [aprssig] APRS in-dash display<br>
>From: Lee Bengston<br>
>Date: Sun Jan 17 11:25:02 CST 2016</p>
<p>><br>
</p>
<p>>On Jan 17, 2016 12:24 AM, "Greg D via aprssig" <<a
moz-do-not-send="true" id="LPlnk166402"
href="http://www.tapr.org/mailman/listinfo/aprssig">aprssig
at tapr.org</a>> wrote:</p>
<p>>><i> Hi folks,</i></p>
<p>>><i> Picking up on a thread I started a while back...
Not sure if this will</i></p>
<p><i>>> </i>lead to something permanent or not, but I
tought I'd give it a try.</p>
<p>>><br>
</p>
<p>>><i> I got access to the back of my car's in-dash
unit, and the video</i></p>
<p><i>>> input </i>connector. It's meant for use with a
back camera, which I</p>
<p>>> currently don't have (though it's on the wish
list...). Found a VGA</p>
<p>>> to RCA adapter box, and fired up APRSIS32 which was
loaded </p>
<p>>> on a small laptop. Here's the result:</p>
<p>>><i> <a moz-do-not-send="true"
href="http://home.wavecable.com/%7Eko6th/aprs_dash_display.jpg">
http://home.wavecable.com/~ko6th/aprs_dash_display.jpg</a></i></p>
<p>>><i> <a moz-do-not-send="true"
href="http://home.wavecable.com/%7Eko6th/aprs_laptop.jpg">http://home.wavecable.com/~ko6th/aprs_laptop.jpg</a></i></p>
<p><i>>></i><br>
</p>
<p>>><i> Given the difficulty, if not questionable
legality, of controlling a
</i>GUI-based</p>
<p>>> laptop while driving, I think the next steps need to
include:</p>
<p>>><br>
</p>
<p>>><i> 1. Replace the laptop and VGA adapter with a
Raspberry Pi. VGA output</i></p>
<p><i>>> </i>is built-in, also much better power draw and
small size. (The car is a sports</p>
<p>>> car, so no room for anything bigger.)</p>
<p>> I think you meant RCA is built in, right?</p>
<p>><br>
</p>
<p>>><i> 2. Replace APRSIS32 with YAAC (for Raspberry Pi
compatiblity).</i></p>
<p><i>>></i><br>
</p>
<p>>><i> 3. Probably still need a keyboard for full
control while parked, but add
</i>some</p>
<p>>> fixed key switches tied to keyboard shortcuts for
the common stuff while driving.</p>
<p>>> During the earlier exchange, Andrew figured it was a
"simple" matter of a Java</p>
<p>>> library to bridge the swtiches to keyboard
shortcuts... Hope he's right.</p>
<p>>><br>
</p>
<p>>><i> 4. The Pi will boot itself when the car turns on,
but I need a way to</i></p>
<p><i>>> </i>automatically safely power down the Pi when
I turn the car off. Any ideas on this?
</p>
<p>><i> </i>A lot of vehicles don't shut the radio off
immediately - will eventually time out - and</p>
<p>> many will shut off once you open the door. You could
source the power from a</p>
<p>> source that doesn't shut off right away and buy yourself
time to shut down gracefully.</p>
<p><br>
</p>
<p>>Sounds like fun - my truck has a backup camera that I
would not want to be without. :-)</p>
<p>>Lee - K5DAT</p>
<p><br>
</p>
<p>This is a project I've been fiddling with for a couple years,
since I acquired a motor home. However, after a couple years
of driving "the moose", I don't think I want to give up the
backup camera video monitor, because:</p>
<p><br>
</p>
<p>1. The monitor is tiny and black and white (the motor home is
an old 2005 model and actually has a 6" CRT monitor, not a
LCD/LED one).</p>
<p><br>
</p>
<p>2. Driving a vehicle that large and awkward with all the
lunatics on the highway, I want all the views I can get of
overtaking maniacs so I can be ready for them.</p>
<p><br>
</p>
<p>However, I could defeat the ignition power interlock for the
main TV set (above the windshield) and hook a Pi onto that
larger monitor (and I've been looking at replacing that old
CRT TV with a flat-screen 12v set anyway), so I could have the
Pi view up there.</p>
<p><br>
</p>
<p>The Pi4j library (<a moz-do-not-send="true" id="LPlnk158343"
href="http://pi4j.com/">http://pi4j.com/</a>) provides
Java-language access to the GPIO pins on the Pi, including
supporting I2C; as an exercise for the student, I wrote a
non-published plugin for YAAC (based on the provided sample
plugin) that would copy the text of incoming messages to one
of those 16x2 LCD displays that connect to the GPIO pins.
Using the same library, you could have YAAC listen to button
pushes on one of the Pi daughterboards that provides user
input (the LCD module I had also had a few buttons on it, but
in places mechanically awkward to put in a project box), and
convert a button push into the equivalent of clicking on a
menu entry (by calling the actionPerformed() function on the
desired menu entry or GUI widget, such as the zoom in or zoom
out buttons).</p>
<p><br>
</p>
<p>Regarding power, I have already had to replace the CD-eating
broadcast-band radio in the motor home's dashboard anyway, so
I know I have multiple power source wires in the dashboard,
some direct from the engine starting battery, some
ignition-switched, and some from the coach (RV appliance)
battery bank. Not sure what kind of "safe" you need for
powering down the Pi; I usually just pull its power cord,
although I suppose it should have a proper power cycle and
"poweroff" command for flushing disk caches from writing the
YAAC log files; you could figure that out with a GPIO pin
connected to switched power (through an appropriate voltage
divider so you don't fry the Pi), and using one of those timed
poweroff devices that are sold to protect your battery from
being overdrained by your ham radio rig when the ignition is
off (just make sure the time is longer than the interval
needed for the Pi to shut down) to feed the power to a
12v-to-5v converter for the Pi.<br>
</p>
<p><br>
</p>
<p>I have found a few tiny (approx. 6" long) Bluetooth
keyboard/mouse gadgets that work well with the Pi over the
WiPi USB plugin, so you could shove said keyboard in the door
pouch and pull it out when needed (i.e., when parked).</p>
<p><br>
</p>
<p>I've mostly been delayed on this project by trying to figure
out how to wire an anemometer on the roof of the RV without
putting more leaks in the roof, having the anemometer
destroyed by the first low-hanging tree branch I pass, or
wrecking the interior trim trying to get the anemometer wiring
back to the Pi at the dashboard.</p>
<p><br>
</p>
<p>I strongly recommend using the Pi 2 for this project, as YAAC
is not a very fast renderer of streets on a Pi (despite all
the effort I've put into making the street renderer faster);
you'll need all the CPU power you can get.</p>
<p><br>
</p>
<p>Just my $.02.</p>
<p><br>
</p>
<p>Andrew, KA2DDO</p>
<p>author of YAAC<br>
</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>