openrcforums

Here is another log from Juergen with a documented lockout with ACCST pre2.0. Eventually combined with an unintended roll command, if you look at the pilot's reaction with aileron (blue), but it may also be a coincidence. It took 8 months to find a pilot with an affected TX and the ability to build ...

Do we know if this only applies to LBT mode or does it apply to FCC as well? Mike I've got no answer, needs to tested. It seems they have no clue about SBus. So it was an easy game for FrSky to sell them the suppressed lostframe information (until up to 3 frames in a row presumably, but I want to v...

Some news from the CRC-group ;) It seems, that V2.0.1 does not report 3 consecutive missing frames. Only the forth missing frame sets the lost frame bit. The capture was published in fpv-community from a member of the Engel testteam. https://fpv-community.de/threads/vorsicht-bei-telemetrie-verloren-...

If you do not want to build your own RX, Jumper R8 could be a good alternative to use alternative firmware. https://www.rcgroups.com/forums/showthread.php?3504875-Jumper-R8-Receiver-8-channel-PPM-16-channel-SBUS-D16-LBT-D8-compatible-firmware Btw. interesting information from Pascal regarding V2 fir...

You can fly inhouse in rangetestmode with reduced power to verify, if swamping ist causing your issue.

Juergen, don't worry about it. I only wanted to share some findings and to make clear, that people using SBus with V2.01 can not trust the lost frame information. Most users do not use it or do even not know, what it is. The few who know, have the chance now to read it here.

https://www.rcgroups.com/forums/showpost.php?p=43622233&postcount=8272 I don't think they have encrypted the data as such. I believe part of the problem (servo glitches) was due to some transmitters frequency drifting. When this happens, the receiver can have trouble decoding the data, as it is ...

Then you have bad servo. I am affraid you not undestand. If there will be bad frames and bits says signal is OK then you get bed signal for servo. But if the sbus signal is good because lost frame was reconstructed you cant get bad signal for servo. You will understand, when you see it. If the serv...

And the flight logfile with lockout in 4th session (GPS column removed - it is not my own file).

Sure. The additonal "LED" csv is in rangetestmode, where LQ was always 100% while the LED was flickering a lot.

If the issue is distance related, it is clearly not an OpenTX issue.

I do not think, this is the way it should work. Presumably I can show easily a stuttering servo, while SBus LQ is still 100%.

What is your theory for the drastical reduced frame losses? Especially considering, that this happened already with 191112 firmware?
And what does the frame loss bit in FrSky SBus represent? And why did frameloss not happen with X9D/E?

I'm happy to meet an expert

That's what I want to discuss. I think it is very unusual to have inhouse no framelosses with LBT most of the time. The idea is, that the lost frame bit does not represent the truth anymore, but the LED still does. This started with the new R-XSR/G-RX8 firmware 191112 "1.Fixed the problem of ab...

Hi guys, I would like to discuss some findings here. I'm unsure, how to interpret this. I'm not a fanboy of the CRC-story, which caused the big update. I'm watching the issue for a long time and I'm convinced it is a lockout for about 0.8s sometimes together with a wrong channel value (unwanted serv...

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

But I think those 2 lines are confusing Every line of the code confuses me, sorry (but not because of the code ;)). I've attached manually edited config files. Reference voltage changed to 3300mV and the second baro sensor in oXs_config_advanced deactivated (only, because it is very unusual to have...

Hi , I tried the compile the new oxs code with config file generated by the new configurator, and I get an error. Hi, this is a question for mstrens - it seems he is making holidays ;) When I edit the config files manually, there is no error with the actual master. Probably a configurator issue. Ca...

No need to order anything additionally. BN180 comes with 2 readymade cables. For every future flashing you have to unplug the GPS. Thus I would not solder the leads.

Yep. Nano should work and your BMP's also. But as it seems, with less accuracy compared to MS5611. You only have to change MS5611 in this line in oXs_config_basic.h: // --------- 4 - Vario settings --------- // ***** 4.1 - Connecting 1 or 2 barometric sensor(s) ***** #define FIRST_BARO_SENSOR_USE MS...

Thanks for your feedback! We had just a little issue in our german forum, where the vario was activated in the sketch, but not connected. In this case openXsensor does not find the GPS. If no MS5611 is connected, it must be disabled //#define FIRST_BARO_SENSOR_USE MS5611

I'm only the practical man, but as far as I understand the code the GPS is set not only to a faster baudrate, but also the output format is changed from nmea to UBX in oXs_gps.cpp. 0xB5,0x62,0x06,0x00,0x14,0x00,0x01,0x00,0x00,0x00,0xD0,0x08,0x00,0x00,0x00,0x96, // CFG-PRT : Set port to output only U...

Everything sounds good. I can think of 2 causes. RX and TX swapped, been there, done that. And a GPS issue (configuration for oXs fails). Beitian GPS work very well, probably it is a good idea to buy a 10$ BN180 or BN220 to crosscheck.

Here is a summary: https://openrcforums.com/forum/viewtopi ... 22#p146828
But mstrens latest oXs release has the changes by default "add num of sat and hdop as test1/2"

Seems you want to display 3 independent batteries (divided to a 1s voltage) as cell voltages of one 3s battery. To simulate this, simply change this line: #define RESISTOR_TO_VOLTAGE 30.0 , 30.0 , 30.0 into #define RESISTOR_TO_VOLTAGE 30.0 , 60.0 , 90.0 and (I hope) it will work. To reduce the risk ...

I have looked at logs and RSSI has been fine but getting this blip for a split second. not receiver signal lost but Telemetry signal lost. Still I will try the reposition of the antenna this morning. Did you fly solo or were other 2.4GHz radios active in close distance? Turning sideways may increas...

I would prefer industrial produced hardware. I like to DIY, but not with RX. An open design, with open firmware. Faster telemetry with less overhead, combining the advantages of FPort and passthrough telemetry. TX and RX with UART interface. Identical design for RX and TX module.

@carbo, I have been speaking about a new open source protocol since years. But no one really listened because of the frsky fever. :) FrSky hardware is still OK for me, only firmware and bunker mentality suck more and more. Mike's approach, to flash it's own firmware on it, was very convinceable. Of...

The more I think about it, the more I like the idea of developing an open source RF protocol.

Mike Blandford showed here, how versatile this could become: https://www.rcgroups.com/forums/showthr ... st42583371