Page 1 of 1

2008 3.0R-B ROM definition

PostPosted: Sat Mar 17, 2012 10:32 pm
by Jonty
I was chasing down some error codes on the car so downloaded Learning View and RomRaider etc. When I tried to connect to the ECU I was a bit surprised to find that the ECU wasn't supported :( I would have thought a few tuners would have been dabbling with the 3.0R-B's by now?

FYI - The ECU ID is 4B5A347007. From a 2008 3.0R-B auto (ADM).

I'll start the search on RomRaider.com and openecu.org and see if I can track down the definintion and get support added. Just thought I'd post here in case anyone else with this type of ECU has had any success before.

Re: 2008 3.0R-B ROM definition

PostPosted: Thu Mar 29, 2012 1:45 pm
by BJ
I have a 2006 3.0R and when I connect it always says "definition not found" but you don't need it. You can use learning view and get logs with romraider without needing the definition.

Re: 2008 3.0R-B ROM definition

PostPosted: Thu Mar 29, 2012 3:38 pm
by Jonty
I'll have another go, but I was using Learning View to try and get the error codes in the first place. As soon as it gave me the "definition not found" error in Learning View, I couldn't do anything else or see any data.

Do you get the same error using Leaning View and it still lets you continue on? Which version?

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Mar 30, 2012 8:21 am
by BJ
Yes, Learning View should show you the error codes. I only get the "definition not found" error with romraider, not with learning view. Maybe yours is different because it's a later model, I don't know. My learning view is 0.6.0.0.

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Mar 30, 2012 8:29 am
by Jonty
Ahh OK. That would explain it then :) I'd say your ROM ID is different to mine and yours is supported by Leaning View. Mine definitely isn't and I can't do anything inside the program once connected. I've asked for my ROM to be added to the supported list, so fingers crossed!

I tried again last night and couldn't see how to pull error codes with Romraider? I was able to go into the logger and log some parameters, so that's a start. It's useless if I wanted to flash the ECU though as there is no rom definition for my ECU yet, so I can't open it in ECUFlash :( It's an uphill battle!

Maybe I should have got a GT :lol:

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Mar 30, 2012 9:09 am
by BJ
It's sort of tricky getting ECUFlash to connect. You have to turn the ignition on a second before you try to connect, if you don't get it right it won't connect. Again, I can load ROMs without having the definition, but it could take a few tries to get it to connect.

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Mar 30, 2012 10:32 am
by Jonty
Yes but I don't really want to upload a rom that I can't see and edit in ECUFlash first. Or are you saying you can edit it in Romraider and then upload it in ECUFlash? I haven't tried that yet. I downloaded my ROM off the ECU via ECU flash, but couldn't do much with it due to a lack of a definition file.

I'm a bit new to the Suby open ECU stuff sorry - I've been tuning my Evo for a couple of years now with EvoScan and ECUFlash, but I just need to work out the little differences for dabbling with the Subaru ECU. Looks like I've picked a model (3.0R-B) with a serious lack of ECU support! :)

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Mar 30, 2012 11:25 am
by BJ
Yes that's all you can do. I wouldn't recommend changing anything unless you are a tuning expert. It's better to get someone who knows what they are doing to do the tuning, like Edward from XRT.

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Mar 30, 2012 11:48 am
by Jonty
No I won't be changing anything just yet. As I said, I was just trying to track down an error code when this first started, but it would be good to know I can flash tune it if required.

I've seen XRT's threads, so might have a chat when the time comes to extract some more power out of this thing. Need to sort out the exhaust first :)

Re: 2008 3.0R-B ROM definition

PostPosted: Tue Sep 25, 2012 10:18 pm
by Jonty
This ROM has now been defined by one of the guys on RomRaider :D

So if you have this ECU ID, it can now be flash tuned. I've also requested support for this ECU in the upcoming release of Learning View, so fingers crossed it's included.

Here's the link:
http://www.romraider.com/forum/viewtopic.php?f=34&t=8818

Re: 2008 3.0R-B ROM definition

PostPosted: Wed Sep 26, 2012 12:18 am
by telemekas
For the DTC you can use SSM (Subaru Select Monitor) protocol.
http://developer.berlios.de/projects/freessm/

Re: 2008 3.0R-B ROM definition

PostPosted: Thu Oct 04, 2012 11:06 pm
by Jonty
Thanks telemekas, but SSM doesn't appear to work either. Whenever I try and connect, SSM throws an error saying 'invalid or no response from ECU'.

I'd say it has the same problem as Learning View - my ECU ID is simply not supported :(

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Oct 05, 2012 12:05 am
by KiDo_Tuning
Jonty wrote:This ROM has now been defined by one of the guys on RomRaider :D

So if you have this ECU ID, it can now be flash tuned. I've also requested support for this ECU in the upcoming release of Learning View, so fingers crossed it's included.

Here's the link:
http://www.romraider.com/forum/viewtopic.php?f=34&t=8818


Sorry I did not get a chnace to post up mine. Orens one included a lot more tables though

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Oct 05, 2012 12:39 am
by telemekas
Jonty wrote:Thanks telemekas, but SSM doesn't appear to work either. Whenever I try and connect, SSM throws an error saying 'invalid or no response from ECU'.

I'd say it has the same problem as Learning View - my ECU ID is simply not supported :(

What cable are you using?
SSM protocol will not work with Tactrix cable.
The software works with all ISO-9141-2-/ISO-14230-1-compliant (K/L- and KK/L-) interfaces,

Re: 2008 3.0R-B ROM definition

PostPosted: Fri Oct 05, 2012 9:57 am
by Jonty
telemekas wrote:What cable are you using?
SSM protocol will not work with Tactrix cable.
The software works with all ISO-9141-2-/ISO-14230-1-compliant (K/L- and KK/L-) interfaces,


OK that would be it then :) I'm using a Tactrix 2.0 cable.

Thanks!