qikslvr

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.

Grab them with some pliers and twist them a bit. then jam a flathead underneath and twist. odds are they are old and hard and going to split anyway.

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.

So you would agree that my 2006 will work fine with this ebay cable? Excellent information and should be put in the very first post of this thread.

 

Thank you.

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

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.

[02:11:17.738] Unable to find parent metadata SM5236

[02:11:17.738] ROM metadata models SM5237.xml is invalid.

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.

I did read that. I didn't really consider LV or logging to be reading.

 

FWIW my 1.3 Tactrix cable works to do both on the CAN-BUS ECUs. If that is the case, will the VAG-COM also work?

I actually use my APv1 cable and ST-A to do everything on my car and rarely, if ever; use the VAG-COM cable for anything(other than to create these threads). I guess I did try to use this cable to log about a year ago on an 08 WRX and couldn't connect with it, but I didn't spend much time messing with it as someone else there had a Tactrix v2 cable that worked right off. Maybe someone else could give it a try and report back.

Is that v1.3 Tactrix cable a serial connection or a USB(tan or black)?

O.K. so you've got an EDM(European? help me out) 2003 STi that you would like to READ the ECU off of. Correct?

Sounds like the cable is working fine as it is currently working with all other applications. So from here it looks like you need to also get another piece of hardware from what I can gather. If your STi isn't drive by wire; then you will need a "port initiator" that will pass the flashing voltage and end-line signal to the ECU. At least this is the case for USDM vehicles of the same year and model. Yours may be different, so you might want to scan the OpenECU forum for more info on your specific model.

Here is a link to the part that is needed for USDM vehicles:

http://www.tactrix.com/product_info.php?products_id=33

Check it out and let us know what you find...

Don't give up just yet. I've been meaning to do screen shots of the procedures(for this and my other thread), but have been dealing with a few family emergencies(in other cities), so I haven't had time to get it done. There are a couple things that are easier to explain with pictures than words. I use StreetTuner-Advanced most of the time personally and I don't have my old laptop that has ECUflash with me, so I will get some screen shots when I'm at home Friday. I will then work them into another version of the walkthrough and post it up here.

If Learning view is working then ECUFlash should too. We just need to figure out which setting needs to be tweaked. Again, I don't have the tools or time to work with you today, but I will get you up and running when I get home and have a free minute so please hang in there just a little longer.

Good call asking the basic questions, you have definitely done this for a living at one point lol. Yes, I have the green connectors hooked together and ignition is in the on position (w/ fan cycling). I've uninstalled/reinstalled the drivers maybe 4 times along with ecuflash. I'm at the point of giving up

The easiest way to test the cable is with RR logger. If you have plugged in the cable and watched it pop up in Device Manager, found the correct COM Port, adjusted the BAUD rate(not bit rate) then it should work with RR logger. Please comb back through the tread and make sure you are following all the instructions thouroughly.

Make sure you turn the key forward to the "ON" position before starting RR. Make sure you are selecting the correct COM port from the drop box in RR. If your COM port shows up in RR it should work(might be flakey, but it will work). Watch to see if the words in the top right corner change from red to green when you select the com port(should change from Connecting to ECU to Reading Data also). Make sure you select something from the Parameter list on the left AFTER you connect to the ECU.

It's all rather basic. It may take a little work on your part to figure it out, but I'm sure you will if you try. Again, read back through this thread. Every possible problem has been covered more than once. I made the instructions as simple and thourough as possible. It's all covered in here somewhere;).

Are you connecting the green test connectors that are found in the passenger side footwell(top centerish behind the glovebox may be tucked under carpet in a little pocket)?

Also do you have the key turned to the "ON" psoition?

Are you sure that the drivers for the cable were installed properly and the computer is seeing the cable? If you open Device Manager(under system in control panel) and then plug in the cable; you should see a new item pop up under LPT&COM ports. It should show either a "Serial to USB Adapter", "Mosfet usb device(or something like that), or some other name depending upon which driver was used. If it does; you will need to figure out which COM Port it is assigned to. When you open RomRaider Logger; you will need to select that com port from the drop box in the upper right corner. When you do that the words in the upper left corner should change from "connecting to ECU" to reading data or something. I'm actually out of town, but will be back soon and will gladly assist when I can.

Did you get a driver disc with the cable?

Does anyone know of anywhere to download romraider 0.5.0? I cat seem to get ecuflash 1.29a to connect to my ECU and I want to try romraider but the latest version isn't working. I've spend hours trying and followed qikslvr's instructions. I'm a little frustrated to say the least! I need to figure this out so I can install my UP/DP and get infamous tuned. Please help.

I downloaded romraider and ecuflash, in romraider it keeps on telling me i need to download the definitions. and i did. but it keeps telling me i still need to do so. I dont understand what is going on

After you update or download the definitions; you need to go find where they were downloaded to, unzip them if necessary and move the resulting files to the RR directory. The other option is to select "ECU definitions location" from the menu and then browse to the folder where the downloaded them to. You can't just download them and let RR find them; it's not that smart;).