dschultz Posted September 7, 2012 Share Posted September 7, 2012 I've have a couple of vag-com cables that EcuFlash recognizes but will not read/write the ECU with. I also have a couple of vag-com that do work too. The difference between the working and non-working cables seems to be the FTDI chip that the cable is built with. I speculate that EcuFlash does not work with all versions of FTDI chips. It's hard to know this ahead of time when ordering one from a seller. Your best bet is to use the Openport 2.0. Link to comment Share on other sites More sharing options...
jjtjp Posted September 7, 2012 Share Posted September 7, 2012 Thanks for the info...I purchased one off of amazon that others recommended, but maybe its different... who knows. I know op 2.0 is best, but for the price, and what I want to do(flash correct ROM for my car)...vagcom seemed fine. Besides, my time isn't worth much since I'm unemployed. Link to comment Share on other sites More sharing options...
jjtjp Posted September 8, 2012 Share Posted September 8, 2012 Just to update, I found a local guy who had an open port, and he had the same results as I was getting with the Vagcom. Romraider worked for him, but no ecuflash. We deduced that I have a locked ECU. Now to find some way to unlock it or hunt down a replacement. Anybody know a really nice person in Charlotte nc area with cobb ap v2? But the good news is, my vag com works...i think ;-) Link to comment Share on other sites More sharing options...
UTwrestler22 Posted October 19, 2012 Share Posted October 19, 2012 Where could i find a vag com cable locally most likely? Im having some issues with the ecu and would have liked to have logged 2 weeks ago so the sooner i get one the better. Any ideas? Link to comment Share on other sites More sharing options...
uncle humjaba Posted February 12, 2013 Share Posted February 12, 2013 Yes there have been multiple reports of that problem but no concrete solution. I have personally seen a problem where data values logged were not what was expected. Such as a 3rd gear pull and the Throttle Position started at 100% in the log then random values appeared until the end of the pull. A low-level RomRaider trace indicated that it is what the ECU was sending out. Either that or the serial driver for the cable started to act weird and caused the random numbers to appear. Unfortunately there's no way to trace the serial driver. Then we tried to repeat the problem using the Openport 2.0 standalone logger and it read just fine. So maybe that does point to a driver problem either USB or serial VCP. Has anyone had any issues with romraider halting data logging at WOT. I've no issues with idling and driving normally, but during a WOT third gear pull romraider inevitably fails at ~4k and stops data logging. I've read multiple threads/ideas concerning spark plugs and random EMF; there does not, however, appear to be a solution. Anyone have any thoughts on this? Has there been any progress on this in the last year? I'm having the same problem. Bought a vag-com cable off Amazon, spent a few hours futzing with the drivers and such so now both ecuflash and rr are happy (I can read and flash, and I can log as long as I'm not WOT >~4500RPM). But, as with the guy above, all my logs seem to cut out between 4-5kRPM and then come back after the pull is over. RR doesn't crash, and has no trouble continuing to log once the ECU starts responding again. I've tried 2 and 4 ferrite chokes on the cable, and it still doesn't work. I can drive around to my heart's content, but the second I go WOT and let it pull, it dies... This on an Alienware Windows 7 home edition laptop. Link to comment Share on other sites More sharing options...
iNVAR Posted February 17, 2013 Share Posted February 17, 2013 Hmm, can you do me a favor and log battery voltage when you do are having this problem with the cutting out of the logs? I want to test a theory.... thanks. Link to comment Share on other sites More sharing options...
uncle humjaba Posted February 20, 2013 Share Posted February 20, 2013 Hmm, can you do me a favor and log battery voltage when you do are having this problem with the cutting out of the logs? I want to test a theory.... thanks. I did this after reading about how replacing the battery fixed it. I don't think I have the log anymore, but voltage was constant throughout the pull. Link to comment Share on other sites More sharing options...
iNVAR Posted February 20, 2013 Share Posted February 20, 2013 Darn... Okay. Hmm maybe some cars have bad grounds...? I used to have this problem and it mysteriously went away... Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 20, 2013 Share Posted February 20, 2013 I too am having this problem. I have put on 3 ferrite chokes on the wires BEFORE the OBD plug in the car and put 1 choke on the vagcom cable where the OBD plug is. I added another ground strap wire to the passenger side head to frame rail as well. Nothing. I can log all day without problems and then as soon as I go WOT, it drops the connection around 4K. I'm so lost. Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 20, 2013 Share Posted February 20, 2013 Hmm, can you do me a favor and log battery voltage when you do are having this problem with the cutting out of the logs? I want to test a theory.... thanks. Here you go.romraiderlog_20130220_154045.csv Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 21, 2013 Share Posted February 21, 2013 Small update: I am 95% sure that this is a cable problem that cannot be remedied. It is doing the same thing with Learning View. After the WOT pull, learning view cannot connect. I have to unplug the cable from the USB and plug it back in. After that, its fine. Link to comment Share on other sites More sharing options...
iNVAR Posted February 22, 2013 Share Posted February 22, 2013 Here you go. Interesting. The voltage dips a tiny bit prior to it cutting off... Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 22, 2013 Share Posted February 22, 2013 It dips the the same voltage earlier in the pull. 13.98 is still incredibly high for it to cause problems. I could see maybe 11.98... Link to comment Share on other sites More sharing options...
uncle humjaba Posted February 22, 2013 Share Posted February 22, 2013 Not sure if I posted here or not, but I used a friend's Tactrix Openport 1.3 (the official cable) and it worked like a charm. I can still use the vag-com for learning view, flashing, etc but for logging you may just need the real thing. Link to comment Share on other sites More sharing options...
iNVAR Posted February 22, 2013 Share Posted February 22, 2013 (edited) It dips the the same voltage earlier in the pull. 13.98 is still incredibly high for it to cause problems. I could see maybe 11.98... That's not true at all. Graphed over time with the engine speed and voltage. I only graphed a tiny bit of it after logging resumes, to shrink the graph a bit. http://legacygt.com/forums/attachment.php?attachmentid=142648&stc=1&d=1361502522 You can see voltage dips down for whatever reason. Yes, the voltage should be sufficient enough, but that's not my point. The point I'm trying to make is that there's clearly an electrical anomaly that causes it to have problems. Edited February 22, 2013 by iNVAR Link to comment Share on other sites More sharing options...
iNVAR Posted February 22, 2013 Share Posted February 22, 2013 And here's the entire log you gave me so you see how it behaves when you're not flooring it. http://legacygt.com/forums/attachment.php?attachmentid=142649&stc=1&d=1361502803 Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 22, 2013 Share Posted February 22, 2013 That's not true at all. Graphed over time with the engine speed and voltage. I only graphed a tiny bit of it after logging resumes, to shrink the graph a bit. I'm not sure what part isn't true? The voltage drops to 13.92 several times before it cuts out. That is a fact Link to comment Share on other sites More sharing options...
iNVAR Posted February 22, 2013 Share Posted February 22, 2013 Are you talking about it dipping to 13.92 some other time that's not shown in your log? Because in your log, it's not true. Look at the graphs. It only dips down to 13.92 immediately before cut out. Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 22, 2013 Share Posted February 22, 2013 This is the log. It drops at 3,217 3,302 ect. Link to comment Share on other sites More sharing options...
iNVAR Posted February 22, 2013 Share Posted February 22, 2013 Yes, that's my point. That is immediately preceding your cutoff. Can you not see the graphs? Sheesh. Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 22, 2013 Share Posted February 22, 2013 I guess I just don't understand. If the 13.92 voltage is what caused the cut off then why didn't it cut off at one of the earlier points, that is all Link to comment Share on other sites More sharing options...
iNVAR Posted February 22, 2013 Share Posted February 22, 2013 (edited) Look at the graph. It clearly shows that during WOT, your voltage is lower and immediately preceding the cutoff there are dips down to 13.92. Everything during WOT is lower than after WOT. Edited February 22, 2013 by iNVAR Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 23, 2013 Share Posted February 23, 2013 You do know that your alternator is turned off during WOT right... hence the voltage drop. None of this really matters though as this is clearly not a voltage problem, its the cables issue. Link to comment Share on other sites More sharing options...
iNVAR Posted February 23, 2013 Share Posted February 23, 2013 It could be that these cheaper cables are more sensitive to electrical issues because I've been using the SAME cable for close to 4 years now and used to have this problem, and then it mysteriously went away. Yes, I know that the alternator is shut off during WOT. I also know that this makes the electrical system more susceptible to gremlins since the alternator also has an integrated voltage regulator which acts as a buffer for electrical anomalies. Maybe I'm not explaining myself clearly enough to you so I'll try again. The 13.92 drop might not be the reason why the cable drops connection. In fact, the voltage being too low is most likely not the issue at all. I'm sure the cable can operate at a lower voltage... What I'm saying is that the 13.92 is a symptom of an underlying problem in the electrical system that causes it to lose connection. I used to have this same problem with an Accessport also and I'm fairly certain a bunch of other people did as well. Link to comment Share on other sites More sharing options...
Cone_Killer Posted February 23, 2013 Share Posted February 23, 2013 Damn, now that you mention it, I used to have this problem with my accessport as well. I first had the AP with the dongle and had the same logging issue. Then I sold it and bought the newer style with the cable and everything was fine. Hmmmm, I wonder what it is? 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