EvoScan for Evo X Beta Parameter CAN-ID's? Log attached
I have a bunch. I will try to post them up later tonight.
Definately not stock. FP Red and I beefed up the timing quite a bit from stock as am hitting different load sites. ECU never pulls timing but then again I am being cautious at only 22 PSI for now. Will be turning boost up another lb or two soon. Just have to do many logs to make sure it is safe and haven't had time to do that.
OK so I'm going to go and try to get boost and load logging working. Or at least get some time in on figuring them out. I wish I did this for a living or could take vacation right now to figure it out...
Well I figured out another value instead. Knock count 
I have my "Knock Retard" value set to CAN11-1 and it is definitely what I am used to seeing for "Knock Sum/Count." It's definitely not degrees of timing, seems like 1 degree timing per 3 "degrees" of this value.
Anyway, I also found that CAN7-0 is indeed accurate for Timing Advance.
Timing Advance: CAN7-0
Knock Sum/Retard: CAN11-1
I'll be working on MAP now cause I didn't even bother.

I have my "Knock Retard" value set to CAN11-1 and it is definitely what I am used to seeing for "Knock Sum/Count." It's definitely not degrees of timing, seems like 1 degree timing per 3 "degrees" of this value.
Anyway, I also found that CAN7-0 is indeed accurate for Timing Advance.
Timing Advance: CAN7-0
Knock Sum/Retard: CAN11-1
I'll be working on MAP now cause I didn't even bother.
One additional bit of info. I don't see how we can be logging actual load without combining two CAN return values. Since they are bytes, they have a range of 0-255 for integer values. Hence why we are seeing a maximum reported load of 255. There must be a 2nd value for load that can be added to the first to get "actual" load. Maybe it is CAN20-1 + CAN20-2. I'll try it later.
Nice going gurus!
Would it be a good idea to summarize the discovered can-settings so far so that
mortals like me can try logging as well since I have the Evoscan SW and
an openport 2.0 cable.
I do not know if my logging would help but it would be interesting anyway...
I am reading up on tuning so I hope to be able to help eventually...
/L-O
Would it be a good idea to summarize the discovered can-settings so far so that
mortals like me can try logging as well since I have the Evoscan SW and
an openport 2.0 cable.
I do not know if my logging would help but it would be interesting anyway...
I am reading up on tuning so I hope to be able to help eventually...
/L-O
yw.
The knock count/retard one I posted is definitely spot on. I tested it on another X today and I was able to identify the dealer filled the poor car with 85 or 87 before it left the lot... 13 counts stock! Pretty ridiculous. Even after reflashing the car was still dumping fuel and pulling timing due to the detected knock.
The knock count/retard one I posted is definitely spot on. I tested it on another X today and I was able to identify the dealer filled the poor car with 85 or 87 before it left the lot... 13 counts stock! Pretty ridiculous. Even after reflashing the car was still dumping fuel and pulling timing due to the detected knock.
yw.
The knock count/retard one I posted is definitely spot on. I tested it on another X today and I was able to identify the dealer filled the poor car with 85 or 87 before it left the lot... 13 counts stock! Pretty ridiculous. Even after reflashing the car was still dumping fuel and pulling timing due to the detected knock.
The knock count/retard one I posted is definitely spot on. I tested it on another X today and I was able to identify the dealer filled the poor car with 85 or 87 before it left the lot... 13 counts stock! Pretty ridiculous. Even after reflashing the car was still dumping fuel and pulling timing due to the detected knock.
EvoScan is telling me 64/sec so I guess 8/sec if I'm logging 8 items? That's about what I see in my logs. 6-8 per second. Not great, but it works I guess.


