Importing Dives from Shearwater Pursuit

[Michael Ionescu]

Hi all,

I own a Shearwater Pursuit and don't find it as a selection in the import dialog.

Is this computer supported through another selection?

Or is it possible to import dives from Shearwater Desktop?

Or is it possible to import dives from Shearwater Cloud?

I do realize that this is an old model, but they are still in circulation, in particular integrated into certain older model rebreathers.

Thanks,
Michael

[Jef Driesen]

I don't know for sure, but I suspect the Pursuit uses the same protocol as the
Predator. If that's indeed the case, it shouldn't be difficult to get it
supported. If I'm correct, the Pursuit uses IrDA (infrared) instead of bluetooth
communication. That means subsurface won't work out of the box.

I assume you are using Windows and have IrDA communication working (with
Shearwater Desktop)?

In that case, you can try with the libdivecomputer command-line tool:

https://libdivecomputer.org/builds/stable/windows/dctool.exe

First scan for available IrDA devices:

dctool.exe -vv -l scan.log scan -t irda

Note the address of the Pursuit, and then try to download:

dctool.exe -vv -l dump.log -f predator dump -o dump.bin -t irda <address>

Email me the two log files.

Jef

[Michael Ionescu]

Jef,

thanks for your encouraging message.

No, I actually didn't have communication yet. The current versions of Shearwater's Desktop and Cloud SW no longer support their Pursuit model, and I have not yet dug deep enough to excavate an older, compatible version.

I have so far been using Subsurface with my OSTC 2 and am hoping for some guidance perhaps from other Pursuit users.

But to try to analyze the connection with your tool, I have done the following:

1. Follow https://dataloggerinc.com/resource-article/irda-dongle-win-10/

2. Windows-Update -> Optional Updates -> Drivers -> IrDA

3. reboot

4. Find the USB IrDA Dongle properly installed, purportedly working, and sporting USB\VID_9710&PID_7780&REV_0001.
   

Sadly, dctool.exe -vv -l scan.log scan -t irda outputs only the timestamp and version, both on command line and in the logfile.

C:\Users\Michael\Downloads>dctool.exe -vv -l scan.log scan -t irda
DATETIME 2022-06-18T22:26:31Z (1655591191)
VERSION 0.7.0-devel (6ef72ab4203f8bf6189f0e2c81e9a15b4ae771c5)

C:\Users\Michael\Downloads>

Or do I need to have an active connection with the DC for dctool to detect?

Michael

[cyberdiam...@gmail.com]

You will need to have the Pursuit in download mode for it to work.

Steve

[Michael Ionescu]

Having the Pursuit in log-upload-mode facing the IR-dongle didn't change a thing.

I may still be having issues with the dongle/driver.

1) The driver install log C:\Windows\INF\SetupAPI.Dev.log shows one possibly relevant error:

>>>  [Device Install (DiShowUpdateDevice) - USB\VID_9710&PID_7780\5&2232045E&0&1]
>>>  Section start 2022/06/19 08:49:45.689
      cmd: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc
     dvi: {DIF_UPDATEDRIVER_UI} 08:49:45.692
     dvi:      Default installer: Enter 08:49:45.693
     dvi:      Default installer: Exit
     dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 08:49:45.694
     ndv: {Update Driver Software Wizard - USB\VID_9710&PID_7780\5&2232045E&0&1}
