Cone_Killer Posted February 28, 2013 Share Posted February 28, 2013 I have done tons of research on this problem with no fix yet. My issue is this; I can flash, use learning view and log normal driving without any issues. As soon as I try a WOT pull, it cuts out anywhere from 3-4.5k. When it cuts out, romraider says "connecting". So far this is what I have done to try and fix: Load test battery (597 out of 600cca and 12.97v) its good Check and clean engine grounds (two head to frame and the top of tranny) Installed 3 ferrite magnets on the OBD harness before plug Installed 1 ferrite on the vagcom cable after the OBD plug Disconnected my phone charger Turned the radio and A/C off I have tried logging with vagcom and a Tactrix 2.0. I have also tried stand alone SD card logging with the Tactrix and it doesn't turn off but the data is sporatic and repeating. I have included a log from each style and posted them labeled accrodingly. Any help would be greatly appreciated because I have to start this tune with Cryo.Vagcom log.csv2nd gear pull Tactrix USB cable.csv2nd gear pull Tactrix SDcard.csv3rd gear pull Tactrix SDcard.csv Link to comment Share on other sites More sharing options...
iNVAR Posted February 28, 2013 Share Posted February 28, 2013 OP knows this already, but for everyone else: As I mentioned in the other thread, a whole bunch of people seem to have this issue too... Can't figure it out. And like I mentioned, I used to have this problem intermittently with an APv2 (silver dongle, sold it already) and my vagcom cable. The problem then completely disappeared with the vagcom after a while. This guy just posted a thread about his AP having this problem: http://legacygt.com/forums/showthread.php/accessport-keeps-cutting-out-wot-202461.html Link to comment Share on other sites More sharing options...
Strizzy Posted February 28, 2013 Share Posted February 28, 2013 http://legacygt.com/forums/showthread.php/wot-logging-issues-179542.html My bad luck build Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 28, 2013 Author Share Posted February 28, 2013 I read you're thread. You replaced the entire ECU? Was it reprogrammed for your key? Link to comment Share on other sites More sharing options...
Strizzy Posted February 28, 2013 Share Posted February 28, 2013 I found an ECU on car-part.com for $125 + shipping. I replaced my old ECU with it and reprogrammed my keys (I have access to Subaru's SSM tool if I ask nicely) with the codes on the small metal tags that came with my keys when I got the car. Flashed it with my map, started it up, and completed a log. My bad luck build Link to comment Share on other sites More sharing options...
blongo804 Posted February 28, 2013 Share Posted February 28, 2013 Just encountered this problem today for the first time in my car using a Tactrix 1.3. Pretty upsetting and it better not happen again!!! Link to comment Share on other sites More sharing options...
bnguyenbb6 Posted March 1, 2013 Share Posted March 1, 2013 I'm assuming that the connectors on the OBD2 port itself are wearing down or losing connection. I had this problem sometimes and problems connecting other times. Try picking up a OBD2 extension and plugging the Tactrix to the extension(leave the extension plugged in). That way, when the connectors wear down, you just replace the $20 extension cable. Works for me... Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 1, 2013 Author Share Posted March 1, 2013 Talked to Mike at Tactrix today. He had me send him all of my SDcard logging data. It looks like its an ECU issue as Strizzy encountered. He said that the data loss appears to be caused by the ECU lowering the priority of the OBD port during those times. Therefore, dropping the connection. Link to comment Share on other sites More sharing options...
iNVAR Posted March 1, 2013 Share Posted March 1, 2013 That would be weird though because my own problem went away on its own... Unless maybe mine was just caused by a bad connection, hrm. Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 1, 2013 Author Share Posted March 1, 2013 I may just check the ecu connections and try again. Could be something a wee bit loose from the factory, who knows. Link to comment Share on other sites More sharing options...
G5892 Posted March 1, 2013 Share Posted March 1, 2013 This used to happen to me a lot. This was the main reason why I switched over to the AP. Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 1, 2013 Author Share Posted March 1, 2013 I also had the same problem with my AP which is why I sold it. Link to comment Share on other sites More sharing options...
Spec B Posted March 2, 2013 Share Posted March 2, 2013 I slightly bent the pins on my tactrix cable to get a better bite on the port. Solved my problem - but they eventually (after a few months) loosen up again - rinse and repeat. Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 2, 2013 Author Share Posted March 2, 2013 The OP2.0 is only a week old. I wish the pins were the problem Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 2, 2013 Author Share Posted March 2, 2013 Spoke with Mike at Tactrix again yesterday. He is having me add in "showsample = 1" in the .cfg file to narrow down repeat data. I have also extended the logging interval by 15 miliseconds to help the communication complete. I'll post up results tonight after I log with the changes. Link to comment Share on other sites More sharing options...
iNVAR Posted March 2, 2013 Share Posted March 2, 2013 Eh, try messing with the OBD port anyway. Plug/unplug it a bunch of few times to make sure the contact is good... The OBD port bites onto the cable's pins, not the other way around. So if the OBD port isn't biting firmly or maybe there's corrosion or oxidation, it won't make good contact... Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 2, 2013 Author Share Posted March 2, 2013 I'll definitely check as I am running out of other things to narrow it down with lol Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 5, 2013 Author Share Posted March 5, 2013 The plug was spotless. I just don't understand. It logs beautifully until 3kish, and then shit just goes haywire. I just made this log 10 minutes ago. I'm staring to think its the ECU like Strizzy had... but I can't figure out why it would be.romraiderlog_20130304_191422.csv Link to comment Share on other sites More sharing options...
Spec B Posted March 5, 2013 Share Posted March 5, 2013 Even if it is spotless..try slghtly bending the pins. It is worth a try..takes 2 minutes, and you can cross it off the list of things you checked. Hope you get it worked out. Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 9, 2013 Author Share Posted March 9, 2013 Looks like I will never be able to tune. I've done everything short of replacing the ECU. I don't want to spend all that money just to find out that doesn't work either. Link to comment Share on other sites More sharing options...
iNVAR Posted March 9, 2013 Share Posted March 9, 2013 You tried messing with the pins? I'd be very surprised if this required an ECU replacement being that I had the issue and I still have the same ECU. Maybe a battery replacement for some reason? Ugh... Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 9, 2013 Author Share Posted March 9, 2013 The battery can't be any better than it is. I talked to Strizzy about this and it seems as if we have identical problems and the ECU fixed his. He is VERY knowledgeable on this problem. Link to comment Share on other sites More sharing options...
iNVAR Posted March 9, 2013 Share Posted March 9, 2013 http://www.romraider.com/forum/viewtopic.php?f=15&t=7686 http://www.romraider.com/forum/viewtopic.php?f=15&t=4374 http://www.romraider.com/forum/viewtopic.php?f=5&t=5524 Might help. You are definitely not alone my friend. Link to comment Share on other sites More sharing options...
Harbs Posted March 15, 2013 Share Posted March 15, 2013 I had the same thing with my $140 EvoScan cable (which now works awesome). Turned out it was the cord. I Had to crack open the plug and de-solder the cord and replace it with a decent quality printer cable I'd cut the end off. Soldered up the 4 connections it's rock solid now. Doesn't cut out. Before that though, I aslo had trouble getting it to recognise on my laptop properly and it would cut out at revs too. All good now though. Link to comment Share on other sites More sharing options...
Cone_Killer Posted March 29, 2013 Author Share Posted March 29, 2013 Update: After numerous conversations with Tactrix and other members.... the car still won't log a WOT pull. I think I might light it on fire. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now