Jump to content

Recommended Posts

Posted
2 minutes ago, bowtiemark said:

I just install the upgrade from a 4 inch screen to Apple carplay 8 inch screen, first week or two it works amazing! After that the screen itself begins to go to a different page it self. Now this morning the screen itself does not work anymore. Not to sure if anyone knows about this problem. I bought the screen from a eBay part seller I believe it came from a total truck. It does have a 60 day warranty. I try to recalibrate the screen and nothing works. 

Hey man. I would absolutely check your LVDS connections (blue USB on HMI, black USB on screen) as well as the black connector on the back of the 8 inch screen as that is what's responsible for the LIN bus communication for touching the screen. 

Posted
6 minutes ago, th3magpi3 said:

Hey man. I would absolutely check your LVDS connections (blue USB on HMI, black USB on screen) as well as the black connector on the back of the 8 inch screen as that is what's responsible for the LIN bus communication for touching the screen. 

Ok so check if any connections are not on right. The rest of the controls work but the screen itself doesn’t sense any touch. The eBay seller had a warranty should I try and get another screen? 

Posted
Ok so check if any connections are not on right. The rest of the controls work but the screen itself doesn’t sense any touch. The eBay seller had a warranty should I try and get another screen? 
Do the volume knobs work? There are 2 Lin bus connections on the square connector on the back of the screen. One is responsible for the audio volume knobs and button controls and one is responsible for the touch screen. If the volume and buttons are working then there's an issue with the touch screen Lin connection. Try reseating that connector and seeing if the touch screen starts functioning again. The fact that it was working for a few weeks tells me it could be not seated properly.

Sent from my Pixel 3 XL using Tapatalk

Posted
5 minutes ago, th3magpi3 said:

Do the volume knobs work? There are 2 Lin bus connections on the square connector on the back of the screen. One is responsible for the audio volume knobs and button controls and one is responsible for the touch screen. If the volume and buttons are working then there's an issue with the touch screen Lin connection. Try reseating that connector and seeing if the touch screen starts functioning again. The fact that it was working for a few weeks tells me it could be not seated properly.

Sent from my Pixel 3 XL using Tapatalk
 

Yes the knobs work fine, that is how I been controlling the screen, the screen it self seems not to getting any demands 

Posted
1 hour ago, bowtiemark said:

I just install the upgrade from a 4 inch screen to Apple carplay 8 inch screen, first week or two it works amazing! After that the screen itself begins to go to a different page it self. Now this morning the screen itself does not work anymore. Not to sure if anyone knows about this problem. I bought the screen from a eBay part seller I believe it came from a total truck. It does have a 60 day warranty. I try to recalibrate the screen and nothing works. 

I have a screen if needed HMU 

Posted
Yes the knobs work fine, that is how I been controlling the screen, the screen it self seems not to getting any demands 
Re seat the square connector on the back of the screen. Unplug it and plug it back in. Ensure all wires are firmly pressed into their connector and see if the issue persists.

Sent from my Pixel 3 XL using Tapatalk

  • 2 weeks later...
Posted

Hey all,

   I read through the first couple dozen pages on this. I have a shortage 2016 2.0. From what I am reading all I need is the 2.5 module and have it programmed to the truck. Is that a correct assumption?

Posted
Hey all,

   I read through the first couple dozen pages on this. I have a shortage 2016 2.0. From what I am reading all I need is the 2.5 module and have it programmed to the truck. Is that a correct assumption?

Here, you will find the most up to date and accurate info on this upgrade. Even though it says 2014-2015.5, since you have the leftover 2.0 HMI in your 2016, this would apply to you.

 

https://www.whiteautoandmedia.com/product/2014-2015-5-c-k-platform-car-play-upgrade-retrofit-programming/

 

If you have the newer USB hubs, you may not need to swap those out. But the HMI and Radio Module you will for sure.

 

EDIT: Since your truck is 2016, this is the correct link. https://www.whiteautoandmedia.com/product/2016-android-auto-car-play-upgrade-retrofit/

 

You can select to have them provide the hardware.

 

Sent from my iPhone using Tapatalk

Posted
5 hours ago, pgamboa said:

Here, you will find the most up to date and accurate info on this upgrade. Even though it says 2014-2015.5, since you have the leftover 2.0 HMI in your 2016, this would apply to you.

 

https://www.whiteautoandmedia.com/product/2014-2015-5-c-k-platform-car-play-upgrade-retrofit-programming/

 

If you have the newer USB hubs, you may not need to swap those out. But the HMI and Radio Module you will for sure.

 

EDIT: Since your truck is 2016, this is the correct link. https://www.whiteautoandmedia.com/product/2016-android-auto-car-play-upgrade-retrofit/

 

You can select to have them provide the hardware.

 

Sent from my iPhone using Tapatalk

Might want to do a bit more research. Not saying you're wrong but I've done plenty of swaps for people who have the 2016's and only the HMI is needed to be programmed. The radio does not need to be touched. 

 

If @Goinovr has any more questions he can also reach out to us at Coastal Flash and we'd be happy to assist.

Posted
2 hours ago, th3magpi3 said:

Might want to do a bit more research. Not saying you're wrong but I've done plenty of swaps for people who have the 2016's and only the HMI is needed to be programmed. The radio does not need to be touched. 

 

If @Goinovr has any more questions he can also reach out to us at Coastal Flash and we'd be happy to assist.

Yep.  I did update my post with the EDIT.  I was helping few others with this and missed the 2016 mention in my response.  

Posted
33 minutes ago, pgamboa said:

Yep.  I did update my post with the EDIT.  I was helping few others with this and missed the 2016 mention in my response.  

No stress. Just figured I'd point it out that if it's a 2016 you don't need the radio done. Just the HMI. 

Posted

Hey all,

 

I just came across this thread whilst looking to add car play to my 2015 Silverado. I know I have to replace the modules and what not but what are the part numbers and where did you guys find them? Also, do I need to get them flashed for my VIN? 

Posted
Hey all,
 
I just came across this thread whilst looking to add car play to my 2015 Silverado. I know I have to replace the modules and what not but what are the part numbers and where did you guys find them? Also, do I need to get them flashed for my VIN? 

You can find a list of hardware on our website and yes they do need to be programmed for your specific application.

www.whiteautoandmedia.com :)
Posted

will be ordering the HMI swap this month for my 2015 GMC.  Is it worth the extra money to get the navigation?

Posted
1 minute ago, bradman0087 said:

will be ordering the HMI swap this month for my 2015 GMC.  Is it worth the extra money to get the navigation?

I ditched the built in navigation and don't miss it at all. Google maps is much better so I didn't see any point in having both. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...