Ardupilot V4.5.x - ESC telemetry on the OSD has "stopped working" about ardupilot HOT 3 OPEN

This is a pre-existing bug. The OSD ESC information would only show info about the "first" ESC, including ESCs that did not exist. So unless you physically had your drone setup in a particular way you would not get ESC information. The change in 4.5 is that the "first" ESC is now SERVO1 rather than AUX1 due to the support for ESC telemetry on IOMCU. The solution is to either allow the ESC to be configured to to automatically determine a reasonable ESC.

from ardupilot.

Absolutely agree, just be able to configure in the OSD which ESC to show as ESCTEMP, ESCRPM and ESCAMPS (I never understood why ESCVOLTS is absent, telemetry voltage is in virtually all ESCs with telemetry).
Now you cannot so taking SERVO1 as reference if you have ESCs connected in other outputs the telemetry will not work.
More than a bug it is an implementation I think necessary.
Then if it were possible to have multiple ESCs active in the OSD it would be the top, but other software such as INAV also does not have this feature, they only show the first one.

from ardupilot.

And today by doing a test I noticed that the telemetry problem also goes to create problems if for example you set the ESC to SERVO1, declaring it in the bitmask of BLHeli goes to disable the pwm of SERVO2.
So yes, it is a bug because it still doesn't do what it should.
Tested on SpeedeBee F405 WING.

from ardupilot.