Hi team,
I was wondering if I could get some assistance with an issue I'm having. Long story short we contract to telcos in New Zealand to do Cellular drive testing. The carriers will come to us with a site (or cluster of sites/highways etc) that need to be driven. We make routes in BaseCamp in advance and transfer the file to our Drivesmart 61 for navigating on the day. The unit is currently using firmware 6.70, using the City Navigator Australia and NZ 2023.1
Basically I did a firmware update (and I think I upgraded the maps too as they were available.) and since this update, I have an issue where if I load a route, it loads correctly, but it doesn't like the alerting waypoints. When driving the route we have it set to have 10 - 20 alerting waypoints, the rest are just standard waypoints to guide us to the correct streets. I noticed today when loading a previous route, that the unit will navigate to the alerting waypoint fine (see first image), however when we pass the waypoint it clears the path behind the waypoint (where we've just been - see second image) but tries to navigate back to the alerting waypoint as if we haven't passed it (third image.) Eventually the GPS asks if we'd like to skip it, we do and carry on until the next alerting waypoint. Sometimes even though I've pressed to skip that alerting waypoint it will still try send us back, othertimes it will route to the next. One problem with this, is sometimes there's a delay in the question of skipping comes up, by which time I may have passed another alerting waypoint, causing further issues. Sometimes we'll get two waypoints ahead in which case we'll restart the route, chosing the upcoming alerting waypoint so we don't have to start the run again.
This is an existing route we have previously used, so I don't think anything is wrong with the route itself (happy to supply though, if that is any use) and can confirm it happens on different routes too, so it's not isolated to just that one route.
I've tried doing a factory reset on the device, with the same issue. I've also uploaded the same route to my personal Montana 700i, which I had better success with, although potentially similar issues, in that the 700i skipped a chunk of the run for reasons I'm not sure of (maybe the same problem?) Our current fix that we tried today, is to remake the route into smaller sections, then select Part1, drive, then select part2 etc, however this isn't really that ideal, as I need to keep remembering what part I've done - and I won't always be able to stop and select runs depending where I am (it'd be fine in the country, but not all of my testing is rural)
Any thoughts would be greatly appreciated! Could it be that the maps were made using the City Navigator AU/NZ 2021.3 version, not the last being 2023.1? If so that could explain some issues, however there's probably 150 odd routes, with more being added... so redoing them all would be very painful, some of the routes are over 4hours drive long. Has anyone else found this? Obviously most people don't use routing like we do, so it's not a problem a lot of people have probably come across...
Any thoughts would be greatly appreciated! Could it be that the maps were made using the City Navigator AU/NZ 2021.3 version, not the last being 2023.1? If so that could explain some issues, however there's probably 150 odd routes, with more being added... so redoing them all would be very painful, some of the routes are over 4hours drive long. Has anyone else found this? Obviously most people don't use routing like we do, so it's not a problem a lot of people have probably come across...
Cheers,
