forum.heinrichsweikamp.com

Ciao swissdiving
Grazie per la risposta.
La mia domanda era se fosse possibile aggiungere la funzione di calcolo automatico della ratio deco come utilizzata da GUE oppure UTD.
Potrebbe diventare una buona soluzione di backup per chi utilizza questo metodo decompressivo.
Grazie in anticipo per le risposte.

@Our Italian natives,
Can one of you translate/answer styledivings question?

I've asked the question before

read.php?2,9537

I understand that having automated set point changes are not currently planned at this point in time however, if it's of any good use I'd like to reiterate my desire to have this feature added.

It reduces my task loading on a regular basis. I tend to do a large number of dives comming down on shot lines (or almost vertical anchors) often with current.

Thanks

D

Hi Swissdiving
Thanks for the reply.
I try to repeat the question using the translator.

My question was whether it was possible to add the function of automatic calculation of the ratio deco as used by GUE or UTD.

May become a good backup solution for those who use this method decompression.

Thanks in advance for your answers.

stylediving Wrote:
-------------------------------------------------------
> Hi Swissdiving
> Thanks for the reply.
> I try to repeat the question using the
> translator.
>
> My question was whether it was possible to add the
> function of automatic calculation of the ratio
> deco as used by GUE or UTD.
>
> May become a good backup solution for those who
> use this method decompression.
>
> Thanks in advance for your answers.


Hi Marco,

The OSTC is following a well tested algorithm. Deco ratio is, to say the least, an untested common sense model that tends to work wellwith certain standard gases at certain standard depths. Vary any and it doesn't actually work well.

So, to answer your question. It's unlikely that reatio deco wil be implemented on the OSTC (unless you wish to code your own firmware)

Regards,

D

heinrichsweikamp Wrote:
-------------------------------------------------------
>
> Missing texts... Sorry for that. If some native
> speaker can replace the English Expressions in the
> attached file I can upload a working version in
> French.
>
> Text 61,229,110,111,229,230,231,232 TXT_DIL_C,
> TXT_DIL5 need a translation update...
>
> regards and thanks,
> Matthias


Hi Matthias,

I've been through your list of translations to be done and actually most of them are already fine in the file you attached:

61: "Diviseur Debug" for "Divisor Debug" is already ok
110 and 111: "Menu SetPoint CCR" for "CCR SetPoint Menu" is already ok
232: "Diluent" for "Diluent" is already ok
TXT_DIL_C: "D" for "D" is already ok
TXT_DIL5: "Dil.#" for "Dil.#" is already ok

The ones to change:

229: I propose to use "Réglage Diluent" for "Diluent Setup"
230: I propose to use "Réglage SetPoint" for "Setpoint Setup"
231: I propose to use "Liste des Diluents" for "Dil. Setup - Gaslist". We currently have "Liste des Gaz:" for the 106 "Gas Setup - Gaslist", but actually the ":" should not be there in the french version to be consistent with the english one.

I uploaded the file with these modifications (including removing the ":" for n 106).

Thanks,

Matthieu

Hi Matthieu,

Thanks. Four last lines (For the next beta):

[pre]
TCODE .40, .35, "S.StopLength[ s]" ;199 S.StopLength[ s] (CF70: Safety Stop Duration [ s])
TCODE .40, .35, "S.StopStart [ m]" ;200 S.StopStart [m] (CF71: Safety Stop Start Depth [m])
TCODE .40, .35, "S.StopEnd [ m]" ;201 S.StopEnd [m] (CF72: Safety Stop End Depth [m])
TCODE .40, .35, "S.StopReset [ m]" ;202 S.StopReset [m] (CF73: Safety Stop Reset Depth [m])
[/pre]

Please use "diluant" in french.

Stephane Wrote:
-------------------------------------------------------
> Please use "diluant" in french.

Sorry for the spelling error ! Here are the translations I propose for the other four lines (remove the space in [ s]):
[pre]
TCODE .40, .35, "Durée P.Sécu[ s]" ;199 S.StopLength[ s] (CF70: Safety Stop Duration [ s])
TCODE .40, .35, "Début P.Sécu[m]" ;200 S.StopStart [m] (CF71: Safety Stop Start Depth [m])
TCODE .40, .35, "Fin P.Sécu [m]" ;201 S.StopEnd [m] (CF72: Safety Stop End Depth [m])
TCODE .40, .35, "RaZ P.Sécu [m]" ;202 S.StopReset [m] (CF73: Safety Stop Reset Depth [m])

[/pre]

You can find attached the updated file which also correct "diluent" to "diluant".

Matthieu

Oh no... 4 CF's for the safety-stop feature ;-(
Matthias: Don't you think you could at least skip the Stop Reset line and set it to 10m fix!?

Or just merge CF65 and CF70 : CF70=0s is the same as CF65=False...

Iglooz Wrote:
-------------------------------------------------------
> Or just merge CF65 and CF70 : CF70=0s is the same
> as CF65=False...

Agree

Iglooz Wrote:
-------------------------------------------------------
> Or just merge CF65 and CF70 : CF70=0s is the same
> as CF65=False...

Good idea!

@Matthias,
is the adation of the diluent gasses to the oc gasses planned with the next beta?

Regards
Rob

Posted by: Iglooz ()
Or just merge CF65 and CF70 : CF70=0s is the same as CF65=False...

I agree, it does make sense.
Vassilis

tiefunten Wrote:
> Matthias: Don't you think you could at least skip
> the Stop Reset line and set it to 10m fix!?

We really want this topic out of the discussion, I think everybody is able to configure it's safety stop now

regards,
Matthias

Well, at least when this feature is set to "off" per default, it is ok for me...

It's still nonsense, I think.

Jo

P.S. Someone remember the "Anti-Diveguide" feature our missing user "Solodiver" requested once? Would such feature be implemented today?

:)o

JoStein Wrote:
-------------------------------------------------------
> our missing user "Solodiver" requested once?

Solodiver got lost?

I'm looking forward to the next beta and i'm happy too if the safety stopp discussion will end. I'm sure that every OSTC-User will do a lot of OC-, CCR, Tec-, Rec-diving with no harm at all...