EvoScan for Evo X Beta Parameter CAN-ID's? Log attached
Thanks WarmAndSCSI for your contributions! They seem to work for me - now all we need is boost and load 
BTW, I'm also at high elevation and I think my car at 5000 feet is hitting lower load cells than typical stock evo x's. I believe load is really topping out at between 180-200 at 3500-4500 rpm's and dropping from there (compared to a stock X at sea level that tops out between 200-220 load). Hitting lower load would explain the slightly higher timing advance values we're seeing.
Also, I tried both 11-1 and 11-3 for knock sum and both stay at zero in all my logs. I guess the only way to truly find out if it's working is to advance timing until it registers knock?
I'd appreciate anything you can share on boost or load logging!
BTW, I'm also at high elevation and I think my car at 5000 feet is hitting lower load cells than typical stock evo x's. I believe load is really topping out at between 180-200 at 3500-4500 rpm's and dropping from there (compared to a stock X at sea level that tops out between 200-220 load). Hitting lower load would explain the slightly higher timing advance values we're seeing.
Also, I tried both 11-1 and 11-3 for knock sum and both stay at zero in all my logs. I guess the only way to truly find out if it's working is to advance timing until it registers knock?
I'd appreciate anything you can share on boost or load logging!
I knew that but wasn't sure where to paste these lines or if I can insert new lines between the existing ones? Is the order important?
Thanks WarmAndSCSI for your contributions! They seem to work for me - now all we need is boost and load
BTW, I'm also at high elevation and I think my car at 5000 feet is hitting lower load cells than typical stock evo x's. I believe load is really topping out at between 180-200 at 3500-4500 rpm's and dropping from there (compared to a stock X at sea level that tops out between 200-220 load). Hitting lower load would explain the slightly higher timing advance values we're seeing.
Also, I tried both 11-1 and 11-3 for knock sum and both stay at zero in all my logs. I guess the only way to truly find out if it's working is to advance timing until it registers knock?
I'd appreciate anything you can share on boost or load logging!
BTW, I'm also at high elevation and I think my car at 5000 feet is hitting lower load cells than typical stock evo x's. I believe load is really topping out at between 180-200 at 3500-4500 rpm's and dropping from there (compared to a stock X at sea level that tops out between 200-220 load). Hitting lower load would explain the slightly higher timing advance values we're seeing.
Also, I tried both 11-1 and 11-3 for knock sum and both stay at zero in all my logs. I guess the only way to truly find out if it's working is to advance timing until it registers knock?
I'd appreciate anything you can share on boost or load logging!
Thread Starter
Evolved Member
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
I'm running the stock map and timing dips down to 11 degrees at the lowest point. Basically, all my values are about 2 degrees higher than what Bryan posted for stock X's, and I believe this is due to the car making less power (less dense air) at high elevation.
Newbie
Joined: Jul 2008
Posts: 55
Likes: 0
From: Little Elm, TX
I have verified that 11-1 is knock for Evo X MR. I logged knock, got some knock, then took timing out, and no more knock. Sweet. I did notice that when you open the log in Excel, it shifted the value to 11-2. I can't explain that one. Maybe the numbering got off somewhere in the definition file.
I will verify on my GSR tonight.
I will verify on my GSR tonight.
Did you copy the data.xml that was supplied with the beta into the install folder? It looks to me you don't have any EvoX parameters.
Evolving Member
Joined: Aug 2008
Posts: 147
Likes: 0
From: Singapore
I copied everything in the beta zip files into the program file directory. When I launch evoscan and press CTRL E, I can edit and see the EvoX parameters though...
AFR Logging
Just wondering if anyone has successfully logged AFRs using an USB interface on Evoscan. I'm using the AEM UEGO WB O2 with an USB adpater and it logs for about 2 seconds, then cuts off. Most people have success with direct serial port logging but I only have USB ports on my laptop.
I can log with PCMScan correctly and the proper COM port is selected so I'm sure it's not a hardware issue. It seems to be an issue with Evoscan and serial/USB adpaters.
I can log with PCMScan correctly and the proper COM port is selected so I'm sure it's not a hardware issue. It seems to be an issue with Evoscan and serial/USB adpaters.
hrmm 11-1 isn't knocksum on the GSR.
maybe the CANID bug got my evoscan confused, but I didn't see the usual KS behavior with 11-1.
need to log less things - getting 1 second jumps logged EVERYTHING
maybe the CANID bug got my evoscan confused, but I didn't see the usual KS behavior with 11-1.
need to log less things - getting 1 second jumps logged EVERYTHING
11-3 seems to work for me on the GSR, I crossed referenced it ECUTek DeltaDash and got the same numbers.
It worked for me. Every decline in timing was accompnied by a change in the KS.
I am not sure about the IPW and IDC. The IDC hits above 100% on this tuned Evo X. The AFR is at 10.9-11 by redline and the boost is at 18.7 psi. The IDC is at 99.88%. It just seems too high.
Check the log and tell me if IDC and IPW are normal.
I am not sure about the IPW and IDC. The IDC hits above 100% on this tuned Evo X. The AFR is at 10.9-11 by redline and the boost is at 18.7 psi. The IDC is at 99.88%. It just seems too high.
Check the log and tell me if IDC and IPW are normal.
Last edited by nj1266; May 4, 2009 at 07:46 AM.
