Friends,
I've used an Archimede 2 computer for 19 dives. On three dives, including two on Saturday, the DIVE mode functioned as usual, but there was a non-diving related error in the LOG mode.
One dive on 5/13/2006 lasted 54 minutes. The LOG mode shows the dive starts at 15:46 and ends at 16:00. A 48 minute dive the same day displays the start as 13:58 and end at 14:06 The LOG mode displays the correct length of the dive, but does not correctly indicate the clock time that the dive was stopped. This happened also on March 17, making a 50 minute dive read as 10:58 in, and 11:08 out. The error between the two displays is constant at 40 minutes.
These three dives were ocean dives of a normal drift dive profile. The other 16 dives were recorded correctly. Fortunately, this does not affect the DIVE mode.
I understand there are Tusa, Dive-Rite and Apeks computers that are the same hardware and software. Has anyone else had this problem? What did you do about it?
I've used an Archimede 2 computer for 19 dives. On three dives, including two on Saturday, the DIVE mode functioned as usual, but there was a non-diving related error in the LOG mode.
One dive on 5/13/2006 lasted 54 minutes. The LOG mode shows the dive starts at 15:46 and ends at 16:00. A 48 minute dive the same day displays the start as 13:58 and end at 14:06 The LOG mode displays the correct length of the dive, but does not correctly indicate the clock time that the dive was stopped. This happened also on March 17, making a 50 minute dive read as 10:58 in, and 11:08 out. The error between the two displays is constant at 40 minutes.
These three dives were ocean dives of a normal drift dive profile. The other 16 dives were recorded correctly. Fortunately, this does not affect the DIVE mode.
I understand there are Tusa, Dive-Rite and Apeks computers that are the same hardware and software. Has anyone else had this problem? What did you do about it?