1.90 Stable released for the Mk.2/2N

[heinrichsweikamp]

Hi,

The 1.90 stable is now available for the Mk.2 and 2N and recommended to all users. users upgrading from the 1.80 will notice a lot of new features like the "Future TTS", an improved runtime planer, a nicer logbook and more.

http://www.heinrichsweikamp.com/en/ostc_2n/firmware/

A new PC bootloader application will be available in a few weeks, as well. With 1.90 or later this application will update your OSTC Mk.2/2N with a single click to the latest stable version.

Cheers,
Matthias

[mike coull]

Thanks, downloaded it tonight and now enjoying trying a few simulations on it.
Mike

[Carl]

Hi,

Will the new PC bootloader run on 64-bit WIN7 ... I had problems with the previous version.

[heinrichsweikamp]

> Will the new PC bootloader run on 64-bit WIN7 ...

Yes, but the old one does work on 64bit Win7, as well.

The new bootloader can download the latest stable from the Internet, updating the OTSC Mk.2/2N then requires one click. Beta versions need to be downloaded manually. It will only work with 1.87beta or later so we'll wait a few weeks before publishing it.

Regards,
Matthias

[Mike]

Danke für die Arbeit und die 1.90 ist auf mein MK2 Ohne problem.

MFG

[Mike]

Nur zu Info,

-CF56 ist begrenst bei 25l/min, da ich immer mit 1/3 mehr planne geht es nicht.

Ist aber nicht so schliem

MFG

[Stephane]

Hello,

I have upgraded to 1.90 and I found something annoying when in CCR mode:
I'm using air as diluent. My bailout gas is Nx38. If I bailout to that gas and come back to CC mode, the diluent is note air but Nx38 which is not so good.
The Shearwater as two different gas list: one for OC (or bailout), on for CC. Is there a way to implement a thing like that? Or at least to have one gas marked as diluent so when you switch back to CC mode, it will use this particular gas.

Stéphane.

[cparsons]

Been trying to compile the source and there appears to be a problem?

Message[311] C:\USERS\CSIT044\DOCUMENTS\PERSONAL\DIVING\OSTC\SOURCECODE190\OSTC_CODE_ASM_PART1\MENU_LOGBOOK.ASM 338 : Operand of HIGH operator was larger than H'FFFF'.

Also, you mention not requiring the C18 compiler but you need the clib.lib library?

