Hello!

I connected my Jivepro120/SpiritPro with the Cable Kontronik cable and connected correctly.
Unfortunately, I get totally wrong RPM signal displayed in the DS16.
I have already set in the JivePro software RPM to 1.00 and MotorPole to 2, but also set normal for an XNova Motor and GearRatio.
Always have wrong RPM in the display.
What do I need to do to get correct RPM signal?

Thank you!
Greeting

Hi,

you have to set settings in the General - Throttle/Governor window - Sensing Divider and Gear Ratio.
The problem is that in both you can set the same parameters. So they can be configured only in one to display correct values.

_________________
Spirit System developer

I do not use an external sensor!

Of course, these settings also apply for ESC RPM sensor!
To access them, you have to temporarily enable Governor, then disable it after settings.

_________________
Spirit System developer

Ah, Ok!
And in the JivePro I do not?
I have an XNova Motor.

Hi!

I now have a lot of settings through.
Unfortunately without a successful result.

My target speed: 1050-1600
Software v 2.4.1

According to Tomas, I set my Gear Ratio to 12.30: 1 and Motor Pole to 5 (XNova) in the Spirit.
(Governor of course deactivated!)
Here I have in the DS16, at Idle 1, of 154 ...?
Now comes a strange component in the game. I switch to Idle 2 and / or 3 decreases the RPM in the DS16 to 5 ... ???

Then I set all the data "the other way round".
In the JivePro my gear Ratio of 12.30: 1 and motor poles set to 10. In Spirit Gear Ratio on 1 and Motor Pole also on 1.
Even then I do not get any result.

Would be pleased if there is someone here, where it works!

Did you tested it with provided firmware or it is official?

With our Jive Pro 80 it is working nicely when comparing between external RPM sensor.
Everything in default in the ESC. In the Spirit Settings according the motor - Sensing Divider = Motor Pole / 2 (with the latest firmware) and Gear Ratio per model specification.

Tommorow we will be doing another comparison. So I will provide you further details.

_________________
Spirit System developer

Thank you for your efforts!

Firmware with solution was released right now

The problem was, that Kontronik implementation allow that the RPM overflow (it does not fit in the variable they are sending the data). So Spirit have to find when it overflows and correct the data.

But I hope that everything will be fine now.

_________________
Spirit System developer