JJRC H20 Hex Quad

fwiw, I have been using 401 build cb08cba with the h20 and its been pretty good. good work (overall; I have at least 6 models in my 7e; every single one of my quads/etc has 7e support!).

not sure what was going on when I first tried it; I was seeing some lag or latency and it was more obvious on pitch and roll changes. it may even be that my batteries on the 7e were low; after I recharged them, I -think- the latency problem went away. I'm using the amped nRF24L01 chip and maybe the extra power and low charge AA's were the culrpit.

now that I'm making sure my batts are fully charged, I am not seeing any latency and this is one of the smoothest and most controllable indoor fliers I own. love it!

thanks for the good work. someday, I'd like to be able to build 7e images, as well; but for now, I have to run builds that others kindly make available.

cheers,

/bryan

Deal57, sorry for my lack of knowledge but did you have to install a hardware module? or is it just a matter of a software update to get the jjrc h20 working with deviationtx?
Thanks in advance.

goebish wrote: You've to install a nrf24l01+ module.

Doesn't the normal NRF24L01 from BG work with the H8-3D protocol?

goebish wrote: Any nrf24l01 ("normal" or "+") works for this protocol, only 250kbps protocols requires the "+" version.
I think all the boards on bg are the "+" version anyway, the "normal" version is not produced anymore.

Thanks, what a relief. Since it is not documented in the manual, where can I find H8-3D channel usage so I can try to configure a JJRC H20 on a DEVO 7E without extra switches (even if it has to be a basic config without bells and whistles)?

Does anybody have issues to calibrate the JJRC H20 with Devo7e or could tell me how to exactly do this?

Both sticks lower left for headless calibration = this works on stock TX and my Devo 7e
Both sticks lower right for gyro calibration = this works on stock TX, but not on my Devo 7e

I thought that I might have configured the rates too low or the like, but I couldn't figure it out why it's not working.

My H20 has the red PCB with timestamp label 2015.05.28

The behavior implies that your sticks may be calibrated slightly differently from right to left. You might be able to see a slight difference in the channel monitor, but maybe not. In any case you can try a few things:
- recalibrate your 7e sticks and be sure to apply even pressure to all sides... Some gimbals may have a little "give" when you push them one direction, and you want to have them even. Be sure you have centered your Trims BEFORE calibrating.
- give a bit of right trim to get it into calibration mode, then center it back... I don't know if that will affect your flying after...
- slightly increase your scale on the aileron and rudder channels, say to 105.
- fly without worrying about calibration ... I've only ever done the calibration maybe once to see if it works. Maybe that's why it seems so lively to me?

Thanks for your suggestions.

I tried recalibrating the sticks, centering the trims (also with stock TX before, in case those values are stored in the FC), and increased the scale on AIL and RUD to 105, 110, 125. All steps with no luck.

Btw. the same "gesture" (both sticks lower right) works well with my Devo 7e and Eachine H8 Mini, so I'm not sure if there are stick calibration issues.

However, I can confirm that flying without worrying about calibration works most of the time It's just that I don't really want to depend on the stock TX.

Tested channel 7,8 and 11 on my devo 7e. It works. I only have 4 two-way switches there. Now I have to recall how to make use of the up and down buttons or throttle trim for stepping the camera. I've done that once, but I forgot. I don't have any extra RF modules on my devo 10 yet.

Thanks.

I have a hard time implementing the camera up and down on 7e using trims or buttons while it is perfectly fine on a devo10 with 3 way switches. However my 7e does not have any 3 way switches. As up and down are on the same channel 11, that does not like taking 2 momentary trims going in opposite directions. It seems to be able to take one and cannot really inverse and offset them too. Perhaps we are supposed to use virtual channels to preform the trims first, but virtual channels does not seem to respond to trims at all. I am going to read the manual to see why not, since we can configure them on the trim page.

Of course I can use 2 swtiches for the gimbal, 1 for D/R, but I only have 1 switch left even if I don't use TH.
Could we also put camera down on channel 12 such that camera down would be controller by either a low on channel 11 or high on channel 12? That makes life easier for devo 7e without a 3 way switch. For devo with a 3 way switch, we can use channel 11. For my poor 7e, I'll use trims/buttons to pulse both channel 11 and 12. Leaving the switches for more frequent tasks.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
OK, the new manual gave me some hint. For the virtual channel to response to trim, it has to be set to src from itself and the curve should be set to 1+1.... I guess once we have a trim as source we should be OK to pack 2 trims into a signal channel 11. Just noticed that we can only configure 6 trims on devo 7e (10 on devo 10). Have to kick out all existing trims for cyclics and rudder to make way for the other 7 channels.

goebish wrote: Thanks for reporting, I'll make a pull request so it's included in the nightly then

I noticed one little thing though. H11D does not respond to sticks at bottom left. No D/R yet, TX monitor reports the sticks are at their corners correctly (with channel = +/- 100),

There is a reset button on the H11D stock TX. With throttle stick at bottom and reset button held for 2 seconds, LEDs on H11D flash. I guess "reset" on the stock TX = ACC calibration.

As I've ran out of switches and trims on my 7e already, there is really no urgency to get this to work. The best I can do is make reset share a switch with others like TH.

Regards.

I'll resolder the leads on again to capture probably some time this week. Thanks for looking into it in advance.

BTW, I notice that at9 code is in the stream. Does that work? Too bad I'v just bought a devo 10.

Postedt the reset capture in RCGroups again.

] www.rcgroups.com/forums/showatt.php?atta...9046796&d=1464751940

On H11D, headless mode is channel 9 and RTH is channel 10.

BTW, how should I exit Logic? It always asks me if I want to send an error report on next run. Perhaps I should if there is no known way of a clean shut down.

Thanks.