This is not really a big problem. I had two standard (red) Sprits with v3.1.0 firmware. The flashing to v3.2.0 failed on both of them. See the Sprit Settings error screen dump. However, both flashed to v3.2.0 successfull in Recovery Mode. Also, the normal flashing to v3.2.0 worked successfully once the v3.2.0 firmware was loaded. On the other hand, the update to v3.2.0 on a Spirit Pro worked OK.

Just tried updating a spirit pro to latest and it failed. Rebooted the unit and it came back but cannot update, it fails everytime.

FrankFuss: Thank you for the message!

Nmony: Please use Spirit Settings 3.2.0, not old 3.1. Then it should work.

_________________
Spirit System developer

Just updated Spirit Pro with a Macbook Pro and via Wifi-Link. All went perfect.

Hi,

out of curiosity I updated my Spirit Systems as well.

System #1: Spirit Pro, Geolink, Jeti REX3
System #2: Spirit II, Geolink, Jeti REX3

The updates worked as expected, no problems. Prior to the update the Spirits have been on FW 3.1.0.

BR, Eugen

same here... updated 3 of my Spirits (2&RS) this morning... went like a charm - and is really much faster now!

btw: ... and YES the HW temps readings are now +/- identic to the ones given by i.e. jLog S32! now i can remove the jLogs soon of all my helis log of a testflight i just did attached! (the 2 purple ones are Hw temps via jLog & Spirit 2. Spirit log having better resolution / higher logging frequency)

_________________
cheers
Michael

I am afraid I was not so lucky - reading the waring about using a Mac I reinstalled my VMware and ran windows 10...not fun to start with

Anyway did you usual firmware update procedure and got a "failed" message. Now my RS is dead as a doornail.
No LED at all - yes I tried recovery procedure but the Spirit Settings app just hangs

Updated Spirit2 with no problem.
Spirit Pro says it updated now when I power it up I get slow flashing red led on the Pro and it will not initialize. tried Recovery Mode still does the same thing !!!
What to do next ??

i did it using Windows 10 running in Parallels on my Mac... just attached the interface cable, assigned it to Windows virt. machine... and click, click, ready. maybe you could try this way? Parallels is very powerful with various fbl/controller/etc interfaces... like HW Link, YGE Setup, Futaba S-Link, SPM programmer, and many others.... just great experience with all controllers i've ever tried.

_________________
cheers
Michael

The problem is the RS unit is now completely dead..no light no communication.
Recovery does not work....

As mentioned on Helifreak though I have been able to update a Pro and another RS unit just find directly on my Mac using updated drivers.

Unfortunately the original RS is unrecoverable