Jump to content
SAU Community

Recommended Posts

hey guys

Recently bought v35 coupe and having a few dramas.

its a 6sp manual and has had a button clutch/lightened flywheel fitted. now im stressing about the transmission as when you first take off (release clutch, load up trasnmission) the gearbox makes this weird vibration/pulsing/deep knocking noise... really noticable through the gear knob (rattles badly). the vibration happens with engine rpm increase... follows it perfectly, definatly something spinning too.

it wont do it on deceleration, nor in netural (with clutch in or out) and i even jacked the rear of the car up, placed in gear and let the wheels spin in the air.... no noise/vibration, so must need load on the driveline.

the engines runs freely, no knocks or noises and the trans shifts smoothly... just the horrid vibration.

i have read plenty of info regarding removing the stock duel-mass flywheel and replacing with a lightened unit creating lots of noises and transfering vibrtions.. but i just cant see this being normal!!

has anyone else out there exprienced something like this?

the only possible things i could think of are

-damaged spigiot bearing?

-worn bearings in trans

-damages imput shaft

-incorrectly fitted clutch/flywheel (but think it would always make noise then)

-excessive lash between gear sets?

-shifter flogged out and just ratteling around with engine rpm (thinking it may be a short-shift kit, very short shifts.. never seen stock to compare)

-worn diff bushes, allowing the diff to move under heavy load, thus moving the tailshaft a tiny bit out of whack?...(prob stupid but taking a stab in the dark)

if anyone can shed some light on the situation i would greatly appreciate it..

sorry if this post is hard to understand, its hard to try and explain the problem. im going to record a vid and upload so you can hear the problem.

thanks guys, alex

Link to comment
https://www.sau.com.au/forums/topic/366915-strange-vibration-in-trans-6sp-man/
Share on other sites

  • 1 month later...
  • 5 years later...

I'm bringing this back from the dead, hoping someone may be able to help.

I have a recent purchase 2004 v35 sedan 6mt with the load vibration/knock/rattle noise on acceleration but not cruise or deceleration in all rpm/all gears.

I replaced the oem dmf clutch with a locally sourced exedy uprated clutch/npc smf kit - NSK-7454SMF, I use Castrol VMX-M 75W-85 transmission fluid.

The first clutch install was botched by a local gtr specialist workshop (it made the noise then), a new clutch was fitted along with my dad/I replacing the important input and output shaft bearings in the CD008 gearbox before reinstallation by another workshop.

After the new clutch install I still have the same acceleration vibration as before.

The pedals/gear knob vibrate badly with the accompanying rattle/knocking noise.

I took the car to a car importer familiar with v35s and he said it was normal for the CD008, and that the CD009 was as better transmission.

I have listened to videos and don't believe it's rod knock or knock from bad fuel, the diff bush is flogged so will be replacing that soon.

Any ideas or 350z/v35 experts in melbourne who may be able to help diagnose please let me know.

 

 

 

 

 

Not normal for any V35 6MT..  only difference on the CD009 was improved multicone synchos.

Have you checked engine mounts/transmission mount, diff mounts?

How did the first workshop 'botch' the clutch install?  did they possibly cause some damage which is causing the fault and it hasn't been fixed?

The problem was there after the botched clutch install and now after new clutch install. 

The second workshop checked only trans mount, but I'll check all mounts.

I suspect the exedy clutch kit wasn't balanced, but lets see if the mounts are ok.

Interesting that an importer (not the importer of the car) said it's normal, hmm, pretty rough compared with my long throw vibration-free r34 gearbox.

 

 

If it was normal, it would have been there before the first clutch install.

One of my pet hates is car dealers and sometimes mechanics saying 'they all do that, it is normal'..

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


  • Similar Content

  • Latest Posts

    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
    • I don't think it's a good buy, the trend looks bad     lol.
×
×
  • Create New...