← VBar Control Touch / EVO

Electricity and consumption Hobbywing translated

VBar Control › VBar Control Touch / EVO · Started by Ronny1975 on 21 June 2026 10:1221.06.2026 10:12
Ronny1975 21 June 2026 10:1221.06.2026 10:12
Hello dear VBar team,

First of all, I would like to express my sincere appreciation for your system.
It is currently the best and easiest-to-use system on the market.

However – and please don't misunderstand – this might also blind you somewhat.

I've read several posts about problems with controller telemetry, where users, i.e., your customers, report that values from various controllers are being transmitted incorrectly. Examples: current too high, consumption incorrect, etc.

Your response is always: "We only report it."

You can do it that way, but perhaps you shouldn't. As a customer, I don't want to have to deal with a Chinese manufacturer because their power rating isn't right. I bought an FBL system in Germany, and it shouldn't be a big problem for its developer to adapt it for their customers.

Please just include a factor that I can apply to the telemetry values. Or give the customer a calculation function to do it themselves.

This won't be a problem for you if you apply it to the displayed values. I come from a software development background myself. If desired, all of this can run solely on the GUI.

This is a small issue that makes many people happy and doesn't require much effort. I simply don't want to live with my VBar system showing a 3,068 mAh discharge at -20% – with a 3,600 mAh battery – when I'm only recharging 2,590 mAh.

I've observed this over several flights. I know it's a problem with Hobbywing's telemetry. But Hobbywing doesn't seem to care about customer wishes. I hope things are different with you.

The image shows the factor setting in Rotorflight.

Best regards
Ronny

machine-translated from German · Show original
RV 21 June 2026 14:4321.06.2026 14:43
So... generally speaking, we will not try to "correct" the telemetry data that others deliver incorrectly.

Quote: Your answer is always: "We only report."
Yep. That's it, it'll stay that way.

HW simply has to address this. HW is perfectly capable of doing it, with one exception where one of their controllers lacks a proper measuring device (cheap, cheap) – in that case, it will probably never amount to anything – but... they've now managed it with the Stratos controller, for example... they just need enough external pressure from customers.

If they don't want to do it, there are other controller manufacturers who do it better (YGE, Scorpion, for example) and may offer a correction (Scorpion) directly within the controller (accessible through us). Having it integrated into the controller would be the right approach; then none of the "evaluation centers"—like us—would have to constantly adjust settings depending on the controller, manufacturer, etc.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
Ronny1975 21 June 2026 15:0021.06.2026 15:00
Hello Rainer,

First of all, thank you for your reply.

I can't understand it at all. All FBL manufacturers have this feature: Rotorflight, Spirit, etc. It's not about making a special deal for every ESC manufacturer, but about customer satisfaction for their own customers.

Being forced to buy YGE is not a satisfactory solution for me as a customer of a €1,350 FBL system. Open source does it better and for free, and as I said: these are just display values.

I understand the frustration of always having to clean up other people's messes. As I said, I work in software development myself. But customer satisfaction is more important to me, so I also fix mistakes made by well-known companies like Siemens and Meteor Ink in my software if it helps the customer and makes them happy.

Please think about what I've said.

Everyone loses in this situation!

Best regards
Ronny

Oh, and one more thing I forgot to mention. I'd like to buy a current sensor from you. Unfortunately, you don't have one; that would allow me to bypass the hardware problem.



Edited once. Last edited on 21.06.2026 at 15:03 by Ronny1975.
machine-translated from German · Show original
RV 21 June 2026 16:3621.06.2026 16:36
Ronny, a current sensor is no longer needed because the controllers now handle telemetry. Only a few rare examples were sold towards the end. As far as I know, that era is simply over.

Therefore, I can understand your frustration, but it should be directed at the hardware. That's where the problem lies – and that's where it needs to be fixed.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
Ronny1975 21 June 2026 19:4121.06.2026 19:41
Hello Rainer,

Believe me, I have no resentment towards you.
I see this as a normal discussion about a technical problem.
As you said, in my opinion, the problem with HW stems from the switch to the new generation of controllers. There aren't as many variants anymore, and sometimes the controllers aren't operating within the optimal range of the shunts. This results in a loss of accuracy.
I am familiar with the problem and I can understand it.
The problem is that neither side can or wants to do anything.

