Jump to content

Adding Navigation to Intellilink / MyLink System

bluegrasscamper

Recommended Posts

  • Replies 618
  • Created
  • Last Reply
Mjw76248 Enthusiast

Mjw76248

Posted
Posted

Kodiakz or anyone.... I installed the factory Nav module a week or so ago in my 2014 GMC Sierra, and it works like a champ. Easy install, as described, and Kodiakz is ready, willing, and able to answer questions if necessary. Thank-you!!

 

I got Onstar to update the account after the drill described elsewhere in this thread. XM was easy, but like everybody else, a subscription was required for traffic and travellink, even though I'm on a trial for the radio. Traffic and weather popped right up but the fuel prices and movie times didn't. Can't find them anywhere, even with foreign tech support. They reprovisioned my radio but they still don't appear. No buttons or menu items...

 

Any solutions, ideas or suggestions would be greatly appreciated....

 

TIA

Mike

calgator73 Senior Enthusiast

calgator73

Posted
Posted

There is no dedicated button like intellilink. From the nav screen hit destination, poi, auto and fuel, fuel stations and the price will show up in just like the buick system. It will also show up along route if you do this while navigating.

calgator73 Senior Enthusiast

calgator73

Posted
Posted

Anybody notice the rounding error this thing does when counting down the distance for a turn? I didn't notice it until I was running Google Navigation alongside the factory nav and noticed that anytime you drop down below a mile it would automatically round down to the whole number mile instead of the decimal mile.

 

Sent from my LG-G2

 

 

kodiakz Enthusiast

kodiakz

Posted
Posted

Guys, just an FYI. We have found that if the dealer does flash these back to your vin, navi will disappear. We will gladly refresh them for you if this happens and are working to see if we can use a usb flash to update them. Just wanted everyone to be aware of this possibility. We advise our clients NOT to have the dealers flash the HMI unless the truck has issues due to that module.

Dres79 Enthusiast

Dres79

Posted
Posted

Guys, just an FYI. We have found that if the dealer does flash these back to your vin, navi will disappear. We will gladly refresh them for you if this happens and are working to see if we can use a usb flash to update them. Just wanted everyone to be aware of this possibility. We advise our clients NOT to have the dealers flash the HMI unless the truck has issues due to that module.

What issues could the truck have with that module?

 

 

Sent from my iPhone using Tapatalk

Bones810 New Member

Bones810

Posted
Posted

PM me what you would charge to flash my module. I was going to have the dealer do it but now I might just have you do it.

khotaling Enthusiast

khotaling

Posted
Posted

Kodiakz I PM'd you weeks ago with no response yet. Getting close to breaking down and buying from someone else....if you want the business I'm just sayin ...

wandern Enthusiast

wandern

Posted
Posted

Kodiakz I PM'd you weeks ago with no response yet. Getting close to breaking down and buying from someone else....if you want the business I'm just sayin ...

 

I've got to say that Kodiakz normally responds ridiculously quickly to PMs. Possible that he just missed yours at the time?

khotaling Enthusiast

khotaling

Posted
Posted

Yeah it seems like he responds quickly. If it helps you find my PM i sent it on March 26th.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
    • KARNUT
      2027 GMC Sierra: Official Discussion

      By KARNUT · Posted

      It was all part of the tiny bit of fuel savings it goes towards what was mandated by the government. Much like cylinder deactivation. That was relaxed by the recent administration. All that doesn’t help the individual buyer. But as a whole helps the manufacturer to try to reach the previous ridiculous past mileage per gallon mandate. So yes it was mandated and added cost to the vehicle. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...