Hi

I've recently purchased a Jeti DS-14 + REX7 for my Goblin 570. It's nice to be able to buy myself birthday pressies

I would like to know the answer to two questions:

1. What throttle frequency should I use in the gov/throttle settings for the 80HV Jive Pro? I do not intend to use the governor, but I would like to have the frequency correct because my master throttle cable from the Jive Pro is plugged into AUX on the Spirit FBL.

2. What's the expected transmitter throttle throttle curve value in the transmitter I should use to reach approx 60% throttle signal going from Spirit into the ESC?

#2 above might sound like an odd question, you'd normally think the answer is "roughly 60% dude". However, I believe I've calibrated stuff correctly and I need to set 18% and 19% for ID1 and ID2 respectively - and that just seems to me to be dead wrong. So before I maiden this setup I figured it's best to ask.

Here's what I've done with the goblin 570 setup - sorry for the long post but I wanted to be clear about the steps I’ve already taken, and of course there’s quite a few components to setup these days - so, I’ve:

- ensured the JLog 2.6 has the correct firmware for the Kontronik Jive Pro / Jeti EX (26-K_E-41.23.bin) - and that I'm not subject to the recent bug introduced by Kontroniks latest firmware for TelMe (which I'm not using) that apparently stuffs up the calculation of RPM.

I've triple checked the values I entered into the JLog that are used to calculate the headspeed telemetry values. I run a Pyro 650-620, so that's a 10 pole motor with 206 tooth count, and a final drive ratio 1:9.8 - both JLog and the Gob 570 manual agree on these ratio numbers.

- confirmed that the REX7 has the latest firmware, v1.01, specifically the latest version ensures the gap between frames is 2ms (IIRC).

- upgraded to Spirit FBL 2.0.1 I re-did all the configuration, ensuring the 0-100% values appeared in the diagnostics tab, that the tail limits we’re correct, mounting direction was correclty and used my Soko heli tool to level the head and get correct values for collective/ail/ele limits.

- I have manually verified that the FBL corrects in the right direction, same for bail out, and for tail direction and correction.

- I’ve reset the Jive Pro using Mode 1, then Mode 4 and cross checked using the ProgUnit on Windows (also to set 7.4v BEC voltage).

- When I use 18% the telemetry shows me a head speed of approx 1950, for 19% its approx 2050.

So back to my question - I wonder why I need only 18% for ID1 and 19% for ID2 - that seems waaaaay to low - anyone got some ideas I can try out?

_________________
--
John Clayton

I just reset everything again - not much change in the sense that my throttle curves to get the right RPM now require 19% and 20%. While I was looking at the throttle curve UI in the Jeti I wondered... when setting a throttle curve in the Jeti, I use a constant value - the following is what I set for Autorotation (e.g. normal mode):



Am I correct in interpreting this: the throttle value is a constant, and it'll always be 17% of the input? OR does this mean, the output will be 17% of 50% of the input, e.g. if I put in 70 then the output will be 17% of 35 (50% of the input).

Guess I need to read the Jeti manual again.

If anyone has a great explanation of how to read/interpret the throttle function curves - that'd be awesome.

_________________
--
John Clayton

One way to check could be to temporarily activate the Spirit Governor and double check your values there.

For this you should also set your Jive to work with an external Gov, and plug the RPM sensor in the Spirit though.

Then enter 5 in the Spirit sensing divider (poles / 2), 9.80 in the Gear Ratio and 2050 in the Max Head Speed.

Sending 100% from the TX you should see Requested RPM 2050.
Sending 94% from the TX you should see Requested RPM 1927.
Do you see those values?

What do you see as Current RPM?

_________________
Oxy 2 ♦ X-Vert ♦ Warp 360 ♦ Blade 450X ♦ Blade 450X Nightflyer ♦ Goblin 500 (RIP) ♦ 2 X mCPX v2 ♦ night fly mQX ♦ LadyMQX ♦ nano QX ♦ nano QX FPV ♦ Inductrix ♦ DX8 G1

I may be having a blond-moment, but any idea how I get RPM from the Jive Pro to the Spirit?

_________________
--
John Clayton

Ooops. True. Jive does not output RPM sensing. You would need an external RPM sensor.

Not familiar with JLog, just trying to help... checked if you have to set the value about poles to 10 or 5?

_________________
Oxy 2 ♦ X-Vert ♦ Warp 360 ♦ Blade 450X ♦ Blade 450X Nightflyer ♦ Goblin 500 (RIP) ♦ 2 X mCPX v2 ♦ night fly mQX ♦ LadyMQX ♦ nano QX ♦ nano QX FPV ♦ Inductrix ♦ DX8 G1

UPDATE: Throttle %ages as specified previously are not accurate.

The initial measurements were made with no blades on and (surprisingly? unsurprisingly?) it turns out that having the weight of the blades plays a large role in what the ESC will output in order to gain a particular head-speed.

The new %age values in my Jeti for ID1 and ID2 are 22% and 24% - ok, so not a massive difference. I recall seeing 1340 RPM on the Jeti when I had the Goblin 570 sitting on the ground and tried ID1 for the first time not really what I had expected. I ended with ID1 @ 22% for 1920 and ID2 @ 24% for 2150 RPM (21t pulley).

In any case, the maiden flights went very well and while I still don't understand why the throttle %ages are so low - the heli flies well, and I can confirm that tuning a heli using the Jeti integration ROCKS. Here's my tuning workflow now:

1. take off, test a particular attribute (e.g. pitch pumps for tail, ail/ele inputs for man gain etc)
2. land, and hit throttle hold (this forces slow start up and not autorotation-fast-startup)
3. use the Jeti <-> Spirit integration to adjust a value
4. go to step 1 by coming outta throttle hold
5. rinse / repeat

Compared with tuning the heli with Android or the computer - its *such* a joy!

_________________
--
John Clayton

Good, now you fly it so you can check the RPMs with an Android App or a Magic Mirror to compare to your readings....

_________________
Oxy 2 ♦ X-Vert ♦ Warp 360 ♦ Blade 450X ♦ Blade 450X Nightflyer ♦ Goblin 500 (RIP) ♦ 2 X mCPX v2 ♦ night fly mQX ♦ LadyMQX ♦ nano QX ♦ nano QX FPV ♦ Inductrix ♦ DX8 G1

Or I can attempt to perfect my piro-flips Raaaaaa! Lets go!

_________________
--
John Clayton