hwOS4: New Firmware 1.6.2 with RTE 3.10

[heinrichsweikamp3]

ENGLISH below.

Hallo,

Die neue Firmware 1.6.2 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.)

Wir emfehlen ein Update über die Apps OSTConf (iOS) oder HWOS Config (Android)

Videos:
OSTConf: https://www.facebook.com/17049381164554 ... 339989145/
HWOS Config: https://www.facebook.com/17049381164554 ... 561539708/

Folgende Änderungen und Neuerungen gibt es seit der V 1.5.9:
[1.6.2] with RTE 3.10
CHG: Allow dates >2022 to be set in the menu
NEW: Support for DiveO2 Solid-State-Oxygen sensor
NEW: Sensor autodetect allows combination of one solid-state sensor and up to two analog sensors
FIX: Bugfix compass bearing: In previous version an invalid value was set in case the bearing was set
without compass calibration. Rootcause was that the bearing -1 is received in case the compase is
not calibrated. This has been fixed by setting bearing to 0 (360) in that case.
NEW: Extension scrubber time: In previous version only one scrubber timer was available. After movement
of scrubber timer menu menu space became available allowing to upgrade the functionality to support
two scrubbers. To make it easier to identify combination ID to used scrubber the date of the last usage
of the scrubber timer has been added.
NEW: Added new info page for extended sensor data: The new source file may be used to create a
information page individual for every smart sensor type. The DiveO2 sensor is the first supported sensor
NEW: Show saturation in large font view: In case the DecoTTS custom view is active then the saturation
will be displayed if the diver is close to the surface (TTS < 1 minute).
FIX: invalid setpoint (0.0) was used after switch from CCR to extra (OC) gas
NEW: Add mini compass with marker declination indication selectable in dive mode
NEW: Enable start dive in Big font display: The diver had to manually switch to the big font view in dive
mode. By selecting the big font view as default view in the custom menu the BF view will now be shown
from the start of the dive. In order to have a qucker access to the settings menu, the settings menu
has been added to the quick menu selection. The settings menu will then also be left to the BF view.
NEW: Added button lock after wakeup in surface mode: During setup of diveequipment the OSTC4
is sometimes operated unintended (e.g. while equipping the jaket). To avoid this it is now possible
to activate a button lock in the button lock sensitivity menu. The OSTC4 will then wakeup as usual
but if the diver wants to oerate the menus he has to press the buttons in a certain order. The button
to be pressed is indicated by a blue bar. The button lock is deactivated in dive mode.
NEW: Quit simualted dives after the dive time set in the SIM tab.
NEW: After a firmware update, use the factory settings for button sensitivity if these exist, the
default settings otherwise. The factory settings for the buttons can be updated in the System menu /
Reset menu / Maintenance / 'Store button factory defaults'.

