Concept2 Forum

Turns out we were both investigating this around the same time - wish I had seen this sooner. I ended up making a diagram for the bit layout to help map each bit/byte's value to the words concept2 uses in their spec when talking about piece timestamps (the bold text on the left). Initially I was as...

Stroke distance is a collection of bytes broadcast under BLE characteristic 0x0035. Most apps don't command the PM to return this data, instead they subscribe to updates for this characteristic (and pretty much all the characteristics). In this case, the PM sends updates after every stroke and the a...

There is a way. Look in the C2 CSAFE Bluetooth definition and you'll find that it is sent across as an enumerated value under "Erg Machine Type": typedef enum { ERGMACHINE_TYPE_STATIC_D, ERGMACHINE_TYPE_STATIC_C, ERGMACHINE_TYPE_STATIC_A, ERGMACHINE_TYPE_STATIC_B, ERGMACHINE_TYPE_STATIC_E = 5, ERGMA...

I have an app for the C2 that is in a very late state of development. My CSAFE over BT stack works flawlessly in configuring workouts with one exception- utilizing the C2 proprietary wrapper to configure variable interval workouts. Whenever the frame size goes over 120 bytes (I'm aware that is the l...

Alright, after months of banging my head against the wall I found a solution. The "real" GOFINISHED command is C2 proprietary:

[0xF1, 0x76, 0x04, 0x13, 0x02, 0x01, 0x02, 0x60, 0xF2]

tijmenvangulik wrote: ↑

January 17th, 2016, 11:41 am

Hi,

Have you found a fix for this problem or a response from concept 2 ? I get the same strange values and I can not see an work around.

Tijmen

Here I am having this problem 5 years later. Did you ever find a solution?