HUD Navigation

[silverchris]

Hey Everyone, Not sure if this is the best place to ask, but I am debating installing this on my car (Mostly being lazy, as I have to dig out the serial console connection :) ), and was wondering if there has been any research into getting navigation directions onto the little HUD display in some cars?

Haven't had a chance to dig into the code to see if this is something android auto passes to the car, but I would assume it may be possible on the car side, as factory navigation does it?

[zahitkara]

Mine started to work all of a sudden today after the google maps update i think. I haven't updated AA or CMU. Latest AA installed with CMU 56.00.513 and 2015 Mazda 3 with mono color hud.

Could be related with this: https://productforums.google.com/forum/?noredirect=true#!topic/android-auto/9U2N6d5mYV0

[mellda]

U. Latest AA installed with CMU 56.00.513 and 2015 Mazda 3 with m

Do you have the stock CMU and AA in CMU?

[zahitkara]

U. Latest AA installed with CMU 56.00.513 and 2015 Mazda 3 with m

Do you have the stock CMU and AA in CMU?

No. Using AIO version of AA v1.10+.

[mellda]

U. Latest AA installed with CMU 56.00.513 and 2015 Mazda 3 with m

Do you have the stock CMU and AA in CMU?

No. Using AIO version of AA v1.10+.

Is the hud navigation reliable? I mean if it is accurate. Same as in the navigation displayd on infotainment screen.

I have installed the upgrade of USB unit and got the official AA in FW version 70. I cannot go back to 59 to use the AIO version of AA.

[GekoCH]

for me it is only "accurate" during city driving. On the speedway there are a lot of strange turn signals displayed...

[zahitkara]

I haven't test it long enough to decide whether it's reliable or not.

[ryoncy]

for me it is only "accurate" during city driving. On the speedway there are a lot of strange turn signals displayed...

same with me on speedway a lot wrong turn signals

[frtnrn]

i have tested with android auto 3.9.5850 / mazda3 2017 with colored HUD everything works but main problem is too many direction.This problem root cause is HUD not displayed 3.4km and over.I think minor fix resolved this issue and works perfectly

[beauchar]

Spontaneous genesis for me as well a couple of days ago in my 6! No updates to the CMU (59.00.449 EU N) or the AIO AA install (v2.8.3 AIO, AA1.10) but I recently had an Android update and Google Maps updated to v10.10.1 about the same time, so I'm guessing it's a side effect of that.

I also now see that the directions displayed on the HUD don't match the main maps display. There seems to be a couple of things going on that may be causing this:

1. Mismatch in display units. Maps is displaying in miles and the HUD is displaying in Km
2. HUD seems to be displaying in chunks of 3.4km, when there are no turns in the main display. So main display shows straight ahead for 80 miles. HUD will display a turn in 3.4km, count it down and then start again.

I'll take a closer look at the work @leonunix did to diagnose this but was wondering if any updates were made to the code in the end as it wasn't clear to me from this thread. I will try and see if I can get a better view of what's going on and report back.

[ryoncy]

Any update for this HUD, now my HUD is no showing turn by turn navigate after android auto and google maps update. any facing the same problem?

[kennethgp]

I have CMU 56.00.100A and latest headunit AndroidAuto_v1.05-52-g54b38d6 (the one someone compiled to fix the restarts caused by Google's AA update) and HUD navigation does not work; it only shows the intital arrow for the first turn and it gets stuck, will not go away until you exit AA and switch CMU Navigation enabled setting on and off again. I leave this setting Off all the times but it does not prevents the arrow to appear. This also happened in headunit AA-v1.12 and it is very annoying. I read somewhere CMU 59.x was needed to HUD to work, is this true? If so, for all of us that can't upgrade it would be nice HUD navigation is either fixed or a setting to shut it off is available. I'd prefer to have that HUD off/on setting because I think it also contributes to Spotify stutter when maps auto-zoom or re-positions on a turn. I see stutter is almost all fixed by that latest 'user-compiled' version and turning off Waze auto-zoom, but still it happens on hard turns, for example in roundabouts, so I think maybe the HUD functionality is related.

[xeacott]

Hey guys how is this going? Is there any way I can offer some help? Testing or development.

[silverchris]

I have been meaning to get back to this for awhile. I have ordered a bricked CMU off ebay, to hopefully help with testing it. I was getting a bit nervous using my daily driver as a test rig! :)

[silverchris]

Update: Got a CMU running on my bench. Need to see if I can source a cluster with HUD from an auto wrecker around here., and maybe the HMI controls lol

I do think the HUD code does need an option to turn it off and on, as I can understand people not wanting to use it for what ever reason.

[silverchris]

The round about code I wrote originally I think didn't work well or at all. I haven't had much chance to try it, as I only see a round about once a year.

I am from America, so yes, left hand drive

On Tue., Nov. 3, 2020, 7:25 a.m. Radarwild, notifications@github.com wrote:

@silverchris https://github.com/silverchris @Trevelopment https://github.com/Trevelopment regarding the latest code for AA v1.13 fw59 roundabout in the HUD do you sit on the left with steering wheel and drive on the road on the right? And exit roundabout anti-clock wise? If so E.g when you wanted to do a u-turn at the roundabout exiting anti-clock wise does the (diricon 49 or 37) image shows up on your HUD? If so what is the log please if you could provide. My steering wheel are on the right and drive on left the roads roundabout enter & exit clock-wise. Therefore taking a u-turn at roundabout should show diricon 49 on HUD but it doesn't. All others diricon 50+ shows. Anyway to re-write the code in hud.cpp to make it show up on HUD?

//original uint32_t diricon; if (navi_data->turn_event == 13) { diricon = roundabout(navi_data->turn_angle, navi_data->turn_side - 1); } else { int32_t turn_side = navi_data->turn_side - 1; //Google starts at 1 for some reason... diricon = turns[navi_data->turn_event][turn_side]; }

//i tried some codes and diricon 49 or 37 shows on HUD but then all other roundabouts are mirror afterwards

uint32_t diricon; if (navi_data->turn_event == 13) { diricon = roundabout(navi_data->turn_angle, navi_data->turn_side - 1); } else if (diricon == 60) { diricon = 49; //37 for steering wheel on the left { int32_t turn_side = navi_data->turn_side - 1; //Google starts at 1 for some reason... diricon = turns[navi_data->turn_event][turn_side]; } //why is it mirroring all roundabout diricons except u-turn roundabout this time shows up on HUD correctly?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gartnera/headunit/issues/135#issuecomment-721085311, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFW6Z5BZN6NGDR7URCWHDDSN7ZC5ANCNFSM4FS7QQ6Q .