Howto: EvoScan v2.3 reduced diagnostic light flashing
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
I have been trying hard to get daisy chain innovate device support working, but firstly I have trouble with mts.dll not always correctly connecting to the innovate device, which I think is what causes the innovate connection issues people see, I think its not bad ground connections, I think it was just the innovate mts.dll software itself causing problems. And for me to program the daisy chain serial protocol manually myself requires more work, I'll take a look at it after this release. So it looks like it wont make v2.3, but I already spent ~180hrs trying to make it work. for one feature, it was starting to get a little ridiculous. I'll come back to it.
If I am not interested in AYC (my Evo is an 04) nor the ABS ECU. Can I still use the Universal Tactrix Cable as it is (without cutting any pins) for general data logging including the external wideband with the new Ver 2.3?
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
Yes you can still use the cable as is, but if you get an ABS dash light, you're going to want to know pretty fast what the hell that light has come on for, lol.
Evoscan v2.2 was not really released, but is available to only new downloads, this is because I added mutithreading support and removed wideband support. V2.3 has new improved wideband support, including all versions of innovate widebands using a direct serial comport, none of the silly mts.dll sdk stuff, which would only cause installation issues, I communicated directly with the innovate widebands. and i have also discovered how to calibrate the innovate wideband from evoscan, which i will include in a future version.
I have now figured out how to do all the actuators for EFI, ABS, and AYC mitsubishi computers, and also included all the diagnostic codes for EFI(both MUT DTCs and OBDII DTCs ) ABS DTCs and AYC DTCs into EvoScan v2.3. i.e you can now bleed your own AYC.
the EvoScan 16pin reprogramming cables support these MUT protocols: EFI, ABS and AYC. these Subaru Protocols: SSMII, and these generic protocols: USA Mandated OBDII.
Obviously Evo7/8/9 EFI ecus have both the MUT and slower USA Mandated OBDII protocols, and the OBDII protocol has the best DTC code information and is what is displayed via the check engine light.
A few interesting things is that Evo7/8/9 don't need to be put into flash diagnostic mode to successfully datalog. so the evoscan cables have been designed to support 1994-1999 mitsubishis that do need diagnostic pin1 flashing mode for datalogging. if you have a pre jan2008 evoscan cable and an evo7/8/9 and only want efi logging, disconnect your pin1. Evoscan cables has now connected pin1 to a transistor to electronically enable disable pin1 where needed, also a new option has been added to evoscan to enable this. pin1 is also used for connecting to AYC and ABS ecus, so those with a tactrix cable will not be able to connect to them. Also some evoscan cables have pin 9 and pin 3, mostly for subaru support. Both of these pins interfere with the correct operation of EvoScan AYC and ABS connections and they cause the dashboard lights to flash all the time. So i would highly recommend to break off pins 3 and 9 from your evoscan cable, or disconnect the wires from the car side. AYC and ABS computers on all mitsubishi vehicles require the ABS/AYC lights to always flash when datalogging, there is no way around this. (short of disconnecting or putting in a switch on the led light, hehe) Actually an interesting point to note, is that when you connect to the AYC computer, the AYC diagnostic light stops flashing, but the ABS continues to flash. and vice versa, i.e. when you connect to the ABs computer, the ABS diagnostic light stops flashing and the AYC continues to flash.
I will be releasing a Beta version of V2.3 tomorrow, so I would like any feedback I can get to make it better, and to ensure there is zero bugs when logging. I have had a number of issues with Subaru SSMI and SSMII logging, so I will be doing a new round of subaru beta testing on this Monday to rid of all these issues, mostly around supporting all the different ecu_ids. if you have a subaru and want to beta test this for us, send me a support call or pm.
EvoScan V2.3 has a number of enhancements for Map Tracer, background image support for gauges, and thousands more enhancements that I'm sure you'll like.
EvoScan V2.3 now reaches 60,000 lines of code... thanks to all those involved so far, this has certainly been a successful project to date. and much more to come.
I have now figured out how to do all the actuators for EFI, ABS, and AYC mitsubishi computers, and also included all the diagnostic codes for EFI(both MUT DTCs and OBDII DTCs ) ABS DTCs and AYC DTCs into EvoScan v2.3. i.e you can now bleed your own AYC.
the EvoScan 16pin reprogramming cables support these MUT protocols: EFI, ABS and AYC. these Subaru Protocols: SSMII, and these generic protocols: USA Mandated OBDII.
Obviously Evo7/8/9 EFI ecus have both the MUT and slower USA Mandated OBDII protocols, and the OBDII protocol has the best DTC code information and is what is displayed via the check engine light.
A few interesting things is that Evo7/8/9 don't need to be put into flash diagnostic mode to successfully datalog. so the evoscan cables have been designed to support 1994-1999 mitsubishis that do need diagnostic pin1 flashing mode for datalogging. if you have a pre jan2008 evoscan cable and an evo7/8/9 and only want efi logging, disconnect your pin1. Evoscan cables has now connected pin1 to a transistor to electronically enable disable pin1 where needed, also a new option has been added to evoscan to enable this. pin1 is also used for connecting to AYC and ABS ecus, so those with a tactrix cable will not be able to connect to them. Also some evoscan cables have pin 9 and pin 3, mostly for subaru support. Both of these pins interfere with the correct operation of EvoScan AYC and ABS connections and they cause the dashboard lights to flash all the time. So i would highly recommend to break off pins 3 and 9 from your evoscan cable, or disconnect the wires from the car side. AYC and ABS computers on all mitsubishi vehicles require the ABS/AYC lights to always flash when datalogging, there is no way around this. (short of disconnecting or putting in a switch on the led light, hehe) Actually an interesting point to note, is that when you connect to the AYC computer, the AYC diagnostic light stops flashing, but the ABS continues to flash. and vice versa, i.e. when you connect to the ABs computer, the ABS diagnostic light stops flashing and the AYC continues to flash.
I will be releasing a Beta version of V2.3 tomorrow, so I would like any feedback I can get to make it better, and to ensure there is zero bugs when logging. I have had a number of issues with Subaru SSMI and SSMII logging, so I will be doing a new round of subaru beta testing on this Monday to rid of all these issues, mostly around supporting all the different ecu_ids. if you have a subaru and want to beta test this for us, send me a support call or pm.
EvoScan V2.3 has a number of enhancements for Map Tracer, background image support for gauges, and thousands more enhancements that I'm sure you'll like.
EvoScan V2.3 now reaches 60,000 lines of code... thanks to all those involved so far, this has certainly been a successful project to date. and much more to come.
Based on your post... My cable will work to access the ABS and AYC but I will continue to get my diagnostic light flashing when car speed is below 15 mph?
It's ironic the dyno operator questioned why my lights were flashing and I thought it was normal for them to flash with cable plugged in and then turn off when vehicle speed reaches approx. 15mph
Please advise as I do not want to cut pins and lose functionality of my cable.
PS do you offer upgrade or trade up to new transistorized cable?
The light flashing does get annoying and like you said you really can't see if there is a legitimate problem with all that flashing going on
Thanks
I realize it might be normal with Hamish's cable i just want to know If I keep pin1 and cut the other pin will Flashing be minimized and will i still be able to use the ABS ACD functionality in his new version? Thanks for confirming this though
I'm interested in an upgrade if we can figure it out or a trade if anyone else is.
Running a tactrix ordered from them on Mar 18th with pins 4,6,7,9,15,16. I'd buy a transistorized upgrade kit if it was possible and reasonable Hamish.
I definitely would have bought one of yours if I had known when I purchased!
-----
For anyone looking to find a pinout, here is an OBDII cable diagram: hxxp://www.mefi4.com/sc/details.asp?item=obd2cable (copy, replace xx with tt)
Running a tactrix ordered from them on Mar 18th with pins 4,6,7,9,15,16. I'd buy a transistorized upgrade kit if it was possible and reasonable Hamish.
I definitely would have bought one of yours if I had known when I purchased!
-----
For anyone looking to find a pinout, here is an OBDII cable diagram: hxxp://www.mefi4.com/sc/details.asp?item=obd2cable (copy, replace xx with tt)
Last edited by fostytou; Jun 4, 2008 at 06:19 PM.
Thread
Thread Starter
Forum
Replies
Last Post
evoscan
ECU Flash
1338
Aug 16, 2020 04:22 AM
tsitalon1
Evo X Engine Management / Tuning Forums
29
Sep 14, 2010 07:33 PM
evo4mad
ECU Flash
477
Mar 30, 2007 09:03 AM
