Getting weird knock
i logged mine everytime i drove. simple and keeps the tune tight. mine is wired up through the EGR harness. on the corvette i bought HPT pro with teh afx wb to make it alittle easier this time around. only plus is that i dont need to have my laptop with me to log anymore. you read my FB statues to know why i dint get to install my WB today.
Sam, thanks for your help. The first tune i had in my car i paid for at quality. Because u blew off my phone calls but no big deal lol
The first tune i paid for is attached. The 2nd is help from 01z28camaro & HUMMER.
Can you tell me if the burst knock is 100% disabled?
The first tune i paid for is attached. The 2nd is help from 01z28camaro & HUMMER.
Can you tell me if the burst knock is 100% disabled?
yeah i knw ur busy its not a big deal. what exactly needs alot of work on the tune?
I don't think the aem wideband I posted above is the one you're running.
This is the correct PID function for the UEGO wideband ([PID.2811]/.5)+10
Verify the scanner and gauge display are reading the same AFR.
This is the one right ? http://www.aemintakes.com/instructio...-4100_inst.pdf
This is the correct PID function for the UEGO wideband ([PID.2811]/.5)+10
Verify the scanner and gauge display are reading the same AFR.
This is the one right ? http://www.aemintakes.com/instructio...-4100_inst.pdf
I just looked at that latest log, the IAT's look good as well as ECT. Once you can figure out how to log your A/F with the log you can rule out it being to lean or too rich causing it to knock. I think your timing is pretty conservative so I dont think thats an issue. Arent you running TR6's, what do you have them gapped at?
Another thing I noticed wrong in your tune that may or may not affect anything is that you have the MAF fail set to 32000hz, for a stock os to revert to speed density this has to be set to 0hz. I have the 3bar os also & I set the maf fail to 0 just out of habit when I went to 3 bar.
i have the maf set to '2 no mil light, under the DTC's'
As far as my actual wideband idk if i have the one that you posted since i cant see a pic. but this is the one that i have
http://www.amazon.com/AEM-30-4100-Di.../dp/B003ITFA9Q
As far as my actual wideband idk if i have the one that you posted since i cant see a pic. but this is the one that i have
http://www.amazon.com/AEM-30-4100-Di.../dp/B003ITFA9Q
Do you have this wideband? http://www.aemintakes.com/instructio...-5130_inst.pdf There is info here how to hook it up.
That is the wrong PID also for that wideband. You need to be logging EGR Position (V) as one of your PID's.
Try this setup with the config I posted on hptuners
That is the wrong PID also for that wideband. You need to be logging EGR Position (V) as one of your PID's.
Try this setup with the config I posted on hptuners
what value should i put just 0?
Also i got my wideband hooked up finally but the wideband is not matching up with whats showing. its slightly off. i think its because i had the wrong model number for the aem one that i have. is that why nitrous383? also the histograms in the config u sent me isnt working... lol
Also i got my wideband hooked up finally but the wideband is not matching up with whats showing. its slightly off. i think its because i had the wrong model number for the aem one that i have. is that why nitrous383? also the histograms in the config u sent me isnt working... lol
Custom PID's do not transfer when you try to send them to someone. The correct wideband function is ([PID.2811]/.5)+10 for your wideband, plug that in and try it.
You will also need to setup a user defined AFR Error % function. Mine is setup for a NGK wideband so use this function instead:
100*((([PID.2811]/.5)+10)-[SENS.121])/[SENS.121]
Make sure on histogram #7 and #8 to select the AFR Error % PID you just created to plot the values.
I setup a boost PID which is always kind of handy so you're not trying to convert KPA to boost. You may have to do a little work for your 3 bar map sensor as I'm not sure what the PID# is for a 3 bar. The function for the 2 bar PID is ([PID.2333]-[PID.2340])*.145
PID.2333 is for a 2 bar sensor so just change it to the 3 bar PID. Keep in mind you will need to scan the barometric sensor PID.2340 for this to work correctly. Here are some pics included to help explain, do not add any values to the sensor or units as the beta version has a glitch not allowing it to work correctly. I have reported the issue and they are aware of it.
You will also need to setup a user defined AFR Error % function. Mine is setup for a NGK wideband so use this function instead:
100*((([PID.2811]/.5)+10)-[SENS.121])/[SENS.121]
Make sure on histogram #7 and #8 to select the AFR Error % PID you just created to plot the values.
I setup a boost PID which is always kind of handy so you're not trying to convert KPA to boost. You may have to do a little work for your 3 bar map sensor as I'm not sure what the PID# is for a 3 bar. The function for the 2 bar PID is ([PID.2333]-[PID.2340])*.145
PID.2333 is for a 2 bar sensor so just change it to the 3 bar PID. Keep in mind you will need to scan the barometric sensor PID.2340 for this to work correctly. Here are some pics included to help explain, do not add any values to the sensor or units as the beta version has a glitch not allowing it to work correctly. I have reported the issue and they are aware of it.
I know the custom pids dont transfer but on your config i can view my wideband just fine. but when i try to do it in my custom config it says undefined parameter?
Is there something else im missing for just the simple function and pid?
once i am able to view my AFR's on my table in scanner i think i will be able to set it up and plot it for the histograms.
Is there something else im missing for just the simple function and pid?
once i am able to view my AFR's on my table in scanner i think i will be able to set it up and plot it for the histograms.
see heres my latest log with the wideband going as well and i still have 4* of knock up top! i dont get what else it could be from unless its to much fuel.
I doubt its spark because im running 12* of timing??
I doubt its spark because im running 12* of timing??