[chirp_devel] issue #967 - add aprs beacon and message parsing

[Robert Terzi]

On 12/28/2014 12:51 PM, Angus Ainslie wrote:
> issue #967 - add aprs beacon and message parsing
>
> The FT1DR stores the APRS messages and beacons in the clone.
> This patch displays those messages in the settings tab.
[...]
> - based on the Yaesu vx8 driver

FWIW, The VX-8* also stored the APRS beacons and messages in the
clone accessible part of the email.  I never added anything to Chirp
to access it, instead using a standalone Python script.

Sean Burford explored things further and had some better APRS
parsing dump scripts (also python).  He added additional APRS menu
settings in issue #821

I don't have an FT1D to test with only a VX-8DR, but I would be
interested to see if these bits can be back ported to the VX-8(D).

One hitch is that the memory layout for the APRS data is different
on the original non-D VX-8, and the D version (VX-8D[RE]) due
to storing 50 beacons vs. 40.  It looks like the FT1D stores 60
beacons so it will also be different.  It's been a while since I looked
but I think the reason I didn't try to add the APRS beacons/messages
to the memory structure definitions was not knowing how to handle
the layout differences between the non-D and D in the same driver.

--Rob