forum.heinrichsweikamp.com

ENGLISH below.

Hallo,

Die neue Firmware 1.5.3 ist nun veröffentlicht.

heinrichsweikamp.com

Anleitung zur Installation: viewtopic.php?f=7&t=19186 (Je nach aktueller Version kann es nötig sein, das Update zweimal zu starten. Der OSTC4 gibt dazu nach dem Update nötigenfalls eine Meldung aus. Grund ist, dass möglicherweise auch sehr alte Teile der Firmware wie der Schriftsatz und der Bootloader aktualisiert werden.)

Wegen aktuell noch nicht ganz geklärten Problemen mit der iOS App OSTConf empfehlen wir, das Update mit dem OSTC Companion auf einem MAC oder Windows PC einzuspielen.

Folgende Änderungen und Neuerungen gibt es seit der V 1.4.8:

[1.5.3] with RTE 2.03
CHG: Always show battery voltage in surface mode
CHG: battery status is now preserved for future updates
NEW: Support for much faster updates (With OSTC companion 3.2 and later)
FIX: (very) short screen lag removed during sample storage in dive mode

[1.5.2] with RTE 2.02
Beta Version!
FIX: display of time of minimum voltage
FIX: Display of Sensor values. At divestart sensor values were shown even sensors were deactivated (fix SP)
FIX: Bugfix invalid voltage / temperature after coldstart
FIX: Instant dive start at several meters out of sleep mode (Jumping into the water) may resulted in lagged/freeze depth reading
CHG: Speed increase of Bluetooth communications
CHG: Look and Feel for Gauge/Apnea mode with flipped screen improved
FIX: Deco warning after Gauge mode
FIX: Download issues of corrupted dives
FIX: Proper logbook write (Very spurious error, mainly in CCR mode)

[1.5.1] with RTE 2.01
NEW: Support for end-2019 hardware

[1.5.1] with RTE 2.00
FIX: 1.5.0 could enter dive mode when ambient pressure reduced during flight

[1.5.0] with RTE 1.90
FIX: Optical port timeout fixed
FIX: firmware version in logbook data
FIX: battery information in logbook data
FIX: correct main version number logbook data
FIX: fix drawing of CCR bailout profile in internal logbook

ENGLISH:

Hello,

The new firmware 1.5.3 is now public.

heinrichsweikamp.com

Manual on how to install: viewtopic.php?f=7&t=19186

(Depending on your current version it may be required to start the update twice. The OSTC4 will show you a message after the update if this is required. Reason is, that this update also may update some older parts of the firmware like the font table and the bootloader).

Because of currently existing issues with the iOS App OSTConf we recommend to install the upgrade with the OSTC Companion on a MAC or Windows PC.

The following changes have been made since V 1.4.8:

[1.5.3] with RTE 2.03
CHG: Always show battery voltage in surface mode
CHG: battery status is now preserved for future updates
NEW: Support for much faster updates (With OSTC companion 3.2 and later)
FIX: (very) short screen lag removed during sample storage in dive mode

[1.5.2] with RTE 2.02
Beta Version!
FIX: display of time of minimum voltage
FIX: Display of Sensor values. At divestart sensor values were shown even sensors were deactivated (fix SP)
FIX: Bugfix invalid voltage / temperature after coldstart
FIX: Instant dive start at several meters out of sleep mode (Jumping into the water) may resulted in lagged/freeze depth reading
CHG: Speed increase of Bluetooth communications
CHG: Look and Feel for Gauge/Apnea mode with flipped screen improved
FIX: Deco warning after Gauge mode
FIX: Download issues of corrupted dives
FIX: Proper logbook write (Very spurious error, mainly in CCR mode)

[1.5.1] with RTE 2.01
NEW: Support for end-2019 hardware

[1.5.1] with RTE 2.00
FIX: 1.5.0 could enter dive mode when ambient pressure reduced during flight

[1.5.0] with RTE 1.90
FIX: Optical port timeout fixed
FIX: firmware version in logbook data
FIX: battery information in logbook data
FIX: correct main version number logbook data
FIX: fix drawing of CCR bailout profile in internal logbook

[i][1.5.3] with RTE 2.03
NEW: Support for much faster updates [b](With OSTC companion 3.2 and later)[/b][/i]

Hello,
Where can we upload OSTC Companion 3.2 ???

