2014-2024 Touring Models This Section Is For Rushmore and Gen 1 M8 Touring models from 2014 to 2024
Sponsored by:
Sponsored by:

nav/boom bugs

Thread Tools
 
Search this Thread
 
Old Jul 26, 2014 | 04:40 PM
  #1  
SecondGear's Avatar
SecondGear
Thread Starter
|
Road Captain
Joined: Nov 2013
Posts: 528
Likes: 14
From: pittsburgh
Default nav/boom bugs

Just finished an 8 day, 2700 mile trip. Over the first 4 days the Nav/Boom worked flawlessly. I'm actually really impressed with how well it worked. At first I was unhappy with the paltry Nav notifications but when I found all the "Display Next ...." stuff and all those complaints went away.

But I did have a few issues. I created gpx files from the Harley Trip Planner but one file caused problems. I tried re-generating & re-loading it several times. It would start to load but never finish loading. The "loading" screen never went away. When I canceled and tried a second time I got this:



And attempting to load anything else would cause the same thing. I was able to enter an address to get to that days destination but this really freaked me out.

Second issue was that on three times the Nav instructed me to "Exit the highway" only to come right back on. I ignored the Nav because I knew I had another 180 miles on I70 but the map showed the exit&immediate re-entry. This happened three times over the last 2 days.

The damn volume bug bit a couple times. It's a royal pain in the *** to make the driver & rider get on the bike and attach com cables before turning on the ignition and then waiting for the damn "accept" screen. Even after doing all of that, the volume bug hit once. I pulled over and shut off the ignition but apparently you have to leave it off for a while because it came right back in the screwed up state.

The screen will go into night mode and sometimes not come back out. I was parked in a garage and the screen started in night mode but when we exited, it never swapped back to day mode. I had this also happen when going through a tunnel. Entered in day mode, it swapped to night mode but when I came out of the tunnel it stayed in night mode.

All in all it worked really well but some of these bugs have been known for six months. I cannot believe that no update was released but hope when the '15s release we get a major update.
 
Reply
Old Jul 26, 2014 | 08:13 PM
  #2  
rmc115's Avatar
rmc115
Road Master
15 Year Member
Photogenic
Joined: Oct 2006
Posts: 1,122
Likes: 23
From: Mishawaka,Indiana
Default

The best thing to do is pull over and remove the master fuse under the left side cover for 30 seconds and then it should be good. I have only had to do it 1 time in 5k miles. Mike
 
Reply
Old Jul 26, 2014 | 10:25 PM
  #3  
RevRaz's Avatar
RevRaz
Tourer
Joined: Dec 2012
Posts: 386
Likes: 0
From: No Cal & So Cal
Default

I've never had to do any of that stuff and mine has always behaved correctly
 
Reply
Old Jul 28, 2014 | 09:04 AM
  #4  
jkane13's Avatar
jkane13
Tourer
Joined: Aug 2013
Posts: 361
Likes: 1
From: Wisconsin
Default

That database error is related to special characters in the .gpx file you imported. Once you get that error, turn the bike off and back on. It will keep giving that message until you do that.

Make sure you do NOT have any apostrophes in your destination names. Don't name something "Bill's Place" or anything like that. Leave the apostrophe out. That is what gave me those errors.
 
Reply
Old Jul 28, 2014 | 10:22 AM
  #5  
WaucondaRider's Avatar
WaucondaRider
Tourer
Joined: Apr 2014
Posts: 351
Likes: 0
From: Illinois
Default

Originally Posted by jkane13
That database error is related to special characters in the .gpx file you imported. Once you get that error, turn the bike off and back on. It will keep giving that message until you do that.

Make sure you do NOT have any apostrophes in your destination names. Don't name something "Bill's Place" or anything like that. Leave the apostrophe out. That is what gave me those errors.
I agree. I had the same problem and double checked all my stops and remove the special characters and had no problems after that.
 
Reply
Old Jul 28, 2014 | 10:40 AM
  #6  
SecondGear's Avatar
SecondGear
Thread Starter
|
Road Captain
Joined: Nov 2013
Posts: 528
Likes: 14
From: pittsburgh
Default

Originally Posted by jkane13
That database error is related to special characters in the .gpx file you imported. Once you get that error, turn the bike off and back on. It will keep giving that message until you do that.

Make sure you do NOT have any apostrophes in your destination names. Don't name something "Bill's Place" or anything like that. Leave the apostrophe out. That is what gave me those errors.
Good lord, that's it! One stop I had on that trip was for "Fiorella's Jack Stack Barbeque". That's a pretty idiotic bug that should f'ing be fixed. But it's good to know & easy to avoid.

I had pre-loaded the first 4 days of the trip while I was at home. Going to KC was contingent on the weather & when I tried to load the GPX file in a parking lot in St Louis and the Nav went south, I was concerned. Once I was able to enter the address directly, all was good.

I thought the GPX file was corrupt so I built a whole new trip in the Harley ride planner but used all the same names & addresses. But the issue remained.

I sure hope there's a lot of updates available when the '15s come out.
 
Reply
Old Jul 28, 2014 | 10:48 AM
  #7  
SecondGear's Avatar
SecondGear
Thread Starter
|
Road Captain
Joined: Nov 2013
Posts: 528
Likes: 14
From: pittsburgh
Default

Originally Posted by RevRaz
I've never had to do any of that stuff and mine has always behaved correctly
The volume bug has had a bunch of threads and is well documented. The Nav/database error was due to the Nav not being able to handle ' in destination names. The Nav routing me off & on interstates was new to me.

The real point is that the last Boom firmware was released last February. That's way too long to let known issues in the field. Especially when new '14s are being shipped with an update that isn't available to other '14 owners.

As I said in my original post, it all mostly worked really well but 2 of the 3 issues were already know and should have been fixed.
 
Reply
Old Jul 28, 2014 | 11:07 AM
  #8  
GoGetter5832's Avatar
GoGetter5832
Road Master
Joined: Feb 2011
Posts: 818
Likes: 7
Default

I turned my display from "automatic" to always being on "daytime." Best thing I did. Always bright enough in the day and looks great at night. I was having the same issue when it was too dim during the day & would get stuck in "night" mode when driving through a tunnel or shaded area, etc.
 
Reply
Old Jul 28, 2014 | 11:16 AM
  #9  
bigrobtemp's Avatar
bigrobtemp
Road Captain
Joined: Jul 2014
Posts: 577
Likes: 19
From: Michigan
Default

I also switched off the automatic screen brightness and let it on daytime. I would get on bike in morning and not have any screen for 5 minutes? They need to work on the bugs and get them out in updates. I would not care if I had an update a month as long as I knew they were trying.
 
Reply
Old Jul 28, 2014 | 02:07 PM
  #10  
SecondGear's Avatar
SecondGear
Thread Starter
|
Road Captain
Joined: Nov 2013
Posts: 528
Likes: 14
From: pittsburgh
Default

Originally Posted by GoGetter5832
I turned my display from "automatic" to always being on "daytime." Best thing I did. Always bright enough in the day and looks great at night. I was having the same issue when it was too dim during the day & would get stuck in "night" mode when driving through a tunnel or shaded area, etc.
Another great idea. I'm going to change mine to "daytime".

I sure hope the '15s bring major upgrades to the firmware. It sure would be nice to have thsi stuff just work.
 
Reply



All times are GMT -5. The time now is 10:29 PM.