some bugs V 1.50 ???
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
some bugs V 1.50 ???
hi
i have downloaded the 1,50 version and i am facing 2 problems. I dont mean this comes from the V1.50 as one of this problem occured a while ago and has already been adressed by other owners.
v
Clock is not stable at all i can have more than 1hour difference within 24 hours.
i thought this would have been corrected.
other problem concerns the simulator, as eventhough i have set up gas, set up MOD, the other gas such as nitrox and oxy 100% are not taken in consideration in the decoplan.
i have same deco time using air only, and using air+EAN 40, and air+EAN 40+ O².
do you have any suggestion for me?
kind regards
harold
i have downloaded the 1,50 version and i am facing 2 problems. I dont mean this comes from the V1.50 as one of this problem occured a while ago and has already been adressed by other owners.
v
Clock is not stable at all i can have more than 1hour difference within 24 hours.
i thought this would have been corrected.
other problem concerns the simulator, as eventhough i have set up gas, set up MOD, the other gas such as nitrox and oxy 100% are not taken in consideration in the decoplan.
i have same deco time using air only, and using air+EAN 40, and air+EAN 40+ O².
do you have any suggestion for me?
kind regards
harold
Re: some bugs V 1.50 ???
divingcool Wrote:
-------------------------------------------------------
> Clock is not stable at all i can have more than
> 1hour difference within 24 hours.
> i thought this would have been corrected.
i was testing clock problem with my unit (firmware 1.47)
few weeks ago.
the time is always ok during normal operation of ostc.
but if you perform any operation, which will recalculate
md sum (i.e. firmware update) then clock stops to run
and you get wrong time.
there may be other operations, which cause clock to stop.
maybe it is worth to list them in the wiki?
hope this helps.
-------------------------------------------------------
> Clock is not stable at all i can have more than
> 1hour difference within 24 hours.
> i thought this would have been corrected.
i was testing clock problem with my unit (firmware 1.47)
few weeks ago.
the time is always ok during normal operation of ostc.
but if you perform any operation, which will recalculate
md sum (i.e. firmware update) then clock stops to run
and you get wrong time.
there may be other operations, which cause clock to stop.
maybe it is worth to list them in the wiki?
hope this helps.
-
- Posts: 4465
- Joined: 13 May 2007, 18:07
Re: some bugs V 1.50 ???
Hello,
The MD2 calculations actually stop the clock for about 90 seconds. Also the bootloader. I don't think any other routine does...
regards,
Matthias
The MD2 calculations actually stop the clock for about 90 seconds. Also the bootloader. I don't think any other routine does...
regards,
Matthias
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
Hi MATTHIAS
Any ideas about my simulator decoplan problem wqith deco gas?
thanks
Any ideas about my simulator decoplan problem wqith deco gas?
thanks
-
- Posts: 4465
- Joined: 13 May 2007, 18:07
Re: some bugs V 1.50 ???
Hello,
All non-used gases de-activated in the gas setup? Simulation works fine with the 1.50, can't reproduce the described behavior, sorry.
regards,
Matthias
All non-used gases de-activated in the gas setup? Simulation works fine with the 1.50, can't reproduce the described behavior, sorry.
regards,
Matthias
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
hi Matthias
the deco gas are fully activated, but are not taken in consideration in the decoplan
i get the same results using air only and air + deco gas.
i could send pictures if you want.
i even got a bug planning an air dive at 60 m for 20 mn with 99 minutes at each stops.
thanks
harold
the deco gas are fully activated, but are not taken in consideration in the decoplan
i get the same results using air only and air + deco gas.
i could send pictures if you want.
i even got a bug planning an air dive at 60 m for 20 mn with 99 minutes at each stops.