[1.6.0] mit RTE 2.09
FIX: Automatisches Umschalten auf o2-Sensor-Ansicht:
Im Oberflächenmodus schaltet die benutzerdefinierte Ansicht automatisch auf die O2-Sensor-Ansicht um, wenn der OSTC4 auf
Sensor-Modus eingestellt ist. Dies geschah auch dann, wenn die O2-Sensor-Ansicht deaktiviert war. Dies führte zu einer automatischen Umschaltung
auf z.B. Kompass, was nicht beabsichtigt war. In der neuen Version ist die automatische Umschaltung deaktiviert, wenn
die benutzerdefinierte Ansicht deaktiviert ist
CHG: Automatische Setpoints während des Aufstiegs ignorieren:
In der bisherigen Version wurden Setpoint, die für den Abstieg konfiguriert wurden, bei der
für die Deko-Berechnung berücksichtigt, wenn ein oder mehrere zusätzliche Diluent Gase aktiviert wurden. Dieses Verfahren entspricht
nicht der üblichen Vorgehensweise, den Setpoint bis zum Ende des Tauchgangs hoch zu halten, um die Dekozeit zu verkürzen.
In der neuen Implementierung geht der OSTC 4 davon aus, dass der aktuelle Setpoint bis zum Ende des Tauchgangs verwendet wird.
FIX: Bugfix: Warnung bei niedrigem ppO2 im Bailout-Modus:
Der Code hat unterschiedliche Quellen für die Tauchgangseinstellungen (real und simuliert). Der ppo2 Berechnungscode verwendete
den Pointer auf die reale Struktur. Als Ergebnis trat im Simulationsmodus ein Fehler auf, der durch die ppo2
Berechnung, die nicht wusste, dass ein Bailout stattgefunden hat (weil die reale Struktur referenziert wurde
statt auf die des Simulators verwiesen wurde). Das Problem wurde durch die Verwendung des "stateUsed"-Pointers behoben, der
auf die aktuell verwendete Struktur verweist.
FIX: Warnung bei niedrigem ppO2-Wert im Bailout-Modus:
Der Code hat unterschiedliche Quellen für Tauchgänge (real und simuliert). Der ppo2-Berechnungscode verwendet den
Zeiger auf die reale Struktur. Als Ergebnis trat im Simulationsmodus ein Fehler auf, der durch die ppo2-Berechnung
die nicht wusste, dass ein Bailout stattgefunden hat (weil die reale Struktur anstelle der Simulatorstruktur referenziert wurde).
Simulator referenziert). Das Problem wurde durch die Verwendung des "stateUsed" Zeigers behoben, der sich auf die
Struktur verweist, die gerade verwendet wird.
FIX: Ereignis "Batterieladung abgeschlossen":
In der vorherigen Version konnte es vorkommen, dass der Ladezustand des Akkus auf 100% gesetzt wurde, obwohl der Akku
nicht vollständig geladen war. Die Ursache dafür war, dass das externe Ladegerät-IC manchmal Fertigstellung signalisierte, weil
z.B. die Verbindung zwischen Ladegerät und OSTC innerhalb eines kurzen Zeitfensters unterbrochen wird.
Dies kann passieren, während der Benutzer versucht, den OSTC in eine gute Ladeposition zu bringen. Um dies zu vermeiden,
prüft die Zustandsmaschine nun jedes Mal die Spannung auf einen gültigen Ladebereich, bevor ein Ladeende signalisiert wird.


ENGLISH:

Hello,

The new firmware 1.6.2 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).


To update, simply use one of our two apps OSTConf for iOS or HWOS Config for Android.
OSTConf: https://www.facebook.com/17049381164554 ... 339989145/
HWOS Config: https://www.facebook.com/17049381164554 ... 561539708/

The following changes have been made since V 1.5.9:
[1.6.2] with RTE 3.10
CHG: Allow dates >2022 to be set in the menu
NEW: Support for DiveO2 Solid-State-Oxygen sensor
NEW: Sensor autodetect allows combination of one solid-state sensor and up to two analog sensors
FIX: Bugfix compass bearing: In previous version an invalid value was set in case the bearing was set
without compass calibration. Rootcause was that the bearing -1 is received in case the compase is
not calibrated. This has been fixed by setting bearing to 0 (360) in that case.
NEW: Extension scrubber time: In previous version only one scrubber timer was available. After movement
of scrubber timer menu menu space became available allowing to upgrade the functionality to support
two scrubbers. To make it easier to identify combination ID to used scrubber the date of the last usage
of the scrubber timer has been added.
NEW: Added new info page for extended sensor data: The new source file may be used to create a
information page individual for every smart sensor type. The DiveO2 sensor is the first supported sensor
NEW: Show saturation in large font view: In case the DecoTTS custom view is active then the saturation
will be displayed if the diver is close to the surface (TTS < 1 minute).
FIX: invalid setpoint (0.0) was used after switch from CCR to extra (OC) gas
NEW: Add mini compass with marker declination indication selectable in dive mode
NEW: Enable start dive in Big font display: The diver had to manually switch to the big font view in dive
mode. By selecting the big font view as default view in the custom menu the BF view will now be shown
from the start of the dive. In order to have a qucker access to the settings menu, the settings menu
has been added to the quick menu selection. The settings menu will then also be left to the BF view.
NEW: Added button lock after wakeup in surface mode: During setup of diveequipment the OSTC4
is sometimes operated unintended (e.g. while equipping the jaket). To avoid this it is now possible
to activate a button lock in the button lock sensitivity menu. The OSTC4 will then wakeup as usual
but if the diver wants to oerate the menus he has to press the buttons in a certain order. The button
to be pressed is indicated by a blue bar. The button lock is deactivated in dive mode.
NEW: Quit simualted dives after the dive time set in the SIM tab.
NEW: After a firmware update, use the factory settings for button sensitivity if these exist, the
default settings otherwise. The factory settings for the buttons can be updated in the System menu /
Reset menu / Maintenance / 'Store button factory defaults'.

