openrcforums

OK, sorry. If you want to try again later, just ask for. If you want, I could make some change to the code in order to force the sensor to send always a dummy value. If you Tx receives this value, then at least you should know that the communication works. The issue would then be in the way the RPM ...

On this forum, you can upload your files as attachement if you can't easily make a copy/paste in the body.

It is a good point that you continue trying to solve your issue. In your last post there was only one file content. I had expected that you would put 2 files (oXs_config_basic.h and oXs_config_advanced.h) In order to make it easier, I put here the 2 files that you should use. I already edited the &q...

OK. No problem at all, It is your choice.

If you want to try again later, just let me know.

For info, as said, it is possible to edit the 2 files outside of arduino IDE and then to compile.
So it would for sure be possible to find a solution.

On my Dell Vostro 220 computer running Linux Mint 19.1, I am able to open the Arduino IDE by clicking on the openxsensor.ino file. Then I find the tabs. However, the tabs for the basic and the advanced files are not present! Lots of other tabs are offered but not the ones required. Mysterious! It n...

I think I begin to understand your mistake. It seems you try to put every thing inside one single file (with a function setup() and a function loop() at the end). This is not good. In openXsensor projects the code is spread on quite are many diferent files (about 20 or more). First check that you fo...

You edited it right.

The files provided are foreseen for a receiver that support the Frsky Sport protocol. Your D8R-11 receiver does not support this protocol. This can explain why you do not get data on the Tx. For your receiver, you have to use the Frsky Hub protocol. You have to edit the oXs_config_basic.h file. Ther...

OK.
There is no reason why you would not be able to finish the project.
You are probably just making a stupid mistake.

Look at Arduino tutorials and make exercises with basic sketches.
Good luck.

Michael, I tried that. I received a "permission denied" notification. I changed the port and tried that, with the same result. I changed the bootloader to the old bootloader, still no good. Jim. It is not clear for me when do you receive a "permission denied". Is it before compi...

In your folder, you select the file openXsensor.ino. This opens automatically the Arduino IDE with all tabs. You select the tab oXs_config_basic.h Then you do CTRL+A (to select all) and you press del (to get a blank tab). You make a copy /paste of the config_basic from my message. You select the tab...

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.

I found a bug in the program.
It was ok for Frsky protocol but not for others.
I fix it in a new version that I just put on github.
Please dowload new version and edit config files according your needs.

Here the content of the 2 files to be used: First, the content of the oXs_config_basic.h file // OpenXsensor https://github.com/openXsensor/ // started by Rainer Schlosshan and maintained by Michel Strens // This is version : 8.2.13 (22 oct 2019) //***************************************************...

In oXs_config_basic.h you have
#define A_MPU6050_IS_CONNECTED YES // select between YES , NO

Try using NO instead of YES (you do not have such a sensor; it could be that it blocks the program)

Normally oXs GPS works with Jeti.

The file that you show is a file that is normally in the "configurator". It is part of a python application that allows to generate the 2 config files (oXs_config_basic.h and oXs_config_advanced.h) being used by oXs. This file has not to be edited within the Arduino IDE. It should not be i...

Thanks for the feedback. Another user reports also some issues with the Acc data (he get values but out of range). I will look for a bug. You said you changed the INT to Pin3 = #define PIN_INT_6050 3 So I presume you solder also arduino digital pin3 to MPU6050 INT pin. Othewise, it is inconsistent a...

The documentation is given in file oXs_config_description.h It is quite long but normally you should find all informations about this project. You do not have to be able to write program to use this project but it is supposed you already know how to use an Arduino. There are many videos/tutorials on...

GRacing wrote: ↑Fri Feb 14, 2020 10:56 am You need to solder the INT(interrupt) to Digital PIN 2 of the Arduino Pro Mini clone, if you don´t do it, it will not work!!!!

Please try it....

Are you sure?
The doc (oXs_config_description.h) says that you can use pin 3 too (config file has to edited accordingly)

The GY86 has a voltage regulator (close to the hole). So, if you provide 5V on Vcc-in pin, you should get only 3.3V on the pin marked with 3.3V. The accelerometer/gyro are working on 3.3V and the GY86 has level converter on SCL and SDA signal in order to be able to communicate safely with an arduino...

Joao and Karl, I have had lots of time to think about what might be going wrong with my attempts at this project. I've tried two nano boards with the same no go result. I suspect that it is the way I am editing the code into the Arduino IDE. I will attach a screenshot of the Arduino IDE open for a ...

Now I downloaded the folder openXsensor and used it for a fresh new version and I could realize it as described by you. Now there was no more message. ...as soon as you get it right, it already works!! (the ACCY,Z,X are waked up and send datas, however only about once a minute, also the GPS didn´t ...

The oXs_config_advanced.h file that you use is not based on the file on github. It contains e.g. those lines (and more ) that have been moved to another file in the latest version. So please, use the latest version (including for basic and advanced config files #define BASED_ON_AIRSPEED 0 #define BA...

When I try to compile with the latest version on Github , it seems OK.
Please note that I the latest version , I made some change in the config file. So edit the files from this version and do not reuse config files made with a previous version.

Let me know if it still does not work.

In order to get Acc, you have to modify the config files. By default, those data are nore sent. So in oXs_config_basic.h file you have to uncomment those lines //#define ACCX_SOURCE TEST_1 // select between TEST_1, TEST_2, TEST_3, GLIDER_RATIO , SECONDS_SINCE_T0 ,AVERAGE_VSPEED_SINCE_TO , VOLT_1, VO...

I recommend using a resistor on the GPS RX pin in order to protect the GPS. I am not sure if it can support 5V. I know the some people seems not to use a resistor but I do not know if it is safe or not. When the data starts to flow, the voltage on D2/D4 will not really increase. It is a digital sign...

some more points about your tests with the "master" release:
- did you check that there where no other line in the config that asked for filling Test1 ,2 and 3 with other values than accelerations?
- if you rotate your sensor, does the accX and Y change in a logical way?

I expect that if you put the sensor quite close to a window and if you wait long enough (perhaps 5 min), the GPS could get a fix and the sensor should start sending the data

It is strange. Perhaps I introduced a bug in some changes. I do not have a GY86 to make my own tests. Could you try with an oldier release of oXs. You can try e.g. release V7. Take care that in this old release: - there is only one config.h file (but most parameters are similar) - in order to fill T...

This seems OK. I presume that you uncomented this line //#define FILL_TEST_1_2_3_WITH_LINEAR_ACC // uncomment this line if oXs has to fill TEST_1, TEST_2, TEST_3 with linear Acc And that you asked to transmit the Acc using #define ACCX_SOURCE TEST_1 // select between TEST_1, TEST_2, TEST_3, GLIDER_R...