[SOLVED] Question regarding migration from FW 2.5.2 to 3.1.0

[LapinFou]

Hi folks,

Due to some personal reasons, I've not been able to fly my helis for more than 1 year.
Now, I'm back into business and discovered that Tomas has been working very hard.

After some search on the forum, I didn't see any particular recommendations/warnings concerning the firmware migration.
So I concluded than all intermediate major versions could be skipped (2.6 / 2.7 / 2.8).
The only relevant information were:

It is necessary to set the Special features again (if used) after the update from a previous version.

No need to change any parameter after update from version 2.6. and newer.

I migrated my helicopters from version 2.5.2 to 3.1.0:
- Align 500 ESP (Flybar + Spirit Pro + Platinum 80A V4 + FrSky X4R SBus / Governor mode)
- OXY3 (FBL + Spirit + Platinum 60A V4 + FrSky X4R SBus / Governor mode)
I also updated the WiFi-link module and LUA scripts on my FrSky X9D+ (OpenTX 2.3.9).

After the upgraded, without surprise since I was in the major branch 2.5.x, the rescue channel mapping was gone.
I mapped again the rescue mode to the correct channel.

Now, everything looks OK on the bench (servos travel and direction).
However, because I jumped some many versions, I'm a bit scared to fly again...
Maybe than jumping all those versions was not a brilliant idea after all...

Tomas, what would be you expert recommendation? I'm safe? Or it was a very bad idea?

Best regards,
Seb

[ZeXx86]

Hello,

all should be same except channel mapping.
So it should be enough to verify all features on the bench and this should be enough.

[LapinFou]

Hi Tomas,

I didn't expect a so fast answer (specially a Sunday).


I did check the channel order and nothing change.
The only missing setting was the special function "rescue".
The swatch plate is moving in the correct direction when moving the gimbals on my radio.
So, everything should be good !

I was scarred that some hidden data could get corrupted in this big version jump (for example new Flash/EEPROM data mapping or something similar). Specially, when I saw this kind of message "This unit has been detected for the 1st time by Spirit 3.1.0, do you want to launch the wizard?".
I'm glad I don't need to got through the whole setup process again.

Thanks again for yours greats products.
Whish you a lot of success.

Seb

PS: I changed the title to "SOLVED" status

[ZeXx86]

You are welcome.

I also recommend to Set Failsafe in the channels tab.

[LapinFou]

I also recommend to Set Failsafe in the channels tab.

I think I already did it (long time ago), but it is worth to check it.
By the way, what would be the recommended failsafe setup on the FrSky receiver? I guess it must be "No Pulses", correct ?

Seb

[LapinFou]

I also recommend to Set Failsafe in the channels tab.

I think I already did it (long time ago), but it is worth to check it.
By the way, what would be the recommended failsafe setup on the FrSky receiver? I guess it must be "No Pulses", correct ?

Seb

I'm asking the question, because I know the SBus does include a "Failsafe" flag, but I read on some drones forums that the FrSky SBus failsafe flag was kind of buggy.
So, I want to be sure to setup the failsafe parameters as expected by the Spirit unit.

[ZeXx86]

It should be enough to test failsafe - just turn off your radio and see what will happen.

Unit should display Receiver signal lost log event.

[LapinFou]

Thanks. I will test it with the "No pulses" choice (after disconnecting the motor... ).
I will post the result of the test ASAP.