A few questions

[greenforce]

Hi,

I'm very interested in this computer.

I have 3 questions right now, but will have more in the future;

1. Is it possible to modify the last stop depth (6m instead of 3m)?
2. Is it possible to modify the security level? (0 to 50% on a VR3 for example)?
3. Do you plan to integrate Deep Stops within a short time?

Thanks and congratulations for your work!

[heinrichsweikamp]

Deep Stops are not planned to be implemented immediately.
Since the modification of the last stop depth is requested quite often we will take care of this in one of the next releases.

The security level is fully customizable in all OSTC firmwares released. The major functions are CF11 and CF 12 .
A security level identical to the VR3 is possible by increasing the inert level of the gas at the gas setting.
Additionally CF16 modifies the conservatism of the deco predictions.

[greenforce]

Hello again,

I bought the computer, looks nice but not been diving with it yet.

Firmware version installed is 1.10, I'd like to upgrade to 1.11.

But when using tinybldwin, I get the following message:
"Searching for PIC ...Not found,
ERROR!"
Though the interface and OSTC are on, and I had a reset of the interface.
Downloader found the right existing firmware version (1.10) and firmware id.

Did I miss something?

Thanks

[heinrichsweikamp]

Hello,

First, when pressing the "Write" button, the "TX" LED at the interface must blink weakly for about 10 seconds. If not, please check if the COM port is correct (The bootloader uses a virtual COM port) and the FTDI driver is installed properly (Device Manager must show "HeinrichsWeikamp OSTC" somewhere). Then, within the 10 seconds after the "Write" press and release the Reset button at the interface. The yellow LED (Warning) at the OSTC must be ON, "RX" and "TX" should flicker for about 60 seconds.

Can you download the profiles with any PC software (Divinglos or JDiveLog)?

regards,
Matthias

[greenforce]

Hi,

When I press Write, the TX Led blinks for 10 seconds.
I make a reset within the 10 seconds, the warning + usb leds on the OSTC go on for a few seconds, but after that, nothing happens.

Jdivelog sends me the message "Com port not defined"

Thanks

PS: I often get the message "Building MD2 Hash"

[heinrichsweikamp]

Hello,

There seems to be a problem, because the Bootloader starts (Yellow LED+USB LED on) but the PC does not see it. You can configure the COM port in jDiveLog at -> File -> Settings -> Divecomputer -> Driver

Then you should be able to download the profiles and adjust the settings. There can also be an hardware issue with the interface, so don't hesitate to contact us directly (info@heinrichsweikamp.com) if there is some kind of hardware problem.

MD2 is a fingerprint of the firmware, it's build once after every reset (takes about 70 seconds).

regards,
Matthias

[greenforce]

OK, it worked!

Thanks for your help!

[heinrichsweikamp]

Hello,

You also update the firmware with JDiveLog....

Regards,
Matthias

[greenforce]

Hi,

Another question:

Since firmware version 1.10, the Change depth to another gas can be specified, which is great.

But if I want to let the OSTC specify the change depth, do I set the change depth on 0?

Thanks.

[heinrichsweikamp]

Hello,

The change depth can be specified, so the OSTC calculates a gas change for the decompression display. e.g. deco with EAN70 will cause shorter decotimes then deco with Air.

You still have to change the gas manually! When change depth = 0m, the OSTC will display the decompression based on the set gas only. You can still switch gases, the decotime display will be adjusted after the gas change then.

Regards,
Matthias

[greenforce]

Hello Matthias and team,

First dive with the OSTC this morning!

Fantastic display visibility!
Easy to use, even with gloves...

I was diving with a Tx 18/20 and a deco Nx 76.
Total dive time 40min, bottom time 10min at 52m.
Both gazes where activated and the depth for the Nx 76 was set to 11m.

2 Remarks:

- OSTC was giving me total deco time with Tx 18/25, and it is only when I switched manually to the Nx 76 around 10m that it recalculated a new deco time.
Was it not supposed to calculate the right deco time from the beginning in this case?

- after the dive, the total desaturation time was of only 3hrs, which seems short to me.

Thanks for your help and congratulations for this fantastic computer!

[heinrichsweikamp]

Hello,

Thanks again for the feedback. This bug in the 1.10 and 1.11 was reported from other Trimix users, too. It will be fixed in the beta we will release tomorrow.

Additionally, a 6th gas can be free configured underwater.

Edit: See: http://www.heinrichsweikamp.com/read.ph ... 37#msg-237

Desaturation and no-fly times calculation will be adjusted in one of the next releases (We will change desaturation limits in the model).

Cheers,
Matthias