Jump to content

Recommended Posts

Posted

'16 with 8" non-Bose. Want to lose the cd player to have room for my lc7i and dont listen to CDs. Unhooked it and entire system dies. Is there some kind of delete cable I can get/make?

 

Internet searches have come up with nothing so far.

 

@pgamboa?

  • 7 months later...
Posted

Totally missed this. Let me look into into it.


Sent from my iPhone using Tapatalk

Posted
[mention=159655]pgamboa[/mention]
 
Still looking for a delete. Need that spot for my LC7i. [emoji3]

PM me. I have what you need.


Sent from my iPhone using Tapatalk
Posted
32 minutes ago, pgamboa said:


PM me. I have what you need.


Sent from my iPhone using Tapatalk

I've tried a few times but it says you can't receive messages. ?

Posted
I've tried a few times but it says you can't receive messages. [emoji24]

Weird. Just sent you one. Let me know if you got it.


Sent from my iPhone using Tapatalk
Posted

do i need special programming to install a dvd player into the 8" entertainment system or is it plug and play , toss the cd out install dvd unit???

Posted (edited)
12 hours ago, GTPprix said:

thats a bit steep to watch a dvd on my screen, i can watch some movies on the trucks screen with a usb in the glove box.  i wish there was an easier way to do this.

 

is it possible to take a blueray or dvd player from a PC with a sata connection,  converted to usb with adapter,  heck office depot has usb dvds for laptops too, then plug that into the glove box port to watch a cd?

Edited by flyingfool
Posted
13 minutes ago, flyingfool said:

thats a bit steep to watch a dvd on my screen, i can watch some movies on the trucks screen with a usb in the glove box.  i wish there was an easier way to do this.

 

is it possible to take a blueray or dvd player from a PC with a sata connection,  converted to usb with adapter, then plug that into the glove box port to watch a cd?

No.

Posted
do i need special programming to install a dvd player into the 8" entertainment system or is it plug and play , toss the cd out install dvd unit???

You have to replace the screen to a compatible 8” screen that has the decoder to play the DVDs too. I did it to mine. Screen, HMI unlocked (to get video button), DVD player, custom retrofit harness.


Sent from my iPhone using Tapatalk
Posted

whats the diffence between the movie installed on the usb vs, remote dvd plugged into the usb port? data is data...

Posted (edited)

sorry i didnt mention i already have the 8" HMI in the truck, its plays some movies already via flash drive

Edited by flyingfool
Posted
6 hours ago, flyingfool said:

whats the diffence between the movie installed on the usb vs, remote dvd plugged into the usb port? data is data...

Video format. DVD's are multiple files that get put together in sequence and decoded by firmware. Typically this is done at the OS level on a PC with USB dvd player or locally in a home based dvd player. The videos you can play from a usb stick are already encoded to the correct format and put together. Which is why you can't just download a single file from a BR/DVD to make a "backup". You need to use software to rip all of the separate components and stitch them together to make a single playable file. Typically MP4, AVI, or MKV.

  • Sad 1

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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • 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. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • 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.
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...