The New Hubsans

Hi Goebish,

I know you have many projects and really appreciate your work! Any advance on the H301s data would be much appreciated! Also, I you point me in the right direction, I might be able to do some of the work...

Best
Tom

Thanks! Looking forward to your input!

Hi Goebish,

Any update? Hope you had a great vacation!

On a side note....

It's interesting how undeveloped telemetry is - especially full range. This makes the Hubsan implementation so interesting: full range telemetry with attitude, gps and battery - all in a stabilized FC board with a built in full power A7105! If only we could control or even turn off the buggy RTH function, the electronics would be worth transferring to other planes. The H501s has similar capabilities and it remarkable in the quad implementation.

For future reference, I found this information at www.hubsanfpv.com/forum/viewtopic.php?f=11&t=889 re attitude and GPS data transfer:

They begin with bytes 0xE7 and 0xE8
0xE7 - is atitude (roll, pitch, yaw, number of GPS sats, voltage)
0xE8 - latitude, longitude, altitude and also voltage

The author chose to use the information for OSD, but I hope the raw data can be used directly. I can do some experiments to determine ranges for each parameter if that would help.

No rush, just excited about the future!

Great! I'll take a closer look at that post and try to increase my understanding...and stay out of your way!

I don't recall. But I DID do the following - I hope it answers your question:

1. Confirmed it auto-binds to both H107 and H501 options on Hubsan protocol.
2. Changed ID on the Tx.
3. Did a binding on H107, changed to H501 and it continued to be bound. Turned of Tx and Rx. Turned on Tx then Rx - auto-bound on H501.
4. Changed ID on Tx.
5. Did binding on H501, changed to h107 and it continued to be bound. Turned off TX and Rx. Turned on Tx then Rx - auto-bound on H107.

Once the Tx and Rx are bound. They remain bound regardless of setting H107 or H501.

I could detect no difference in behavior or control of the plane in h107 or h501: both control only the control surfaces and motor. Both leave the plane in 'Stabilize' mode.

Best,
Tom

As I would hope, the stock TX required a rebind procedure: hold Enter when powering on.

The H301 seems to be more versatile than the H501: it can bind with either Hubsan protocol.

T

Now I have a couple of questions:

First: I have Devo 6s, which generally uses the same firmware as a Devo8. Can I use the 7e test?

Second: Do I need the other files in the zip or is updating the dfu enough?

Thanks!

So far...so good!

LEDs - working
Stab/Man - working

RTH - need to test in flight - too windy right now!
Video - need to find my micro sd card!

Thanks!
T

Video on/off: also working!

I will attempt to test RTH later this week, but the other switches are all working....

Now - is there any way to change your mind about tackling the GPS coordinates? I think you had started some work on the H501 GPS. Do you think the H301 is similar?

Thanks again for all you work!

Tom