Frsky compatibility

Just came across this and reading with interest.

I hope the X4R-SB will be supported in the future.

I recently got a devo 6S and will be having it modded to be used with my D4r-ii. But I am transitioning all my D4r-ii away to X4R-SB...

If someone is committed to finding a solution to X4R-SB, I will be happy to donate a piece.

D16 protocol capture from X4R-SB RX is now available at www.rcgroups.com/forums/showthread.php?t=2503871
I will try to capture also XJT TX part.

D16 protocol capture from X4R-SB RX is now available at www.rcgroups.com/forums/showthread.php?t=2503871
I will try to capture also XJT TX part.

Yay! And I see midelic is already on it. Hopefully, he'll either do a deviationTx port, or provide code that can be ported.....

I'm in the same boat as many others, just ordered an X4R-SB and CC2500 from banggood in the hopes of using them with Deviation on my new 6s.

Do you amazing people believe that this protocol can be implemented post haste? Or should I try and cancel the order now, before it has shipped?

Hi,
I started decoding the protocol but the go further identifying data used I need an X4R.RX. for testing the code.
Unfortunately I don't feel like buying immediately another RX,
I bought so many things for my multiprotocol testing. and have a lot of stuff I don't need .... so is going lower on my priorities list.

Hi Midelic, did you ever looked into the feature of setting the Rx failsaves from button of the TX ?

With the D series it is possible and I find it very handy as receiver is normally somewhere not easy to reach after tunning configuring makes easy to store failsave before flying.

midelic wrote: Hi,
I started decoding the protocol but the go further identifying data used I need an X4R.RX. for testing the code.
Unfortunately I don't feel like buying immediately another RX,
I bought so many things for my multiprotocol testing. and have a lot of stuff I don't need .... so is going lower on my priorities list.

Hello midelic, where are you located? I would love to send you my X4R-SB for you to work on the protocol, as I have nothing to use mine for until it is supported by Deviation.

I sent you PM.

I made code for XJT 16 channels,But for test I need an X4 RX.
Maybe somebody from Europe is willing to sell one to me.
I need it in 2-3 weeks max.If not I will be able to test after 2 months.

Hello,

I have a devo 8s on last NB version and cc2500/d4r-II and i would like to have RSSI on my minimosd via a spare Channel to my naze32 (in ppm)
But i dont Know how?!...

Hello,
I think I have the same need. I am building a new 250 based on dr4-ii, flip32 and minimosd and I would like to send back RSSI to the flip32 in order for the RSSI to be displayed by the minimOSD.
Should be possible to do it with the Taranis (see http://http://vk4ghz.com/mwosd-display-rssi-via-spare-radio-channel/ ). But i think it is not yet possible with deviationtx ?
Any chance for that to be developed ?

rssi at Rx is just coming out of d4r receiver if ouput in ppm mode.

I have problem with telemetry frsky at devo 7e, telemetry only comes in after bind or after an Rf power change.
Also the Tx voltage is being displayed instable going up and down. Further would be interesting if the minmax values, could be displayed, so after flight you can check min RSSi etc.

The problems with data not being displayed until bind or power change were fixed by a fix a while back, though you may be having another problem with the same symptoms.

So which version are you running? In particular, have you tried my frysky telemetry test build? deviationtx.com/downloads-new/category/2...kysensorhubtelemetry

Days logging isn't going to happen on the 7e. I had to take out the vario reading to get the sensor hub battery voltage to display.

Excellent thanks for that. I am running v4.0.1-b381655, I put that as it was developed for Bayang Eachine H8 at the time.
Will run your test build if it has also the bayang protocol.

Wishlist:
For telemrtry, no full logging required. But as I can't read screen during flying, some Telemetry Statsistics screen would be very nice, giving min max Voltages, RSSI etc, or a possibly to set a counter, which can count the nr of samples RSSI / Voltage was below threshold as set etc. Just after the flight you can check it.
At power down, those values maybe deletet.

You can display RSSI and battery voltage on the main screen, but you'll have to config it by hand since the 7E doesn't have layout editor. I can provide instructions if you need them.

You can also set alerts for both the voltage and RSSI levels. That's how I use it on my 10.

There's no room store any more telemetry values on the 7E in my test code. I had to turn some of them off in order to get it to fit already. So you can't get anything that requires keeping a value around, like a count or min/max/etc. I'm loathe to do much tailoring for the 7E until it's it's mostly sorted out. After that, we can revisit the list and decide how to squeeze it down to the 7E.

Prompt it was succeeded to connect X4R-SB to CC2500?

No. The protocol has not been fully decoded yet.

Does anyone uses this high precision variometer with their Devo+Frsky ?

www.hobbyking.com/hobbyking/store/__4231...cision_Version_.html

Or his little brother :

www.hobbyking.com/hobbyking/store/__4231...cision_Version_.html

Thank you.

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.

Super !!!
Missing value could it be for setting of the failsave of the Tx, I requested that also for the excisting Frsky protocol.
With mh Frsky DHT-U I can set failsave from my tranmitter over the air (no need to use a pencil in the rx to set failsave), but with deviation the set failsave feature from Tx is missing.
So it must be somehere in the protocol.