hi again,
so, in the meantime i got the F.10 back from the shop, with a firmware update done, as they told me. today I was able to test it in the pool. the problem I most hoped to be solved now was the wet-activation/deactivation issue. i went to the bottom of the deep pool with wet act set "off" - and wow, the F.10 indeed did not log. great, I thought back at the surface, now lets set it "on". I did so and went back down. As expected, the F10 started to log the dive. very good. at the surface, i switched the wet act "off" again and went down once more, and there we were: the F10 logged the dive! :blackeye :vangry oh no!! I repeated the procedure, but from this moment on every dive was logged, regardless of the setting. so, exactly the same situation as before the "firmware update".
I suspect now that the whatch logging despite the wet act set "off" might somehow be related to the so called FREE surface mode - a feature whose purpose is pretty obscure to me anyway. the fact is that this FREE surface mode counts the time for I don't know how long after you made a dive, even a ridiculous one of 10 sec to 3m of depth. My last dive in the pool is over since 3 hours now, and still, if by pressing the M botton for more than 2 sec i change from TIME display to FREE surface mode, the F10 counts the secs, mins and hours from my last dive. What for ??? And as long as this time is counted, i am afraid the computer will log any dive you perform, regardless if wet act is set "off". only after the count is completed (when? after how long??) it might be that the F10 does not activate under water any more with wet act set "off". but i could not test this hypothesis. and even if its true, what is the benefit of it? I don't know. I just know that i can not have the F10 first logging my dives in the deep pool and than just acting as a whatch in the (very) shallow pool when I do laps underwater.
So, that sucks.
all in all i did'nt notice any change after the firmware update. ok, so far no battery-change icon. i hope it stays like this, but as fondueset told us, this is rather a hardware problem and has nothing to do with the software.
so far, everythin seems back to normal: still no date in the logbook, still a ridiculous 3-beep daily alarm, still a wet activation/deactivation function that has a mind of its own...
:head
Ivo