Frsky compatibility

Thanks for your reply mwm

The Receiver is on the way to me.
If you could do a test build for the 2 Way FrSky, it would very nice!
When I get it and install the testbuild, i will check all functions and give a reply.
Thank you very much!

Uploaded to test builds area of downloads under main menu.

This is just a WAG as to what the >8 channel protocol might be, and I will be surprised if that actually works. It wouldn't surprise me if it broke things with less than 8 channels, but I can't test it as the CC2500 I have in my 10 is dead..

Anyone can confirm it is possible to set the failsave from the Tx using the Frsky protocol?

What module do you recommend?

m.banggood.com/Upgraded-Adaptor-for-Walk...ntenna-p-909692.html

m.banggood.com/CC2500-PA-LNA-Romote-Wire...F24L01-p-922595.html

What distance do you get for those module?

The second link is the one I use, and that works.

what about this XL2500-D03 from ebay. will this one work.

I have the same issue as some other guys here, which all telemetry parameters become 0 and only right after binding it is possible to see the telemetry data. Once you turn off and on the transmitter then there will be no telemetry (all 0). I think it is somehow related to particularly 7E transmitter that Im using So, does any one have a solution for telemetry with 7E and frsky and not only right after binding? If yes, please post the version you are using and it worked for you.

I have installed the CC2500 (version with the shield) from BG on my DEVO 10.
But when I try to Bind the X4RSB i get no connect.
I have try to play on the FreqFine option but without success.
I have also Connect the PA EN and the LNA EN to GIO0 and GIO2.
and I try to connect PA EN and LNA EN to 3.3V and GND
but no Bind!
Have anyone a idea or a hint
I'runing the last nightly Version (2015-06-09)

From Frsky site:

X4RSB 3/16ch Telemetry Receiver
Compatibility with FrSky X-series Module (XJT etc.) Taranis X9D in D16 mode
(X4RSB is not work with D-series Module)


Myself I use D series receivers and can confirm works with Deviation:
FrSky D4R-II - 4/8 Channel Receiver With 27ms CPPM
Compatible with FrSky Taranis and the telemetry modules: DFT, DJT, DHT, DHT-U

The D-series I beleive have different protocol no "model match" and only 8 ch.

I have tried bind the FrSky X4RSB again with the Testbuild from mwm but without success.

Have anyone runing a frSky X-Series Receiver on DeviationTX?
If anyone have time to implement the Protocoll it would be nice!

@anybody who has installed the CC2500 module:
Since it was mentioned, that the CC2500 draws approx. 360mA which sounds way too much,
can you please measure the current consumption of your module and post it either here or over there:
www.deviationtx.com/forum/3-feedback-que...63-i-need-a-rx#34232

Please also mention which module you have and/or post an according link...

Thank you very much!

I proposed some fixes to the issues I had with Frsky Telemetry (See the pull request #80)
My setup :
•devo 7e (with 2 modules from banggood : A7105 and CC2500 PA LNA Romote Wireless Module)
•frsky dr4-ii
•naze32 (flashed with cleanflight)

The fixes :
•Fix the id 0x6 for voltage3 (could be further improved with little endian and big endian value definition )
•Fix the fact that Frsky telemetry is only working after binding. Otherwise, Telemetry window is always '0'.

Give it a try and don't hesitate to feedback.

Thanks kerzin that seems to have fixed the telemetry problems for me (at least turning it on/off twice I kept telemetry).

My devo 7e is now pretty much perfect for me.

This is great improvement and seems that the RSSI and voltae is stable on 7e and displayed every switch-on time.

Thank you very much for that solution. BTW what was the problem so the telemetry didnt work on 7E after second turn-on of the transmitter?

In the initialize function (file frsky2way_cc2500.c), when already binded, the state variable was initialized to FRSKY_STATE2 and counter variable was not initialized (should be to 0) where as if you start from FRSKY_BIND_DONE, the counter variable is well initialized.

I am now very happy as well with my 7E. Thank you very much to the deviation team.

When I set alerts based on the telemetry, I get a couple of blank names in the list - among other problems. I have a fix for this, but would like to verify that others are seeing it before I create a pull request.

Hi guys, i have some problem with my cc2500 pa lna from Banggood on my devo 7E

I already installed a A7105 which works fine with my hubsan h107, i did the range-diode mod and added 2X3 way switches which works fine too.
Now i'm tring to install the cc2500 PA LNA transceiver bought on banggood...
I followed the PB pinout datagram, connected 5->10 and 7->9, upgraded to latest nightly, formatted the file system and copied a fresh version.

The issue is that, when i try to bind to a d4r-ii receiver using the frsky protocol, as soon i press the bind button the devo7e shuts down... it just turns itself off...
I tried to change the connections, 9->3.3v and 10->gnd but didn't solve the issue... i tried to remove the a7105 module but didn't solved either.

this is my hardware.ini
;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
extra-switches=3x2
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
enable-cyrf6936 = B12
has_pa-cyrf6936 = 1
enable-a7105 = A13
has_pa-a7105 = 1
enable-cc2500 = A14
has_pa-cc2500 = 1
; enable-nrf24l01 = A14
; has_pa-nrf24l01 = 1
; enable-multimod = A13

does any of you gurus know what could be the problem?

Thank you very much,
Kata


p.s. more info: I never powered on the module without antenna, a7105 is connected to TMS and so i connected cc2500 to TCK

Did you go back to 4.0.1. when you changed the power connections? That's what that's for.

Frankly, it sounds like a short somewhere. You didn't say you'd done it, so forgive me if you have, but try cross-checking all the connections to see if two of them are shorted. If that doesn't turn anything up, post photos of the connections so others can help with a visual inspection.

ok, solderings seems ok but i didn't cross checked them with a multimeter, this evening i sure will, thanks for the moment.

what you mean by "Did you go back to 4.0.1. when you changed the power connections?"

Sorry, "power connections" is misleading, if not wrong. It's what you connect pins 9 & 10 to. For anything up to and including 4.0.1, it's power and ground. For any nightly build and any release after 4.0.1, it's two IO pins. So when you changed those connections, you should have gone back to running 4.0.1. I'm not sure it's required, but I don't know that anybody has actually tested that configuration.