Hyperion sensor failures ?

[TBur]

I'm about to put my third sensor in (over a 6 month period), things go great for a few months then after a while the govenor won't "catch". repowering up the heli usually fixes it, eventually though the govenor does not work at all I replaced the first one after 2 -3 months, didn't note any bad connections to the motor wire or SK.

(note when the govenor doesn't "catch" - the heli spins up at 30% throttle or whatever percent the flight mode has setup for the throttle)

The Hyperion sensor is mounted towards the rear of the heli, at least 3 -4 inches away from the motor and esc.

I'm running a 720 @ 6V (bec) with a HW70 esc, 12S setup. Hyperion sensor going direct to the 720.

any else seeing this ? other things I should check ?

(given the logging bug I always have logging off - so can't look at SK logs for help)

Tim

[newbheliusr]

Can't someone help here?


Sent from my iPhone using Tapatalk

[georgi UK]

=] Tim, the sensor isn't expendable, doesn't wear out? the wires to the board are vulnerable to vibes / tugging. I fold them back to create a loop with a heatshrink sleeve, then soft mount the sensor.

3.15 firmware with logging on will give you a small tail shake at worst, so run a playback log and lets see what the rpm's show?

[ModelGuard]

ive only ever experienced this when one of my lipos had a dead cell leaving 11s instead of 12s.

[TBur]

certainly seems plausible that a strained connection (or otherwise vibrated) becomes intermitent.

I'll pull the blades off, do some bench testing with logging on and see if I can cause it to lose the rpm reading.

the other change I want to make is to run it through the power bus - that will alleviate any strain on that side of the sensor wiring as my bus is very close to the sensor. (I've seen a diagram posted recently on how to do this)

I'll let you know if I find anything.

Tim