Jump to content
SAU Community

Recommended Posts

Ok so all those with an SAFC II, know that the knock sensor needs to be calibrated.

So first you let the car warm up and set the knock at 1500rpm and then at 3500rpm. This sets the basline of the knock sesnor.

IE as per this post:

http://www.skylinesaustralia.com/forums/in...=132717&hl=

Ok so with the new ECU i have not reset the knock on the SAFC II so i could compear this to the new ECU to make sure it wasn't doing damage.

So with the new ECU, the knock values are exactly the same as before, well in the same range, zero most days when cold and creeps up to 10-15 on hot days and stayes there.

However i have an interesting question.

If you go to SENSOR CHECK screen, you can see the raw value of the knock sensor, now at idle with no load, my car showed 0065, not sure what the units are, at 6900rpm, the value was 0125, so that is double.

However, back in the MONITOR SCREEN, the value goes from 0, coresponding to 0065, and then to 10, corresponding to 0125.

SO WHAT THE HELL, i do not understand the Knock part of the SAFC II, if the car was actually knocking, it would be dead, long time ago, trust me. There is no audiable knock, it is not lean and timming is at 18 deg, as at 15 it seams slugish, so bumped it up one by one, and 18 seams great.

The Figures between the old ECU, stock nissan one, and the new ECU, Central20, are the same, but i do not understande how the vlues relate to eachother.

in the SENSOR CHECK screen, is the knock value in volts, milivolts, what.

HELP i am going insane.

PS. The car has new pump, FMIC and all supporting mods, including exhaust, no cat, new plugs, splitfire coils ect. ect. Compression is near enough tto 150psi across all cylinders, and plugs looked ok.

that raw sensor monitor is the 'volume' being heard by the knock sensors.. knock is only determined to have occured when the volume breaches a certain level ^_^ so basically, your sweet ;)

someone with more knowledge and exp better confirm this, but i definately seem to remember reading that.

I C, well i'm gona do a map trace to make sure it is all good, but so far i think it is ok. I can't hear any knock at all, and pinging, well that is a bit hard to tell, so hopefully i won't blow the engine. LOL.

yup.. always better to be safe than sorry..

remember that the knock sensor is just a microphone. Depnding on the mods your engine has, the engine sound will be different. So when you first calibrate your SAFC, you set the base 'knock value (basically, ambient noise) at 1500 and 3500 i think it was. this tells the SAFC what normal values are for your car. If the raw sensor value jumps by (as someone suggested in that other thread) 50 or 60 from base, then your probably getting some knock.

opps today on a hot day on peak recall i saw 52 knock max and 10 idle so i guess that is about 42 total. Still all good.

Got it booked into the tuner to do a run and hopefully, fingers crossed it will be all good.

Forget about the idle readings. And its a perculiarity that the SAFC shows more knock on idle when the weather is hotter too.

Its the max value from a peak recall after a hard run that matters. If its 60+ then its real knock. I've mucked around with an SAFC II for 2 years and thats what i found.

Cool, so as long as the differance between the idle and peak recal is 60, then it's all good?

Hay Busky2k, can you PM me with some more details explaining how it all works, the knock issue on SAFC II. Down here in tas there is no one to tune it properly, so i have to kind of so it myself and then check it.

So basically all i hve to worry about is the diferance between the idle monitor setting and the peak recal? Correct, as long as differance is less then 60 then all good.

Forget about the idle readings. And its a perculiarity that the SAFC shows more knock on idle when the weather is hotter too.

Its the max value from a peak recall after a hard run that matters. If its 60+ then its real knock. I've mucked around with an SAFC II for 2 years and thats what i found.

Is this in monitor mode or sensor check in ETC? in sensor check at idle mine is like 0036 or something from memory, in monitor i have only seen 0.

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

    • Consider a 35 too...
    • He's right ~ there is no 'magic' with stuff like this ... it is more likely that in the process of looking for the short, the loom/wire 'incidentally' got moved in the process, thus removing the short ~ now, that maybe a wire (in a loom) rubbing against the edge of some grounded metal, that's worn through the insulation, causing the (now intermittent) short to ground. If one wire in a loom has been damaged in this fashion, it's reasonable to presume that other wires beside it may have also be damaged, and now exposed...you can bet the green crusty copper corrosion will start... ...that'd be a pisser, Murphy's Law steps right in as GTS observes...but worse, something like that is easier to find when shorted...ie; unplug bulb and fuse, and put multimeter in continuity mode so you get constant beep, and carefully poke about hoping to find if some movemet of the harness stop the beeping.... ...it's still all a bit Arnie tho' ..It'll be back... 馃槂
    • Yeah, but knowledge of one wire's insulation worn through to short on earth implies the possibility of other wires doing the same. I had my power steering die, because the wire that runs to the solenoid valve on the rack runs in the same loom as the power wire for the O2 sensor. And when the O2 sensor/wire did something stupid and burnt part of that loom to death, the only indication was the shit(ter) fuel economy and the heavy steering. It took deep excavation of the looms in the bay to find the problem. Not wear through in that case, but similar shit.
    • Ah, I thought he'd wired it to one of the spare ECU inputs! Too long ago since I read that post, ha ha. I've been arguing with radiators, harmonic balancers, alternators and rust since reading it.
    • Correct. The ECU cannot read oil temp. (Well, I think it probably can in some situations. I did have the thought of potentially repinning the ECU when I was doing oil pressure). I am using this into the MPVI dongle, so that the MPVI dongle can read oil temperature. It is attached to a VDO gauge which is obviously calibrated to whatever curve the sender actually is using. This would be easy if I could setup a table of voltage to temperature like many sensors, but it appears I cannot do this and can only setup the transform rule which appears to be Input (voltage) x Multiplier, and add an offset. This to me means it MUST be linear. So it may be a complete waste of time wiring this into the ECU. The idea was that the MPVI3 has standalone logging. I wanted to use this instead of a laptop with serial cable (for wideband) for long datalogs. Given the wideband also has electric interference, I may never trust this either in a world where the serial wideband and the analog output wideband do not agree. Last time I did a trace I could see the two wideband traces follow each other, but one was a little leaner than the other. I plan on playing with voltage offsets and actually driving the thing to see how close they correlate. If they never correlate... then, well, maybe I'll never use either. Ideally I'd like to have the Analog wideband read ever so slightly leaner than the serial one, because the serial one is 'correct'. Tuning the car to be ever so slightly too-rich would be the aim. Not needing to have a laptop flying around in the footwell connected with cables is... an advantage. About the only one from the forced upgrade to MPVI3.
  • Create New...