Frsky compatibility

Arakon wrote: Thanks. I got a D4R-II on the way and just installed the CC2500 in my Devo 7e.. let's see if this'll work.

If you ordered one of the CC2500's from the ModuleList, it should work fine. I just ordered two more of D4R-II's, as HK tends to sell out of them quickly.

If you ordered a CC2500 that's different than those, things get dicey. In theory, there are some internal settings in the FrSky protocols that you can tweak if they have problems, but I don't know if that's been tested. But that will be an issue with any FrSky Rx and that module.

Just wanted to say I've got my devo7e with a XL2500 module fitted and working lovely.

Had a question re: telemetry, and was looking for an explanation of what's being displayed on the page? Bound with a D4R-ii.

Thanks for all the efforts.

mwm wrote:

Arakon wrote: Thanks. I got a D4R-II on the way and just installed the CC2500 in my Devo 7e.. let's see if this'll work.

If you ordered one of the CC2500's from the ModuleList, it should work fine. I just ordered two more of D4R-II's, as HK tends to sell out of them quickly.

If you ordered a CC2500 that's different than those, things get dicey. In theory, there are some internal settings in the FrSky protocols that you can tweak if they have problems, but I don't know if that's been tested. But that will be an issue with any FrSky Rx and that module.

I got the one from banggood, www.banggood.com/CC2500-PA-LNA-Romote-Wi...F24L01-p-922595.html
From what I read, that one should work, no?
Jon.m.barter had posted about it 2 weeks ago here in this thread and his works, so I am fairly sure mine will too.

work like a charm with 7E. but it's a bit fragile, the place where you solder it tends to come apart :/

@arakon,

I have had zero issues with the cc2500 from banggood, already insalled around 3 of them on different radios.

midelic wrote: No these are the modules below.
Ali express module and BG one
They look the same but they are different.
www.aliexpress.com/item/CC2500-PA-LNA-wi...-2-4G/359941652.html
www.banggood.com/CC2500-PA-LNA-Romote-Wi...F24L01-p-922595.html

I believe the Aliexpress one have base channel frequency shifted(the famous offset),

The aliexpress one is the one recommended buy PB in the modules list.

The BangGood one is the one linked to in SebyDocky's tutorial video. I've tried playing with fine on mine, and managed to get the RSSI to be about 10 to 15% higher - whatever that means (Bueller?). It certainly didn't make any difference in the piss-poor range I was getting from FrSky.

If someone can tell me what that means, I'll verify that the same procedure works after I get a replacement. Of course, first I need to order a replacement. So the question is - which one should I order? The one recommended in PB's documentation that apparently needs FINE tweaked, or the one used by SebDocky to presumably do the FrSky RSSI work?

HI,

I'm on deviation nightly v4.0.1-817a6ff and having troubles receiving telemetry from a FrSky D4R-II. I only seem to get telemetry if I rebind or sometimes when I bind to another model then go back to FrSky. Any suggestions what might be wrong?

Okay.. D4R-II is here and seems to work fine. I can't seem to get RSSI values on the transmitter, or any telemetry for that matter.. all 0 (I don't have a voltage divider hooked up yet, though).. but shouldn't at least RSSI show?

Edit: Actually, seems to be the same issue as JaiCee has.. after binding, I get voltages + RSSI, but if I turn off both again, no more telemetry.
7e with 2cb43c0.

Also, is it normal for the RSSI value to fluctuate wildly? It's jumping anywhere from 65 to 98% for me even with the transmitter at rest and nearby.

I don't have that configuration to try, but for a 2.4GHz signal (where RSSI actually means very little) most indicators tend to jump, unless you are in the open, nothing nearby, and complete line of sight.

2.4GHz signals have massive problems with mutipath reception, so I can imagine that any approximation of an RSSI signal when the Tx and Rx are close by will jump around a lot

Arakon wrote: Also, is it normal for the RSSI value to fluctuate wildly? It's jumping anywhere from 65 to 98% for me even with the transmitter at rest and nearby.

Yes it's normal... packet[5] is normally a dBm value. I rescaled/mapped into [0-100%] but as you know loss is a quadratc function versus distance so ... it's normal to have huge variation in close distance. Maybe, it's possible to remap with a more adequate non-linear function but we need some FPU capaciities ... (or good DL approximation)

SeByDocKy wrote: packet[5] is normally a dBm value.

dBm measure of what? S/SN ratio?

SeByDocKy wrote:

Arakon wrote: Also, is it normal for the RSSI value to fluctuate wildly? It's jumping anywhere from 65 to 98% for me even with the transmitter at rest and nearby.

Yes it's normal... packet[5] is normally a dBm value. I rescaled/mapped into [0-100%] but as you know loss is a quadratc function versus distance so ... it's normal to have huge variation in close distance. Maybe, it's possible to remap with a more adequate non-linear function but we need some FPU capaciities ... (or good DL approximation)

Ok, thanks. I don't consider the RSSI value that important anyways.. however, the voltage telemetry would be nice to have working. Any idea about the issue JaiCee and I have seen?

Added a7105 and cc2500 last night to devo 6s. Everything seems fine except for this one small detail. Battery reader jumps like crazy. Stops going nuts when i scroll protocols, even if i return to previous protocol it stops. currently running latest nightly for devo 6s. Should i try the latest nightly for 8s?

Devo 6s voltage bug:

No, don't try the 8S build. You might try:

1. Disabling the two modules in hardware.ini, and if that helps try them one at a time.
2. Go back to 4.0.1 and see if it also displays the problem.

FWIW, I've got an RF24L01 and A7105 in my 6S, and don't see such issues with either 4.0.1 a recent nightly build.

I expect you are on high output level and have telemetry enabled....(protocol: Devo or DSM2/X)

Going to try your advice right now, might even do a fresh install.

Dont know if this helps anyone, but in the "errors" sheet, I got this:



[Hard fault]
devo6-v4.0.1-e1cdc10
R0 = 00000000
R1 = 00000030
R2 = 00000000
R3 = 0801ff09
R12 = 2000bf20
LR [R14] (subroutine call return address) = 080252c1
PC [R15] (program counter) = 080252c2
PSR = 01000000
BFAR = e000ed38
CFSR = 00000400
HFSR = 40000000
DFSR = 00000000
AFSR = 00000000
SCB_SHCSR = 00000000
Top of Stack:2000c000
Stack Detect:2000bf90
Backtrace:
2000bf9c : 0801ff09
2000bfa4 : 080252c1
2000bfb4 : 08025391
2000bfb8 : 0801ff09
2000bfbc : 0801ff4f
2000bfc0 : 0801ff09
2000bfc4 : 0802209d
2000bfcc : 08022467
2000bfdc : 0800ac0f
2000bfec : 0800acfb
2000bffc : 0802b485
Done

cant use regular 4.0.1 because last i checked it did not have frsky protocols, which is what I am using the radio for to fly d4r-ii receivers

The point of trying 4.0.1 isn't to use it, it's to see if it may be a software issue with the nightly builds. If the problem doesn't happen on 4.0.1, then we can try and figure out what changed. if it does, then we can eliminate any changes since then as the source of the problem.