RomRaider

Windows 11 64bit, RR 1.00 experimental 64bit, tactrix 1.3U cable (2.0 doesn't work at all in RR).
06 2.5 STI.
Premise : Tactrix 2.0 works in ecuflash but don't in RR and in Evoscan.
Tactrix 1.3U works in ecuflash and evoscan, but in RR sometimes yes sometimes not.

First day I datalogged the car with RR and the 1.3 cable for one hour, doing multiple datalogs.
Second day, RR connects for few milliseconds and after that nothing.
If I change protocol and than select back the good one sometimes it works.
Attached a clean rr_system log woth only the problem, and another one when RR is working, than I tried to read DTC and it stopped working.
Whats going on here?

Oh, I forget to tell that I cannot run RR ad administrator. When I try I receive an error about javaw.exe not found.

EDIT : I modified the run.bat file with the correct path for javaw.exe ; Now, only when I start as administrator, I receive a new error "unable to access jarfile romraider.jar

RR logger works and connects at first try with a VAG KKL cable!

The problem I see in the logs it that it takes a long time to get the ECU response back, longer than the set timeout (2sec) for a read.
In this example the ECU took 2.3 secs to answer the Init request. Is it the ECU or the 1.3U driver that is slowing down the data?

Then you asked the Logger to read 16 parameters (probably to many), the request went out but the reply didn't come before the timeout.
Since the VAG-COM works, there must be something else (other than the RTS setting) with the 1.3U cable/driver that is not quite right with the switch from RXTXcomm to JSerialComm.

Could it be related to query length, does it work any better logging just a few parameters?
How many parameters can you request before it breaks the Logger?

Update, on another car, a wrx bugeye, the 1.3U cable works with no problems. Same notebook. This has no sense

Did you check the rr_system.log to compare the ECU response time to the requests?