JJRC X1 capture

SPI data from this nice racer ....

I don't know if it's a XN297 or a Beken ... (or something else)

mon-partage.fr/f/3yar0KpF/

goebish wrote: Looks like it's a Beken:

29 ACTIVATE(53) bank switch to 1
30 W_REGISTER(00) 40 4B 01 E2
31 W_REGISTER(01) C0 4B 00 00
32 W_REGISTER(02) D0 FC 8C 02
33 W_REGISTER(03) 99 00 39 41
34 W_REGISTER(04) F9 96 82 1B
35 W_REGISTER(05) 24 06 0F A6
36 W_REGISTER(06) 00 00 00 00
37 W_REGISTER(07) 00 00 00 00
38 W_REGISTER(08) 00 00 00 00
39 W_REGISTER(09) 00 00 00 00
40 W_REGISTER(0A) 00 00 00 00
41 W_REGISTER(0B) 00 00 00 00
42 W_REGISTER(0C) 00 12 73 00
43 W_REGISTER(0D) 36 B4 80 00
44 W_REGISTER(0E) 41 20 08 04 81 20 CF F7 FE FF FF
45 W_REGISTER(04) FF 96 82 1B
46 W_REGISTER(04) F9 96 82 1B
47 R_REGISTER(07) 0E
48 R_REGISTER(07) 8E
49 R_REGISTER(08) 63 00 00 00
50 R_REGISTER(07) 8E
51 ACTIVATE(53) bank switch to 0

I'm already on too much protocols right now, maybe someone else ?

Good news if it's a Beken ....so probably very close to the H26D... I guess HexFet will work on it

Here a new revision of the ZIP capture with a new one associated with the right shoulder button even if this one is not used for the X1

mon-partage.fr/f/T3oEgurs/

It's our old friend the Hontai protocol! But on a Beken instead of XN297, and different RF channels. And some of the features are in different bytes

Would you please make separate captures for the sticks? Can't pick out the data from the combined capture. Also a capture of the trims would help. It seems some of the features use the same bits that Hontai uses for trim. You can just export the SPI csv file - don't need the logicdata.

There wasn't anything in the "idle down idle up" capture. What does that do on the aircraft?

hexfet wrote: It's our old friend the Hontai protocol! But on a Beken instead of XN297, and different RF channels. And some of the features are in different bytes

Would you please make separate captures for the sticks? Can't pick out the data from the combined capture. Also a capture of the trims would help. It seems some of the features use the same bits that Hontai uses for trim. You can just export the SPI csv file - don't need the logicdata.

There wasn't anything in the "idle down idle up" capture. What does that do on the aircraft?

Well a relative good news so

Ok I will produce separate captures for both sticks as well as trim


The "idle up/down" select the RPM speed in idle. In practice it's very useful coz if you press down twice, you can desarm the quad instead to wait 10s ...

Here are some new capture in CSV format

mon-partage.fr/f/vT6bxWwM/

Sorry, should have been more specific. Looking for the CSV export from the SPI analyzer (click on the settings icon in the SPI Analyzer heading). Thanks.

hexfet wrote: Sorry, should have been more specific. Looking for the CSV export from the SPI analyzer (click on the settings icon in the SPI Analyzer heading). Thanks.

No problem I kept also session files
Wait 2min for uploading

All sessions: mon-partage.fr/f/qd3TA1EN/

I've updated the combo build with a first draft of this protocol. There's a Hontai protocol option for JJRCX1. It should at least bind and may work almost completely. Even the tx address algorithm seems to be the same as Hontai. Please give it a try and let us know how it goes.

The right stick capture is fine but the left stick and rudder trim captures are confusing. Only one channel changes in the left stick capture, which seems to be the rudder channel. Is there something that has to be done on the stock tx before it starts sending the throttle signal, like moving the throttle to max then back to min? You could capture with the quad on to ensure the throttle signal is being sent (not so easy I know).

The RUD trim capture seems to affect the same channel as in the left stick capture. Maybe that's right since the channel Hontai uses for rudder trim seems to be used for RTH and headless bits.

The shoulder button controls the same bit that Hontai uses for flip, so might be the same on the X1?

I guess the idle down/up only affects the transmitter and doesn't send anything to the quad.

hexfet wrote: I've updated the combo build with a first draft of this protocol. There's a Hontai protocol option for JJRCX1. It should at least bind and may work almost completely. Even the tx address algorithm seems to be the same as Hontai. Please give it a try and let us know how it goes.

The right stick capture is fine but the left stick and rudder trim captures are confusing. Only one channel changes in the left stick capture, which seems to be the rudder channel. Is there something that has to be done on the stock tx before it starts sending the throttle signal, like moving the throttle to max then back to min? You could capture with the quad on to ensure the throttle signal is being sent (not so easy I know).

The RUD trim capture seems to affect the same channel as in the left stick capture. Maybe that's right since the channel Hontai uses for rudder trim seems to be used for RTH and headless bits.

The shoulder button controls the same bit that Hontai uses for flip, so might be the same on the X1?

I guess the idle down/up only affects the transmitter and doesn't send anything to the quad.

Bad news ... it's not binding (with or w/o a TXiD ...)

EDIT: Minor point: The radio is crashing as soon as I want to change from JJRCX1 option to Hantai

I updated the combo build. I'd skipped part of the initialization that I didn't think mattered - it does. In this version the fixed id doesn't matter. If it works I'll add that functionality.

Unable to replicate the problem of the reboot on my Devo 10. Did it occur on your 10 or 7e? Is there an errors.txt file on the USB drive?

hexfet wrote: I updated the combo build. I'd skipped part of the initialization that I didn't think mattered - it does. In this version the fixed id doesn't matter. If it works I'll add that functionality.

Unable to replicate the problem of the reboot on my Devo 10. Did it occur on your 10 or 7e? Is there an errors.txt file on the USB drive?

Good news It's binding

I can't arm yet .... (maybe some channels are reversed)
To arm : i) push both stick in lower outoors (a beep is emitted) then do right-left-right with the left stick

¨Photo & camera buttons seems to work too

A new capture with the specific first step "stick in lower-outter directions" and another one with some left stick mouvements

mon-partage.fr/f/OTv7mSl8/

Great I just updated the combo build with another change that may or may not make a difference. I've also changed the txid to be same as Hontai so hopefully will still bind.

If you can bind but not arm with this build, we'll need a capture with the arming sequence done, then moving the throttle up and down.

SeByDocKy wrote: A new capture with the specific first step "stick in lower-outter directions" and another one with some left stick mouvements

mon-partage.fr/f/OTv7mSl8/

Please make a capture going through the full arm sequence so the stock tx gets all the way to sending a throttle signal.

hexfet wrote: Great I just updated the combo build with another change that may or may not make a difference. I've also changed the txid to be same as Hontai so hopefully will still bind.

If you can bind but not arm with this build, we'll need a capture with the arming sequence done, then moving the throttle up and down.

Ok I will complete with another capture with full arming sequence (both sticks outter then right-left-right as in the video)

Here is full arming sequence + throttle up & down

mon-partage.fr/f/HUVUNmfx/