Closed Feuerwerko closed 1 month ago
Ive just checked some of the sonde flight log files, and they all seem to follow a very weird pattern. Humidity and Pressure are logged as -1 and temperature as -273 while the sonde is ascending. Once the sonde has burst, the pressure readout turns into a realistic value for the rest of the flight. The temperature and humidity turn to normal values a while after the burst. A little sample where you can see this behaviour:
timestamp,serial,frame,lat,lon,alt,vel_v,vel_h,heading,temp,humidity,pressure,type,freq_mhz,snr,f_error_hz,sats,batt_v,burst_timer,aux_data
...
2024-09-23T19:01:20.000Z,V1041038,9118,50.16755,8.16899,15046.5,-11.5,9.8,62.7,-273.0,-1.0,-1.0,RS41-SGP,402.699,20.3,187,10,2.5,-1,-1
2024-09-23T19:01:21.000Z,V1041038,9119,50.16759,8.16911,15035.1,-11.7,10.2,58.7,-273.0,-1.0,-1.0,RS41-SGP,402.699,20.3,187,10,2.5,-1,-1
2024-09-23T19:01:22.000Z,V1041038,9120,50.16764,8.16924,15023.9,-11.4,11.0,55.3,-273.0,-1.0,-1.0,RS41-SGP,402.699,19.9,187,10,2.6,-1,-1
2024-09-23T19:01:23.000Z,V1041038,9121,50.16770,8.16936,15012.7,-11.4,11.0,53.8,-273.0,-1.0,123.8,RS41-SGP,402.699,19.6,187,10,2.6,-1,-1
2024-09-23T19:01:24.000Z,V1041038,9122,50.16776,8.16948,15001.6,-11.2,11.1,48.9,-273.0,-1.0,124.0,RS41-SGP,402.699,21.0,187,10,2.6,-1,-1
2024-09-23T19:01:25.000Z,V1041038,9123,50.16783,8.16960,14990.3,-11.9,11.4,49.4,-273.0,-1.0,124.2,RS41-SGP,402.699,21.0,187,10,2.5,-1,-1
2024-09-23T19:01:26.000Z,V1041038,9124,50.16789,8.16972,14978.4,-12.2,11.5,49.9,-273.0,-1.0,124.5,RS41-SGP,402.699,19.6,187,10,2.5,-1,-1
2024-09-23T19:01:27.000Z,V1041038,9125,50.16796,8.16984,14966.9,-11.8,11.4,48.0,-273.0,-1.0,124.6,RS41-SGP,402.699,19.6,187,10,2.5,-1,-1
2024-09-23T19:01:28.000Z,V1041038,9126,50.16803,8.16996,14955.8,-10.9,11.5,45.5,-273.0,-1.0,124.8,RS41-SGP,402.699,18.4,187,10,2.5,-1,-1
2024-09-23T19:01:29.000Z,V1041038,9127,50.16811,8.17007,14944.8,-11.1,11.4,43.9,-273.0,-1.0,125.0,RS41-SGP,402.699,18.8,187,10,2.6,-1,-1
2024-09-23T19:01:30.000Z,V1041038,9128,50.16818,8.17018,14933.4,-11.5,11.4,44.1,-273.0,-1.0,125.3,RS41-SGP,402.699,18.8,187,10,2.6,-1,-1
2024-09-23T19:01:31.000Z,V1041038,9129,50.16825,8.17029,14922.1,-11.2,10.4,47.2,-273.0,-1.0,125.5,RS41-SGP,402.699,18.1,187,10,2.5,02:46:05,-1
2024-09-23T19:01:32.000Z,V1041038,9130,50.16831,8.17039,14910.7,-11.9,9.8,43.3,-273.0,-1.0,125.7,RS41-SGP,402.699,17.5,187,10,2.5,02:46:05,-1
2024-09-23T19:01:33.000Z,V1041038,9131,50.16838,8.17048,14899.6,-11.4,10.0,37.5,-273.0,-1.0,125.9,RS41-SGP,402.699,17.5,187,10,2.5,02:46:05,-1
2024-09-23T19:01:34.000Z,V1041038,9132,50.16845,8.17056,14888.2,-11.7,9.9,36.7,-273.0,-1.0,126.1,RS41-SGP,402.699,17.2,187,10,2.6,02:46:05,-1
2024-09-23T19:01:35.000Z,V1041038,9133,50.16852,8.17064,14876.7,-11.4,9.1,38.2,-273.0,-1.0,126.3,RS41-SGP,402.699,17.7,187,10,2.6,02:46:05,-1
2024-09-23T19:01:36.000Z,V1041038,9134,50.16858,8.17072,14865.8,-11.1,8.6,37.3,-273.0,-1.0,126.6,RS41-SGP,402.699,17.7,187,10,2.6,02:46:05,-1
2024-09-23T19:01:37.000Z,V1041038,9135,50.16864,8.17079,14854.8,-11.5,9.1,38.6,-273.0,-1.0,126.8,RS41-SGP,402.699,17.5,187,10,2.5,02:46:05,-1
2024-09-23T19:01:38.000Z,V1041038,9136,50.16871,8.17088,14843.5,-11.8,9.7,43.4,-53.2,-1.0,127.0,RS41-SGP,402.699,17.3,187,10,2.5,02:46:05,-1
2024-09-23T19:01:39.000Z,V1041038,9137,50.16877,8.17097,14832.1,-12.0,9.2,47.8,-53.2,-1.0,127.2,RS41-SGP,402.699,18.4,187,10,2.5,02:46:05,-1
2024-09-23T19:01:40.000Z,V1041038,9138,50.16882,8.17107,14820.6,-11.2,9.1,49.1,-53.3,-1.0,127.5,RS41-SGP,402.699,18.4,187,10,2.5,02:46:05,-1
2024-09-23T19:01:41.000Z,V1041038,9139,50.16888,8.17116,14809.3,-11.7,9.3,50.7,-53.3,-1.0,127.7,RS41-SGP,402.699,18.6,187,10,2.6,02:46:05,-1
2024-09-23T19:01:42.000Z,V1041038,9140,50.16893,8.17127,14798.0,-11.2,9.2,52.8,-53.2,-1.0,128.0,RS41-SGP,402.699,18.6,187,10,2.6,02:46:05,-1
So it seems like, atleast after burst the pressure is being decoded. I would guess it is actually being decoded the whole flight and just not being logged due to some weirdness. Why the log gets this data and not any other exporter is weird tho. If I understood the code, the logs are also just getting the telemetry straight from the decoder, like the payload summary generator.
Just checked the Sondehub OpenSearch dashboard, autorx does seem to be reporting pressure to Sondehub. For some reason its just not in the payload summaries.
I've only just been able to look at this.
Yes, not every field is being passed out in the payload summary message. I've just fixed this in the testing branch.
The payload summary from my autorx instance doesnt seem to be sending a pressure value even tho I am receiving RS41-SGP sondes. Here is an example payload summary packet I received with the UDP listener example script: