Miata 1.8 swap done - next steps

To keep it short...

  • Swap went well
  • Managed to snap some key coolant piece was the only issue at the time, decided to do the coolant re-route
  • Also managed to incorrectly assume that the clutch would not need re-adjusting because...hey I haven't changed clutch components or drained the fluid or anything...
  • The above caused me to run for 2 weeks on a misadjusted clutch, so the shiny FM Stage1 clutch is now pretty much toast - we played with the adjustment afterwards to try and salvage it...no luck
  • I've decided to get off the 'because racecar' bandwagon - ordered the OEM-level value clutch, and I'll get the 1.8 flywheel I have resurfaced
  • The de-powered steering thing has become a saga...continue to have 'stiction' issues
Had the bushings done (IL Motorsports rubber ones), only the mechanic didn't replace the rear bushings due to some miscommunication.  The good news is that alignments are now holding, the bad news is that 1 week after the fronts were done (and rears not), I started getting noises in the rears.

Also getting a clunk noise that I'm hoping is the hard top being slightly loose (latches didn't really 'pull' shut)

Anywho, list of stuff to do...
  1. Get flywheel resurfaced
  2. Engine out, but this time not a weekend blitz
  3. Replace clutch/flywheel/clutch fork
  4. Install coolant re-route & front block-off
  5. Install 1.8 crank pulley, 1.8 WP pulley, 1.8 alternator
  6. Put on replacement hood hinges
  7. FM front sway
  8. Maybe going to try out a thicker trans fluid (suspect the 'exhaust' noise I have is gear lash...?)
  9. Need to do BG oil flush & BG injector flush
  10. REALLY REALLY REALLY clean the engine/trans/everything - suspect oil leaks but can't really tell if it's oversprayed penetrant from the mechanic, spills from filling shift turret, or what
  11. Time available for rear bushing install?
  12. Stop by a body shop and see what rust repair & paint will actually cost

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 of us work in seem to apply this as law - an
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 on
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-5E67-4DA1-99A
Read more