Jump to content
SAU Community

Recommended Posts

Just finished installing my poncams and valve springs. Started the car and first crank started no worries worked all day. Now just set the timing to 15 degrees went for a light drive no boosting and was going fine no probelm them all of a sudden at the lights stalls and doesnt start again.

Took off the top timing belt cover and checked if the cams were still alligned and they are both alright havnt skipped and the belts tension seems fine so I dont see how it could have skipped a gear so running out of ideas.

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/
Share on other sites

have checked all the connectors there fine, have taken off both timing belt covers and belt has not skipped, have checked for fuel and have spark. Just dont get it ran normal than all of a sudden at lights stalls and thats it.

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/#findComment-5617675
Share on other sites

Don't convince yourself it's anything at all to do with the cams. You'll probably find that it would have happened regardless of whether you changed them or not. Just check the usual things.

Although, CAS could play a part in this, maybe not the plug but it could have died as a result of being removed.

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/#findComment-5617684
Share on other sites

Just abit of an update. I have noticed the back of the cas had made contact with the cam gear bolts and has sort of grinded it as you can see in the pic. I think it happened due to I didnt put the top timing belt cover on. Could this affect the CAS?

post-50426-0-14735100-1294623131_thumb.jpg

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/#findComment-5617905
Share on other sites

have checked for fuel and have spark

and?

you need to have the timing belt cover or a spacer of the same thickness between the CAS and its bracket, otherwise it gets pushed into the cam too far. cant see anything wrong with it from that picture tho?

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/#findComment-5617925
Share on other sites

yep I reckon youve kill the cas, I was told to be sure to use the rubber spacer that is on the cam gear cover otherwise as stated above the cas sits too far in, and yep can kill the cas, I was running no timing gear cover but the tuner said it was a common mistake to have happen and he sees it often

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/#findComment-5618078
Share on other sites

Just put everthing back together and put it on with the timing cover this time started up first crank guess I was lucky didnt kill the CAS. Its one of those things that are really simple but you just dont think about it.

Link to comment
https://www.sau.com.au/forums/topic/349750-r33-problem/#findComment-5618233
Share on other sites

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

    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • 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!!!
×
×
  • Create New...