Why is SSI so unresponsive to diver wants?

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Your earthquake dive, that is an AWESOME and unique experience. If that was me, I would have journaled a page or so of what happened. To that end, I've discovered that each diver is different and has different viewpoints to logging dives. To each their own.
Thanks - Had an interesting side discussion re: that experience and underwater acoustics/audio phenomenon with Doctor @Angelo Farina

Cool to get a better understanding of the audio physics involved.
 
The other answer is that due to the Mares/SSI partnership, SSI has access to the programing source code. I had sent in an email to SSI asking about the same thing. I must have spent an hour trying to connect my Shearwaters to their app. :confused: The last sentence of the e-mail said that if other computer companies were to share their source code they would add it. Of course no company is going to share their source code so that's mute.
Sounds like BS to me, considering that 3rd party logs like MacDive support the Shearwaters - which means that either Shearwater is willing to share, or Mares/SSI app folks aren't willing to figure it out. I seriously doubt that they need access to the source code in any case - they would need the download interface documentation (how to talk to the computer thru bluetooth)
 
The last sentence of the e-mail said that if other computer companies were to share their source code they would add it. Of course no company is going to share their source code so that's mute.

Most companies have SDK packages available, they just need to ask for it. Garmin is the only major company that I know of that doesn't provide an SDK.
 
Sounds like BS to me, considering that 3rd party logs like MacDive support the Shearwaters - which means that either Shearwater is willing to share, or Mares/SSI app folks aren't willing to figure it out. I seriously doubt that they need access to the source code in any case - they would need the download interface documentation (how to talk to the computer thru bluetooth)
That's disappointing to hear. But yeah that was their reply to me.
 
Most companies have SDK packages available, they just need to ask for it. Garmin is the only major company that I know of that doesn't provide an SDK.
Garmin provides a free SDK that you can use to read and write dive log files.
 
  • Like
Reactions: L13
Sounds like BS to me, considering that 3rd party logs like MacDive support the Shearwaters - which means that either Shearwater is willing to share, or Mares/SSI app folks aren't willing to figure it out. I seriously doubt that they need access to the source code in any case - they would need the download interface documentation (how to talk to the computer thru bluetooth)
Something which can be easily "sniffed", doing proper reverse engineering.
You do not need help from the manufacturer for doing that .
 

Back
Top Bottom