That said, I decided to look at what the WebSync software was written in. I had a sneaking suspicion that it might be.
NET — I was right! So, I decided to look under the hood and see if I could tackle writing my own front end to their devices.
I started by pulling in the obvious assemblies to see what was built. The project looked reasonably well built. There was enough evidence ot see that there was at least SOME design put into the application. I even found some tests in tone assembly — at least there were some tests checked that off on their requirements eh?
So I started drilling down into WebSync. I found a Polar. Program class with a static Main method. Bingo — my entry point. I immediately saw some minor concerns. For instance, they were using a Mutex to provide the functionality of a Singleton pattern. Worse yet, they were calling GC. KeepAlive on the Mutex. They did, however, have what looked like an external exception reporting framework, so that at least gave me SOME hope. I found Application.
Oh my! I closed my eyes and looked again. I closed then and then looked one more time. Tell me what you see wrong with this:. These guys are on crack! They have a retry counter that apparently will never be more than 1. Because the tick event will go away and there is no loop in this code, the retryCount will always be 1 taking note that they decided to start with a 1-based counting system rather than zero because n-1 is a bit complex.
This is insane! I have no idea how this even works. I can only hope that, as I dig in further WristUnitListener actually works the way it is supposed to and the only thing that sucks is the WebForms code. I was able to successfully hack around with the API and get data off the watch with little effort. The trick was to working around some wonky and non-working APIs.
As you can see by the image, I can even pull the bitmap logo off of the watch and, if I so desire, set it. This is far from complete but I will work it over some this week and this weekend before publishing the source on Codeplex. I have posted this code to codeplex as-is. Is there anywhere in the code for the upload settings — trying to get the software working via a proxy server is a nightmare as there is nowhere to set username and password for the proxy to use.
Tobin, You are my hero. That was awesome. You rock! I might write my own driver and get rid off de Polar SW altogether. Being it. NET makes that a little easier ;o Thanks, man. There are a lot of people screaming for a way of getting access to their raw polar hrm data… Great to see someone doing some work in this area….
Thanks everyone. Seems to have been a lot of sudden interest in this topic this week. I will post my code tonight on codeplex and try to get something better out soon. It will provide at least a starting point, I think. Did you put it on CodeP? Thank U very much! Thats cool. I tried it 3 times, but still this error. If U select more than one session in the calender to delete. Are you sure you wish to do this? If U select session, it will ask times;.
She uses iSmartTrain now with her S I just want to confirm this point to buy a Flowlink and register the iSmartTrain. Thanks a million. Out of curiosity i tried it with mine, seems to pull back the data but he date formats are messed up all the time stamps are set as either or Double checked my watch and the settings appear to be fine locally so assume its a different format than the RSx. The FlowLink is not recognized as option in the download menu.
On the FlowLink, the data led shines orange, and the align led shines green — therefore assume the FlowLink is healthy. Using version 3. To download from the FR60, you need to use Garmin Connect. Your email address will not be published. Save my name, email, and website in this browser for the next time I comment.
Skip to content. Home About. This entry was posted in Uncategorized. Bookmark the permalink. Thanks for help. Stuart Tevendale says:. Thanks Stuart. Could it be because I use the trial version?
0コメント