PDA

View Full Version : Evoscan connectivity issues



LeRoyDL
10-18-2013, 10:41 PM
Hopefully this will help some unlucky soul in the future as well as source community knowledge / suggestions.

The Basics:
91tt bpu,
Brett's ECU
Antero's harness (i assembled)
Wintel/Win7 (6.1.7601 Service Pack 1 Build 7601)
Evoscan (any version)
EcuFlash (1.44.3721)
Tactrix openport 2.0 (firmware 1.12.3688)


The Issues:
1. EcuFlash will communicate (and write) to the ecu but EvoScan version 2.6, 2.7 or 2.9 will not initiate communication.

I receive the following:

Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.12.368
Info: Battery 12.068V
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Timer: 2480.006ms
Info: Initialization Complete...
Info: Waiting for INIT Response...
Error: J2534 Read Error - 16
Info: Datalogger Ended.

EcuFlash on the other hand reads and writes:

174625.530 EcuFlash Version 1.44.3721
174625.530 OS Version Windows 7
174625.530 Qt Version 4.8.0
174625.541 63 memory models read.
174625.541 scanning for metadata models in f/ecu/OpenECU/EcuFlash/rommetadata
174625.684 612 ROM metadata models scanned.
174625.684 checksum module subarudbw loaded.
174625.684 checksum module mitsucan loaded.
174625.684 checksum module mitsuh8 loaded.
174625.684 patch module Subaru CAN Enhanced RAM Parameter Logging loaded.
174625.684 patch module Mitsu CAN RAM Parameter Logging loaded.
174625.686 flashing tool wrx02 loaded.
174625.688 flashing tool wrx04 loaded.
174625.690 flashing tool sti04 loaded.
174625.692 flashing tool sti05 loaded.
174625.692 flashing tool mitsukernel loaded.
174625.692 flashing tool mitsukernelocp loaded.
174625.692 flashing tool mitsubootloader loaded.
174625.692 flashing tool shbootmode loaded.
174625.693 flashing tool shaudmode loaded.
174625.695 flashing tool subarucan loaded.
174625.697 flashing tool subarucand loaded.
174625.699 flashing tool mitsucan loaded.
174625.718 J2534 API Version 04.04
174625.718 J2534 DLL Version 1.00.3721 Jan 9 2013 172459
174625.718 Device Firmware Version 1.12.3688
174625.718 Device Serial Number TA$1ZuBJ
174625.719 interface close
174625.750 J2534 API Version 04.04
174625.750 J2534 DLL Version 1.00.3721 Jan 9 2013 172459
174625.750 Device Firmware Version 1.12.3688
174625.750 Device Serial Number TA$1ZuBJ
174625.750 interface close
174625.760 J2534 API Version 04.04
174625.760 J2534 DLL Version 1.00.3721 Jan 9 2013 172459
174625.760 Device Firmware Version 1.12.3688
174625.760 Device Serial Number TA$1ZuBJ
174625.760 interface close
174628.988 131072 byte image read.
174628.988 using metadata XML ID 23862006 from file f/ecu/OpenECU/EcuFlash/rommetadata/mitsubishi/23862006.xml
174644.268 J2534 API Version 04.04
174644.268 J2534 DLL Version 1.00.3721 Jan 9 2013 172459
174644.268 Device Firmware Version 1.12.3688
174644.268 Device Serial Number TA$1ZuBJ
174649.720 sending init sequence 2
174649.730 got 0x11 response
174649.730 sending init sequence 3
174650.090 entering bootloader
174650.090 sending kernel size (2029)
174650.100 sending kernel load address (0x0000F000)
174650.110 uploading kernel
174650.440 verifying kernel checksum response
174650.440 kernel valid
174650.640 kernel get version
174650.650 kernel version is OpenEcu Mitsubishi H8/539F Kernel V1.07
174650.650 reading kernel comm buffer size
174650.680 comm buffer size set to 256
174650.680 reading kernel flash buffer size
174650.690 flash buffer size set to 1024
174650.713 -- flashing image to ECU memory --
174651.122 -- comparing ECU flash memory pages to image file --
174651.122 seg start len ecu CRC32 img CRC32 same?
174651.272 LB7 00010000 00003000 18023FFE 1EFDA5D6 NO
174651.292 SB0 00013000 00000200 D90A49D9 D90A49D9 YES
174651.312 SB1 00013200 00000200 614E4403 614E4403 YES
174651.322 SB2 00013400 00000200 9C5C2520 9C5C2520 YES
174651.342 SB3 00013600 00000200 9D0A5827 9D0A5827 YES
174651.352 SB4 00013800 00000200 529496AA 529496AA YES
174651.372 SB5 00013A00 00000200 AB1E2EDA AB1E2EDA YES
174651.382 SB6 00013C00 00000200 01D43F34 01D43F34 YES
174651.402 SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
174651.602 LB6 00014000 00004000 570329C0 570329C0 YES
174651.802 LB5 00018000 00004000 5363B41F 5363B41F YES
174651.992 LB4 0001C000 00004000 D4CD69CA D4CD69CA YES
174652.192 LB3 00020000 00004000 5E12815E 5E12815E YES
174652.392 LB2 00024000 00004000 968D0FC7 968D0FC7 YES
174652.592 LB1 00028000 00004000 BFC27FD9 BFC27FD9 YES
174652.792 LB0 0002C000 00004000 8F3E818E 8F3E818E YES
174652.792 kernel flash enable
174652.822 kernel blank flash page addr 00010000
174653.574 erased in 10 pulse(s)
174653.574 kernel write flash buffer addr 00010000 len 00000100
174653.625 kernel write flash buffer addr 00010100 len 00000100
174653.666 kernel write flash buffer addr 00010200 len 00000100
174653.716 kernel write flash buffer addr 00010300 len 00000100
174653.766 kernel commit flash addr 00010000 len 00000400 crc32 6330f141
174653.836 written in 4 pulse(s)
174653.836 kernel write flash buffer addr 00010800 len 00000100
174653.887 kernel write flash buffer addr 00010900 len 00000100
174653.928 kernel write flash buffer addr 00010A00 len 00000100
174653.978 kernel write flash buffer addr 00010B00 len 00000100
174654.034 kernel commit flash addr 00010800 len 00000400 crc32 e51fa8bb
174654.100 written in 4 pulse(s)
174654.100 kernel write flash buffer addr 00010C00 len 00000100
174654.150 kernel write flash buffer addr 00010D00 len 00000100
174654.200 kernel write flash buffer addr 00010E00 len 00000100
174654.250 kernel write flash buffer addr 00010F00 len 00000100
174654.300 kernel commit flash addr 00010C00 len 00000400 crc32 61b412be
174654.370 written in 4 pulse(s)
174654.370 kernel write flash buffer addr 00011000 len 00000100
174654.426 kernel write flash buffer addr 00011100 len 00000100
174654.472 kernel write flash buffer addr 00011200 len 00000100
174654.522 kernel write flash buffer addr 00011300 len 00000100
174654.572 kernel commit flash addr 00011000 len 00000400 crc32 05211dd0
174654.642 written in 4 pulse(s)
174654.642 kernel write flash buffer addr 00011400 len 00000100
174654.695 kernel write flash buffer addr 00011500 len 00000100
174654.744 kernel write flash buffer addr 00011600 len 00000100
174654.784 kernel write flash buffer addr 00011700 len 00000100
174654.834 kernel commit flash addr 00011400 len 00000400 crc32 57012e2e
174654.894 written in 4 pulse(s)
174654.894 kernel write flash buffer addr 00011800 len 00000100
174654.944 kernel write flash buffer addr 00011900 len 00000100
174654.996 kernel write flash buffer addr 00011A00 len 00000100
174655.046 kernel write flash buffer addr 00011B00 len 00000100
174655.096 kernel commit flash addr 00011800 len 00000400 crc32 2692d34d
174655.166 written in 3 pulse(s)
174655.166 kernel write flash buffer addr 00011C00 len 00000100
174655.216 kernel write flash buffer addr 00011D00 len 00000100
174655.258 kernel write flash buffer addr 00011E00 len 00000100
174655.308 kernel write flash buffer addr 00011F00 len 00000100
174655.358 kernel commit flash addr 00011C00 len 00000400 crc32 d1425302

LeRoyDL
10-18-2013, 10:42 PM
174655.428 written in 4 pulse(s)
174655.428 kernel write flash buffer addr 00012000 len 00000100
174655.483 kernel write flash buffer addr 00012100 len 00000100
174655.530 kernel write flash buffer addr 00012200 len 00000100
174655.580 kernel write flash buffer addr 00012300 len 00000100
174655.630 kernel commit flash addr 00012000 len 00000400 crc32 de4171e3
174655.700 written in 3 pulse(s)
174655.700 kernel write flash buffer addr 00012400 len 00000100
174655.750 kernel write flash buffer addr 00012500 len 00000100
174655.790 kernel write flash buffer addr 00012600 len 00000100
174655.840 kernel write flash buffer addr 00012700 len 00000100
174655.890 kernel commit flash addr 00012400 len 00000400 crc32 5647f3c8
174655.960 written in 4 pulse(s)
174655.960 kernel write flash buffer addr 00012800 len 00000100
174656.014 kernel write flash buffer addr 00012900 len 00000100
174656.062 kernel write flash buffer addr 00012A00 len 00000100
174656.112 kernel write flash buffer addr 00012B00 len 00000100
174656.152 kernel commit flash addr 00012800 len 00000400 crc32 53c4384a
174656.222 written in 3 pulse(s)
174656.222 kernel write flash buffer addr 00012C00 len 00000100
174656.278 kernel write flash buffer addr 00012D00 len 00000100
174656.324 kernel write flash buffer addr 00012E00 len 00000100
174656.374 kernel write flash buffer addr 00012F00 len 00000100
174656.424 kernel commit flash addr 00012C00 len 00000400 crc32 4d348c5d
174656.484 written in 4 pulse(s)
174656.484 kernel flash disable
174656.514 verifying result...
174656.514 -- comparing ECU flash memory pages to image file --
174656.514 seg start len ecu CRC32 img CRC32 same?
174656.666 LB7 00010000 00003000 1EFDA5D6 1EFDA5D6 YES
174656.676 SB0 00013000 00000200 D90A49D9 D90A49D9 YES
174656.696 SB1 00013200 00000200 614E4403 614E4403 YES
174656.706 SB2 00013400 00000200 9C5C2520 9C5C2520 YES
174656.726 SB3 00013600 00000200 9D0A5827 9D0A5827 YES
174656.736 SB4 00013800 00000200 529496AA 529496AA YES
174656.756 SB5 00013A00 00000200 AB1E2EDA AB1E2EDA YES
174656.766 SB6 00013C00 00000200 01D43F34 01D43F34 YES
174656.786 SB7 00013E00 00000200 BD7BC39F BD7BC39F YES
174656.986 LB6 00014000 00004000 570329C0 570329C0 YES
174657.176 LB5 00018000 00004000 5363B41F 5363B41F YES
174657.376 LB4 0001C000 00004000 D4CD69CA D4CD69CA YES
174657.576 LB3 00020000 00004000 5E12815E 5E12815E YES
174657.776 LB2 00024000 00004000 968D0FC7 968D0FC7 YES
174657.976 LB1 00028000 00004000 BFC27FD9 BFC27FD9 YES
174658.166 LB0 0002C000 00004000 8F3E818E 8F3E818E YES
174658.166 flash correct! exiting.
174658.206 interface close

