Bricoop
Well-Known Member
Figured I'd start a new thread, rather than clog up the Dakar 2017 post. Based on the translation, it sounds like Coma is going to make finding the WPs more difficult. In the past, when you were ~800m from a WP you would receive a directional arrow to help you find the WP. This year it sounds like you won't be notified until you are within 300m. The difference being you no longer have those directional arrows after notification. I assume the graded roads will have WPs on the road, but in the dunes it sounds like there has been issues with top teams finding WPs. Is anyone familiar with how close to a WP a vehicle needs to be to a WP to trigger crossing it?
Because I work better with illustrations, here's how I would use this technique in a real race. This is just based on my research and what I've read from many of you guys.
Co-dog indicates a WP is coming up. We cruise through and get a beep at 2 locations (unclear how this works exactly if it is a sustained beep or one every time you enter the 300m radius of the WP). Based on that we can identify how far we traveled within the notification circle. No indication we hit the WP so we've got to turn around to find it, mind you each of these 300m circles is an area of ~22acres, not small! So what do we do? We go to the location of the second beep. Based on our original heading of 100 degrees, we'd now be heading @ 280 degrees after we turn around. Based on this chart, the co-dof would know I need to head 54.14 degrees off my current route. Have the driver pin it for 300m at a heading of 334.14. If that doesn't work, go back to that second beep and adjust 54.14 degrees the other way other way for 300m at a heading of 225.86(or from the first beep at 154.14 degrees).
Distance traveled - Degrees off route
50 - 57.10
100 - 56.50
150 - 55.51
200 - 54.14
250 - 52.39
300 - 50.28
350 - 47.82
400 - 45.03
450 - 41.92
500 - 38.53
550 - 34.86
Like before, green is original route, yellow dots indicate notification points and purple is after we've turned around with our revised heading.
There are a lot of variables that can affect this such as sensitivity of the GPS, ability to measure distance between notifications and the ability to mark and return to specific locations.
How do you guys think the pros will solve the new challenge?
Because I work better with illustrations, here's how I would use this technique in a real race. This is just based on my research and what I've read from many of you guys.
Co-dog indicates a WP is coming up. We cruise through and get a beep at 2 locations (unclear how this works exactly if it is a sustained beep or one every time you enter the 300m radius of the WP). Based on that we can identify how far we traveled within the notification circle. No indication we hit the WP so we've got to turn around to find it, mind you each of these 300m circles is an area of ~22acres, not small! So what do we do? We go to the location of the second beep. Based on our original heading of 100 degrees, we'd now be heading @ 280 degrees after we turn around. Based on this chart, the co-dof would know I need to head 54.14 degrees off my current route. Have the driver pin it for 300m at a heading of 334.14. If that doesn't work, go back to that second beep and adjust 54.14 degrees the other way other way for 300m at a heading of 225.86(or from the first beep at 154.14 degrees).
Distance traveled - Degrees off route
50 - 57.10
100 - 56.50
150 - 55.51
200 - 54.14
250 - 52.39
300 - 50.28
350 - 47.82
400 - 45.03
450 - 41.92
500 - 38.53
550 - 34.86
Like before, green is original route, yellow dots indicate notification points and purple is after we've turned around with our revised heading.
There are a lot of variables that can affect this such as sensitivity of the GPS, ability to measure distance between notifications and the ability to mark and return to specific locations.
How do you guys think the pros will solve the new challenge?
