← Cafe

Vstabi Evo in the Stratos 200 from XL Power translated

Public Talk › Cafe · Started by Zille1987 on 3 May 2026 16:1903.05.2026 16:19
Zille1987 3 May 2026 16:1903.05.2026 16:19
Hello Team Mikado,

I pre-ordered the Stratos 200 from XL Power and also a Vstabi Evo in a neon yellow aluminum case.

Then it suddenly occurred to me that it's not a rear servo but a rear motor that's being controlled.

How is this "selected" or implemented in Vstabi Evo? Is there a setting for it, or do macrocells need to be written? I haven't encountered this situation before.

VG
Zille



Edited 1 time(s). Last edit at 05/03/2026 04:20PM by Zille1987.
machine-translated from German · Show original
thomas1130 3 May 2026 16:2103.05.2026 16:21
That's no problem - there's a "setting" for that...

LG
machine-translated from German · Show original
Zille1987 9 May 2026 14:1609.05.2026 14:16
Hello everyone,

Unfortunately, I have to bring this topic up again.

Yesterday I wanted to put the Stratos 200 into operation and first created a new model as "No Mikado Helicopter". Then I went through the entire setup (servos set to center pulse and 200 Hz, etc.) and then, at the "tail rotor" point, switched from servo to motor by holding down the button for a long time.

Unfortunately, the tail motor only beeps and twitches – so there's clearly some kind of fault. If I lower the DShot protocol from DShot600 to 300 or even further, the beeping slows down, but the motor still doesn't start. The main motor, on the other hand, works perfectly.

I then created a new test setup with "Logo Helicopter" -> "Logo 200" and adjusted the servo settings accordingly. While this eliminated the problem with the beeping and jerking of the tail motor, the helicopter initially flew terribly.

In the afternoon I went briefly into the field and made a total of five familiarization flights.

Initial situation with the settings of the Logo 200:

The main rotor experiences problems with strong pitching impulses, even while hovering. The tail section then oscillates up and down at a high frequency.
Tail rotor practically non-existent: strong oscillation while hovering, no clean locking into place. With positive pitch inputs, the tail rotates up to 120°, and with negative pitch inputs, it rotates in the opposite direction.
During cautiously tested tick-tock maneuvers, the helicopter rotates completely around its own axis under load shocks. Clean tail stops while hovering are practically impossible.

Result after five test flights:

By reducing the main rotor gain, I was able to eliminate the tail bouncing during pitching maneuvers.
The tail section itself is still not really under control. While I was able to improve it somewhat with pitch pre-compensation and torque compensation, 3D flying is currently out of the question.

To make sure I hadn't gotten a "Monday heli," I then quickly installed a Nexus-XR with a Radiomaster Pocket (ELRS) and set up Rotorflight with a few basic adjustments. This immediately made the tail stand rock-solid – completely unobtrusive and without any problems.

Therefore, I'm now fairly certain it's purely a settings issue. However, I do find it strange that the manual setup with "No Mikado Heli" was practically unusable.

Therefore, my question is:
What am I doing wrong here, or what am I perhaps overlooking? I would really like to fly the Stratos with the EVO instead of the Nexus.

Thank you in advance for any helpful tips and experiences!



Edited 1 time(s). Last edit at 05/09/2026 02:17PM by Zille1987.
machine-translated from German · Show original
RV 9 May 2026 14:5509.05.2026 14:55
You're probably not doing anything wrong; the problem lies deeper.

