Cone_Killer

My ecu version is A2WC521C. I'm not sure about the boost. These are 2nd gear logs on my initial base map from Cryo.

Small update: On the way to work this moring, I tried to log with the vagcom again. This time though, I changed all of my 4 byte parameters to 2 byte. It is logging further into the high rpms for some reason. Take a look at the logs labeled accordingly.Old vagcom log.csv New vagcom log.csv

Thats the one I couldn't log with. This is the one I could. http://i105.photobucket.com/albums/m219/born2race94/2012-10-23_10-58-52_843.jpg

Very odd. I see that the last guy in this thread with this problem fixed it by using the Tactrix 1.3. This might get a bit confusing but I will try to explain. I bought a used Accessport last year and it was the original v2 with the silver dongle w/metal clip on the port connector identical to the Tactrix 2.0 setup. I could not log with that AP for some reason. It would always say something like "dropped comms". So I sold it and picked up the newer v2 with the 1 piece cord, very similar to the Tactrix 1.3. If I remember correctly, that AP logged just fine all of the time. I may just need a Tactrix 1.3

Ok, I have tried a few things here. So far this is where I am at. I have 3 ferrite clips on the OBD harness. I cleaned the ground straps from the exhaust manifolds to the frame rails along with the large starter ground on top of the tranny bellhousing. I disconnected my phone charger and my boost gauge. I also turned my radio and A/C off. I am getting the same results. I also changed my parameters to 2 byte instead of the 4 that I had. I even tried SDcard logging on the Tactrix and its doing almost the same thing. One thing that does seem to be odd is that I can get a full log into the higher rpms if I kind of feather the throttle (see log 1). I only hit 100% throttle for a brief second. Right after that, I tried to slowly roll into WOT but it cut out just the same (see log 2). Log 3 is the first pull with the Tactrix 2.0 today. I'm just running a standard battery from advance auto. The terminals are perfect and have never had a hint of corrosion on them in their lifetime. Log 1.csv Log 2.csv Log 3.csv

Got my new 2.0 from Tactrix... same shit different day

Would anyone happen to have swaybars for sale?

I may be going as well.

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?

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.

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

This is the log. It drops at 3,217 3,302 ect.

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

Just a simple Toshiba satellite running Win7. It ran the vagcom very well so I'm hoping the tactrix will be even better.

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...

I appreciate it but I don't want to ever bug you to use it. I went ahead and reordered one.

Ahh Dale, you seem to have beaten me out of my second Tactrix in two days.

Order is on hold

I'll call and cancel my order from Tactrix if you're selling. Hell, I might even pay just to use it.

Good to hear the install went well. I would like to take a ride in your car to see how those hotchkis sways feel. I bought a Tactrix 2.0 this morning so I can finish up tuning with Dave at Cryo.

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.

Here you go. romraiderlog_20130220_154045.csv

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.

and the RomRaider woes continue. Can't get it to log at WOT which seems to be a common error.

Thanks. You and Dale ever work out a date for your bilstein install?