JJRC H26D

hexfet wrote: There's no info in the altitude hold or flip captures - just the bind sequence followed by unchanging data. Need to get the altitude hold info.

I've updated the test build with the following changes. Please check and let me know.

The gimbal code is changed to just use the fixed rate same as the stock tx. If the channel is outside +/-50 the gimbal will move, otherwise it will not. See if this is easier to work with than the previous version.

The txid code is changed to same as the x800 (basically ignored). Should still work.

I was able to build a 7e version with gcc 4.8.4 Cannot build the 7e with 4.9.3 due to space.

Ok Just tested last build.. Yes the gimbal control is much better now with pots

and the Devo7E build is also working

Great Job as usual )

Nice video

Please try the gimbal again with the updated test build. I simplified the code quite a bit.

Can you also please test with an MJX model? I put in the table of txid to rf channel mappings we've found so far, selected by fixed ID. No fixed ID should be same as current version. Please try a few values between 1 and 7. Since we haven't figured out the algorithm yet this is something I'd feel comfortable making a pull request with.

hexfet wrote: Nice video

Please try the gimbal again with the updated test build. I simplified the code quite a bit.

Can you also please test with an MJX model? I put in the table of txid to rf channel mappings we've found so far, selected by fixed ID. No fixed ID should be same as current version. Please try a few values between 1 and 7. Since we haven't figured out the algorithm yet this is something I'd feel comfortable making a pull request with.

Part1: MJX X800 test; ID={1,2,3,4,5,7} OK, ID={6} KO
Part2: H26D test New gimbal code OK, ID={} OK, ID={2,3,6,7,9} OK, ID = {1,4,5,8} KO, ID={2222, 4444, 6666,7777,9999,1234,4321} OK, ID={1111,3333,5555,8888,5678} KO

SeByDocKy wrote: Part1: MJX X800 test; ID={1,2,3,4,5,7} OK, ID={6} KO
Part2: H26D test New gimbal code OK, ID={} OK, ID={2,3,6,7,9} OK, ID = {1,4,5,8} KO, ID={2222, 4444, 6666,7777,9999,1234,4321} OK, ID={1111,3333,5555,8888,5678} KO

So only three of the seven MJX txid->rf channel mappings work for the H26D (0-none,2,3). That's enough to make a pull request Please check the updated build - all fixed id values should work. There are only three different mappings so only three aircraft simultaneously.

hexfet wrote:

SeByDocKy wrote: Part1: MJX X800 test; ID={1,2,3,4,5,7} OK, ID={6} KO
Part2: H26D test New gimbal code OK, ID={} OK, ID={2,3,6,7,9} OK, ID = {1,4,5,8} KO, ID={2222, 4444, 6666,7777,9999,1234,4321} OK, ID={1111,3333,5555,8888,5678} KO

So only three of the seven MJX txid->rf channel mappings work for the H26D (0-none,2,3). That's enough to make a pull request Please check the updated build - all fixed id values should work. There are only three different mappings so only three aircraft simultaneously.

Tested successfully (with the previous none-working IDs)
No problem too with the my MJX X800

I recently purchased a H26WH, the variant with altitude hold. It cannot bind using the H26D protocol. The circuit board looks similar to Seby's H26D but it probably carries a different MCU software.



I have uploaded the SPI capture of the binding with the stock transmitter here

Any comment on whether it is a known protocol is much appreciated.

Yes I did try all available options under MJXq but no joy. The chip on the top edge is RFX2401 (PA+LNA) whilst the chip next to the crystal is covered by black epoxy. According to previous threads it is supposed to be a Beken transceiver.

Thanks for the prompt feedback. I noticed Seby's H26D did not have a button to start the engine. The throttle can action as soon as binding has completed. On my H26WH I have to press the Altitude Hold button to start the engine before the throttle can work. By the way my radio is a Devo 10, thanks.

It would be really nice if that button can be skipped. Looking forward to the trial build.

I also got hold of a JXD 506 ( a gigantic version of JXD 510) which binds with V202 protocol. However it also requires a start button before throttle can apply. I am going to open a new thread for this quad later.

goebish wrote: It's pretty similar to the H26D format, looks like only the nrf24 address is different, I'll post a test build later today ...

Sorry if I miss anything. Has the test build been posted yet?

Thanks for the build. Things are weird.
First it can bind successfully. However I cannot arm the quad. The stock transmitter throttle is always centred and if I move it down and press the arm button, motor will not start. I tried to centre the Devo throttle during binding, but motor still would not start.
I just discovered my camera was faulty and so I could not test photo and video. However the camera can pan and tilt properly using Devo transmitter.
By the way there is no light on/off (ch5) on this quad and the stock transmitter also does not offer this feature.

Yes. One capture only covers the binding and another one covers binding + arm + disarm. I can redo any capture if needed, just let me know, thanks.