I'm having the same problem. Did this get resolved?

Sent from my SM-G935P using Tapatalk

Hi,

we think that the problem is a fauly current sensor from the ESC. I couldnt test it yet because I haven't got a new Hobbywing so far.
I will post an update when i get it.

This morning I tried 1) a different Telem UNI cable, 2) plugging the Telem UNI cable into the other sat port on the Spirit, 3) going direct from the Telem UNI cable into the ESC (instead of just the white wire into the fan plug), and 4) dropping the ESC firmware back to FL-04.0.05. Nothing worked. All the telemetry sensors were discovered, but RB1A, RB1C and RB2C just sit at 0. Here’s my setup:

ESC: HW 160A V4
Hardware: HW160_V1.00456NB
Firmware: PL-04.0.06

Spirit Pro
Telem UNI cable
FrSky Horus X12S Tx
OpenTx 2.2

Hopefully this can get sorted soon. I took all my FrSky sensors and wiring off the heli. Thanks!

So current is at zero all the time? Even during hard maneuvers?
So you nearly tried everything except a new ESC, just like i did. Therefore i think that actually nobody can fix this problem, Tomas really tried everything possible to solve my problem.

I think that the current sensor in my ESC is faulty and delivers wrong values - low current is way to low, so capacity is way to low, too.
And maybe your current sensor doesn't work at all because it's at zero the whole time...


Did you try to readout the ESC with the progbox after a flight? You have to plug in the progbox directly after a flight and it can display the maximum current.

No, I did not fly it. Just running it on the floor with all blades off. I realize the current draw is low like this, but my FrSky current sensor would be steadily reporting current draw when run without blades. I suspect if I flew it I would see some small current draw like you did.

I also sent a note to HW. Figured if they hear enough reports they might be motivated to look into it faster. HW is a popular ESC and some other FBL's now pull telemetry, so I wonder if the problem is unique to the HW.

My 80a V4 doesn't see any current in a hover, but my 130a V4 does. Although that being said the 130 was still off by 20% after hovering for a minute.

Sent from my SM-G955U using Tapatalk

HW and CC ESCs require a load until they will report any value. But in hovering there should be definitively something.
The biggest problem is, that it looks like to be a different between ESCs or whatever difference is (maybe motor could affect this), it is causing a big difference (with HW).

_________________
Spirit System developer

Okay, I'll hover it and see what happens. Unfortunately, going on travel for more than week so it will be a while before I can do this. As I said earlier, I reported this to HW tech support, and waiting for their response. I'll share what I learn when they get back to me.

Hovered today and verified that I am getting current consumed readings with blades on. Interesting that absolutely zero current consumed with blades off...I would have expected something. My next question is how to calibrate the reading, but I'll start a new post for that one.

In the telemetry screen there is a setting to adjust the scale of the current sensor. My 130a in my 570 is within 5% after a minute long hover.

Sent from my SM-G955U using Tapatalk