Re: investigating BT problem MacBook Pro <-> Aqualung i770R
Wireshark also runs on a mac. It might work, never used it for BT troubleshooting. Kind regards, Martin de Weger > Op 30 mei 2022 om 18:12 heeft Daniel Azuelos via subsurface > het volgende geschreven: > > [ Rédigé dans le sens de lecture normal. > Written in the usual reading direction. ] > > Le (on) 30/05/2022, Jef Driesen a écrit (wrote): > > | I'm afraid I can't help you with that part. I don't know any Mac tools. > > I am rather looking for Unix env. tools, like ping, tcpdump, nmap, Wireshark, > I am not at ease with Apple tools which don't help to debug real problems. > -- >« The only thing necessary for the triumph of evil >is for good men to do nothing. » >Edmund Burke > > daniel Azuelos > ___ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: investigating BT problem MacBook Pro <-> Aqualung i770R
[ Rédigé dans le sens de lecture normal. Written in the usual reading direction. ] Le (on) 30/05/2022, Jef Driesen a écrit (wrote): | I'm afraid I can't help you with that part. I don't know any Mac tools. I am rather looking for Unix env. tools, like ping, tcpdump, nmap, Wireshark, I am not at ease with Apple tools which don't help to debug real problems. -- « The only thing necessary for the triumph of evil is for good men to do nothing. » Edmund Burke daniel Azuelos ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: investigating BT problem MacBook Pro <-> Aqualung i770R
On 29/05/2022 13:50, Daniel Azuelos via subsurface wrote: [ Rédigé dans le sens de lecture normal. Written in the usual reading direction. ] Le (on) 29/05/2022, Jef Driesen a écrit (wrote): [...] | This is a problem at the bluetooth (or driver) layer. Subsurface is unable | to connect, so we don't even get a chance to communicate with the dive | computer. Thank you Jef, clear. Which tool would you recommand as a kind of ping or nmap on the Bluetooth field? Which method could help me diagnose if this is coming from MacOS ( not sending ) or the i770R ( not answering )? I'm afraid I can't help you with that part. I don't know any Mac tools. Jef ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: investigating BT problem MacBook Pro <-> Aqualung i770R
[ Rédigé dans le sens de lecture normal. Written in the usual reading direction. ] Le (on) 29/05/2022, Jef Driesen a écrit (wrote): [...] | This is a problem at the bluetooth (or driver) layer. Subsurface is unable | to connect, so we don't even get a chance to communicate with the dive | computer. Thank you Jef, clear. Which tool would you recommand as a kind of ping or nmap on the Bluetooth field? Which method could help me diagnose if this is coming from MacOS ( not sending ) or the i770R ( not answering )? -- « The only thing necessary for the triumph of evil is for good men to do nothing. » Edmund Burke daniel Azuelos ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: investigating BT problem MacBook Pro <-> Aqualung i770R
On 27/05/2022 18:23, Daniel Azuelos via subsurface wrote:
Since Subsurface 5.0.8 was crashing sometimes during repeated tests,
I went back to 4.9.7 which seemed to be crash proof in the exact
same radio environment.
Distance from my Mac to the i770R: 30 cm.
i770R RSSI: -62 dB
Nb of other env. BT equipments: 9
best RSSI: -54 dB
Here are my results on 30 attempts to just download from the i770R
and then exit without saving:
success failure
22 8
Strange behaviour: the time to get an answer either success or failure
seems to vary from 2 s to 30 s. Is this coming from the underlying
BT driver?
Here are included 2 subsurface log I got with the -vv arg.
Based on the information in the failure log file:
qt_ble_open( {c7d52420-5e99-4800-a1bc-e5b07b2d0770} )
trying to connect
timeout while trying to connect to the controller
{c7d52420-5e99-4800-a1bc-e5b07b2d0770}
Finishing download thread: "Unable to open LE:{c7d52420-5e99-4800-a1bc-e5b07b2d0770}
Aqualung (i770R)"
This is a problem at the bluetooth (or driver) layer. Subsurface is unable to
connect, so we don't even get a chance to communicate with the dive computer.
Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: investigating BT problem MacBook Pro <-> Aqualung i770R
Since Subsurface 5.0.8 was crashing sometimes during repeated tests,
I went back to 4.9.7 which seemed to be crash proof in the exact
same radio environment.
Distance from my Mac to the i770R: 30 cm.
i770R RSSI: -62 dB
Nb of other env. BT equipments: 9
best RSSI: -54 dB
Here are my results on 30 attempts to just download from the i770R
and then exit without saving:
success failure
22 8
Strange behaviour: the time to get an answer either success or failure
seems to vary from 2 s to 30 s. Is this coming from the underlying
BT driver?
Here are included 2 subsurface log I got with the -vv arg.
--
« The only thing necessary for the triumph of evil
is for good men to do nothing. »
Edmund Burke
daniel Azuelos
Subsurface v4.9.7,
built with libdivecomputer v0.7.0-devel-Subsurface-NG
(d52dfb002d40e70cf77c76bc175c8e1401af8357)
built with Qt Version 5.13.2, runtime from Qt Version 5.13.2
built with libgit2 0.26.0
"validateGL(): created OpenGLContext."
"validateGL(): obtained QOpenGLFunctions."
"validateGL(): detected OpenGL version 2.1."
loading dive data from ("/Users/dan/Library/Application
Support/Subsurface/test_i770R_2022.xml")
Unable to match dive 'program.divelog' (subsurface)
Unable to match dive 'version.divelog' (3)
Unable to match autogroup 'model.divecomputerid.' (Suunto Vyper)
Unable to match autogroup 'deviceid.divecomputerid.' (2cb68919)
Unable to match autogroup 'nickname.divecomputerid.' (Suunto Vyper (2cb68919))
Unable to match autogroup 'model.divecomputerid.' (Mares Puck Pro)
Unable to match autogroup 'deviceid.divecomputerid.' (32291d2f)
Unable to match autogroup 'nickname.divecomputerid.' (prêt de Yann Legros)
Unable to match autogroup 'model.divecomputerid.' (Aqualung i770R)
Unable to match autogroup 'deviceid.divecomputerid.' (5d9d9589)
Unable to match autogroup 'serial.divecomputerid.d.' (010747)
Unable to match autogroup 'model.divecomputerid.' (Suunto Vyper)
Unable to match autogroup 'deviceid.divecomputerid.' (636e9a36)
Unable to match autogroup 'nickname.divecomputerid.' (Suunto Vyper (636e9a36))
Unable to match divecomputerid 'state.autogroup.' (1)
File locations:
Unable to get local git directory
Cloud URL: No valid cloud credentials set.
Image filename table: /Users/dan/Library/Application Support/Subsurface/hashes
Local picture directory: /Users/dan/Library/Application
Support/Subsurface/picturedata/
BTDiscoveryReDiscover: localBtDevice.isValid() true
"BTDiscoveryReDiscover: localDevice noether is powered on, starting discovery"
starting BLE discovery
Starting download from BT
downloading only new dives
still looking scan is still running, we should just wait for a few moments
Found new device: "" "LE:{850d8be4-680c-4025-88d4-90a09a19abd5}"
Not recognized as dive computer
Updating RSSI for "00:00:00:00:00:00" -38
Updating manufacturer data for "00:00:00:00:00:00"
"{fe61--1000-8000-00805f9b34fb}"
Found new device: "" "LE:{e59614db-f0a8-40d7-9ea2-05d5de942aaf}"
Not recognized as dive computer
Found new device: "" "LE:{83656bbf-9a3e-4539-842b-e234e07ae605}"
Not recognized as dive computer
"{cb3c4555-d670-4670-bc20-b61dbc851e9a}"
Found new device: "i770R" "LE:{c7d52420-5e99-4800-a1bc-e5b07b2d0770}"
"this could be a Aqualung i770R"
Updating RSSI for "00:00:00:00:00:00" -66
Found new device: "i770R" "LE:{c7d52420-5e99-4800-a1bc-e5b07b2d0770}"
"this could be a Aqualung i770R"
---> stopping the discovery agent
qt_ble_open( {c7d52420-5e99-4800-a1bc-e5b07b2d0770} )
trying to connect
connected to the controller for device {c7d52420-5e99-4800-a1bc-e5b07b2d0770}
finished service discovery, start discovering characteristics
Found service "{180a--1000-8000-00805f9b34fb}"
.. ignoring standard service
Found service "{180f--1000-8000-00805f9b34fb}"
.. ignoring standard service
Found service "{9e5d1e47-5c13-43a0-8635-82ad38a1386f}"
.. ignoring service Broadcom Upgrade #1
Found service "{cb3c4555-d670-4670-bc20-b61dbc851e9a}"
.. recognized service Pelagic (i770R, i200C, Pro Plus X, Geo 4.0)
starting service characteristics discovery
.. service state changed to QLowEnergyService::DiscoveringServices
.. done discovering services
.. service state changed to QLowEnergyService::ServiceDiscovered
Found service "{cb3c4555-d670-4670-bc20-b61dbc851e9a}" "Unknown Service"
c: "{5ee30931-ccaa-4870-ab32-6b87ef1f78ed}"
c: "{17738114-18db-467c-b15f-a5bdb84025be}"
c: "{6606ab42-89d5-4a00-a8ce-4eb5e1414ee0}"
c: "{a60b8e5c-b267-44d7-9764-837caf96489e}"
d: "{2902--1000-8000-00805f9b34fb}"
c: "{a60b8e5c-b267-44d7-9d65-857bad95479f}"
Using service "{cb3c4555-d670-4670-bc20-b61dbc851e9a}" as preferred service
.. enabling notifications
Using read characteristic "{a60b8e5c-b267-44d7-9764-837caf96489e}"
now writing "0x0100"
