openrcforums

Endorphin wrote: ↑Thu Jan 09, 2020 11:40 am Is this unit compatible with "D" series receivers?

Yes. You can change this line (oXs_config_basic.h):

// --------- 1 - Telemetry protocol ---------
#define PROTOCOL FRSKY_SPORT // select between FRSKY_SPORT , FRSKY_HUB , FRSKY_SPORT_HUB
into
// --------- 1 - Telemetry protocol ---------
#define PROTOCOL FRSKY_HUB // select between FRSKY_SPORT , FRSKY_HUB , FRSKY_SPORT_HUB
for D-series RX or
// --------- 1 - Telemetry protocol ---------
#define PROTOCOL FRSKY_SPORT_HUB // select between FRSKY_SPORT , FRSKY_HUB , FRSKY_SPORT_HUB
to autodetect the protocols SPort and Hub (D-series)

Endorphin,
Take a look at the OpenXsensor config_description file.
You need to select the correct protocol for the radio system/receiver type used.
By default this is set to SPORT for SBUS compatible receivers.
The D8 receivers use the FrSky Hub protocol, so you ideally need to use the HUB protocol option.
The SPORT_HUB option is intended to allow the same sensor to be used on SBUS and Hub protocol receivers, but is not guaranteed to always work on Hub type receivers according to the description file - try it and see.
PeterB

Thanks Carbo and Peter.

[Not Working]
Hi,
I have build this gps with a Pro mini 5V/16 MHz and BN-220, but this don't work OK.
The sketch OpenXsensor + lib is that of 01 june 2019.
Compile is OK (of course) and upload also OK.
I use for the test a FrSky X6R through SPORT , OpenTX 2.3.4 on X12S transmitter and a fresh created model, so no telemetry sensor history.
(note That the GPS is the only sensor on the SPORT!)
I have on BN-220 both blue en red led flashing (so assuming a fix) and even waiting then several minutes.
On telemetry discovery , i have (beside RSSI & RxBt)
AccY ID 231
AccX ID 231
VFAS ID 226 ??
But NO GPS nor coordinates data

A test with a FrSky X8R receiver, GPS on SPORT and a FrSky X9D transmitter show exactly same results.
A second GPS build with another mini pro build module show exactly same results.
(A genuine FrSky GPS SPORT gives correct coordinates in telemetry.)

