Well, I'm lost in all this but I was keen on taking up the
challenge to run the route in post 28 from BaseCamp onto a Nav V to see if it would work with no effort.....
To avoid any possible 'pollution' (or suggestion of cheating) I took a Nav V and took it right back to its factory settings, starting from square one as it were.
I opened up the OP's route on my Mac, running map version 2017.1 NTU in BaseCamp. The Nav V also has the same map, properly installed.
I turned off all routing preferences on my Mac and on the Nav V, just to make sure nothing would interfere.
Looking at the route's info there are a few oddities, including a departure time at point 009292 that is before the fellow arrives but other than that it looks OK, so let's load it onto the unsuspecting virginal Nav V........ hey-ho, let's go....
1. I requested BaseCamp to send across the route AND the waypoints
2. The OP's route was created in a different map version, so (naturally enough) BaseCamp asked me if I wanted to recalculate it before it was sent. I said, NO
3. I ejected my Nav V, as required by a Mac
4. I turned on the Nav V and was prompted that it had found a new route and would I like to import it into Trip Planner? YES
5. The Nav V then imported the route. It has to make a calculation of it, unavoidable.
6. The route appeared in the Trip Planner App..... Big roll on drums......
7. It is 167 miles which matches the OP's distance
8. The Nav V says it will take 4 hrs 35 minutes.
9. The route displays correctly and looks OK in the Nav V's review function
10. I have to switch the Nav V to indoor use, which turns the GPS off. That doesn't matter, I can still simulate driving the route.... The Nav V does it perfectly. I am confident it would have done it had I started in Wolverhampton, rather than simuated the ride from the comfort of my home in London, E1
11. I then shared the route with a second (non-virginal) Nav V via Bluetooth. Again, it worked perfectly.
12. I then re-imported the route from the Nav V, back into BaseCamp on my Mac...
13. I then changed the re-imported route's colour, just so it would stand out against the original route. There were no obvious differences.
So, what have we learned.....
(a) That there is nothing at all wrong with BaseCamp, it dealt with everything I asked it to do and more besides.
(b) That there is nothing wrong with the OP's route as such. Yes, it's maybe a bit untidy in its creation but so many routes are.
(c) That there is nothing wrong with the way my two separate Nav V's (one virginal, the other most definitely not) handled the OP's route and a simulation of driving it.
(d) That there is no need to start creating all sorts of additional waypoints which are (in the hands of the unwary) an invention of the devil. Similarly, there is no need to create a track or muck about with all the alternative software to Basecamp; all it does is cause even more confusion. I did the lot without mucking the OP's route about at all, all from with good old bog standard BaseCamp.
(e) That there is - in this instance at least - no need for OSM maps. Garmin's (or Navetec's) worked fine, in that all the roads the OP wanted to use seemed to be there.
14. Just for fun, I then recreated the OP's route afresh (and maybe more simply) in BaseCamp, mirroring the route by simply tracing over it by dragging. Here it is, hosted in Dropbox. It was exported as a .gpx file, called 'Wapping - IAM route thing'. If anyone downloads it, just make sure it ends with the .gpx extension, as a Mac (or Dropbox) will sometimes convert it into a text file. The route is coloured red, just to differentiate it.
https://www.dropbox.com/s/4jgr5gxbhk1yuix/Wapping - IAM route thing.GPX?dl=0
I suggest the OP tries it out; I'd be happy to ride it.
Lessons to be learned, OP......
You lost your bet of:
Get to know and love BaseCamp, it really does work well
Get to know and love your Nav V, it really can (and will) work well
Richard
PS I did run the OP's route via OSM maps, too. It worked fine both in BaseCamp and on my Nav V.