Here's how I see it: you advertise that you support hardware. And you do, no question. But if I have no way to optimize this value with the VBar, then it's not so good.
If HW now introduces the factor into their firmware, then you would also have to make it adjustable in your software so that I can change it via the transmitter.
Same work for you.

Like I said, I can understand you, I get just as frustrated sometimes.

Okay, now I'll leave you alone about it and continue to annoy HW.
If you ever need help with software or hardware, I am happy to assist you and would be delighted to support the product.

Best regards
Ronny
machine-translated from German · Show original
RV 21 June 2026 21:2821.06.2026 21:28
Hi Ronny,

Let's try this:

Please give me the serial number of the VBC, the target/actual data of a flight, as well as the exact controller type and firmware version.

I can gladly forward that, maybe something can be done about the cause ;-)

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
Ronny1975 22 June 2026 06:3322.06.2026 06:33
Hello Rainer,

Thank you for the offer, serial number 11007711.
The controller is a Hobbywing v5 HV 180A with the latest firmware version 5.1.1.

During the flight on 20.06.2026 at 17:19:31 (test flight), the battery was clearly down to almost -20%, display VBC 3062mAh, and I recharged 2485 mAh.

20.06.2026 16:29:53 Display VBC 2789 mAh => Recharged 2140 mAh

The flights can only be found via batteries in the cloud. They are included in the 3600mAh XGen batteries.

Thank you in advance for your work.

Best regards
Ronny
machine-translated from German · Show original
Eddi E. aus G. 22 June 2026 10:3422.06.2026 10:34
Hi Ronny,

One problem that is often ignored is also a technical one:

The way some controller manufacturers measure – not via a calibrated shunt, but via an auxiliary construction, let's say how much a peripheral component heats up, if that were the case – measurement errors are inherent to the system.
This means that for a certain flying style that is consistently followed, a factor can be applied on the controller side (or on the transmitter side).
In your case, that would be a range of 1.23-1.30, which – if you wanted to push the battery to its limits – would be a critical difference of 7% in my opinion, which can quickly amount to half a minute.

When flying a mix of country and western styles, the range becomes even greater depending on the weighting, increasing the risk of deep discharging the battery accordingly, or one must leave a really substantial reserve, at least as much as could have been used at most + x ...

In addition, these types of measurement are also slower and, if we stick with the example of temperature, also dependent on environmental conditions; even if you measure a delta, it behaves non-linearly over certain periods of time, differently at low temperatures than at high temperatures, during the first flight and the next back-to-back flight.

So, in the controller or transmitter, you would actually need a matrix or a formula and other information to straighten this out.

To ensure customer satisfaction, some – many – controller manufacturers have also considered backward compatibility, offering telemetry via software update even for older controllers (without suitable measurement technology) that are not expected to allow precise measurements. They then use workarounds, or, especially with new developments, simply pay attention to feedback from their (3D) pilots and adjust the 'measurement' accordingly – by a single factor.
Which then again is not suitable for beginners, hobby pilots, average pilots, or scale pilots.
This means that some, many transmitter manufacturers allow factors to be adjusted to correct factors, in order to improve customer satisfaction.

However, the result is not wide-ranging; it only works relatively reliably for a relatively narrow power range.

In the end, I'm afraid the whole thing is much more complex :-/

If you or we confront HW with this, for example, there will again be a variety of things that can happen, or not.

Only with existing controllers (the older the system, the more affected it is) will things probably never really improve; they can only work with what they have, and even there, development is generally moving forward. With new developments, one could of course rely on more accurate measurements as a basis, but that again raises the question of cost.

Cat, tail... and we're basically stuck in the middle, the asshole who's supposed to fix it :-) (or explain the world...).

This is all meant to be taken with a grain of salt ;-) but that pretty much explains why we're only filing charges and not trying to save the whole world :-)
If 'one' (we, and also the customers, who also pay ^^) exerts pressure, simply saying, hey, that's not right, can't that be done, or can't you do better?, then (hopefully) things will improve overall in everyone's interest.

