I tested with battery connected too, but then Spirit software on PC could not connect the unit. I'll retest tomorrow, maybe I did sth wrong...

I retested today. After I made vibration analysis "in flight" (on the floor), I can't connect Spirit to the PC anymore. I always get a message "Unit was not detected".
I have to unplug the battery and plug it again, and then connection works, but analysis graph is empty.

I tried connecting USB first, then Spirit, and also the other way around - same result.

Exact steps I'm doing:
1. Turn on the radio
2. Connect heli main battery, which powers on BEC too
3. Spool up (with tail blades, no main blades)
4. Turn on the switch to record vibration log
5. Turn off the switch
6. Spool down (throttle hold)
7. Bring heli to the PC and connect the cable.
8. Start Spirit. No unit detected..

@Thomas: am I doing something wrong?

These steps are looking good,

is unit normally responding to commands all the time? Is status LED steady On?

Make sure the Spirit Settings is started only once cable is connected to the unit.

_________________
Spirit System developer

Do you have an integration cable connected to the sys port when you are not doing the test?

Normally I have OpenTx integration cable there. But during these tests this is disconnected all the time to free the SYS port.

I'll retest today and try to find which specific action breaks the communication.

Ok, I retested today. It seems something is different in Spirit 3.2 comparing to 2.8. But I also compare two different helis and two different units.

On my Red Spirit, having 3.1, unit has to be connected to the PC when I power it on. If I connect unit to the PC later, after it is initialized, then Spirit software will not see the unit. However if unit is connected to PC when connecting the battery / powering on, then it works, and then I can disconnect it from the PC and reconnect multiple times and connection works as long as FBL is powered.

In my Spirit Pro, having 2.8, whenever unit is connected to the PC and powered, software can connect, no matter what the order was.

As for vibration graph, here it is, made on hard floor with tails blades on, main baldes off. I have to say I didn't try 3.1 on this heli yet, it is still on 2.8.

That looks fine to me. I don't think you would have any issues with vibration from I can see.
As for the connection to sys port - there is some configuration that happens when you have it configured for integration but when a usb cable is connected then it override that configuration. I have seen this in 2.8 and in 3.1. Not sure if there is a baud rate change or something else that happens.
Will have to dig a bit deeper to see if I can replicate the process

I installed 3.1 on this heli and tested this yesterday, with "Stabi Correction" enabled. It handles well all type of sport flying as well as aileron tic tocs and rolls. But if I do 15 consecutive elevator back flips, with rate ~250 deg/s, the rescue will be ~30 degrees off.

What is improved, is the rescue corrects itself over time. I think it wasn't like this in 2.8. If it was off by 30 degrees, it would be off until end of flight. In 3.1 it seems to work fine again after some time.

So should I look for problems in my heli or just assume recuse has some limits how good it can be?

Hello,

do you have any fan on the model?
Well, normally, even 3D pilots are not flying so many rolls/flips but it should work well in any condition. Did you try really hard flying? Not just these simple maneuvers?
Even rescue from 2.8 and earlier should handle any kind of flying.

The problem could be also in a slight deviation in sensor of your unit.

_________________
Spirit System developer