#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
#12: Shearwater Petrel (and Predator) -------------------------------------+------------------------------------- Reporter: joebar | Owner: Type: task | jefdriesen Priority: minor | Status: Version: 0.4 | new Keywords: Shearwater Petrel, | Component: Bluetooth, connection | Device communication | Resolution: | Plattform (please give specifics in | the ticket text): Windows -------------------------------------+------------------------------------- \ \ \ \ \ \
Comment (by jefdriesen):
One possibility is that the bluetooth serial emulation isn't always working very well. At least that's the impression I have when trying to download from my petrel or frog. Sometimes downloading suddenly fails (with an error message on the petrel), for no obvious reason. But when I switch to my prototype native bluetooth communication, the problems disappears. I'm not sure whether this is a similar problem or not.
I have uploaded a build with native bluetooth enabled to the libdivecomputer website:
http://www.libdivecomputer.org/builds/experimental/windows/universal- bluetooth.exe
Run it with the following arguments:
universal-bluetooth.exe -v -l petrel.log -d petrel.xml -b petrel <MAC>
Replace <MAC> with the bluetooth mac address of your petrel. You should be able to find it somewhere in the device manager (sorry don't remember exactly where). It's a number that looks like 00:11:22:33:44:55. Also note that there is only support for the Microsoft bluetooth stack. It won't work with alternatives like the widcomm stack. \ \ \
-- Ticket URL: http://trac.libdivecomputer.org/ticket/12#comment:1 libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers
-
Libdivecomputer Bug Tracking System