Are you sure you downloaded the 64-bit versions...? And by they don't work what do you mean...

 

hi. i need some help. dont know what else to do. i have evoscan v2.5 on my laptop w/windows vista. im trying to run the dtc codes, i click on dtc, it connects, but the a get an error: Vehicles ECU not responding, below that it says :ecuID:0000, and then it says dtc's completed.
and the on the dtc's box it says ecuID...i have no idea why

 

i bought EvoScan almost 2 years ago and i've tried getting the updates for it, but when i emailed the vendor, i haven't heard back from them. How do you guys get updates? i don't get any notifications in my email.

 

hi guys just wanna know in ur opinion, before i invest....being a beginner wat is better to start off with but limited to in the future
1) the evoscan ecu management
2) apexi fc power l-jetro

 

evoscan + ecuflash + logging cable is all you need...I have links to everything on my website and even a video tutorial

 

hey! i was wondering if anyone knew what could cause this:

[21:15:48.152] reading ecu programming voltage
[21:15:48.152] programming voltage is 11.84 volts
[21:15:48.152] kernel flash enable
[21:15:48.168] kernel blank flash page: addr: 0002C000
[21:15:48.386] erased in 1 pulse(s)
[21:15:48.386] kernel write flash buffer addr: 0002C000 len: 00000200
[21:15:48.527] kernel write flash buffer addr: 0002C200 len: 00000200
[21:15:48.667] kernel write flash buffer addr: 0002C400 len: 00000200
[21:15:48.823] kernel write flash buffer addr: 0002C600 len: 00000200
[21:15:48.963] kernel write flash buffer addr: 0002C800 len: 00000200
[21:15:49.104] kernel write flash buffer addr: 0002CA00 len: 00000200
[21:15:49.244] kernel write flash buffer addr: 0002CC00 len: 00000200
[21:15:49.385] kernel write flash buffer addr: 0002CE00 len: 00000200
[21:15:49.525] kernel commit flash addr: 0002C000 len: 00001000 crc32 233d4963
[21:15:49.915] written in 1 pulse(s)
[21:15:49.915] kernel write flash buffer addr: 0002D000 len: 00000200
[21:15:50.055] kernel write flash buffer addr: 0002D200 len: 00000200
[21:15:50.196] kernel write flash buffer addr: 0002D400 len: 00000200
[21:15:50.336] kernel write flash buffer addr: 0002D600 len: 00000200
[21:15:50.477] kernel write flash buffer addr: 0002D800 len: 00000200
[21:15:50.617] kernel write flash buffer addr: 0002DA00 len: 00000200
[21:15:50.757] kernel write flash buffer addr: 0002DC00 len: 00000200
[21:15:50.913] kernel write flash buffer addr: 0002DE00 len: 00000200
[21:15:51.054] kernel commit flash addr: 0002D000 len: 00001000 crc32 5bdb4350
[21:15:51.132] kernel error: programming voltage is too high
[21:15:51.147] failed to commit flash at 0002D000!
[21:15:51.147] failure in flashing block
[21:15:51.147] kernel flash disable
[21:15:51.163] interface close
[21:15:51.179] interface close

------------------------

I can download, but fail to upload!

thanks

 

Hello all, we are having a problem with this:

I know this has been asked before and we tried keeping the car running, the unlocker, and the 1.41 of ECUflash. We are using the tatrix 2.0 cable and nothing seems to be working with ECUflash.

EVOscan seems to work fine with no issues, so we know the cable, USB port, all hardware can see the ECU okay, we believe it to be a software issue with ECUflash...

Any ideas? Thanks!

Jack

 

hi chris (mellon tuning)
ur website is so helpful just wished i had ready more forums before buying everything, oh well just a quick ?
a)
1) evoscan - man i paid the for the software throu pay pal and after clicking the submit order the screen returns to items page would der be another site i can download it frm
2) evo flash-downloaded
3) logging cable is ordered

shall email once i`m done installing

b)
before reading these forums i had already ordered apexi fc L-jetro and trust me it take time to understand ,would u hve any sites or how to start tuning frm start
- apexi fc boost contorller
-apexi fc pwer fc L-jetro
-wideband o2 gauge and sensor
-defi link exhaust temp gauge/intake manifold pressure
hve these things wid me but not installed as after reading evo scan i would rather start tweaking the standard ecu

currently on the car installed
-HKS BOV
-HKS cams 268in 278out
-Turbo smart manual Boost controller
-upgraded to 2bar capacity intercooler
-upgrade manifolds - removed the gas anzler pipe which fits the manifolds
-3" TBE complete S/s milteck frm uk
-defi link boost gauge bf series

at the moment car is very rich and idle is haunts now and den!! dont know where to start

 

jack
how did u buy the evo scan software, i paid for it via pay pal as on the website then filled the details den submited the order! after that the site throw me back to items of selling.....

amz

 

how do u guys download evo scan! already paid for it via pay pal!! after submitting screens comes back to items for sell screen!!! ne1 wid this problem!!

 

so how does one get the free updates, anybody?

 

subsribing - having same problem as most people with evoscan not logging properly especially with the map trace. If anyone has any updates on this please let us know.

 

Probably a noob question, but one to fill in some blanks. I have been reading up on the MAF Scaling mods, converting to Hz etc which makes a lot of sense.

My question is, if the MAF sensor is providing air flow volume in Hz to the ECU, why are we tuning with a simulated load and not in Hz. I realise you could change the load axis on the fuel / ignition maps to a MAF Hz value? Is this because the value can only go to 1600Hz and with increased boost, it maxes out the MAF? What about for N/A cars wouldn't tuning in MAF Hz be more accurate and easier to log?

Probably answered many years ago when all this first come out, but someone please educate me.

 

Silly point, but it is really annoying that when you end a log it copies all of the values from whatever the last item being logged was to the rest of the cells. Alot of times this winds up being RPM for me and causing the whole last line to be filled with values > 4000+ and throws off the scales on everything when you try to graph/chart.

I believe this is "new" as of 2.6b11

 

When I log the car with evoscan 2.5, in the DTC box it says "o2 level: 19.9%)

What does this mean?