Nissan 370Z Forum

Nissan 370Z Forum (http://www.the370z.com/)
-   Forced Induction (http://www.the370z.com/forced-induction/)
-   -   Help with possible Knock issue (http://www.the370z.com/forced-induction/139274-help-possible-knock-issue.html)

Z4fun 12-10-2023 07:28 AM

Help with possible Knock issue
 
2 Attachment(s)
Hi,

I have a vortech v3 , stillen kit with top gunz a2a upgrade in my Z. it was originally tuned on uprev for years with 19 degrees of timing on top and no knock and had the stillen 600CC injectors and 9PSI pulley in florida and intake temps around 120 ish summer. Tuned by admin

I switched to ecutek after doing the soho intake relocation and seeing the afr's were getting lean. I re-tuned with admin the car was running fine no knock and 19 degrees on top, but injectors were maxed and startup was not good on SD tune.

Recently I upgraded to 1050cc ID injectors and re-tuned with Seb, the timing is the same but im getting possible knock in the mid rpm range but only sometimes. I can do the same pull twice and once will have knock sensor pass the threshold on one cylinder like 4 or 5 kind of random with each test and the car will pull timing 1 to 2 degrees. I will attach logs and pic.

I would like to know what is your knock thresholds and timing compared to mine, on the dyno its making almost 500 whp.

I'll attach 2 logs please let me know if any ideas, my next step is to add octane booster to test the knock.

Spooler 12-10-2023 12:22 PM

Do you have a proper set of catch cans? If not, install those and see if it improves.

ByThaBay 12-11-2023 01:20 PM

What you need to do is run this program on a set of logs covering the entire RPM range:

https://www.dropbox.com/s/ww0pvzp2a6...ilder.zip?dl=0

This program will reconstruct the knock threshold table from within the tune and will show if it has been tampered with directly. There are also other ways to disable or desensitize knock sensors, but based on the data you're posting, I think you're after determining the KS threshold table from within your tune.

In order to determine the factory table, we need to know your calibration ID. If you can post it, I can open the stock rom and post the stock KS threshold table for you to reference. You can then compare the generated table from your logs VS the oem table to see what kind of tampering has been applied.

ByThaBay 12-11-2023 01:20 PM

let me know if you need help running the program.

Z4fun 12-11-2023 01:47 PM

@spooler yes I have duel catch cans.

@bythebay , thanks will download it, try to run it this evening and get back to you.

Just fyi, since seb tuned it I dont think I can edit the tune if we find something

Z4fun 12-11-2023 01:52 PM

Quote:

Originally Posted by ByThaBay (Post 4047565)
What you need to do is run this program on a set of logs covering the entire RPM range:

https://www.dropbox.com/s/ww0pvzp2a6...ilder.zip?dl=0

This program will reconstruct the knock threshold table from within the tune and will show if it has been tampered with directly. There are also other ways to disable or desensitize knock sensors, but based on the data you're posting, I think you're after determining the KS threshold table from within your tune.

In order to determine the factory table, we need to know your calibration ID. If you can post it, I can open the stock rom and post the stock KS threshold table for you to reference. You can then compare the generated table from your logs VS the oem table to see what kind of tampering has been applied.

Where do I find the calibration ID ?

Z4fun 12-11-2023 01:58 PM

Quote:

Originally Posted by ByThaBay (Post 4047566)
let me know if you need help running the program.

Yes, please advise how to run this program?

redondoaveb 12-11-2023 05:47 PM

What did Seb say? Have you talked to him?

ByThaBay 12-11-2023 06:39 PM

Quote:

Originally Posted by Z4fun (Post 4047570)
Yes, please advise how to run this program?

You must have Java installed. Search "download java" then simply drop your log files into the same folder as the .bat and .jar files, and double click the .bat file - the program will run and will produce a new KS table for you to review.

You can get the calibration id by using ecutek query ecu or using the bluetooth to check "ecu information"

Z4fun 12-12-2023 03:40 PM

Quote:

Originally Posted by redondoaveb (Post 4047575)
What did Seb say? Have you talked to him?

Yes, he said he's not to sure if its real knock and to run octane booster to see if it changes.

I ordered his recommended boostane and waiting for it.

Z4fun 12-12-2023 03:42 PM

Quote:

Originally Posted by ByThaBay (Post 4047576)
You must have Java installed. Search "download java" then simply drop your log files into the same folder as the .bat and .jar files, and double click the .bat file - the program will run and will produce a new KS table for you to review.

You can get the calibration id by using ecutek query ecu or using the bluetooth to check "ecu information"

Thanks for the info, will try it when I get home.

Z4fun 12-13-2023 11:16 AM

1 Attachment(s)
Quote:

Originally Posted by ByThaBay (Post 4047576)
You must have Java installed. Search "download java" then simply drop your log files into the same folder as the .bat and .jar files, and double click the .bat file - the program will run and will produce a new KS table for you to review.

You can get the calibration id by using ecutek query ecu or using the bluetooth to check "ecu information"

I ran the program it created a new file called ks.map.new I attached it for review, thanks again.

I found this Cal ID - #Ecu 1 CALID: 1TH1B

ByThaBay 12-13-2023 01:19 PM

Quote:

Originally Posted by Z4fun (Post 4047596)
I ran the program it created a new file called ks.map.new I attached it for review, thanks again.

I found this Cal ID - #Ecu 1 CALID: 1TH1B

it looks like you ran it on a narrow rpm range only , 1600 rpm to 6300 rpm - if you want a more accurate table you'll want to feed in as much data as possible for the widest range possible.

ByThaBay 12-13-2023 01:33 PM

1 Attachment(s)
Kudos to you for running the program - you've taken the first step to awareness!

I pulled out your data and the OEM knock threshold table then I did the math to calculate the % threshold difference. It looks like within your log data your thresholds show to have been increased on average over 55% with some areas having the threshold more than double the factory allowance! According to ecutek tuning guide here: https://ecutek.zendesk.com/hc/en-gb/...ents/204332925

Quote:

Raising these maps by 5% (or maybe 10%) will make the ECU less sensitive to knock retard but
you MUST always check for detonation with a 3rd party device.
Given that your thresholds have been raised far beyond the mentioned 5/10% I would give some serious consideration as to why and what risks are being accepted by doing this.

It's not uncommon to have issues with the knock detection system for a variety of reasons and false knock is a real thing. The key take-away here is that the less sensitive (higher threshold) the ecu is to knock, the more likely that real knock will get missed.

Attachment 152801

Z4fun 12-15-2023 08:42 PM

Quote:

Originally Posted by ByThaBay (Post 4047600)
Kudos to you for running the program - you've taken the first step to awareness!

I pulled out your data and the OEM knock threshold table then I did the math to calculate the % threshold difference. It looks like within your log data your thresholds show to have been increased on average over 55% with some areas having the threshold more than double the factory allowance! According to ecutek tuning guide here: https://ecutek.zendesk.com/hc/en-gb/...ents/204332925



Given that your thresholds have been raised far beyond the mentioned 5/10% I would give some serious consideration as to why and what risks are being accepted by doing this.

It's not uncommon to have issues with the knock detection system for a variety of reasons and false knock is a real thing. The key take-away here is that the less sensitive (higher threshold) the ecu is to knock, the more likely that real knock will get missed.

Attachment 152801

Thanks so much for your reply! I will run more logs with full rpm soon.

Im surprised because all of my tunes were on dynos and no knock. Also the ECUTEK recommended knock threshold change is that for Supercharged Z's? I've heard from some tuners that they make alot more noise.

If anyone on the forum has a supercharged Z with stillen, vortech, topgunz, SOHO ect.. can you chime on ur knock thresdholds as well please it would be nice to compare. Thanks.


All times are GMT -5. The time now is 07:01 PM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 PL2