markmantei
Contributor
On the tail end of a recent dive trip I had issues with my VT4. On Feb 4 I did my first dive of the day 31% Nitrox to a depth of 105 ft. Dive was fine and VT4 performed normally. We did a fairly short surface interval and I switched my VT4 to 36% and used the VT4 to plan my next dive which would be very shallow, max depth ~30 ft. Everything checked out and I had ample no deco time for the dive. I splashed and almost immediatly the VT4 jumped into deco. That was strange, but since it was a long dive at shallow depth I was able to clear the deco before the next dive. I continued to fight with the computer for the following 2 dives of the day before I finally locked it out on the night dive. I was able to complete my diving as I dive with a sherwood wisdom as a backup, but it was rather frustrating to have the computer malfunction. If it was too short of a surface interval I would expect the sherwood (also a pelagic computer) to have mimiced the same output as the VT4, but the other computer was fine. I am sure I could download the sherwood for comparison if that will help. Firmware version of the VT4 is 1B.02, which I believe is the latest version.
Any ideas on what may have caused this. I have uploaded screenshots of the first 2 dives in oceanlog and the excel exports of the dives in case this helps.
I figured I would jump in the pool this weekend to see what happens, but since this will be a shallow non-repetitive dive I am not convinced that the problem would show up anyway.
Thanks for the help!
Any ideas on what may have caused this. I have uploaded screenshots of the first 2 dives in oceanlog and the excel exports of the dives in case this helps.
I figured I would jump in the pool this weekend to see what happens, but since this will be a shallow non-repetitive dive I am not convinced that the problem would show up anyway.
Thanks for the help!