!    ndv:      Searching Windows Update has been disabled for the Update Wizard.
!    ndv:      Policy has been set to prevent searching Windows Update for drivers.
     ndv:      Search options: 0x00000011
     ndv:      Searching currently installed INF
     dvi:      {Build Driver List} 08:50:01.524
     dvi:           Searching for hardware ID(s):
     dvi:                usb\vid_9710&pid_7780&rev_0001
     dvi:                usb\vid_9710&pid_7780
     dvi:           Searching for compatible ID(s):
     dvi:                usb\class_ff&subclass_00&prot_ff
     dvi:                usb\class_ff&subclass_00
     dvi:                usb\class_ff
     dvi:      {Build Driver List - exit(0x00000000)} 08:50:01.530
     ndv:      Recursively searching directory 'C:\Users\Michael\Downloads\MosChip 7780-USBFIR Adapter Driver V.1.3.0.0 2007-08-16'
     dvi:      {Build Driver List} 08:50:01.541
     dvi:           Searching for hardware ID(s):
     dvi:                usb\vid_9710&pid_7780&rev_0001
     dvi:                usb\vid_9710&pid_7780
     dvi:           Searching for compatible ID(s):
     dvi:                usb\class_ff&subclass_00&prot_ff
     dvi:                usb\class_ff&subclass_00
     dvi:                usb\class_ff
     sig:           {_VERIFY_FILE_SIGNATURE} 08:50:01.635
     sig:                Key      = mosirusb.inf
     sig:                FilePath = c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf
     sig:                Catalog  = c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\MosIrUsb64.cat
     sig:                Success: File is signed in catalog.
     sig:           {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 08:50:01.670
     dvi:           Created Driver Node:
     dvi:                HardwareID   - USB\VID_9710&PID_7780
     dvi:                InfName      - c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf
     dvi:                DevDesc      - USB-Infrared Adapter
     dvi:                Section      - MosIrUsb.Dev.NT
     dvi:                Rank         - 0x00ff0001
     dvi:                Signer Score - WHQL
     dvi:                DrvDate      - 05/18/2007
     dvi:                Version      - 1.3.0.0
     dvi:      {Build Driver List - exit(0x00000000)} 08:50:01.676
     dvi:      {DIF_SELECTBESTCOMPATDRV} 08:50:01.676
     dvi:           Default installer: Enter 08:50:01.677
     dvi:                {Select Best Driver}
     dvi:                     Class GUID of device changed to: {6bdd1fc5-810f-11d0-bec7-08002be2092f}.
     dvi:                     Selected Driver:
     dvi:                          Description - USB-Infrared Adapter
     dvi:                          InfFile     - c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf
     dvi:                          Section     - MosIrUsb.Dev
     dvi:                {Select Best Driver - exit(0x00000000)}
     dvi:           Default installer: Exit
     dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 08:50:01.685
     sto:      {Setup Import Driver Package: c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf} 08:50:01.698
     inf:           Provider: MosChip Semiconductor Technology
     inf:           Class GUID: {6bdd1fc5-810f-11d0-BEC7-08002BE2092F}
     inf:           Driver Version: 05/18/2007,1.3.0.0
     inf:           Catalog File: MosIrUsb64.cat
     sto:           {Copy Driver Package: c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf} 08:50:01.709
     sto:                Driver Package = c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf
     sto:                Flags          = 0x00000007
     sto:                Destination    = C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}
     sto:                Copying driver package files to 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}'.
     flq:                {FILE_QUEUE_COMMIT} 08:50:01.716
     flq:                     Copying 'c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\mosirusb.inf' to 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\mosirusb.inf'.
     flq:                     Copying 'c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\MosIrUsb.sys' to 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\MosIrUsb.sys'.
     flq:                     Copying 'c:\users\michael\downloads\moschip 7780-usbfir adapter driver v.1.3.0.0 2007-08-16\MosIrUsb64.cat' to 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\MosIrUsb64.cat'.
     flq:                {FILE_QUEUE_COMMIT - exit(0x00000000)} 08:50:01.757
     sto:           {Copy Driver Package: exit(0x00000000)} 08:50:01.757
     ump:           Import flags: 0x00000000
     pol:           {Driver package policy check} 08:50:01.819
     pol:           {Driver package policy check - exit(0x00000000)} 08:50:01.820
     sto:           {Stage Driver Package: C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\mosirusb.inf} 08:50:01.821
     inf:                {Query Configurability: C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\mosirusb.inf} 08:50:01.834
     inf:                     Driver package 'mosirusb.inf' is configurable.
     inf:                {Query Configurability: exit(0x00000000)} 08:50:01.839
     flq:                {FILE_QUEUE_COMMIT} 08:50:01.840
     flq:                     Copying 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\mosirusb.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{698c03da-8787-574b-b6c4-246e755af6b9}\mosirusb.inf'.
     flq:                     Copying 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\MosIrUsb.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{698c03da-8787-574b-b6c4-246e755af6b9}\MosIrUsb.sys'.
     flq:                     Copying 'C:\Users\Michael\AppData\Local\Temp\{b59341fa-a8b5-6b4f-bfc0-0515be654b2e}\MosIrUsb64.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{698c03da-8787-574b-b6c4-246e755af6b9}\MosIrUsb64.cat'.
     flq:                {FILE_QUEUE_COMMIT - exit(0x00000000)} 08:50:01.871
     sto:                {DRIVERSTORE IMPORT VALIDATE} 08:50:01.873
     sig:                     Driver package catalog is valid.
     sig:                     {_VERIFY_FILE_SIGNATURE} 08:50:01.898
     sig:                          Key      = mosirusb.inf
     sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{698c03da-8787-574b-b6c4-246e755af6b9}\mosirusb.inf
     sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{698c03da-8787-574b-b6c4-246e755af6b9}\MosIrUsb64.cat
     sig:                          Success: File is signed in catalog.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 08:50:01.905
     sto:                {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 08:50:01.910
     sig:                Signer Score  = 0x0D000005 (WHQL)
     sig:                Signer Name   = Microsoft Windows Hardware Compatibility Publisher
     sig:                Submission ID = 1272178
     sto:                {Core Driver Package Import: mosirusb.inf_amd64_a8384f40e03f7d64} 08:50:01.915
     sto:                     {DRIVERSTORE IMPORT BEGIN} 08:50:01.916
     sto:                     {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 08:50:01.916
     cpy:                     {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{698c03da-8787-574b-b6c4-246e755af6b9}} 08:50:01.917
     cpy:                          Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\mosirusb.inf_amd64_a8384f40e03f7d64
     cpy:                     {Copy Directory: exit(0x00000000)} 08:50:01.920
     idb:                     {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mosirusb.inf_amd64_a8384f40e03f7d64\mosirusb.inf} 08:50:01.921
     idb:                          Created driver package object 'mosirusb.inf_amd64_a8384f40e03f7d64' in DRIVERS database node.
     idb:                          Created driver INF file object 'oem133.inf' in DRIVERS database node.
     idb:                          Registered driver package 'mosirusb.inf_amd64_a8384f40e03f7d64' with 'oem133.inf'.
     idb:                     {Register Driver Package: exit(0x00000000)} 08:50:01.926
     idb:                     {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mosirusb.inf_amd64_a8384f40e03f7d64\mosirusb.inf} 08:50:01.926
     idb:                          Activating driver package 'mosirusb.inf_amd64_a8384f40e03f7d64'.
     cpy:                          Published 'mosirusb.inf_amd64_a8384f40e03f7d64\mosirusb.inf' to 'oem133.inf'.
     idb:                          Indexed 2 device IDs for 'mosirusb.inf_amd64_a8384f40e03f7d64'.
     sto:                          Flushed driver database node 'DRIVERS'. Time = 15 ms
     sto:                          Flushed driver database node 'SYSTEM'. Time = 0 ms
     idb:                     {Publish Driver Package: exit(0x00000000)} 08:50:01.948
     sto:                     {DRIVERSTORE IMPORT END} 08:50:01.951
     dvi:                          Flushed all driver package files to disk. Time = 16 ms
     sig:                          Installed catalog 'MosIrUsb64.cat' as 'oem133.cat'.
     sto:                     {DRIVERSTORE IMPORT END: exit(0x00000000)} 08:50:02.086
     sto:                {Core Driver Package Import: exit(0x00000000)} 08:50:02.087
     sto:           {Stage Driver Package: exit(0x00000000)} 08:50:02.088
     sto:      {Setup Import Driver Package - exit (0x00000000)} 08:50:02.170
     dvi:      Searching for hardware ID(s):
     dvi:           usb\vid_9710&pid_7780&rev_0001
     dvi:           usb\vid_9710&pid_7780
     dvi:      Searching for compatible ID(s):
     dvi:           usb\class_ff&subclass_00&prot_ff
     dvi:           usb\class_ff&subclass_00
     dvi:           usb\class_ff
     dvi:      Class GUID of device changed to: {6bdd1fc5-810f-11d0-bec7-08002be2092f}.
     ump:      {Plug and Play Service: Device Install for USB\VID_9710&PID_7780\5&2232045E&0&1}
     dvi:           {Core Device Install} 08:50:02.207
     utl:                {Select Drivers - USB\VID_9710&PID_7780\5&2232045E&0&1} 08:50:02.212
     utl:                     Driver Node:
     utl:                          Status         - Selected
     utl:                          Driver INF     - oem133.inf (C:\WINDOWS\System32\DriverStore\FileRepository\mosirusb.inf_amd64_a8384f40e03f7d64\mosirusb.inf)
     utl:                          Class GUID     - {6bdd1fc5-810f-11d0-bec7-08002be2092f}
     utl:                          Driver Version - 05/18/2007,1.3.0.0
     utl:                          Configuration  - USB\VID_9710&PID_7780
     utl:                          Driver Rank    - 00FF0001
     utl:                          Signer Score   - WHQL (0D000005)
     utl:                {Select Drivers - exit(0x00000000} 08:50:02.218
     dvi:                {Configure Device - USB\VID_9710&PID_7780\5&2232045E&0&1} 08:50:02.220
     dvi:                     Device Status: 0x01806400 [0x1c - 0xc0000490]
     dvi:                     Config Flags: 0x00000060
     dvi:                     Parent Device: USB\ROOT_HUB30\4&25d1c80b&0&0
     sto:                     {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mosirusb.inf_amd64_a8384f40e03f7d64\mosirusb.inf}
     sto:                          Source Filter  = USB\VID_9710&PID_7780
     inf:                          Class GUID     = {6bdd1fc5-810f-11d0-bec7-08002be2092f}
     inf:                          Class Options  = Configurable
     inf:                          {Configure Driver: USB-Infrared Adapter}
     inf:                               Section Name = MosIrUsb.Dev.NT
     inf:                               {Add Service: MosIrUsb}
     inf:                                    Start Type    = 3
     inf:                                    Service Type  = 1
     inf:                                    Error Control = 1
     inf:                                    Image Path    = \SystemRoot\System32\drivers\MosIrUsb.sys
     inf:                                    Display Name  = MosIrUsb.sys
     inf:                                    Group         = NDIS
     inf:                                    Updated service 'MosIrUsb'.
     inf:                               {Add Service: exit(0x00000000)}
     inf:                               Hardware Id  = USB\VID_9710&PID_7780
     inf:                               {Configure Driver Configuration: MosIrUsb.Dev.NT}
     inf:                                    Service Name  = MosIrUsb
     inf:                                    Config Flags  = 0x00000000
     inf:                               {Configure Driver Configuration: exit(0x00000000)}
     inf:                          {Configure Driver: exit(0x00000000)}
     flq:                          {FILE_QUEUE_COMMIT} 08:50:02.266
     flq:                               Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\mosirusb.inf_amd64_a8384f40e03f7d64\MosIrUsb.sys' to 'C:\WINDOWS\System32\drivers\MosIrUsb.sys'.
     cpy:                               Existing file 'C:\WINDOWS\System32\drivers\MosIrUsb.sys' remains unchanged.
     flq:                          {FILE_QUEUE_COMMIT - exit(0x00000000)} 08:50:02.282
     sto:                     {Configure Driver Package: exit(0x00000000)}
     dvi:                     Install Device: Configuring device. 08:50:02.284
     dvi:                          Configuration: oem133.inf:USB\VID_9710&PID_7780,*
     dvi:                     Install Device: Configuring device completed. 08:50:02.299
     dvi:                     Device Status: 0x01806000
     dvi:                     Install Device: Starting device 'USB\VID_9710&PID_7780\5&2232045E&0&1'. 08:50:02.307
     dvi:                     Install Device: Starting device completed. 08:50:02.500
!    dvi:                     Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
     dvi:                {Configure Device - exit(0x00000000)} 08:50:02.505
     dvi:           {Core Device Install - exit(0x00000000)} 08:50:02.509
     dvi:           Waiting for device post-install to complete. 08:50:02.511
     dvi:           Device post-install completed. 08:50:02.684
     dvi:           Device Status: 0x0180600a
     ump:      {Plug and Play Service: Device Install exit(00000000)}
     ndv:      {Install Related Drivers} 08:50:02.701
     ndv:      {Install Related Drivers: exit(0x00000000)} 08:50:02.704
     dvi:      {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 08:50:02.725
     dvi:           Default installer: Enter 08:50:02.726
     dvi:           Default installer: Exit
     dvi:      {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 08:50:02.727
     ndv: {Update Driver Software Wizard exit(00000000)}
<<<  Section end 2022/06/19 08:50:08.502
<<<  [Exit status: SUCCESS]

2) Also, whenever I plug in the IrDA Adapter, the HW-Manager shows a "Device not migrated" event:

3) Also, I've found comment on the web that say, that when an IrDA device is plugged in, it's supposed to start blinking. Mine doesn't, but I'm not sure it's supposed to. It's hard to tell whether there's a status LED under the cap.
It's a CABLES UNLIMITED USB-1510 USB to IRDA Adapter for which there does not seem to be a manual on the web.

I've contacted both the previous owner and the manufacturer about a version of Shearwater Desktop that still supported this interface and we'll see what comes of it.

In the mean time, if you guys have any comments on the above issues...

Michael

[Michael Ionescu]

Everything from my last post has been cleared up. I have been able to upload the logs from the Pursuit to Shearwater Desktop via IrDA and dctool  is finding the IrDA address:

> ./dctool.exe -vv -l scan.log scan -t irda
DATETIME 2022-06-19T19:38:58Z (1655667538)
VERSION 0.7.0-devel (6ef72ab4203f8bf6189f0e2c81e9a15b4ae771c5)
INFO: Discover: address=b5b5b5b5, name=Generic IrDA, charset=00, hints=9004
b5b5b5b5        Generic IrDA

However, it can not connect to the DC:

> ./dctool.exe -vv -l dump.log -f predator dump -o dump.bin -t irda b5b5b5b5
DATETIME 2022-06-19T19:39:05Z (1655667545)
VERSION 0.7.0-devel (6ef72ab4203f8bf6189f0e2c81e9a15b4ae771c5)
Opening the I/O stream (irda, b5b5b5b5).
ERROR: No valid device address specified. [in examples/common.c:498 (dctool_irda_open)]
ERROR: Error opening the I/O stream. [in examples/dctool_dump.c:55 (dump)]
ERROR: No device found

When I put the Pursuit in log upload mode, Windows finds it and offers to transfer files to it. IR-connectivity is therefore a given.

I've attached all the files dctool wrote.

Michael

[Jef Driesen]

On 19/06/2022 21:53, 'Michael Ionescu' via Subsurface Divelog wrote:
> Everything from my last post has been cleared up. I have been able to upload the
> logs from the Pursuit to Shearwater Desktop via IrDA and dctool  is finding the
> IrDA address:
>
>> ./dctool.exe -vv -l scan.log scan -t irda
> DATETIME 2022-06-19T19:38:58Z (1655667538)
> VERSION 0.7.0-devel (6ef72ab4203f8bf6189f0e2c81e9a15b4ae771c5)
> INFO: Discover: address=b5b5b5b5, name=Generic IrDA, charset=00, hints=9004
> b5b5b5b5        Generic IrDA

Great, that means the driver is working and the device is detected. The name is
a bit strange. I would have expected something like "Pursuit" here. That just
means autodetection won't work. Not a big deal because most people won't have
multiple IrDA devices connected :-)

> However, it can not connect to the DC:
>
>> ./dctool.exe -vv -l dump.log -f predator dump -o dump.bin -t irda b5b5b5b5
> DATETIME 2022-06-19T19:39:05Z (1655667545)
> VERSION 0.7.0-devel (6ef72ab4203f8bf6189f0e2c81e9a15b4ae771c5)
> Opening the I/O stream (irda, b5b5b5b5).
> ERROR: No valid device address specified. [in examples/common.c:498
> (dctool_irda_open)]
> ERROR: Error opening the I/O stream. [in examples/dctool_dump.c:55 (dump)]
> ERROR: No device found

My mistake. I forgot dctool expects the address to be a hexadecimal number, and
thus needs to be passed with the "0x" prefix 0xb5b5b5b5. Just passing no address
at all will probably work too, because then it should pick the first device it
finds.

Can you try again with 0xb5b5b5b5 as the address?

Jef

[Michael Ionescu]

Jef,

we have limited success!

Connect was established both with explicit address and without, however there seems to have been a protocol change between Pursuit and Predator:

[0.000019] DATETIME 2022-06-19T20:23:15Z (1655670195)
[0.000175] VERSION 0.7.0-devel (6ef72ab4203f8bf6189f0e2c81e9a15b4ae771c5)
[0.000648] Opening the I/O stream (irda, 0xb5b5b5b5).
[0.000750] INFO: Open: address=b5b5b5b5, lsap=1
[0.649307] Opening the device (Shearwater Predator).
[0.649513] INFO: Timeout: value=3000
[0.649891] INFO: Sleep: value=300
[0.961788] Registering the event handler.
[0.961923] Registering the cancellation handler.
[0.962347] Downloading the memory dump.
[0.962478] Event: progress 0.00% (0/10000)
[0.963706] INFO: Write: size=15, data=FF010B00350034DD000000020080C0
[1.356758] INFO: Read: size=1, data=00
[1.356899] INFO: Read: size=1, data=00
[1.357251] INFO: Read: size=1, data=01
[1.357350] INFO: Read: size=1, data=00
[1.357439] INFO: Read: size=1, data=04
[1.357534] INFO: Read: size=1, data=02
[1.357630] INFO: Read: size=1, data=00
[1.357717] INFO: Read: size=1, data=06
[1.357825] INFO: Read: size=1, data=00
[1.357925] INFO: Read: size=1, data=01
[1.358024] INFO: Read: size=1, data=04
[1.358117] INFO: Read: size=1, data=01
[1.358206] INFO: Read: size=1, data=01
[1.358301] INFO: Read: size=1, data=01
[4.357845] INFO: Read: size=0, data=
[4.357960] ERROR: Failed to receive the packet. [in src/shearwater_common.c:239 (shearwater_common_slip_read)]
[4.358293] ERROR: Failed to receive the response packet. [in src/shearwater_common.c:358 (shearwater_common_transfer)]
[4.358387] ERROR: Error downloading the memory dump. [in examples/dctool_dump.c:100 (dump)]
[4.359249] ERROR: Timeout

There was no binary dump file.

BTW, I have now been able to do XML Exports of individual dives from Shearwater Desktop and import them to Subsurface as a pain-in-the-butt workaround.

Michael

[Jef Driesen]

The low-level IrDA communication is working, but it looks like the
Pursuit protocol is different after all. At this point I have no idea
whether is something completely different of just a small change.

With Shearwater Desktop the communication is done with a separate helper
tool (located in the bin subdirectory of the installation directory).
Can you try to execute this manually, and send the output it generates,
including the log file:

ShearwaterConnectorPC.exe -p irda -l shearwater.log

(I don't remember exactly, it's possible the -p should be -b).

Jef

[Michael Ionescu]

I tried both incantations and all I got was a timeout on the PC and a DC waiting for connect.

C:\Program Files (x86)\Shearwater Research\Shearwater Desktop\bin>ShearwaterConnectorPC.exe -p irda -l pursuit1.log
[Info #100] Connecting to dive computer...
[Error #170] Connect to dive computer timed out.
^C

ShearwaterConnectorPC.exe seems to silently ignore superfluous parameters, so I am not sure whether these were right in the first place. No log appeared and I cancelled the process after a minute or so.

[Jef Driesen]

On 21/06/2022 18:49, 'Michael Ionescu' via Subsurface Divelog wrote:
> I tried both incantations and all I got was a timeout on the PC and a DC waiting
> for connect.
>
> C:\Program Files (x86)\Shearwater Research\Shearwater
> Desktop\bin>ShearwaterConnectorPC.exe -p irda -l pursuit1.log
> [Info #100] Connecting to dive computer...
> [Error #170] Connect to dive computer timed out.
> ^C
>
> ShearwaterConnectorPC.exe seems to silently ignore superfluous parameters, so I
> am not sure whether these were right in the first place. No log appeared and I
> cancelled the process after a minute or so.

I double checked, and the "-p irda" was correct.

Maybe try something else. The shearwater database is stored in this directory:

C:\Users\<username>\AppData\Roaming\com.shearwaterresearch.divebook\Local Store

Can you send me those files, after doing a download, so I can have a look what's
in there? Just zip the whole directory. You can send it private if you don't
want to share your data with the rest of the world.

Jef