Frsky compatibility

Help to connect X4R-SB to CC2500 what it is necessary to make for this purpose?

I have a problem with the translation. Sorry

Fernandez wrote: Missing value could it be for setting of the failsave of the Tx

Unfortunately failsafe are not the unknown value because we know where failsafe values are: www.rcgroups.com/forums/showthread.php?t...&page=8#post32874735

You can read rest of linked thread if you want to know more about unknown value.

I uploaded 4.0.1-9cce188 into my devo 7e. Telemetry reception is indeed stable does not affect other data, but I find that on telemetry monitor the rssi always comes in, but that voltages sometimes are not displayed. When this is the case,
selecting to view those voltages on the main page config, they are diplayed on mainpage correctly, so they are being received/decoded.

Is there allready a request to put the ratio's as input, so we can get the real voltage displayed?

What voltage are you talking about? The AD2 gains is settable in the model config, under the protocol options. I believe that on the most recent nightly you have to reboot the Tx for this to take effect, I've fixed this in my FrSky-telem-names test build, though the build is lagging behind default now.

jry wrote:

petr512p wrote: Prompt it was succeeded to connect X4R-SB to CC2500?

Yes, it works fine with my testing code and CC2500. D16 protocol is clear, we can write both TX and RX including telemetry. There is one unknown value but it doesn't look critical for RX/TX communication.

I'm about to order an Rx for my new cat. Any chance I can get this to test in a couple of weeks if I order an X4R, or should I go ahead and order the D4R or R620X I Was expecting to put in it?

It entirely depends on Deviation developers (I'm on Taranis). If anyone will need any further information or tests not described in mentioned thread on rcgroups, I can help. I'm working on latest two unknown (and related) values but as I said, they doesn't seem to be crucial for TX/RX implementation.

I am in for some new receivers too if this protocol is implemeted into deviation will defenitively make use of it

jry wrote: It entirely depends on Deviation developers (I'm on Taranis). If anyone will need any further information or tests not described in mentioned thread on rcgroups, I can help. I'm working on latest two unknown (and related) values but as I said, they doesn't seem to be crucial for TX/RX implementation.

The thread hasn't seen a new post in a week and a half, and I haven't seen anything on it as to where I can get the code to try building it in deviation. If you can provide a pointer to that, I can see about getting it into deviation. Or is someone already working on that?

I didn't publish any code yet, I have just some hard coded fragments - it was enough to explore protocol. I would like to finish it and release open source... I will let you know.

Right now I'm looking into Frsky firmware encryption scheme. I hope we would be able to understand mentioned unknown values with decrypted firmware.

Hello. I establish not the first time. But the module ss2500 consumes about 0,60 A. Thus it is heated strongly and doesn't contact the receiver, it doesn't work.

Any link for the module ?
BTW, your other modules are not working as intended. They should be into sleep mode if not in use.
A modded 7e should be at around 170 to 200 mA (with range mod).
The LDO (3.3V) is a 250 (peak300mA) type........

Edit: Please change the your topic...this is something that should not be in here.


Edit1: Devo7e, whole transmitter....
Devo > 100mW > 156.5 mA
FrSky > 100mW (D8 protocol) > between 195.4 and 207.4 mA (telemetry on).

Hi Guys!

Please Help!!
I installed CC2500 module in Devo 10 and binding with D4R-II without problems, I have telemetry, BUT the RSSI signal is very poor. I lost signal a los 5m. I changed the antenna, but persist the issue.

Any ideas?

I had that issue with mine as well, because I didn't install the jumper between the pins on the CC2500. Installing that fixed it.

If you've already done that, make sure all the connections are solid, and post photos of our install for the hardware guys to inspect.

Thank you very much mwm!!

I had a bad jumper connected. Solder it again and it works very well.

Hello, and failed to connect X4SB?

petr512p wrote: Hello, and failed to connect X4SB?

As mentioned repeatedly in the thread, not supported. Unless you're using the older 8-channel protocol, which some of them don't do. Hope to have the 16 channel protocol soon, though.

Just wrote that is sort of managed to tie

mwm wrote:

petr512p wrote: Hello, and failed to connect X4SB?

As mentioned repeatedly in the thread, not supported. Unless you're using the older 8-channel protocol, which some of them don't do. Hope to have the 16 channel protocol soon, though.

Are you going to support both EU and international versions of the protocol please?

djdazzy wrote:

mwm wrote:

petr512p wrote: Hello, and failed to connect X4SB?

As mentioned repeatedly in the thread, not supported. Unless you're using the older 8-channel protocol, which some of them don't do. Hope to have the 16 channel protocol soon, though.

Are you going to support both EU and international versions of the protocol please?

Is there a difference? I know the international radio gear doesn't support the old 8-channel protocol, and that there are power differences in them, but will the EU gear and international gear not work together?

vlad_vy wrote: The best flexible antenna for Tx modules and telemetry modules. The same antenna can be found inside 2.1dBi rigid antenna (DX8, WiFi).

www.himodel.com/radios/250mm_Long_2.4G_R..._Receivers_2pcs.html

www.himodel.com/radios/400mm_Long_2.4G_R..._Receivers_2pcs.html

www.himodel.com/radios/600mm_Long_2.4G_R..._Receivers_2pcs.html

The same antenna used in Walkera telemetry module

Looks like a receiver antenna to me. Are you sure it can be use for TX?