← Logo 200

Logo 200 v8 with new update - problem

Mikado Model Helicopters › Logo 200 · Started by dtx66 on 21 May 2026 07:4821.05.2026 07:48
dtx66 21 May 2026 07:4821.05.2026 07:48
Hi, just update my logo200 v8 to least version 8.2.38, but the first flight it's oscillate and can not lock the tail. finally crash my logo 200. did I missing some setting ? I already reset my logo 200(use the vbce to creat a new logo200 send data to the micro EVO) I will repaire the damage today and try tomorrow.
Eddi E. aus G. 21 May 2026 08:5221.05.2026 08:52
Hi,

we're sorry to hear.

Was your transmitter updated, too, and did you do a new setup before the incident?
Because the preset now afaik would be for the V8 with updated ESC.

If you just updated your EVO micro, though, nothing odd should have happened, settings don't change with an update.

—Eddi

Born to fly ...
forced to work.
dtx66 21 May 2026 09:1121.05.2026 09:11
the transmitter was updated too. Just update the Evo micro and nothing changed set up before my flight.
but after I crashed. I reinstalled the presets. I think maybe it changes something. it’s the ESC need to update too? how to do it?
Eddi E. aus G. 21 May 2026 15:3921.05.2026 15:39
Hi,

hm, strange.

Please let me know the serial no. of this unit and I can have look at the logs in your cloud (if VBar Control Touch or EVO and cloud enabled).
Please also save the setup file to your transmitter (Model Setup/Tools/Save), then I can also have look in your cloud.

The ESC can be updated using OMPHOBBYs bluetooth adapter OSHM4118 and Sunnysky's smartphone App.

*** disclaimer ***
Obviously, any damage done during the process is unfortunately on you, dear reader, like with all DIY things we do, all the time, we take calculated risks ^^
Particularly damage resulting from misconnection/reverse polarity, but also when testing on the bench (w/o blades), and when maidening again.
If in doubt, contact your local dealer for help, you may also send in your heli for us to update it (or painstakingly remove the ESC, and mount it again later, and mind doing the software updates and a test flight ...).
***end disclaimer ***

All you need to do is _carefully_ unplug the yellow and white wires from the TELE ports (take note which goes where, don't pull/rip the wires ...) and MacGyver them somehow to the yellow and white wires of the BT module, and wire the red and black wires (power supply, live and ground) to a power supply (can be the ESC proper, or some standard receiver battery). Double-check polarity.

Once powered up, you can connect to the ESC via Sunnysky App (BT needs to be allowed), load the update file (attachment, needs to be unpacked and copied to your smartphone first, or downloaded and unpacked there directly), and update the ESC.
Don't make any other changes.

I MagGyvered a wire harness for our internal use here (attachment), it has two JST couplings for the data wires, and one of the smaller OMP size connectors, to steal power from AUX.

Lastly, with the VBar EVO micro and the transmitter updated, you can change the settings for Tail and ESC to LOGO 200, and that's that.
Seems to be. Should be it.

I've done the update just before lunch so I can be sure it works this way, but I haven't flown the 200 yet.

By the way, I also updated the EVO micro from 8.1.something to 8.2.current in the process, and I didn't notice anything odd, yet.
At least held in the hand while it was running, everything worked as it should, the tail showed the expected response so far.

Fun fact: I can install this iOS App on my Mac and use it there, Bluetooth and all.
Try it with Android and on Windows or Linux ^^ :-)

Best,

Eddi

Born to fly ...
forced to work.

Attachments:
open | download - Vbar-B1.9.sqlite3.zip (112.6 KB)
dtx66 21 May 2026 16:2521.05.2026 16:25
Hi Thanks for the solution and my evo id is 27009508. I have save the settings and please to check.
I will try to make a cable to upgrade the ESC.
dtx66 21 May 2026 17:1321.05.2026 17:13
Hi? I have updated the esc to 1.9 make a cable to do this. and choose both tail and main rotor to logo200. I will test tomorrow and make some report here.

Eddi E. aus G. 22 May 2026 09:0422.05.2026 09:04
Hi again,

update managed, yay! :-)

The setup looks pretty much default, then.

So I guess it's safe to test, start in bank 1, easy on the sticks, when it feels OK, bank 2, same, then bank 3, and watch out for oscillations, be prepared to switch back to a safe bank or to cut throttle and set the model down.

The logs in your cloud look pretty much uneventful, can't seem to find the one with the incident (last logs with flights I think from May 12th, then from yesterday (ground work only?).

—Eddi

Born to fly ...
forced to work.
PeteStewardson 22 May 2026 10:0622.05.2026 10:06
I had something like this. On lift off the tail was pulsing which meant the heli turned clockwise like a clock hand. I selected model setup as a new model, and selected logo 200, so basically resetting everything. This fixed it 100% and it flies superbly now. The update to the latest FW seemed to need a full reset after the upgrade.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Eddi E. aus G. 22 May 2026 13:0022.05.2026 13:00
Hi all,

OK, I just revisited our latest Essay about Micro Heli Optimization here, and I guess it's obvious.

Quote:Link above | Tail Gain (Tail Sensitivity)

The gain value is scaled significantly higher than before. A gain of 25 corresponds roughly to 80 in the previous software version (only for motorized tails!). Therefore, always start with low values, such as 10, and work your way up. Values from 25 onward already yield very good tail performance. Too much tail gain leads to wagging/shaking in a hover, or heavy tail slapping under high motor loads. Too little tail gain causes control delays, especially under load (e.g., tictocs with simultaneous tail input).

Means, on every model with a tail motor _and if_ this model was already set up with an older firmware, you _have_ to dial down tail rotor gain to approx. 1/3 of the original value. Then, you can start increasing the gain again to the point where it feels good or beyond, where it starts to oscillate.

Means, if you had 80 before, you now have the equivalent of 240 ... whoopsie :-)

If you do a New Setup, it's already all right, though, so nothing to worry about with e.g. XLPower Stratos (unless you had a pre-production model and VBar from before), so it basically only affects LOGO 200 with EVO micro.

We'll inform everyone soon, via News App.

—Eddi

Born to fly ...
forced to work.
dtx66 23 May 2026 08:0323.05.2026 08:03
Hi Eddi,

Today I have a test for my repaired Logo200, So far so good, everything come back and I feel good for my flight. I will asking my friends to test more who can do more 3D flight than me.

P.s. what update for the new ESC 1.9 version ? I just find the tail motor sounds a little aggressive. but not obvious form the filghts.
Eddi E. aus G. 27 May 2026 09:0427.05.2026 09:04
Hi,

I'm not deep into what the update was, but basically it allows the ESC to work at higher refresh rates, which in turn allows the VBar to provide better tail performance, working both with the main motor and the tail motor torque.
This is probably also what you hear.

Best,

Eddi

Born to fly ...
forced to work.
VStabi VStabi Pioneer of Flybarless