JJRC H20 Hex Quad

Thanks for the advice. Ch5 works properly for arming and emergency stop after removing Ch11.

ajtank wrote:
@wasp09
Could you test ch11 again as above?
Did you capture at maximum rate?

What maximum rate? I did not have D/R.

I have channel 5 on a switch. I keep it same state in flight. If I turn off lights in flight via channel 11, it would bring the H20H down. However I can turn/keep lights off, take off and keep flying.

Anyway, this is a side effect with unknown result. Just avoid using it.

FDR wrote:

goebish wrote: Is there a reason it's not in the template hardware.ini files ?

Yes, because it is dangerous.
If we had it in the source, everybody would have the same txid!
I would strongly recommend to set it to some random value instead of 12345678...

Is that a way to find out what the tx id is on my devo 7e, like printing it out under some menu? I have more than 30 models on my devo7e. It is hard to rebind them all, especially satellites and walkeras. If I know the txid of my devo7e, I can set the txid of my devo 10 via hardware.ini. I don't have that many models on my devo 10 yet.

Thanks.

OK, I'll look into that piece of code to see what I can do.

Why do we want to add randomness?

Suppose my devo7e goes bad and I get a new one to replace it. Restoring the ini files should get it back into action without rebinding.

Thanks.

wasp09 wrote:

ajtank wrote:
@wasp09
Could you test ch11 again as above?
Did you capture at maximum rate?

What maximum rate? I did not have D/R.

I have channel 5 on a switch. I keep it same state in flight. If I turn off lights in flight via channel 11, it would bring the H20H down. However I can turn/keep lights off, take off and keep flying.

Anyway, this is a side effect with unknown result. Just avoid using it.

Did you set the stock transmitter to maximum rate when you used the logic analyzer to make the SPI capture? It seems to me the quad with Devo Tx is not responding as fast as with stock Tx.

ajtank wrote:
Did you set the stock transmitter to maximum rate when you used the logic analyzer to make the SPI capture? It seems to me the quad with Devo Tx is not responding as fast as with stock Tx.

Can't remember now, it's quite a while ago. I think we captured the rate change events but probably not the cyclic and yaw outputs against each rate. However full channel range is fixed, normally we set it to the highest rate in implementing the protocol. With the full range, we can create our own rates/curves under the mixer menu if we need anything else,

I just flew my H36 (with F36 motors and frame), E011 with FPV camera and H20H on my devo 10, all at full rate. H20H is most sensitive among the 3. Unless we want them spin fast in headless mode, yaw on H20H is a bit excessive for normal flight.

I definitely would not call channel 5 emergency stop. My H20H landed too close to a box and it decided to stick vertically onto the side of the box. Channel 5 could not stop it. Throttle down could not stop it. It only stopped a few seconds after I turned off my devo. I still hate altitude hold.

I believe the logic of the H20H FC is to level first before servicing any requests unless it's a signal loss. It cannot reverse the motors and ends up stuck. Channel 5 cannot shut it down. I'll check if chanel 11 shuts it down next time it happens.

Haven't flown my H8 mini and 3D for quite a while. Forgot how it was like.

Now I an busy with FPV. The camera is on my E011. And I have to sort out the ID for my Q90 using sats...

Looking at the code for tx id, we have been using up to 12 bytes. I guess we preferred making up the length by using rnd instead of taking a long ID directly. Anyway I am not going to be able to find an entry that matches my devo7e id, unless we modify the code for longer intake and then try figuring out the MCU id...

The current implementation could have been good if we know it before hand i.e. before we loading up our first devo.

Let me put tx id on right now to prepare for the future.

I'll go through the rebinding when needed. First one, opening up the Q90 again to rebind the sat to both devo...

Yes, I spent the afternoon going through lots of stuff that I haven't flown for a while.

The ones requiring rebinding are mostly 450s with kbars and lemonrx sats and some walkera birds using fixed ID including HiFa a plane. For walkera birds, we have to reset to not fixed ID using a rebind plug first and then add the fixed ID back while TX is talking to RX with non-fixed ID. I have to read the manual word by word to figure that out. That seems completely news to me. How did I manage to set fixed ID before?

I only have orange standalone RX to rebind my lemonrx sats. By default the sat comes up as 7 channels. For 450s configured on devo7e, I had been configuring the sat as 8 channels even though I am using only 6. When I configured it back to 7 channels, one of my 450s would not initialize its ESC/motor. It worked if I fed the kbar and sat from another ESC. It's a weird timing issue among sat/kbar/ESC. That might have been why I set number of channels to 8. Obviously I forgot about that too.

Going through my fleet brings back a lot memory and reveals something have been forgotten...

Anyway I still have a few more to rebind. I also have a few not covered by deviation yet, e.g. F36, L6F...

BTW, I have a devo10 and devo7e with 2 extra 2 way switches. The model files can differ in switches and knobs.

Hey goebish.... finally got to finishing the 4 in 1 install and tested your H20/30 mini build. Looks good. I hate flips, but for completeness sake I'll check it works when it isn't 6:30am and I haven't slept =). The controls for the H30 are all reversed, but that's no problem. Does that sort of thing make itself known to you during engineering?

And btw, THANKS!!! You rock.