Just wondering if anyone else has had a problem whereby the D3 seemed to be really late in starting a freedive log?
I was doing a dive on the weekend, and noticed that the first depth it recorded in the profile was 24ft! Usually it starts around 5-10ft. So, not only was the profile missing for the first 24ft, but it obviously didn't count this period of time in the overall dive time.
I first noticed the problem when it said my 40m dive was only 1:07! It missed out on probably 8 seconds worth of data. This also happened on another dive where it showed a start of 22ft.
Usually I leave it in FREE mode, and I am wondering if my surface interval was delayed (over 15 mins) that it might have gone back to TIME mode. In TIME mode, I thought it was supposed to detect the depth (>6ft) and switch to FREE. Could it be that the FREE mode times out after 15 mins and the "auto-detect" from TIME mode takes much longer to start?
Any help would be GREATLY appreciated!
Thanks.
I was doing a dive on the weekend, and noticed that the first depth it recorded in the profile was 24ft! Usually it starts around 5-10ft. So, not only was the profile missing for the first 24ft, but it obviously didn't count this period of time in the overall dive time.
I first noticed the problem when it said my 40m dive was only 1:07! It missed out on probably 8 seconds worth of data. This also happened on another dive where it showed a start of 22ft.
Usually I leave it in FREE mode, and I am wondering if my surface interval was delayed (over 15 mins) that it might have gone back to TIME mode. In TIME mode, I thought it was supposed to detect the depth (>6ft) and switch to FREE. Could it be that the FREE mode times out after 15 mins and the "auto-detect" from TIME mode takes much longer to start?
Any help would be GREATLY appreciated!
Thanks.