"Official" New V4 firmware update/questions/issue thread

[omerco]

I have a solution for you:
Take another setup which works ( from another Heli).
Copy the model in your radio to a new one (or just copy all the travels and reverses).
Take the setup from the other gyro and copy it to your gyro. Write all the relevant parameters before that (mechanical setup) so you can put the numbers back after you do that.
Your stick scaling will be the same as the other model.

I have done stick scaling only once. Since than I copy the model in my tx and copy the setup before I set a new Heli.

[miron]

I had strange crash. It seems that tail servo went to left limit. I had fast clockwise pirotate. On ground servos were powered, but heli had no reaction to stick. I forgot to look to led on SK. But on video I saw steady red light. I turned off heli and powered and it worked fine. Fan on HW is dead. tail grip was jammed (grip was over rotated and link touched tail shaft), I fixed it but servo stayed at this position.
I havent antistatic kit on my logo 600. On 550 I haven't any problems with statiс. I made an conversion to 600

I can't understand SK540 behavior

2017 0730 161012 002 (0 min 11 sec)

2017 0730 161012 002 (0 min 42 sec)

[CZorzella]

Originally Posted by miron

I had strange crash. It seems that tail servo went to left limit. I had fast clockwise pirotate. On ground servos were powered, but heli had no reaction to stick. I forgot to look to led on SK. But on video I saw steady red light. I turned off heli and powered and it worked fine. Fan on HW is dead. tail grip was jammed (grip was over rotated and link touched tail shaft), I fixed it but servo stayed at this position.
I havent antistatic kit on my logo 600. On 550 I haven't any problems with statiс. I made an conversion to 600

I can't understand SK540 behavior

I'm sorry for your loss. At this point we can only try to guess what went wrong with your heli.

I'm sure that others with a lot more experience will jump in, but let me ask you a couple of things: did you have Blur Piros option enabled? at what rate?

Carlos

[omerco]

Sorry to see that

Please check if a log was saved on the sk for that flight and than we can see your event log.

[miron]

No blur piros.
How many flights SK saves? I turn off and turn on heli 3-4 times.

[CZorzella]

Originally Posted by miron

No blur piros.
How many flights SK saves? I turn off and turn on heli 3-4 times.

I'm not sure if there is actually a limit in terms of number of records. AFAIK it is only limited by the size of storage.

Like Omerco said, post the log file. You should connect the FBL to your computer (I'd disconnect the servos first in your case); organize files by its name and get the last large file that you find in there.

Depending on the log settings for this model, there is a lot we can learn by analyzing what is in there.

Carlos

[miron]

Heli is at country house. I will dowload logs on holidays

[miron]

logs

[miron]

I don't know were flight logs are.
Same problem today. Heli crashed in normal flight after takeoff and idle up. No response to sticks in flight and on land. SK led was solid red after crash. RX had green led. I don't understand why fbl didn't react to sticks. Solid red led is initialization, but during initialization servos mast work. This fbl error state will not end with time. I need to reset power to get working heli.

[omerco]

I don't understand why you flew it before we could see the log?
Red led is not just init - it is also error, like low voltage or comm lose, or a problem like faulty sensor and such.

When I had exactly what you describe it was a bad BEC causing in flight reset.

I will check your logs first thing in the morning.

[miron]

Flashing red led indicates low voltage, I has solid red led. After in flight fbl reset fbl must response to controls.
I set optipower guard. I thought that it will rescue heli, but I connected guard battery after heli battery and guard didn't work

[omerco]

flashing red might be low voltage BEFORE there is a reset. after a reset you will have solid red and no response: happened twice to me unfortunately.

here is the only log with flight data. the rest are on the ground. its obvious you have some power/BEC problem. also in the event log there are is a warning regarding link loss so you might also have an Rx/S-bus problem:

[miron]

Thanks.
This is strange. I think that it's a problem with BEC wire somewere.
Is it possible to view vibrations or thr channel and voltage at the same screen?

[miron]

I had 4 flights today without problems. I grounded tail boom , soldered bec voltage switch (I have bec like YEP 20 with jumper switch) , added second wire to RX (I used one wire directly to fbl from bec) and set optiguard.

[omerco]

Post the logs so we can see if it's solved

[miron]

I'm at home now. I'll download logs on next holidays

[omerco]

When you do I'll try to reply quickly so you can fly after we check them and not before

[miron]

Ok.
On pictures from logs there are steps of bec voltage. I set bec to 7.4V, but there are sharp steps with idle zone 6.4V. It's strange.
I can understand step to 5V, becouse without jumper bec works at 5V. It's possible if jumper contact is bad.
But there is perfect switching from 7.4V to 6.4V

[omerco]

1 that can show a bad bec not sustaining the desired voltage under load.
2 what's you optiguard voltage?

[miron]

There are no logs of previous flights in SK memory.