-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meteomodem M20 serial decoding sometimes incorrect? #384
Comments
Thanks for reporting this. Actually I see two separate issues:
|
Thank you for the quick reply. |
I have some new information. I haven't fully clarified the matter yet, but I wanted to let you know... I talked to Yannick Saindrenan (F5IKO) from France, who found the second radiosonde that I mentioned in my initial post. That radiosonde actually isn't an M20. It's a PS20 pilotsonde, which is actually a stripped down version of the M20 with no sensor arm, no parachute and no serial number sticker. Vigor G. - another guy from France that I recently came into contact with - is also investigating this issue. He contacted Meteomodem and they told him that the last part of the M20 serial number should be between 0 and 18192. Also M20 production currently doesn't exceed 8192 units per month. And since that last part of the serial number is a unit number which is assigned in ascending order beginning at zero for every new month, it's safe to say that this number should be less than 8192. |
Alright, as long as the last 5 digit number is below 8192, all decoders will produce the same serial number :) The interesting part is when it reaches that limit. After 8191, dxl will simply continue with 8192, but auto_rx will continue with 10000. Another unclear part is the "middle" number. For -2- and -3- seems like all software produces the same number, but auto_rx will never output -1- (the code is simply doing 2 + (some value 0..3)). The information I got is that the number indicates the production site (with values 1/2/3), but I have seen -1- only in old instances from 2019. |
Vigor said that factory number 1 was from a previous factory that doesn't produce Meteomodem radiosondes anymore. |
Hello,
I recently dug a little deeper into the radiosondy.info database and I noticed something that might be an issue.
Please take a look at these two radiosondes:
When comparing the data, I'm under the impression that those were not two different radiosondes. It seems to me that this was just a single radiosonde, but different stations with different softwares decoded different serials and therefore two different entries were produced in the database.
MEA061741 (209-2-61741) was exclusively decoded by stations using rdzTTGOsonde, while MEA012637 (209-2-12637) was decoded by a station using radiosonde_auto_rx.
Here is another example where this happened:
I'm not quite sure which software decodes an incorrect serial and which serial is actually correct. But I suspect that rdzTTGOsonde is decoding the incorrect one.
Greetings,
Simon
The text was updated successfully, but these errors were encountered: