I'm too much of a newb for that, I had blackstealth make me the latencies for 680cc injectors and most of the file.Quote:
Originally Posted by Goallie11
Printable View
I'm too much of a newb for that, I had blackstealth make me the latencies for 680cc injectors and most of the file.Quote:
Originally Posted by Goallie11
If anyone is having trouble getting Evoscan 2.9 to recognize the definition file, it needs to be placed here: \Users\YourUsername\Documents\EvoScan\DataSettings
2.9 doesn't have a folder for data settings in it's main folder that gets created from installation for some reason.
hi guys,was hoping someone could help me out with a couple questions I have,reflashed my control unit and went in and set my injector scaling and latency numbers but when i tryed to set my periphery bit numbers like aaronatstate i couldnt change the 0 and ones around like i did the others by clicking the the number clicking edit the (set) then enter,not sure what im doing wrong,the other guestion i had was when you go into the rom and change your scaling or any thing or numbers is that like real time or do you reflash every time you make changes,not sure if i said that right,went thru the thread a couple times and the videos but didnt see the answers,any help wpuld be great. Thanks
Could try to click on the cell and use the + and - keys. And every change needs a reflash.
Can anyone confirm if evoscan 2.6 can be used on a 95 car ? Seems I tried every setting and I get no results codes stored...
I'm using 2.6 on my 95...no problems here. Whats your issue?
You need to have evoscan on the ODBII setting if you're using 2.6.
In this picture on the upper left select ODBII. There are also all the id's, which you can add if you right click any of them.Attachment 4475
can you tell me exactly what settings you are using? I'm using openport1.3-->obdII96+ and when I hit display codes I don't get anything even the speed sensor code that I know for sure I have..Quote:
Originally Posted by NOMIEZVR4
BTW I can't select openport 2.0, it gives me a communication error.
You need to use 2.0. It won't communicate with 1.3 selected unless you have a 1.3 cable (which you shouldn't have).Quote:
Originally Posted by vr4whore
Sounds like you need to reinstall your 2.0 drivers.
There shouldn't be any reason you need to have OBD2 selected. If its not retrieving codes, try starting and stoping a data log (which was mentioned a few posts ago). Not sure why this works but it usually does.Quote:
Originally Posted by Goallie11