So, bit the bullet and ordered a VR4 Clone ECU and 1G adapter harness, and a Tactrix OpenPort 2.0 thingamabob. Which version of EVOScan will work? The site lists the newest V2.9.0020, but the first page of this thread says only V2.6 will work.
Printable View
So, bit the bullet and ordered a VR4 Clone ECU and 1G adapter harness, and a Tactrix OpenPort 2.0 thingamabob. Which version of EVOScan will work? The site lists the newest V2.9.0020, but the first page of this thread says only V2.6 will work.
2.6 is what you will want to use for the time being. 2.9 is being worked on as far as I know.Quote:
Originally Posted by Stealth_RT
I completed version 2.9 conversion greg just testing it now
Are there any noticeable differences between 2.6?Quote:
Originally Posted by 99 vr4
Yeah... You can NOT check or clear DTCs.... LolQuote:
Originally Posted by Toni
Besides that version 2.9 is actually easier to integrate. the older versions used xml files which were shared for the different types of vehicles. this requires you to delete the old file before copying in a new file. the new version is a separate xml file for each vehicle. so I was able to create a separate EFI 3000 gt xml file.
That being said I think most of the code changes were in the way version 2.9 handles the external files. overall look and feel is the same. version 2.9 did add some new features. there is sposed to be real time graphing and logging but I have not played with that yet
I have never had an issue with this using 2.6.Quote:
Originally Posted by 99 vr4
I have been using 2.7 prior and did not have a problem with that...
I got a CEL yesterday, didn't notice when it came on. It said something along the lines of 'excessive time to enter closed loop fuel control' or something. What can cause this? Car has been driving fine outside of running rich on startup until some unexplained event happens, and then it likes to idle normal and hit stoich at cruise and idle around 16.2 which feels like the sweet spot on e85.
On startup the wideband pegs around 10-10.3 and will stay in the 10's and 11's even while cruising around 25-3000rpm. And then I increase load and build a couple pounds of boost and let off and then it's like she finds stoich just fine. Is that right there the ecu stuck in close loop?
I'm running a 3.5'' gm maf with MafT in blow through for those who don't know. Am I gonna have to do some tweaking with the maf tables?
The CEL means what it says. Don't care about the wideband. It's only useful for fine tuning WOT. What are your Narrowbands doing?
Silly question (but one I could not search for since search term "GM" is too short for the search engine to like): does Chrome 1.1 support using a GM MAP sensor rather than the EVO MDP sensor?
I don't intend to use ECU boost control, but if I am reading the feature list correctly, v1.1 uses the MDP reading to control the stock boost gauge, which I am using for the moment.
I intend to use a GM MAP in my build, not the EVO sensor. This signal will feed my ext boost controller and the ECU for logging purposes, via the MDP wire.
Please let me know if I am overlooking anything regarding the MDP/MAP sensor's importance when using the v1.1 Chrome rom.
Thanks!