Evo Scan Issue

[marcman804]

I have been trying to install Evo scan 2.5 to be able to log on my 95 ecu but I keep getting error messages after I install and run the program. Here is a screen shot of the errors Im getting. Any help would be much appreciated, Im trying to get my car ready for the shootout and the only thing I have left is to get the tps set and I plan on doing it with evoscan. Thanks

 

[marcman804]

I got rid of those messages, I just had to get the correct serial for version 2.5 but now I am receiving another message when I try to log. Whenever I try to log I get an error in the "Event Log" that says... "Error: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) Info: Datalogger Ended. Ive attached a screenshot as well. Thanks for any help.

 

[rts91tsi]

Which operating system are you running on your laptop? I know that with version 2.5, if you are running Windows 7 that you have to be logged in as administrator in order to run the program.

My old PC was running Vista as an OS, and I had to run it as administrator too.

If trying what I suggested doesn't work, then you may want to submit a ticket for tech support.

 

[marcman804]

Im using Windows 7 and I tried running it as administrator and the program will load but when I try to log my car it gives me the error message about incorrect format. I wonder if this has something to do with running a 64bit computer versus a 32bit.

 

[Tiki2777]

Are you using the correct setting for your cable and the right ecu setting? I know 98-99 ecus use MUTIII, but not sure about 95 (probably the DSM/3kgt one).

 

[PieEyedPiper]

Not a 64bit issue.

Honestly, I'd try EvoScan 2.7. It appears to be the latest version that still works. i.e. can pull dtc's.

 

[Tiki2777]

Not a 64bit issue.

Honestly, I'd try EvoScan 2.7. It appears to be the latest version that still works. i.e. can pull dtc's.

That too, i'm not sure why you'd want 2.5 for any reason, i get only using 2.7 over 2.9 for some reasons (which i still think is dumb) but yea i would try that too.

 

[H@xtGSX]

I had a lot of trouble getting Evoscan to log anything off the '96 ecu I was using just prior to installing the '98 ecu I have now. The baud rate had to be at the lowest speed I could get it to. The DSM connection never worked, I had to use the OBD2 option, and even then the thing logged so slow that it was not really worth the effort. Honestly, if you want to use Evoscan as it is intended, I'd recommend switching out your ecu. The SH2 chipset ecu's are the only ones I have seen so far that completely work with Evoscan. Even the H8 ecu's have a few issues with it, depending on the version. I run the H8 with 2.7 and it seems to work well enough, but now that I have seen the difference between it and an SH2 ecu, I'll be switching to the SH2 as soon as I can... They have a 100x more support from the Evo guys.

 

[marcman804]

Im just using it right now to get my tps set up correctly and I was told that I would have to use v2.5 in order to do that. I do have a 99 ecu but Im not able to get a tune on it right now so Im just using the 95 ecu with the dsmchip tune. I have tried to use v2.7 but I always get the message there is not enough volts or whatever it says in regards to the 5v that the cable needs.

 

[Tiki2777]

Im just using it right now to get my tps set up correctly and I was told that I would have to use v2.5 in order to do that. I do have a 99 ecu but Im not able to get a tune on it right now so Im just using the 95 ecu with the dsmchip tune. I have tried to use v2.7 but I always get the message there is not enough volts or whatever it says in regards to the 5v that the cable needs.

Are you still using the 2.0 cable to log? I have the same problem, and its just the fragility of the cable and brittle/poor design. You have to "jiggle" the mini usb connection to the OBDII 2.0 main plug. That's where the connection gets loose, and other than flashing which it is needed for, the cable is almost impossible/useless to use for logging while moving unless you have a great shock setup . It always gets knocked loose .

Now, I got my 1.3 VAGCOM cable off of ebay and it works great for logging.

And for Frank (toothless), why didn't you use 2.9? It works great on the H8 for me.

 

[marcman804]

Oh ok because when I played around with the 99 ecu and I got it to reflash with ecuflash but I was using evoscan 2.9 and it logged nothing whatsoever, so I tried to go to v2.7 and it hasnt worked since so I went back to the 95 eprom ecu. For just logging with the OpenPort 2.0 do I need to use the stereo headphone jack or is that for just reflashing?

 

[H@xtGSX]

Did you add the stereo jack plug to pin 79? That's where the 5v message comes from, I think... It supplies the flash voltage for the H8's anyhow. I'm not sure why you'd need it for the older ecus, other than maybe to keep the software happy.

Are you still using the 2.0 cable to log? I have the same problem, and its just the fragility of the cable and brittle/poor design. You have to "jiggle" the mini usb connection to the OBDII 2.0 main plug. That's where the connection gets loose, and other than flashing which it is needed for, the cable is almost impossible/useless to use for logging while moving unless you have a great shock setup . It always gets knocked loose .

Now, I got my 1.3 VAGCOM cable off of ebay and it works great for logging.

And for Frank (toothless), why didn't you use 2.9? It works great on the H8 for me.

I couldn't get 2.9 to pull DTC's and the live map stuff didn't work at all for me. I am still figuring it out though, but 2.7 has worked without any complications so far. I'm using it now to get my speed density maps filled in for the switch over to that.

Side note: Do you guys use the 2.0 SD memory card logger on the Tactrix module? I've been using it, and it is really nice not having to have the laptop in the car if your just logging.

 

[Tiki2777]

Did you add the stereo jack plug to pin 79? That's where the 5v message comes from, I think... It supplies the flash voltage for the H8's anyhow. I'm not sure why you'd need it for the older ecus, other than maybe to keep the software happy.



