Page 1 of 1
Knock count reading, but not connected
Posted: Wed Mar 06, 2013 12:56 pm
by brett_32i
hi,
another ghost reading!
my ecu doesn't have a knock board as it isn't turbo (but it thinks it is)
i am getting erroneous readings for knock count.
can i disable it in nistune?
Re: Knock count reading, but not connected
Posted: Wed Mar 06, 2013 6:50 pm
by Matt
You have a VL turbo ROM image loaded into the Nistune board (for an RB30ET/E+T application)
There is no way to disable the input because Nistune does not know if the board is installed in a proper VLT ECU (with knock board) or not. Would just suggest ignoring the knock count from the ECU
Re: Knock count reading, but not connected
Posted: Wed Mar 06, 2013 9:10 pm
by brett_32i
so i just ignore it?
or set the ecu to ignore it?
Re: Knock count reading, but not connected
Posted: Thu Mar 07, 2013 1:19 pm
by Matt
Would suggest just ignore it. The ECU responds to a knock count query from Nistune. I could offer an option not to gather the knock count perhaps
Re: Knock count reading, but not connected
Posted: Thu Mar 07, 2013 8:11 pm
by bachig24u
wish it was as simple as grounding a pin on the knock board connector.
Re: Knock count reading, but not connected
Posted: Fri Mar 08, 2013 10:51 am
by Matt
It probably might be. I would have to work out what each pin does again. One is used for resistance measuring (DTC knock fault code) and another passes the pulse through
Re: Knock count reading, but not connected
Posted: Sat Mar 09, 2013 4:19 pm
by brett_32i
ok, so although the ecu is reading something, nothing is actually being done with the input. ill just ignore it then.
Re: Knock count reading, but not connected
Posted: Mon Mar 11, 2013 11:21 am
by Matt
Thats correct with these older ECUs knock count does not pull timing due to the fault code