qikslvr

Just an FYI. I have been able to get all software and drivers to work in WINDOWS 8.

Just going to chime in on this last series of posts... Just checking to make sure that you guys have adjusted the communications (BAUD) rate in the driver's properties, it should be backed down to 4800. Also if you go into the "advanced" section of the driver properties, you can adjust the sliders that control the data transfer rate too. I always back both sliders down by one notch. That and if you are using a newer version of the RR software, check to see how you have the "enable fast polling mode" option set. Try it with and without this option selected and see if it makes any difference. In other news. I've got the newest versions of ECUFlash and all the Romraider programs/functions working on my new laptop that is running WINDOWS 8. I just plugged in the my usb to serial cable and then chose which driver to use and then I selected the "ftdibus.inf" file from the "cdm v2.08.28 certified" driver from the ftdi webpage. Or, if you already have a driver installed, be sure to choose the device as a "usb to serial adapter" and not the "prolific device". Works great so far. I've used it to pull my rom of my OutbackXT and to do a little logging.

Doing mine right now and found that heating the hoses up with with a hair dryer to soften them up a little and makes it easier to get them off without damaging the ends of the hoses.

Hey guys just thought I'd let you know that I'm back and will be working on an 05 OBXT project this time, so I should be around more often now and I will try my best to keep this tread up to date and help out wherever I can.

Use the original Street Tuner or Street Tuner Advanced, but not Access Tuner Race.

Look under the EDIT drop menu and select ADVANCED PARAMETERS. It will bring up a window that lists all the DTC codes. Items with a check mark will NOT set of the Check Engine Light. Hope this helps...

Just an update. I really don't get on here much anymore and I really appreciate you guys helping each other out. I no longer have my own LGT, so I will be of limited assistance in troubleshooting from this point forward. The only windows7 computer I have is a desktop, so I won't be of any help in that arena...

Ask and you shall receive. First post updated...

And that's the way it's been on the three of those cables that I have had. This is the reason why I get a little frustrated with these people who just can't seem to make it work. If the cable is good; it should be pretty much plug and play:confused:.

Thanks for the pic. Now I know where my driver disc is now that I've seen the picture.

Whenever you install RR and ECUflash; you need to get/download the ECU Definitions which are additional files. Then you need to unzip them (if they are zipped). After that you need to copy the ECU Defs and/or Standard Units files to the folder where ECUflash or RR is installed. Just right click on the ECUFlash or RR shortcut and look at the program location or click on the find target button. This is the directory you need to copy the ECU defs into.

When using RomRaider or ECUflash; you need to have the current ECU Definition files to go with them. If you have not downloaded the ECU defs and unzipped them and copied them in to the same directory as the ECUflash or RR software; then it won't work properly. The other option is to go into the menu for ECU flash and select ECU METADATA file location and go find where you downloaded the defs to. Also, it appears as if you do not have the proper drivers installed for the cable or you have not selected the correct COM port for your cable. If the ECUflash software cannot see your cable it cannot use it to connect to the car. Make sense? Most of this isn't a "Subaru Thing"; it's a matter of properly configuring the computer so RR/ECUflash software will be able to access the VAG-COM cable and connect to the ECU. If the RR logger is working ; then it's just a matter of configuring ECUflash software properly so it will work too.

You need to get the right/un-corrupted ECU DEFINITIONS for ECU flash. That or you haven't pointed ECUflash to the directory where the defs are if you have them. And it also appears as if ECU flash doesn't know whatCOM port your cable is on.

Sure. I think it' still hanging in the garage where it's been forever. My little blue netbook went up in smoke one day when I plugged it in, so I bought another Dell netbook to use while my original netbook was in for repairs. When I migrated everything over to the Dell; I also had issues with RR synching up and staying connected. The problem I have with this laptop is that the properties/settings window for the ports is different. I use two cables(1 for RR/ 1 for WB) and both have serial->usb convertors in line. The Cobb v1 cable I use with ST and the APv1 shows no advanced settings at all now and the cable I use for the wideband now shows a completely different different advanced settings tab:confused:. ST-A hooks up to the ECU real quick and works flawlessly, but RR is still flakey at best. I get zeros from the wideband like every tenth line of the log. I'm thinking that Microsoft did us a favor and re-wrote that part of device manager in the last full release of XP. It's basically treating USB1 devices different than it used to. I'm using the same cables and drivers I've always used, so something else has changed. I'll go back out with my original netbook and see if the wideband works properly with that one. If it does; then it's got to be something in windows.