FAQ: Tymewear Datashift and timestamp fixes

[MedTechCD]

If there was a way to time shift

Once you have the streams in Intervals, you can export the Ve stream as a csv, add the number of empty rows you need at the beginning (1 sec per row), and then reupload. Those features are on the Data tab. If you need more assistance with that, ping me on the Intervals forum.

[fulmar2]

Hi guys -

Today I just released a new merge engine that is VERY beta. I'm looking for feedback to see if it resolves the issues discussed in this post. It does a lot more "cleanup" on the files. I am looking for feedback. The new engine is designed to fix a lot of issues that come up in these "edge cases"

Thanks again for your feedback!!

[j4m1eb]

Still out of sync.

[fulmar2]

This is interesting.. All of your files are offset by 14 minutes? I'm working on this today, but was wondering if you could tell me how to reproduce these graphs on intervals.icu. I don't use that tool and want to be able to replicate the issue so I can fix it. Talk to me like I'm 5. Ok, maybe like I'm 10.

[j4m1eb]

the few I've go to work are around 14 minutes, they only seem to work at all if I crop the longer tyemwear file to the same length as the Karoo file.

That could be me doing something wrong with merging

To add the breathing charts you need to.

go to activity, click on charts at the bottom, search for VE Zones then click on it to add it, it should then show in your charts

[j4m1eb]

Try this one

[fulmar2]

@j4m1eb - OK, I spent the better part of the day analyzing your files and working on GOTOES to try and make it work for you. Here is my thought:

First: intervals.icu seems to have some issues (at least in my browser). The time of day is "cut off" on the far left hand side of the screen. Also, when I search for data fields to add (thanks for the tip), I do not see the ones you suggested.. but if I "keep trying" they sometimes appear, and they sometimes don't. Enough of my griping; my site has bugs too, I'm sure

Second: I loaded your files into GOTOES and graphed out the raw data streams - separately (before merge). The device that shows up as "No Device Selected" (I'm going to add "Tymewear" today) is probably the culprit. If I had to guess, your Hammerhead has the correct time set (because GPS devices automatically set their time from satellite).. and your Tymewear device (which I don't know much about).. maybe has had some time drift. Are you able to double check the time on these two devices to be sure that they correspond? GOTOES uses the time that is embedded in the files; it's supposed to always be in UTC format, and GOTOES does not change the time in the files (unless you use the timestamp too (which would fix this by the way if you wanted to do a time-shift)).

At this point, I'm completely satisfied with the output by GOTOES, and cannot see any issues with the app itself (at least regarding this file pair). Please let me know if you discover that your clock is off by 14 minutes; that will make me feel like I finally understand this issue completely!

[j4m1eb]

Hiya, it's a weird one as the tymewear device is a bluetooth sensor, so not sure where it would get a timestamp from, the files recorded from it are on the iPhone app and I would assume thats uses the iP{hone for time so no reason it should be off?

I'm going to get a separate pair and see if they too are off, or maybe it was just that pair.

[j4m1eb]

I'm more confused now.

2 more files, this time I think they are more like 30 minutes out. The 2 marked points are maximum breathing at the top of the climb and the altitude itself showing the climb.

I've attached fit files.

from intervals.icu the merged file

None of this is your fault and I'm only trying to find a third party solution because tymewear broke there own tool, it used to merge fine

[fulmar2]

@j4m1eb - I just wrote to Tymewear for clarification on how the device syncs time. It will be interesting to see if that is the cause. Meanwhile, consider doing a time-shift on your GPS file using the GOTOES timestamp tool. When I released the new update, one of the things I did was ensure that Tymewear data fields are also time-shifted when using this tool (previously, that was not happening). This should solve your specific problem (and anyone else whose GPS doesn't get a satellite fix and thus has the wrong time set). It's a super useful feature!


So just for fun, I took your original file (the one that was off by 14 minutes). I did a time shift in GOTOES by 14 minutes, and exported that file. I got "shifted.fit"

Then I took that GOTOES shifted file (shifted.fit) and uploaded it along with the karoo file:

I merged these as usual and got this in intervals.icu:

This obviously does not answer the questions about your device (hopefully Tymewear will chime in)... but it does offer a viable solution for the issue at hand. Hopefully this will help other TymeWear users as well.

[j4m1eb]

Thanks thats definitely a workaround.

No idea where it gets timestamp and why it's out and also not even always out by the same amount.

I'm away in Spain riding soon so will have a much bigger play with it.
Might venture outside this weekend but its freezing here