Helicopter 3.6.0 Firmware can not get RPM information

ArduCopter Traditional Helicopter
1

Hi guys
I’m Rico man.
I needed your help, so I wrote this.

I started with 3.5.7 and tried all 6 to 12 beta firmware.

And there was a problem while testing 3.6.0 today.

pixhawk can not get rpm

Using multiple versions of firmware
In some versions I could not get rpm, but of course I got it somehow by changing the AUX port.

But 3.6.0 is not.
I checked all the AUX ports 2 through 6, but I did not get the RPM.

I checked the binary log, and even in the binary log, Pixhawk did not get rpm itself.

What the problem is …

2

In 3.6 you have to set the rpm type to 2 instead of 1.

3

Hello Chris
I missed your answer

My helicopter has a governor called aero spire.

The rpm type was set to 2

rpm Type 1 and 2

rpm rpm1 and rpm2 have been tested several times alternating.

There is no trace of accepting rpm information at all.

4

I use Aerospire governors too. But that doesn’t have anything to do with the rpm that you get in Mission Planner. The Aerospire has its own hall effect pickup device. You need a separate rpm pickup for ArduPilot and use pin 54. The Aerospire hall effect sensor works fine with ArduPilot’s rpm, but it doesn’t work if you try to y-cable it.

5

Hi Chris
I’m using y cable as you say.
The line from the tachometer goes to the one on the governor, the other to the Pixhawk aux.
I’ve been getting rpm information so far.
If you do not receive it, you can get it if you change the aux port.
But different in 3.6.0
Does not work on any aux port

It’s a feature that worked well over the y cable.
If you are not working in 3.6.0
Do I have to attach other sensors to my helicopter?

6

I’ve only gotten it to work with dedicated hall effect sensors. A hall effect is a transducer and it requires proper VRef and ground to work. y-cable it and you’ll get erratic governor operation, or erratic readings on the ground station.

7

My helicopter is an engine helicopter.
The Y cable was used in 3.5.7 firmware.
The RPM is set to 6600, but it actually moves to 6400 ~ 6800.
Can i solve the problem that you mentioned?