Odd behavior
Posted: 30 Apr 2010, 18:59
Hello Matthias & Christian,
For the third time in less than a month, my ostc has a very odd behavior with max depth and, today, min depth too... Let me explain: the first time happened when I tried 1.52, as described here. Since then onwards, I had twice the same problem: once as I was back to 1.50, and today for my first dive with 1.60.
Today arrived a new thing: during my dive, the ostc showed suddenly 0m, and after some seconds back to the current depht (44m).
Find enclosed some screen capture on my ostc (sorry for the bad pictures). You'll see how the logbook give me dives up to 109m and how the profiles are shown in the logbook (with a big space between real max depth and the bottom of the screen). I put the Jdivelog export of the three dive on a server, here (it was too big to join to the message, let me know when you get it). You'll see especially the third one which speak for itself...
I really don't know if it could be a unit-specific trouble (related to the pressure sensor ?) or a firmware bug... but please tell me what you think !
It'll be a pleasure to help you finding the problem if you let me know what I can do to help...
Regards
Olivier
For the third time in less than a month, my ostc has a very odd behavior with max depth and, today, min depth too... Let me explain: the first time happened when I tried 1.52, as described here. Since then onwards, I had twice the same problem: once as I was back to 1.50, and today for my first dive with 1.60.
Today arrived a new thing: during my dive, the ostc showed suddenly 0m, and after some seconds back to the current depht (44m).
Find enclosed some screen capture on my ostc (sorry for the bad pictures). You'll see how the logbook give me dives up to 109m and how the profiles are shown in the logbook (with a big space between real max depth and the bottom of the screen). I put the Jdivelog export of the three dive on a server, here (it was too big to join to the message, let me know when you get it). You'll see especially the third one which speak for itself...
I really don't know if it could be a unit-specific trouble (related to the pressure sensor ?) or a firmware bug... but please tell me what you think !
It'll be a pleasure to help you finding the problem if you let me know what I can do to help...
Regards
Olivier