TSX imports from indoor rowing sessions?

Afternoon, all:

Switched from a Concept2 to an RP3 for indoor rowing. I can track the four primary data series easily on the device: time, distance, HR, power. I also can sync those data to Strava, which are then pulled down to Athletica.ai.

That feed, however, does not contain power data. So I looked to import those data myself. I first export those data in .tcx form from RP3, then convert them to .fit and finally import them to Athletica.ai as a new session.

Still no power data. But I believe the .fit file has power; confirmed by reimporting the converted .fit file to Strava.

Perhaps the .tsx file would include the power? Other thoughts?

Not sure the power is needed for the load (which I understand to be the more meaningful output of the session; as an aside, the load for the session I just uploaded seems a bit high, but I have only prior sessions against which to gauge, am I’m far from knowledgeable on the calc. For reference, intervals.ai gave the session a 46 load)

1 Like

Raising this again (not sure why I wrote .tsx earlier…should be .tcx). I can see the power data written in an “extensions” component of the .tsx file:

<Trackpoint>
<Time>2024-11-05T22:18:29Z</Time>
<Cadence>26.572187776794</Cadence>
<DistanceMeters>9.1196594032564</DistanceMeters>
<HeartRateBpm>
<Value>57</Value>
</HeartRateBpm>
<Extensions>
<ns3:TPX>
<ns3:Speed>2.8077347267654</ns3:Speed>
<ns3:Watts>68.147943132232</ns3:Watts>
</ns3:TPX>
</Extensions>
</Trackpoint>

Any way to have those power data feed into the math?

On another platform, seems the “ns3:” bit is the offending component of the file

OK. So either the issue was fixed on the server side, or search/replace “ns3:” for “” in the .tcx prior to upload seems to allow the power data to show up. Phew!

2 Likes

I also have problem with uploading RP3 tcx into Ahtletica from.
How did you do the converstion to .fit?

Found my way around, removing all the ns3: and then using gotoes.org to convert. Phew…

Heya, @lol12321, there are a few ways to make this happen:

  1. You can sync the workout from portal.rp3rowing.com to Strava (if you have Strava). Those data then will flow to athletica.ai, though the pace details will not be correct and I do not believe the power data come over at all
  2. You can use the GOTOES site, referenced in this thread, to convert the .tcx to .fit for import to athletica

However, via both those “solutions” the pace data are wonky. See this thread for a discussion. Seems these issues are endemic to source RP3 data (and variously to C2 data) , not specific to athletica.ai’s interpretation of those data. And since I don’t believe there are many of us rowing on RP3s, I imagine a fix will be for us to find, so I will keep exploring potential solutions.

Example from my SS row yesterday:

versus, RP3:

3 Likes

Thank you! Very helpful