Jump to content

Recommended Posts

Posted

My truck came with the plastic cargo organizer under the back seat. Part of me wants to keep the storage it provides but it’s preventing me from getting a subwoofer under there. 
Any boxes out there or set ups to save storage space and get a sub??

Also, shop quoted me at 1700 for Alpine type R 6.5in comp (front) and coaxial (in the back), 5 channel amp by JL, JL 8inch sub with enclosure,lc7 converter and labor. 
I think it’s a fair deal. Opinions??

Posted
14 hours ago, Alberto Aguirre said:

My truck came with the plastic cargo organizer under the back seat. Part of me wants to keep the storage it provides but it’s preventing me from getting a subwoofer under there. 
Any boxes out there or set ups to save storage space and get a sub??

Also, shop quoted me at 1700 for Alpine type R 6.5in comp (front) and coaxial (in the back), 5 channel amp by JL, JL 8inch sub with enclosure,lc7 converter and labor. 
I think it’s a fair deal. Opinions??

I currently have a vinyl wrapped box in place with a single Diamond Audio 10 and an ARC 5 channel amplifier... and I hate it. They put the amp on the passenger side and put the half length box behind the driver seat. It completely defeats the purpose of keeping partial storage. 

 

I have been eyeing this: https://mtiacoustics.com/product/mti-acoustics-enclosure-upgrade-on-enclosure-amplifier-mounting-will-not-work-for-ported-enclosures/

If you can live with a single subwoofer, MTI has a full length box with a storage cubby & integrated amp enclosure. I am going with the JL VX1000 5 channel & the JL 13TW5 sub. I currently have Focal Door speakers & Kenwood Excelon Dash Speakers.

 

 

Posted
2 hours ago, ArcherMP said:

I currently have a vinyl wrapped box in place with a single Diamond Audio 10 and an ARC 5 channel amplifier... and I hate it. They put the amp on the passenger side and put the half length box behind the driver seat. It completely defeats the purpose of keeping partial storage. 

 

I have been eyeing this: https://mtiacoustics.com/product/mti-acoustics-enclosure-upgrade-on-enclosure-amplifier-mounting-will-not-work-for-ported-enclosures/

If you can live with a single subwoofer, MTI has a full length box with a storage cubby & integrated amp enclosure. I am going with the JL VX1000 5 channel & the JL 13TW5 sub. I currently have Focal Door speakers & Kenwood Excelon Dash Speakers.

 

 

I have never heard of focal until I was at the shop the other day. My mind was set on the type Rs but the sales man was pitching me the focals. I don’t know anything about them. That set up you linked me is nice. But, I want a smaller sub. I used to be a 2 12s type of guy but now I’m looking like a 10inch. 

Posted

I just ordered my harness from John real nice guy answered all the questions I had. Now I have a question for you guys The plastic door trim pieces to get under the carpet the just pull up right?  Thank you guys 

Posted
On 12/29/2019 at 4:42 PM, Alberto Aguirre said:

I have never heard of focal until I was at the shop the other day. My mind was set on the type Rs but the sales man was pitching me the focals. I don’t know anything about them. That set up you linked me is nice. But, I want a smaller sub. I used to be a 2 12s type of guy but now I’m looking like a 10inch. 

I’ve never been a 12 type guy I’ve always liked the tighter sounds of 10’s. I bought the ground shaker box off eBay it holds 2 10’s or you can get one that holds 2 12’s.

Posted

can anyone steer me to an amp for my CTB door speakers... which I already upgraded? do I need special interfacing parts for factory head unit?

Posted
3 hours ago, tomleo67 said:

can anyone steer me to an amp for my CTB door speakers... which I already upgraded? do I need special interfacing parts for factory head unit?

As said earlier in the thread contct John at [email protected]

he makes the harnesses so no cutting required I just bought my sub harness with the lci2 this weekend 

Posted

To access the corner speakers in the dash do the grills just pry up or are the some bolts to remove ?? Thank you 

Posted
4 minutes ago, greco2003 said:

As said earlier in the thread contct John at [email protected]

he makes the harnesses so no cutting required I just bought my sub harness with the lci2 this weekend 

thanks trying to avoid reading thru 22 pages

Posted
1 hour ago, tomleo67 said:

thanks trying to avoid reading thru 22 pages

I have a harness with the aqua plug if anyone is interested. Don't have the truck any longer. $80 shipped.

Posted
7 hours ago, drewbiehd said:

I have a harness with the aqua plug if anyone is interested. Don't have the truck any longer. $80 shipped.

I'm def interested if this is what I need to add an amp?

Posted
9 hours ago, greco2003 said:

To access the corner speakers in the dash do the grills just pry up or are the some bolts to remove ?? Thank you 

You have to remove the A pillars first before you can pry up the dash speaker covers.

Posted
2 hours ago, tomleo67 said:

I'm def interested if this is what I need to add an amp?

It will work if you have the IOR infotainment system.There are 5 other system types(IO5-IO6-IOB-IOS-IOU) and if you have one of them then his harness will not work.

Posted
4 minutes ago, JH1973 said:

It will work if you have the IOR infotainment system.There are 5 other system types(IO5-IO6-IOB-IOS-IOU) and if you have one of them then his harness will not work.

I have no idea which one I have...

Posted

 

Keep in mind that if his harness is for subwoofer integration only then you'll have to cut the speaker wires in the middle of it and route them accordingly.If his harness is already set up for doing a full system then you're good to go.

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