Frsky compatibility

Aaaahhhhgh, problem solved indeed ican confirm AD2 voltage from D4R works......

In the FRSKY protocol button, there is a setting , multiplier factor for AD2 field. By default this is set at 0.


Basically not any Voltage being displayed.....I had to put at 59, to get moreless correct value. I have to note that setting it to 60, gave me too high voltage, setting to 59 slightly too low, so steps should be smaller to get a correct fine tune....or I have to trim my devider at RX side...
I recommend in new builds we put default at 60.

As you saw, the correct value depends on your resistor setup. Which means there is no obviously correct value. Setting it to zero is obviously incorrect, which isn't true for any other value. So I favor leaving it as is.

Just to see what happened I connected, the current sensor and cel voltage sensor to d4r-2.

I can see, 1 cell voltage displayed correctly lowesst field middle columm other cell voltages not displayed. The total voltage is now in correct. I can't see current coming in.

**********
Update default setting is 1, but with setting 1 voltage is rounded out to zero, so nothing being displayed like all other field which are not connected.
So it looks like does not work. I would expect to get at least some voltage displayed when connecting AD2. That why though not working...
A default at 60, would at least show voltage........ but anyway it is not a bug, it works.

The hub telemetry(not taking about link telemetry) in deviation is buggy.Anyway the code I've seen so far.
It shows a lack of understanding on how the received telemetry frames are handled on TX.It will never work fully as it is now.
I struggled also for a while to understand how it really works.

Fernandez wrote: Aaaahhhhgh, problem solved indeed ican confirm AD2 voltage from D4R works......

In the FRSKY protocol button, there is a setting , multiplier factor for AD2 field. By default this is set at 0.

---

cut

---

.

Which version do you use? On my Devo the lowest value is 1...at this field.

Another thing;my Tx battery voltage of devo 7e displayed is fluctuating quite a bit and not stable, don't know were it comes from. Power level setting does not matter also on lowest power it appears.
Example:5.35 - 5.46 - 5.41, the time between updates is bit random between 2 and 6sec? Can anyone confirm that tx voltage is stableon your tx?

I try to switch off telemetry, in order to see if it is related to that. But I find a bug, switching Frsky telemetry off, it is still enabled, telemetry still comes in.

Fernandez wrote: Another thing;my Tx battery voltage of devo 7e displayed is fluctuating quite a bit and not stable, don't know were it comes from. Power level setting does not matter also on lowest power it appears.
Example:5.35 - 5.46 - 5.41, the time between updates is bit random between 2 and 6sec? Can anyone confirm that tx voltage is stableon your tx?

.

No, thats normal because of switching PA/LNA chip (T212)

Edit:
To have telemetry off, you must change the protocol or do a cold start . Same with DSMX....
its not a bug, a feature....lol

aMax wrote: No, thats normal because of switching PA/LNA chip (T212)

Edit:
To have telemetry off, you must change the protocol or do a cold start . Same with DSMX....
its not a bug, a feature....lol

be warned that changing protocol will also change all the channel assignmens as well accordingly... one of the big flaw in deviation implementation

for one day in the field, I have change from devo to dsmx and back, found all the ch1... ch6 are in a mess..

cmPang

....did not discover this,....meanwhile preparing, my tx is off.
I mostly changed the protocol before power down.

aMax wrote:
....did not discover this,....meanwhile preparing, my tx is off.
I mostly changed the protocol before power down.

in Devo, I set my throttle to CH3. After switching the protocol to DSMX, deviation would change my throttle to CH1 ...

I can never figure out why the channel assignment has to follow the protocol selected...

cmPang

midelic wrote: The hub telemetry(not taking about link telemetry) in deviation is buggy.Anyway the code I've seen so far.
It shows a lack of understanding on how the received telemetry frames are handled on TX.It will never work fully as it is now.
I struggled also for a while to understand how it really works.

does it make sense to port midelics work to deviation (frsky d8 telemetry)
https://github.com/pascallanger/DIY-Multiprotocol-TX-Module
unfortunately i dont have the skills.

cheers Werner

mazi wrote: Finally I solved the problem with short range. The receiver (D8R-XP) was faulty! I got new one and it seems to be OK

aMax wrote:

mazi wrote: The module is from BG! And I tried different Fine freq values

...search function..? Two and a half years old but something you might find usefull.

www.deviationtx.com/forum/protocol-devel...ility?start=100#8446

I have tried connect PA_EN and/or LNA_EN pins of XL2500 module to Vcc, GND, GDOo or GDO2, but nothing helped Range with 150mW is still only 2m. I propably fried PA, because when I tried this module for the very first time, I noticed after while, that connection to antenna had been broken. Is it possible to somehow check it?

But why I can't bind D6R XP with the BG module? Devo doesn't report "CC2500 is missing".

Yes, it makes sense. I agree that the hub telemetry in the nightlies is buggy, and took a stab at fixing it a while back (there's a test build of that available). However, no one has been willing to test it, and my "hub" is a DIY sensor system designed for yachts, not FrSky hardware, so I can't really test it properly. When I get back to this, I'll be looking at midelic's code. But there's not much point until someone has hardware that we can use to test it.

i am willig to buy some Hardware.for testing
what do we need at least.
I want to buy a X8R with some smart port sensors (GPS, vario, 6s sensor)

I've updated the protocol_combo test build with two fixes to frsky2way telemetry that I ran across while working on frskyx. Looking at midelic's implementation and the opentx code revealed two issues with the deviation implementation: it didn't handle telemetry data split across rf packets, and it depended on certain data elements being received in order. I've tried to fix that in the combo build. I did not look at the units conversions nor the display code. I also have no way to test this - time to finish my multimodule...

Unfortunately this build does not fit on the 7e.

hexfet wrote: Unfortunately this build does not fit on the 7e.

What is this then please?
Link

djdazzy wrote:

hexfet wrote: Unfortunately this build does not fit on the 7e.

What is this then please?
Link

Sorry - posted and forgot to upload the files I've updated them now.

The Frskyx you tested is the latest. Thanks! I'll make some sanity checks. If I make changes I'll make a different test build of just frskyx for the 7e.

Good afternoon everybody.
I finally received all the hardware necessary to upgrade my devo 12S to frSky protocol.
A friend more informed that i am will do the job ; tunings to.
I am lost now in the course of discussions in the subject.
I would be sure of few datas before going forwarfd
1) Is this one the most recent file for Devo12S : deviation-devo12-v4.0.1-4fc5268.
2) in this file will I find all software necessary to add FsSkyX potocol to my devo 12S ? A tutorial somewhere ?
3) with this FrSkyX protocol will I need to use only D receiver such as the D8 one.?
4) X** one receiver in project ? by upgradind the 4.0.1 deviation ?
5) Wiil I be able to use it with an APM 2.8 in PWM or PPM sum protocol ?
Thanks for helps and answers.
Regards

FrskyX is still completely in development and not working properly at all yet.
Give it some time.

Thanks Arakon for your answer.
i refer toone other subject on the forum "New FrSkyX protocol".
It seems that i could use a D** receiver using 8 PWM connexion and FrSky "standard" .
I dont care about telemetry. for the moment.
I have enough datas coming from the APM 2.8 via the3 DR telemetry.
Regards