Miata: Door speaker cabling

Wow.  That was the closest I've come to outright profanity in a long time.  For whatever reason the door grommet/gasket thingy in the Miata is an 'S' shape, and makes routing cabling through it nigh impossible.

Also, I had the choice between 18- and 14-gauge wiring for the speakers, not the 16- I wanted.  Probably should have gone with 18-gauge, as the 14- is rather chunky.  I was barely able to route the two runs of it through the door grommet, but it is done.  If you're curious, you must remove the grommet from the door and body - otherwise it's impossible to run.  I tried for an hour with various methods, ended up having to use a rod with the cabling taped to it even with the grommet removed.

I only got the one door done.  Between the high winds (media calling it a hurricane) and my wife wanting to watch Castle with me (who am I kidding, Nathan Fillion is witty and charming), didn't have time to do the passenger side.

Tomorrow hopefully will see the speaker wiring done (assuming I bought enough!!!) and amplifier power/remote wiring completed as well.  Still haven't thought about how I'll switch the amp on/off, or how I'll cover the old double-din location.

Stock speaker is actually decent.  Too bad one is blown.

I zip-tied the old wiring to itself, hopefully shouldn't rattle.

Naked doors.

I thought the stereo was kinda wobbly.  Pretty sure strapping is not OEM.

Back of the door panel, will need some cutting to fit the new tweeters.

I will be mounting the crossovers in here - no headunit FTW!

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more