Governor Issues - Critical

[davehour]

Hi,
Yes, I would like to try it.

[davehour]

Do I have to use it in both, Spirit Pro and Spirit GT with V4.0.0?

[davehour]

I recommend to try connecting RX cable to SBUS1 instead of SBUS2 port to make sure there is no transmission issue due to telemetry interference.
The port is more prone for powering issues too - because of Futaba design difference that are mentioned in Futaba manual.

Hello,

I connected the cable to S.BUS port and the issue didn’t happen. The heli flew fine.

Connected the cable back to S.BUS2 port and glitches started right away. According to what you said, there is transmission issue due to telemetry interference.

Is there a way to feed the telemetry data to the S.BUS2 port and channels data to the S.BUS port?

[ZeXx86]

Hello,

unfortunately using both ports at the same time will not work. But we will try to reproduce the issue and find way how to bypass the problem.
Do you know from when it started to happen?

[davehour]

Hi,

It started from first flight.
It happened in the three flights I used the S.BUS2 port.

[ZeXx86]

Can you let me know what is your FASSTest settings?
Is it 18CH modulation?

[davehour]

Hi,

Yes, it’s FASSTest 18CH.

[ZeXx86]

Thank you. We are trying the same with our Futaba 16SZ + HobbyWing v4. Unfortunately without a success yet.
Tomorrow we will continue and check if Governor could have influence.

[davehour]

Thanks for the support.

In case it’s relevant, the cutoffs happened with firmware 4.0.0 (Static Throttle Out).
After firmware 4.0.1, the Throttle Out was working again.

Next flight with S.BU2, I had tail glitches with v4.0.1 as soon as I took off. I mainly hovered for about 20 seconds and landed . Then, changed back to S.BUS and it flew fine.

[ZeXx86]

If you are referring to Throttle Out in the Real Time logging then yes, the issue there was also with V3. But regarding SBUS2 glitches nothing changed there from V3.