Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.
Benefits of registering include
I don't think it's a problem with the Cobalt, particularly if it has continued to read pressure consistently on other dives. What I suspect is a tank valve that was partially blocked or not fully open, allowing the HP to fluctuate to the 1st stage of the regulator. This would become more extreme as the pressure was less in the tank. The exact moment a sample was taken in relation to a breath cycle could create fluctuations like this. With a decent regulator you probably wouldn't notice any difference in breathing effort. Firmware versions 1.1 and later, now on the Atomic website, sample the HP more frequently and would probably show the fluctuations more clearly. This is not a diagnosis (I could be missing something), but I think is the most likely explanation.I wanted to bring up one issue I had, to see if you or your counterparts at atomic felt it might be a computer issue or not. I dont feel it is, for various reasons, but I will let the experts chime in before i go off spouting theories.
On dive number 6 of the trip, near the last 1/3rd of my tank, I noticed extreme pressure fluctuations. Infact i noticed because I actually heard my alarm continually going off. Id see 1100, then 600, then 900, then 0, then 1200. Sometimes it would settle down for more than 10s, but most of the time it would vary quite a bit. I dont think I noticed any substantial increase in breathing resistance....I may have just become more cognizant of my breathing resistance. Its just hard to say.
I completed 3 more dives on this trip without being able to repeat this issue. I've also since tried it on a couple more tanks just to check, and pressure reads as it should before and after a long purge through a reg.
Now, while I only noticed this fluctuation in the last third of my tank thanks to the alarm, its clear that it was happening throughout the entire dive. Dive log data is attached.
So, what do you guys think?
Computer or not computer?
Is this concern for you guys for me to send it in or not?
Secondly, after the new software and everything, I have a few comments.
I figured since you are more tied to the software, and are very responsive, these might fall on the most receptive ears out there. Here they are;
1. I cant enter anything with a ' at the end. Such as 10'. Causes the program to have an error.
2. It would be great if we could set the scales of each item rather than having it auto fit. On occasion a data spike makes it hard to read a line. (ie RMV...see 2nd attachement)
3. In the Gas Table summary, it would be nice if the Start Pressure was included just above the End Pressure.
4. Notes area. Has a very small limit on the amount of text. Can this be increased?
5. Add the ability to average data to create a trend line. Reading a trend in RMV is tricky since it bounces around a lot with the relatively slow sample rate.
6. Might be nice to add the ability to chop the end of dive data. See 2nd attached graph. I think the captain shut off my wife's main valve while she was still breathing on her reg as she was getting back on the boat due to some chop in the water. The captain should have waited till she was on board, but didnt.
Looks like it fooled the computer to thinking she used 950psi in 30s.
Also, I know its easier for me, but if you need me to respond or send in my computer or something, please do also send me a quick email.
My email is my username_on_scubaboard @ gmail dot com
This sounds like a driver issue. Diving Log uses a different driver, and you need to change to go back to the firmware updater.Can anyone help with this??
I had no problem flashing the first update but the second one now will not update, I know where the unzipped file is and I am connected to the computer.
It goes directly from pushing the start button to connection closed. The cobalt does not even blink it is still at the connection page saying it is connected. When I check the version it is still at 1.10/1.
My USB connections applet shows the Atomics-Cobalt is there and it will disconnect/eject it if asked so the usb connection appears to be working.
I can also connect to Diving log 5.0 and upload with no problems.
If I try to upload from the Atomis software I get an exception error. See attached JPG
BTW I have uninstalled the software and reinstalled it 2 x's. Still get the same results
@bthinnes: I don't know if this error is related to this, but make sure to switch the driver back to the original Atomic driver, when using the Atomic software (libdivecomputer in Diving Log is using a different driver).
This sounds like a driver issue. Diving Log uses a different driver, and you need to change to go back to the firmware updater.