JJRC H20 Hex Quad

That is fine for me. I am getting the Eachine E011 instead of reordering the F36. E011 is using something similar to bayang protocol. It has bigger motors. Hopefully it can carry more than my H36 and its auto hover is not as annoying as my H20H on stock TX.

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

Not sure if the E011 actually has auto hover. The link is about FC of another H36 like quad. No altitude hold to worry about is fine for me. That should not take too long to arrive via ePackage.

Almost a month after last post, my E011 is heading out towards Canada. Shouldn't take too long via ePacket.

The F36 ordered early Jan 2017 and the H36 batteries ordered in 2016 have not arrived. If they ever show up, they would break the record of longest shipping time.

How about the H20H protocol, any news on that?

Thanks, I'll try it out.

Been testing F36 against H36 today. The F36 stock TX is flyable after adding FPV camera (about 5g) onto F36. Without the extra weight, throttle through the stock TX is bouncing up and down especially on fresh battery, it could be poor throttle curve or simply not enough resolution.

H36 with devo 10 is definitely more precise and smoother.

goebish wrote: Here are test builds for H20H:
www.dropbox.com/sh/a8ppobevjuvdazd/AAB59...6wtW1u919Sss17a?dl=0
H8_3D protocol + H20H format option

CH5: emergency motor stop
CH6: flip
CH7: snapshot
CH8: video
CH9: headless
CH10: RTH

accelerometer / headless calibration: same sticks position as stock transmitter

I'm not sure CH5-CH10 are correct, so please test carefully.

Please report

I cannot open zip files for devo10 or devo7e. Please check.

Regards.

Tried it again. Should be OK now. Please ignore my last message.

Goebish

No problem in binding using the test load. However I haven't figured out how to get the H20H airborne consistantly even after I managed to get it up in the air a couple of times.

Do we need toggle channel 5 back within a certain time after switching it on according to the capture? When I switch channel 5 on, the motors started but then shut down shortly after. It turned off the lights when I toggled it back and forth a few times. Sometimes I can get it airborne before the motors shut themselves down. Once in the air, cyclics and yaw worked correctly.

When I can get it up consistantly, I would verify others, e.g. flip, headless and return. Any hints on how we should drive channel 5.

Thanks.

And this may have something to do with throttle as well. The throttle is spring loaded on the stock TX, that it auto centers at idle.

It works. Switch channel 5 to on to start the motors and keep channel 5 on in flight.

The throttle on the H20H isn't a normal throttle. It is kind of a 3 position switch, step up in height, no change and step down in height. After starting motors, throttle stick up passing a certain position would shoot the H20H up from ground. It looks like the H20H control would not take other commands from the TX untll it achieves its last goal. For example if it hits the ceiling before it finishes an altitude increase, it won't come down with throttle down on TX or even channel 5 off. It won't listen to any commands either after running into my blinds and hanging 90 degrees there, insisting on levelling itself. We don't really have throttle control in regular sense. The only way I can get myself out of it is to power off the TX and wait. That is why I don't like the H20H.

There was something wrong with the battery/battery connector a few crashes into testing last night. My H20H came with a battery with one broken solder tag inside. Very little solderable space was left. It was completely gone last night. I could not solder it back on any more, so RIP my stock H20H battery.

Then I used the remaining battery cable to adapt my H36/F36 battery for the H20H. It turned out the H20H battery connection was loose as well.

Since that kind of battery/connector was the one I had, I decided to replace the battery connector on board of H20H with the H36/F36 connector. After all seemed working fine. I pulled out the solder pad on the H20H after a test. I hate surface mount connectors with tiny solder pads. I had bad times with those surface mount servo connectors on my HCP's. We can easily break them on disconnect. They cannot handle any stress. Come on we use a connector there so that we can disconnect and reconnect...

I spent more time repairing the rail and resoldering the connector with a longer cable far away from the damaged rail.

Of course the CG is off after. For 3-axis gyro, it is no big deal. For 6-axis gyro on H20H, I have to carefully position the battery to the front to offset the new connector weight otherwise it would pop up right into my face during airborne. We have zero cyclic control at that time even if I give it full elevator before take off.

Sorry for the rant. After all binding and channel 1 to 5 work fine. I'll check the rest later.

Thank you for the good work.

Flip, headless and RTH work fine. One flip per channel 6 on. For more, toggle channel 6 off and on. I cannot verify 7 and 8 since my H20H does not have any camera.

The default number of channels is 11 for the protocol. What is on Channel 11?

I put channel 11 on a switch. it turns lights on when it is on and lights off when it is off. It works like a light switch for H20H. However if we turn lights off in flight it also turns off the motors like channel 5. We can still fly with lights off when we switch off the lights before takeoff. Turning lights back on in flight does not cause any problems. Strange.

One thing I forgot to mention, to airborne, we have to put the throttle stick at centre before flipping channel 5 to on. Then throttle up to pop the H20H up. If we keep the throttle down like ordinary aircraft, the motors would shut down again zoon after starting them with channel 5. We probably won't have time to pop the H20 up before motors shut down. Throttle on stock TX is spring loaded to keep it at centre on idle, we have to operate it same way on devo. I won't spring load my throttle stick on devo though.

BTW, my H20H yaw clockwises slowly on devo but holds solid on stock TX. I have calibrated the sticks but I still need trim to stop the yaw. I do not notice that on controlling other aircrafts with my devo10. Is that anything special on coding channel 4 for the H20H protocol, or could we be missing a gyro setting? It is still flyable, not a big issue.

Go ahead merge it. If others find anything else, you can always add changes to it afterwards. Protocol is usable at this stage.

Thanks.

goebish wrote: Channel 11 is for camera gimbal (up / down).
Ok, so let's merge it into trunk, it should be available in the nightly soon, thanks !
github.com/DeviationTX/deviation/pull/266

H20 mini / H30 mini coming soon.

You want the rest of the captures then goebish? I've still got the controller wired up. Unless you've got your own mini's of course.

I one and only one H20H. Stock battery is dead. I am flying it with my V911 batteries on new connectors. I have 8 of them never used. My V911 is still on old connector.

It flies well on devo 10 now, just have to get used to the special throttle operation and don't run it into the ceiling and blinds.

Just the bind captures of each one so far. They were identical. IE. H20 mini flies with H30 mini TX, and vice versa.

www.dropbox.com/s/rtoxwfra43uy4o3/JJRC.H....Mini.logicdata?dl=0
www.dropbox.com/s/vrkonzu2kjf6uk4/JJRC.H....Mini.logicdata?dl=0
www.dropbox.com/s/ig3vfr5m44wmx43/JJRC.H....Mini.logicdata?dl=0

I just looked on the bench and there's 2 more I haven't unboxed yet . I'll wire them up as well. So total = 2 x H20 mini/2 x H30 mini.

Just let me know if you want only bind captures, or some stick/button captures as well