Jump to content

New System----nnbs

AthensGaZO6

Recommended Posts

AthensGaZO6 Enthusiast

AthensGaZO6

Posted
Posted

waiting on installer (Dr Audio) to show up to start the install of my new stuff. Here is what I got:

 

Kenwood ddx7019 dvd

 

JL 650 comps for front door

 

JL 525 comps for rear door(powered from head unit)

 

JL 500.1 slash for subs

 

JL 300.2 slash for front comps

 

2-10inch eD 11KV2s (haters can eat me)

 

subthump box

 

Sirrius

 

I will take some pix of install as it goes along if you want.

 

Here is my stuff waiting for Dr Audio-SYSTEM.jpg

 

here is my 07 ltz z71 it is going in with old grilleoldgrille.jpg

here it is with new grille-newgrille.jpg

AthensGaZO6 Enthusiast

AthensGaZO6

Posted
  • Author
Posted

rear seat removed. It is gonna be tight mounting 2 amps there....I will beleive it when I see it. May have o find a new location.....was afraid of that.

rearseatremoved.jpg

AthensGaZO6 Enthusiast

AthensGaZO6

Posted
  • Author
Posted
Is the DVD player onstar and steering wheel controller compatible? I hope this turns out good, it looks inspiring so far! :cheers:

 

 

yes, I have the adapters for both.

AthensGaZO6 Enthusiast

AthensGaZO6

Posted
  • Author
Posted

well I finally got it all finished. Added a back up camera :) while I was at it. I cant describe how much the 2 10s pound in the Subthump box........way better than I dreamed of. I am amazed. For those that are curious.......there IS enough room behind a ext cab rear seat to mount 2 big amps and a cap.....I was worried, but it fits. I can actually still fold my back seat up if needed. Here is a pic of head unit playing Neal Pearts drum solo......again....I cant get over how hard the 10s hit. Hell yeah!!!!!

 

headunit.jpg

-Devil- Enthusiast

-Devil-

Posted
Posted
For those that are curious.......there IS enough room behind a ext cab rear seat to mount 2 big amps and a cap.....I was worried, but it fits. I can actually still fold my back seat up if needed.

 

that is good to hear .. it looked like the seat folded up and pressed against the back wall .. but i guess there is some space in there with the carpeting ... would be interested in seeing how the amps hold up heat wise ...

 

i have been eyeballing those boxes as well ... does it retain room for the jack and stuff?

AthensGaZO6 Enthusiast

AthensGaZO6

Posted
  • Author
Posted
For those that are curious.......there IS enough room behind a ext cab rear seat to mount 2 big amps and a cap.....I was worried, but it fits. I can actually still fold my back seat up if needed.

 

that is good to hear .. it looked like the seat folded up and pressed against the back wall .. but i guess there is some space in there with the carpeting ... would be interested in seeing how the amps hold up heat wise ...

 

i have been eyeballing those boxes as well ... does it retain room for the jack and stuff?

 

 

I think you can leave jack and jack accesories in place, but you will have to remove box to get to them. I decided to throw them both in my toolbox however.

The amps should be ok......there is more room back there than I ever thought coulda mounted 3 back there.

If I were to fold my seat completely up it would touch the amps.....with seats down....no problem.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      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? 
    • 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.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...