This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Recording big .fit files

Former Member
Former Member
Hi,

I recently bought 1030 and I'm happy with so far ;)
I will be doing long endurance race in France this July and was wondering how big .fit file can you record on E1030?
I know that previous EDGE version had problems with 10h long .fit file (you had to reset ride and start again).
Does anyone done long 12h/15h+ ride in one go?

Regards, Seb.
  • I rode a 13hr 350Km ride recently with no problem. There's no file size limitations like the Edge800 had.
    Hopefully doing a 400Km+ ride this weekend so we'll see how that goes
  • I've dipped my toe in the .fit file protocol, however I'm no expert. The biggest fit file I have is from a 240km ride over 12.5 hours (9 hours ride time), and looking inside, it could've been 6000 times larger (according to the protocol) before the file size field overflowed. So from that point of view, you are safe.

    I upgraded from a Edge 520 to a 1030 last year, and one thing I've noticed is performance. For example, for training I have an auto-lap at 2km, and for shorter rides, the lap summary screen is handy to looks at how I've been going for the last few splits. However, on the 520, if I was doing a longer ride > 80km, if I accidentally view that screen it would take many seconds to update it with the 40+ time splits. With the 1030 its practically instant.

    What I'm trying to say is that it doesn't surprise me if some of the older Edges would struggle with larger files, just from a pure processing point of view, and if they take too long to move or save a large piece of data, I imagine bad things could happen. I'd be pretty confident in the 1030.
  • Update: So I did the 430km ride at the weekend.. Circa 16hrs. & had 20% battery at the end.
    I had navigation on from the start based a TCX course created in Ride With GPS then imported into GCM so I could download to the Edge without connecting to the computer.
    The route was a mix of road, cycleways & a little off-road. The unit performed flawlessly.
    At each fuelling stop I stopped the timer then put the Edge to sleep & then woke it up, ensuring I had a GPS fix before starting again.
    Due to the size of the course it took around 15min to calculate,, which I did on the move as I knew the initial route. It may be quicker if I'd done that before starting. On the first calculation I did worryingly get a failed message but acknowledged that & it worked 2nd time.
    Hope that gives you some confidence for your up and coming adventures