Updating the thread as I’ve encountered another issue.

Deactivation of Core Isolation / Memory Integrity (suggested by Raimo Järvi) is still working:
https://support.microsoft.com/en-us/windows/device-protection-in-windows-security-afa11526-de57-b1c5-599f-3a4c6a61c5e2

However, Uninstalling the drivers simply within Windows 11 is no longer enough to activate the Memory Integrity back.

This linked helped me do it:
https://www.minitool.com/news/ftdibus-sys.html

Steps to do it:

Go into Windows Security, Try to activate the memory integrity, when that fails click on the “details” option available to you. You will find the driver causing problem.
In my case it was the FTDI bus driver with “OEM61.inf”

Open Command Prompt as Administrator and type the 2 following commands

dism /online /get-drivers /format:table pnputil /delete-driver oem61.inf /uninstall /force

(make sure to replace the oem61.inf if needed, you will have the full list of drivers after the 1st command)

Uninstalling properly this driver allowed me to Activate again the Memory Integrity.

@Alfred-Stoppels in your case you should use type B, base on your picture.

However, adapters are not standard, except the thread. Thus these restrictors may not function well. In this case try this one:
Restrictor for AI transmitter

Hi @marbjo,

One session is actually more than enough. Really appreciate your help!

If possible, you could send me all the file formats that you could export. I will evaluate which format is okay to process and easy for users.

I’m a freediver as well, but at first, I couldn’t find this kind of FREE software helping me with this. So, I developed my own one, originally supporting only my dive computers.

After I posted my training videos online with depth overlay, people often asked me how I did it. So, I decided to publish this tool and work on expanding dive computer supports to cover more brands.

I think my software will target only freedivers and be completely FREE and opensource (anyone can see the source code and make improvements). You may take a look at my GitHub repo here for the details: https://github.com/noppanut15/depthviz.

When you’re ready to share the logs, please email them to noppanut.connect@gmail.com. I’m happy to give you credit on the contributor list as well. 🙂

Thanks in advance!

This is my classic chat support dialog, this one is from today, but essentially they are exactly the same.

e11ef965-3555-4e29-ab60-44e8b74438e6-image.png

And they even don’t know where my D5 is now.

e4ac156b-c047-4058-924f-b4c197ed5593-image.png

And after that they told it is in the one of the finnish service, (it is listed on suunto service locator site) I called there - they told they haven’t received anything by mail.

My guess they lost it somewhere.

@Mikael said in Suunto Solution (1992 year dive computer):

Hello Community
I have an working Suunto Solution and also the data interface for it, but this uses RS232 not supported by any PC today.
Are there any modern interface to transfer data from it?
Have anyone built one, e.g. by Arduino?
Are any interface specs available/public to support a modern build?
Mikael

I know there are RS232-USB adapters, it could be what you’re looking for.

@Jérôme85 You might want to read this thread: https://forum.suunto.com/topic/10284/suunto-watches-to-come-in-2024/69

There are some hints or information sources in there 🙂

@jez01 Suunto app doesn’t support Vyper Novo, use SuuntoLink:
https://www.suunto.com/en-gb/Support/faq-articles/suunto-app/how-do-i-sync-dive-logs-from-my-dive-computer-to-the-suunto-app/