Camp Lejeune/Jacksonville Evos
Evolving Member
Joined: Jan 2010
Posts: 208
Likes: 0
From: NC
Evolved Member
iTrader: (16)
Joined: Jan 2007
Posts: 691
Likes: 0
From: Fayetteville, NC via Puerto Rico
Holy sh*t..i'm about totally fed up. I just connected to the car 2 hours ago. Now, I update the xml file in evoscan and change 1 thing in my ROM, and now I can't connect to the car. I already searched a possible driver issue, but someone suggested that changing the xml could have affected it. I know the xml worked bc it opened a bunch of other items in my item list within ecuflash so I don't think I screwed that up. Ben, where is that ditch you were eyeing a while back?
Evolving Member
Joined: Jan 2010
Posts: 208
Likes: 0
From: NC
Evolved Member
iTrader: (37)
Joined: Sep 2003
Posts: 3,146
Likes: 2
From: Spec-Ops Motorsports, Fayetteville, NC
+1
Change that D to a B and eye some of that
Bob, advice....
Start over. Completely uninstall evoscan, d/l and install the latest version.
Completely uninstall ecuflash, install the latest version. Either d/l or copy the ecuflash xml files from here or ben and load those in the appropriate folder. Open your rom and all should be well.
Change that D to a B and eye some of that
Bob, advice....
Start over. Completely uninstall evoscan, d/l and install the latest version.
Completely uninstall ecuflash, install the latest version. Either d/l or copy the ecuflash xml files from here or ben and load those in the appropriate folder. Open your rom and all should be well.
Thanks for your help and patience. I was so frustrated yesterday. I'm totally better today! lol
I uninstalled ecuflash and reinstalled. All drivers loaded successfully, I plugged in my cable and it loaded ok. I'm headed to the garage to test it out now..fingers crossed.
I uninstalled ecuflash and reinstalled. All drivers loaded successfully, I plugged in my cable and it loaded ok. I'm headed to the garage to test it out now..fingers crossed.
OK. Well that narrowed down maybe 50% of a problem. It still won't connect with ecuflash, however evoscan connects and logs perfectly fine. So, I guess that tells me the cable and drivers for it are fine. Here's the message it gives me. I don't ever remember all the zero's following my cable's serial #. Is that a problem?
[17:16:47.121] Using interface OpenPort 1.3 Mitsubishi TX14qc0X388f6900000000000000000000000000000000
[17:16:47.121] interface close
[17:16:47.137] unable to connect to vehicle interface.
[17:16:47.121] Using interface OpenPort 1.3 Mitsubishi TX14qc0X388f6900000000000000000000000000000000
[17:16:47.121] interface close
[17:16:47.137] unable to connect to vehicle interface.
I did ANOTHER full uninstall of every f-ing thing I can find that's associated with ecuflash. FTDI crap, tactrix stuff..everything. Did a restart and downloaded 1.42 AGAIN. Now, when I plug in the 1.3m tactrix cable it looks for a driver, then fails. I prompt it to look in the ecuflash folder where the drivers are and it locates 1 but gives me an error saying "driver not intended for this platform"
Sound like a bug with 1.42 download? All 3 drivers said they loaded OK when ecuflash installed..so now what. I don't have the patience for this.
Sound like a bug with 1.42 download? All 3 drivers said they loaded OK when ecuflash installed..so now what. I don't have the patience for this.
Yeah, I thought I was going to outsmart it by switching over to my XP partition, and launching 1.29. It won't even connect, so I either locked the ecu somehow, or something else is up. I can data log perfectly fine. I did a FULL uninstall of ecuflash and every associated thing..ftdi drivers, openport stuff..everything. Reinstalled and same problem. I know I didn't have this issue prior to flashing a ROM with the v7 tephra stuff so I'm thinking that's the problem.