I see the world very positively, because I am an optimist (F4).
Even though I'm occasionally proven wrong ^^

—Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
RV 22 June 2026 17:1122.06.2026 17:11
Hi Ronny,

Before I send this email, could you please do another flight and then check the percentage displayed using a LiPo battery checker (ideally two different ones, as they're not that accurate)? It's possible the problem lies with the charger. Or have you perhaps already tried different chargers with the same result?

Please also include information about which charger is used, the initial charging voltage, and the final charging voltage, both with a checker and with a display on the charger.

I'd like to formulate that in a "watertight" way ;-)

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
Ronny1975 22 June 2026 18:4022.06.2026 18:40
Hi Eddi,

Thanks for your answer.

I initially wanted to quote you, but I can't find a single point in your text where I disagree with you. This, of course, makes it difficult for me to argue against it, especially since I was also aware of the hardware issue.

What bothers me as a customer, however, is that HW apparently doesn't want to, can't, or for whatever reason isn't addressing the problem. Unfortunately, I have hardly any options to change this – except by switching manufacturers, but I don't know if that would actually improve things.

I am, partly due to my profession, a fan of precise measurements and would therefore have preferred to avoid the problem by using an external sensor.

Right now I'm completely unsure what to do. Would a different speed controller manufacturer be a good idea? Do you have any good experiences with any of them?

Thank you and best regards
Ronny
machine-translated from German · Show original
Ronny1975 22 June 2026 19:0122.06.2026 19:01
Hello Rainer,

Thank you very much for your reply as well.

The charger is an ISDT K4.
I took screenshots on June 20, 2026 at 5:19:31 PM. Unfortunately, I didn't think of it right away when charging started, but the battery was at about 31% at that point.

I don't currently have a second charger, but I can coordinate with a fellow club member and run some tests this weekend. However, I don't think the charger is the problem. The ISDT charging values work very well with my Goosky RS6, which was previously flown with a different FBL charger. The VBar Evo for the RS6 is already here, and my KSE will be getting one too :-) .

The voltages measured by the LiPo tester deviate from the values of the charger and the voltage displayed by the VBC by only a few millivolts. After charging was complete, the tester showed approximately 4.194V per cell.

I hope that's enough. Otherwise, I'll do more tests over the weekend.

Thank you and best regards
Ronny



Edited once. Last edited on 22.06.2026 at 19:03 by Ronny1975.

machine-translated from German · Show original
RV 22 June 2026 21:4722.06.2026 21:47
Okay - that's enough, I think. I just wanted to be sure there wasn't another cause.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
flydown 25 June 2026 21:4625.06.2026 21:46
Hello,
I'm just a small fry, but I'm blowing the same horn as Ronny.
I also have a Hobbywing Platinum 150A V5.1, where the discharged value doesn't have much in common with the recharged value. I wrote to Hobbywing at the time:

Hello,
I recently purchased a Hobbywing Platinum 150A V5.1.
However, I have to set the discharged capacity of my flight battery to 2500mAh to actually get 3000mAh.
I find this discrepancy very large. Is there a way to adjust this?

Thanks and regards,
Uwe Bendschneider

Answer: (If this is not allowed to be published, please delete it)

Hi sir

This is Hobbywing support team!

The issue is not actually an issue setting with ESC. You need to make corresponding adjustments based on the discharge efficiency of the battery. Each type of battery has its own discharge efficiency. The capacity marked on each battery is actually the charging capacity, not the discharging capacity. The discharge capacity of the battery is only about 80% -90%. Based on your test data, the discharge efficiency of your battery should be around 80%.

Best regards,

XXX

2026-04-02

I did end up replacing the controller with a YGE one. With YGE or Unisens controllers, I never experienced any significant discrepancies in the discharged and recharged capacities.
Therefore, I would agree with Ronny's request for a way to specify a correction value.

Best regards
Uwe
machine-translated from German · Show original
RV 26 June 2026 00:1226.06.2026 00:12
Regarding the correction value:

As I said, we have this built into the Scorpion controller. This has the advantage that it works for all users of the controller, regardless of the remote control. This is the only way it works if the controller itself is already such a "precision gauge".

