forum.heinrichsweikamp.com

Hello,

Today, we released the 3.00 stable for the OSTC2 Series (2N/Mk.2/2C). It includes several smaller fixes, display fixes and some new features like the Ceiling display and a better battery warning.

Updating is very easy if you have 1.90 or later and using Windows.
1. Get new bootloader v2: http://www.heinrichsweikamp.com/?id=145&version=en
2. Follow the step-by-step instructions: http://www.heinrichsweikamp.com/?id=117&version=en

Hallo,

Heute haben wir die Version 3.00 stable für die OSTC2 Serie (2N/Mk.2/2C) veröffentlicht. Sie beinhaltet zahlreiche kleinere Verbesserungen und einige neue Features wie die Ceiling Anzeige oder eine bessere Batteriewarnung.

Das Updaten auf die neue Version ist sehr einfach, wenn bereits 1.90 oder später installiert ist und Windows verwendet wird.

1. Neuen bootloader v2 herunterladen: http://www.heinrichsweikamp.com/?id=145&version=de
2. Die einfache Schritt-für-Schritt Anleitung befolgen: http://www.heinrichsweikamp.com/?id=117&version=de

Viele Grüße/Best Regards,
Matthias

Done! Quick and easy. Thanks.

Note that some things reset back to default, for example, safety stop (off and depths), alternate GF (off) and perhaps others.

I've noticed the same. Thanks for update and fast respond.

New features like the Ceiling display

Can someone please explain me how this feature can be used?

I was doing a sportsdive these days with some light deco at 6m and 3m... While ascending i was playing around with the Custom View and got a ceiling display of 1.10 or 0.90 when i was somewhere between the 6m and 3m stopp...

in few words :

deco stop are defined every 3m (10 feet) since Haldane.

this means that when the real calcul of supersaturation defines you gotta stop at 4.4m, your OSTC shows you a deco stop at 6m.

The new feature CEIL displays ... 4.4m
According to the algorithm Bulhmann + GF, you can't go above this limit.

Is it pure ZH-L16C or modified by GF?

Shouldn't it be done like this: I have ceiling @3,2m deco is calculated according to GF set (let's say 70%) so the deco ceiling will be @4,16m but computer will show stop @6m? But ceiling displayed will be @3,2m?

i wrote "Bulhmann + GF"

Ceil is calculated with GF High

OK. Thanks.

Frage zu "NEW: Show event Bailout in internal logbook"

Bailout hat ich ja nur im CCR (pSCR) Mode, oder?

bei OC Tauchgängen ist das ja dann ein normaler Gaswechsel auf Dekogas und kein "Bailout"...

oder hab ich bei meinen OC Gaswechseln was falsch (im OSTC) gemacht, so das es als "Bailout" im Logbuch steht?

Vassilis Wrote:
-------------------------------------------------------
> This time, bootloader V2 could not automatically
> locate the .hex file for V3.0 firmware. It kept on
> reloading V2.9. This never happened in the past.

The bootloader should try to get http://www.heinrichsweikamp.net/autofirmware/ostc2.hex - which is the 3.00 stable. You can check your tinybld.ini for this link.

But at least you had success by manually installing it.

Regards,
Matthias

Chilihead Wrote:
-------------------------------------------------------
> oder hab ich bei meinen OC Gaswechseln was falsch
> (im OSTC) gemacht, so das es als "Bailout" im
> Logbuch steht?

Mit der 3.00 gemachte Tauchgänge?

Gruß,
Matthias

Hello Matthias

I tried bootloader V1 and JDivelog to resuscitate my OSTC2, even my PC system manager recognize the port COM3 when OSTC2 is plugged. But JDiveLog is sending: Could not establish handshake. Did you press RESET? And Bootloader V1 is showing the following:
ootloader for HeinrichsWeikamp OSTC,
based on TinyBootLoader, v.1.9.5 written by claudiu.chiculita@ugal.ro
http://www.etc.ugal.ro/cchiculita/softw ... loader.htm
Support: info@heinrichsweikamp.com
--------------------------------------------------------------------------------------------------

Connected to \\.\COM3 at 19200
HEX: 3 hours old, INHX32,18Fcode+cfg, total=92679 bytes.
Searching for PIC ...Not found,
ERROR!.

I'm using a magnet during the all process, but :S.

Help please.

divewithkarim Wrote:
> I'm using a magnet during the all process, but
> :S.

Last try: Please follow these instructions STEP BY STEP read.php?2,14083

I think it's easier if you send the unit to us for the update...

Please email us directly: info@heinrichsweikamp.com

regards,
Matthias

divewithkarim Wrote:
-------------------------------------------------------

>
> I'm using a magnet during the all process, but
>


No magnet is needed for the update.
A magnet reset during the update process may cause the unit to end up with a corrupted OS.
This might inhibit any further update attempt.
Better follow the procedure linked to by Matthias.

I got, unusually a Could not write.. Error ! the 1st time.
Just tried Update Firmware again and all OK.
Remember when the initial v3.00 screen comes wait for the reboot..

heinrichsweikamp Wrote:
-------------------------------------------------------
> Chilihead Wrote:
> --------------------------------------------------
> -----
> > oder hab ich bei meinen OC Gaswechseln was
> falsch
> > (im OSTC) gemacht, so das es als "Bailout" im
> > Logbuch steht?
>
> Mit der 3.00 gemachte Tauchgänge?
>
> Gruß,
> Matthias

nein, mit der 2.7 - ist vermutlich schon längst behoben.

In the logbook, profile graph has a color legend for different mixes, but profile curve displays different colors than a legend.
F.e - last weekend, switched to O2 @6m.
Legend shows G2: 100/0 as green color. Graph shows it blue. There is a red text "Bailout" in bottom right corner but for sure I did not bail out as I was on OC.

Best regards

@gorcio

I have seen exactly the same on a dive in my logbook. But this dive was before i update to Firmware 3.00. With my old Firmware 2.90 was this dive displayed correct.

@Sandro - fully agree. The dives I was referring to were also done while unit was still on 2.9. It only means that 3.0 does not display properly data from logbook dives, recorded with 2.90. Just an annoying detail.

Hi,

It's faulty data from 2.9 dives that is now (correctly) displayed in the 3.00. You won't see this with new dives made with the 3.00.

regards,
Matthias

Hallo zusammen,

ich wollte gerade das Update von der 2.90 auf die 3.00 Version machen.
Der Bootloader ( egal welche Version ) gibt mir folgende Fehler:

Connected to \\.\COM3 at 115200
Searching for PIC ..., unknown pic type: 57h
ERROR!


Connected to \\.\COM3 at 115200
HEX: 36 min old, INHX32,18Fcode+cfg, total=92622 bytes.
Searching for PIC ..., unknown pic type: 57h
ERROR!
Not found!





Was kann das für ein Fehler sein?
mfg Willy

Nachtrag:
über Diving Log funzt alles

Die tinybld.exe nicht direkt aus dem ZIP file starten, sondern erst beide Dateien entpacken (z.B. auf den Desktop) und dann vom dort starten.

Gruß,
Matthias

Danke @ Matthias,

jetzt passt es!

Super danke!

Falls meine Frage bereits gestellt und beantwortet wurde, bitte um Entschuldigung und Link zur Antwort.

Anderenfalls: Wie lässt sich die neue Firmware mit einem Mac (OSX 10.10) updaten?

Danke, André