March 2015 - tickets - libdivecomputer.org

[libdivecomputer] #6: Add support for parsing gas changes in the Oceanic backends
by Libdivecomputer Bug Tracking System 24 Dec '15

24 Dec '15

#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

1 2

[libdivecomputer] #13: Mares icon HD black: Bad profile import
by Libdivecomputer Bug Tracking System 14 Mar '15

14 Mar '15

#13: Mares icon HD black: Bad profile import -------------------------------------+------------------------------------- Reporter:| Owner: jefdriesen Bushi | Status: new Type:| Component: Device communication defect | Keywords: Icon, mares, profile Priority:| major | Version:| 0.4 | Plattform (please give specifics in | the ticket text): Windows | -------------------------------------+------------------------------------- Mares icon HD Black: firmware 4.1 Import of dive from icon to window 8 pc resulted in scary incirrct profile. Profile on pc show drop to 600ft then rocket to surface in middle of profile. This shows if I import with mares dive app, subsurface & dive log 5. This drop dose not appear on icon profile, further if I import to Mac aplications, subsurface or mares dive diary, the drop in profile dose not appear. Somthing about importing on the pc or how data is parsed seems in error. Not sure what is best to attach Thanks -- Ticket URL: <http://trac.libdivecomputer.org/ticket/13> libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers

1 2

[libdivecomputer] #14: Native bluetooth communication
by Libdivecomputer Bug Tracking System 09 Mar '15

09 Mar '15

#14: Native bluetooth communication -------------------------------------+------------------------------------- Reporter:| Owner: jefdriesen jefdriesen | Type:| Status: new enhancement | Priority:| Component: Device communication major | Version:| Keywords: master | Plattform (please give specifics in | the ticket text): All | -------------------------------------+------------------------------------- A while ago, I have been prototyping a native bluetooth communication backend for libdivecomputer. The goal is to be able to replace the serial emulation in the future. The main reason behind this effort is that the current situation, where we rely on serial emulation, is less than ideal. It requires some setup by the end-user, and last but not least it doesn't appear to work very well on linux! I have arrived at a point where I have a functional implementation for windows and linux. With functional, I mean I'm able to connect to the dive computer and successfully download dives. What is still missing is device discovery, which means you have to figure out the bluetooth address of the device manually. Certainly not perfect yet, but it does work! I have attached the patches with my prototype code. These patches include the bluetooth communication code, together with the necessary changes to integrate it into the Shearwater Predator and Petrel backend (the same could be done for the Heinrichs Weikamp Frog too). The linux and windows implementations are very similar because they both provide a socket interface ![1,2]. (I actually spend most of the time debugging a failure on Windows. In the end, the problem turned out to be caused by a bug in the mingw header files, and not my code. The bug was already fixed upstream ![3], but not yet included in the packages I was using.) I'm now looking at Mac OS X support, but this appears to be much harder than I expected. The developer documentation ![4] isn't very helpful. It contains lots of information, but appears to lack the info I'm looking after (e.g. how to connect to a device, send/receive data, etc). The fact that I don't have any experience with Objective-C code or the Mac framework doesn't really help either. So if anyone can provide some assistance here, that would be great! Ideally, I would like to avoid using Objective-C code completely and use the C api of the Mac framework instead. Of course help is not limited to the Mac OS X part only. If you have some knowledge about bluetooth in general, or have some experience with the Windows and Linux bluetooth api's, then any help in that area is appreciated too! ![1] http://people.csail.mit.edu/albert/bluez-intro/ ![2] http://msdn.microsoft.com/en- us/library/windows/desktop/aa362932%28v=vs.85%29.aspx ![3] http://sourceforge.net/p/mingw-w64/code/6249/ ![4] https://developer.apple.com/library/mac/#documentation/DeviceDrivers/Concep… -- Ticket URL: <http://trac.libdivecomputer.org/ticket/14> libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers

1 6