So basically what this tells me is that when you do get it working for the 95-97 Ecu's it will be just as slow as EVOSCAN? If that is the case I wouldnt even bother with doing all of the work. Evoscan is so slow with my 95 ECU that it is useless for tuning
If you log less items, you will have more resolution per item.
You should get at least 15 samples a second.
Log RPM, AirFlow and KnockSum only and they will update 5 times a sec.
WideBand is logged separate from other items.
RPM, AirFlow, KnockSum and WideBand is all you should need for WOT tuning.
Your only options for a faster sample rate are a ecu swap or a complete ems.
Also if you are using EvoScan to log KnockSum on a 95-97 the RequestId should be 3E not 26.
KnockSums address is different between 95-97 and 98-99.
Address 26 will always read zero on a 95-97.
Advertisement
To browse the forums without the advertisements above, Login/Register
make it compatible to a 1G as well! That would rock!
TMO is really outdated.. and MMCD sux on laptop.
btw. have a 1G so can`t test it, but I need one special thing:
I want to know where in the timing/fuelmap I am!
so simply: just show the timing table/fueltable position where the car is running right now.
that would be badass for tuning via Eprom.
and maybe a "dynoish thing" ... where you can enter car weight and gear ratio... and it will get you hp/tq curve based on the gearratio and weight.
I use EvoScan on my car right now. It's a 97 Eagle Talon Tsi AWD with a 4/97 build date, and I can log ~80 sample per second with it in Mitsubishi mode, not the hybrid mode. That's plenty to tune with. If it works in Mitsubishi mode, it should work with your program? Right?
I'll try to try your software out on my car later.
____________________________
Wes - '97 Talon Tsi AWD
I use EvoScan on my car right now. It's a 97 Eagle Talon Tsi AWD with a 4/97 build date, and I can log ~80 sample per second with it in Mitsubishi mode, not the hybrid mode. That's plenty to tune with. If it works in Mitsubishi mode, it should work with your program? Right?
I'll try to try your software out on my car later.
Do you happen to know your ECU's case Id? MD326328 would be a 97 AWD.
I'm not sure when they switched protocols, and I don't own any 97 ECUs.
I'd be interested to know if it works with your 97.
I have a 98 ecu that can do all three protocols; MUT, Hybrid and OBD2.
Do you happen to know your ECU's case Id? MD326328 would be a 97 AWD.
I'm not sure when they switched protocols, and I don't own any 97 ECUs.
I'd be interested to know if it works with your 97.
I have a 98 ecu that can do all three protocols; MUT, Hybrid and OBD2.
I don't know which case Id I have. I've never had the ECU out to check. If it weren't 19*F out right now, I'd check it for you. But....
I can confirm it works on my late 97 car!
April 1997 Build Date
Openport 1.3U cable from EvoScan, Pin 9 cut for ABS.
Vista 32-bit SP1
It says 60 sample per second in that frame, but I had no problems and connected at ~80 samples per second after about 5 seconds.
Few suggestions: -Lock the size of the form.
I usually do this by setting the form's values of "MaximumSize" and "MinimumSize" to the same value as "Size".
-Have and option to output to a comma or tab separated file.
Then users could open it in Excel to make graphs. I noted you could output to XML, but a normal .txt file would work fine. Just make a data stream that dumps it all (neatly) into a file. Make it so that every time your start a new data log, it makes a new file. Just name it the current time and date. EvoScan does it this way and it's convenient.
-Make an option so the user can enter how often they want the scanner to prompt for each element.
(Ex. I only need the coolant temp every 30 sec or so.) You could approach this 2 ways... Have the user enter a time (in seconds) to wait between reading that element. Thenkeep track how long it's been since each item was pulled, if it's due, poll it. OR Just have the user enter how many loops to wait between polls. Then when that loop comes up, (current loop)mod(#loops to wait) = 0, poll it.
Other than that, nice work. I'm working on my car over spring break (March 8th-14th) and if I get the chance, I'll get the case Id # for you.
I've done VB and C++ with Visual Studio. If you want any help with little segments of code, PM me. I'll be happy to bounce back ideas for you.
I have VB Express Edition 2008 (just downloaded ) and C++ Express Edition 2008. I've better with VB than C++, by leaps and bounds.
PM me about any updates and I'll check them on my car.
____________________________
Wes - '97 Talon Tsi AWD
when are you going to have it working for us 95 eprom guys i need a logger bad..........also would you know what needs to be done to get evoscan v2.5 to connect......... i am running a elm323 cable through a serial convertor !
I am also anxious for you to say you finally got it working for poor "fogotten" us '95 guys. When do you think you will have it working for 95's or is there any hope at all? Screenshots look amazing...
when are you going to have it working for us 95 eprom guys i need a logger bad..........also would you know what needs to be done to get evoscan v2.5 to connect......... i am running a elm323 cable through a serial convertor !
Quote:
Originally Posted by 95Eclipse
I am also anxious for you to say you finally got it working for poor "fogotten" us '95 guys. When do you think you will have it working for 95's or is there any hope at all? Screenshots look amazing...
Quote:
Originally Posted by Apeximprt2nr
+1 for us '95 guys!
I'm working on the 95-96 protocol now. Hope to have it working by the end of the weekend.
I'm making some good progress, when I have free time.
The Hybrid protocol for 95-96 is ugly and unnecessary complicated and has slowed things down a little. The Hybrid protocol is wrapped up inside the OBD2 and Emissions junk. The protocol is what they call "Designed by Committee", they make things complicated so you have to buy their datasheets and manuals.
I could not control the inter-byte and inter-message timing that OBD2/Hybrid is picky about with the .NET VCP driver. So I have completely switched to the FTDI D2XX DLL. This allows a lot more things to be done and should be a little faster. This also allows more than one FTDI cable to be plugged in, with VCP having more than one cable screwed things up.
I also got some info from Innovate Motorsports about their WideBand's protocol. I will probably add support for their WideBands in the future.
Also I have found a source for some dirt cheap cables, but I want to test them out a little more.
Progress Report:
Transitioning program from Virtual Com Port to FTDI Driver.
97-99 DSM is done.
95-96 DSM Init Sequence is done, as well as some simple requests.
I have about 8 to 10 hours of work before my next release which will support 95-99 DSMs.
I would like to add support for 1Gs, if anyone has a ECU and harness plugs they would like to donate it would help out a lot.
Also IRL today, I stripped three exhaust manifold studs. If anyone in the Reading, PA area wants to help a brother out, and has a right-angle drill I could borrow for a day, that would be awesome.
I have completely switched to the FTDI D2XX DLL. This allows a lot more things to be done and should be a little faster. This also allows more than one FTDI cable to be plugged in, with VCP having more than one cable screwed things up.
So we can use the VAG KKL FTDI cables that are easily found for like 15 bucks? They are said to work with programs such as Evoscan & Mitsulogger.
Do you mean you could log to two separate programs or PC's at the same time just by having a Y adapter to plug two cables into the diagnostic port at the same time? That would be nice for having a screen in the car that shows some data, kind of like the screen on myrollingroad.com, and still log to your PC at the same time.
So we can use the VAG KKL FTDI cables that are easily found for like 15 bucks? They are said to work with programs such as Evoscan & Mitsulogger.
The cable I got was: USB Cable KKL 409.1 VW/AUDI OBD2 OBD OBDII VAG COM 409
Works perfect so far. Don't know how the chinese do it, the parts alone cost more than 30 bucks.
Quote:
Do you mean you could log to two separate programs or PC's at the same time just by having a Y adapter to plug two cables into the diagnostic port at the same time? That would be nice for having a screen in the car that shows some data, kind of like the screen on myrollingroad.com, and still log to your PC at the same time.
Some new laptops don't have serial ports. So if you had a USB Diagnostics cable and a USB to Serial converter to hook up your WideBand there would be driver conflicts.
I think the ECU would get mixed up if two loggers where talking to it at the same tome.
I noted you could output to XML, but a normal .txt file would work fine. Just make a data stream that dumps it all (neatly) into a file. Make it so that every time your start a new data log, it makes a new file. Just name it the current time and date. EvoScan does it this way and it's convenient.
