RomRaider

Hey guys,
This is probably some simple thing I am doing wrong. I am having issues getting the logger to communicate with my 2010 usdm sti.

I am using tactrix openport 2.0
Lenovo x250 windows 10

ecuflash will pull the image off my ecu no problem. I can open that binary in the romraider editor. So I have the ecu defs working for the editor and ecuflash.

However the logger will not see my ecu. CAL ID unknown EDU ID unknown is all it says.

I have tried placing the logger defs in various folders. Went through the trouble shooting guide and reinstalled everything. Thinking maybe it had something to do with windows 10 I tried out an old laptop with win 7 and I still couldn't get it to work.

Perhaps related, learning view will not read my ecu either, I get this log message.

[06:52:32.8320823] Learning View version 0.6a
[06:52:36.5943823] PassThruOpen returned 0 and DeviceID 1
[06:52:36.5943823] PassThruReadVersion returned 0
[06:52:36.5943823] Device firmware version: 1.17.4877
[06:52:36.5943823] DLL version: 1.02.4870 Feb 3 2017 23:36:05
[06:52:36.5943823] API version: 04.04
[06:52:36.5943823] PassThruConnect returned 0 and ChannelID 3
[06:52:36.5943823] PassThruStartMsgFilter returned 0
[06:52:36.6099847] ECU Init
[06:52:36.6412762] PassThruWriteMsgs returned 0
[06:52:36.6412762] WRITE 6 bytes: 80 10 F0 01 BF 40
[06:52:36.7194096] PassThruReadMsgs returned 0
[06:52:36.7194096] READ 0 bytes
[06:52:36.9069207] PassThruReadMsgs returned 0
[06:52:36.9069207] READ 110 bytes: 80 F0 10 69 FF A2 10 11 72 12 78 60 07 F3 FA C9 8E 0B 81 FE AC 00 00 00 66 CE 54 F9 B1 E4 00 13 00 00 00 00 00 00 DC 00 00 5D 1F B0 80 F0 E6 00 FC 43 FB 00 F5 C1 86 00 00 00 01 FD F1 80 00 A1 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15
[06:52:38.2499924] ECU ID of 7212786007 not found in definitions
[06:52:39.4452304] PassThruDisconnect returned 0
[06:52:39.4452304] PassThruClose returned 0

Save the logger.xml in your personal folder. Then tell the Logger where to find it in the Settings menu.

If you still have problems send the rr_system.log
https://www.romraider.com/index.php/Rom ... HowToDebug

Guess I should post this publicly as well. I have told the logger where to find the def file. Doesn't seem to change much. Tried every communication protocol which didn't change anything either.

Here is another rr log

The log doesn't tell me much. There's no evidence that the Logger can find the OP2 connected to your computer. You'll have to repeat the log at TRACE log level to see more diagnostics.
The log shows you are set for OBD protocol, for an STI you should be using SSM - CAN.

I was trying all the protocols to see if it made a difference. Here is another with it on ssm can.

I have tried downloading the defs again, placing them in random folders. Its just strange that ecuflash can connect but rr cannot.

I assume that each time you move the def to a different folder you are updating the Logger Settings to tell it you moved the file, otherwise it will never know where to load it from? What do you expect moving the file around is supposed to do?

RR Logger requires the Openport 2 be installed properly as it reads the Registry to figure out which J2534 cable you have installed. If the Registry is empty, then no cable will not be found, the Logger then tries a COM port, it you have none logging is not possible.
EcuFlash does not consult the Registry, it knows what driver it is looking for and where to find it.
To re-install the openport2 driver and update the Registry, run:
"C:\Program Files (x86)\OpenECU\EcuFlash\drivers\openport 2.0\DPInst.exe"

This log shows there's no attempt to connect with the ECU via Openport2 or a COM port.

I suggest you shutdown RR and delete the settings file. Restart RR and re-select the logger.xml file location, your saved Log output location and Protocol again.

I don't know man I thought/hoped it was a permissions thing so I tried some different locations out. Yes I told the logger where each new location was.
I just really wanted to get some logs done so I could see what the vvt values were between my two exhaust cams. I had a suspicion even though my one OCS measured the correct resistance and actuated when I applied power that it was failing hence my p0024.
Ended up buying the btssm app which confirmed my suspicions about that OCS. Got a new one and the car's running much better.

I'll give your suggestions a go.

This might be the problem. viewtopic.php?p=162791#p162791

Interesting, so would this be a modification to a future release of romraider or something I can fix my self? I never did have any luck so I have just been using btssm for the past little while.

It's fixed already.