JJRC H20 Hex Quad

Good point. Even though the exit error also happens without connecting to the clone analyzer at all, I suppose we won't get support unless we are a customer. I am also running Debian unstable with 4.5 kernel, they probably won't support anyway.

I'll check up the test load after work.

goebish wrote: Ok, please check if calibration is working with both sticks bottom right:

Devo 7e: www.dropbox.com/s/rf6fcpyg3dgjoy1/deviat...0.0-750e0f0.zip?dl=0
Devo10: www.dropbox.com/s/na348cvupe4j77l/deviat...0.0-750e0f0.zip?dl=0

Regarding your issue with Logic software, just try another version (I'm using a beta and I've no issues), but anyway, if you're using a "clone" hardware, I wouldn't send an error report, just buy the real thing if you want support

That works on my 7e. Thanks. I don't have any extra modules on my devo 10 to verify it.

Why would a manufacturer make it different for every model? Do they want to keep selling as many models of TXs and RXs like Walkera did before they discont'ed everything!

goebish wrote: Regarding your issue with Logic software, just try another version (I'm using a beta and I've no issues), but anyway, if you're using a "clone" hardware, I wouldn't send an error report, just buy the real thing if you want support

Just tried the same version of Logics on my ubuntu trusty laptop at work. It exits cleanly.

Actually there was a bug reporting that if we don't send the fault report, Logics would not remove the core file and keep asking us on every start up. Let me delete the core file to see if it helps when I get back home. However I remember the timestamp was current last time I looked at it. It was a SEGV on exit. I am running Debian unstable at home, probably the libs are too new for Logics.

+++++++++++++++++++++++++++++++++++

Removed core file. Now it won't ask me to send report on start up at home.

I think there may be a bug in setting the rf channels. In h8_3d_nrf24l01.c the code is:


rf_channels[0] = 0x06 + (((txid[0]>>8 ) + (txid[0]&0x0f)) % 0x0f);
rf_channels[1] = 0x15 + (((txid[1]>>8 ) + (txid[1]&0x0f)) % 0x0f);
rf_channels[2] = 0x24 + (((txid[2]>>8 ) + (txid[2]&0x0f)) % 0x0f);
rf_channels[3] = 0x33 + (((txid[3]>>8 ) + (txid[3]&0x0f)) % 0x0f);

whereas in www.deviationtx.com/forum/protocol-devel...-quad?start=60#39934
the comments are:
TX2
id: AF C5 17 00 chk: 8b
ch: 10 17 2C 33

ch0: a+f=19 %0f=0a; 06+0a=10
ch1: c+5=11 %0f=02; 15+02=17
ch2: 1+7=08 %0f=08; 24+08=2C
ch3: 0+0=00 %0f=00; 33+00=33


Shouldn't those ">>8" be ">>4"? (This might also explain the latency issue that was reported in this thread, since only some of the packets would be decode.)

Hi,

I have received the JJRC H22 today (AFAIK it has the same FC as Eachine H8 3D) and I have the same problem with calibration not working, like I have with the JJRC H22.

Can anyone confirm that it's (still) actually possible to calibrate with H8-3D protocol? It would be great to know if it's just me, since I don't know what I'm doing wrong and don't have any ideas left.

Both sticks lower right = works for me on stock TX with JJRC H22 & JJRC H20, but not with Deviation.

Both sticks bottom left works for my H11D with nightly build. Please make sure no D/R when calibrate.

Here is an ini file for my JJRC H20 using a Devo 7e transx. I am using dual rates via fmod sw. I have flip control on throttle trim switch (momentary).
I never use the rudder trim for trim, so I used it for Headless mode toggle. I am using a sticky throttle feature also! I like the way this ini file works! Nice built in safety.

BTW the channels for the H20 are as follows:
CH6= Flip Mode (momentary), full ail/ele while engaged.
CH9= Headless Mode (toggle) On/Off
CH10= Return Home

I've tried to bind the JJRC H20C (cam version) with the Devo7e NRF mod and it does not respond to the same protocol as the H20 (non-cam version).

Has there been any attempt to develop the protocol for this H20C model??

Hi there,

I am ordering a JJRC H20H. It has no camera but alt hold:



It hasn't arrived yet. It think a hex with alt hold may be better than a regular quad in carrying an AIO camera, so that I can do some FPV indoors during winter.

I wonder if anybody have luck binding H20H with deviation.

Thanks.

++++++++

According to the tracking, the H20H was in Customs last weekend. Many of my still outstanding orders had been in that state over a month ago. Hope I'll get something soon.

Anyway if H20H requires more work, I'll post the trace in a new thread.

My H20H arrived last night finally, with a dead battery though. I don't have any battery with that kind of plug. I have to make up a temporary battery adaptor to test fly it.

I cannot bind the H20H to my devo 10 using any of the nRF24L01 based protocol. Hence I need to find my capturing kit, hopefully this week end. Hope some developers are still interested to add it to the support list.

The H20H is very sensitive to CG. I have to tie my longer batteries onto the bottom to keep it centre enough to stay airborne. It has less lifting power for extra weight than I hope (to host my 5g camera + bigger battery) probably something to do with the altitude hold being targeted for a fixed AUW.

The throttle stick on the stock TX is spring loaded for self centring. Throttle is kind of in a rate mode. Stick idling at centre would keep the hovering height as is, up to stay higher, down to stay lower. We also press the throttle stick down to start/stop the motors. I wonder if throttle status is also a factor in binding, spring loaded throttle is something new.

Regards.

Thank you in advance. I really have to find my capturing tool.

I wasn't able to post the capture files here. What is the proper way?

Spent the whole evening going through bags and boxes. Had no luck in locating my capturing tool yet. The chance of H20H using the same protocol of H20 is quite low. I have tried the reverse, i.e. using the stock TX to bind with H11D, it did not work either.

The stock TX uses a RF chip labelled xN29 with 2 faint digits which look like 7L, but it only has 8 pins, i.e. 3 pins left for the MCU after counting ground and VCC, RF out and 2 pins for the crystal. Does that make sense?

++++++++++++++++++++++++++++++++++++++++++++++++

Found the Saleaelogic. I was looking for a lot of cables but I put it inside my bag of test probes, no cables at all,.

Eight pins including connections to antenna and crystal seem too few. Anyway I can probe every pin. It's too late to start probing for today. That would be a task for tomorrow.

Good night.