RomRaider

Running an antique XP laptop and attempting to use the logger on a 1999 Subura Legacy Outback. First I tried a blue KKL 409.1 cable, couldn't connect, assumed it was the cable's fault, so I upgraded to a true FT232RL chip cable, but haven't been able to get it to talk to the ECU, either.

Is there anything obvious that this newbie is doing wrong? Or is it normal to have difficulty connecting a particular PC/cable combo to a particular Subaru?

What COM port number is your cable?

Since my original post I tried some more tweaks:

-- uninstalled, then reinstalled the ftdi FT232RL cable in Windows. The instructions that came with the cable said set it to Com #1 in device manager, so I tried that. But oddly, with that setup, RomRaider only offered me the choice of Com #3. In any event, still no connection. So I experimented with setting the cable to Com #3, then Com #6 in device manager. Still no connection. When RomRaider offered me several Com # choices, I tried them all, but none connected.

-- I moved my ECU definitions around -- apparently I had them in the wrong location before -- and verified that RomRaider could find and load an ECU definition, though it wasn't clear which definition I was supposed to choose for my 1999 2.5. Still no connection.

Are we sure it is possible to connect RomRaider to a 1999 Subaru Legacy Outback 2.5ej manual transmission?

Thank you for taking the time to try to help.

Just let the system assign the COM port and use what is assigned, then select that in RR Logger.

That might be an SSM1 ECU and not supported by RomRaider.

I got busy doing other things so I apologize for the slow reply.

Since my last post, I temporarily swapped Subarus with my daughter and am now wanting to use RomRaider logger to troubleshoot a P0420 code on her 2010 Forester with normally aspirated 2.5 MT. But I still get the dreaded cannot connect to ECU error.

RomRaider automatically selects COM1 but also offers 3 & 6. I tried them all to no avail.

Any further suggestions?

Update: my main problem seemed to be not pointing the ECU editor to the ecu_def.xml file.

After I pointed the ECU editor / Definitions Manager to my ecu_def.xml file, I was able to connect to the ECU with the logger protocol set to SSM/Kline and COM set to COM6. It did not connect in DS2/Kline. I'm not sure which protocol is recommended other than to say SSM/Kline seems to be working at the moment.