If this is done at the VBar Control level, a file containing this special value must be created in the VBC for each model. Furthermore, we must ensure that this value is not used in all ESC telemetry (even those not affected), even if the aforementioned file is present (e.g., after an ESC change). The Bind&Fly function would then again be affected by inaccurate telemetry when changing transmitters until it's re-enabled. This entire process must then be tested with other ESCs to ensure it continues to function as before – and this must be done after every change.

This is too much fuss for just one affected controller type from a single manufacturer, especially since, as already mentioned, this is the wrong end of the line for us.

I remember from the early days of telemetry when I used to test-fly ESCs from all manufacturers in various sizes using a UI sensor (our UI sensor is calibrated and temperature-compensated) to compare them – some developers were already sweating bullets because the capacitances weren't accurate enough. You could clearly see from the readings which ESC manufacturer had put in some effort and incorporated a calibrated shunt, which used a copper track as the shunt, which could calculate the currents from the internal data, and which still only provided rough estimates.

YGE is definitely the benchmark here; they do a fantastic job. You can tell that the developer actually flies and tests the software himself and knows exactly what's important.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
flydown 26 June 2026 08:4726.06.2026 08:47
Well, perhaps you could approach HW about this issue, if it concerns the ESC firmware. Or whoever writes the apps.
You definitely have more leverage here.

Greetings, Uwe
machine-translated from German · Show original
Eddi E. aus G. 26 June 2026 09:2426.06.2026 09:24
Hi,

We've done that before, and repeatedly, because (as Rainer's example shows) we always take parallel measurements during the app adaptation phase to see what the results are. We do this, but not for all controllers from a manufacturer, nor for every new firmware they release. Instead, we use one or two controllers as examples, which the manufacturer kindly provides for testing (also with update capability, so that we can always cross-check their adjustments during this phase).

From the controller manufacturer's perspective, it would then be ideal – as Rainer correctly points out – for it to output correct data, regardless of the telemetry system. It's just one value, or rather three: U(V), I(A), Q(mAh).

And it would be in our and your interest if the values were correct without having to fiddle around, or having to start all over again when changing transmitters/bind and fly/controllers to a different model/varying flying styles and thus varying performance and measurement accuracy, which poses a risk, and possibly even requires running a timer in parallel...

HW's statement is vague... within a wide range (battery charge level), the usable/discharged capacity is very easy to measure; there's no room for interpretation regarding voltage and current. Towards the end, the voltage naturally plays a role in determining how far I can go without damaging the battery. This voltage also depends on the temperature, but also on the cell balance within the battery (when the voltages start to diverge, which can lead to damage to individual cells). But you leave a 20-30% reserve at the time of the warning anyway, and the charger almost automatically monitors how much it's recharging, adjusting as needed. The battery management system also takes time and cycles into account, which is quite accurate as long as you're only using one transmitter (data stored there) or can exchange data between transmitters using Battery ID V2.

If HW is probably correctly assuming (because that's just how it is... ;-) ), that the usable capacity (discharge capacity) – before one can expect premature wear or damage to the battery – is indeed 80%, then that confirms exactly what was described above ^^ nothing new.

What doesn't fit, however, is that the removed and charged capacity differ so drastically (unless the battery is worn out, and a lot of energy is wasted at the balancer until all cells reach charging voltage).
The counter-evidence can be nicely demonstrated with the current sensor; my experience from that time shows a deviation of +/- 50 mAh with a normal, good 5,000 mAh battery.
Reference class... ;-)

—Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
Ronny1975 26 June 2026 13:0526.06.2026 13:05
Hi everyone,

What I, as a customer, find unfortunate is that I cannot change it.
I now have 3 hardware units that are probably all inaccurate.
The U/I sensor is no longer available. The controllers are quite expensive.

Best regards
Ronny
machine-translated from German · Show original
Eddi E. aus G. 26 June 2026 14:0626.06.2026 14:06
Hi Ronny,

understandable.

If the deviation were always roughly the same, one could juggle (cheat) the remaining capacity or percentages so that the 'fly by capacity' feature could be used safely, landing earlier (or having to) and conserving battery power rather than landing too late or unintentionally, ... even if the recorded data in the logs is then inaccurate.

