forum.heinrichsweikamp.com

I get the idea behind SP's, but I don't like the detail that they can't be represented in the current version number scheme, with anything less than changing the protocol and logbook format of the device.

Numbers are just numbers, so rather than sticking with 2.97 and adding service packs on top of ...

I use whatever random micro-usb cable that comes up on top in the cable drawer and I've only had problems once. It took me about 15 minutes to figure out that the cable was a "power-only" cable, which didn't even have the leads for the D- and D+. I immediately threw that cable away.

Is the source for these new features going to be published?

It would be awesome to be able to follow the development.


//Anton

The link is to subsurface-mobile, A android app.

If you don't have a android device I'd suggest you try to remove CSR Harmony Wireless or plain reinstall the computer.

Your problems isn't related to either your OSTC 2 or Subsurface.


//Anton

What bluetooth stack vendor?

Then as a last exit I suggest you download your dives with https://play.google.com/store/apps/deta ... log.mobile , and sync them to your desktop via subsurface cloud.

//Anton

Your system doesn't allow subsurface to talk to COM12. Why? I have no clue. Maybe there's a setting somewhere where in your bt software where you can allow it.

Another suggestion is to try to use the "native" bluetooth connection in Subsurface. Click the "Connect via Bluetooth" button and choose ...

On your storage partition, there should be a subsurface.log file which contains technical logging about what happens when you hit download.

Report a issue over at https://github.com/Subsurface-divelog/subsurface/ and attach the log file to the issue and me or some of the other devs will take a look ...

I've google translated your post so I could read it.

There's probably a bug in libdivecomputer which i'm looking at. It has to do with some odd logic in libdivecomputer on how it figures out which dives to download.

I haven't had the time to fully understand whats going on there, but I plan to ...

Your xml file looks damaged, due to a bug in subsurface, thats fixed in the current development tree.

Open toto.xml and cleanup that Deco model info row or just delete it and things will work again.


//Anton

I think the protocol is the same as between the ppo2 monitor, hud and the ostc3, as described in:
read.php?6,14906,14906#msg-14907


//Anton

You need to plan a dive with more than just a litte deco for the information to appear.

Ex. 13min@40m/air with VPM +3 gives you to little deco to be able to fit a Bühlmann to it, while 14min@40m/air with VPM +3 gives you a effective GF=61/61.


//Anton

FYI: The bug in subsurface was not that it wasn't writing it in "two's complement" , it was actually a copy-paste error, where it wrote pressureSensorOffset instead of tempSensorOffset. The bug fix is released in v4.6.0.

Subsurface is a awesome tool written by beautiful and brilliant people. Its also awesome price performance ratio.

(for you who didn't figure it out by your self, i'm one of the developers of Subsurface =)

On the topic of VPM on a pic. I barely read pic assembly, but Subsurface deco.c contains both ...

ZHL-16C with GF 20/80 is similar to VPM-B for some depth / time / gases, but not for all.

A tip is to use Subsurface to calculate your VPM-B profile, and it will tell you with which GF you can approximate that profile.

Look at the bottom part of the "Dive plan details", you will see something like ...

Just some feedback on the contributions to the code that you have published.

I read all of the code that lands in the hwos_code and ostc2_code repositories. I haven't contributed any real code and probably never will, but I have given my feedback on multiple ocation's over email, and also reported ...

The OSTC 2N is a good dive computer, even if you're dives aren't to 80-90 meters. I use it on all my dives, even the ones that's only to a couple of meters.

Anyhow, I would recommend that you use the configure dive computer feature in Subsurface. I think its the best tool out there, but I'm a bit ...

I would love to see the code for the OSTC4 too.

//Anton

There's a bug in 4.5.4, which is fixed in 4.5.5 which affects safety stop parameter. Upgrade to that one and it works.


//Anton

I'd suggest you use a computer based software and download the data from for your dive computer and look at the profile on the computer.

I'd recommend Subsurface, which can be downloaded for free on https://subsurface-divelog.org/download/


//Anton

Can you create a libdivecomputer log file as described previously, for me to look at.


//Anton

You can now test a patched version from http://subsurface-divelog.org/downloads ... 66a8de.dmg

Did some reading of the code and spotted the bug.

The internal values ain't in meters, they are in 0.1 meters. Bugfix coming in the next beta, and i'll be posting links when they are built.

//Anton

If you're having problems with the configure dive computer functionality in subsurface, id suggest that you create a libdivecomputer log file from that page, and post it here. That way i can take a look at whats happening.


//Anton

You could always use Subsurface to both change settings and update the firmware.

Subsurface doesn't support changing all the settings on the OSTC, Mk.2/2N/2C , because they are so darn many, but the ones I have felt the need for is there.

//Anton

You can use http://subsurface-divelog.org/downloads/daily/Subsurface-4.5.3-31-g2163ae026fdd.dmg , which is a pre-release of what is to become 4.5.4, and it contains the Safety stop configuration parameters.

For anyone who would like to try it on windows, the url is:
http://subsurface-divelog.org ...