Skip to content

Audio Upgrade Finished

Featured Replies

Just finished a bit of (for me) a mammoth build. Was very disappointed with the stock audio, and Canton wasn't available at the time. Have ended up installing the following:

  • Match m5.4 DSP (Running Active crossover for the fronts. The rears are still off the HU, and I generally just run it faded to front. I may add another amp and take a line out of the DSP to it to drive the rears at some point).
  • Focal Flax PS165FE
  • Match PP8E-Q Subwoofer (under trunk floor)
  • Musway aluminium speaker rings
  • Dodo speaker surround foam / back foam

 

Got the last of it in today, and I can say after a (very rough) DSP tune I'm really quite happy with it. I understand the speakers take a lot more running in, and I need to do a better job of both the input and the output EQ, but it sounds night and day, like something I'm going to enjoy listening to. 

 

Biggest challenge along the way turned out to be how best to power the amp. I wanted to use high power mode so that I can drive 60Wpc from the Match, and 120W to the sub. I ended up finding a salvage fuse box, and removing the wire from the back of one of the maxi fuses to put in an unused maxi slot in my car. The dash crossmember has some really good grounding points, and both of the above are right where the Match ended up (behind the glovebox).

 

The only bit that I'm struggling with now is the input EQ, or ideally flattening the sound dataset on the MIB3. I've tried just about every different adapter and software going, but don't seem to be able to read / write the datasets (even though both OBDEleven and VCTool suggest I should be able to). I've ended up with a DoIP adapter now which is fantastic, and I rather like VCTool. Does anyone have an ODIS / VCDS / VCP setup in SE London / Kent that they'd be willing to help with in return for many crates of beer?

 

Happy to share any further details of the build. 

 

Salvaged fuse terminal on Match harness:

725BC6FF-9019-4BA2-A2AA-FD9A2249F3A4_1_105_c.thumb.jpeg.6f138cf52ad836f7041a1669755b5a31.jpeg

 

Match hiding on side of glovebox:

90E4A42F-6F4F-40FE-9F29-B91813CCE80A_1_105_c.thumb.jpeg.a58d5a3b85d25bd69bba1170189565b8.jpeg

 

Wires fairly neatly tucked away:

3431578A-CF00-4EFB-A4CC-B2E0DE0C96E9_1_105_c.thumb.jpeg.d2d37ce88158a331d9e533a58ab295e4.jpeg

 

Stock tweeter location:

A9056C75-C1F7-494A-996B-B0913CB374BD_1_102_o.thumb.jpeg.4e923640727733e5fd096fac6dc35f2c.jpeg

 

Musway alu rings in place:

2E85E6D9-5E60-4731-B5ED-D5B4C8B6E375_1_105_c.thumb.jpeg.e8378f613624c9eb0000c8bc9b1e395b.jpeg

Edited by bdavbdav

  • Author

Remaining to fix / do:

  • Hopefully flatten the sound profile of the MIB3
  • The center speaker is still there, and annoyingly if I disconnect it, SOS throws a fault code / error in dash. Not sure how to silence it, or how the radio is configured to play audio through the SOS module. There seems to be no coding / adaptations for it.
  • Still unsure on the input sensitivity on the match. There doesn't seem to be a straightforward way to work this out.
  • Author

Subwoofer fits perfectly wedged in foam in boot

IMG_4634.jpeg

On 25/10/2024 at 13:14, bdavbdav said:

Remaining to fix / do:

  • Hopefully flatten the sound profile of the MIB3
  • The center speaker is still there, and annoyingly if I disconnect it, SOS throws a fault code / error in dash. Not sure how to silence it, or how the radio is configured to play audio through the SOS module. There seems to be no coding / adaptations for it.
  • Still unsure on the input sensitivity on the match. There doesn't seem to be a straightforward way to work this out.

try without the subwoofer, just connected the DSP and try it.

  • Author
3 hours ago, manuelin said:

try without the subwoofer, just connected the DSP and try it.

Sorry not sure why you mean?

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.