forum.heinrichsweikamp.com

Hi,

Is https://hwdiving.com an official Heinrichs-Weikamp web site ?

The hwos_tech_changelog.txt included in the zip indicates :
[3.30]
MD5: 8316baf84e49e5f8e87b3a2dfc43f435
BUGFIX: After a power-on reset, some hardware versions would enter divemode delayed for the first dive

Description of 3.29 ...

Hi Chris,

Could you explain what you mean ?

Regards.

Marcomet : are you sure your computer is connected to COM5 and not to another COM port ? Have a look to the Windows peripheral panel.

jb2cool : yes, this USB port is the only way to update the firmware and download dive profiles since there is no Bluetooth on this unit.

Regards.

You got it !

Hi Marc,

In 2015 I had an OSTC 3 S/N 3999, it has a USB connection but no Bluetooth. Yours being S/N 3090, I guess it is the same model. So try to update the firmware through UCB.

Kind regards.

Hi Matthias,

This error was reported several times once at the surface today. The surface pressure reported by the OSTC (found in the subsurface file is 1016 hPa :

<surface pressure='1.016 bar' />

This gives a PO2 = 0.213 bar...

Regards.

Hi,

Yes, I saw theses alerts on the OSTC screen. During the last dives with the threshold set to 0.16 bar, no such warning occurred. I set it to 0.21 bar again for the next dives, to see if the problem comes again.

Kind regards.

Hi,

For a few days I dive with air in open circuit using release 3.26, and I encountered several PO2 alerts close to the surface. The threshold was initially set to 0.21 (several alerts), then to 0.20 (several alerts again) and finally to 0.15 (one alert). The surface pressure reported by my OSTC ...

A new firmware 3.26 is available here : https://heinrichsweikamp.com/index.php/ ... /firmwares.

Regards.

Hi Leovank,

A similar feature has existed for a long time, this is the fTTS (future time to surface). It is described int he user's manual in §4.4.1, page 19.

Kind regards.

Hum, this never happened to me (about 1000 dives with an OSTC).

Kind regards.

Hi Matthias,

Beta release 3.25 loaded and explored (on surface), looks better for me.

Kind regards.

Hi,

The firmware file names (NNN_LL_2_tr_ostc3_firmware.hex or NNN_LL_3_cr_ostc3_firmware.hex) do not clearly reflect the OSTC to which a particular file applies. Could this be changed in the future ?

Kind regards.

Bonjour,

Ce serait vraiment dommage de vous passer de vos OSTC, je vous conseille de consulter ce post qui traite d'un sujet similaire : viewtopic.php?t=22536.

Bien cordialement.

Hi,

Well, I don't understand all the subtleties of your exchanges (Korinthenkacker-Unterteilung ?) but for me, with a salinity value from 0 to 4% the pressure to depth conversion is largely accurate enough, since not used for deco computation.

Kind regards.

Hi,

Last month a friend of mine got his computer back from HW with the firmware upgraded to 3.22, but this firmware is not available for download. Any reason ?

Kind regards.

Thanks a lot Matthias !

Hi,

What are the differences between OSTC 2 version 2017 and version 2022 ? Pictures look similar...

Is serial number 18835 2017 or 2022 ?

Thanks a lot.

Hi,

I replied to your other post on July 16th : viewtopic.php?p=24336#p24336.

Regards.

Hi,

I remember my first OSTC 3 (#3999) had no Blutettoth, on USB. What is the serial number of yours ?

By the way, what's the meaning of "Can my car not have bluetooth?" ?

Kind regards.

Hi,

"my OSTC 3 allows BT data transmission but only USB" : could you clarify ?

"Planner does not see the machine and does not allow me to change the settings (version 2.7.5 for mac)" : you should better post this on a Planner forum.

Kind regards.

Hello,

I recently saw this once on my OSTC 2, running hwOS 3.21. I don't remember the full context, it was during a shallow open circuit dive ; entering a menu solved the trouble.

16 dives later in CCR mode, did not see it any more...

Kind regards.

Hi,

I had exactly the same trouble two years ago. HW concluded the pressure sensor was faulty.

Kind regards.

Hi,

As fa as I know my own OSTC, it's not possible to insert a dive into the logbook. I guess it would be a lot of work to add this feature, for a very marginal benefit...

Regards.

No, it's not normal. If you are using an USB port, it is probably not powerful enough, try a 2 A mains charger.

Regards.