Issues Cobalt 2

[DuikerPaul]

I've been recently (February '16) upgraded from a Cobalt 1 to a Cobalt 2 (after battery and compass issues with the Cobalt 1).
I was a satisfied user of the Cobalt 1 (an earlier issue with the buttons of the 1 was solved perfect by Atomics.)

I have now multiple issues with the Cobra 2:
-After removal from the charger the battery indication drops immediatly from 100% to 93%.
-The screen brightness adjustment doesn't respond on manual changing (DOWN button) during a dive (preference setting is on: scroll up/down)
-During a recent dive the screen froze whilst entering the Safety Stop depth, this lasted about 1 1/2 minute then it resumed . Back on land the Cobalt wasn't operable via the buttons. After approx. two hours the Cobalt was operable again.
-On my latest dive yesterday; when entering the Safety Stop depth, the compass went haywire; it rapidly started turning and the numbers where everywhere. After the Stop the compass seemed to function normal again.
-Battery power cosumption seems very high; After 1 dive (30 min, 26 meters max, water temperature 7C) the battery was after less than 24 hours down from fully charged to 81%.

The Cobalt seems to do the dive calculations correct, yet I don't feel that the Cobalt is reliable.
Software Version onboard is 2.42

Solutions I've tried but didnt work:
-leaving the Cobalt for 24 hours at the ACcharger.
-performed a reset (via simultaneously Select and Back button)

(I've contacted my dealer via mail but he has responded(yet))
Does anyone experience the same problems/issues?
What would be the solution?

Thanks in advance.

 

[RonR]

I responded where you posted this on the Atomic Scubaboard section, I will repost here:

I’ll try to take your problems in sequence.

1) The charger may read 100% for a slight while before the battery is actually full, while it’s finishing the change at a trickle rate for the last few % the gauge might not read completely accurately. Ideally wait until you see the message “Charging Done”. Then it should read 100%, or very close to, on removal.

2) The manual screen brightness adjustment being inaccessible during a dive is a known issue with the firmware you have, and has been corrected, I don’t think it has yet been posted to the Atomic website, but the new version will be 2.43. I have sent you a link to this version, but I think you have bigger issues.

3) Any kind of screen freeze indicates a serious problem, possibly related to water getting into the electronics, a broken connection, or a failed component. This should definitely get checked out, as it is something that should never happen and makes me suspect this particular Cobalt 2.

4) re. The compass going haywire on entering the safety stop depth- was this when the sounder was signaling arrival at stop? The accelerometer in the compass will be affected by the vibrations from the sounder, and will dance around as long as it is making noise. When the sounder stops, it should resume function. The Cobalt 2's more responsive compass makes this much more noticeable. We don’t have a way around this other than turning off the compass when audible alerts sound. We do plan to offer the option to turn off audible alerts, though.

5) Battery power consumption will be a little more than the Cobalt 1, but this makes me wonder if it is related to #3 above. If you do not use the Cobalt, in sleep/ standby mode it should not be dropping more than 1-2% per 24 hours. Power consumption in diving is mostly driven by screen brightness, but you should still be able to get 20-30 hours of diving even at maximum brightness.

I hate to not have an easy solution for all your issues, but the screen freeze and loss of button function makes me think this one should go back. Out of curiosity, what is your serial number? That will tell me the date of manufacture.

-Ron

 

[johnmckenzie]

Ron here is a new problem a friend is having with his Cobalt.

His Cobalt 1 went to deco after about 20 minutes into his first dive of the day. The whole dive was 42 min. Most of the dive was shallower than 70 fsw with only a quick drop (early on) down to 93 fsw for less than 5 min total time deeper than 70fsw. His buddy's computer indicated plenty of NDL.

 

[RonR]

Hi John,

What firmware version is on this Cobalt 1?

The first thing I would do is to look at the Cobalt's onboard log and make sure the saved depths match what really happened, to rule out the possibility of a malfunctioning depth sensor. You can also look in the log to see where in the dive a deco schedule was generated. NDT will also display for each segment.

Also check the time / date settings to make sure they are correct. if the Cobalt has recently been reset (as in a firmware update) or had the battery run down it will revert to the time of the last dive exit, that can create deco or short no-deco times because the Cobalt is seeing the dive as a repetitive dive. This would also show in the Cobalt's log.

There was a very rare issue with some older firmware versions that could result in deco dives being logged when there should have been no deco obligation. I think we only found three instances, but the issue was tracked down and corrected. If everything else looks correct and the firmware is older he may have experienced this issue. It's hard to say more without knowing the firmware version.

Let me know.

Ron