← VBar NEO/EVO VLink

Re: Hobbywing 180a v5 with Vstabi EVO V8 hard shutdown? translated

VBar › VBar NEO/EVO VLink · Started by Danny on 1 June 2026 18:3601.06.2026 18:36
Danny 1 June 2026 18:3601.06.2026 18:36
Hello everyone,

What can I say? I bought a new helicopter and transferred the components from this one to it. First flight, flew for about 1:30 minutes, then a rough warm start, and the helicopter was wrecked. Just like the helicopter from this thread.

I don't get it, after updating the controller everything worked without problems for 35 flights, now I have the problem again.

This time the engine didn't stall; the helicopter simply tipped over uncontrollably to the right.

What I can remember now is that, like last time, I landed a few times to turn down the sensitivity on the TS.

Since the buffer is switched on and off via the motor switch and is fully charged, there is always a current source that feeds into the BEC when the motor is switched on again.

Could this disrupt the ESC's stabilization or BEC?

Thank you.

BG Danny
machine-translated from German · Show original
RV 1 June 2026 20:1601.06.2026 20:16
New helicopter, new problem, new headline. How should I change it?

What are the serial numbers of the Stabilizer and VBC so I can check them in the cloud?

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
Danny 1 June 2026 21:1701.06.2026 21:17
Hi Reiner,

First of all, thank you very much for always replying so quickly.

I would say new helicopter, same problem, or rather, same components, including the stabilizer.
Same number, therefore.

But here again are the SR numbers.

EVO 0027006743 31.05.2026
VBAR-Control Evo+ 11007239

https://www.vstabi.info/forum/read.php?42,152865

I would say it's like with the BK servos, backflow when switching on the buffer.
When fully charged, it switches on 2-6 seconds later, after switching on via macrocell as described above, after switching off the motor buffer off, motor on again, take off, buffer on again after 2-6 seconds.

See old lock, exactly at approximately warm start.

This is my logic here.

Now it's your turn :-)

600€ are now wasted, but I still want to find the solution and solve it for the next one so they don't have this problem.

Yes, the lock is no longer showing BEC current, therefore a warm start and reset are performed by powering on.

However, I don't believe it's a BEC failure, since there is one master BEC, one slave BEC and a full buffer connected to the EVO and the lock is not indicating any BEC undervoltage.

I suspect it's backflow from the buffer when switching on, like with the BK servos.

BG
Danny



Edited 3 times. Last edited on 01.06.2026 at 21:32 by RV.
machine-translated from German · Show original
RV 1 June 2026 22:4801.06.2026 22:48
So:

- 1 Master BEC, 1 Slave BEC
Nope. Those are just two cables from the same BEC.

- Buffer
Which buffer? It's not a Mikado buffer, otherwise it would be in the log. Where exactly is it connected? What is your circuit configuration for it?

We just analyzed your radio logs. There's interference or crackling every few seconds. Either loose connectors, static electricity, or something like that.

Please run a test using only the stabilizer with an RC battery and "simulate" a flight (motor on, move away, rotate transmitter). 1-2 minutes is enough. Then let me know about the log.

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
Danny 4 June 2026 18:2104.06.2026 18:21
Unfortunately, it took a bit longer than expected; I also had to repair the controller, which had fallen directly onto the capacitors. Thankfully, the Hobbywing isn't potted.

So, here are the questions.

Throttle output regulator on ESC with +-

RPM controller signal with +- in RPM

Buffer is a ZTW and on AUX 3 (same combination as the other helicopters I have)

Please take a look at the logs from 04.06.2026 10:23/10:29/10:35.

10:23 First power-on after repair, setting tail servo endpoints in the setup menu (No start-up) Warm start.

10:29 Engine on/off, moved all the servos like crazy. Nothing.

10:35 same thing again, servos were stirred across all axes with motor, without motor, with buffer, without buffer, the servos even had a temperature of 37° :-) .

And again, no Wamstart in the log.

Nothing was changed in the wiring during any of the tests.

All connectors on the EVO were fixed with hot glue.

If peaks are still present in all logs, I will use an external 2S battery as a power source and then write the results.

Thank you.
BG Danny



Edited twice. Last edited on June 4, 2026 at 6:28 PM by Danny.

machine-translated from German · Show original
RV 4 June 2026 22:5004.06.2026 22:50
So... general information about buffers and capacitors:

If a Mikado VBackup were installed, we could have more information about whether and when it had to intervene.

