No Vario function ...

Development & General Chat for the superb openxvario project.

Moderator: rainer

Post Reply
Bruchpiloten
Posts: 5
Joined: Tue Jan 30, 2018 7:41 pm
Country: Europe

No Vario function ...

Post by Bruchpiloten »

Dear all,

Today I soldered an OpenX sensor together with a BMP280 sensor and a separate MCU6050 sensor.

I first checked the addresses with an I2C scanner,
the BMP280 has the address 0X76 and the MCU6050 has the
Address 0X68.

Then I loaded a test sketch for the BMP280 and the
Sensor has issued a corresponding value. See screenshot in the * .pfd file.

I did the same for the MCU6050, this one too Sensor sent the data.

So I have to say the wiring and the sensors are ok and working.

Then I configured the OpenXSensor, first just the Vario.
RC signal for the connection on D4 and the protocol on FRSKY_SPORT.
Sketch uploaded, but I don't get any Data on the Horus X12 with FrOs.
The RX voltage / RSSI goes.

I then checked the address in the BMP280 file that was
wrong with the H file. Unfortunately without success.

Then I tried to see if I could see anything in the serial monitor
but I only see the data when I want to calibrate the MCU,
but I don't see the MCU data from the 6050 either.

Slowly but surely I have no idea where the problem is
can lie. Thank you for your help in advance.

Many greetings
Willi
Attachments
OpenXsensor.pdf
Screenshots from Arduino
(730.8 KiB) Downloaded 210 times
Photos (58).zip
Images from the Hardware
(2.71 MiB) Downloaded 210 times
oXs_config_basic.h
(11.35 KiB) Downloaded 202 times
oXs_config_advanced.h
(15.73 KiB) Downloaded 197 times

mstrens
Posts: 1435
Joined: Fri Dec 27, 2013 7:49 pm
Country: -

Re: No Vario function ...

Post by mstrens »

your config files seems OK (when using both sensors).
I do not see the error.
The I2C address are OK (the adr defined in H file is not used; it seems overwritten by one in cpp file.

I am not sure the combination IMU and BMP has been tested. Normally the combination IMU and MS5611 works.
I suggest that you first try with only the BMP280 (deactivate the IMU in the config file). Do not forget than to change also to #define VSPEED_SOURCE FIRST_BARO
Then you can best try a debug mode. To do so, in oXs_config_macros.h, uncomment the line //#define DEBUG
And in oXs_BMP280.cpp, uncomment the line //#define DEBUGDATA

The Arduino serial terminal should then normally reports some values read from the BMPsensor.

Question : I presume you know that on the Tx side you have to ask to discover new sensors. They are not discovered automatically.
User avatar
kalle123
Posts: 905
Joined: Sat Mar 29, 2014 10:59 am
Country: -
Location: Moenchengladbach

Re: No Vario function ...

Post by kalle123 »

Bruchpiloten wrote: Fri Apr 24, 2020 7:49 pm ... but I don't get any Data on the Horus X12 with FrOs.
Just curious.
My personal experience with oXs is on FrSky and MPX.
Could FrOs be a problem here?

br KH
Bruchpiloten
Posts: 5
Joined: Tue Jan 30, 2018 7:41 pm
Country: Europe

Re: No Vario function ...

Post by Bruchpiloten »

Good evening,

Many, many thanks to everyone for your help and ideas.

Well, FrOs, which I use, knows no sensor search and
just take the fixed addresses. It is also not possible
(at the moment) to use other sensor addresses.

Then I took the MCU6050 out of the configuration,
but the baro / vario sensor still didn't work.

Then I programmed the DEBUG mode, and then I
had a compile error as soon as I got the BMP280.ccp file too
had changed.

Somehow I was without an idea again, but then I looked
in my sensor warehouse and found another BMP280 board.
I soldered this BMP280 to another Arduino, the Sketch
and renewed and reconfigured the config files. I load the
Sketch in the new "sensor world" and lo and behold, the sensor goes
and I see the altitude on the transmitter, the Vario signal too.

Is the other, original Arduino broken now? Then I have that
tried individual test sketches again that worked.
I then decided to unsolder the MCU6050 and
the sensor now worked without reloading anything.
But what had happened? I have no idea why this is so now.

In conclusion, I have to assume that the software from
Despite the deactivation, OpenXsensor sees the MCU6050 sensor
and does what, only not what is actually intended. I think the
Software specialists may have an idea if you think about it.

I have now ordered new GY-86 boards and will report.

Many greetings
Willi

Post Reply

Return to “OpenXVario - an open source vario supported by the open source firmwares!!”