HW built a controller with firmware that has some quirks. We disclosed this as soon as we knew about it (and unfortunately, they don't ask us at the beginning...). It's almost always the same story: there's a collaboration, we get it too late for testing and feedback, and then this is how it turns out.

Doesn't XL have a preset "in stock" that works?

Therefore - please address to XL and HW.

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.




Edited 1 time(s). Last edit at 05/09/2026 03:24PM by RV.
machine-translated from German · Show original
Zille1987 9 May 2026 17:2909.05.2026 17:29
Hello Rainer,
thanks for the quick reply.

Even though Mikado doesn't seem to be directly "at fault" here, I, as an end customer, would like to describe my perspective:

I deliberately chose a Mikado FBL system, which in my configuration costs a total of €379 (Pro & Rescue upgrade, Yellow version). Other FBL systems cost only a fraction of that – in my case, the FBL system even exceeds the value of the rest of the helicopter.

Therefore, I honestly expect the system to function reliably. Unfortunately, that is currently not the case.

When I then receive feedback that I should contact XL Power or HobbyWing, I find that quite incomprehensible.

Therefore, my specific question is:
Are you actively working on this issue and will there be an update? If so, what is the approximate timeframe for this?
machine-translated from German · Show original
RV 9 May 2026 19:2509.05.2026 19:25
Well, we're in contact with Hobbywing. We're also working in parallel to see if we can achieve anything on our end. Alex and Uli are working hard on this, and Carl is helping out wherever he can.

I can't say more about it, I'm not directly involved.

If XL had shown up earlier with the part and given us some time... then it might all be over by now. But we only got involved after sales had already started; to be precise, that became clear on April 29th.

Incidentally... if you install an OMP controller from the Logo 200, everything is fine - tests were also carried out with this to make sure that the problem was with 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.




Edited 1 time(s). Last edit at 05/09/2026 07:34PM by RV.
machine-translated from German · Show original
Zille1987 10 May 2026 10:4810.05.2026 10:48
Hello Rainer,

First of all, thank you very much for responding to my request and being available over the weekend.

Last night I saw a video on Facebook from Carl-Henning Siebert showing that you're already actively working on the problem and apparently have a solution in sight. It seems only the final touches are needed before it's released to customers.

Here is the link to the video:
Facebook video by Carl-Henning Siebert

To be honest, this information would have defused my dissatisfaction much earlier, or even prevented it from escalating to such an extent in the first place. Transparent communication is simply enormously helpful in such situations and shows that the issue is being taken seriously.

Greetings from North Rhine-Westphalia!
Zille
machine-translated from German · Show original
Eddi E. aus G. 11 May 2026 09:1411.05.2026 09:14
Hi,

In our opinion, XL should actually be obligated to provide information and offer a solution.
Carl is also involved, fighting :-)

It would have been even better to come around the corner earlier, so that any potential inconsistencies could be uncovered and resolved before they reached the customer.
And when you (their team pilot and we in this case) give qualified feedback, you should accept and review it, not stonewall first.
All of this takes time.

Otherwise... everyone would be happy.

A workaround is in the works, but it would be better if the cause could be eliminated in parallel, which would mean an update of the controllers that have already been produced and delivered.
It would be even better if this could have been noticed before production, so

Now that workarounds are on the horizon, I almost don't believe it anymore, as it suggests that the problem lay elsewhere, which has been proven in both image and sound to be simply not true.

There's so much more performance potential to be squeezed out... for the customer, that would probably mean with V2...

Grüßle

Eddi

Born to fly ...
forced to work.
machine-translated from German · Show original
steveman 13 October 2026 20:2713.10.2026 20:27
Has there been any change with the Stratos 200?
I'd really like it, but only if it works well with VBar. Best regards, Stefan
machine-translated from German · Show original
RV 13 October 2026 20:3313.10.2026 20:33
https://www.vstabi.info/forum/list.php?68

Is there a dedicated forum for this, moderated by Carl-Henning Siebert? ;-)

Maybe you'll find something there, otherwise we'll have to wait until Carl gets in touch.

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.




Edited 1 time(s). Last edit at 10/13/2026 08:34PM by RV.
machine-translated from German · Show original
thomas1130 14 October 2026 05:0614.10.2026 05:06
steveman Wrote:
-------------------------------------------------------
Has there been any change with the Stratos 200?
I would really like that, but only if he's with
> vbar works well. Best regards, Stefan

The Stratos 200 works excellently with VBAR - both 2 and 3 blades :-)
I've already done many flights on the mechanics - it works fantastically - it's extremely fun.

LG
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless