Telemetry Parser

[EA5AER]

Hi:

I've seen that the packets of telemetry are still not supported for parse. For any reason? I say that because telemetry.py has already parse_comment_telemetry that will do more or less the job.

If a force parse_comment_telemetry for this beacon:
DEBUG:aprslib.parsing:Parsing: ED5YAM>APTT4,EA5RCD-15,WIDE1,WIDE2-1:T#790,551,564,999,085,716,11000000*
DEBUG:aprslib.parsing:Parsed ok.

i will obtain this:
{'raw': u'ED5YAM>APTT4,EA5RCD-15,WIDE1,WIDE2-1:T#790,551,564,999,085,716,11000000', 'via': '', 'from': u'ED5YAM', 'to': u'APTT4', 'path': [u'EA5RCD-15', u'WIDE1', u'WIDE2-1'], 'format': 'beacon', 'text': u'T#790,551,564,999,085,716,11000000'}**

This is better than obtain:
Mar 15 14:42:54 MonitorAPRS sh[563]: File "/usr/local/lib/python2.7/dist-packages/aprslib/parsing/init.py", line 162, in _try_toparse_body
Mar 15 14:42:54 MonitorAPRS sh[563]: raise UnknownFormat("format is not supported")

[rossengeorgiev]

Comment telemetry format is different. Telemetry report is not implemented, since I never needed it. I may implemented it soon™

[Charlie-Gale]

It looks like something was done to address this, but when I try to use it nothing is returned:
DEBUG:aprslib.parsing:Parsing: VY1CC-3>APOT30,WIDE2-2,qAR,VY1YC-1:T#057,487,000,000,000,000,00000000
then nothing else, not even an exception.
Compared to:
DEBUG:aprslib.parsing:Parsing: VY1YC-1>APMI06,TCPIP*,qAS,VY1RC:@031728z6045.13N/13505.86W-WX3in1Plus2.0 U=16.3V
DEBUG:aprslib.parsing:Parsed as normal position report
DEBUG:aprslib.parsing:Parsed ok.