forum.heinrichsweikamp.com

Hello Reiner,

sounds like an usefull function. I am interested in some more details how you use it and what would be your expectations.
Does the function consider one bailout gas or all gases which are in the bailout list and marked as "deco"?

=> Will the answer "You most likely will get out" be ...

Hallo Tom,

hat das Display beim Reset kurz geflackert? Alternativ könntest Du mal die Batterie rausnehmen und nachmessen wie hoch die Spannung ist. Dann fällt der Akku als eventuelle Fehlerquelle schon mal weg.

Viele Grüße,
Thorsten

Hi Alex,

what tool did you use for the update? Was the fast mode activated? I assume you tried to update from the last offical release?
I just did the update using an old OSTC4 HW and the OSTC companion SW. Worked without problems.

KR,
Thorsten

Hi Riku,

it looks like for some reason the bluetooth modul is offline. If I remember correct even if it is not communicating with the OSTC it should be visible for your computer. But it is not => I guess a hardware problem. I asked for the voltage because I hoped that it would be to low but 3.8V is ...

Hi Riku,

is the voltage of the battery shown? If you have not used the OSTC for a long time it could be extrem low.

Kind regards,
Thorsten

Hi Humberto,

I tried to reproduce it with my OSTC5 and have to agree. Even if you missed one half turn with all your movements the measurement points of the axis should be matched. By the way: The visualization is just a guide to support the calibration. In the background the OSTC is measuring all ...

Hi Humberto,

I had a look at the video and it looks like you missed one direction while turning the OSTC (only half turn) you see that the pitch is 50%.
You can do it by try and error => start turning the OSTC and check if the bars are changing to green. If they do it is the correct axis. If not ...

I used Polypropylen because the material should be flexible. TPU should be fine as well.

Hi,

you may also try this one if you want :-)

https://www.thingiverse.com/thing:7112082

Have fun,
Thorsten

Hi Sven,

looks like you have connected the sensor directly to the OSTC? I think that does not work well because the OSTC4 output voltage does not match the needed input voltage of the sensor. The sensor responds but it is operated out of specification. HW offers a multiplexer board which takes care ...

Hi Fabio,

there is an activation condition for the timer: The dive needs to be longer than 15 minutes (to avoid that the slow exit is shown in an early dive situation where you would prefer to have the normal ascend speed).

I have just tried the 6m ascend in the sumulator and was wondering why it ...

Hello Teun,

thank you for the version information. The missing graph data is pointing to a problem during storing the data. As posted last time a very low battery could be an issue.
Looking for different root causes: Was there a special situation / handling during the last dives? Did you, for ...

Hello Teun,

if I understood correct then the log display at the OSTC is fine => no corrupted data graphs? In that case maybe something goes wrong during the data transfer to subsurface. Did you update the OSTC or subsurface SW before the problem showed up? What versions are you using?

Kind regards ...

Having Ralphs explanations in mind the next firmware version will have some updates of the VPM function. Not regarding the algorithm itself but with regard to the output data usage.
The planner will freeze the worst case deco table without simulating an ascent => The values provided will look like ...

Well, it is like it is written in the manual: a deco forecast. If there is no deco time then the result is zero.
If a futureTTS considering the time needed to get to the surface would be added (use case no deco pending) then the behavior compared to the visualization of the current deco would be ...

Well from decompression calculation point of view the behavior is correct. If the exposure of gases is not adding decompression time at the depth you are (15m in this case) then the answer to the question where is the diver in 5 minutes is: "on the surface".
But I see your point: when I am on 15 ...

Hi Humberto,

I guess you had some deco obligation during the dive? As you metioned correct otherwise you would see the NDL.
I think what you see is the situation when you have less than 1 minute deco time. In that case no stops are visible but the TTS is still displayed because the deco seconds ...

Sounds like an interesting idea. 0-5m is quite slow => we will have to improve the speed measurement to avoid that the OSTC turns into a disco maschine in case the diver moves his arm but that should not be a big problem.

I will keep you updated once the feature is implemented

Hi,
I had a look at the download link but could find only one divelog (the SW). Could you add the the OSTC dive in a separate file?

Cheers,
Thorsten

Hi Teunn,

could you provide some more details regarding the corrupt data (peaks in log graph, not data at all etc.)? I assume the depth data is not visualized as graph (in OSTC log view) but the generic time / depth information are available?
The download of dives is still possible, meaning that ...

Hallo Pimi,

ja da gab es einen Bug. Der sollte aber in der 1.6.5 gehoben sein:

[1.6.5] with RTE 3.20
FIX: Die 1.6.4 konnte zu Problemen führen, wenn die Standardansicht "Große Schrift" auf "Dekoplan" voreingestellt war.
Der Menüeintrag "Große Schrift" in SYS2 konnte den OSTC4 im Oberflächenmodus ...

Hi,

the multiplexer support is part of the last released software (1.6.5 / 3.20). I attached some pictures showing my upgraded Habanero. All you need is an adapter case for the PCB (in this cases 3D printed). Beside the 4 pin connectors you can see a jack plug which is for legacy sensors. Of course ...

Hallo Christoph,

nur um sicher zu gehen, das wir die selbe Option meinen im Anhang ein Bild von dem Harken, der deaktiviert sein sollte.

Leider fällt mir ansonsten nichts mehr ein.

Viele Grüße,
Thorsten

... mir ist noch was eingefallen:
Im OSTC Companion die Option "Schnelle Aktualisierung aktivieren wenn unterstützt" deaktiviren, falls diese gesetzt ist.

Viel Erfolg,
Thorsten

Hallo Christoph,

am Updateverlauf hat sich bei den neuen Versionen nichts geändert => wenn es schon mal bei Dir geklppt hat sollte es das auch wieder tun.
Was immer wieder zu Problemen führt sind die Energysparotionen von Geräten, deshalb sollte der OSTC4 beim Update möglichst nah am Bluetooth ...