[1.6.0] with RTE 2.09
FIX: automatic switch to o2 sensor custom view:
In surface mode the custom view will automatically switch to the o2 sensor view in case the OSTC4 is set to
sensor mode. This was also done in case the o2 sensor view was deactivated. This lead to a automatic switch
to e.g. compass what was not intended. In the new version the automatic switching is deactivated in case
the custom view is deactivated
CHG: Ignore automatic setpoint changes during ascend:
In the previous version setpoint changes which have been configured for descending were considered
for deco calculation in case one or more additional diluents have been activated. This procedure does
not fit to the common way to keep setpoint high till end of the dive in order to get rid of the deco time.
In the new implementation the OSTC 4 assumes that the current setpoint is used till the end of the dive.
FIX: low ppO2 warning in bailout mode:
the code has different sources for divesettings (real and simulated). The ppo2 calculation code used the
pointer to the real structure. As result in simulation mode an error occured caused by the ppo2 calculation
which was not aware that a bailout happened (because the real structure was references instead of the
simulator ones). The problem has been fixed by using the "stateUsed" pointer which is refering to the
structure currenty in use.
FIX: Battery charge complete event:
In previous version it could happen that the battery charge state was set to 100% even the battery was
not completly charged. Rootcause was that the external charger IC signals sometimes completion because
e.g. the connection between charger unit and OSTC is disconnected within a short time slot. This may
happen while the user is trying to get the OSTC in a good charging position. To avoid this the state
machine now checks the voltage everytime for valid charging complete range before a charging complete
is signaled.

[swissdiving]

Update klappt nicht mit HWOS config und auch nicht mit Subsurface.
Verbindung klappt, nach 6% bricht das update up mit Bluetooth ausgeschaltet auf dem OSTC4

Divelog download funktioniert

[Rob]

Von welcher Firmware auf welche versucht ihr es?

Whhat ist the current installed firmware?

Regards
Rob

[swissdiving]

1.6.0 --> 1.6.2

[Rob]

for update problems wit hHWOSConfig, please see

OSTC Tools for Windows - HWOS Config for Android

Regards
Rob

[OceanDiver]

Same problem while trying to update firmware 1.60 to 1.62 on OSTC 4 #125 and #478 with current version of HWOS config:
Bluetooth disconnecting randomly somewhere after 23% up to 96% of firmware data transferred (bluetooth automatically switched "off" while firmware upload)). Tried on both computers more than 15 times each: always disconnection of bluetooth (bluetooth switched "off" while firmware upload)
Without starting firmware update bluetooth remains "on" for long time!
Computers are charged to 100%. After each of the failed update runs the computer was cold-restarted.
What's the problem?

[swissdiving]

I wouldn't think it is a HWOS Config issue. Same problem with Subsurface.

[Rob]

I think I have a solution. at least with my OSTC 4 it's working.
I will post a new android APK in the hwosconfig thread by this evening.

[swissdiving]

FW update successful from 1.6.0 to 1.6.2 on slow switch

FW update on different hardware from 1.5.9 to 1.6.2 successful on slow switch. But it took 2 goes plus separate upgrade of RTE.

Testing on weekend

[swissdiving]

CCR Test today of 1.6.2
Good
However.
I configured 2 scrubbers because I dive a Sidewinder. Both to 240 Minutes configured.
On completion of the dive only one scrubber had counted down the dive time.

The request for two scrubbers was for rebreathers such as Revo and Sidewinder who have two scrubbers. So what we need is for both scrubbers to count down as we may choose to replace the lime only in one scrubber after a number of dives. So when time is set on both scrubbers the time needs to count down on both scrubbers.

Second point, in the Scrubber menu the dive time did not record.

Otherwise all good (though I haven't tested the other features yet).

[mikeller]

CCR Test today of 1.6.2
[...]

Happy to help with this. CCR diver myself, and have been doing some improvements on the OSTC4 firmware in the past months.
But can I propose that we open a new topic, or use Updated - Feature requests ccr ostc4 to discuss the detailed requirements for this? The release announcement does not seem to be the best place for it.

[swissdiving]

There already is a feature request thread and the discussion in this thread is about what works and what doesn't work in this release specifically .

[Nextstagegauges]

Is the pinout available for the S8 cable to make use of the DiveO2 sensor? I'm buying one and I assume I need to use a few of the unused wires in the S8 cable to hook it up.

And just to confirm, any OSTC4 with an S8 connector is capable of driving the DiveO2 sensor, correct?

[heinrichsweikamp]

Continue here: viewtopic.php?t=22469