Support for Mares Sirius L

122 views
Skip to first unread message

Phil

unread,
Jul 15, 2026, 9:29:11 AMJul 15
to Subsurface Divelog
Hello,
I wanted to ask if the Mares Sirius L (https://www.mares.com/product/sirius-l-414180) is supported by Subsurface.
It isn't listed among the supported devices, just its bigger brother the Sirius.
So if they both share the same protocol, it could already be supported.
I ordered a Sirius L and am waiting for it to arrive, so I cannot test it yet. But maybe somebody already tried using it.

If it isn't supported yet I would love to help add support for it, though I'm not familiar with the codebase yet.

Best regards
Phil


Phil

unread,
Jul 21, 2026, 5:50:37 AMJul 21
to Subsurface Divelog
So I finally received my Sirius L.
I can currently only report on how it works without any logged dives in it.

On mobile it seems to work. It says that it didn't download new dives from the computer (which is expected, as there are none), but no error message.
On Linux using the latest AppImage build it seems to always have a "Dive data import error".
I don't get why mobile and desktop versions seem to behave so differently, but as I said, I'm new here.

I'll add the desktop logfile below, maybe someone can help me with what the issue might be.

Thank you
Phil

Log file:
Subsurface: v6.0.5576.0, built with libdivecomputer v0.10.0-devel-Subsurface-NG (ed5961d62532377a9e001eb0f80a5c3a510a900f)
[0,000001] INFO: Open: transport=32
[0,000018] INFO: Configure: baudrate=115200, databits=8, parity=2, stopbits=0, flowcontrol=0
[0,000022] INFO: Timeout: value=3000
[0,000025] INFO: DTR: value=0
[0,000027] INFO: RTS: value=0
[0,000029] INFO: Purge: direction=3
[0,001770] INFO: Write: size=2, data=C267
[0,074559] INFO: Read: size=142, data=AA00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000536972697573204C000000000000000030312E30302E30310100010031382D30332D32360000444546494E495245000000000000000000000000000000000000000000000000EA
[0,074574] DEBUG: Version: size=140, data=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000536972697573204C000000000000000030312E30302E30310100010031382D30332D32360000444546494E495245000000000000000000000000000000000000000000000000
Event: vendor=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000536972697573204C000000000000000030312E30302E30310100010031382D30332D32360000444546494E495245000000000000000000000000000000000000000000000000
[0,076321] INFO: Write: size=2, data=E742
[0,168995] INFO: Read: size=1, data=AA
[0,170623] INFO: Write: size=8, data=0C00000004000000
[3,171462] INFO: Read: size=0, data=
[3,171472] ERROR: Failed to receive the packet data. [in src/mares_iconhd.c:351 (mares_iconhd_packet_variable)]
[3,171483] INFO: Sleep: value=1000
[4,171828] INFO: Purge: direction=1
[4,173955] INFO: Write: size=2, data=E742
[4,256811] INFO: Read: size=1, data=AA
[4,258707] INFO: Write: size=8, data=0C00000004000000
[7,264038] INFO: Read: size=0, data=
[7,264050] ERROR: Failed to receive the packet data. [in src/mares_iconhd.c:351 (mares_iconhd_packet_variable)]
[7,264058] INFO: Sleep: value=1000
[8,264229] INFO: Purge: direction=1
[8,266039] INFO: Write: size=2, data=E742
[8,359013] INFO: Read: size=1, data=AA
[8,360725] INFO: Write: size=8, data=0C00000004000000
[11,361559] INFO: Read: size=0, data=
[11,361574] ERROR: Failed to receive the packet data. [in src/mares_iconhd.c:351 (mares_iconhd_packet_variable)]
[11,361584] INFO: Sleep: value=1000
[12,361776] INFO: Purge: direction=1
[12,363659] INFO: Write: size=2, data=E742
[12,446879] INFO: Read: size=1, data=AA
[12,448629] INFO: Write: size=8, data=0C00000004000000
[15,458388] INFO: Read: size=0, data=
[15,458408] ERROR: Failed to receive the packet data. [in src/mares_iconhd.c:351 (mares_iconhd_packet_variable)]
[15,458421] INFO: Sleep: value=1000
[16,458657] INFO: Purge: direction=1
[16,460685] INFO: Write: size=2, data=E742
[16,595415] INFO: Read: size=1, data=AA
[16,597224] INFO: Write: size=8, data=0C00000004000000
[19,602472] INFO: Read: size=0, data=
[19,602488] ERROR: Failed to receive the packet data. [in src/mares_iconhd.c:351 (mares_iconhd_packet_variable)]
[19,602498] ERROR: Failed to read the memory. [in src/mares_iconhd.c:835 (mares_iconhd_device_foreach_raw)]

Phil

unread,
Aug 18, 2026, 7:59:50 AMAug 18
to Subsurface Divelog
I finally took my Sirius L diving and now could try importing dives via Bluetooth (on mobile).

It seems to connect correctly, but doesn't correctly receive the dive logs from the computer.
So it seems it doesn't work correctly with the Importer from the Mares Sirius.

Would anyone be interested to get this computer supported?
I would be happy to help. Otherwise I would be stuck with the Mares App :/

Greetings
Phil

Jef Driesen

unread,
Aug 18, 2026, 8:33:09 AMAug 18
to subsurfac...@googlegroups.com
On 2026-08-18 11:14, 'Phil' via Subsurface Divelog wrote:
> I finally took my Sirius L diving and now could try importing dives via
> Bluetooth (on mobile).
>
> It seems to connect correctly, but doesn't correctly receive the dive
> logs from the computer.
> So it seems it doesn't work correctly with the Importer from the Mares
> Sirius.
>
> Would anyone be interested to get this computer supported?
> I would be happy to help. Otherwise I would be stuck with the Mares App
> :/

The Sirius L is already supported:

https://github.com/libdivecomputer/libdivecomputer/commit/cc9e75630f5afd5b37212d8e1ec3be5b9e1b182d

> Subsurface: v6.0.5576.0, built with libdivecomputer
> v0.10.0-devel-Subsurface-NG (ed5961d62532377a9e001eb0f80a5c3a510a900f)

But the subsurface version you used, doesn't include the Sirius L
support yet. You need a newer development build.

Jef

Phil

unread,
Aug 19, 2026, 5:58:32 PMAug 19
to Subsurface Divelog
Uh, that's awesome news!
I might try out a dev build on Linux, but am mostly going to wait for the mobile release with the Sirius L Support.

Thank you for the Info, Jef!

This thread can then be considered closed.

Cheers
Phil

Phil

unread,
Aug 19, 2026, 9:49:30 PMAug 19
to Subsurface Divelog
Sorry, got another question..
I was too curious and downloaded the latest dev build as an AppImage (Subsurface-6.0.5681-CICD-release), but I still don't see the Sirius L in the List of Computers from Mares.
I also installed the Android Dev version, same thing there.
Am I missing something or is it also not in the latest dev release?

Here a screenshot of the list of Mares devices on Subsurface-6.0.5681-CICD-release AppImage:
Screenshot_20260820_002341.png

Greetings
Phil

Michael Keller

unread,
Aug 22, 2026, 1:08:08 AMAug 22
to subsurfac...@googlegroups.com
Hi Phil

On 20/8/26 10:29, 'Phil' via Subsurface Divelog wrote:
> Am I missing something or is it also not in the latest dev release?


The Sirius L support is included in PR #4919
(https://github.com/subsurface/subsurface/pull/4919), which updates the
bundled libdivecomputer version and adds Sirius L to the
supported-device list. Build 6.0.5681 predates that change, so it will
not show Sirius L yet.

If you would like to test it now on Linux:

1. Open the Linux AppImage build for the pull request
(https://github.com/subsurface/subsurface/actions/runs/32547912067).
2. At the bottom of the page, download the Subsurface-Linux-AppImage-...
artifact. GitHub may require you to sign in.
3. Extract the downloaded ZIP file, make the included AppImage
executable, and run it:
      chmod +x Subsurface-*.AppImage
   ./Subsurface-*.AppImage
   4. In the dive-computer import dialog, select Mares and Sirius L,
then try an import.

Please report whether the dives import correctly. If not, attach a new
Subsurface log and include the Sirius L firmware version.


Ngā mihi

  Michael Keller

Phil

unread,
Aug 24, 2026, 5:59:02 AMAug 24
to Subsurface Divelog
Hey Michael,
Thank you for the detailed instructions.
Using the AppImage build artifact of the PR the Sirius L showed up and the import worked perfectly.

Greetings
Phil
Reply all
Reply to author
Forward
0 new messages