Furibee F36 protocol attempt

That's a shame as the stock controller is awful.

I wonder all the time how to get hands on one of these datasheets. I mean, the developers of those quads obviously should have them. Maybe it's possible to get the datasheet if ordering a bunch of those mcus? Assuming a datasheet would help to reverse engineer the protocol or make the whole compatible with Silverware for example - which means no need for reverse engineering the protocol anymore... Deviation compatibility is given then anyway...

Best option currently is simply replace the fc with the E010 control board it is nearly the exact same thing and is deviation compatible...

Of course - but that isn't the same. Then the board rocked you and not vice versa

goebish wrote: I wouldn't count on it anytime soon

My Jan 15 order of F36 is still no show, got refunded after dispute. With no deviation support I don't think I would reorder the F36.

Perhaps I'll spend that money to beef up motors and battery for my H36.

Please remember you still have a H20H protocol waiting for you to finish.

Stupid question as I'm no expert in any of this, but this thread says the Furibee F36 has or shares the same TX board as the Eachine H8 mini, although it does look like a it may be a slightly different version, so is it possible they are using the same protocol?

www.deviationtx.com/forum/model-requests...-f36-needs-deviation

May 5 here. My Jan 15 order of F36 has not arrived. It has already been listed as Expired on SG Post according to 17track. However suddenly CanadaPost updated its tracking not available timestamp this morning. Perhaps there is still a chance that I would need the F36 protocol 110 days after order.

BTW I have ordered an E011 to fill in the void. It is on its way via epacket. It should be faster than going through SG I hope.

Too bad. You give up when I finally receive my F36 ordered 110 days ago.

Plan B would be merging it with my H36 if I cannot stand the stock TX any more. I suppose it won't be too difficult transplanting the H36 FC into the F36 body.

Quick test by attaching a piece of AA battery (almost 14g) to the stock F36 showed that it could still take off. I should be able to use a bigger battery after mounting the FPV camera.

Goebish, anything I can do to help? I have my analyzer and should have my F36 by the end of the week.

I am finally getting into the protocol analyzing side of things.....I am a glutton for punishment...LOL

Right now I have a bit of personal time to invest in trying to get the F36 in Deviation......sure would love to fly it with my Devo 7E.......

Now this has me very interested.....will have to get my radio/EE geek buddies in on this......Furibee F36, you will assimilated, resistance is futile......LOL

Will let you know when I get this in the RF lab and see if they can get some sense of it.

Good luck but I think this one isn't worth the effort. It can't be emulated with an nrf24l01+ and there are much better options out now. The Eachine E011 and Boldclash BWHOOP B-03 both use Bayang protocol and can be flashed with custom firmware.

For the challenge!

I wanted to get back to this, but suddenly I am in the middle of other things. The LT8900 did arrive, but it's kind of late

I just got my Eachine 011, and it seems an aweful lot like the F36 and will see about getting it working with my Devo 7e once I get the 3in1 module installed.

My E011 has been in Vancouver Customs since yesterday. I should get it within a week.

It would fight for my 25mW AIO camera against my existing H36 and F36. I guess the F36 FC would be out since there is little hope on getting this protocol hacked out. E011 should have most power and FC should have been supported under bayang_nrf24l01.

++++++

The E011 arrived today. I ordered a mode 2 but I received a mode 1. I kept running it the wrong way as the sticks are reversed. I could not control it by crossing my hands. Had to fly it using my devo 10 right away.

The build quality of the E011 isn't that good. It came with loose and out of balanced props. The frame seems the weakest comparing to F36 and H36. I have also swapped the FCs of F36 and H36. In a sense I have more than enough to carry my FPV camera around. I can live without F36 protocol for now.

Thanks for attempting.

Hi guys,

First of all thank you for your all efforts in the reverse engineering of this beast!

If my understanding is correct the main issue is the fact that the MCU/RF piece is unknown.

If someone has least two dead boards or receiever ICs it might be useful to contact with zeptobars:
zeptobars.com/en/support-us
to see if they would have a willingness to decap and scan them.

It might show some directions about the chip/MCU type.

Hi bikemike!

Could you please check which pins of the receiever IC is GND, VCC and which pins are wired to the SCL, SDA testpads and to the antenna?

A quick google search with TSSOP24 2.4GHz MCU lead me to this IC:

www.nst-ic.com/f/1/1702115145.pdf

Could you please check if the pinout of this could match the IC's pinout on the board?

Thanks in advance! (My device is still on it's way from China, but I definitely would like to fly with a normal TX at some point.)

the pins do seem to match.