EVOSCAN 2.1 Maptracer Problems!
ok so it still didnt work, maybe i'm doing something wrong. I open evoscan v2.5, click the map tracer, its completely blank, i right click the very bottom graph, i load my xml from ecuflash (91470015 pretty sure the first 4 numbers are in the right order) then the window flickers a little bit and its still the window but now it says load .hex or .bin, so i go into my desktop (thats where i saved it to so i could find it) and i load my .hex that i uploaded to my ecu last night, then the window closes and my values show up in the bottom map. i click knock sum, and nothing happens. did i miss anything?
Close evoscan and reopen it. Now just do a stand still log for a few seconds revving the car a few times. Open maptracer and make sure you select that .csv log you just did, do the usual load xml/hex files and see if that helps. Your knock sum should show a bunch of 0's (given that you're not knocking at idle
) but other items should show up though.Hope that helps
the items i'm logging are:
# TPS
# RPM
# TimingAdv
# O2Sensor
# InjPulseWidth
# Battery
# LoadCalc
# KnockSum
# AFRMAP
# Wideband A/F Ratio (need to have an external afr wideband sensor)
# TPS
# RPM
# TimingAdv
# O2Sensor
# InjPulseWidth
# Battery
# LoadCalc
# KnockSum
# AFRMAP
# Wideband A/F Ratio (need to have an external afr wideband sensor)
send me your csv log file. I'll see if it shows in my evoscan map tracer.
przemek2000@gmail.com
przemek2000@gmail.com
its has nothing to do with what you are logging, it should be able to plot anything that it recognizes. I don't know what the issue is but it shouldn't be this difficult.
well... if you won't log for example timing advance then it won't show in map tracer because there will be no log of it :-) same thing for knock sum. so it is kind of important what you log :-)
It has a lot to do with what you're logging (well the order in which you are logging them i should say)
If you are logging items in that exact order then it wont work because loadcalc refers to battery and afrmap in its calculation so having afrmap below loadcalc wont work. Thats why I said put them in the exact order I showed you. Battery, then AFRMAP, then LOADCALC...
likewise you cant log injector duty cycle without having injector pulsewidth being logged before it...
try it and let me know
If you are logging items in that exact order then it wont work because loadcalc refers to battery and afrmap in its calculation so having afrmap below loadcalc wont work. Thats why I said put them in the exact order I showed you. Battery, then AFRMAP, then LOADCALC...
likewise you cant log injector duty cycle without having injector pulsewidth being logged before it...
try it and let me know
It has a lot to do with what you're logging (well the order in which you are logging them i should say)
If you are logging items in that exact order then it wont work because loadcalc refers to battery and afrmap in its calculation so having afrmap below loadcalc wont work. Thats why I said put them in the exact order I showed you. Battery, then AFRMAP, then LOADCALC...
likewise you cant log injector duty cycle without having injector pulsewidth being logged before it...
try it and let me know
If you are logging items in that exact order then it wont work because loadcalc refers to battery and afrmap in its calculation so having afrmap below loadcalc wont work. Thats why I said put them in the exact order I showed you. Battery, then AFRMAP, then LOADCALC...
likewise you cant log injector duty cycle without having injector pulsewidth being logged before it...
try it and let me know
No I didn't mean for it to sound like I was coming down on you, what I mean is the evoscan maptracer is very tricky, from my experience with it you have to have loadcalc selected for it to work, even if you don't use it (whether you use 2byte load or 1 byte load) Apparently the maptracer needs loadcalc.
Not arguing here, just trying to figure it out.
Not arguing here, just trying to figure it out.
No I didn't mean for it to sound like I was coming down on you, what I mean is the evoscan maptracer is very tricky, from my experience with it you have to have loadcalc selected for it to work, even if you don't use it (whether you use 2byte load or 1 byte load) Apparently the maptracer needs loadcalc.
Not arguing here, just trying to figure it out.
Not arguing here, just trying to figure it out.
No I didn't mean for it to sound like I was coming down on you, what I mean is the evoscan maptracer is very tricky, from my experience with it you have to have loadcalc selected for it to work, even if you don't use it (whether you use 2byte load or 1 byte load) Apparently the maptracer needs loadcalc.
Not arguing here, just trying to figure it out.
Not arguing here, just trying to figure it out.
