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?
Knock count reading, but not connected
Moderator: Matt
Knock count reading, but not connected
- Attachments
-
- NIStune_2013-03-06_0959_54.csv
- (405.1 KiB) Downloaded 208 times
-
- knock count.JPG
- (222.86 KiB) Downloaded 2808 times
Re: Knock count reading, but not connected
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
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
so i just ignore it?
or set the ecu to ignore it?
or set the ecu to ignore it?
Re: Knock count reading, but not connected
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
wish it was as simple as grounding a pin on the knock board connector.
Re: Knock count reading, but not connected
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
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
Thats correct with these older ECUs knock count does not pull timing due to the fault code