Devo10 ESky protocol draft

Yea, that's implied. Sorry for the confusion.

victzh wrote: Yea, that's implied. Sorry for the confusion.

Ok I just finished to solder some tiny wires as probes ....

1mm step between pins .... I had to be precise ... Hope Now I will capture the signal...

I will try to record the binding procedure ... switch on first the heli than run recording then switch on TX

You're fast! Seems to be you're motivated

Yes I am motivated

Ok here is the first zip of the sniffing

mon-partage.fr/f/QxVdIe59/

I binded the heli then play with right stick (circular movement)
then play at then end with left stick ... (low throttle values)

I hope I didn't swap between MISO and MOSI .... I think no

Sorry, something is very wrong with your SPI trace. MOSI is always 0, and MISO is very strange.

victzh wrote: Sorry, something is very wrong with your SPI trace. MOSI is always 0, and MISO is very strange.

Ok I should a bad contact somewhere ... I will try to capture a new session and save the logig analyser session too

Ok the new one ... with the session


mon-partage.fr/f/CHJcl4fC/

Yes, it seems to be backwards, but it's OK, I'll fix the decoding script.

This trace is OK.

What I've figured so far:
Data rate - 2Mbps, CRC - 2 byte, address length - 4 bytes
Packet period - 4.8ms, packet length - 15 bytes
Transmits on two channels which are 40 channels apart (original ESky transmits on two channels 37 ch apart) every packet changes the channel.

Packet structure:
byte 0: channel 1
byte 1: channel 2
bytes 2-3: throttle value, big endian 1001-2000, middle 1500
bytes 4-5: stick value (aileron), same
bytes 6-7: stick value (elevator), same
bytes 8-9: stick value (rudder), same
bytes 10-13: always 00 d8 18 f8, may be 2 extra channels, not used
byte 14: sum of all other bytes in the packet

SeByDocKey, what else I need from you - another trace. I have not seen binding, so we can't make the protocol. Please make another trace as it was the last time - your soldering is good. This trace can be just as the last one, I need to verify the channels and TX address.

Then make the binding trace - set trigger on CSN going down first so that you don't write empty stuff. Bind the heli as if it was not bound - I don't have more specific instructions because I did not find ESky 150 manual.

victzh wrote: SeByDocKey, what else I need from you - another trace. I have not seen binding, so we can't make the protocol. Please make another trace as it was the last time - your soldering is good. This trace can be just as the last one, I need to verify the channels and TX address.

Then make the binding trace - set trigger on CSN going down first so that you don't write empty stuff. Bind the heli as if it was not bound - I don't have more specific instructions because I did not find ESky 150 manual.

Well is strange coz I first switch on the heli then recording and then power on the TX and the it was binding ....

I will do another one in the case of ...

"trigger on CSN goind down" ? How to proceed ?

Ok ... hope with this one will be useful ...

mon-partage.fr/f/YFTGOXYF/

Sorry to disappoint you, this trace shows that you did not touch the sticks but I failed to figure out how the binding is done.

It's probably the case when we need another TX for comparison. I will ask in RCGroups forum, may be there are people like you who are not afraid to break their TX with soldering iron. I'm afraid if I order it from Banggood it will be another month or so, and I have so many models I physically don't have time to fly that only take space and bother my wife...

victzh wrote: Sorry to disappoint you, this trace shows that you did not touch the sticks but I failed to figure out how the binding is done.

It's probably the case when we need another TX for comparison. I will ask in RCGroups forum, may be there are people like you who are not afraid to break their TX with soldering iron. I'm afraid if I order it from Banggood it will be another month or so, and I have so many models I physically don't have time to fly that only take space and bother my wife...

Ok maybe, I will try to switch on first the TX than after the helo .... maybe the binding procedure will be more visible ...

mon-partage.fr/f/aY8HhpS5/

OK, here is the build for Devo 10 with a new protocol, ESky150. Can you check that it binds and controls your heli? It's 4 channel only because I don't know what extra buttons and switches it has.

I did not try it myself - I don't have a heli.

victzh wrote: OK, here is the build for Devo 10 with a new protocol, ESky150. Can you check that it binds and controls your heli? It's 4 channel only because I don't know what extra buttons and switches it has.

I did not try it myself - I don't have a heli.

Bad news ... Doesn't bind ....

I don't know if it's normal, but when I press bind button, nothing happened on the TX. Usually, there is a timer

Timer is OK - ESky 150 does not have a separate bind phase, so it's actually reinit, I will fix this as well.

I made a mistake analyzing the protocol, let's try once more. Check the attachment.

victzh wrote: Timer is OK - ESky 150 does not have a separate bind phase, so it's actually reinit, I will fix this as well.

I made a mistake analyzing the protocol, let's try once more. Check the attachment.

Hi Victzh,

It's binding successfully that the good news ....

The bad new I broke again my MM . I wanted to make a slight ajustement ... and a CC2500 pin broke ... I am so unlucky