Generally, these devices only offer limited help against short back currents in the air (servos without diodes and/or capacitors); the buffers have a different purpose (emergency landing capability) and use different capacitors than would be needed for that.

A simple, additional capacitor in parallel with the outputs would be better here (doesn't one always come with hardware ESCs, as far as I know?). For example, a 16V or 25V 4700uF capacitor connected in parallel to the + and - terminals of a free space on the ESC.


Regarding the logs:

I'm still experiencing inexplicable interference in the radio log.
The same applies to Steam, the RS7, and the RS7U, by the way. The Logo 200 is clean.
The Steam, RS7, and RS4 were clean both before and during 09/25!

What changes were made to the helicopters after 09/25?
Please hover for a moment:
- once without the buffer
- once without the TELE plug of the controller

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 04.06.2026 22:51 von RV.
machine-translated from German · Show original
cc1975 5 June 2026 07:1905.06.2026 07:19
Why are both the +/- and signal inputs going into RPM for you? Normally, only the signal input goes in, and +/- is essentially a slave?
Regards, Christian
machine-translated from German · Show original
RV 5 June 2026 07:3205.06.2026 07:32
That's one way to do it. RPM can also have a voltage input. I do it that way too; the connector for RPM holds better then because three pins are engaged.

The "separate" version dates back to the days of the old stabilizers (standard, mini) where RPM couldn't handle any input voltage...

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
Danny 6 June 2026 08:5306.06.2026 08:53
Good morning Reiner,

Nothing would be changed on the helicopters after 09/25.

I would say it's an update to V8, but that can't be the case, since the logs show that V8.1 was already installed. This applies to all helicopters since the recording started in Control.

What I do remember, though, is that the Steam was the first to receive the V8 update. And on July 25th, after the maiden flight and crash, it got the buffer update.

After that, all helicopters except the RS 4 and Logo 200 received a buffer.

After your statement that all my helicopters except the Logo 200 have inexplicable radio interference, I don't want to fly them anymore until the matter is resolved.

The Logo 200 has the EVO chip you replaced installed, see here in the forum (the Evo simply switches off during operation), it already has the V8.2 version installed.

The other helicopters are equipped with the EVO engines purchased on June 25th.

I have ordered the aforementioned ELKOS 25V 4700UF capacitors, will connect them to AUX 3 and perform the mentioned tests (- once without the buffer).
- Perform this test once on the workbench (without the TELE connector of the controller). Then report back here so we can check if there is any improvement.

BG Danny



Edited once. Last edited on June 6, 2026 at 11:48 AM by Danny.
machine-translated from German · Show original
Danny 6 June 2026 17:2606.06.2026 17:26
Hello,

I found the ELKO from HW and ran the tests with Steam.

Logs from June 6, 2026:

15:55 Without buffer.

15:57 Without buffer and telemetry.

15:59 with ELKO on AUX 1.

16:01 with ELKO on AUX 1 and telemetry.

16:04 with ELKO on AUX 1 and telemetry and buffer.

Distance to the helicopter was increased and decreased in all tests using the control.

BG Danny

machine-translated from German · Show original
RV 6 June 2026 20:2806.06.2026 20:28
Quote: 15:55 Without buffer. Not OK

15:57 Without buffer and telemetry. io

15:59 with ELKO on AUX 1. io

16:01 with electrolytic capacitor connected to AUX 1 and telemetry. Not OK

16:04 with electrolytic capacitor connected to AUX 1, telemetry, and buffer. Not OK.



The hardware controllers (the telemetry) represent the common problem with helicopters.

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 06.06.2026 20:29 von RV.
machine-translated from German · Show original
Danny 7 June 2026 11:2107.06.2026 11:21
Hello dear Reiner,

Thank you very much for checking.

If I understand the situation correctly, the telemetry output of the Hobbywing ESC (Electronic Speed Controller) causes a pulse that can lead to a malfunction or a reset of the receiver module in the VBar EVO.

As a result, communication between the Control and the EVO is interrupted. The connection is then automatically re-established through a warm restart. This error doesn't necessarily occur, but can be triggered under certain circumstances. Since this combination is used by many users, it could currently be an isolated incident—as in my case—that might also affect other users.

The following controls are affected in my case:

Hobbywing Platinum 80A V5
2 x Hobbywing Platinum 180A V5
Hobbywing Platinum 200A V4

All controllers have the latest firmware installed.

Against this background, I have the following questions:

Is this problem already known to Mikado?

Does Mikado plan to investigate the described issues further and, if necessary, provide a solution?

Has there already been an exchange between Mikado and Hobbywing regarding this, especially since the telemetry functionality was implemented jointly?

Thank you in advance for your feedback.

Best regards

Danny



Edited 3 times. Last edited on 07/06/2026 at 11:26 by Danny.
machine-translated from German · Show original
RV 7 June 2026 15:0207.06.2026 15:02
Quote: If I understand the situation correctly, the telemetry output of the Hobbywing ESC (Electronic Speed Controller) causes a pulse that can lead to a malfunction or a reset of the receiver module in the VBar EVO.

Nope – that hasn't been proven. I suspected it at the time, but the evaluation of several models from different controllers and pilots this morning shows that it can't have anything to do with the crash.

The initial reset that caused the crash was almost certainly due to discharges. And you've fixed that, haven't you?

I only noticed unclear logging values from the internal radio telemetry when your helicopters with HW ESCs had the telemetry connected. In this case, the values repeatedly jump to 0 instead of remaining at a meaningful number.

Since the feedback consists of developmental telemetry values – which, in their observed form, are not directly related to any malfunctions – I think this is irrelevant to your original situation. Otherwise, you would hardly have been airborne for 15 seconds.

For comparison, I also checked cloud data from well-known pilots using HW ESCs – and to give it some significance – also with other ESCs. I found that two former club members with a different ESC brand, which works flawlessly for me, produced similar logs.

Incidentally, the same telemetry protocol also transmits the "normal" controller values, which were always received without gaps. Therefore, it can't be a general issue.


Conclusion:

I thought there might be a connection, and thanks to you I was able to investigate it.

The causal relationship cannot be established. I've led us both astray here ;-(

But - of course, we need to investigate further internally to find the cause so that the logs provide us with the necessary information for support purposes and so that the customer - as in this case - is not unnecessarily confused when we refer to these values.



One last question remains: Which operating mode and software version are installed in your radio module? - It's in the system settings, under the radio icon...

And... are the controller telemetry signals connected to TELE1 or TELE2 (antenna or servo connector side)?

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.




3 mal bearbeitet. Zuletzt am 07.06.2026 15:12 von RV.
machine-translated from German · Show original
Danny 7 June 2026 17:0507.06.2026 17:05
Here is the additional information requested.

I hope these are the correct ones? See attached images for operating mode and software version; I can't find anything else on the Control Evo (system settings, function icon...).

The telemetry is connected to TELE2/servo connector side. I just checked the other helicopters and it's connected to TELE1/antenna side.

One more piece of information regarding the EVO you replaced: the telemetry was also connected to the TELE2/servo connector side.

BG
Danny

machine-translated from German · Show original
RV 7 June 2026 17:4907.06.2026 17:49
Hi Danny,

I meant this - if the small green icon is on the right side of the heading:

Regards (EN) / Greetings (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.

Please use a PC and a proper keyboard for posts and replies, and answer all questions completely. Take your time and answer follow-up questions thoroughly and completely.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
For individual communication, please use email exclusively ! - Private messages, messenger, chat, etc. will not be processed.
For single user communication please send an email only ! PM, Messenger, Chat etc. won't be read.


machine-translated from German · Show original
Danny 7 June 2026 18:0807.06.2026 18:08
Hello Reiner,
Nope – it's not available on my system.

We need all your Control EVO + ² to delve deeper ;-) .

Is there any other way I can give you this information?

BG Danny

PS:
Let's get down to brass tacks, it's Sunday and 6:10 PM. Thank you so much for the support, thumbs up and hands up! :-)



Edited 4 times. Last edited on 07/06/2026 at 18:13 by Danny.
machine-translated from German · Show original
RV 7 June 2026 18:4107.06.2026 18:41
Hi Danny,

Okay - then you have the standard radio module installed, which is also compliant in the EU and cannot be changed.

That information is sufficient for now; I'll need to test it with the appropriate hardware. Thanks!

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
Danny 17 June 2026 12:1517.06.2026 12:15
Hi Rainer,

Is there any news to report?

I went flying the helicopter again on June 14th, made 3 starts, everything was uneventful.
Perhaps you could take a look at the logs.

BG
Danny
machine-translated from German · Show original
RV 17 June 2026 19:5217.06.2026 19:52
After it turned out that the radio glitches I was chasing were probably only related to telemetry - nothing new there.

We will investigate this further to possibly understand it, but the systems that Uli or I have access to show no abnormalities.

Therefore, your flying is safe for now; the first effect was certainly a discharge, and after that I went astray based on the logs.

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