You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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?
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
The text was updated successfully, but these errors were encountered: