openrcforums

I'll remove MVARIO for next fly, and I'll change OXS configuration for scanning GPS to 10Hz.

Thanks for your help !

Thanks for your answer. I understand for GPS. I use a NEO8, I will try to update to 10Hz. But, why, during same same timelapse, OXS Vario transmits 118 entries and a Jeti Vario 580 entries ? Is there a priority for telemetry message ? Maybe a wiring trouble ? This graph can confirm : OXS's and Jeti'...

Hi all,

Sensor works, but it seems I don't have a lot of values.

For example : for a fly, I have 500 log entries for Jeti Mvario, 400 log entries for MU-3, but only 90 log entries for OpenXsensor GPS.

I use an Expander for connecting 4 sensors.

What can be wrong ?

Ok, my bad, it's working.

Original baudrate was nos correct (57600), I changed it, Send it, but not saved it into Flash memory.

After flash, I can get values after GPS Fix !

Thanks a lot, your job is awsome!

You are too fast ! I make some tests : - It's a Drotek M8N, I think it's not a fake UBLOX chip - Fix and U-Center works, with USB connector (9600) - Try to connect U-Center with FTDI, and 9600 bds : not working - With Autobaud, U-Center finds device at 57600 bds - I changed it to 9600, but what are ...

Please note that even if it compiled, I do not think it will works because it is not foreseen to transmit the TEST1,2,3 fields in the Jeti protocol. The TEST1, 2, 3 are foreseen for the Frsky protocol to reuse predefined telemetry fields for other purposes. This has not been implemented for Jeti. H...

nigelsheffield wrote: Fabe , did you test on hub or s.port?
Great work!

I made test with s.port, oXs v7.0 and vario, not GPS

Hi,

I made some flights today : everything works perfectly !

Thanks a lot

Well, I make some tests. Now it's working, I can have MS5611 temperature into transmitter ;) I use test1.value. By the way, if you comment this line, it returns a "Cel" field into SPORT : #define NUMBEROFCELLS 0 // Put this line as comment or set value to 0 (zero) if you do not want to tra...

It is strange that you did not get a compilation error using testValue = .... When I try it, I get a compilation error because this variable does not exist anymore in V7.0 As said in previous message you must now use new variable (being part of a structure (this explain the dot). test1.value = oXs_...

I find some new Values :

- test1.value
- test1Value

I need to use which one ?

I don't have any compilation error. I add these lines into readSensors function, like I do in v5.0 : #ifdef VARIO newVarioAvailable = oXs_MS5611.readSensor(); // Read pressure & temperature on MS5611, calculate Altitude and vertical speed; if ( oXs_MS5611.varioData.absoluteAlt.available == true ...

With V7.0, I can't read MS5611 temperature using TEST_1.

FrSky SPORT fields selector changed, and sensors Instance too.

Hi, I finish to tuned "ALT_TEMP_COMPENSATION" variable, with last version. It seems the ratio is about 333 for 1 meter of drift. In "oXs_config_description.h", you had a value of 1000 for 3 meters of drift. I will have to insert a value of 1400, in order to correct a drift of 4 m...

Hi mstrens,

It works ! I can read MS5611 temperature

Thanks a lot !

Thanks a lot ! As you write, I find the readSensors() function :D With v5.0, there's already somthing similar, but with test3Value : #ifdef VARIO oXs_MS5611.readSensor(); // Read pressure & temperature on MS5611, calculate Altitude and vertical speed if ( oXs_MS5611.varioData.absoluteAltAvailabl...

Hi all, I made my first OpenXsensor Alti/vario, and it's working great with X9E and X8R ! Now, I would like to send MS5611 internal temperature to T1 OXS field. I check configuration file, and I read there's some TEST var, but I don't know How To write the code, and where (maybe oXs_ms5611.h file......