OpenXSensor project page on google code

[RightRudder]

How does one configure for jeti? I don't know anything about jeti but I am curious how to make an oXs for jeti radios. I don't see anything in the config.help about it either.

[mstrens]

The current version on github does not yet contains the code for Jeti.
The Jeti version is just on my laptop waiting for bug fixes.
In this Jeti version, there will be a new value in the config.h file in order to let select JETI protocol instead of MULTPLEX, HOTT or FRSKY.

[MikeB]

I've received request(s) to support JETI telemetry protocol on ersky9x. Do you have details of whatthe protocol looks like?

Mike.

[mstrens]

I think there are several versions.
Here the document I used for the duplex protocol between Rx and sensor.

There is also some code available here:
https://sourceforge.net/directory/os:wi ... =jeti%20ex

and here:
https://github.com/DevFor8/Mav2Duplex

[RightRudder]

I gather from what I have read that different people have different ideas about what they want to do with Jeti compatibility. Some folks want to use oXs as a sort of hub for jeti sensors so they can use jeti sensors with taranis. Others want to use oXs as a sensor that can send telemetry to a jeti receiver.

Mike it is good to know someone still cares about Sky9x! It almost seems like openTX is openTaranis these days. I have a 9x with a sky board but I admit it mostly sits as a backup for taranis these days. I have special feelings for it though.

[jhsa]

I have a 9x with a sky board but I admit it mostly sits as a backup for taranis these days. I have special feelings for it though.

You don't know what you are missing then With some new functionality Ersky9x has for all the platforms
No way I would swap any of my radios for a Taranis, as I already have the best parts of the taranis in them, that is, gimbals and sliders. All the rest (Perhaps except the LCD) is far superior in my opinion..
You can install new hardware quite easily for example.. It's a dream

João

[RightRudder]

I'm sure you are right, I don't know what I am missing. I find it challenging to simply keep abreast of all the changes that happen just with Taranis and oXs. I put the 9x aside 'temporarily' when I got a taranis and haven't gotten back to it yet! I did upgrade the LCD display when I bought the sky board. I'll have to get back to that one day soon. It is such a cool radio now with so much more than the original 9x.

[MikeB]

I tend to actually fly using ersky9x on a Taranis, mainly so I have a specific Tx with all my models in ready to use.

Mike.

[RightRudder]

Well we are off topic and I will bring it back at the end of this post , but I didn't even know you could do that. I thought ersky9x was just a version of opentx for the hardware on a sky board. You can load it onto a taranis?

Back on the Jeti subject, I have been making my own hardware for oXs, I started doing that with something tailored toward DLG and now that I've gotten bit by the heli bug I use an oXs to trigger rescue mode in the flybarless controller which flips the heli level and climbs automatically when an low altitude threshold is crossed. The heli guys are calling this a 'hard deck' although it is really a 'soft deck' The latest version of this sensor incorporates a 40A hall current chip and has provision to monitor a 4s pack and head speed. I found it wasn't very economical to make and try to sell the boards tailored for DLG. It will likely be worse with this heli oriented board but if it could be made to work with Jeti then that brings in a larger possible market and I could see if there is any interest in making it available to others.

[mstrens]

You can expect in some weeks (or days) that oXs will support Jeti (as wel as Multiplex, Hott and Frsky).
I do not think it should be possible to support Futaba with an Arduino Pro Mini.
I think it would require another MCU like a STM32 but then a large part of the code should be rewritten.

[jhsa]

Off Topic

I thought ersky9x was just a version of opentx for the hardware on a sky board.

No, it is actually the other way round OpenTX was forked from Er9x/ErSky9x

You can load it onto a taranis?

Yes you can flash Ersky9x to a Taranis Radio.. Please check www.er9x.com

João

[cfsix50]

Hi,

Thank you for all this excellent work.
I am interested in reading airplane attitude angles from the telemetry between my Taranis QX7 and S8R receiver.

Gyro angles are measured by a GY-521 (MPU6050). I add a NEO-6M GPS sensor.
And I upload openXsensor on an Arduino Pro Mini.

• SPort - , GPS Groung, GY-521 Ground are connected to Arduino Ground,

• SPort + is connected to Arduino Raw Pin, and SPort Signal to Arduino pin D4.

• GPS Vcc is connected to Arduino 3.3V, Rx to Arduino D6 by a 10kOhm resistor, Tx to Arduino Rx by a dip switch

• GY-521 Vcc is connected to Arduino 3.3V, SDA to Arduino A4, SCL to Arduino A5, INT to Arduino D2

If I use the GPS alone my transmitter detects the GPS and shows the correct data.

Code: Select all

#define A_GPS_IS_CONNECTED      YES                // select between YES , NO
#define A_MPU6050_IS_CONNECTED      NO              // select between YES , NO

But if I select YES to connect the MPU6050 with "#define PIN_INT_6050 2" in oXs_config_advanced.h, the transmitter cannot detect openXsensor (MPU6050 and GPS).
DEBUG get this :

openXsensor starting..
milli=0
freeRam=989
End of GPS setup
FRSky Output Module: TX Pin=4
Sport protocol= 1
Initializing MPU...

It seems that initialization is stuck somewhere with no result (failed or complete).

To check GY-521 and Pro Mini, I upload MPU6050_DMP6. Data from GY-521 is correct and InvenSense teapot demo works fine.

I read many posts on these threads but find nothing about this issue. Any idea ?

[Carbo]

I read many posts on these threads but find nothing about this issue. Any idea ?

Here is an example with GY521. It is used as TX sensor, but it does not make a difference, which SPort it is connected to.

http://openrcforums.com/forum/viewtopic.php?f=86&t=9412

[cfsix50]

Thank you Carbo,

When i tried with a S6R neither my sensor nor the LUA-script worked. When i changed the sensor ID from 0x1B (28) to 0x67 (8) everything worked.

In oXs_config_advanced.h the sensor ID is correct.

Code: Select all

#define         DATA_ID_ACC    0x67  //          7 used for Acc X, Y, Z

The question is why initialization process stop somewhere ?

[Carbo]

The question is why initialization process stop somewhere ?

Usually because i2c does not work. Did you swap SDA and SCL by mistake?

[cfsix50]

Sorry, transfer this to new thread

[michel49]

Hi,

Is there a way to build a simple 12S Sport voltage sensor ? that doesn't exist in FrSky range

[mstrens]

Hi,

Is there a way to build a simple 12S Sport voltage sensor ? that doesn't exist in FrSky range

Do you want to get the voltage of each individual cell or only the voltage of the 12S.
With oXs you can't get the voltage of each cell but it is easy to get the total voltage (just using a voltage divider with 2 resistors)

[michel49]

Thanks mstrens, I just want to monitor the pack voltage; could you tell me which electronics to use ? I just know the vario board.

[kalle123]

You have been through this here?

oXs_config_description.h

A very comprehensive description about oXs.

For your task, chapter 6

**** 6 - Voltage measurements and current sensor settings (optional) ***************************************************

br - KH