fbl100

PhracturedBlue wrote: going to need a 'universal' module sooner or later to manage this terrible situation.

Put me on the waiting list, if you don't mind.

Hello, since you're the only one posting his model for FBL100
I have some troubles with it, I modified it according to have something that work with my Devo7e and HT8 V3.

So for now all is working fine except one things !

AIL is inverted, and when I start to Invert AIL all is starting to change
ELEV become AIL, AIL Become ELEV and Pitch doesn't work anymore ...

So I give my model ini If someone now what I am missing help me.

It's my frst time on deviationtx I need to understant why i can just Invert a channel without messing up entire commands ..


Edit : and I fogot to mention i'm using deviation 3.0.0

I'm not sure about that but I would look at the swashmix. You haveThe mix values look strange to me (usually 60-60-60). I think you try to achieve something (like little pitch range) at the wrong place - don't do that in swash, but at the right channel (6?). Also you do some inverting here, what might be necessary, but may cause your trouble.
Also I'm unsure if you need this kind of swashmix for a fbl heli (they need at most "1 servo"). When they do not get the pure values the internal stabilization can not work correctly.
There is a good manual for setting up a fbl heli in the howto-section. Have you read this?
You can also take the 6-ch-heli-template as a starting position.

I copied what i used in devo FW it is what i used for make it work
In pure devo FW on my devo7e

But if I need to switch to something else I would do it

Edit: yes i saw it and successfully created my own template for the V120d02s
But it seems that FBL100 with HT8 is more difficult to make work

FBL 100 needs a swash mix 120, CCPM must be done in the TX.

Not the usual way, mixing done in the RX.

Manual calls for JR :

3 servos 120° Ail 37% Elev 37% PIT 60%

Invert throttle channel all others normal.

For Futaba :

Ail -50% Elev -50% PIT -50%

I don't know if swash mixing on deviation follow the (0-100)*2-100 rule, or if for the swash we stay with the 0-100%.

All channels NORM but Ch 4 Inverted

Hello, yes it's from the PDF for HT8v3
Putting the JR rules just work fines on the original Devo FW

So i kept those settings in mind on deviationtx 3.0.0
Inversed Ch4 and Ch3(throttle) as if it was not throttle at -100 and RUD inverted ...

But now all control Throttle Pitch RUD Elev are fines only AIL is inverted and as soon as I invert it all other controls are messed up ...

So I tried this afternoon to switch to 1Servo the swash and it was worse

Reverted to my settings but it seems I can't find a way to invert only AIL without having all going wrong ...

If someone had this issue and know how to solve it ...
Maybe it's only on Devo7e and it' is a related bug to it ...

So I found, if I invert in the TX menu AIL all are upside down
but If I edit model2.ini and remove the line ail_invert=1 under
[swash]
type=120

All is working now fine !!!
Just need to make it more agressive and it's done
I'll repost my model.ini after I have what I want !

But after 1 hard day it will be nice to give it for those who have deviationtx 3.0.0 and a devo7e with HT8v3 and I hope it will work with FBL80 !

Initially I found programming the tx difficult but it turns out its easy now. I think the hardest part in the beginning is unfamiliarity. I can say, battling it out with patience certainly is the best way, you learn more about the tx and what you can implement on other models along the way. I cant say it enough to all involved but kudos to you for creating the software for users like me, hopefully someday I can contribute something useful

There it is my model.ini for flying the HK FBL100 with HT8 attached to Devo7e

It fit my needs feel free to edit it and make your Own model

So, PhracturedBlue, do you plan to work on HiSky in foreseeable future? If not, I can try to. It uses nRF24L01, and I now familiar with it. I would order HiSky quad with HT8 and try to analyze it. But if it's in the works, I may be do something else.

@chaosson
Thank you. Loaded up your latest model.ini and it binds just fine. Interestingly though, my Elevator controls works opposite of what I expect. Pushing ELevator stick forward, the v922 wants to go backwards. Pulling the Elevator stick back, and the v922 flies forward.

I'll try directly editing the model.ini and see if that fixes the problem.

@victzh
PhracturedBlue isn't hacking on the HiSky protocol at the moment. He was concentrating on the SkyArtec. And then I think he wants to do the FrSky implementation.

Let me try to dig up the thread where he mentioned the "E(?)" version of the nRF24L01 that comes with the v922 making it more difficult to snoop.

That's probably not that big of a problem. Someone somewhere was negligent enough to leave the protection open on HiSky-enabled Q-BOT micro. So it's firmware was downloaded and disassembled, which as you can imagine is a great help in reversing the protocol. I'm ordering it now - it will take time to come, though. Also, as I have Mini CP (V922's prototype), I'll order the board of V922 (or FBL100) , which is quite inexpensive.

LOL. Yep, I am following the mQbot/FF120 thread with great interest. I do love my qBot. Can't wait till you get yours as well. Then there were be a few smarties putting their collective mind to hack that FC.

@chaosson
On the swash, I changed ele_inv=1 to ele_inv=0. And now get the correct ele movement.

However, the bird feels a little weird in the air. Almost like the swash mix is a little off. Giving ele forward on the stick, and the heli feels like it has some ail mix. Anyways, I'll play with it some more. These are just ramblings by me at the moment.

How's it flying for you.

Daryoon wrote: Yep, I am following the mQbot/FF120 thread with great interest. I do love my qBot.

Hi Daryoon, where can we follow this thread?

Here you go. It starts to get good at post #956 where gke manage to connect to the ARM

www.rcgroups.com/forums/showthread.php?t=1826018&page=64

Daryoon, if you have Q-BOT, can you look at the board, does it have nRF24LE1 or nRF24L01? I may be was a bit hasty with this. LE is not that easy, it has a MCU inside and if the protocol implemented in there we're screwed a bit.

I don't see any indication of it. Am I looking at the right place? Or are you talking about the transceiver used in the HT-8 module?

Here's a photo of the flight controller.

I took off the shield covering the chip in the HT-8 module. Here's a photo:

Here's the bottom of the HT-8. Has pads.

I see. Thank you, now I know what awaits me as this heli comes to me. Many hours of torture - last time it took me 2 sittings 2 hours each to solder to receiver, this time I see it's even less space than in V202. But, and it's very important, it's Si24R1, which is another clone of nRF24L01 without any MCU's on board, so fully traceable.

For nRF24LE1 in transmitter I couldn't care less - I doubt they forgot to burn fuses (but they did on the receiver, so it makes sense to try!) and I don't have any experience with nRF's 8051.