read and understand the info in Romraider tips link below, the oft roms have special software patch for lc\ffs and its only on some roms , romraider and ecuflash defs do not reference this patch only the oft definitions reference the software patch on oft roms.

Beware some oft roms are calid adjusted and can cause problems with tactrix\ecuflash rom flashing, if you dont understand whats going on with oft roms its very easy to brick your ecu.

A02B is indeed the latest that will be compatible with the hardware (there is an F00B, but that's a 2015 IIRC).

This will need to be defined, none of the B series seem to have ever made it to the queue. Odd.

Thanks to all who have contributed to this thread. It has been very helpful.

Does anyone happen to have OVC Duty logging parameter addresses for OP2 on the B01C ROM? The only one that I've found that seems to work is 0xFFF8C20C, but I don't know which bank this is in reference to.

Thanks.

These are the ones I have:
Ram_Intake_OCV_Duty_Left FFF8C20C
Ram_Intake_OCV_Duty_Right FFF8C218
Ram_Exhaust_OCV_Duty_Left FFF8C3C8
Ram_Exhaust_OCV_Duty_Right FFF8C3D4

Thanks. Were these released somewhere else?

I don't think so...

Has anyone else encountered problems with logging after the recent firmware update on the OP2?

After plugging it in, the leds keep on running the 'rainbow cycle'. At first I thought about a misconfigured logcfg.txt, so I tried stripping it down to the bare essence without success. I tried the g-series one linked in the op as well. Still rainbow cycle.

Picked up a fresh micro sd card, put it in and still no luck.

Weird thing is, I'm still able to read out the rom and even writing to the ecu works without any problems.

The currently installed version on my Tactrix device is: 1.16.4647
Could anyone check logging capability with above mentioned revision?

PS: my logcfg.txt

mines working ok, but I have not updated in last couple of months.


ill check what version it is.


your SD is formatted FAT32 ?


do you get a logcfg.out file with the debug info in it ?

Don't have laptop connected to Tactrix for logging, it must be standalone for logging to work.


make sure you use a simple text editor it doesn't like any non-text characters in the logcfg.txt file


assume it all worked ok before update ?


I'd try bending both rows of pins inwards slightly (an old full size SD card or similar works well) to get better contact with obd socket.

For the record, there is logging with a laptop connected, but it's the standard OBD2 style logging, like what Torque does. Just want to make sure which kind of logging he's doing.

I was trying to do the OP2-standalone sd-card logging.
Both sd-cards I've tried were formatted fat32. File encoding should be ok, too.
Took tons of logs since last year, so yes, it was working before.

I'll try bending the pins since the device is basically useless without logging capabilities. :-(

A logcfg.out file is generated everytime I plug the Tactrix in, but I can't spot anything unusual out of it. Here's a copy of my last try: click

I too am having logging problems using same firmware revision as freerunner.
New tactrix cable direct from tactrix.
Successfully reading and writing ROMs.
Tried multiple logcfg.txt from this thread and those loaded with latest ecuflash. I can get a logcfg.out but no CSV files.
Attached logcfg is a minimal version that are tried immediately after a successful ROM read.
Logcfg out.txt is the logcfg.out file renamed so that I could attach here.

Tried two sdcards, reformatted at least twice. They are 8gb but this is stated as OK on the cboles development thread on openorg

Very interested in feedback on this.

Thanks in advance. (Thread has been invaluable getting the flashing side of things going).

Thanks steve

looks like a bug in tactrix firmware.


Please contact the Tactrix support guys at www.tactrix.com

If both of you guys contact tactrix it should get sorted pretty quick, they are usually very good considering their is only two guys in the company ;-)