forum.heinrichsweikamp.com

Hi,

i noticed that the selected gas is no more showing in dive-mode.
Also the indication for the max depth and temperature is interfering.
I'm using 1.50 and CF9 is set to 20.

Reiner

Hi,

so all your OSTCs are still showing the presently selected gas on the UW-screen?
Or nobody else is missing that display?

Maybe i have a faulty 1.50 download?

Would be more then happy to hear some comments on this.

Thanks a lot, Reiner

P.S.: i've changed the headline to selected gas indication to prevent confusion

i will check it tomorrow

I have only used air in the last couple of weeks, and I am sure that "Air" was showing on the display

Steve Wrote:
-------------------------------------------------------
> i will check it tomorrow

Would be very helpfull, thanks

Hi,

mine is showing the selected first gas ( or first ccr setpoint ) in the surfacemode before starting the dive.

I'm looking for the display of the presently selected gas in the divemode under water.
Air as selected gas will only show in divemode when you choose CF9 < 21%.
I set CF9 to 20 but Air or NX21 is not displayed and NX50 and O2 is not showing either.

Thanks, Reiner

I have run the simulator. It displays Air for air and 50/0 for ean50.
I just noticed that the upgrade to v 1.50 switched all my gases to active, weird.

Hi Reiner,

I just checked it too
First gas EAN30 active
Second gas EAN 68 active and switching depth 9m.
When selecting a gas it is nicely displayed.
Firmware 1.5
Decotyp Buhlmann OC wo GF

dunno why it isn't working n your ostc.

grz,
Steve

Hello,

here a follow-up regading this.

First i downloaded 1.50 again and loaded it onto the existing 1.50 on my OSTC, still the same problem.

Then i downgraded the OSTC to 1.40 and everything was as it is suppossed to be, all indication where there.

Ater this i upgraded to 1.50 with the newly downloaded software and guess what, now the same 1.50 is working like a sharm.

So my first 1.50-download must have catched a bug.
I just wonder why the first reinstallation didn't work but the upgrade did with the same newly downloaded 1.50.

Anyhow, everything fine now.

Steve, Bradipo, thanks for checking!

Reiner

Hello Reiner,

Thanks for this post - additionally I can't see this behavior here. I though that a working but faulty download is very unlikely. The update is also CRC-protected...

Cheers,
Matthias

Hi Matthias,

maybe you remember another customer ( Peter ), i don't know his name here on the forum.
I loaded the same 1.50-file onto his MK1 that gave me the problem and his MK1 failed also.
When he send his faulty unit in he got the message from HW that the loaded software was faulty.
So somehow there is a chance to either spoil the software when downloading from the net or to spoil it when unzipping or uploading to the MK1.

Anyhow, as mentioned before i solved the issue with a new download of the same 1.50 version.

Thanks, Reiner

Hello Reiner,

In case you have such problems again, the "Md2 Hash" value (Available in the "Divinglog Downloader") would be very interesting.

regards,
Matthias