I have found what is causing the problem and I have a workaround for you.
The issue is with the data that is being generated by RWGPS and how the Edge is using it.
To determine if you are on or off course the Edge builds a bounding box around the track points that it considers to be part of the course that you are following.
In selecting what track points to use it looks at the total time specified in the course file for completing the course. Using that time it goes through the list of track points and selects all the track points that fall within that time window.
Here is the problem. The time for completing the course specified by RWGPS is much shorter than the time taken using the timestamps that are on each track point. The bigger the difference the fewer the number of track points that are included in the bounding box calculation.
As an example I looked at the values in the file I was using and found that the time delta between the first and last track point was 18,370 seconds, while the time reported for completion of the course was 2,198 seconds. As you can see unless my course was confined to a very small area I would only be able to pick it up near the start.
I'm betting if you look at the tcx file that you downloaded from RWGPS you will see a similar thing.
Here is how to fix it.
Using an editor (I like using the firstobject xml editor) open up the tcx file.
Go to the first track point in the file and get the value for "Time". Do the same for the last track point. Then workout the difference between these 2 times in seconds and take that value and use it replace the value that is currently associated with the tag TotalTimeSeconds under lap near the top of the file.
Save the changes and place the file in the Garmin\NewFiles folder.
- We have this bug with RWGPS files where you HAVE to start from the beginning of the course or you will get no turn cues.Is this something newly introduced after an update on the RWGPS site because on my 810 this works fine. I can stop the course are re-load it and once it finds the course, it will determine the position on the course and the cue points are then skipped through until the correct position and start working from there.
Following a course is a CORE function of a bike GPS computer
So today I did a ride with Bike Route Toaster with turn cues and advance turn cue's at 150 ft before course point, exported to the edge 520 in TCX form. The results were not good. For some intersections it did not give me the early turn cue, and random turn cues popped up when there wasn't even a turn!Try this. Create your route in RWGPS. Then import the TCX into BRT. Then export the TCX with advanced cues.
Is this something newly introduced after an update on the RWGPS site because on my 810 this works fine. I can stop the course are re-load it and once it finds the course, it will determine the position on the course and the cue points are then skipped through until the correct position and start working from there.It also works fine with the 500. Sounds more like a bug with the 520.