2. Car wont start, am getting fuel pressure to rail and spark (ive not yet verified injector pulse). This issue i'll focus on after EvoScan's working.

The background:
I've uninstalled and reinstalled both evoscan and ecuflash 10+ times, I've followed Greg's instruction thread and have the proper files in place and configured as advised.
Harness has been gone through, thoroughly twice to verify correct pin out.

Sadly i shipped out my stock ecu the morning my flashecu was to arrive but the car was pulled into the garage the night prior under its own power (hindsight, dumb move; i'm looking for a replacement).

(need to get the kids settled for the night, i'll post more shortly).

LeRoyDL
10-18-2013, 11:16 PM
Was just looking over tufftr's write problem thread and noticed a diff in dll's

Mine: J2534 DLL Version 1.00.3721 Jan 9 2013 172459
His: J2534 DLL Version 1.00.3719 Dec 28 2012 233848

Just to rule it out, does anyone also have the newer version (3721) that is operational?

I'm poking around for more logs to compare against.

surreal
10-18-2013, 11:49 PM
i have a similar setup and ive also gotten the same error a couple times.

im sure youve tried this, but i had to remove the tactrix unit from the obd2 port, unplug the voltage booster, unplug both ends the usb cable... and then plug it all back together again. unplugging only the tactrix unit or only the usb cable etc did not work.

i dont know why this happens. i have even had it communicating just fine and sitting in the car at idle, and then it disconnects and gives that error. obviously nothing was even touched or bumped, so i was pretty confused.

im also using the same dll as you are.

Greg E
10-19-2013, 08:46 AM
Evoscan won't connect when battery voltage is less than a certain voltage. I don't remember what that voltage is.

99 vr4
10-19-2013, 09:57 AM
From another user with this same problem....

Tactrix 2.0 J2534 error - Club3G Forum : Mitsubishi Eclipse 3G Forums (http://www.club3g.com/forum/3g-eclipse-gt-gts-specific/149745-tactrix-2-0-j2534-error.html)

EcuFlash J2534 Error Will not Read ECU Please Help - DSM Forums (http://www.dsmtuners.com/forums/evoscan-ecuflash-tuning/399061-ecuflash-j2534-error-will-not-read-ecu-please-help.html)

Drew Technologies : Introduction (http://www.drewtech.com/support/J2534/errorcodes.html)

LeRoyDL
10-20-2013, 04:49 PM
Evoscan won't connect when battery voltage is less than a certain voltage. I don't remember what that voltage is.

EvoScan logs are showing above 12v every time I've tried. I also have a charger on that car I've tried.

LeRoyDL
10-20-2013, 04:50 PM
i have a similar setup and ive also gotten the same error a couple times.

im sure youve tried this, but i had to remove the tactrix unit from the obd2 port, unplug the voltage booster, unplug both ends the usb cable... and then plug it all back together again. unplugging only the tactrix unit or only the usb cable etc did not work.

i dont know why this happens. i have even had it communicating just fine and sitting in the car at idle, and then it disconnects and gives that error. obviously nothing was even touched or bumped, so i was pretty confused.

im also using the same dll as you are.

I have tried all of this :(

LeRoyDL
10-20-2013, 04:51 PM
From another user with this same problem....

Tactrix 2.0 J2534 error - Club3G Forum : Mitsubishi Eclipse 3G Forums (http://www.club3g.com/forum/3g-eclipse-gt-gts-specific/149745-tactrix-2-0-j2534-error.html)

EcuFlash J2534 Error Will not Read ECU Please Help - DSM Forums (http://www.dsmtuners.com/forums/evoscan-ecuflash-tuning/399061-ecuflash-j2534-error-will-not-read-ecu-please-help.html)

Drew Technologies : Introduction (http://www.drewtech.com/support/J2534/errorcodes.html)

Thank you for the links, I had read the 1st already. So far no luck.

LeRoyDL
10-20-2013, 04:54 PM
Question for you guys, is it normal that ecuflash can only communicate with the ECU once before requiring a ignition cycle?

For example, I can perform a read but if I try anything else without turning the ign switch off and then back on I get an communication error. Same goes for if I do a compare or even a write. After each operation the following will always fail until I turn the car off and then back on.

Also if i turn the ign switch on, and attempt to connect with evoscan (even though it fails), ecuflash then fails if I don't turn the car off and back on.

As for the lastest, I've completely uninstalled everything and performed a system restore back to before I installed any of the software of drivers. Same results after I reinstall. I've also tried manually nuking evoscan, ecuflash and tactrix out of the registry, no help.

Tomorrow I'm going to grab another hard drive and do a fresh winxp install (guess that is what Brett is using) and try everything from scratch on a virgin OS. Hopefully some headway is on the horizon.

LeRoyDL
10-21-2013, 09:50 PM
Clean winxp install no dice.

I also tried installing echflash 1.42, I now get different errors in evoscan:

Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.12.368
Info: Battery 12.112V
Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Timer: 2481.2076ms
Info: Initialization Complete...
Info: Waiting for INIT Response...
Error: No Response from Vehicle ECU
Info: Actuator Complete.

When attempting to start data logging it just goes into a loop of retrying.

Still seeing the same sort of oddness where 1st operation is successful and any after fail w/o power cycle. I'm going to be trying the entire setup in my NA next just to verify something odd didn't happen to the awd.

99 vr4
10-30-2013, 10:30 PM
Perhaps your Tactrix is faulty? I have had one fail on me. It is not common, but it does happen.

Also, in your email, you mentioned that you have a SL ECU on the way. The SL ECU and the TT ECU are DIFFERENT! The Clone2 ECU is compatible with both, but the ROM is different. It needs to be flashed for the vehicle that you have.

Lets revisit the basics.

Your car, is this a AWD TT that was converted to a FWD TT or is this a FWD NA that was converted to a FWD TT, or is this a true AWD TT?

If this is not a true AWD TT, is this a auto or manual transmission?

What year is your car?

LeRoyDL
10-30-2013, 11:34 PM
Yes it very well could be the tactrix, i'm not by any means ruling it or the harness out.

I do know the SL ecu is different. First step I was planning on pluging it in and see if evoscan will communicate with it and if I still see the ecuflash disconnected like i do with the other ecu. The SL ecu was verified to be working (communicating with evoscan and ecuflash) prior to it being shipped to me. If that is successful i will flash chrome to it and see if it starts my car. If that fails the tactrix is probably the culprit.

Basics,
The car this is going into is a 91 RT/TT AWD. I also have a 92rt mtx converted to TT which I also tested in with same results as the awd.


Perhaps your Tactrix is faulty? I have had one fail on me. It is not common, but it does happen.

Also, in your email, you mentioned that you have a SL ECU on the way. The SL ECU and the TT ECU are DIFFERENT! The Clone2 ECU is compatible with both, but the ROM is different. It needs to be flashed for the vehicle that you have.

Lets revisit the basics.

Your car, is this a AWD TT that was converted to a FWD TT or is this a FWD NA that was converted to a FWD TT, or is this a true AWD TT?

If this is not a true AWD TT, is this a auto or manual transmission?

What year is your car?

99 vr4
10-31-2013, 08:57 AM
Since you have a 91, this is very easy to trouble shoot...

First, to rule out something in the car causing the issues, you just need to be absolutely sure that only the OBDII connector is connected to pins 84 and 85.... They should not connect to the vehicles original harness.

This way the OBDII data streams are isolated from the vehicle.

FYI, on a US 1G MTX, you do not need to tie in the OBDII data stream to the vehicles MUT bus. There is nothing on this bus that the ECU needs.

In fact, there is nothing else that communicates with the ECU on any other lines EXCEPT the AC controller and the ATX controller. But these additional communication lines are not data streams, they are, simple logic (think on or off) inputs and outputs and they do not use the MUT bus or OBDII data stream.

Baring that, send me the ECU, your harness (I know its not mine, but I can verify it for you), and your Tactrix. I will test everything for you.

Using priority mail, three days to me, a couple for testing, three days back to you... A little more than a week. You have been fighting this for a while now...

Greg E
10-31-2013, 09:01 AM
Leroy, do you happen to have another mini USB cable laying around? I've run into situations where the customers tactrix cable didn't work due to a faulty USB. The actual tactrix port was fine. Just the USB cable that came with it was bad.

Thought I made a thread about it at one point...

99 vr4
10-31-2013, 09:06 AM
Leroy, do you happen to have another mini USB cable laying around? I've run into situations where the customers tactrix cable didn't work due to a faulty USB. The actual tactrix port was fine. Just the USB cable that came with it was bad.

Thought I made a thread about it at one point...

Lol, yes yes check that too....

LeRoyDL
10-31-2013, 01:41 PM
Greg,
I think it was one of your threads where I read it, yes I have tried a new usb/mini cable.

Brett,
Can do, I'll see what the SL ecu does this evening as I am curious but I can package it all up and get it out to you this weekend.

Greg E
10-31-2013, 02:15 PM
Greg,
I think it was one of your threads where I read it, yes I have tried a new usb/mini cable.


Damn... :(

One last question.

With the tactrix cable unplugged from the car, hook up the USB to the laptop and wait for the windows notification to tell you it's detected.

Does the tactrix plug still light up?

Chris@Rvengeperformance
10-31-2013, 04:23 PM
Greg,
I think it was one of your threads where I read it, yes I have tried a new usb/mini cable.

Brett,
Can do, I'll see what the SL ecu does this evening as I am curious but I can package it all up and get it out to you this weekend.

I guess you got the ecu? Glad it made it ok. I know 100% that will connect if the rest of your setup is right.

LeRoyDL
10-31-2013, 05:44 PM
Damn... :(

One last question.

With the tactrix cable unplugged from the car, hook up the USB to the laptop and wait for the windows notification to tell you it's detected.

Does the tactrix plug still light up?

It does, it also lights up when it is in the car with the ignition switch on and usb disconnected.

LeRoyDL
10-31-2013, 05:46 PM
I guess you got the ecu? Glad it made it ok. I know 100% that will connect if the rest of your setup is right.

It's out for delivery right now, it should be waiting for me when I get home :)

LeRoyDL
10-31-2013, 09:59 PM
Okay, so SL ecu same issue where initial ecu connection works secondary fails.

Just to clarify what happens.
1. turn on ignition
2. compare chrome rom successfully
3. attempt to test write fails.
4. turn off ignition switch, turn back on
5. attempt to test write successfully
6. attempt to write fails
7. turn off ignition switch, turn back on
8. attempt to write successfully
and so on..

Evoscan seems to fail no matter what because it appears (watching logs) to initialize connection and then waits for ecu respond. The channel seems to go dead for anything post initial connection attempt.

Just to be certain I also tried the SL ecu in my FWD (i can't attempt to start it atm b/c the turbos are off). Same results as the AWD. It really seems at this point the tactrix is faulty.

Brett/Greg,
Can either of you imagine any circumstance where crossed wires could cause this behavior? Again, i've verified every wire on this harness several times visually as well as with multimeter.

Would I be correct assuming that as long as the ecu is powered, communication should work across these pins and the tactrix cable? I am more then willing to pack up all this stuff and send it to you Brett and I appreciate the offer. However, I would hate to waste your time and add the extra time just to confirm the tactrix is faulty.

Brett,
If you have a harness ready to go or can soon, I'd assume buy one and have it on the way while I try to see if i can get the tactrix replaced. That is if you guys feel the harness might still be a contributing factor; the ecu(s) and car(s) are ruled out.

Thoughts?

~LeRoy

LeRoyDL
10-31-2013, 10:03 PM
FWIW: To further rule out a problem with the car I'm picking up another 1st gen ecu this weekend to see if my AWD still starts (since no luck with either ecu running chrome). Silly mistake thinking everything would go flawless and I'd never need one again :D

mb3000
10-31-2013, 10:27 PM
My .02 is to keep the ignition off. Click the "Test Write to ECU" then switch the ignition to "ON" and quickly hit the "OK" button on the dialogue box. I think that the ignition needs to be cycled for everything you are trying to do.

Even with Evoscan, click the datalog button and then when it says "Waiting for Vehicle ECU" switch the vehicle ignition to "ON" and see what it does. Very intrigued with this problem.

striker2
10-31-2013, 11:12 PM
My .02 is to keep the ignition off. Click the "Test Write to ECU" then switch the ignition to "ON" and quickly hit the "OK" button on the dialogue box. I think that the ignition needs to be cycled for everything you are trying to do.

Even with Evoscan, click the datalog button and then when it says "Waiting for Vehicle ECU" switch the vehicle ignition to "ON" and see what it does. Very intrigued with this problem.

I dont have to do that with my 93. I can go between evoscan logging, stop the log, start it again, stop the log, flash the PCM, log, etc. without ever turning the key off.

to me, this sounds like either a driver issue on the PC or a bad tactrix.

LeRoyDL
10-31-2013, 11:12 PM
With the ignition switch off I get a less then 5v warning and the tactrix LEDs are not illuminated unless connected to usb. Brett suggested it is normal for the leds on the tactrix to illuminated when plugged into that diag port with the ignition switch in the off position but seemed to think it was okay (unless i misunderstood).

If that is abnormal? Pin 12(47 for 99) & 25(59 for 99) on the 1st gen plug are switched.

mb3000
10-31-2013, 11:38 PM
My Tactrix lights up when plugged in.

LeRoyDL
10-31-2013, 11:43 PM
:confused:
Dang, so w/o usb just plugged into the car?

The both power leads are switched on my awd, ill verify the fwd tomorrow. You are 1st gen?

mb3000
10-31-2013, 11:45 PM
I have a '97. The Tactrix illuminates the second it is plugged in.

mjannusch
10-31-2013, 11:59 PM
I have a '97. The Tactrix illuminates the second it is plugged in.
Same here on my '95. I don't know what's correct for sure on 1st gen cars though. It could be that the harness to the OBD port isn't configured for constant power - I dunno.

striker2
11-01-2013, 09:54 AM
:confused:
Dang, so w/o usb just plugged into the car?

The both power leads are switched on my awd, ill verify the fwd tomorrow. You are 1st gen?

on my 93 the tactrix doesnt illuminate until the key is switched on or the USB is plugged in.

Chris@Rvengeperformance
11-01-2013, 10:34 AM
yeah if i plug the tactrix in my 95 it stays lit even with the key off. my 92 did that too. It will even kill the battery after a few days. I'm pretty sure something is jacked with your harness setup. if you want you can mail your tactrix to me and I can test it for you.

Greg E
11-01-2013, 10:57 AM
yeah if i plug the tactrix in my 95 it stays lit even with the key off. my 92 did that too. It will even kill the battery after a few days. I'm pretty sure something is jacked with your harness setup. if you want you can mail your tactrix to me and I can test it for you.

This!

99 vr4
11-01-2013, 11:05 AM
The Factory (And Clone PnP Harness) configuration is that the OBDII power comes from the Battery Backup line on the ECU which means it ALWAYS has power. Whenever the Tactrix is plugged into the OBDII port, even with the car off and the USB cable not attached, the Tactrix LEDs should be on and color changing. Per Mike at Tactrix, this in no way will hurt the Tactrix or cause a premature failure. He stated to me that there are thousands of customers who leave their Tactrix plugged in all the time and he has not seen a single failure from this yet.

Now some of the other harnesses out there are not wired this way. This in no way is not really wrong; it is just not the factory configuration. The only down side is you won't be able to log startup issues because the OBDII port will not have power until the MFI relay kicks on and powers up the ECU.

@LeRoy, I am sure that the ECU is fine as it seems that you have ruled out the ECU. I do believe that it is either the harness, or the Tactrix. I will be more than happy to test BOTH of them here on the test bench to determine if they work correctly or not. This would be far faster than sending the Tactrix back to them, especially if the Tactrix is OK and it is the harness. Just PM me and I will send you back my address. They both should fit in a small flat rate box or padded envelope and that should be less than $5 for two day Priority Mail.

LeRoyDL
11-01-2013, 09:30 PM
Brett,
PM sent.

LeRoyDL
11-01-2013, 09:47 PM
I wasn't initially planning on running a flashable ecu in my FWD since I'm on the fence about parting it but since I have a spare ecu now, why not. I'm thinking I'll just purchase a harness from Brett to rule that out. It looks like Tactrix support / sales is closed until 11/5. Once they are available I'll see if they have any suggestions or recommend a firmware change or reflash of it.

Thank you all for all the help and suggestions.

99 vr4
11-01-2013, 11:40 PM
LeRoy,

I got the pm re the harness purchase. The harness is significantly different between the NA SL and the TT. If I build a harness for the TT, it will not run correctly in a NA SL and if I build a harness for the NA SL it will not run correctly in a TT.

This applies to your harness as well. The SL is unique.... And slightly more complicated and slightly more expensive.

So if you want a harness, no problem. Just choose wisely. Unfortunately I will not be able to offer a package price this late in the game. Sorry. FWIW, I am leaning towards your Tactrix being bad.

LeRoyDL
11-02-2013, 02:46 AM
huh, figured they were plug in play since tt ecu works fine in the NA. Regardless, I am trying to do what makes most sense and is quickest, the car has already been down long enough and i have other projects on hold until i get this wrapped.

Sent you pm about the other part.

LeRoyDL
11-04-2013, 06:12 PM
FWIW:
The car still starts right up with the 1st gen ECU. I ordered a harness from Brett and will talk to tactrix when they reopen in a few days and see if they have any suggestions.

LeRoyDL
11-08-2013, 09:03 PM
I got the harness from Brett, the car starts right up and evoscan works. The tactrix also stays illuminated when plugged into the diag port as Brett suggested it should.

I'll go through the harness I made and compare it to Brett's to see if i can figure out where the problem is.

Thanks all for the help and advice.