RonR
Contributor
What Eric says above about the way MacOS negotiates is correct. You wont see the connected on the Cobalt until you connect from the application.
The 2.26 issue is not really a problem with the Cobalts firmware, but an issue with the way MacOS handles USB- essentially the problems is that if the last segment in the dive is exactly divisible by the buffer size, the Mac doesnt see the end of file and just keeps looking. Its not an issue for Windows or any other OS, and in new firmware we insert dummy bits in this instance to avoid the problem- a workaround. If you see this problem let me know and I will give you the fix. New Cobalt 2 firmware should be posted soon.
MacOS doesnt require drivers for the Cobalt because it is a true USB device- the other computers you mention are probably using using a serial interface and need a driver.
Apart from the MacOS quirk related to buffer size, there isnt any general problem we are aware of with Mac dive log applications. We, the Cobalts developers, are Mac users and in fact most of the Cobalts development was and continues to be done on Mac hardware. MacDive was the first dive log app available for the Cobalt. Both MacDive and Dive Log DT have many happy users (including under 10.10), and both have great support.
Id be interested to know who you contacted at SubSurface, we can work with them to figure out whats happening- Cobalt support is a little newer for them, but I will reach out to my contact there. I just tried downloading to SubSurface and it worked (under MacOS 10.10.5)- but Im seeing the same thing you are with SubSurface 4.4.2 re- showing a Bluetooth-Incoming-Port as the mount point. Thats clearly not right, but when I clicked the Download button anyway, it saw the Cobalt and downloaded the dives- and showed the "connected" message.
We are supporters of the open source libdivecomputer project, and actively encourage third party dive log applications. I know a few more are coming, but the list you have is complete for now.
-Ron
The 2.26 issue is not really a problem with the Cobalts firmware, but an issue with the way MacOS handles USB- essentially the problems is that if the last segment in the dive is exactly divisible by the buffer size, the Mac doesnt see the end of file and just keeps looking. Its not an issue for Windows or any other OS, and in new firmware we insert dummy bits in this instance to avoid the problem- a workaround. If you see this problem let me know and I will give you the fix. New Cobalt 2 firmware should be posted soon.
MacOS doesnt require drivers for the Cobalt because it is a true USB device- the other computers you mention are probably using using a serial interface and need a driver.
Apart from the MacOS quirk related to buffer size, there isnt any general problem we are aware of with Mac dive log applications. We, the Cobalts developers, are Mac users and in fact most of the Cobalts development was and continues to be done on Mac hardware. MacDive was the first dive log app available for the Cobalt. Both MacDive and Dive Log DT have many happy users (including under 10.10), and both have great support.
Id be interested to know who you contacted at SubSurface, we can work with them to figure out whats happening- Cobalt support is a little newer for them, but I will reach out to my contact there. I just tried downloading to SubSurface and it worked (under MacOS 10.10.5)- but Im seeing the same thing you are with SubSurface 4.4.2 re- showing a Bluetooth-Incoming-Port as the mount point. Thats clearly not right, but when I clicked the Download button anyway, it saw the Cobalt and downloaded the dives- and showed the "connected" message.
We are supporters of the open source libdivecomputer project, and actively encourage third party dive log applications. I know a few more are coming, but the list you have is complete for now.
-Ron