WLH-08 & JJRC H13C protocol

Thanks for great job of Hexfet !

Now you can try download test build here

It can bind and fly both WLH-08 and JJRC H13C,some functions are hacking by Hexfet.





It's a variant of the MJXq protocol, enable it in MJXq protocol option.



It will move faster if more folks join to test!

@Hexfet

New test build "ee51ea2" has been tested and I got good news .
I tried many different FixID and find the rule, it can bind with FixID which is divided by "8" , for example : 8,16,24,32,40,56 ...... 123456 ....
I tested both WLH-08 and H13C, get the same result!
CH5 for WLH-08 ground / air works fine.
CH6 Filp : not work
CH9 Headless : not work
CH10 RTH : not work

Thanks!

I've updated the combo test build. Hopefully the flip, rth, and hl controls are sorted. This build also sets the txid to random number multiples of 8, so hopefully it will still bind

Ho great news ....

@hexfet

New FW is awesome! I tried both WLH08 and H13C.
FixID works fine with any number
CH6 : Flip OK
CH9 : Headless OK
CH10 : RTH OK (it will be triggered by both -100 to 100 and 100 to -100,set this function to a 'button' is a better choice!)

I don't have camera, I can't test CH7 & CH8 function, sorry!

Here is WLH08 and H13C trim data:
www.mediafire.com/download/a9izkw0fr4mmu...C-H13C-SPI-09-11.zip
www.mediafire.com/download/32fl8v350ve5vgj/WLH08-SPI-09-11.zip

There is no THR trim function on both TX.
When I move trim from L to R or R to L , it always will stop at Mid automatically, I need to press trim button again.

Thanks for your awesome job again!

Nice Thanks for the testing and captures.

I've added driven trims to the combo test build. Hopefully I got the directions correct. Please give it a try.

Good job guys
So the MJXq original protocol is fully hacked now? The rule for TXid as multiple by 8 is also valid for MJXq protocol?

hexfet wrote: Nice Thanks for the testing and captures.

I've added driven trims to the combo test build. Hopefully I got the directions correct. Please give it a try.

All trims work perfert! Thanks!
Last job needs someone to help to confirm photo&video function,but I think it should be ok!

Durete wrote: Good job guys
So the MJXq original protocol is fully hacked now? The rule for TXid as multiple by 8 is also valid for MJXq protocol?

We still need your help for MJX txID,can't find the rule yet!
Have nice vacation!

Thanks!
Probably I will capture from 2 different x800 transmitters.

dc59 wrote: All trims work perfert! Thanks!

Did you notice any difference in the responsiveness of the aircraft? Hopefully the dyntrims expand the control range a bit.

The current test build uses the same txid formula for MJX, so if the MJX quads work with a few different fixed ids, I think we're done

hexfet wrote:

dc59 wrote: All trims work perfert! Thanks!

Did you notice any difference in the responsiveness of the aircraft? Hopefully the dyntrims expand the control range a bit.

The current test build uses the same txid formula for MJX, so if the MJX quads work with a few different fixed ids, I think we're done

Yes, I do more test and find something difference!

This version FW always in LOW RATE, I can't fly it in high rate both WLH08 and H13C, even I set DR to 125 , it still very slow especially for yaw!
I also check MJX X600, I can't bind it with FixID=13,and I do some FixID test as below:
NONE : Can't bind
1~3 and 5 : Bind, but with delay and very small DR(maybe only 10%~20%)
4, 6~9 : Can't bind
10~11 : not stable , sometimes it can bind(also with delay and very low rate) , sometimes it can't bind

I'm sorry,I don't have more time to test more FixID today and tomorrow (family time~ )
If you have any test requirement , I will test it when I back home,thanks a lot!

dc59 wrote: This version FW always in LOW RATE, I can't fly it in high rate both WLH08 and H13C, even I set DR to 125 , it still very slow especially for yaw!

If you got lower rates than before implement Dynamic Trims, maybe the trims packets are reversed reducing the rate instead increase.

Hopefully that's all it is. I've updated the test build. I also restored the known working MJX protocol txid when fixed id is none.

hexfet wrote: Hopefully that's all it is. I've updated the test build. I also restored the known working MJX protocol txid when fixed id is none.

Hi Hexfet,
BINGO ! BINGO !
First BINGO, WLH08 & H13C back to normal , I have high DR.
Second BINGO, MJX X600 also back to normal,but the most excited thing is that I got the rule of txID of MJX. The secret number is '13'
I tried few different numbers which is divided by 13, it bound nice with no delay, I think the same engineer develop MJX and WLH08 protocols , maybe 8 and 13 are his lucky number or birthday

That's interesting. The starting txid from the capture is not a multiple of 13, but adding multiples of 13 to it makes working txid values.

Let's see what Durete's captures show. Almost there

hexfet wrote: That's interesting. The starting txid from the capture is not a multiple of 13, but adding multiples of 13 to it makes working txid values.

Let's see what Durete's captures show. Almost there

Maybe it's formula = '13X+offset' ?
That's better to have Durete's captures, solve all questions.
Thanks!

The good news about capture from X800 TX is we will have the light control also, not present at X600 TX but working if I'm not wrong.
I will capture ASAP, I guess my X800 is waiting at my local post office.

Posted the same at MJX protocol thread.

Just received my X800 . Will capture SPI traces as soon as possible.
After a quick testing using latest test build with driven trims reversed, I found a weird behaviour at rudder channel.
Aileron and Pitch are working great, with a lot higher rates than with stock TX (driven trims working )
But rudder channel, is greatly improved to the right, but after about 50% stick position is not increased any more.
To the left side, to about 50% is working good, at about the same rate as the stock TX, but after pass about 50% stick position, the rudder speed is reduced
I think probably the driven trims are working OK now for Pitch and Roll channels, but needs to be reversed for rudder channel.

Thoughts?

I think you should try replacing line 137 with