I red here "If no MS5611 is connected, it must be disabled //#define FIRST_BARO_SENSOR_USE MS5611"
Does this apply in my case? (no ref to this #define found in the sketch?)

Any idea is welcome
Thanks

In sketches from this thread MS5611 is enabled by default. In this case oXs will not find a GPS until the baro was found during startup. If you do not connect a MS5611 then this line in oXs_config_basic.h:
#define FIRST_BARO_SENSOR_USE MS5611 // select between NO_BARO , MS5611, GY86 , BMP085 , BMP180 , GY87, BMP280
has to be changed into:
#define FIRST_BARO_SENSOR_USE NO_BARO // select between NO_BARO , MS5611, GY86 , BMP085 , BMP180 , GY87, BMP280
and it should work.

Bernd

@ carbo
Thanks for this quick reply.
I replaced in oXs_config_basic.h with
#define FIRST_BARO_SENSOR_USE NO_BARO // select between NO_BARO , MS5611, GY86 , BMP085 , BMP180 , GY87, BMP280
And it's working OK.
(nb: i did try before with oxsConfigurator and protocol FrSky , only GPS activated, but that gives compile error)
Your help was appreciated, Thank's
Dan

I'm also using a fork from the original LUA widget from Hobby4life https://github.com/Hobby4life/Lua-GPS-Widget
you can find it here (see member "Phaedra" ) https://www.modelbouwforum.nl/threads/g ... 48/page-6
I want the GPS update to be as fast as possible.
So, am I right that to have a GPS rate at 5 or 10 , I have to use U-Center to modify BN-220 and adapt rate in openXsensor sketch?
Thanks
Dan

DanD3 wrote: ↑Mon Feb 10, 2020 8:45 am So, am I right that to have a GPS rate at 5 or 10 , I have to use U-Center to modify BN-220 and adapt rate in openXsensor sketch?

No, it's easier. You can simply change this line in oXs_config_advanced.h (see 9 - GPS):
#define GPS_REFRESH_RATE 5 // rate at which GPS sent new data; select between 1, 5 or 10 (Hz)
into
#define GPS_REFRESH_RATE 10 // rate at which GPS sent new data; select between 1, 5 or 10 (Hz)
that's all. Btw for my gliders 5Hz is already overkill

Bernd

Thank you vey much, Carbo.
I think i'm all set by now
Regards,
Dan

Hi
Is there any chance to get the information what had to be changed to get it running with Telemetry Viewer?
What's the different in S.port information/protocol between Standard Frsky and this version.
Regards Chris

ChrisOhara wrote: ↑Mon Feb 01, 2021 12:02 pm Hi
Is there any chance to get the information what had to be changed to get it running with Telemetry Viewer?
What's the different in S.port information/protocol between Standard Frsky and this version.
Regards Chris

Hi,
here is a complete sketch, ready to flash. T1 and T2 are manipulated to simulate a GPS fix and transmit number of sat in iNav way. Do you need to know the changes in detail?

https://openrcforums.com/forum/viewtopi ... 07#p145962

Thanks for the quick response.
Yes I would like to know the details.
To be honest I have already a GPSlogger2 and would like to find a solution to adapt it.
regards Alois

T1 = 4 (armed)
T2 = 1000 + number of satellites

https://github.com/iNavFlight/inav/blob ... lemetry.md

Hi Carbo
thanks a lot
Stephan Merz of SM-Modellbau made a Testversion for my GPS-Logger2 with the changes.
First test with "Telemetry Viewer" was great.
If there happens to be no negative effects in the test version he will put it in the next official update
regards Alois

Hi Carbo
I have ordered the parts now.
Having no sensor for pitch and roll there will be no artificial horizon?
If that's the case would it be possible to get the horizon by adding a MPU-6050 as a third board to the Arduino Mini?
https://frsky-forum.de/lexicon/index.ph ... enxsensor/
Did you try?
regards Alois

Ps: or would it be possible to use GY-87 instead GY-63 baro/Mpu-6050 ? Big changes to code??

https://www.christians-shop.de/GY-87-10 ... aerendruck
https://www.christians-shop.de/GY-87-Mu ... inem-Modul

Did read some code now. Looks like iNav has two additional values.
(I've made a test with a simplesensor program with 0x0440 and a dummy value. It worked, see picture)
0x0430 : if frsky_pitch_roll = ON set this will be pitch degrees*10
0x0440 : if frsky_pitch_roll = ON set this will be roll degrees*10
https://github.com/iNavFlight/inav/blob ... lemetry.md

Udate:
If did some test-programming with the software.
I think I can manage the changes on my own.
Will come back with a feedback in a few weeks (parts to test may arrive mid of march earliest)
Regards Alois

Hello
Short feedback. I have made my first testflight wie my software extensions.
It is looking promissing. Artifical horizon is working in "Telemtry viewer APP" and in "INAV Lua Script".

I've added the following telemetry values (calculated in OpenXsensor):

distance, pitch, roll, yaw (in INAV syntax)
distance covered in 2D (over ground)
distance covered in 3D

Regards ChrisOHara

Hello.

I read this instructions but i have one small problem.

my idea it s mount only a gps for HOTT.

1.- #define PROTOCOL HOTT // select between FRSKY_SPORT , FRSKY_HUB , FRSKY_SPORT_HUB , MULTIPLEX , HOTT, JETI
2.-#define FIRST_BARO_SENSOR_USE NO_BARO // select between NO_BARO , MS5611, GY86 , BMP085 , BMP180 , GY87, BMP280

But when verify in arduino ide i found this problem

openXsensor.ino: In function 'void calculateAllFields()':
openXsensor:934: error: 'GPS_hdop' was not declared in this scope

Any idea ?

Many thanks for this proyect

Sorry, not need answer, it s a problem of one computer, with other is ok