Code Monkey home page Code Monkey logo

Comments (14)

rs1729 avatar rs1729 commented on September 26, 2024

Yes, I know Vaisala M211486EN-C:

RS/demod/mod/rs41mod.c

Lines 791 to 793 in 35136f9

static int get_Aux(gpx_t *gpx) {
//
// "Ozone Sounding with Vaisala Radiosonde RS41" user's guide

I didn't have plans to decode the raw aux data. Also sometimes there are several instruments attached to the RS41 (have seen up to 3 aux-strings per frame); don't know if this wouldn't be too much output. Maybe it could be optional similar to the sat data.
Will think about it.

from rs.

JRus-design avatar JRus-design commented on September 26, 2024

Yes, some stations, like Payerne (CH), can launch several instruments connected in chain, normally the first is OIF411 Ozone sensor from Vaisala (Id05), and connected to it the Cobald Backscatter Aerosol Detector or to the Cryogenic Frostpoint Hygrometer. Each sensor has an identifier and a chain number in the Xdata packet.
Attached documents to decode Cobald Backscatter Aerosol Detector (Id19) & daisy chain sensor connection.
GRUAN-TN-8_GRUAN-Monitor-MW41_01.pdf
CobaldOperationInstructions2017.pdf
iMet-1-RSB Radiosonde XDATA Daisy Chaining.pdf

from rs.

rs1729 avatar rs1729 commented on September 26, 2024

AUX data processing should be placed in a separate module.

from rs.

LukePrior avatar LukePrior commented on September 26, 2024

A JavaScript approach for XDATA decoding can be found here: https://github.com/projecthorus/sondehub-tracker/blob/testing/js/xdata.js

from rs.

rs1729 avatar rs1729 commented on September 26, 2024

Added basic xdata decoding, ID=0x05 (OIF411) and ID=0x01.
99d0425

from rs.

rs1729 avatar rs1729 commented on September 26, 2024

ID=0x08 CFH (Cryogenic Frost Point Hygrometer)
@LukePrior
You don't have information on this?
In https://www.gruan.org/gruan/editor/documents/gruan/GRUAN-TD-5_MeiseiRadiosondes_v1_20180221.pdf
on (p.95) it says

Table A.1: An example of the ASCII data format of the CFH sensor, for the case
xdata=0802E21FFD85C8CE078A0193 as 1-second data.
offset  bytes   description
Table A.1: An example of the ASCII data format of the CFH sensor, for the case
xdata=0802E21FFD85C8CE078A0193 as 1-second data.
offset  bytes   description
 0      1       Instrument_type = 08 (=CFH)
 1      1       Instrument_number = 02 (Second instrument in the daisy chain)
 2      3       Mirror temperature = E21FFD
 5      3       Optics voltage = 85C8CE
 8      2       Optics temperature = 078A
10      2       CFH Battery = 0193

but no derived values. Enough for raw data output, though.
I found 3 examples
https://www.gruan.org/gruan/editor/documents/gruan/GRUAN-TN-8_GRUAN-Monitor-MW41.pdf
(p.13)

CFH xdata=0803DC5EF086C244078601A5
08 03
DC5EF0 : Tmir
86C244 : Vopt
0786   : Topt   // temp optics: 34.42C ?
01A5   : Vbat   // battery    : 12.33V ?
frostpoint: 23.56C
testpoint: 2.63201V

https://www.gruan.org/gruan/editor/documents/gruan/GRUAN-TN-8_GRUAN-Monitor-MW41-and-Vaisala-RS41-Additional-Sensor-Interface_v1.0.pdf
(p.7)

CFH xdata=0802DD44D58A7B320567018E
08 02
DD44D5 : Tmir
8A7B32 : Vopt
0567   : Topt   // temp optics: 39.72C ?
018E   : Vbat   // battery    : 11.66V ?
frostpoint: 24.22C
testpoint: 2.70471V

(p.8)

CFH xdata=0802A2D58B8050FE08290174
08 02
A2D58B : Tmir
8050FE : Vopt
0829   : Topt   // temp optics: 32.83C ?
0174   : Vbat   // battery    : 10.90V ?
frostpoint: -19.15C
testpoint: 2.50618V

Vbat <-> battery <-> is not exactly linear, but close. Not sure if "testpoint" and optics_voltage are related, "frostpoint" might be derived from mirror_temperature (and other values), there might be calibration involved? And temp_optics increases with lower values of Topt? Assuming the examples are actual values.

from rs.

pavolgaj avatar pavolgaj commented on September 26, 2024

Some descriptions of measured values are in https://www.gruan.org/gruan/editor/documents/gruan/GRUAN-TN-11_GruanToolRs92_v1.0_2020-10-01.pdf (page 33). And there "FrostPoint" = "MirrorTemperature".

I found the coeficients for voltages according to examples:

  • testpoint/optics_voltage = int_value/3355443.0
  • battery_voltage = int_value/34.136

and for temperatures:

  • optics_temp = (5452.847-int_value)/102.4637
  • mirror_temp = (int_value-12362317.72)/88293.637

Where int_value is value decoded for XDATA. But, these numbers are only the results of a linear fit. I don't know if they're correct and universal for all CFH devices :(

Edit: Just tested on these data: #43 (comment). Relation for 'optics_temp' seems to be more or less good - temperatures are always close to 34C. But, the calculation of 'mirror_temp' is wrong - it returns temperature around -88C.

from rs.

rs1729 avatar rs1729 commented on September 26, 2024

More examples hidden in the GRUAN documents, thanks!
In the 3 examples above, for the Vbat quotient I got 0x1A5/12.33=34.144, 0x18E/11.66=34.134, 0x174/10.9=34.128, could be rounding errors (0.66 and 0.33 could indicate some factor 3 involved), but with this resolution I would expect a bit more.
Really strange these magic numbers, there is enough space, no need to squeeze the values. Perhaps raw values.
Don't understand why scientific instruments are not better/transparently documented... Maybe there exists documentation, but I hear CFH is closed source?

from rs.

LukePrior avatar LukePrior commented on September 26, 2024

Yeah I never found the correct coefficients for all the CFH fields so restrained from adding it to the JS decoder and wiki. If anyone can figure it out fully I would be happy to include it.

from rs.

pavolgaj avatar pavolgaj commented on September 26, 2024

I found out that RS41Tracker (http://escursioni.altervista.org/Radiosonde/) can decode also CFH data. Unfortunately, I don't have any RAW data with CFH to test.

from rs.

LukePrior avatar LukePrior commented on September 26, 2024

I reached out to the developer of that program for any information he might have about the various xdata instruments but I haven't heard anything back.

from rs.

rs1729 avatar rs1729 commented on September 26, 2024

I would prefer having documentation from the developer or manufacture of the instruments.

from rs.

JRus-design avatar JRus-design commented on September 26, 2024

from rs.

rs1729 avatar rs1729 commented on September 26, 2024

Is there a protocol description (except for the modulation parameters)?
In the new En-Sci documents I didn't find any protocol descriptions, the ECC Ozonesonde manual is an old version, not on the website.
Or maybe I just didn't see it.
EDIT:
The protocol description in the older ECC Ozonesonde manual was specific to iMet-1-RSB. I think En-Sci is not only for iMet now, but the xdata part is basically the same, hence they could describe the xdata output of the interface.

from rs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.