Closed labomat closed 4 years ago
The protocol works and is up to date. It's just that this little heli is not so easy to bind. You need to bind at the right time. I can't remember exactly when but try at different time. Also you have to do a specific stick movement to start the heli. It's in the doc of the heli.
No comment since 9 days, I'm condidering it's working.
No, unfortunately it's not. I tried every possible moment with no luck. I also wrote to rcgroups where a guy could reproduce the problem: https://www.rcgroups.com/forums/showthread.php?3050896-Esky-f150-v2-can-bind-to-taranis-transmitter
Hi, I also have this issue and cannot get the esky 150 v2 to bind... I have a t16 pro v2 with internal multi module. tx is running 1.3.0.52 RETA for multi module setup a new model in opentx inputs to ch1 Rud ch2 Ele ch3 Thr ch4 Ail
mixer to same
tried using 4 ch, or 7 ch in multi setup to no avail. tried adding in ch5,6,7 normally and then setting to zero as some have suggested.
Nothing will allow me to bind, Just get the flashing blue and green lights on heli..
Once the green and blue lights are flashing you can bind with the original transmitter so that appear to be the right time to bind, but the multi module wont.
Is this a problem with this protocol? or Can anyone suggest any other things to try or share a opentx model that works?
Thanks in advance
It's a long time ago (couple of years) but I remember that the esky150x airwolf is a pain to bind. The bind with the original TX works each time because the heli already knows it... You need to do the bind at the right time. If I remember correctly you have to power it on, wait for the LED pattern to change then only bind but if you wait too long it gives up, so it's all about timing. You also need to do something with the sticks to activate it which is indicated in the documentation if I remember. I have a friend which has one (the one I used to reverse the protocol) but with the confinment I don't know when I'll be able to borrow it.
Pascal
Just realized, could it be another version? The one I've worked on was the esky F150X airwolf. If yes I need someone to send me the TX and heli so I can see what has changed and reverse the protocol if possible. Pascal
I think they made a new version some time ago -> v2
There are two major upgrades from ESKY F150X and it seems they changed something at the rc part:
Without the remote and heli there is nothing I can do... If someone is willing to ship it to me I will have a look.
I have the heli - is there something I can do from here? Taking some measurements?
Do you a logic analyzer that you can connect on the SPI bus? Can you open the TX to see what RF chip is being used (picture of the rf board)?
The main chip is labeled (as far as I can read it): N5 1822 QFAAH1 16 (or "0") 21CX
And yes, I have one of theses cheap usb logic analyzers - but not used it yet ... So I would giv it a try this evening if you can tell me what to measure.
Can you do some pictures? Is the RF really going out direct from this main chip?
Oh that's an arm + 2.4GHz in a single chip... So nothing to connect to for analyzing. SDR is the only chance at this stage... Can you see the receiver side components?
That is just a STM32 and a flash
The rf chip is not in the picture. I might be on another board or the backside of that board.
Looks like the same as on the tx ...
SDR is the only way at this stage...
That is just a STM32 and a flash
The rf chip is not in the picture. I might be on another board or the backside of that board.
Welcome back! Long time not seeing you around.
So I guess it is not possible to get some information by analyzing the signaling between rf module and the rest of the system. I do not have any experience with sdr and do not have any equipment. I ve seen some cheap sdr usb sticks on amazon - are they suitable for recording the communication between tx and rx?
@pascallanger I am still lurking and reading the mail from github but almost no time to really work on OpenTX/Multi :( The curiosity what RF would be on that board was strong enough to peek into this issue
I asked the manufactorer about the protokoll - this is what he told me:
Halo my friend, thank you for your support our product, for the old version protocol, we are using the fixed 2.4 frequency, so we heard many user can use their own receiver, but our F150V2 are using non-fixed frequency to avoid the lose control problem, the frequency will change every seconds, we are sorry to let you know we cannot provide you. Does this mean it is generally impossible to use the 4in1 module for this heli?
All protocols do frequency hopping... Their old protocol was using only 2 channels. FrSky is using 47 channels. So what they are saying is more that they don't want to give you the protocol they are using. I've never seen a company doing so anyway. I'm using this SDR: https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview
is it possible to send private messages here - in order to exchange adress data?
Contact me by MP on RCGroups (hpnuts): https://www.rcgroups.com/forums/showthread.php?t=2165676&goto=newpost
If you can't contact me on RCG, look at my GitHub's profile, my email is there. Or press the donate button, my email address is there as well.
Another one unsuccessfully trying to bind the 150 v2 (different model but the same internal parts): https://www.youtube.com/watch?v=XmUIdMsBnZI&feature=youtu.be
I'm not sure what you are looking me to do... I've proposed you to ship me the heli+TX or I purchase the heli with a participation from your side. I haven't received an answer since a week or two. There is nothing I can do on this protocol remotely which we know will be hard to reverse anyway. Pascal
Just stumbled upon this video - messaged you on rc groups.
The TX is sending packets using GFSK at 250Kb/s. Here is just a preliminary analysis:
This mode is not compatible with a NRF24L01 which can only transmit a payload of max 32 bytes. The CC2500 should be able to send this payload.
There does not seem to have any extra checks in the payload.
Left to do:
Pascal
The bind packet is sent on channel 0 at 250Kbps every 57ms. It contains:
The CC2500 should be able to send all this data but no guarantee... But wow that's a lot of data in a single packet...
Pascal
Ok I can fly the heli using the multi module configured to use the original TX ID and hopping frequencies which the heli is already bound to. Now the problem is to send the bind frame...
Protocol fully reversed. It is available if you compile from master v1.3.0.95. I will do a release a bit later.
Release: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/releases/tag/v1.3.0.95 @labomat and @pete9999, please test and report. Pascal
@pascallanger Binding and flying seem to work flawless! Superb work!
I've got this heli, but mine is the V3 version, I have tried the Esky V2 protocol on my TX16S MkII, Max, with built in 4-in-1, but it doesn't map the functions correctly, I can't get the throttle to work whatever I try. Any ideas I could try?
I am not sure about your specific instance. However, throttle is often restrained by channel position, calibration, or an Arming switch position.
On Sun, Aug 11, 2024, 10:45 yakacm @.***> wrote:
I've got this heli, but mine is the V3 version, I have tried the Esky V2 protocol on my TX16S MkII, Max, with built in 4-in-1, but it doesn't map the functions correctly, I can't get the throttle to work whatever I try. Any ideas I could try?
— Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/182#issuecomment-2282784620, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNT6YB3NPNTCKCVAIM2D5TZQ52HNAVCNFSM6AAAAABMK2AUCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSG44DINRSGA . You are receiving this because you are subscribed to this thread.Message ID: @.*** .com>
Hey thanks for getting back to me, I thought about the arming switch, and I don't see anything, and moving all the switches has no effect. "throttle is oftenrestrained by channel position, calibration" could you elaborate on that, not too sure what you mean by, channel position or calibration.Thanks Andy.On 11 Aug 2024, at 17:24, pitts-mo @.***> wrote: I am not sure about your specific instance. However, throttle is often
restrained by channel position, calibration, or an Arming switch position.
On Sun, Aug 11, 2024, 10:45 yakacm @.***> wrote:
I've got this heli, but mine is the V3 version, I have tried the Esky V2
protocol on my TX16S MkII, Max, with built in 4-in-1, but it doesn't map
the functions correctly, I can't get the throttle to work whatever I try.
Any ideas I could try?
—
Reply to this email directly, view it on GitHub
https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/182#issuecomment-2282784620,
or unsubscribe
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
.com>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
https://www.esky-rc.com/Uploads/202108/ESKY150V3_Manual.pdf
Suggest investigate throttle cut and the troubleshooting sections of the manual.
Maybe see if you can find a youtube video that covers configuration of the F150 (even older versions) in opentx/edgetx.
On Sun, Aug 11, 2024, 15:46 yakacm @.***> wrote:
Hey thanks for getting back to me, I thought about the arming switch, and I don't see anything, and moving all the switches has no effect. "throttle is oftenrestrained by channel position, calibration" could you elaborate on that, not too sure what you mean by, channel position or calibration.Thanks Andy.On 11 Aug 2024, at 17:24, pitts-mo @.***> wrote: I am not sure about your specific instance. However, throttle is often
restrained by channel position, calibration, or an Arming switch position.
On Sun, Aug 11, 2024, 10:45 yakacm @.***> wrote:
I've got this heli, but mine is the V3 version, I have tried the Esky V2
protocol on my TX16S MkII, Max, with built in 4-in-1, but it doesn't map
the functions correctly, I can't get the throttle to work whatever I try.
Any ideas I could try?
—
Reply to this email directly, view it on GitHub
< https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/182#issuecomment-2282784620>,
or unsubscribe
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
.com>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/182#issuecomment-2282868741, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNT6YAVHV7H6MNSZSG2OKDZQ65QDAVCNFSM6AAAAABMK2AUCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSHA3DQNZUGE . You are receiving this because you commented.Message ID: @.*** com>
150v3 flies perfectly fine. A friend has one and i've been able to configure it. The channels are not as described in my GitHub since for whatever reason they changed the order. I recommend removing the blades while playing with the config since his heli took off unexpectedly while I was figuring out the details. I think I still have the model on my radio. If that's the case I'll post the quick config I did at the time.
Thanks for getting back to me, if you could could share the config that would be great. I've spent hours on the thing, and yes blades have been removed since day 1, if not it give you a little surprise, if you have the heli bound to the radio, and you turn the radio off or switch to another protocol, both motors start up full speed. I found this on Github
RX output will match the eSky standard TAER independently of the input configuration AETR, RETA... unless on OpenTX 2.3.3+ you use the "Disable channel mapping" feature on the GUI. To run this protocol you need both CC2500 and NRF24L01 to be enabled for code reasons, only the CC2500 is really used.
So disabled channel mapping, and that ch1 and ch2 working correctly, so, as I said above, it's just throttle I'm struggling with.
Right oh guys, my E150 is now flying. I started again and created a new model, looking at protocol details up here on Github, where it mentions that Ch5 is rate, so I set a switch for channel 5, and then just took a guess at Ch6 being throttle cut, and that did it. I was only able to fly for about 20 seconds, before the batter needed charging, just because I'd spent so long trying to trouble shoot. Just charging the battery now, I'll need to buys some more. Anyway thanks Pascal and pitts-mo for your help, I didn't think I'd ever get this thing flying.
Trying to bind a Esky 150 micro heli v2 ("Airwolf") without success to a Taranis with iRangeX module.
Module is in serial mode (both red and green leds are solid).
Model settings: External RF: Multi - Esky150 Version: v1.2.0.17 Tried the bind option on the tx.
On heli there is a blue led binking and after a few seconds a green led flashing.
On the deviation forum there is a discussion thread about different versions of the protocoll. Is the latest version used here? https://www.deviationtx.com/forum/6-general-discussions/6446-esky-150x-which-protocol?start=80