forum.heinrichsweikamp.com

Hello,
I have a new OSTC sport since end of January 2020.
I try to upgrade the firmware from 10.63 to latest 10.64 through subsurface, I run Windows 10 family 1909 (french) and Subsurface 4.9.3.

When I go to File -> Change settings on dive computer -> Connection via bluetooth -> Scan -> Save: it find the OSTCs 21584 (00:80:25:E0:56:48).
When I clic on "Upgrade Firmware " and chose the file "v10_64_FR_IT_ostc_sport_firmware.hex", upgrade fail with message in the bottom of the windows: "Erreur: La mise à jour du firmware a échoué !", nothing appear on the progress bar

If I clic on "Récupérer les détails disponibles" it works (100% on the progress bar) but the model is view as OSTC Plus (not Sport) and some infos are not corrects, as the language which is English in place of French in the OSTC.
If I change the language to french and send it to the OSTC (clic on "Enregistrer les modifications sur le périphérique") it fail too with message "Erreur : échec !" and nothing appear on the progress bar
I suspect that Subsurface can read but not write on the OSTC Sport, or do I make something wrong?
Any idea?

Thanks for helping.

Bonjour,

Avez-vous essayé de reprogrammer le firmware avec OSTC Companion ? Téléchargement ici : https://heinrichsweikamp.com/index.php/service/software. J'ai moi-même des problèmes avec Subsurface, beaucoup moins avec OSTC Companion.

D'autre part, concernant Subsurface :
- Il indique toujours English comme langue, inutile d'essayer de la changer car cela n'a aucun incidence sur la langue utilisée par l'OSTC.
- Le modèle indiqué est toujours OSTC 2, pour toute la famille 2/3/Sport/Plus, ça n'a pas d'incidence sur les échanges.

Un autre logiciel permet de modifier les paramètre de l'OSTC, il s'agit de HWOS Config. Téléchargement au mêm endroit qu'OSTC Companion.

Amicalement.

Merci pour votre réponse, je vais essayer l'autre soft.
Dommage quand même que l'option prévue dans Subsurface ne soit pas opérationnelle.

Hi,

Tried Subsurface (on linux), HWOS (android) and finally OSTC Companion (windows 10) and cannot upgrade from v3.09 beta 2 after trying multiple times on each program including removing and replacing battery, reset default settings etc.

cyberdiamond wrote: 30 Apr 2020, 10:35 Tried Subsurface (on linux), HWOS (android) and finally OSTC Companion (windows 10) and cannot upgrade from v3.09 beta 2 after trying multiple times on each program including removing and replacing battery, reset default settings etc.

Any error messages shown in the OSTC or in the various apps that might help?

Is this an USB-OSTC3?

regards,
Matthias

Bonjour,
Avec OSTC companion, l'upgrade a réussi chez moi.
Merci

I did this same update from 10.63 to 10.64 using Subsurface 4.9.3 and it worked fine for me. I’m using Linux though in case that makes a difference

heinrichsweikamp wrote: 30 Apr 2020, 17:04

cyberdiamond wrote: 30 Apr 2020, 10:35 Tried Subsurface (on linux), HWOS (android) and finally OSTC Companion (windows 10) and cannot upgrade from v3.09 beta 2 after trying multiple times on each program including removing and replacing battery, reset default settings etc.

Any error messages shown in the OSTC or in the various apps that might help?

Is this an USB-OSTC3?

regards,
Matthias

I actually meant to post in the 3.10 firmware thread

It is a OSTC3+ bluetooth

Message from companion is:

09:02:24.312 OSTC hwOS (USB) selected.
09:02:29.671 OSTC hwOS (Bluetooth) selected.
09:02:33.500 Upgrading firmware...
09:02:56.509 Loading firmware.
09:03:01.131 Erasing Firmware.
09:03:02.256 Uploading firmware.
09:03:03.990 Bad message reply (1)
09:03:04.005 Error: Bad message reply (1)

Then restart bluetooth from the OSTC3 and try again:

09:06:11.435 Upgrading firmware...
09:06:18.917 Loading firmware.
09:06:25.728 Assert: _connectMode != SERVICE_MODE
09:06:25.780 Error: Assert: _connectMode != SERVICE_MODE

I have seen error message on the OSTC3 itself when I kept trying with HWOS Config from Android.
Which was something like Read timeout /or RX timout in red on the screen.

It would get anywhere from 0% to about 8% then the green light on the side of the OSTC would start to flash when it failed.

Hi,

can you give it a try with the command line tools from libdivecomputer? They can be found here:

http://www.libdivecomputer.org/builds/stable/

usage is:

dctool -vv -l <logfile-filename> -f ostc3 fwupdate -f <firmware-filename> -t bluetooth <BT-MAC>

example:

dctool -vv -l dctool.log -f ostc3 fwupdate -f firmwarefile.hex -t bluetooth 008025ce365b

It will also produce a very detailed log (dctool.log in above example).

BR
Ralph

Ok did 3 runs with dctool see attachments.

ran with command:

[steve@t490 libdivecomputer]$ ./dctool -vv -l dctoolfwtest01.txt -f ostc3 fwupdate -f ../../Gear/Computers/Heinrich\ Weikamp/firmware/v_310_hwos_firmware/310_EN_DE_3_cr_ostc3_firmware.hex -t bluetooth 00:80:25:49:D6:DF

At the end of the 1st and 3rd run had on the ostc3+ screen in red:
Data RX timeout
then:
Parameter Error

The second run looks like the Bluetooth port wasn't read correctly so reset it all again before the 3rd test which looks like it got a tiny bit further than the first but not much before failing again.

Cheers,
Steve

Thanks a lot! No. 2 indeed failed due to BT not being ready, and no. 1 & 3 failed due to the same reason, but i'll need to have a deeper look into the logs before i have an idea what it is...

Can you additionally give me the Hardware ID of your OSTC, it's at Main Menu -> Settings -> Information -> more

Hardware ID: 1A-80-F2

cyberdiamond wrote: 01 May 2020, 01:40 I actually meant to post in the 3.10 firmware thread

It is a OSTC3+ bluetooth

You did post it to the 3.10 thread, we moved this here because this is not an issue with the 3.10 but with the version you currently have installed.

We have a low-level bootloader option for recovering a firmware out of unexpected issues. I'll email you the instructions right now. That should fix this (You'll need a Windows-PC ).

regards,
Matthias

After installing the 3.10, please check the hardware string again. There will be an additional byte now and I'm pretty sure it will be "05" and not "06". Then, the rare and tricky issue you encountered is understood and was fixed in the 3.10.

Just to add, here is a decoder for the hardware string: https://bitbucket.org/heinrichsweikamp/ ... /src/Docu/ (ostc_hardware_string.xlsx). Your OSTC 3 with hardware 1A-80-F2 results in this:
Which looks perfectly fine for an OSTC3 approx. made in 2014 or 2015

Regards,
Matthias

That worked and it is fixed now.
Thanks,
Steve