If the deviation varied depending on flying style, temperature, and moon phases, one would have to find the safest compromise (and thus the shortest flight time...) – a single factor would only help to the same extent, because it is only (1) factor.

Or you could draw a table:
Hovering and circular flight, 1.07
Mixed 1.03
3D 1.0
...but then in winter
...different

It has to be on the preflight checklist :-) and you shouldn't deviate too much from the flight plan :-)

Because all transmitter manufacturers seem to be doing their own thing, thinking in a relatively narrow and short-term way, having the model memory built into the transmitter anyway, and simply correcting the inaccuracies of devices like controllers with a factor of (1), regardless of whether that's generally smart or not, there's no pressure on the respective manufacturer. At best, they don't even notice all the tinkering going on, or they think, "After me, the deluge, they'll figure it out somehow."

In many ways, we are perhaps the small Gallic village putting up fierce (humorous...) resistance ^^ It would be smarter if (even back then) the whole populace had said... isn't there another, better way?
:-)

I still think about JLog from time to time... someone was able to really let loose and certainly did a great job for the community (with all the same drawbacks and issues...), because a manufacturer didn't see the need for it for a very long time (after all, there's something from Ratiopharm :-).

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
RV 26 June 2026 17:1326.06.2026 17:13
I contacted HW and haven't received a reply yet.

Furthermore, I have two pilots in my test team who are currently verifying this for me, but it will take a few days.

If HW's "wishy-washy" statement is factual, they probably haven't installed a proper measuring shunt (or aren't evaluating it correctly) and have instead used a "half-baked" calculation model which, depending on the voltage situation, calculates more correctly than incorrectly.

Summing up the currents over the flight duration to determine the capacity requires a certain degree of accuracy and precision in the input data (current and time). If this cannot be achieved, even a few percent deviation in the current "estimate" over time will significantly impact the capacity calculation.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.




1 mal bearbeitet. Zuletzt am 26.06.2026 17:14 von RV.
machine-translated from German · Show original
RV 26 June 2026 22:1626.06.2026 22:16
Update:

I asked Sven (who's reading along here) to verify this. This is what it looks like for him:

Platinum 150A V5.1
Firmware PL 04.1.01

The controller says 2840 mAh.
Charger says 3290mAh

Actually, quite the opposite - and not good for the battery either.
I also sent this to HW. Let's see.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
Ronny1975 26 June 2026 22:2226.06.2026 22:22
Hi Rainer,

Thanks again for taking care of this.
No, what's happening to Sven is even worse.
I'd rather have more battery power than that.

Best wishes and have a wonderful weekend everyone!
Ronny
machine-translated from German · Show original
flydown 26 June 2026 22:4926.06.2026 22:49
Hello,
And thank you from me as well.
Yes, that's how it is for me too, set to 2500mAh
To recharge 3000mAh. That means if I set a 4000mAh battery to 3000mAh, I only get 3500mAh out.

Greetings, Uwe
machine-translated from German · Show original
RV 27 June 2026 10:5127.06.2026 10:51
So - Bob from HW got in touch and is forwarding it to his technician. The guys just got back from the Helifest.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.




1 mal bearbeitet. Zuletzt am 27.06.2026 10:51 von RV.
machine-translated from German · Show original
Eddi E. aus G. 29 June 2026 09:1329.06.2026 09:13
@Uwe,

You have to constantly keep an eye on it and verify it if you have such deviations (especially deviations from the deviations).
What the charger says – with a healthy battery – is usually still the best reference.
LiPo checkers, for example, 'are also quite nice', but they only provide an estimate based on the cell voltages at a specific time x.
What I mean is, I wouldn't adjust the percentage in battery management based on the percentages there.

Let's see what HW does now :-) in the end it's in their own best interest, in competition with the other manufacturers.

—Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
RV 30 June 2026 16:0430.06.2026 16:04
Current status:

HW is taking this seriously and is addressing it. However, I would like to provide more reliable and verifiable data. To that end, I have initiated appropriate tests (thanks to Sven and Stephan) to ensure the most conclusive results possible.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless