Nistune Forums

I've searched all over and can't find an answer to this one, not many people seam to do anything with the R33 ECU. Last year I had mine remapped to 425bhp (Using tuners ECU then burning a chip and putting it into mine) and I've noticed the engine knock a few times. It only seams to do it at full boost in 5th.

Q1 .My question is why isn't the ECU switching to the knock tables

Q2. I've tried to do some digging on it and I've read a few things about R33's not having a knock sensing board

I'm currently just getting a few bits and pieces together to put on to the car and it's going to require another remap. So I'm going to put a Z32 300zx ecu with a type 2 board in, and with a little help from a friend with some mappping knowledge get the car running a little better.

Q3. Will the Z32 ecu pick up on knock and do something about it unlike the apexi PFC which just flashes a light at you

Q4. Can nistune monitor knock I've got datascan and it semas to monitor just about every engine sensor apart from the knock sensors


I've put a list of the important bits of the cars spec below:
standard unopened engine
standard turbo but reworked to it's limit and rebuilt with steel internals (good for 450bhp ish)
power enterprise 550cc injectors
FMIC
3" exhaust from turbo back (no cat)
HKS EVC5 Boost controller
AEM EUGO afr gauge
Apexi boost, oil temp + pressure, exhaust temp gauges

Soon to be fitted Front entry inlet plenum

thanks in advance for any help you guys can give

Andy.

Hi Andy

1. Not sure why ECU doesnt switch to knock maps. How do you know it isnt? Perhaps the tuner made the knock maps same as the primary maps so there is no switching

2. Hitachi later model ECUs (R33) and JECS M7790 processor ECUs dont have knock sensor board, they are actually inside one of the components inside the ECU itself

3. Z32 will detect knock and then if it reaches a sufficient count will pull timing / jump to knock maps

4. Nistune cannot monitor knock for Z32 yet... this is something I'm working on as an enhancement in spare time and some ECUs are proving more difficult than others.

Consult does not report knock count ... because it is an ever growing number. Just streaming out a knock count value wont help much

Nistune implements in internal knock counter and spits it out each consult read, and then resets the counter inside the ECU. this allows us to map count against particular cells in the fuel map when the knock occurs. It requires custom code to do this properly.