#6: Add support for parsing gas changes in the Oceanic backends
-------------------------------------+-------------------------------------
Reporter:| Owner: jefdriesen
jefdriesen | Status: new
Type:| Component: Dive parsing
enhancement | Keywords:
Priority:|
major |
Version:|
master |
Plattform (please give specifics in |
the ticket text): All |
-------------------------------------+-------------------------------------
\
\
Currently, none of the Oceanic backends does support parsing the gas
changes in the profile data.
The first step will be to figure out how the gas changes are stored in the
data. Most likely the tank switch sample is not only used to indicate the
active tank pressure sensor, but also the active gas mix. How this works
for non air integrated models is also unknown. Maybe there is a tank
pressure of zero, or a disabled pressure sensor in this case?
\
\
\
--
Ticket URL: <http://trac.libdivecomputer.org/ticket/6>
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers
#3: Add support for parsing temperature in the dive header
-------------------------------------+-------------------------------------
Reporter:| Owner: jefdriesen
jefdriesen | Status: new
Type:| Component: Dive parsing
enhancement | Keywords:
Priority:|
major |
Version:|
master |
Plattform (please give specifics in |
the ticket text): All |
-------------------------------------+-------------------------------------
\
\
Currently, libdivecomputer only parses the temperature stored in the
sample data, but not the dive header. The consequence is that the
temperature is only reported for those devices that record a complete
temperature profile. For those devices that store only a single
temperature value in the dive header, the dc_parser_get_field interface
should be extended with temperature support.
\
\
\
--
Ticket URL: <http://trac.libdivecomputer.org/ticket/3>
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers
#4: Add support for parsing tank pressure in the dive header
-------------------------------------+-------------------------------------
Reporter:| Owner: jefdriesen
jefdriesen | Status: new
Type:| Component: Dive parsing
enhancement | Keywords:
Priority:|
major |
Version:|
master |
Plattform (please give specifics in |
the ticket text): All |
-------------------------------------+-------------------------------------
\
\
Currently, libdivecomputer only parses the tank pressure stored in the
sample data, but not the dive header. The consequence is that the tank
pressure is only reported for those devices that record a complete tank
pressure profile. For those devices that store only a single tank pressure
value in the dive header, the dc_parser_get_field interface should be
extended with tank pressure support.
\
\
\
--
Ticket URL: <http://trac.libdivecomputer.org/ticket/4>
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers
#12: Shearwater Petrel (and Predator)
-------------------------------------+-------------------------------------
Reporter:| Owner: jefdriesen
joebar | Status: new
Type:| Component: Device communication
task | Keywords: Shearwater Petrel,
Priority:| Bluetooth, connection
minor |
Version:|
0.4 |
Plattform (please give specifics in |
the ticket text): Windows |
-------------------------------------+-------------------------------------
\
\
Hi Jef
I am using Diving Log 5 and tried to download the Logs of my new
Shearwater Petrel.
When I try to connect the following error appears:
Error:DC_STATUS_IO
Bluetooth only activated, the error message appears after about 1min and
20sec.
Bluetooth only not activated, the error message appears immediately.
The Bluetooth connection with the original Shearwater Software (Shearwater
Desktop) works without probems (downloading logs and uploading Firmware)
As I have seen in the Diving Log Forum, there is another guy with a
Predater that is receiving the same error message.
http://www.divinglog.de/phpbb/viewtopic.php?f=3&t=2328
Can you give me some advice?
\
\
\
--
Ticket URL: <http://trac.libdivecomputer.org/ticket/12>
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers
New user registration for user joebar
--
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers
#11: "Leonardo" is listed as Mares device on the "About" page.
-------------------------------------+-------------------------------------
Reporter:| Owner: jefdriesen
mattthias | Status: new
Type:| Component: General
enhancement | Keywords:
Priority:|
major |
Version:|
0.4 |
Plattform (please give specifics in |
the ticket text): All |
-------------------------------------+-------------------------------------
\
\
Hi,
the "Leonardo" dive computer is listed as "Mares" device on the "About"
page [1] and it should be listed as "Cressi". Maybe as "Cressi (non-
Seiko)" as the Cressi homepage states that the "..Leonardo is the first
dive computer designed and built entirely by Cressi" [2].
Thanks for the great library :-)
best wishes,
Matthias
[1] http://www.libdivecomputer.org/index.html
[2] http://www.cressi.com/catalogue/details.asp?id=689
\
\
\
--
Ticket URL: <http://trac.libdivecomputer.org/ticket/11>
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers
New user registration for user mattthias
--
libdivecomputer <www.libdivecomputer.org>
a cross-platform and open source library for communication with dive computers from various manufacturers