forum.heinrichsweikamp.com

Thank you. It was very hot on the boat and the a/c packed upon one day this may have been the reason. I was charging the computer in the saloon on a shelf under a light.
Resolved after a re-boot and battery set to T3

I have an OSTC 2 #10685 running v3.01. Battery 3.747v (T1)
Recently whilst I was away on a 2 week diving trip the battery voltage value was displayed on a red background. It worked fine during the trip.
Is this OK?

It matches the ceiling on my Inspiration Vison nicely, so very useful feature for my backup computer on CCR.

Matthias

Thank you all now working. I think I also had a problem with a faulty cable.

David

I now have a dead OSTC Mk11.

I have just tried to upgrade to firmware version 2.70 from 2.64 using OSTC Planner 434 (should have used bootloader) and it failed part way through giving me a screen of jumbled up words. Tried the magnetic reset and the screen cleared to be replaced with a blank screen ...

Tested it in the pool last night and it works fine now - thank you

Dived the 2.63 version yesterday in CCR mode unfortunately the gases are still coming out incorrectly in the logbook.
Still showed:
G1: 00/21
G2: 0/21
G3: 0/21
G4: 0/21
G5: 0/255
G6: 21/0

Do I need to reset the logbook

Matthias

Thank you, I thought it was something like that.

David

Forgot to say I am running 2.61 beta

I am running my OSTC MK2 in CCR mode.
I have set the gases as follows:
Gas 1 - Air
Gas 2 - 31% nitrox and the rest air.

The computer works perfectly during the dive with a setpoint of 1.30. It ends being quite close to the my Inspiration Vision handset. So I am very happy with it as a backup. I ...

Problem solved - thank you for the help
The dive that caused the problem was done on the latest beta version.
It was my first rebreather training dive and so the time using the computer in ccr mode. I clearly set it up wrong as subsequent dives have been OK.

See attached file. I have just noticed that the universal downloading does noy output all the data
David

Found a solution.
I used the downloader option inthe download window and set it for a Mk11 and the dives where downloaded.

Tried that everything is set back to default settings and Divinglog is now stuck with green progress 95% full and the same error message above, also the message "Writing Binary File" is in the OSTC download window

Updated Diving log 5.0.10 and re installed last stable version, 2.50, onto Mk2
Still had the same problem

I have posted this query on the Divinglog forum as well but maybe someone here can help.

When I try to upload from my OSTC Mk2 to DivingLog5.0
I get the following window:

OSTC ParseHeader2
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ...

I am about to embark on the rebreather route, training booked over Easter and unit,Inspiration Vision, ordered.

I have playing with simulator in CCR mode but wondered if there is any guidance/advice out there on using the OSTC as a backup to the Vision electronics.

Just used v2.09 on my 2 week trip to Maldives.
Ran it alongside Vytec DS. Settings ZH-L16OC with CF32 - 30% and CF 33 - 90%
I did a total of 32 dives, max depth 37m and dive time average 56mins.

The OSTC behaved perfectly apart from 2 small issues.
Some times when scrolling through the logbook it ...

Thank you will now have a play

How do you write the CFs to binary in Diving Log
I have set the option to true in the advanced settings but what do I next?

Yes I have 1.9 installed.
Thank you for the quick response

Am I correct that when the simulator/decoplanner is run it is not affected by any diving history.
Therefore if I run it after the first dive of the day with the info for a second dive, the info from the first dive does not affect the output.

I use a Vytec DS as backup and i carried out the claculation for my last 25 dives.

The value ranged from 1.08 to 1.05 with an average of 1.06

Data from previous dives
Date MaxDepth on first logbook page 1 MaxDepth in profiel data Salinity
21/7/10 31.2 31.2 n/a
31/10/10 30.9 31.8 1.03
31/10/10 14.9 14.9 1.01
1/11/10 30.3 30.6 1.02
26/4/11 35.5 36.5 1.04
26/4/11 30.2 31.4 1.04
2/5/11 31.3 32.5 1.04

The maximum depth on my OSTC MK 2 is different from that shown in the divinglog sofile profile graph and profile data.

Eg OSTC max depth 36.8m
Divinglog lowest postion on graph 38.14 and maximum depth in profile data is 38.14

Why would this be?

David
OSTC 808