Romraider is used with Windows or Linux. Requires an adapter cable, e.g. VAG-COM KKL 409.1 -- relatively inexpensive and available on eBay and Amazon. (Look for cables with the FTDI 232 chip -- seems to work better than others.)

It will provide many, if not all, of the parameters available to dealer's using the Subaru Select Monitor. See attached list.

There have been some issues using it with early 2nd Gen Outbacks (and equiv Legacys), but probably worth trying.

Website: https://romraider.com/ There's also a Romraider Forum on that site.

Not all year/engine/ECU combinations are listed on the site, but that will usually only affect a few parameters.

Romraider uses the Subaru ssm data stream; it's not the same as what OBD2 dongles would access.

 

I was at the site and saw the vehicles covered, which was why I came here to ask, and hopping that you would see my post. I almost joined the forum just to ask my question, but saw some RomRaider users on this forum. I have a laptop (Windows) solely dedicated for my Volvo scanner, could use it for this also. I'll get the cable and go for it.

Thank you so much for the info, well appreciated!

 

Definitions for an H6 second generation Outback were not even in existence until I went to supercharge mine.

I do have a slightly modified ECU Flash, (don't tell Mike), and I have the definitions that were built for my car. What you would need to do is after you download ROM Raider along with all of the definition files and have it set up on your computer, is hook up to the car and open ROM Raiderr and see if there's a calibration ID or ECU ID on the bottom of the ROM Raider window. You would connect to your car using 02 to 04 WRX. The H6 ECM is similar to the WRX and STI.

It is doubtful that there are definitions built for your car unless the definitions for your car will match mine. I have the definitions for my car on my laptop, and that is at the shop at this time, so I will have to attach the file to this thread tomorrow morning. I do believe it's posted on ROM Raiderr somewhere though, so let me look.

 

When I get the cable and ready to roll, I WILL definitely come back to you. I'm not that knowledgeable about super technical part of cars.

Thanks so much!

 

SubaruDefs/ECUFlash/subaru standard/Outback 3.0R/D6JM000B.xml at 36a7c99c224e8eb50c1a2140f6e7b6e915a93c9a · TD-D/SubaruDefs

Subaru ECU Definitions. Contribute to TD-D/SubaruDefs development by creating an account on GitHub.

github.com

You may need to "copy/paste" the definitions onto a "notepad" opened definitions list for the WRX.

If it doesn't work, I'll give you a link to a complete file tomorrow.

 

The Tactrix Openport 2 is far more expensive. (Tactrix Openport 2.0 ) Not sure what that listing is selling. In any event, unless you're looking to modify the programming in the ECU, the capabilities of the Openport are far more than needed to run the Romraider Logger.

When I first planned to use Romraider, there was no ECU-specific definition file for my engine, and, of course, the car was not listed in the coverage. Nevertheless, Romraider still worked, with only a few missing parameters, and others actually displayed but with different "titles/names".

It's my understanding that when the Logger and ECU definition files are downloaded and set up properly in the program, Romraider's Logger function (separate from the ECU Editor) will use those definitions (basically computer "addresses" for each parameter) to find any corresponding parameters in the ECU to which it's connected. If there's data at that address it will display it, using the "name" for that data series that it does have from the existing definition files.

Consequently, even if your particular engine isn't listed, I think it's likely there would still be quite good coverage of the available parameters. ( NOTE: This applies to the Logger function, which is only to display live data. The ECU Editor will not work without a ECU-specific definition file.)

Moreover, although the downloadable definition files might not list your vehicle, or even any H6 from that period, there might now be an H6 ECU definition in the Forum. Once Romraider connects to the ECU, it will display the ECU ID in the band at the bottom of the Logger page. That ECU ID can be used to search the Romraider Forum, to see if it has been defined separately. If it has, then there will likely be a downloadable ECU definition file. When that is installed in the your definition file folder, Romraider will then use the definitions from it, as above, to seek out parameters. This usually adds a few, including some "extended" parameters that even the Subaru Select Monitor does not have, and corrects any that were "misnamed" when using other definition files as proxies. Alternatively, if the ECU ID search doesn't lead to a specific definition file, the forum can be searched for similar ones, i.e., 2002 H6, and perhaps other years of that generation.

(Note: In the Forum, ECU and Logger definition files can be found for Romraider and for ECUFlash. It's my understanding ECUFlash is a different, although somewhat-related program, and it's definition files will not work.)

 

The Tactrix Openport 2 is far more expensive. (Tactrix Openport 2.0 ) Not sure what that listing is selling. In any event, unless you're looking to modify the programming in the ECU, the capabilities of the Openport are far more than needed to run the Romraider Logger.

When I first planned to use Romraider, there was no ECU-specific definition file for my engine, and, of course, the car was not listed in the coverage. Nevertheless, Romraider still worked, with only a few missing parameters, and others actually displayed but with different "titles/names".

It's my understanding that when the Logger and ECU definition files are downloaded and set up properly in the program, Romraider's Logger function (separate from the ECU Editor) will use those definitions (basically computer "addresses" for each parameter) to find any corresponding parameters in the ECU to which it's connected. If there's data at that address it will display it, using the "name" for that data series that it does have from the existing definition files.

Consequently, even if your particular engine isn't listed, I think it's likely there would still be quite good coverage of the available parameters. ( NOTE: This applies to the Logger function, which is only to display live data. The ECU Editor will not work without a ECU-specific definition file.)

Moreover, although the downloadable definition files might not list your vehicle, or even any H6 from that period, there might now be an H6 ECU definition in the Forum. Once Romraider connects to the ECU, it will display the ECU ID in the band at the bottom of the Logger page. That ECU ID can be used to search the Romraider Forum, to see if it has been defined separately. If it has, then there will likely be a downloadable ECU definition file. When that is installed in the your definition file folder, Romraider will then use the definitions from it, as above, to seek out parameters. This usually adds a few, including some "extended" parameters that even the Subaru Select Monitor does not have, and corrects any that were "misnamed" when using other definition files as proxies. Alternatively, if the ECU ID search doesn't lead to a specific definition file, the forum can be searched for similar ones, i.e., 2002 H6, and perhaps other years of that generation.

(Note: In the Forum, ECU and Logger definition files can be found for Romraider and for ECUFlash. It's my understanding ECUFlash is a different, although somewhat-related program, and it's definition files will not work.)

I had to re-read this post twice, and on the third time, just scammed through it, to get all your knowledge in. That's really extensive. My goal for any of my cars is not to modify and parameters in the car; don't want to take chances and mess it up. My goal for a scanner is to troubleshoot any issue that might come up, and find a solution for the repairs. When it comes to cars, am not as extensively knowledgeable as you all here. Even for my Volvos which I have the specific Volvo only scanner, I set my limits on how far I go with it.

On that note, about the cable I saw on Amazon. I also saw the one from the manufacturer for the $169. What would be the difference between the Amazon's and the Tactrix's?

With the RomRaider, what car connector would do me good. I need more than just live data. I get that from my $10 ELM327 dongle and it's app, and still get a lot from it for the Subaru, with it's free app. Maybe am off point, but, I would need some tool that would give me info on the fuel pressure, and similar. I really would like to use RomRaider.

Cheers.

 

I never managed to get ECU Flash nor RomRaider working quite right on my '03 h6. I think some of these need the WRX jumper to read/write, but never found a sure answer. Mine had a fire under the dash and I haven't messed with it much since then.

 

You have to connect the green diag to read the ROM, and you have to have the jumper on the white connector like a WRX, along with the green connected, to write a ROM.

Here's the H6 definitions I use. It ahs worked on 2 Beans in the past.

<rom>
<romid>
<xmlid>D6JM000B</xmlid>
<internalidaddress>200</internalidaddress>
<internalidstring>D6JM000B</internalidstring>
<make>Subaru</make>
<market>USDM</market>
<model>Outback</model>
<submodel>VDC</submodel>
<transmission>Auto</transmission>
<year>2001</year>
<flashmethod>wrx02</flashmethod>
<memmodel>68HC16Y5</memmodel>
</romid>
<include>16BITBASE</include>
<notes>2014/05/22 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014. </notes>
<table name="Manifold Pressure Sensor High Input (CEL)" address="2b25c"> </table>
<table name="Manifold Pressure Sensor CEL Delay (High Input)" address="2b25e"> </table>
<table name="Manifold Pressure Sensor Low Input (CEL)" address="2b25f"> </table>
<table name="Manifold Pressure Sensor CEL Delay (Low Input)" address="2b261"> </table>
<table name="Primary Open Loop Fueling A" address="2912a">
<table name="Engine Load" address="29112" elements="11"/>
<table name="Engine Speed" address="290e7" elements="21"/>
</table>
<table name="Primary Open Loop Fueling B" address="29342">
<table name="Engine Load" address="2932a" elements="11"/>
<table name="Engine Speed" address="292ff" elements="21"/>
</table>
<table name="Minimum Active Primary Open Loop Enrichment" address="29213"> </table>
<table name="Minimum Primary Fueling CL to OL Intermediate Enrich" address="29217"> </table>
<table name="Maximum Primary Fueling CL to OL Intermediate Steps" address="2921d"> </table>
<table name="Front Oxygen Sensor Scaling" address="282e0">
<table name="Front Oxygen Sensor" address="282c4"/>
</table>
<table name="CL to OL Delay" address="29232"> </table>
<table name="CL to OL Transition with Delay Throttle Hysteresis" address="2921f"> </table>
<table name="CL to OL Transition with Delay BPW Hysteresis_" address="29220"> </table>
<table name="CL Delay Maximum Engine Speed" address="29224"> </table>
<table name="CL Delay Minimum (ECT)" address="29222"> </table>
<table name="CL Delay Maximum (Throttle) (Low Atm. Pressure)(AT)" address="2922a"> </table>
<table name="CL Delay Maximum (Throttle) (High Atm. Pressure)(AT)" address="29228"> </table>
<table name="Injector Latency" address="28740"> </table>
<table name="Base Timing A_" address="297d8">
<table name="Manifold Pressure" address="297c2" elements="10" scaling="g/rev"/>
<table name="Engine Speed" address="2979b" elements="19"/>
</table>
<table name="Base Timing B_" address="298d3">
<table name="Manifold Pressure" address="298bd" elements="10" scaling="g/rev"/>
<table name="Engine Speed" address="29896" elements="19"/>
</table>
<table name="Base Timing A" address="299ce">
<table name="Engine Load" address="299b8" elements="10"/>
<table name="Engine Speed" address="29991" elements="19"/>
</table>
<table name="Base Timing B" address="29ac9">
<table name="Engine Load" address="29ab3" elements="10"/>
<table name="Engine Speed" address="29a8c" elements="19"/>
</table>
<table name="Base Timing Idle (Neutral)" address="29770"> </table>
<table name="Base Timing Idle (In-Gear)(Above Speed Threshold)" address="29752"> </table>
<table name="Base Timing Idle (In-Gear)(Below Speed Threshold)" address="29761"> </table>
<table name="Base Timing Idle Vehicle Speed Threshold" address="29749"> </table>
<table name="Knock Correction Advance Max" address="29edf">
<table name="Engine Load" address="29ed3" elements="5"/>
<table name="Engine Speed" address="29ea8" elements="21"/>
</table>
<table name="Intake Temp Sensor Scaling" address="281fc"> </table>
<table name="Coolant Temp Sensor Scaling" address="281b8"> </table>
<table name="Idle Speed Target A (AT)" address="2a202"> </table>
<table name="Idle Speed Target B (AT)" address="2a228"> </table>
<table name="Idle Speed Target C (AT)" address="2a24e"> </table>
<table name="Idle Speed Target D (AT)" address="2a274"> </table>
<table name="Min Idle Speed A/C (AT)" address="2a296"> </table>
<table name="Min Idle Speed Startup (AT)" address="2a45b"> </table>
<table name="Min Idle Speed High Electrical Load (AT)" address="2a457"> </table>
<table name="Front Oxygen Sensor 2 Scaling" address="28316" scaling="Air/FuelRatio">
<table name="Front Oxygen Sensor" address="282fa"/>
</table>
</rom>

 

You have to connect the green diag to read the ROM, and you have to have the jumper on the white connector like a WRX, along with the green connected, to write a ROM.

If all that's needed is to log data using Romraider Logger, rather than read or write to the ROM (uses Romraider Editor), do those requirements apply?

Then again, as far as I know, the Vag-Com cable cannot be used to read/write the ROM.

 

The Vag-COM you found is the correct cable. Vag is VW Auto Group. You don't need any software with it, so if there's a disc or data card, chunk it.

 

So just use this cable with RomRaider, right?

Just checked your temperature today in Austin, Google says 105F? Daaaaaaam!
With such temperature, my sweat will be sweating also. The other day up here in Anchorage, Alaska, we had 70F and I thought it was really hot.

 

Okay, some of the sellers of the vag-com cables sell a software disk for communicating with Volkswagen Auto Group cars. That's the software I'm talking about. You need ROM Raider to read data, and the cable as an interface.

Now on reading and writing a ROM, some cars you can use that Vag-COM cable. I can you use it on both of the Bajas. We're going to find out here in another week or so whether it's going to work on my 01 VDC. I still have the Tactrix cable, but the VAG-COM cable is a little longer for using with the laptop.

 

ROM Raider will record data that is saved in csv format which allows closer examination of the data. You can also put the file on a server like Google and link it here for us to look it over and assist.

FreSSM does not record data, so you have to watch the data on the screen as it happens.

Both will read and clear fault codes on the ECM.

 

ROM Raider will record data that is saved in csv format which allows closer examination of the data. You can also put the file on a server like Google and link it here for us to look it over and assist.

Thank you so much !!!
I really appreciate your help.
Cheers !

 

@Oka

Another advantage of Romraider (RR) is that the recording of data can be turned on and off by simply pressing a button, namely, the Rear Defogger switch on your dashboard. (No "distracted driving" necessary!) Each time recording is stopped, the completed .csv file will be saved to a file you choose, with the date and time as part of its title. This facilitates identifying each log with a particular test run. (The files can be renamed afterwards to make them more descriptive.)

And, incidentally, in addition to text, RR can also display live data gauges of different shapes and sizes and moving graphs. It makes viewing live data easier, if that's desired.

 

@Oka

Another advantage of Romraider (RR) is that the recording of data can be turned on and off by simply pressing a button, namely, the Rear Defogger switch on your dashboard. (No "distracted driving" necessary!) Each time recording is stopped, the completed .csv file will be saved to a file you choose, with the date and time as part of its title. This facilitates identifying each log with a particular test run. (The files can be renamed afterwards to make them more descriptive.)

And, incidentally, in addition to text, RR can also display live data gauges of different shapes and sizes and moving graphs. It makes viewing live data easier, if that's desired.

Wow, that's really awesome.
Thanks a bunch !
Cheers.

 

Yes. I run it using Windows 10 Home.

 

Does anybody have a tune for an 02 h6 that comes with some pops and bangs? Really interested in making my car fast but I know there’s not much wiggle room but some pops and bangs would really make driving the car a blast.

 

pops and bangs: like a turbo WRX crackling backfire ? (2 stepping,...etc ?)

I forgot what XRT use to put out with a basic tune for a 2002 H6. (but Ed from Barbados was doing it a long time)

Contact - Xtreme Racing Tuning

Xtreme Racing Tuning Barbados, Caribbean Info@xtremeracingtuning.com Telegram:- https://t.me/XtremeracingtuningSupport Whatsapp:- https://chat.whatsapp.com/FEn8AnNUPxP91cKZe1zUSy

xtremeracingtuning.com