No rpm with telemetry. Gov ignores requested rpm

[delta peak]

I´m using Spirit, Hobbywing telemetry with Futaba. All values are displayed correctly, so does rpm. Even in rpm tester menu. The problem is that current rpm in the software is not displayed, but requested rpm. I believe that´s why gov spools up to 100% throttle. Maybe a bug?

[thestructured]

Are you spooling it up while connected to the software? Do you have the RPM wire from the ESC connected to the PIT pin in the spirit or are you just running the telemetry cable from the HW?

[delta peak]

Yes, while connected to software. Rpm cable is not plugged in, since i believed it´s not needed. Only telemetry cable from ESC.

[thestructured]

That is why your gov is not working. RPM cable must be plugged in for the governor to work.

[delta peak]

Can I read this somewhere? Spirit is getting rpm via ESC Telemetry cable, so i´m wondering.

[thestructured]

I offered you a solution and you're asking me to prove that you need the wire? Your governor is obviously not working without it.

Read the governor setup section in the manual, it's in there. http://manual.spirit-system.com/index.p ... n#GOVERNOR

[delta peak]

I know, that rpm wire is needed without telemetry, but I´m a little confused that wire is still needed with rpm already been displayed.
Anyway, thanks for help!
I plugged rpm wire into pit. It works now

[LogoX2]

I know, that rpm wire is needed without telemetry, but I´m a little confused that wire is still needed with rpm already been displayed.
Anyway, thanks for help!
I plugged rpm wire into pit. It works now

Because the only thing the Spirit does with Telemetry is pass the information through to the TX.
You need the RPM wire for Spirit governor.

[ZeXx86]

Telemetry data are too slow for Governor. They are displayed only for pilot and telemetry purposes. But Governor require direct measurement that is much faster in order to react quickly for any RPM deviation.

thestructured: Thank you for your support!