I couldn't get 2.9 to pull DTC's and the live map stuff didn't work at all for me. I am still figuring it out though, but 2.7 has worked without any complications so far. I'm using it now to get my speed density maps filled in for the switch over to that.

Side note: Do you guys use the 2.0 SD memory card logger on the Tactrix module? I've been using it, and it is really nice not having to have the laptop in the car if your just logging.

No, i have not tried the SD standalone yet, need to get an SD card first . At first i was like WTF with maptracer because it did not work for me either, but then i played with it for a while and figured out how to make it work. You have to right click it and load ROM HEX from one of the ceddy roms instead of the evo7 one it uses stock... SO, if you want that (and it is pretty sick) i would help you with that. For DTC's, i just have had ZERO luck with evoscan, illl have to try 2.7 for that becaus ei havent tried that yet.


I just wished evoscan would patch a fix to get the SD tables into maptracer, then it would be like one log and boom you have SD, because you can directly edit a rom in maptracer and make changes and save it.

 

[H@xtGSX]

That's why we need to get Evo 8 (or equivalent) ecus... I saw one on an Evo 8 here a week ago. It is so much easier to work with the SH2 ecu, and modifying it is even easier. They can change stuff on the fly. The SH2 makes our H8 ecu's look rather primitive. Since the only mod to use one is switching around a few wires, there is no reason to not move on to one eventually. I'll be using the Ceddymod speed density for a while, but when I have some extra cash around, you can bet I'll be selling my H8 and installing an SH2 immediately.

I read on EvolutionM that the '01 '02 Mirage LS ecu is the same as the Evo ecu without the immobilizer. Much cheaper too. $100 vs $250-$300 for the Evo with the immobilizer enabled. I don't need that immobilizer stuff hassle anyway.

 

[Tiki2777]

That's why we need to get Evo 8 (or equivalent) ecus... I saw one on an Evo 8 here a week ago. It is so much easier to work with the SH2 ecu, and modifying it is even easier. They can change stuff on the fly. The SH2 makes our H8 ecu's look rather primitive. Since the only mod to use one is switching around a few wires, there is no reason to not move on to one eventually. I'll be using the Ceddymod speed density for a while, but when I have some extra cash around, you can bet I'll be selling my H8 and installing an SH2 immediately.

Good luck with SD on the evo8 ecu though, because their system is not easy to get good values for their VE tables. I would rather stick with Ceddy's stuff, for some reason i feel its just wrong to go from and H8 to evo8 ecu because of all the work he's put in. The only thing they have we don't is boost control, and we do "technically" have it because he put a guide about it on his website. (just not finished yet or tested)...

 

[H@xtGSX]

Ceddy's SD set up is smarter than the 2D SD the Evo's have been using, BUT they have people who have used the same concept as Ceddy and made the SD conversion basically the same as his... Personally, I am not too purist about it as long as it works well and is easy to use. The SH2 has the H8 beat in that aspect.

Plus, being that we paid for the software shows we respected his work. He moved on too, so I don't think the switch would imply any disloyalty.

 

[marcman804]

Yeah I did have the jck plug into pin 79. I dont think its very secure so I may just remove it and try it again. Is this needed just to log or is it used for flashing purposes?

Did you add the stereo jack plug to pin 79? That's where the 5v message comes from, I think... It supplies the flash voltage for the H8's anyhow. I'm not sure why you'd need it for the older ecus, other than maybe to keep the software happy.



I couldn't get 2.9 to pull DTC's and the live map stuff didn't work at all for me. I am still figuring it out though, but 2.7 has worked without any complications so far. I'm using it now to get my speed density maps filled in for the switch over to that.

Side note: Do you guys use the 2.0 SD memory card logger on the Tactrix module? I've been using it, and it is really nice not having to have the laptop in the car if your just logging.

 

[H@xtGSX]

That jack is there to supply the H8 ecu's with the necessary voltage to flash the memory. I noticed that without it plugged in though, Evoscan wouldn't read anything off the OBD port. You shouldn't need it for anything on an older ecu, but the software may be looking for some sort of signal from it to read... I'm not sure how that works. I do know if I unplug it from the Tactrix module while Evoscan is on, it'll stop logging anything.

 

[marcman804]

Ok well Im going to try to reconnect it to pin 79 and see if that solves the problem. So far evoscan and ecuflash has been a PITA!!!!

 

[H@xtGSX]

It gets better, but it is a huge PITA when you are learning it. Once you've got it figured out, it's actually pretty nice. We DSM people are the red headed step child of the Evo folks though when it comes to our ECU software. I think Link looks and works well, but it is old and I want to try stay somewhat up to date, and hopefully learn useful stuff in the process. Evoscan and ECU Flash tuning is a crash course with a steep learning curve and not much support on the DSM side. It is faster though, and has a lot of features. I believe it to be at least as functional as Link is though.... And to prove it, I sold the 95 EPROM ECU from my car to get a flash ECU.

 

[marcman804]

I totally agree that it is great because the little while I was actually able to play around with ecuflash I found some great features. Some things that I have not even seen in Link. I just wish I could get everything situated and have it reliable instead of being able to use it one day and then it does nothing the next day.

It gets better, but it is a huge PITA when you are learning it. Once you've got it figured out, it's actually pretty nice. We DSM people are the red headed step child of the Evo folks though when it comes to our ECU software. I think Link looks and works well, but it is old and I want to try stay somewhat up to date, and hopefully learn useful stuff in the process. Evoscan and ECU Flash tuning is a crash course with a steep learning curve and not much support on the DSM side. It is faster though, and has a lot of features. I believe it to be at least as functional as Link is though.... And to prove it, I sold the 95 EPROM ECU from my car to get a flash ECU.