forum.heinrichsweikamp.com

Hi,

The new 1.97beta for the 2N/Mk.2 was just uploaded.

1) When downgrading again from 1.97 to 1.90 you may loose your dive profiles!
2) After installation of 1.97 the internal logbook will be converted into the new format. This takes about eight minutes and can't be interrupted. (If you already have 1.91 or higher installed no conversion is required)

Important new Features/Bugfixes:
NEW: Logbook displays ceilings and temperature curve.
BUGFIX: Decoplanner accumulates CNS during ascent.
NEW: Decoplanner warns in red if CNS is too high.
NEW: Decoplanner OC volumes in liters (or bars), up to 65000.
NEW: Released also in Russian language
BUGFIX: SetPoint store in Profile

Details about the upgrade process: http://www.heinrichsweikamp.com/read.php?2,4071
The link to the firmware: http://www.heinrichsweikamp.com/en/ostc_2n/firmware/

If there are any questions and/or comments, please post them here.

regards,
Matthias

Thanks very much - it appears you have not changed the release number in definitions.asm, still shows 1.96, was this intentional?

Regards

the new logbook looks very nice!
great feature!!!
there are "custom funktions" to change colours?
can´t read the green ceilings curve, specially at daylight.........

ATB Ekki

cparsons Wrote:
> the release number in definitions.asm, still shows
> 1.96, was this intentional?

It actually shows 1.98 already...

Matthias

little (optical) bug-report:

if i open the last dive (01) it looks like this
[IMG]http://up.picr.de/7948431feq.png[/IMG]
if i exit to the main-screen ... wait for standby and try to look at the dive (02) it looks like this

[IMG]http://up.picr.de/7948432frk.png[/IMG]

after that i onle "close" the dive (02) and "open" the dive (01) everything is correct... no red-lines at the beginning

[IMG]http://up.picr.de/7948433obe.png[/IMG]

... looks great

(dives done with FW 1.90)

Hello,

Yes, the temperature graph beginning is a known-issue we'll fix for the 2.0, of course

regards,
Matthias

Interesting - I looked at https://bitbucket.org/heinrichsweikamp/ostc2_code
and looked at the source for 'definitions.asm' and it shows 1.96??

This could explain something, perhaps I am not looking at the current source code?

Doesn't really matter but it would be good to know if I am looking in the wrong place for the current source

Best wishes

Maybe you don't have the latest changeset: https://bitbucket.org/heinrichsweikamp/ ... e5bb28891d ?

regards,
Matthias

What happened to 1.96 btw? Now there are only 2 minor releases left or will they be namend 1.99x if there is need for more bugfixes? As long it is said that 2.0 is on the road there are quite a number of new features (which I like very much!).

Thx,
Jan

Yes, you are correct, it is shown in the link you sent - I must be looking in the wrong place, I am an idiot

Thanks very much

I'm not able to upgrade from v1.90
Error message from bootloader:

===
Connected to \\.\COM5 at 19200
HEX: 4 days old, INHX32,18Fcode+cfg, total=81392 bytes.
Searching for PIC ...Not found,
ERROR!
===

Any idea what is wrong?

and what this error means?

I checked update with JDiveLog and I got error message:
"Could not establish handshake. Did you press RESET?"

I did the reboot and all resets and still doesn't work :/
Please advise.

Best Regards

Just do a reboot when it says "Reset" in the lower status line of JDiveLog. Did you?

Yes, I did it and still not able to upgrade my OSTC

Download, update settings, set time and Reset Deco Information works normally.

Have you tried using the BootLoader program direct? (not using JDiveLog in other words)

I know I struggled a bit until I realised the update has to be started while the OSTC is actually rebooting (you confirm the reboot and then have a few seconds to start the update!)

Or in other words, the transfer has to be started while the OSTC screen is blank, or at least with the BootLoader program it does.

You can get this from HW's site

Cheers

Problem fixed.

Probably broken cable.
Switch to original one fixed the problem.

Habe die 1.97 beta in Deutsch seit 3 Tauchgängen im Einsatz. 2 Probleme gab es:
Decomodell war auf ZHL16 GF CC eingestellt, obwohl ich nach dem Update ZHL16 GF OC gewählt hatte. Beim Auslesen der Tauchgänge an JDIVELOG 2.16 wird in der Kopfzeile immer noch ZHL16GF CC ausgegeben, obwohl das Dekomodell im OSTC auf OC steht.
Wunsch:
Das Umstellen des Dekomodells sollte nicht so einfach möglich sein z.B. mittels Absicherung mit doppelter OK-Abfrage.

mfG
Jürgen