The New Hubsans

Thanks dc59, so that's what I thought, the aircraft has to be associated with the transmitter before flying (as any "hobby grade" RX), see chapter 6.3 in the manual (page 13).

I need a dump of the bind stage (named re-linkage in the manual) to see how it works
(TX side should be enough) .... then I should have everything required to make it work, but there are a few features that won't work with Deviation because the Devos don't have an integrated GPS: Follow Me, Return Home (not sure, this depends if this is return to take off point or return to TX)...



Also, you'll have to make some captures outside so I can try to check where are battery voltage, altitude, gps coords and other telemetry data.

Ah, and just out of curiosity, can you post pictures of the complete pcb of the transmitter please ?

delta75 wrote: i connect RX and TX at analyzer

RX ch 1,3,4
TX ch 5,7,8

No, that will be a mess to extract, but TX side should be enough as I already have RX side only.
edit: nevermind, that's a good idea after all

Thanks, now I think I've everything required to make a basic implementation, I'm still not sure if I'll add a protocol format option to the current Hubsan4 protocol or if I'll create a new one.

There's something I don't understand, how does the Follow Me mode work as there's no gps/compass in the stock transmitter ?

I already found battery voltage telemetry:
packet type ID: 0xE7, 14th byte
I can see you had an almost empty (7.4V) 2S lipo in the aircraft

Also, every 10 TX packets, packet ID cycle through 0xE7, 0xE8, 0xE9 with zero'ed data + checksum.

The H501S is slightly different, the H107P should already work with hexfet's combo and nightly-default builds

Ah OK I can see the GPS now, I suppose GPS data is supposed to be sent via the new packet type IDs, but obviously we'll have to fill this with some zeroes

Here's a test build, please report back
It has a H501 protocol format option for Hubsan4 protocol.
It should bind automatically (if it works ...).

Devo 7e
Devo 10

I think vbat telemetry won't work well, but let's be able to bind and control first

Thanks, I'll try to add those flags and telemetry data
bitbucket.org/goebish/deviationtx/branch/protocol_h501s#diff