M20 position parsing

[Medvidas]

Hi Dave,
it looks like the M20 position and altitude data (from TTGO RDZsonde source) are not correctly parsed.
The corresponding data string on History screen looks ok.
See screenshot for details.
Regards

[daveake]

Thanks, that's an odd one as the formats don't differ by much. I'll take a look. Can you grab the data as text and send it to me? Just to save me typing it in from the screenshot. Dave

…

On Thu, 25 May 2023 at 17:46, Medvidas ***@***.***> wrote: Hi Dave, it looks like the M20 position and altitude data (from TTGO RDZsonde source) are not correctly parsed. The corresponding data string on History screen looks ok. See screenshot for details. Regards [image: M20parsing] <https://user-images.githubusercontent.com/57909431/240981162-b052512a-ad8f-4860-95bd-478ed2881061.jpg> — Reply to this email directly, view it on GitHub <#16>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIGQ5G7Q5IZPFYOQQ3KYHDXH6EH5ANCNFSM6AAAAAAYPDLBW4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Medvidas]

I did not found the way how to export the data frob HAB Base, so I OCR it:

ME9A03859131828h5059.37N/01645.06E0314/004/A=112735!ws&!Clb=-59.0m/s 403.000MHz T - =M20 ser=203-2-03859 rdzTTGOsonde
ME9A03859131827h5059.37N/01645.06E0308/006/A=112927!wG7!Clb=-56.2m/s 403.000MHz Type=M20 ser=203-2-03859 rdzTTGOsondeeL 50950481 *130328h4921.60N/01706.35E0166/005/A=074255!wtqC1b=-30.4m/s 402.100MHz Type=RS41 rdzTTGOsondeY S0950481 *130320h4921.62N/01706.35E0174/007/A=075058Mclab=-30.1m/s 402.100MHz Type=RS41 rdzTTGOsonde • 50950481 *130319h4921.62N/01706.35E0186/006/A=075155!wodab=-30.4m/s 402.100MHz Type=RS41 rdzTTGOsonde❑. 50950481