Hubsan x4 (H107) Support

heliaddict wrote: Not sure why they put it in expert mode before calibrating. I have tried in both modes and it works so not sure if it really makes any difference?

Thanks for your answer

Yes that was the video I was referring to. I thought that maybe they do the calibration in high rates to somewhat set the gyro mode. Something like tell the quad what the full travel is, then it would not allow flipping if the stick travel is less than x% of what was detected during calibration. Again, I may be thinking too much ...

I must say the the accelerometer does work extremely well on this quad and I personally prefer it over the Ladybird. It flips fast and in very tight spaces and also recovers very quick. Its very impressive especially for the low cost.

Mine is coming in tomorrow, looking forward to it after your comments and all the good stuff I read about that little thing. I literally love my ladybird so I guess this will be great!

Sad thing to have to get another useless Tx that will end up in the bin, sad for the environment and sad for my wallet as well!

The Revell QG 550 works fine with Hubsan x4 config and ‘A7105-500m’ module.






www.revell-control.de/quadrocopter/neu-m...xs-series-rtf4chghz/

Could someone explain the option(s) for getting the new Estes ProtoX quad to work with Deviation? I know the quad uses the Husban protocol since I read someone got it to work with a Husban transmitter.

Exactly what module do I need... still the A7105-500m as mentioned 8 months ago?

Also, if a module is added can it peacefully coexist with the stock Devo module and does the Deviation firmware turn off one when the other is in use? I am a little unclear of the overview for multiple modules.

Thanks.

OK, here's a more directed question...

Would this module work in a Devo 6 to control a Hubsan X4 quad?

Thanks.

It should, but it is very range limited. It does not have Power Amplifier, and can have range up to 30 meters or so. May be less.

Yes, the low power won't be a problem with my Proto X which I can only see closer than about 13 meters. However, if a power-amp equipped module (like this one ) is used, I assume the firmware disables it when on a different protocol to conserve power, correct?

If that's the case, then it does make more sense to use the higher-output module.

Not exactly. You should set the module as having Power Amplifier, and then for a given model you can reduce power yourself.

Power conservation should not be that essential - 100mW module theoretically can run from 5v 20mA, or 3.3v 33mA. Usually some losses means that it is more close to 3.3V 40-50mA. Linear power supply used in Devo dominates these power losses with big margin, so if you're power conscious you should care more about enhancing Devo's power electronics than reducing power of your radio.

My only concern is that the firmware communicates to any module that is not being used and puts it in standby mode or turns its power to zero (or whatever the lowest output is.) I would guess the firmware does work this way, but am not sure.

I am not concerned about the linear power supply losses since I get good transmit time with Ni-MH batteries.

Edit: Just found the answer here .
The transmit function is inhibited when Hubsan is not selected. As it should be!

Just picked up one of these at a radio shack going out of business for 70% off lol. I think it was like 15 bucks after tax. Anyways, can I bind this model to my devo 7e? Thanks!

You need an A7105 module installed, and the protocol is "Hubsan". Lots of model.ini files around for it, and you can also use anything that works with the Proto X (but not Proto X SLT).