Mares Puck Pro will not connect.

[B]

Hi all,

I have a Mares Puck Pro and USB cable.  The Puck Pro is put into PC Ready Mode, and the USB connector glows green when connected to a USB port.
I have tried connecting with Windows 10 (64-bit), Linux (Ubuntu and Debian), and Mac OS X El Capitan.
I am able to find the connected dive computer on all four computers and OSes.  Irregardless of the OS, I get the same error of "Failed to receive the answer".  I post
the Mac OS X log here, but I get the same error for all operating systems.  The error says it is accessing the mares_iconhd.c code.
The attached screen shot shows that I am selecting the Puck Pro.  I would appreciate any advice or experiences to get this working.
I have tried the Mares dive software on Windows 10, and it will not connect (within the software) either.  But I can
see the device on COM3 under the Windows control panel -> devices.


INFO: Open: name=/dev/tty.Bluetooth-Incoming-Port
INFO: Configure: baudrate=115200, databits=8, parity=2, stopbits=0, flowcontrol=0
INFO: Timeout: value=1000
INFO: DTR: value=0
INFO: RTS: value=0
INFO: Purge: direction=3
INFO: Write: size=2, data=C267
INFO: Read: size=0, data=
ERROR: Failed to receive the answer. [in ../../src/mares_iconhd.c:167 (mares_iconhd_transfer)]

[Jef Driesen]

On 03-03-17 16:01, B wrote:
> I have a Mares Puck Pro and USB cable. The Puck Pro is put into PC Ready Mode,
> and the USB connector glows green when connected to a USB port.
> I have tried connecting with Windows 10 (64-bit), Linux (Ubuntu and Debian), and
> Mac OS X El Capitan.
> I am able to find the connected dive computer on all four computers and OSes.
> Irregardless of the OS, I get the same error of "Failed to receive the answer".
> I post
> the Mac OS X log here, but I get the same error for all operating systems. The
> error says it is accessing the mares_iconhd.c code.
> The attached screen shot shows that I am selecting the Puck Pro. I would
> appreciate any advice or experiences to get this working.

Have you installed the driver?

> I have tried the Mares dive software on Windows 10, and it will not connect
> (within the software) either. But I can
> see the device on COM3 under the Windows control panel -> devices.

This sounds like a low battery problem. (Or a missing driver.)

> INFO: Open: name=/dev/tty.Bluetooth-Incoming-Port

This is certainly the wrong serial port!

Jef

[B]

Hi Jef,

Thanks for responding.  I'm now using my main Windows 10 (64-bit) machine with Subsurface 4.6.3.

Yes, I have the latest Silicon Labs CP210x USB to UART Bridge drive installed.  When I go to the Mares website:

http://www.computermares.com/index.php?/Knowledgebase/Article/View/73/32/cp210x-driver-xp-s2k3-vista-windows-7-8-and-10

and download and run the executable, I get the message that the driver is already installed.  I have attached a screenshot

of my hardware setup showing the driver version.

The Mares Puck Pro I have only has 20 dives on it, and the Battery status level says it is OK.

Searching through some Amazon comments, a user noted that for the Mares Dive Link 2 cable I'm using,

it will glow green when the USB is powering it, and then red when a successful connection is made.

The light has yet to turn red, so that is certainly a problem!

My Windows 10 screen shot of Subsurface and the error is also attached.

The dive computer is in PC Ready mode.

For Windows, the subsurface.log:

INFO: Open: name=COM3

INFO: Configure: baudrate=115200, databits=8, parity=2, stopbits=0, flowcontrol=0

INFO: Timeout: value=1000

INFO: DTR: value=0

INFO: RTS: value=0

INFO: Purge: direction=3

INFO: Write: size=2, data=C267

INFO: Read: size=1, data=0F

ERROR: Unexpected answer byte. [in /home/hohndel/src/win/libdivecomputer/src/mares_iconhd.c:173 (mares_iconhd_transfer)]

-B.

[Jef Driesen]

Looks like a bad connection, a low battery or some other hardware
problem. Note that the PC interface typically requires more power than
what is needed for diving. So it's perfectly possible to have enough
power left for diving, but not for the PC interface. This is a very
common problem.

The fact that you also can't download with the Mares application
suggests it's not a problem with subsurface/libdivecomputer, but with
your system or your dive computer. And since you see the problem on
multiple systems, I would say it's the dive computer.

Jef

[B]

Thanks Jef.

I replaced the battery in the dive computer, and the log is still intact.  The dive computer will still not connect to the PC, the cable is still glowing
green and not red.   So it must the be the dive computer or cable.  The dive computer works fine in the water.  I will probably return the cable/connector
and try a new cable from a different vendor.

Your troubleshooting was appreciated!

[Philippe Massart]

Hello, 

Did you connect the Mares adapter directly to the computer? From my experience, it works far better when using an USB hub (its external alimentation), rather than direct plugging to the computer (at least, it was the case with my mac).

Philippe

[B]

Hello Philippe,

I tried connecting it to my Windows 10 PC via a hub as well as all six USB ports on the front and back of the computer, both USB 2.0 and 3.0.  It did not work.    I will try with the hub via my Mac next.

Many thanks,

B.