Jump to content
SAU Community

Recommended Posts

i just finished putting an rb25neo from a stagea into my r32

i did a rough wiring job just to get the car started

im getting spark, injectors are pulsing and im seeing fuel getting squirted into the cylinder.

all timing marks on the belt are lined up

compression test results where 120psi on all cylinders on a cold engine.

but it wont start.

and it doesnt fire at all.

when i remove the cas and spin it manually while im cranking the engine, the engine fires

and when i spray aerostart into the manifold it also fires.

what could be the problem?

timing? firing order?

thanks

whats the cas drive in the camshaft like?

thanks for the reply

the drive is ok. and the cas is a secondhand item off an r34 rb25neo

are there two series of neo engines? would they have different cas's.?

Correct me if I'm wrong, but isn't 120 a bit low for compression? My r34 neo came up at 160 to 165 across all 6. Or are the stag neo's different?

it was done on on a cold engine and the engine hasnt been started for over a year. i would expect it to read alot higher if it was at normal operating temperature and properly lubricated.

the only reason i would be worried is if it wasnt even.

my understanding is that even if compression is low in one cylinder or across all cylinders it should still start.

Edited by beRwick_GTRage

hey there, is you cas aligned properly because i had a similar issue on my rb20 when i took it out. it wouldnt crank over until i put it in the right position. otherwise try running an ecu diagnostics check if you can. one of your sensors might not be working properly hence why your car is not starting. hope that helps!

hey there, is you cas aligned properly because i had a similar issue on my rb20 when i took it out. it wouldnt crank over until i put it in the right position. otherwise try running an ecu diagnostics check if you can. one of your sensors might not be working properly hence why your car is not starting. hope that helps!

hey

it shoudnt matter which position the cas is in, should it?. ive tried starting it in different positions anyway.

ive done a diagnostic check, came up with no errors.

update! please help

when i remove the cas and spin it manually in reverse! while im cranking the engine, the engine fires. but when rotating it in the correct direction it doesnt fire.

also when i remove the cas and spin it to fill the cylinders with fuel. then replace the cas and try starting the engine it starts and runs for a few seconds then stops.

is my problem fuel related or cas related?

its obviously getting fuel when i turn it manually.

hey

it shoudnt matter which position the cas is in, should it?.

yes it does
ive tried starting it in different positions anyway.
Then clearly the matching key inside the EX cam has broken. If the key was still there, then you could only mount the CAS in 1 position. (I don't know how many times that point has been made in previous threads!)
yes it does

Then clearly the matching key inside the EX cam has broken. If the key was still there, then you could only mount the CAS in 1 position. (I don't know how many times that point has been made in previous threads!)

why would it be clear that the key inside the ex cam is broken lol. he was asking me if the cas is properly aligned not wether the key was inserted the correct way.

i took the black plastic cover off the cas and watched the disc spin as the engine was cranking. as i said the cas drive is ok

because the key is what causes the CAS to be correctly aligned!

There is a semi-circular hole in the end of the CAS shaft, and a semi-circular protrusion on the end of the EX cam (well, there's supposed to be). The protrusion on the cam is supposed to fit into the hole in the shaft end. It serves two purposes - make sure the cas is in the correct position relative to the crankshaft (#1 piston), and it also helps drive the CAS. That protrusion is prone to breaking off, causing the problem you now have (incorrect CAS alignment).

because the key is what causes the CAS to be correctly aligned!

There is a semi-circular hole in the end of the CAS shaft, and a semi-circular protrusion on the end of the EX cam (well, there's supposed to be). The protrusion on the cam is supposed to fit into the hole in the shaft end. It serves two purposes - make sure the cas is in the correct position relative to the crankshaft (#1 piston), and it also helps drive the CAS. That protrusion is prone to breaking off, causing the problem you now have (incorrect CAS alignment).

thanks for the explanation. as i said the CAS drive is ok!!!!

engine is now running

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

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • 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. 
×
×
  • Create New...