The Petrel 2 (my computer) supports both BLE and old-fashioned Bluetooth. Both work for me with Subsurface. Earlier Shearwaters were old-Bluetooth only, more recent ones BLE-only.
for those here .... 5 minutes w subsurface board Not good news for my use case... ( means we cannot get clean dive logs in under 1 minute from the device )
retarded design issue but they saved money on NFC pads and other items which would have been beneficial for my use cases -- but it explains my problem from JUMP I am pissed at myself now and more enraged at shearwater than 10 minutes ago... because this was a known issue then.
(a) doing a "bonding" pair seems to help some people, but it
shouldn't be necessary, and it causes its own set of issues.
In particular, what happens is that "bonding" creates a long-term key
for the pairing, and from all that I can figure out, the Shearwater
will forget that key (and thus stop responding to a bonded connection
attempt) if it is turned off.
Now, "turned off" is the key here. If you have been diving recently,
and the shearwater is still tracking any deco at all (which will take
days), then it won't actually shut off unless you take the batteries
out for a while.
But if you haven't been diving, and are just using your shearwater for
testing (or you do the download after you get home, several days after
the last dive), then any "screen off" will be a power off event.
End result: you don't _have_ to always re-pair with the Shearwater
dive computers, but re-pairing should fix the "desktop thinks it's
bonded, but the shearwater isn't, and they won't communicate until you
unpair and re-pair".
(b) The shearwater bluetooth stack isn't a real bluetooth stack, and
it resets some state at every "start bluetooth", and it won't accept
more than one pairing or connection attempt per such a session.
So if you have problems downloading, you need to *exit* the shearwater
bluetooth mode, and start again, because otherwise if the shearwater
thinks somebody has connected to it (from a previous failed download),
it won't accept a new connection. Same for pairing.
(b) the shearwater BT stack is _slow_. The new "Petrel Native Format"
makes things worse, because it's much chattier (and yes, I suspect
libdivecomputer probably downloads too much, making the problem even
worse).
groups.google.com