RomRaider

I've been thrown an unwanted Mongoose Pro JLR (Jaguar - LandRover).

I was wondering whether it would work with RR logger. The JLR version has the same pins as the ISO/CAN version (I assume the ISO/CAN version is for Subarus?), so I was hoping it would work. See pic. I installed the Mongoose Pro JLR driver, and the cable is recognised correctly in Device Manager. Note that the driver doesn't show up under USB ports, it has its own category of 'J2534 passthrough devices'. However, when I connect the cable to a 2015 Subaru car with an ECU that most likely uses CAN, RR logger can't communicate, no ECU init, no ECUID etc. I tried both SSM CAN and OBD CAN protocols.

RR still shows COM6 as the COM port (which is the unused port for BT devices). There doesn't seem to be any ability to select the Mongoose Pro. So, I am wondering if I should be selecting the Mongoose somewhere in RR?

I also tried using the Mongoose Pro ISO/CAN drivers, but Windows refuses to allow the cable to use these drivers. If I uninstall the JLR drivers, the cable shows up as a generic USB serial device on COM7. If I select COM7 in RR logger and try SSM CAN or OBD CAN, I can't get communication.

I've not used a Mongoose cable before so I may not be doing something simple.

I'm using RR v0.8.2 if that is significant.

Thanks for any pointers, suggestions!

J2534 devices are automatically recognized and need no user selection like COM ports and J2534 devices have a higher priority when attempting to connect with the ECU.

You should upgrade to the latest RomRaider version. Even with this older version the cable should still be recognized, assuming the driver installed is for a 32-bit OS. If it is only for a 64-bit OS then Java can't load it. There is a 64-bit RR standalone version you can try if the cable only comes with 64-bit drivers.
You may have to look in the rr_system.log to get an idea for why it will not connect.

OBD CAN bus mode should work on any ECU. Which Subaru model are you connecting to? RR does not support logging 2015+ WRX, but STI should connect.

Ah, of course, it's so long since I installed RR on my logging machine that I forgot about the 32bit aspect. Thanks! I knew it would be something simple!

My logging machine is a 64bit OS, running 32bit Java SDK with RR v0.8.2 and a K-Line CH340 cable with WinCH drivers that don't seem to care if it's a 32bit or 64bit OS.

The MongoosePro JLR drivers do care whether 32bit/64bit. After your post, I tried installing the 32bit drivers on the above machine, but it won't let me run the *.msi file (somehow the OS knows and doesn't even allow a compatibility mode install).

So, I dug out an old 32bit OS machine, performed CPR and got it running, installed 32bit JDK, installed the latest RR and the 32bit MongoosePro JLR drivers. OBD CAN protocol now reads ECU ID and seemed to log flatline static data (haven't tried a drive yet). SSM CAN didn't seem to work. Should SSM CAN work? How does SSM CAN differ from OBD CAN? I can't recall seeing two CAN message handling routines in ECU ROMs I have reverse engineered...?

The car is a 2015 NA Impreza. Thanks again!

We can't log that ECU with SSM on CAN or k-line. I suspect it uses OBD mode 23.
CAN is CAN, but OBD-II on CAN is a different message format than SSM of CAN. There should be a check in code to detect the message format and branch to the appropriate handler.

Just so I understand the difference between SSM (via CAN) and OBD-II (via CAN)...

When RR is using SSM protocol (via CAN), does it use the 0xa8 command with the relevant offset for each parameter according to the Subaru PIDs?

And when RR is using OBD-II protocol (via CAN), does it use mode 1 (ie: 0x01 command) with the relevant industry standard OBD PID for each parameter?

And RR does not have the ability to log using UDS mode 0x23? And did Subaru change to logging via UDS mode 0x23 in ~2015? Which means RR can't log Subarus newer than ~2015?

Yes to all.