RomRaider

Hi, Wondered if anyone can help with this frustrating problem thats been going on for 6months now..

I've got a 2001 uk, subaru outback, 2.5ltr and need to find what error code is causing the engine warning light to come on... Ive tried the Tari racing s/w and Romraider and both connect ok and display the realtime engine info correctly, but can the RomRaider s/w display error codes, as Tari racing s/w does not support this....?

Any help would be most appreciated as the local subaru garage charges £50 for this service??

Thanks

no, romraider will not read trouble codes -> only disable them as part of your tune.

This question comes up a lot, so I have added it to the FAQ.

http://www.romraider.com/Documentation/ ... erFAQ#toc5

dude, that is already in the FAQ:
http://www.romraider.com/Documentation/ ... rFAQ#toc81

Well, the next time somebody asks, I'm going to add it again.

Somewhere near the middle next time.

The one thing I've learned is that it doesn't matter where you put it in the FAQ/sticky/whatever. You could put in on the first line in gigantic bold flashing text and someone will still ask the same question. I don't know how many times questions that are already in the first section of the FAQ are consistently asked again and again.

I think part of the problem is that the FAQ is huge. It would preempt more frequently-asked-questions in the forums if it really consisted only of frequently asked questions, with the rest moved into a "documentation" page.

The number of people who bother to check the FAQ is small enough in the first place, and I'm sure we lose more through sheer intimidation when they see how big it is.

How about hosting a wiki, incorporating faq stuff in addition to technical details and howtos (i.e. the stuff that's now in stickies)? If it's an extensive resource, people might be more likely to look there first. I know there are more important things to think about right now, with the imminent release of the new tactrix cable and whatnot, but it might be a good idea for the long run.

I have started working on a new version off-site. I'll see if I can edit it a bit - I know some of the questions go into more detail than is necessary.

All of those links on the left side of the screen go to wiki pages.

Lol... I noticed that just after posting. The articles, too. Maybe rename the faq "Super Resource" or something.

So, can anybody help me with reading error codes, or just recommend some apps out there that might do it? Surely there must be something out there?

Any help would be most appreciated..........

You really should actually read the FAQ. Directly underneath your first question, it states that ecuExplorer can read CEL codes.

ok found it FAQ 10.2, but cant see any mention on ecuExplorerer...

Ive already been in touch with one of the designers for ecuExplorerer, Ive tried it already and it seems it will not read error codes...

Here is is his reply:-

"Its exactly that - frustrating. Subaru seem to move things around in the ECU for each model/year and that makes it extremely difficult to get the software right. I never got around to further developing/completing the OBD error code stuff. Unfortunately there is nobody now doing active development on it now either.

Have you tried alternate apps that are active in development like ROMRaider (http://www.romraider.com). They may prove better for that purpose."

Anything else I could try????

Thanks

Just out of interest, the comment on ecuExplorer was from Calvin Cestari...

Thanks