Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PoolMatePlus #43

Open
ptd006 opened this issue Apr 10, 2017 · 2 comments
Open

PoolMatePlus #43

ptd006 opened this issue Apr 10, 2017 · 2 comments

Comments

@ptd006
Copy link

ptd006 commented Apr 10, 2017

Hi,

I just bought the PoolMatePlus (released late 2016). It uses the same FTDI USB to serial chip and USB product/vendor code as the "type A" pod. However I guess the protocol or data format are different as I cannot get it working with your code. Are there any plans to add support for this new watch? I don't want to duplicate efforts.

Thanks for your work on this,
Peter

@ihewitt
Copy link
Owner

ihewitt commented Apr 24, 2017

Apologies, didn't respond to this sooner.
It should be simple to add support with a dump of the transfer data.
Firstly can you try building and running the "qttest.cpp" file in the contrib directory. The command line to build is in the comment at the top of the file.

@ptd006
Copy link
Author

ptd006 commented Jun 25, 2018

Hi Ivor,
no worries about reply lag!

I can dump data from the pod with gtkterm and the format looks like the Pod A format from skimming the code.

However, I can't get the latest code to even read from the pod! The right port (/dev/ttyUSB0) is returned correctly by find() and opens successfully. The set RTS and DTS functions return true as expected. However handleReadyRead is simply never called.

I checked the code is using exactly the same port parameters as I use in gtkterm. Moreover, the old precompiled binary (poolview_0.5_amd64.deb, dated 23 October 2015) from OBS can download and parse the data so I'm confused as there seem only minor changes in the code from then.

Any tips before I spend more time with it?

OT: for the Strava upload is there no "official" client ID for poolviewer?

Cheers,
Peter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants