I completed two dives in the Atlantic off NJ last week. I wear two computers, one is a TUSA IQ 800, the other a AI Galileo Sol. (I have a backup SPG too). Both computers set on least conservative profiles. (I was wearing the heart strap for the Galileo-important). I was diving air at a depth of 90 feet for both dives. First dive was 40 mins; SI about 90 mins. No issues. On the second dive, the two computers started to differ in NDT after about 10 minutes. The Galileo was showing 3 mins; The TUSA - 7 mins. I ascended to about 70ft. TUSA moves up to 12 mins; Galileo goes into DECO. I ascend to about 50 - do a stop of 5 mins; Then a 10 min stop at 30 and 10mins at 20. Then surface. TUSA is fine. Galileo is alerting the authorities to bring a body bag.
I downloaded the profiles on my computer and identified what I suspect to be the problem. The Galileo calculates NDLs based on standard algorithms, aspiration, temp and heart rate. According to the computer, my heart rate had gone from 80 bpm and stayed at 220bpm for about one minute - three times in the dive. (I work out 4/5 days a week and wear a HR monitor and I've never seen 220bpm!).
I suspect that the HR input (together with 48F water) pushed the computer into early deco. A major pain in the butt. I was beeping like a broken alarm clock when I surfaced. Also flashing the name of my next of kin. I have also found that once you violate NDLs, the computer is done for 3 days.
I will never wear the heart-strap again. It seems like innocuous data but can really screw up your dives big time. I understand that the chest-strap is probably the problem here, but the computer has not been designed to deal with this. The software is incapable of dealing with obviously murky data.
Anyone else have similar issues?
I downloaded the profiles on my computer and identified what I suspect to be the problem. The Galileo calculates NDLs based on standard algorithms, aspiration, temp and heart rate. According to the computer, my heart rate had gone from 80 bpm and stayed at 220bpm for about one minute - three times in the dive. (I work out 4/5 days a week and wear a HR monitor and I've never seen 220bpm!).
I suspect that the HR input (together with 48F water) pushed the computer into early deco. A major pain in the butt. I was beeping like a broken alarm clock when I surfaced. Also flashing the name of my next of kin. I have also found that once you violate NDLs, the computer is done for 3 days.
I will never wear the heart-strap again. It seems like innocuous data but can really screw up your dives big time. I understand that the chest-strap is probably the problem here, but the computer has not been designed to deal with this. The software is incapable of dealing with obviously murky data.
Anyone else have similar issues?