19BLACKGST98
15+ Year Contributor
- 711
- 3
- Nov 6, 2003
-
McKinney,
Texas
Thanks Ill give it a try. I would rather run windows 98 if I could because the computer seemed a little quicker running it.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
This site may earn a commission from merchant
affiliate links, including eBay, Amazon, and others.
This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Sorry about that it sounded right to me because I already knew the situation. My bad.Oh! your post lead me to believe you were wondering if evoscan will install on a laptop with windows 98SE.
.
Well mine isn't a loading-onto-the-server-problem. I can't find the file after I log it. But I can replay the log. ?
The log files come out CSV (comma separated values). So you can open up the file in notepad, wordpad, or even MSword or other typing program and then copy/paste right on to a post you're creating here. It probably would be good to go through the log and only paste the string that you have a question about. Since CSV can get very long. But I can't open up the file. Or even see it. I can jsut replay it in the logger and graphing utility.
Well mine isn't a loading-onto-the-server-problem. I can't find the file after I log it. But I can replay the log. ?
The log files come out CSV (comma separated values). So you can open up the file in notepad, wordpad, or even MSword or other typing program and then copy/paste right on to a post you're creating here. It probably would be good to go through the log and only paste the string that you have a question about. Since CSV can get very long. But I can't open up the file. Or even see it. I can jsut replay it in the logger and graphing utility.
I did a log last night (on someone elses car thats around 425whp or so) and it seemed a little slow. It could be my computer though, I am currently waiting on more memory I ordered. This was on a 1995 GSX with an eprom ECU. The info wouldnt show up on the screen unless I was recording the data??? anyone know why? Did I have the settings jacked up. I had it on hybrid/3000gt.... and on EFI.
Others have had problems finding log files with Windows Vista. If you are using Vista there is a service pack from Microsoft that is downloadable that should repair the problem.
I had problems finding my logs too, and I could find them after running searches. I did not do the service pack though. Under logging I go into the "Open log file in graph", but right click on the one I want and open it with Microsoft Works Spreadsheet.
Others have had problems finding log files with Windows Vista. If you are using Vista there is a service pack from Microsoft that is downloadable that should repair the problem.
I had problems finding my logs too, and I could find them after running searches. I did not do the service pack though. Under logging I go into the "Open log file in graph", but right click on the one I want and open it with Microsoft Works Spreadsheet.
I've tried exactly what works for you, but it doesn't work. The only thing that works: open up the saved logs folder by clicking 'playback log', delete the file, go to the recycle bin and copy/paste the file the desktop. Then I can open it up. . .
Do you have a link to the service pack?
Here's the log file. Click on 'free user' to down load the file. Remeber, I didn't even have the car running.
Thanks! Yep, I can see the file just fine when I click on 'compatibility files' at the the top of the vista window of the saved datalogs. . .
Ok this is a 1997 model year (aug 1996 production date) Eagle Talon AWD turbo. Interestingly, the log I have shows the tps at 0%, air temp at 77*F when it was about 66*F that day, 66*F coolant temp which should be about right, and MAF air temp scaled is at 172.4*F. . . Which is clearly wrong since the car wasn't even running. . . Target idle is also reported at 1216rpms when the car is stock, so target should be 750ish. Clearly the formulas are wrong. The speed with the car on blocks is 263 mph . Do I have to wait for evoscan updates to get this to read accurately? Does someone have the accurate formulas for the logable variables? Or will I just have to trial and error figure out what the formulas are? Does anyone have a suggestion as to how to insure the knock sum is reading accurately And any suggestions on a procedures to generate or test the forumlas for any of the logables.
The injector scaling is defaulted to 450, which is good.
EDIT:
-I'm a douch. This is a MAFT car, so the 77*F air temp is about right since the MAFT locks the air temp input. However, I thought that it locked it at 80*F though, not 77*F (but that's not too much difference). . .
-Apparently I'm not really supposed to pay much attention to the MAF air temps scaled perameter. . .
-The target rpm COULD be 1200rpms because the coolant temp is reading cold, so the ecu is in cold start mode. Would this make sense?. . .
-The evoscan notes say that the ability to log speed from the ecu is for 98 or newer cars. So this explains the speed sensor issue. So I guess we won't be getting any 70-90 times to log how well certain upgrades are doing .
So does anyone know if the 1997 ecu spits out a correct knock sum with evoscan? Does anyone know if the 1997 calculates knock sum the same as 1998-1999 ecus? If so then, the formula in the evoscan software should be the same, correct?
Evoscan will not display anything unless you are logging. Also if you only log the essential data items it will log faster. In other words the less data items you are logging the more samples you will get up to a point. For example. I currently get 150 samples per second logging only around 8 data items. If I log 20 - 25 I only get somewhere around 60-80. Im using my corperate laptop with a core duo .
Ok, there is one more thought that came to my mind.
As far as we know, there is some sort of lockout problems that doesn't allow the ROM to be erased. That could be caused by booting in incorrect mode as well.
The specification at page 520 says:
Example of User Program Mode Execution Procedure:
...
Activate the CPU with a reset. (Activation from user program mode is possible by applying 12 V to the Vpp pin during the reset, i.e. while the RES pin is low*2.))
...
That means you can only enter programming mode if the +12V are applied to a programming pin or something.
I'm not too good with all the electronic stuff, so can anyone confirm that we do have 12V applied to a programming pin if the white plug is connected?
If we don't have, that might be the problem. The programming code supplied in specification relies on +12V being supplied at bootup as well. If the key has been turned, and there is no +12V, the ECU boots and it's too late to reprogram it.
we will not be able to release a version of EcuFlash for the Mitsubishi H8 processor family of ECUs that works with the Openport 1.3. The reason being that the Openport 1.3 power supply circuit that generates the ~16V the ECU needs to supply the regulated reflashing voltage to the CPU does not have a sufficient current capacity, causing this voltage to drop to levels insufficient to safely flash the CPU (the CPU goes into a protection mode to prevent you from even trying). The Openport 1.3 does generate a voltage large enough to cause the processor to startup in boot mode, which is why you could read and compare in past versions, but unfortunately, it just isn't usable for reflashing. Later processors like the SH2 and M32R generate this reflash voltage internally, and have minimal current requirements, which is why the Openport 1.3 works with the Evo 7/8/9 without a problem.