Need a little help with Tactrix flash and Romraider Logger...

[fatboydean]

Hi I use ECUFlash to pull the stock rom and my calid is:ZA1JF40C

When I try to load OFT OTS Rom with the same calid I notice a lot of data in that rom was out of place, that is using the stock ECU Def. I attached a snapshot showing a simple parameter which is idle ctrl. The left one is stock rom using stock def (which I got from Github), the right side one is the OFT rom I got from their website.

My question is: Can I ignore the data out of place situation and just go ahead and flash the ECU using stock def? I am scared that it will 'brick' the car

Attached are my stock rom, the OFT rom and the stock def I use.

As for Romraider logger, I was not able connect to ECU at all, it shows a message: 'Sending ECU init' and "Unable to send ECU init" and as a result I could not see any real time data. I tried both with engine on and switch on. Note that my ECUFlash can read which means the cable is ok.

Also attached are my logger def, do not know if that will effect connection.

Any input will be highly appreciated!!! Thanks for viewing!

[steve99]

This is because many OFT tunes have the internal calibration id of the roms altered to suit the OFT system


Failure to understand these alterarions can result in a bricked ecu .


The oft F40C USA rom is actually based on an A01G European rom


The definitions your using for ecuflash get fooled by these alterarions , this also happens in romraider


while link below is for romraider rom editor its same deal for ecuflash



https://www.ft86club.com/forums/showthread.php?t=79152




romraider logger does not work with brz 86 its never been set up

[fatboydean]

thanks Steve for your reply. I PMed you!

[Flukester]

Hello @fatboydean .

[TL/DR: Log with the Tactrix dongle (no laptop) using a 1GB or 2GB micro-SD card. Find the proper logcfg.txt config file for your Calibration ID and save it on the SD card. Done.]

Apologies for the length of this message, hopefully there is some interesting information for you here.

I'm not sure if you're aware but you can do "offline" logging with the Tactrix OpenPort 2.0 dongle. By offline, I mean without a laptop connected while driving.

This is done with a micro-SD card that can be inserted into the Tactrix "dongle", without the USB cable being connected. The "dongle" gets powered directly by the car through the OBD-II port. Simply connect the dongle on the diag connector under the steering wheel and go.

When choosing an SD card, you don't need a large card since the logs will not be excessively large. I am not sure what the biggest supported capacity is, but I use a 2GB card myself. I have found a lot of posts through various forums indicating that 1GB and 2GB cards work. I am not sure if larger cards would work or not, I have not tried. Buying such a small card (2GB) is not that easy nowadays with most cards being bigger than this.

I'm using a Transcend 2GB micro-SD card that I bought on Amazon.ca. Send me a private message if you want the link to the exact product I bought.

Format the card in FAT32 (not NTFS).

You then create a file called "logcfg.txt" which you place directly in the root directory of the micro SD card. The contents of the logcfg.txt will dictate what parameters are logged (from what memory address to pull the data), what mathematical function to run (scaling, etc), etc.

The RAM addresses are different for each ROM (Calibration ID) so you need to use the correct file. Some ROMs have been reverse-engineered more than others so not all parameters are available for each ROM. Check Steve's threads for more information.

The logs are created in CSV format and are named sequentially (log0001.csv, log0002.csv, etc) and can easily be analyzed using Excel, datazap.me or other log analysis solutions. Datazap is great to share logs online but is limited to 3MB logs. For larger logs, I use MegalogViewer HD myself as it can handle large logs. You can cut long logs into smaller files to stay within the 3MB limit of Datazap. Just make sure you keep the very first line with the column names.

If you don't have a micro-SD adapter to read your card (either USB or micro-SD to SD), you can disconnect the dongle from the car and connect it to your computer using the USB cable. The micro-SD card will appear as a drive on your computer.

Just as an example, my current logging configuration (for a different Calibration ID than you unfortunately) gives me 25 parameters, in addition to "sample" (sequential number) and "time" for a total of 27 columns in my CSV, most of which are "floats". The logging interval in my case is every 75ms based on the number of parameters I'm logging.

When the logging starts, the system creates another file on the SD card, named "logcfg.out" which includes the details of the parameters being logged and a summary at the end, which includes the interval calculations.

With only 25 parameters, my log files do not grow too quickly. I did a log over 2 hours long recently, about 112k records (lines) and the logfile is only 20MB. This is why I was saying that a 1GB or 2GB SD card is more than enough.. I kinda wish I had a few more parameters/addresses known for my ROM but so far what I have seems sufficient. (IAM, MAF_V, MAF, MAP, IAT, ECT, OilTemp, Throttle, Load, RPM, TotTiming, AFR, AFR_command, KCA, FBKC, FLKC, STFT, LTFT and a few others which I log but don't really know what to do with).

Hope that helps,
Fluke