thanks
harold
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
Hi Matthias
here are some simu of decos.
60 M
21 mn
OC BULH
GF= NO gf
MOD EAN 40 30M
MOD O² 6M
Last stop 6m
Air-EAN 40- O²
Stop mn
15m 2mn
12m 4mn
9m 6mn
6m 39mn
air
15m 2mn
12m 5mn
9m 8mn
6m 72mn
air + O²
15m 2mn
12m 5mn
9m 8mn
6m 19mn
air + ean40 same deco as air+ean40+O²
15m 2mn
12m 4mn
9m 6mn
6m 39mn
i might be wrong somewhere
can you let me know
kind regards
here are some simu of decos.
60 M
21 mn
OC BULH
GF= NO gf
MOD EAN 40 30M
MOD O² 6M
Last stop 6m
Air-EAN 40- O²
Stop mn
15m 2mn
12m 4mn
9m 6mn
6m 39mn
air
15m 2mn
12m 5mn
9m 8mn
6m 72mn
air + O²
15m 2mn
12m 5mn
9m 8mn
6m 19mn
air + ean40 same deco as air+ean40+O²
15m 2mn
12m 4mn
9m 6mn
6m 39mn
i might be wrong somewhere
can you let me know
kind regards
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
hi Matthias
can i get some kind of comments about the simu deco on previous post.
as you can see, it looks weird as deco air+o² is same as air ean40 and O².
thanks
can i get some kind of comments about the simu deco on previous post.
as you can see, it looks weird as deco air+o² is same as air ean40 and O².
thanks
-
- Posts: 4465
- Joined: 13 May 2007, 18:07
Re: some bugs V 1.50 ???
Hello,
I repeat: I do not see this behavior at our place. And all I do is use the official 1.50 with a standard OSTC.
Please check your Gas setup. Make sure to deactivate unused Gases and configure the change depth properly when using more then one gas.
21'@60m with EAN40 (ppO2=2.80 bar....) here results in:
1'@9m
5'@6m
13'@3m (Standard ZH-L16)
Compared with 21'@60m and Air:
3'@15m
5'@12m
8'@9m
18'@6m
37'@3m
regards,
Matthias
I repeat: I do not see this behavior at our place. And all I do is use the official 1.50 with a standard OSTC.
Please check your Gas setup. Make sure to deactivate unused Gases and configure the change depth properly when using more then one gas.
21'@60m with EAN40 (ppO2=2.80 bar....) here results in:
1'@9m
5'@6m
13'@3m (Standard ZH-L16)
Compared with 21'@60m and Air:
3'@15m
5'@12m
8'@9m
18'@6m
37'@3m
regards,
Matthias
Re: some bugs V 1.50 ???
Hi Matthias,
Shall 1.47 and 1.50 behave the same way?
I tried yesterday one of scenario presented by divingcool
and I got strange results (air as first gas, then ean40@30m
and o2@6m) with standard ZH-L16. I am using 1.47 at the
moment.
I can provide more details late evening.
Shall 1.47 and 1.50 behave the same way?
I tried yesterday one of scenario presented by divingcool
and I got strange results (air as first gas, then ean40@30m
and o2@6m) with standard ZH-L16. I am using 1.47 at the
moment.
I can provide more details late evening.
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
heinrichsweikamp Wrote:
-------------------------------------------------------
> Hello,
>
> I repeat: I do not see this behavior at our place.
> And all I do is use the official 1.50 with a
> standard OSTC.
>
> Please check your Gas setup. Make sure to
> deactivate unused Gases and configure the change
> depth properly when using more then one gas.
>
> 21'@60m with EAN40 (ppO2=2.80 bar....) here
> results in:
> 1'@9m
> 5'@6m
> 13'@3m (Standard ZH-L16)
>
> Compared with 21'@60m and Air:
> 3'@15m
> 5'@12m
> 8'@9m
> 18'@6m
> 37'@3m
>
> regards,
> Matthias
hi Matthias
on your example, we cannot dive at 60 m with EAN 40, PPO² is over the roof.
all unused gas are deactivated
-------------------------------------------------------
> Hello,
>
> I repeat: I do not see this behavior at our place.
> And all I do is use the official 1.50 with a
> standard OSTC.
>
> Please check your Gas setup. Make sure to
> deactivate unused Gases and configure the change
> depth properly when using more then one gas.
>
> 21'@60m with EAN40 (ppO2=2.80 bar....) here
> results in:
> 1'@9m
> 5'@6m
> 13'@3m (Standard ZH-L16)
>
> Compared with 21'@60m and Air:
> 3'@15m
> 5'@12m
> 8'@9m
> 18'@6m
> 37'@3m
>
> regards,
> Matthias
hi Matthias
on your example, we cannot dive at 60 m with EAN 40, PPO² is over the roof.
all unused gas are deactivated
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
hi Matthias
sorry to bother with this issue, but i think it is important to sort it out
at least for me to understand.
i am doing another try
bulhman OC
GF= No GF
EAN 40= MOD 30 meters
o²=MOD 6 meters
depth= 60 meters
21 minutes at depth.
scenario 1
air
deco EAN 40
deco O²
15 m 2mns
12 m 3mns
9 m 7mns
6 m 11mns
3 m 23mns
total decotime air + EAN 40 + 0²
46 mns decotime
scenario 2
air
deco 0² only
(EAN 40 deactivated in gas setup)
15 m 2mns
12 m 5mns
9 m 8mns
6 m 7mns
3 m 13mns
total decotime air + 0²
35 mns decotime
looking at the above scenario, it means that EAN 40 as a deco gas is USELESS
within its MOD, ie 15/12/9 meters.
this sounds a bit weird, eventhough i am far of beeing a deco specialist.
let's go to scenario 3
scenario 3
air
deco EAN 40 only
(o² deactivated in gas setup)
15 m 2mns
12 m 3mns
9 m 7mns
6 m 11mns
3 m 22mns
total decotime air + EAN 40
45 mns decotime
Looking at different results
we get
AIR + EAN 40 + O² = DECO TIME 46 MNS
AIR + EAN 40 = DECO TIME 45 MNS O² IS USELESS
AIR + O² = DECO TIME 35 MNS EAN 40 USELESS
can someone make a try using these settings?
kind regards
sorry to bother with this issue, but i think it is important to sort it out
at least for me to understand.
i am doing another try
bulhman OC
GF= No GF
EAN 40= MOD 30 meters
o²=MOD 6 meters
depth= 60 meters
21 minutes at depth.
scenario 1
air
deco EAN 40
deco O²
15 m 2mns
12 m 3mns
9 m 7mns
6 m 11mns
3 m 23mns
total decotime air + EAN 40 + 0²
46 mns decotime
scenario 2
air
deco 0² only
(EAN 40 deactivated in gas setup)
15 m 2mns
12 m 5mns
9 m 8mns
6 m 7mns
3 m 13mns
total decotime air + 0²
35 mns decotime
looking at the above scenario, it means that EAN 40 as a deco gas is USELESS
within its MOD, ie 15/12/9 meters.
this sounds a bit weird, eventhough i am far of beeing a deco specialist.
let's go to scenario 3
scenario 3
air
deco EAN 40 only
(o² deactivated in gas setup)
15 m 2mns
12 m 3mns
9 m 7mns
6 m 11mns
3 m 22mns
total decotime air + EAN 40
45 mns decotime
Looking at different results
we get
AIR + EAN 40 + O² = DECO TIME 46 MNS
AIR + EAN 40 = DECO TIME 45 MNS O² IS USELESS
AIR + O² = DECO TIME 35 MNS EAN 40 USELESS
can someone make a try using these settings?
kind regards
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
wrobell Wrote:
-------------------------------------------------------
> Hi Matthias,
>
> Shall 1.47 and 1.50 behave the same way?
>
> I tried yesterday one of scenario presented by
> divingcool
> and I got strange results (air as first gas, then
> ean40@30m
> and o2@6m) with standard ZH-L16. I am using 1.47
> at the
> moment.
>
> I can provide more details late evening.
hi, i'll be interrested to look at your results versus mine.
cheers
-------------------------------------------------------
> Hi Matthias,
>
> Shall 1.47 and 1.50 behave the same way?
>
> I tried yesterday one of scenario presented by
> divingcool
> and I got strange results (air as first gas, then
> ean40@30m
> and o2@6m) with standard ZH-L16. I am using 1.47
> at the
> moment.
>
> I can provide more details late evening.
hi, i'll be interrested to look at your results versus mine.
cheers
Re: some bugs V 1.50 ???
Hi,
I think the reason why there is such a small difference in Deco time is because EAN40 only is being used during the ascent from 30m (MOD EAN40) to 6m (MOD 100%).
So depending on the ascent speed the simulator uses, suppose this is 10m/min, the time using EAN40 would only be 2,5 minutes.
And therefore it cannot influence the total deco time a lot.
I think the reason why there is such a small difference in Deco time is because EAN40 only is being used during the ascent from 30m (MOD EAN40) to 6m (MOD 100%).
So depending on the ascent speed the simulator uses, suppose this is 10m/min, the time using EAN40 would only be 2,5 minutes.
And therefore it cannot influence the total deco time a lot.
Regards,
Georges.
Georges.
Re: some bugs V 1.50 ???
divingcool Wrote:
-------------------------------------------------------
> wrobell Wrote:
> --------------------------------------------------
> -----
> > Hi Matthias,
> >
> > Shall 1.47 and 1.50 behave the same way?
> >
> > I tried yesterday one of scenario presented by
> > divingcool
> > and I got strange results (air as first gas,
> then
> > ean40@30m
> > and o2@6m) with standard ZH-L16. I am using
> 1.47
> > at the
> > moment.
> >
> > I can provide more details late evening.
>
> hi, i'll be interrested to look at your results
> versus mine.
> cheers
well, mine are completely out of space but as i said
i am using 1.47 firmware.
-------------------------------------------------------
> wrobell Wrote:
> --------------------------------------------------
> -----
> > Hi Matthias,
> >
> > Shall 1.47 and 1.50 behave the same way?
> >
> > I tried yesterday one of scenario presented by
> > divingcool
> > and I got strange results (air as first gas,
> then
> > ean40@30m
> > and o2@6m) with standard ZH-L16. I am using
> 1.47
> > at the
> > moment.
> >
> > I can provide more details late evening.
>
> hi, i'll be interrested to look at your results
> versus mine.
> cheers
well, mine are completely out of space but as i said
i am using 1.47 firmware.
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
georges Wrote:
-------------------------------------------------------
> Hi,
>
> I think the reason why there is such a small
> difference in Deco time is because EAN40 only is
> being used during the ascent from 30m (MOD EAN40)
> to 6m (MOD 100%).
> So depending on the ascent speed the simulator
> uses, suppose this is 10m/min, the time using
> EAN40 would only be 2,5 minutes.
> And therefore it cannot influence the total deco
> time a lot.
thanks for this suggestion, indeed, it makes sense. as i previouslay wrote, i am far away of beeing a specialist, my aim is a good understanding of this for a better use.
-------------------------------------------------------
> Hi,
>
> I think the reason why there is such a small
> difference in Deco time is because EAN40 only is
> being used during the ascent from 30m (MOD EAN40)
> to 6m (MOD 100%).
> So depending on the ascent speed the simulator
> uses, suppose this is 10m/min, the time using
> EAN40 would only be 2,5 minutes.
> And therefore it cannot influence the total deco
> time a lot.
thanks for this suggestion, indeed, it makes sense. as i previouslay wrote, i am far away of beeing a specialist, my aim is a good understanding of this for a better use.
Re: some bugs V 1.50 ???
divingcool Wrote:
-------------------------------------------------------
[...]
> scenario 1
>
> air
> deco EAN 40
> deco O²
>
> 15 m 2mns
> 12 m 3mns
> 9 m 7mns
> 6 m 11mns
> 3 m 23mns
may i suggest to run above scenario in the real
time simulator? i got 14min deco with o2 at 6m
(last stop 6m). total deco time was about 34 minutes.
-------------------------------------------------------
[...]
> scenario 1
>
> air
> deco EAN 40
> deco O²
>
> 15 m 2mns
> 12 m 3mns
> 9 m 7mns
> 6 m 11mns
> 3 m 23mns
may i suggest to run above scenario in the real
time simulator? i got 14min deco with o2 at 6m
(last stop 6m). total deco time was about 34 minutes.
Re: some bugs V 1.50 ???
divingcool Wrote:
-------------------------------------------------------
> Looking at different results
> we get
> AIR + EAN 40 + O² = DECO TIME 46 MNS
> AIR + EAN 40 = DECO TIME 45 MNS O² IS
> USELESS
> AIR + O² = DECO TIME 35 MNS EAN 40
> USELESS
Hi folks!
Please consider, that the OSTC calculates the decoplan only with the next higher activated decogas (in the real dive modes as in the simulator). So if you have two decogases activated, the decoplan looks the same as if you had activated only the deeper gas.
Matthias wrote some time ago, that this issue has to do with the limited computing power of the processor, but they are looking forward to find a solution.
Cheers
Matthias
-------------------------------------------------------
> Looking at different results
> we get
> AIR + EAN 40 + O² = DECO TIME 46 MNS
> AIR + EAN 40 = DECO TIME 45 MNS O² IS
> USELESS
> AIR + O² = DECO TIME 35 MNS EAN 40
> USELESS
Hi folks!
Please consider, that the OSTC calculates the decoplan only with the next higher activated decogas (in the real dive modes as in the simulator). So if you have two decogases activated, the decoplan looks the same as if you had activated only the deeper gas.
Matthias wrote some time ago, that this issue has to do with the limited computing power of the processor, but they are looking forward to find a solution.
Cheers
Matthias
Viele Grüße
Matthias
OSTC Mk II #661
Matthias
OSTC Mk II #661
Re: some bugs V 1.50 ???
deco calculator performs whole dive, just
with time passing faster, isn't it? so all
deco calculation should take into account
time spent at deco stops while using ean40
and o2.
imho, it looks like gases are not switched
automatically during fast simulation performed
by deco planner.
with time passing faster, isn't it? so all
deco calculation should take into account
time spent at deco stops while using ean40
and o2.
imho, it looks like gases are not switched
automatically during fast simulation performed
by deco planner.
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
georges Wrote:
-------------------------------------------------------
> Hi,
>
> I think the reason why there is such a small
> difference in Deco time is because EAN40 only is
> being used during the ascent from 30m (MOD EAN40)
> to 6m (MOD 100%).
> So depending on the ascent speed the simulator
> uses, suppose this is 10m/min, the time using
> EAN40 would only be 2,5 minutes.
> And therefore it cannot influence the total deco
> time a lot.
hi looking a bit more deeply, i think you are wrong as
looking at the run time, indeed there are just 2,5 mns of ascent
but there are some stops at
15 m 2mns
12 m 5mns
9 m 8mns
using ean 40 so total time using ean 40 is 15 mns at stops plus the ascent time so it has to be taken in consideration. isn't it?
-------------------------------------------------------
> Hi,
>
> I think the reason why there is such a small
> difference in Deco time is because EAN40 only is
> being used during the ascent from 30m (MOD EAN40)
> to 6m (MOD 100%).
> So depending on the ascent speed the simulator
> uses, suppose this is 10m/min, the time using
> EAN40 would only be 2,5 minutes.
> And therefore it cannot influence the total deco
> time a lot.
hi looking a bit more deeply, i think you are wrong as
looking at the run time, indeed there are just 2,5 mns of ascent
but there are some stops at
15 m 2mns
12 m 5mns
9 m 8mns
using ean 40 so total time using ean 40 is 15 mns at stops plus the ascent time so it has to be taken in consideration. isn't it?
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
ok
lets put it an other way.
the deco calculation should help me to prepare a "what if" i loose deco 1 and/or deco 2 during the dive, isn't it?
i can also prepare a written back up run time.
in that case it 's pretty handy otherwise, what's the real purpose of it.
using the real time simulator is ok as it shows all different settings that one can set up and look the way it is displayed, but planning a 60 m dive for 21 mns plus the deco, is a bit long and boring to watch.
lets put it an other way.
the deco calculation should help me to prepare a "what if" i loose deco 1 and/or deco 2 during the dive, isn't it?
i can also prepare a written back up run time.
in that case it 's pretty handy otherwise, what's the real purpose of it.
using the real time simulator is ok as it shows all different settings that one can set up and look the way it is displayed, but planning a 60 m dive for 21 mns plus the deco, is a bit long and boring to watch.
-
- Posts: 23
- Joined: 25 Feb 2009, 17:07
Re: some bugs V 1.50 ???
Hiasl Wrote:
> Please consider, that the OSTC calculates the
> decoplan only with the next higher activated
> decogas (in the real dive modes as in the
> simulator). So if you have two decogases
> activated, the decoplan looks the same as if you
> had activated only the deeper gas.
>
> hi
do you mean that in real dive eventhough the MOD has been activated for each deco gas, whatever they are and whatever is the depth of use, only the deepest will be taken in account for the deco, sounds weird.
so does it mean also that you have to reach the MOD of next deco gas to have him automatically activated and then the decoplan to be updated.
i dont understand really, and i must miss something somewhere.
> Please consider, that the OSTC calculates the
> decoplan only with the next higher activated
> decogas (in the real dive modes as in the
> simulator). So if you have two decogases
> activated, the decoplan looks the same as if you
> had activated only the deeper gas.
>
> hi
do you mean that in real dive eventhough the MOD has been activated for each deco gas, whatever they are and whatever is the depth of use, only the deepest will be taken in account for the deco, sounds weird.
so does it mean also that you have to reach the MOD of next deco gas to have him automatically activated and then the decoplan to be updated.
i dont understand really, and i must miss something somewhere.
Re: some bugs V 1.50 ???
@divingcool:
I did three simulator-runs right now:
All of them 21minutes in 60m, bottom-gas 21/35 (depth=0m), decogas 1 Nx50 (21m) dcogas 2 O2 (6m)
First run with both decogases activated: total deco-time = 40minutes
Second run only with decogas 1 (Nx50): exactly the same decoplan like in the first run ==> in run 1 the shallower decogas is not used for calculating deco
Third run only with O2 as decogas: total deco-time = 50minutes, with longer midrange-stops (21m - 9m) and shorter shallow stops (6m + 3m) as in run 1 and 2
During a real dive (or with the external simulator an switching gases by hand), the dive with both decogases will have shorter 6m- and 3m- stops than in run 1 in my example.
q.e.d.
Cheers
Matthias
I did three simulator-runs right now:
All of them 21minutes in 60m, bottom-gas 21/35 (depth=0m), decogas 1 Nx50 (21m) dcogas 2 O2 (6m)
First run with both decogases activated: total deco-time = 40minutes
Second run only with decogas 1 (Nx50): exactly the same decoplan like in the first run ==> in run 1 the shallower decogas is not used for calculating deco
Third run only with O2 as decogas: total deco-time = 50minutes, with longer midrange-stops (21m - 9m) and shorter shallow stops (6m + 3m) as in run 1 and 2
During a real dive (or with the external simulator an switching gases by hand), the dive with both decogases will have shorter 6m- and 3m- stops than in run 1 in my example.
q.e.d.
Cheers
Matthias
Viele Grüße
Matthias
OSTC Mk II #661
Matthias
OSTC Mk II #661
Re: some bugs V 1.50 ???
Hey,
I did calculate these dives with V-planner
60m 20 min
air + EAN40 + 02= total time of 57min
air + EAN40= 70 min
air + 02= 70 min
so with VPM B/E with 1 decogas EAN 40 or 100%O2 total diving time is the same. So it has something to do with these decogasses aswell. Concidence that they have both the same tts.
just a thought
grz,
Steve
I did calculate these dives with V-planner
60m 20 min
air + EAN40 + 02= total time of 57min
air + EAN40= 70 min
air + 02= 70 min
so with VPM B/E with 1 decogas EAN 40 or 100%O2 total diving time is the same. So it has something to do with these decogasses aswell. Concidence that they have both the same tts.
just a thought
grz,
Steve
Steve
CMAS 2* Instructor
CMAS Advanced Nitrox Instructor
Belgium
CMAS 2* Instructor
CMAS Advanced Nitrox Instructor
Belgium
Re: some bugs V 1.50 ???
Hello,
regarding deco gases, they need to have a switch depth assigned, see here:
http://www.heinrichsweikamp.com/read.php?2,2057
Reiner
regarding deco gases, they need to have a switch depth assigned, see here:
http://www.heinrichsweikamp.com/read.php?2,2057
Reiner