Miata: Stereo update

Yes, it is complete!  Ish.  Sort of.  Not really.  But I once again have a semi-functional audio system in the car!  It sounds way better than I'd anticipated, although I guess the components/amp are to thank for that.

The actual amp install was pretty easy - the gas tank doesn't come near that part of the chassis, so was safe to drill/screw through.  I am not that happy with using 4ga wire...primarily since I had to cut it down to fit the amp's input terminals.

After an hour's drive to work, amp was barely warm.  Granted was only streaming CBC.  Will upload some trance stuff, see how it fares with some thumpin'.

My stereo tip of the day: When crimping connectors, use vise-grips.  Way better than the 'middle' section of the side cutters I've been using for 10 years.  Also better than a hammer.

Items left to work on:

  1. Securing & tidying the wiring
  2. A non-ghetto solution to the remote switch
  3. A solid solution for mounting the crossovers (some sort of tray, maybe?)
  4. A blanking plate for the gaping hole
  5. Mounting solution for the phone
  6. Charger cable wiring
  7. RCA->3.5 cable wiring
The tweeter holder...modded somewhat.  
The one that came with the tweeters on the right, Dremel'd version on left.

Batt'ry connections.

Ground point I used, directly bolts into the body.

Metal the amp is attached to.

Amp holder peeking out...needs to be bolted down.

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