#5: Shearwater Petrel Firmware V18 -------------------------------------+------------------------------------- Reporter:| Owner: jefdriesen kwkoo | Status: new Type:| Component: General defect | Keywords: Priority:| major | Version:| 0.4 | Plattform (please give specifics in | the ticket text): All | -------------------------------------+------------------------------------- \ \ I just upgraded the firmware for my Shearwater Petrel, and libdivecomputer can no longer communicate with it.
Is there anything I can do to get more debug information?
Thanks! \ \ \
-- Ticket URL: http://trac.libdivecomputer.org/ticket/5 libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers
#5: Shearwater Petrel Firmware V18 -------------------------------------+------------------------------------- Reporter: kwkoo | Owner: Type: defect | jefdriesen Priority: major | Status: Version: 0.4 | new Keywords: | Component: | General | Resolution: | Plattform (please give specifics in | the ticket text): All -------------------------------------+------------------------------------- \ \ \ \ \ \
Comment (by jefdriesen):
What error is displayed on the Petrel itself?
Are you sure /dev/tty.Bluetooth-Incoming-Port is the correct serial port to use? I think Mac OS X creates multiple /dev/tty.* entries for bluetooth adapters, and not all of them work. Can you post the output of the "ls /dev/tty.*" command?
If possible, can you also try on a Windows or Linux machine? For those two platforms, there is also an experimental "universal-bluetooth" build available. This uses native bluetooth communication instead of serial port emulation. You can download it here:
http://www.libdivecomputer.org/builds/experimental/
It takes the same options as the normal build, except that you have to replace the portname with bluetooth MAC address (e.g. something like 11:22:33:44:55:66). There have been reports that the serial port emulation does not always work very reliable. I have noticed this with my Petrel too, and the problem disappears after switching to native bluetooth communication. I'm not sure if your problem is related, but it's worth trying to find out. \ \ \
-- Ticket URL: http://trac.libdivecomputer.org/ticket/5#comment:1 libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers
#5: Shearwater Petrel Firmware V18 -------------------------------------+------------------------------------- Reporter: kwkoo | Owner: Type: defect | jefdriesen Priority: major | Status: Version: 0.4 | new Keywords: | Component: | General | Resolution: | Plattform (please give specifics in | the ticket text): All -------------------------------------+------------------------------------- \ \ \ \ \ \
Comment (by kwkoo):
Thanks jef.
You were right. It works perfectly on Windows!
You were also right about the OS X device. The correct device is actually /dev/tty.Petrel-SerialPort. Everything worked correctly once I used the right device.
Sorry for the confusion! \ \ \
-- Ticket URL: http://trac.libdivecomputer.org/ticket/5#comment:2 libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers
#5: Shearwater Petrel Firmware V18 -------------------------------------+------------------------------------- Reporter: kwkoo | Owner: Type: defect | jefdriesen Priority: major | Status: Version: 0.4 | closed Keywords: | Component: | General | Resolution: | invalid | Plattform (please give specifics in | the ticket text): All -------------------------------------+------------------------------------- \ \ \ \ Changes (by kwkoo):
* status: new => closed * resolution: => invalid
\ \ \ \ \
-- Ticket URL: http://trac.libdivecomputer.org/ticket/5#comment:3 libdivecomputer <www.libdivecomputer.org> a cross-platform and open source library for communication with dive computers from various manufacturers
-
Libdivecomputer Bug Tracking System