Spirit System

It seems problem was fixed.

Please retry with this app:
https://www.spirit-system.com/dl/settin ... r2-mac.dmg

i beg pardon but not yet for me.
i have append crash report. (deleted)
regards

Hi,

on all of mine {iMac 27 2013 Catalina, iMac 27 2017 Catalina, Air 2014 Catalina, Air M1 2020 Big Sur} this version is working, only on MacBook Air 2014 i had to restart once (really only once) after crash - this is the MacBook Air i had not installed the latest 2-3 versions on... it was still on 3.2.0 or so. all others working immediately after copying into 'programs'. all of them are now working...

nb: updated iMac 2017 and MacBook 2014 to Big Sur this evening... after installation of newest SiLabs (6.0.1) spirit settings (3.3.1.r2) worked immediately on both of them.

I also copied Spirit Settings 331r2 into the program directory, but restarting and resetting UBS ports does not matter - unfortunately it remains with the said crash. a pity

Update:
although I had installed the latest SILABS driver 6.01, I ran the driver installation again.
This has now actually led to success.
Many thanks for the support

Thank you very much for the reports!

Folks, how did you get the problem under control?
Brand new Mac mini M1 on Big Sur 11.4: Although I tried the "3.3.1.r2" and reinstalled the SiLabs (6.0.1) my Spirit Software is crashing when USB-Adapter is connected (without not). Starting extracted Software from "Programs".
Crashlog attached!

Thanks

Tino

Afraid this is still not fixed. I am able to run older versions no problem and actually updated one of my units to 3.2.2.
As soon as I open 3.3.1.r2 it crashes.

I then moved to my new Mac and same thing. Both are running Big Sur

Okay so it appears to be the popup that tells you what is new that is causing the issue.
Once I restarted many times I ran through a demo, restarted the spirit and then tried again and this time the popup came up.
Not sure why that is but I have now updated one of my spirit2 units to the latest version...

Any news on this?
Perhaps the admin could change the topic to „NOT Solved“
Thanks
Tino