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

[Marco IZ3GME]

Hi Angus
you email client have modified the structure of the patches, they can't 
be imported back to mercurial.
I'm trying to correct them to import and test but you'd better resend 
them all to the list.
Let me suggest to send them directly from mercurial via patchbomb 
instead of passing through email clients.

73 de IZ3GME Marco

On 29/12/2014 16:50, Angus Ainslie wrote:
> On 2014-12-29 03:35, Marco IZ3GME wrote:
>> Thanks Angus
>> I have a pretty new FT1DE, will try your patches later today.
>>
>> May I help you in any way with this new model? Do you want me to test
>> something?
>>
>
> Hi Marco
>
> I have an FT1DR and not sure what differences to the "E" variant are.
> One thing I think might differ is the _model string. To fix it up one of
> the variants may need to be sub-classed.
>
> line 511 in chirp/ft1d.py
> _model = "AH44M"
>
> By defining CHIRP_DEBUG in your environment, "export CHIRP_DEBUG=1" in
> Linux, the model number will get printed when you download from radio.
> If the number matches then the settings structs should line up and the
> settings will work.
>
> If the models don't match then fix up line 511 so the download will
> work. You'll also need to check whether the settings in chirp match the
> radio. If the model number differs I'd be cautious about uploading to
> the radio until the settings have been checked
>
> Things that are likely issues but I haven't tested yet:
>
> 1) setting AM or FM modes work but digital modes won't
> 2) scan settings are mostly untested.
>
> Looking forward to feedback.
>
> Angus
>
>
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>