Evo scan problem after ecu flash update
#1
Newbie
Thread Starter
Join Date: Apr 2009
Location: Texas
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
#2
Evolved Member
EvoScan must use EcuFlash XMLs for its map-tracing functions... and it doesn't like something in those XMLs.
If you're not actively using those particular ROM ID XMLs, maybe rename them to ".xml_old" or something.
If you are using them, then you could try fixing up the XML definitions - to fix those errors. XML is a very tight spec, but some parsers are slack. I reckon EvoScan's parser dislikes something in the "new" EcuFlash's XML fileset.
Rich
If you're not actively using those particular ROM ID XMLs, maybe rename them to ".xml_old" or something.
If you are using them, then you could try fixing up the XML definitions - to fix those errors. XML is a very tight spec, but some parsers are slack. I reckon EvoScan's parser dislikes something in the "new" EcuFlash's XML fileset.
Rich
#3
Evolving Member
In addition to what Richard has mentioned, EvoScan will also parse all other XML files and if it finds an error in any of them, (even though it's relating to other ECU ID) it may not work properly.
Here's what you can do, created a new folder and place ONLY the ECU ROM file and it's corresponding XML definition file in it and it should open up in EvoScan Map Tracing screen without any problems.
Here's what you can do, created a new folder and place ONLY the ECU ROM file and it's corresponding XML definition file in it and it should open up in EvoScan Map Tracing screen without any problems.
Thread
Thread Starter
Forum
Replies
Last Post
4b11slayer
ECU Flash
2
Nov 5, 2016 11:11 AM