Is this somewhere else? (I couldn't see it!)

Regards

[nakatomi]

As far as I remember that message is just a warning and it first appeared approximately with the final 1.88 changeset. The code does compile nevertheless.

Regarding the lib, I also had to install the C compiler to get it. But there´s a trial version available, so that might help.

[Steve]

very nice

agree with Stephane, would be nice to have 2 gas lists
like the ppO feature

[cparsons]

I installed the C18 trial and it now compiles, thanks very much

Chris

[Solodiver]

After installing 1.90 my unit seemed to be resetted in some way. It is now set to OC (has been CC before) and Gas 1 is Air and active. Any other gases are inactive but seem to be the same as before.

It seems that many more settings and CF has been cleared (set points, GF, etc.).

Will do some tests soon...

[dmainou]

Solodiver Wrote:
-------------------------------------------------------
> After installing 1.90 my unit seemed to be
> resetted in some way. It is now set to OC (has
> been CC before) and Gas 1 is Air and active. Any
> other gases are inactive but seem to be the same
> as before.
>
> It seems that many more settings and CF has been
> cleared (set points, GF, etc.).
>
> Will do some tests soon...


Yep, it's simple good practice to bring it back to default settings to avoid any possible and unintended knock on effect.

I actually wait recommend you to wait some minutes until it reboots by itself before starting to play with it. (you'll see a message with the word "hash" or something like that).

D

[Solodiver]

So you're saying this is done by purpose by the new firmware? Is it the same with your box? I've never experienced a reset like this after installing a new (beta) firmware (and I never missed one in the last 10 month). This should be noted in the change log or installation notes then...

Jan

[Regthing]

I'm sure I've had to reset all my CFs after every upgrade to the point I would go through and note everything that wasn't default beforehand.

[dmainou]

Jan,

Check this link. It's self explanatory


D

https://bitbucket.org/heinrichsweikamp/ ... changesets

Look under commmit 327 which takes you to here:


https://bitbucket.org/heinrichsweikamp/ ... 44f79e298c

[Solodiver]

dmainou Wrote:
-------------------------------------------------------
> Check this link. It's self explanatory

OK, so I did nothing wrong (thought about to have selected the wrong reboot/reset menu).

Again: In my opinion this is a quite serious issue which should be noted in the change log/installation instructions. It would be even better to have some support in jdivelog for reconfiguring the device, f.i. if one could save the settings and compare to the ones from the unit. In my case I had to change many CF to get it back to the way it has been before and I'm not even sure it has the same behaviour now...

Thx,
Jan

[heinrichsweikamp]

Solodiver Wrote:
> Again: In my opinion this is a quite serious issue

No. It would be serious if we do not reset for a stable release.

> unit. In my case I had to change many CF to get it
> back to the way it has been before and I'm not


I doubt that you are not able to re-set your custom functions within a few minutes.

Regards,
Matthias

[Regthing]

Solodiver Wrote:
-------------------------------------------------------
> dmainou Wrote:
> --------------------------------------------------
> -----
> > Check this link. It's self explanatory
>
> OK, so I did nothing wrong (thought about to have
> selected the wrong reboot/reset menu).
>
> Again: In my opinion this is a quite serious issue
> which should be noted in the change
> log/installation instructions. It would be even
> better to have some support in jdivelog for
> reconfiguring the device, f.i. if one could save
> the settings and compare to the ones from the
> unit. In my case I had to change many CF to get it
> back to the way it has been before and I'm not
> even sure it has the same behaviour now...
>
> Thx,
> Jan

There is a great bit of hardware out there for doing this, it's been around for a while now, pen and paper it's called. Takes minutes to skip through the CFs and note the non default ones....

[dmainou]

Solodiver Wrote:
-------------------------------------------------------
> dmainou Wrote:
> --------------------------------------------------
> -----
> > Check this link. It's self explanatory
>
> OK, so I did nothing wrong (thought about to have
> selected the wrong reboot/reset menu).
>
> Again: In my opinion this is a quite serious issue
> which should be noted in the change
> log/installation instructions. It would be even
> better to have some support in jdivelog for
> reconfiguring the device, f.i. if one could save
> the settings and compare to the ones from the
> unit. In my case I had to change many CF to get it
> back to the way it has been before and I'm not
> even sure it has the same behaviour now...
>
> Thx,
> Jan


Jan, you are getting a brand new upgrade. You simply can't assume that it will be as before. I mean, good feedback and all that but you must remember it is not different than upgrading from XP to Vista and to 7. It is not a patch but a full stable release.

Just like your printer settings and your wireless connection details are gone when upgrading your pc (and there is no manual for that bit to the best of my understanding) you must assume that your CF's are gone.

In fact I would recommend you to reset them yourself regardless of what HW forces it or not.

Its just good practice.

D

[Solodiver]

Regthing Wrote:
> There is a great bit of hardware out there for
> doing this, it's been around for a while now, pen
> and paper it's called. Takes minutes to skip
> through the CFs and note the non default ones....

Thx Scott, will do this, brilliant idea.

But wait, there is a problem. Then the change log should note every change in the default setting also (which happens to several settings in the past).And of course I need to know that the settings will be reseted _before_ I do the update.

The only thing I claim about in here is to inform the user that nearly all settings in his box will be cleared (and he can do a paper backup). This is a new feature and can be quite serious! In my case it was easy to recognize because I changed many things, it switched back to OC and even the gas changed. Other guys might miss the resets which can lead to problems in the next dives (wrong deco model, GF, gases etc.)...

[heinrichsweikamp]

Solodiver Wrote:
> be cleared (and he can do a paper backup). This is
> a new feature and can be quite serious!

No. All stable releases since 2004 reset the custom functions. It's not a new feature.

Regards,
Matthias

[Solodiver]

OK, Thx Matthias. Due to the many beta releases in the last months it seems I got used to the "easy" update process, sry.

I still would recommend a note in the release notes...

Thx,
Jan

[Regthing]

[img]http://presentoutlook.com/wp-content/up ... untain.jpg[/img]

[Nordicdive.de]

Hi,

update to 1.90
Yesterday I have run a simulation.
GF High = 85
GF Low = 15
18/45 no decogas
Bottom time: 21min
Depth: 54m
Calculation time ~3 min

Decoplan
33m-1
30m-1
27m-1
24m-2
21m-2
18m-3
15m-5
12m-8
9m-13
6m-255
6m-255
6m-255
6m-255
6m-255
6m-255

TTS: 1484

Run a Start Dive:
same Mix
down to 55m in 2min
after 20 min dive time
TTS 283

Seems to be something is going wrong in the calculation.
Does anybody saw the same issues?
Does anybody test 1.90 in real in Trimix dive?

Regards
Alex