EvoScan 2.5 issue...
Thread Starter
Evolving Member
iTrader: (7)
Joined: Dec 2005
Posts: 240
Likes: 0
From: Jeanette near Pittsburgh
EvoScan 2.5 issue...
Recently my tech switched my car from my 9642008 rom over to a 94170014 rom.
As a result my immobilizer was messed up(fixed for now). And my old version of Evoscan .99 (i think) stopped being able to log 2-byte Load...in fact it logged it giving me figures like 2447.234
As such, I figured i needed to upgrade my Evoscan hoping to remove the bug in the system.
Now that I have updated, Evoscan will initialize, connect, and then disconnect saying " Cannot Open COM1, file not found"
I havent been able to track down the issue, and was hoping people could help me out. I am fine using the new 94170014 rom, but i need to be able to see 2-byte load for obvious reasons.
Thanks
As a result my immobilizer was messed up(fixed for now). And my old version of Evoscan .99 (i think) stopped being able to log 2-byte Load...in fact it logged it giving me figures like 2447.234
As such, I figured i needed to upgrade my Evoscan hoping to remove the bug in the system.
Now that I have updated, Evoscan will initialize, connect, and then disconnect saying " Cannot Open COM1, file not found"
I havent been able to track down the issue, and was hoping people could help me out. I am fine using the new 94170014 rom, but i need to be able to see 2-byte load for obvious reasons.
Thanks
Sounds like you might have it configured to read from an external wideband, but the external wideband isn't hooked up? Try unchecking the "External Wideband O2" logging option.
As for 2-byte load: you need to make a change to the ROM to support the logging of multi-byte load; specifically, you need to change the MUT table to support it. There's some very rudimentary instructions relating to this on the wiki. Also, most folks have moved past using two-byte load logging, because it has a tendency to produce erratic results; if you can convert from 94170014 to 94170015, there's a "tephra" ROM that provides "1-byte load" that doesn't max out at a ridiculously low number.
As for the immobilizer, we also have a wiki page for that; it's a page about 96530006, but the same procedure applies for other versions as well.
All that being said: if you have a "tech" who is doing this stuff for you, you should probably be talking with them about this, and what your expectations were for a switch to a new ROM ID. If you're relying on them for your tuning and other ECU work, you'll want to make sure they're aware of the changes you're making, as it will effect their work later.
As for 2-byte load: you need to make a change to the ROM to support the logging of multi-byte load; specifically, you need to change the MUT table to support it. There's some very rudimentary instructions relating to this on the wiki. Also, most folks have moved past using two-byte load logging, because it has a tendency to produce erratic results; if you can convert from 94170014 to 94170015, there's a "tephra" ROM that provides "1-byte load" that doesn't max out at a ridiculously low number.
As for the immobilizer, we also have a wiki page for that; it's a page about 96530006, but the same procedure applies for other versions as well.
All that being said: if you have a "tech" who is doing this stuff for you, you should probably be talking with them about this, and what your expectations were for a switch to a new ROM ID. If you're relying on them for your tuning and other ECU work, you'll want to make sure they're aware of the changes you're making, as it will effect their work later.
Last edited by logic; May 29, 2009 at 01:31 PM.



