openrcforums

A4 and A5 (i2c bus) is OK for both. They are differentiated by the i2c adress.

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

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

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 simula...

Airspeed is not foreseen in hub-protocol. It should be possible to send airspeed using other fields like T1. But it is not prepared. It is eventually much easier to flash D-RX with D16 firmware: https://www.rcgroups.com/forums/showthread.php?3391195-FrSky-D16-firmware-for-D8-receivers&perpage=20#pos...

Your MS5611 seems to be OK since your VSpd (not compensated) is calm. Your MS4525 airspeed data seems also OK. Running the attached V4.0 firmware should result in a similar compensated VSpd with low noise (+/-0.1m/s). To crosscheck again I can flash the sketch you used in your test and report back. ...

This is a logfile with V4 I've just made. SC is switching between not compensated (1) and compensated VSpd (-1). There is +/- 0.1m/s noise in compensated mode (when airspeed is about constant) and no noise in not compensated mode. Sensitivity was 60% and compensation 110% in this case. If you test w...

You are right. I've crosschecked with the 2016 version and compensated VSpd is indeed not useable. Now I remember I was using this version for glider performance measurement only. Then I've flashed back to 4.0 and everything worked as foreseen. Seems the newer versions are missing some filtering for...

Presumably you should test an older known working version now. Please find attached a 2016 oXs sketch which should work with your configuration out of the box. 2016 there was only one config file (config.h) but you will see a similar structure.

With the sensitivity dialed down to 20, airspeed fixed at 38kts with a syringe (but still fluctuating, might indicate a problem with the sensor), compensation at 82%, vspeed jumping between -0,4 and +0,4 m/s Hmm, there is something wrong, airspeed and VSpd should be stable in your setup, even with ...

At rest, no airspeed, I get readings between zero and roughly 6. This is pretty normal. Variation decreases exponential with increasing airspeed. Imo it is better to simulate airspeed inhouse with a static pressure applied to the dynamic port of the MS4525. Vspeed should be nearly deadcalm inhouse ...

It is actually not intended that way. #define VSPEED_SOURCE FIRST_BARO selects standard VSpeed from first physical baro sensor. MS5611 in your case. #define VSPEED_SOURCE AIRSPEED_COMPENSATED selects airspeed compensated VSpeed #define VSPEED_SOURCE PPM_SELECTION allows to switch between the two VSp...

This is strange. Airspeed data should not change at all if the vario data source is changed. Please upload your config files.

What I want to look into is sending out a telemetry value with the name "compensation" and send the exact value, so I can read it on my X10S radio directly. There are two different ways imo: Activate #define FILL_TEST_2_WITH_PPM_AIRSPEED_COMPENSATION and transmit TEST_2 in a T1/T2 field and change ...

oXs is able to send PWM (PPM) back in a telemetry field. T1 or T2 is a good choice. With a suitable offset and ratio OpenTX should show compensation % directly. On my side I was happy with the PWM value since I adjust compensation acoustically. But you are right, it is smarter to convert it in compe...

Only these lines are needed for your purpose: #define AIRSPEED_RESET_AT_PPM 100 //send a pwm signal +100% to reset airspeed before start #define COMPENSATION_MIN_AT_PPM 60 #define COMPENSATION_MAX_AT_PPM 90 #define COMPENSATION_PPM_MIN 80 #define COMPENSATION_PPM_MAX 140 Compensation is adjusted wit...

123jhe wrote: ↑

Sat Nov 21, 2020 11:13 am

The expected behaviour would be: braking is starting from the camber position of the phase the glider was in before entering brake.

In order to avoid the rapid up and down, you can set the trigger point for the landing phase so that there is never an upward movement due to the switchover.

Hi John Yes, third board is an Arduino pro mini 328 16MHz. It is also possible to use an Arduino Nano which has USB onboard with only a little weight and size penalty. Nano is preferable for beginners if size is negligible. If you are only looking for a 100A sensor without the need of 0.02A resoluti...

A 100pF ceramic cap connected to (D)8 and GND solved a similar issue for me. Interference was presumably caused by RX telemetry. OpenTX filtering should not be neccessary imo.

There is an (useless) A2 voltage in telemetry, but FrSky RX8Rpro have no AIN2 port at all. Where did you connect FBVS-01?

Indeed there is only one slot for current data. But a few for voltage. A workaround is to scale and transmit the voltage output of a 2nd current sensor and change unit and name in OpenTX later.

I consider the following approach: - Setup a calculated sensor from the (Alt) telemetry value. A calculated value (called "Rate") of type "distance" in meters. - Setup a timer, that triggers every minute (for one second). - Setup a function on the start of that timer edge to playvalue "Rate" and im...

Don't worry. It is nearly impossible to damage a iXJT in this context.

https://www.reichelt.de/emi-suppression ... 07635.html
https://fpv-community.de/threads/tod-de ... 12s.79885/

Good luck. Viel Erfolg

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,...

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 , BMP18...

255 is perfect, since it is 2.55 * 100
The ratio for factor 1 is:

Precision 0 --> 255 (Temp)
Precision 1 --> 25.5 (e.g. Current)
Precision 2 --> 2.55 (e.g. Acc)

Took me some years to find out

I want to add my last personal episode with FrSky. I'm testing my gear intensively, because I can not afford any mistakes where I fly. I've flashed v2 to have a first impression inhouse. I know what RSSI and frame loss I can expect. My first thought was, wow what a progress in link quality. At the s...

As the oldest looking in this forum I want to say, that a lot of people are very grateful, for the work some smart people are doing for the community. Without people like the OpenTX devs, Mike, mstrens, Pascal I would for sure not fly RC anymore. It is a lot of fun with you all! Keep going please.

midelic wrote: ↑

Tue Jan 28, 2020 8:49 am

Yes I continued,and I will continue .ABout V2 if will be cracked probably will be added as 4-th protocol on my rx.

I will check merciless, if you also manipulate lost frames with your V2