Some comments...
On Fri, Sep 19, 2014 at 9:55 AM, K7ADD <
very...@gmail.com> wrote:
> Build:
> I was surprised by the mass of the unit.  That's a big battery, given the
> size of the case.
> Build quality was predictably poor.  The case is effectively a silk-screened
> project box.
 I'm actually pretty happy with the case. It's aluminum, but with a
plastic top to let GPS signal in, and a plastic bottom to let
Bluetooth through. The respective antennas are mounted flush to the
plastic, so I had no trouble getting signal through the case. The GPS
works indoors.
https://dl.dropboxusercontent.com/u/8174/2014-09-18%2015.10.18.jpg
https://dl.dropboxusercontent.com/u/8174/2014-09-18%2015.13.54.jpg
By the way, mine is branded AP510. I think this may be a newer
revision than the AVRT5. My photos of the circuit board definitely
show some changes compared to the photos on the website.
> Unit came with battery discharged, but contained a surprisingly heavy
> mini-USB cable.
My battery arrived at 3.7 volts. The recommended storage level for
Li-Ion is 40% (~3.5 volts).
The mini-USB cable is actually a USB-serial cable with USB connectors.
The bulky part houses the USB-serial chip. The 5V and ground pins on
the cable are standard USB, so any charger with mini-USB will work,
but the data pins have serial data, not USB. (I didn't check levels,
but 5V TTL would not surprise me.)
I used the driver linked here in the MediaFire download:
https://www.youtube.com/watch?v=qmtVvKav_LU
> Software is functional, if not polished. Little things that you'd expect
> from more mature software are just missing, for example trailing zeros are
> required on frequency field.
> Setup was pretty quick, given the YouTube video and info on the Yahoo group.
As you mentioned, the software has some idiosyncrasies, but this video
does a good job explaining them.
> Overall impressions:
> Would not recommend, given the plethora of alternatives available.
> This falls into roughly the same class as the Trackduino and is much less
> ham-chic than a homebrew kit.  :)
I am hoping the AP510 hardware can be flashed with some open source
software like the Truckduino project. I haven't done enough reverse
engineering yet to determine if the tone generation is done in a
compatible way--that's the part I really don't want to reinvent
myself.
I have been waiting for perfect hardware for tracking SAR teams. My
requirements are:
1. Some sort of tracker, not necessarily APRS
2. Built-in VHF transceiver
3. Internal battery with 12+ hours life
4. Built-in GPS
5. Decode / plot on map (GPS or smartphone)
6. Digipeat capability
7. Small / lightweight (SAR teams don't like being told to carry extra stuff)
Bonus:
8. Waterproof
9. Frequency agility in the field (no computer)
10. Bluetooth serial for viewing other teams' location on smartphone.
I have a Kenwood TH-D72 and it comes very close to all these points. I
only get about 6 hours of battery life, which isn't enough for many
SAR missions. It's also complicated and expensive, which isn't an
issue for me because I like playing with radios, but it's not a great
choice to hand to a typical searcher.
For everyone else, the AP510 is a perfect form factor. It's a black
box with one button that fits in the palm of my hand. It hits all
points except #8, and it's cheap. My biggest concern is the low power.
I'm going to try testing it again this weekend in a quiet, wooded
valley typical for SAR.
I should mention the Micro-trak AIO. It's a similar product to the
AP510, though much bigger (with 8x the battery life, naturally) and
lacks a receiver. This eliminates of bunch of the features I want,
like digipeat. With the Micro-trak, I would have to make sure the team
that is searching the ridge is issued an alternative tracker that can
digipeat (so we can hear the other team on the far side of the ridge).
It's also twice the cost of the AP510.
Some other solutions, like Garmin Rinos and Astros come close and I'm
seriously considering writing a grant for a pile of them. If you have
any other suggestions, I'd like to hear them (maybe in a new thread).
> A Raspberry Pi with a bluetooth dongle and aprx is the next experiment.  I'd
> love to have APRS data off on our local repeater's health (battery voltage,
> solar panel stats, COS duty-cycle. etc) and this might be the thing to do
> it.
I'm currently testing an RPi igate. Originally, I had the RPi running
two TNCs from the same audio feed: the internal TNC in a Kenwood
TM-D710, and a Dire Wolf soundcard TNC running on the RPi CPU. Dire
Wolf consumes about 50% of the RPi CPU decoding 1200 baud APRS. I've
since moved Dire Wolf to a more powerful PC to see how that affects
decode rates. A typical serial TNC and aprx don't stress the RPi at
all.
Dire Wolf: 
http://aprs.fi/info/a/KD7LXL-10
Kenwood: 
http://aprs.fi/info/a/KD7LXL-11
Bottom line: Dire Wolf decodes a lot more packets than the Kenwood TNC.
You might consider sending your repeater telemetry over HamWAN. The
hardware is similarly priced to a VHF transceiver, TNC, and antenna,
but you'll get a lot more bandwidth out of it. If you need the typical
cavities and isolator for VHF, the 5 GHz HamWAN link starts to look a
lot more economical. It would also leave the possibility of fancier
TCP/IP linking and control systems. If you wanted, you could install
both VHF and HamWAN for an igate at the repeater site.
https://www.hamwan.org/t/tiki-index.php
Tom KD7LXL