Jump to content

Recommended Posts

Posted

Just figured I would post some photographs and details about a recent Subwoofer install I did on my AT4 with BOSE.  I noticed there is not a lot of information out there currently on adding a non factory subwoofer.  Overall I found the process very simple especially since I purchased a wiring harness from A.I.S Audio which worked flawlessly.  Loving the amount of extra bass now. Subwoofer is a JL10 thin woofer paired with a Kenwood Exceleron monoblock.  Figured I would post in case anyone else is on the fence about this upgrade and wondering how to accomplish it.

240917706_543576220281460_4590894295208289683_n.jpg

240829234_4291503560932785_1247048022643813499_n.jpg

240944527_263253085622959_5532495099781544109_n.jpg

  • Thanks 1
Posted
20 hours ago, TxTruckMan said:

Nice. But my kids would destroy that Amp. Where did the harness connect to for inputs?

Harness plugged into the Bose amp behind the rear seats. Super easy plug and play using the PAC LP7

  • Like 1
Posted
58 minutes ago, AML said:

Where did you source the woofer box?

Got lucky and found a shop locally who had one that was custom built.  I just needed to carpet it, then I added some extra pieces on the front so I could downward fire it.  I thought it worked out pretty nice.

Posted

Incase in the future you decide the bass is a little too strong like I did you can swap out the 2 front dash speakers to help. I added audio frog 2.5 upfront and it helped with the clarity a ton. I did not amplify them just ran them off of the factory bose amp. 

  • Like 1
Posted
On 9/15/2021 at 2:14 PM, snowman44 said:

Did you trim your underneath storage?  I have same set up with the storage and dont want to have to take whole thing out to put in sub.

Yes I just cut the underneath storage using a very sharp reciprocating saw and also cut in a few notches on my all weather mats. 

  • 2 months later...
Posted

Where exactly is the factory amp? Working on a truck with the bose system and the rear seats don't fold down they have the storage cubbies in the seats. Will I have to remove the rear seats? 

Posted

Smack dab in the middle of the back wall along with the inverter 
 

have to remove the back seat to get to it 

 

there are a few tutorials on YouTube on how to do it

 

 

Posted

I found the factory amp. Would anyone know which outputs are for the factory subs in the dash? 

 

I have searched all over A.I.S. Audios website and have not found the harness O.P. is referring to... Maybe I'm blind

  • 2 years later...
Posted

I really like how you trimmed down your storage part. I’ve been wondering if there’s anyone out there that has done an install but with keeping the storage compartment. Because I would like to do the same just center the subwoofer and keep the storage on the sides. You kinda gave me an idea. 

  • 5 weeks later...
Posted
On 6/6/2024 at 8:58 PM, Anthony Gill said:

I really like how you trimmed down your storage part. I’ve been wondering if there’s anyone out there that has done an install but with keeping the storage compartment. Because I would like to do the same just center the subwoofer and keep the storage on the sides. You kinda gave me an idea. 

 

PXL_20220822_160129897.jpg

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

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...