Link viewtopic.php?f=7&t=22012 updated a few minutes ago.

I’m pleased to report that I upgraded to 1.5.2 BETA a month ago and logged 45 dives and downloaded daily and had no issues at all. So hopefully the corrupted log file issue that myself and others experienced has been put to bed.

Hi there,
I am having trouble with the upgrade.
This is what happens:
After starting the upgrade the OSTC displays "uploading part one" as usual. As soon as the progress bar in companion reaches 60%, the display switches between the regular screen, the message "download mode enabled" and "service mode enabled".
After 15 minutes the whole things stops and I get one of two time out messages on the companion (see attached screen shots).
What do I do now?
Thanks for your help and stay healthy!
Cheers
Alex

oh, I forgot to mention: I have unit no 198 and FW 1.5.1

I had that problem too. I had to reconnect (several times) and start the install again. Eventually it ran through. I am still convinced HW should never have switched to BT. USB is much more reliable.

I tried 5 times so far. Will keep going....

swissdiving wrote: ↑Saturday 21. March 2020, 17:07 I had that problem too. I had to reconnect (several times) and start the install again. Eventually it ran through. I am still convinced HW should never have switched to BT. USB is much more reliable.

Completely agree with this, or it would be perfect if HW gave the choice of connecting the TC with BT or Usb when ordering, personally I have a TC in Usb and I am not at all ready to do so change against a TC with BT

Well I still love the OSTC and its BT connectivity since it makes sure there is no interface that can cause a leakage. And I have had my share of flooded dive computers...
Cheers
Alex

And now it worked. As swissdiving commented, you have to try numerous times which in my case was about 10 times.

cheers
Alex

Well Alex, I have had a 2N for 8 years now and NEVER had any leakag issues...

ebertalex wrote: ↑Sunday 22. March 2020, 11:37 Well I still love the OSTC and its BT connectivity since it makes sure there is no interface that can cause a leakage. And I have had my share of flooded dive computers...
Cheers
Alex

Try 10 times to update, it's good if you're patient, with my Usb connection once is enough!
As for the flooding of a TC the BT is a very good reason and I think that is the reason why HW switched to the BT,
But you should know that the flooding of a TC is 99% the fault of its user!
So with the normal care and maintenance of your TC it should not happen or only 1%!
It's been 7 years since I make updates in 1 time from v_1.0 to v_309_beta3 and without leaking!
Good luck !

ebertalex wrote: ↑Saturday 21. March 2020, 11:10 Hi there,
I am having trouble with the upgrade.
This is what happens:

Try with the most recent 3.2.1 Companion, please: viewtopic.php?f=7&t=22012

Regards,
Matthias

Matthias, I did use the most recent companion...

Hallo,

meinen OSTC4 habe ich jetzt auch auf 1.5.3 gebracht. Update lief gut mit dem neuen Companion. Tipp: Erst die Daten auf den Rechner holen, dann W-LAN abschalten und Bluetooth aktivieren. Erst dann mit OSTC4 verbinden und Update durchführen. Mein Laptop redet mit aktiviertem W-LAN extrem instabil mit den Tauchcomputer.

Danach habe ich mal die Menüs geprüft und auch mal das gedrehte Display probiert. Fand ich nicht so toll und habe es dann zurückgestellt. Jetzt gingen die Menüs nicht mehr richtig. Ein Menü war leer (keine Anzeige), dennoch konnten die Felder angewählt werden und vereinzelt tauchte wieder Text auf. Dann stellte ich fest, dass im benachbarten Menü (voll angezeigt) das untere Feld nicht erreichbar war (im Menü zuvor gibt es einen Eintrag weniger). Anscheinend glaubte sich der Rechner im Nachbarmenü. Klar wurde das, als ich mich zum Reset entschlossen habe. Das gelang nur mit Austricksen im Nachbarmenü (das Untermenü war OK). Nach dem Reset ist alles wieder OK. Ich denke daher, es ist ein kleiner Bug, der nicht dringend ist. Es wird ja wohl keiner mal kurz vorm Tauchgang, die Drehung mal ausprobieren wollen. Guckt bitte mal bei passender Gelegenheit in den Code.

Danke.

Hallo,

Danke für die gute Fehlerbeschreibung. Das sollte auf jeden Fall zu finden sein.

Gruß,
Matthias