Comments

• Bob0007 Posts: 3 [Apprentice Traveler]

  November 2017

  I am using my drive connect route planner.

  0
• Niall Posts: 10,860
  Superuser

  November 2017

  @Bob0007
  
  There is an irritating bug in that the starting point of a route is not sent in a planned route, so you need to add a sacrificial stop a short distance from the start, then your device will show a route from your current position to the start point then to your destination

  0
• YamFazMan Posts: 18,713
  Superusers

  November 2017 edited September 2019

  Hi
  
  Note the latest MyDrive Web uses Send stops instead of Send to Device... I've edited the post to suit....
  
  During an "A" to "B" route transfer.....
  The device drops Location "A"
  This bug applies to all NAV4/(5 Wifi) devices
  After you have created your "A" to "B" route using the MyDrive Web (2) Route planner where "A" isn't your present location
  When you sync the route to your device using the "Send to Device" menu option
  I think the device removes your planned "A" location and moves it to your present location, but it doesn't replace your original "A" location with a stop, and so the route misses the original "A" location
  
  Note...[1] This bug applies to routes where "A" is not your present location
  For example Route from "A" Birkenhead to "B" Manchester, my present location (Worcestershire)
  Also, See Note... [2] Below... Multi-stop Routes
  
  The device receives the route -> Calculates the route from my present location (Worcestershire)... Then completely ignores "A" Birkenhead
  
  Screen GO 520
  Workaround... When planning your route if you place a sacrificial stop right next to the planned Start of your "A" to "B" Route
  
  Then when you sync the route to your device using the Send to Device Send stops menu option, the device still moves your planned start to your present location... But the sacrificial stop holds the correct route... From your Present location to original "A" then "B"
  In the above example... Worcestershire --> Birkenhead --> Manchester
  
  Screen GO 520
  
  Note... [2] This bug also applies also to Multi-Stop/Waypoint routes... 'A' to 'B' to 'C' to' D' to 'E' etc
  When you sync the route to your device using the Send to Device Send stops menu option
  I think the device removes your planned "A" location and moves it to your present location, but it doesn't replace your original "A" location with a stop, and so the route misses the original "A" location
  
  The same bug existed within the MYDdrive Web (2) Route planner, the route planner also dropped point A
  But that bug appears to have been fixed?
  
  ATB YFM

  1
• ThomasRider Posts: 3 [Apprentice Seeker]

  October 2020

  "But that bug appears to have been fixed?" => No. At least on a TomTom 400 it still shows up. Any news from TomTom Support by when this is going to be fixed?

  0