RomRaider

The OP2 now uses a driver I wrote, which is currently in beta, that greatly improves communication performance and reliability over the Microsoft usbser.sys driver. There is a newer J2534 DLL and EcuFlash version which work fine with this driver, so the only issue is with other software which uses driver-specific methods to detect the presence of the hardware, which I think RomRaider does.

Here is a quick article I just wrote about detecting the presence of a OP2. This is more relevant now that the driver has changed and looking for COM ports won't work...

http://www.tactrix.com/index.php?option ... icle&id=70

Colby

Could you also release a driver for obsolete k-line COM based programs to be used with OP2 ?

I'm guessing learning view wont work as well with the new driver.

Anyone tried it?

Tried this with learning view and it worked but it doesn't work with Romraider logging

Maybe someone could look at getting it working under the new Romraider beta???

Just tried this tonight with the latest 1.43.3 beta and it does not work with RR or Learningview. Basically it doesn't work with any orogram expecting to find the openport 2 cable via a com port.

Is RR going to be fixed anytime soon or is the only way to log going to be with the op2's onboard logging feature?

Leslie

will this allow for faster logging?

Just tried Learning View with the OP 2.0 after installing the latest Ecuflash 1.43.3 Beta and had no problems. There was a firmware update recently, so you need to make sure you update the OP 2.0 firmware - you can do this by attempting an ECU read/write.

Heya Merch,

Glad to see you are still around mate

I just got my new op2 yesterday, and did a write yesterday evening, but was not prompted for a firmware update? Would that mean it is up to date already?

After the flash, I then went to go do some logging, but neither RR or LV would "see" the op2 passthrough device - both just had blank boxes where the com ports are usually listed?

Is there something I need to do for the op2 to be recognised via a com port, or will RR and LV see it some other way?

Leslie.


P.S. This is using the 1.43.3 beta, with the beta op2 drivers to suit. Did you uninstall your old version of ecuflash and the op2 drivers before installing for yous to work?

I have been running the beta version for a while now for the standalone looging capability. You have to click on the help tab, then licensing(control+shift+l) in ecuflash to run the firmware upgrade. Pretty sure you also have to be connected to the internet so it can download the latest firmware.

The newest firmware is included with your install of ECUFlash. Pretty sure I was not connected to the internet when it did the firmware upgrade.

What do you type in the blank text box when you press ctrl+shift+l ?

The com port selection is irrelevant for the OP 2.0 -> you are not selecting anything. I did not do any uninstall. Post up your learning view log after attempting to connect with the OP 2.0 -> it will tell us what version of the firmware you have (assuming it is able to access the device).

Nothing. ECUFlash should be checking your firmware immediately once that box pops up (you can see that in the happening in the logs) and update the firmware as necessary. You can just simply close the box.

Attempting to read/write from/to the ECU will also trigger a firmware check/update. That's how I updated mine before discovering control+shift+l.

I went through device manager and it listed it as a passthrough device, so I didn't think so - cheers for confirming.


That's the thing though, LV and RR don't even see it, nothing is writen to the logs, they just don't recognise anything as attached?

The only thing that it works with is ECUFlash. Here are the relevant lines from ECUFlash log screen:


What are the latest API, DLL and Device Firmware versions?

Leslie

I thought I'd uninstalled ECUFlash and the OP2 drivers and do a reinstall. I removed the openecu folder, and this time I also uninstalled the openport cable in device manager. I then rebooted and reinstalled ECUFlashed and plugged in the op2 cable - but this time I selected what drivers to use and pointed the driver installer to the "drivers" folder in the openecu folder.

I rebooted again for sh!ts and giggles and when rebooted I tried LV. Nothing is listed in the "ports" box, but I clicked connect anyhoo and it worked! So at least LV is working now.

However, RomRaider is still a no go. I reinstalled the latest RR release candidate, but it just doesn't work for me. Does the latest RR work with thew latest OP2 drivers? Does anyone have it working with the latest op2 drivers?

Leslie