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

Race an activity - problems

Last Sunday I rode a Grandfondo that I did before, I wanted to use the feature “race an activity” for 2 reasons:

  1. It would enable Climbpro
  2. It would give me live the amount of “time ahead” (or behind)

 

The original activity was just below 7 hours, recorded with 1 minute intervals, over 25.000 records.

When loading this original activity in the 1040, I did get a route calculation error.

Examining the original file, I noticed that because of a long tunnel, there were a couple of records with Lat/Lon values of zero.

Having no official Garmin tool to adjust that, I loaded the file into Golden Cheetah, copied the Lat/Lon values to Excel, filled in the zeros as if it was a straight line (in fact it was) end copied the values back into Golden Cheetah.

Also corrected one elevation error manually.

Saved the file to GPX because I have bad experiences with FIT files created by Golden Cheetah.

Then I loaded the result into BaseCamp and indeed the elevation graph was smooth and no more virtual trips to the south pole anymore.

 

Ok, next step was to reduce the number of datapoints/records by using the ‘filter’ button.

So, I reduced using the setting ‘maximum records’ set to 1.000, resulting in 814 records.

 

I copied the track to the 1040, restarted the 1040 and there it was in the ‘courses’ list.

I selected “race an activity” and selected the course. Got the usual question “navigate to the start” and pressed the “X” of don’t.

 

When the race started I hit the start button and the device restarted (?)

But after the restart I pressed start again and everything looked good.

The "time ahead" shown was accurate.

About an hour and 15 minutes into the ride something popped up (could not read the message without glasses, too small).

I got 2 options:

  1. Pause navigation (in grey, left side)
  2. In red, could not read the other option, looked like a recalculate

Did not know what to do and tried to pause, but the screen was unresponsive. However, it kept recording, I saw the time ticking.

Then, after some 20 seconds the unit restarted, only to get stuck again. I was too late with trying something, screen was unresponsive.

Manually restarted (long press power button), then directly after startup selected the widgets and pressed “stop course”.

(in the mean time trying to hold my power target ;-))

Normal operation after that, but no more course, so no Climbpro.

 

What is the normal way to race a previous (long!) activity ?

Do I have to select fewer records than 800 ?

Anyone here with experience?

  • No need to be reducing the number of data points. That was really only necessary on a number of early Edge units. The Edge will do it's own point reduction if it needs to.

    I'm assuming this was on build 12.15?

  • Yes, this was with 12.15 build.

    Tried the original course file, with only the zero lat/lon values corrected, but returns an error at startup.

    Reduced file at least no errors besides the one mentioned above.

    By the way, the elevation profile of the new activity file from the 1040 looks stunningly smooth (best GPS mode and 1 sec recording were selected), happy with that.

  • Is there an error log file on the unit? If so could you zip it and post it?

    Garmin\Debug\err_log.txt

  • The file is there, timestamp is 3 minutes ago (did not startup the device, only usb-connect), size is 0 (zero) bytes.

  • Thanks. Hopefully things will go better teh next time you try a course.

  • I think the fact you had to do so much to the course in the first place is not a good starting point to point the finger at the unit.  It would probably be better to start with a previous activity you know the data is good and try that.

    I have seen on the 1030 “Navigation crashes” and it does seem when they have an issue it either freezes and you need to do the hard reset, or the whole unit decides to reboot itself anyway. 

    Something I’ve always though smart whenever this happens is the current ride is still always still there and I’ve not lost anything.  The only thing you will loose is from the time it crashes to when you stop.  Often you then just see a straight line.

  • I do not fully agree. In my experience there are always "dropouts" or faulty values in long courses. In this file there was 1 elevation error (one record with 811 meters within a series of 1511 meters). And when riding through a long tunnel I hear all garmins around me chirping because they lose satellite reception. All units then will record zeros.

    I tried the original fit file: not working.

    Therefore I tried to find out what the cause of the problem was:

    The missing lat/lon because of the tunnel? No.

    The high number of records? aweatherall says no.

    Surely not the one elevation fault, that was only done by me being a perfectionist.

    There is nothing wrong with the course that I am aware of. And that is not nice, I would like to have a coursefile next ride and I want to 'race' this particular race because of the registered times on the climbs, etc.

    So I will have to keep on trying and find out myself what the problem is. I will cut the file in segments and try per segment. Will report later if I find anything useful to share.

  • Are you willing to share the course file you used?

  • I would agree no course Is perfect.  I guess what I was trying to say is this course was a problem from the start and you needed to do a lot of manipulation to even get it to work.

    if you can get a course to load without that, yes it may still have something in it somewhere, but it would be interesting to see if you see problems with that also