OP2 logging discussion

[BRZoomTX]

Originally Posted by steve99

you will need to use the B01D_B01C logcfg.txt third file from the end in this post

http://www.ft86club.com/forums/showthread.php?t=62332

their is also the B01C ram addresses if you need other addresses/parameters.

That did it. Knew it was something regarding the OFT A01C rom being based off of B01C. Just overlooked where to find this.

All values look correct now. Going to do some fixing on the config and add in other parameters. Can't thank you enough.

I'll post my final config here once I've cleaned everything up and verified the values.

[AdrianG]

I've added a link to the B01C logcfg in the main post.

[burdickjp]

Originally Posted by AdrianG

I've added a link to the B01C logcfg in the main post.

Thank you. This made it much easier to get restarted after I lost my own logcfg.

[Tor]

I know it's not engine related. But would anyone know or be able to find out if there is a RAM parameter for brake pressure?

Seeing that OFT can log brake pressure over OBD2, I assume Tactrix would be able to as well if the address was known? It would make Tactrix a real valuable tool for track data logging.

Here an example of a video with Tactrix log/Datazap overlay. It a bit of work afterward to sync it up, but the result is pretty good. After adding the gear parameter, the only thing missing would be brake pressure.

[ame="https://www.youtube.com/watch?v=hC93-8wFo9E"]https://www.youtube.com/watch?v=hC93-8wFo9E[/ame]

[ermax]

Does anyone have working addresses for B01C for these functions:
gear
brake force
steering angle
fuel level

Also, is there anyway to read the tire pressures and temps? I've never seen any talk of this or even any interest in this.

Also, is it just me or do triggers not work at all? It just seems to randomly start and stop the logs. I thought it was because the Tactrix wasn't connected firmly so I added a rubber band and it still just randomly logs. I would like to use the defogger but it isn't working. I do see the defogger in my log so I know I have the right address set for the defogger but it isn't starting or stopping when I press it. Here is a sample:

type = obd
protocolid = 6
mode23txaddrwidth = 4
mode23txlenwidth = 1
mode23rxaddrwidth = 0
mode23uds = 1
sortpids = 1
calcsampinterval = 1000

paramname = rpm
paramid = 0xFFF89570
isfloat = 1	

paramname = defogger_sw
paramid = 0xFFF8939F
databits = 8
isvisible = 1

conditionrpn = defogger_sw,1,==
action = start
conditionrpn = defogger_sw,0,==
action = stop

Sorry if these are dumb questions. I just got the car two weeks ago and the Tactrix on Wednesday.

[ermax]

As a simple work around for my inability to get the defogger to start stop logs I decided to write a simple PowerShell script that will take a log and then export individual logs containing just the samples where the defogger is turned on.

Split-Log.ps1:

param (
    [Parameter(Mandatory=$true)][string]$filename
)

$logNum = 0
$logStart = $false
$logSamples = @()

foreach ($sample in (ConvertFrom-Csv (Get-Content -Path $filename))) {
    if ($sample.defogger_sw -eq 1) {
        if($logStart -eq $false) {
            $logStart = $true
            $logNum++
            $logSamples += $sample
        } else {
            $logSamples += $sample
        }
    } elseif ($logStart -eq $true) {
        $logStart = $false
        $logSamples | Export-Csv -Path "$([IO.Path]::GetFileNameWithoutExtension($filename)).$($logNum)$([IO.Path]::GetExtension($filename))" -NoTypeInformation
        $logSamples = @()
    }
}

if ($logSamples.length) {
    Write-Host "Saving: $([IO.Path]::GetFileNameWithoutExtension($filename)).$($logNum)$([IO.Path]::GetExtension($filename))"
    $logSamples | Export-Csv -Path "$([IO.Path]::GetFileNameWithoutExtension($filename)).$($logNum)$([IO.Path]::GetExtension($filename))" -NoTypeInformation    
}

To run it you would do something like this:

Split-Log.ps1 -filename Log10.csv

It will then export logs for the the samples where the defogger is on and the files will be named Log10.1.scv, Log10.2.csv and so on. After it pulls out the relevant data you could then simply delete the original log. This is assuming you have named your defogger channel as deffoger_sw. You will have to edit the script if you are using some other name for your defogger channel. Hopefully this will help someone out there.

[ermax]

Here is another handy script I wrote. It runs though all your removable drives looking for one that contains the file logcfg.txt. Once it finds the file it create a new folder named with the date (Ex: 2017-10-06 10.11AM) and moves all the csv files off the removable drive and into this new folder. Once it's done moving the files it then launches your web browser and goes to the datazap upload page, then it launches explorer in the new dated folder so all you have to do then is drag and drop the csv file. Once it's all done it also ejects the removable drive so you are safe to unplug the USB cable from the Tactrix.

The dated folders will be created in the same folder in which you launched the script.

Here is the script:
Copy-Logs.ps1

foreach ($drive in Get-WmiObject Win32_LogicalDisk | Where-Object {$_.DriveType -eq 2}) {
    If ((Test-Path "$($drive.DeviceID)\logcfg.txt") -and (Test-Path "$($drive.DeviceID)\*.csv")) {
        $OutputPath = ".\$((Get-Date).ToString("yyyy-MM-dd hh.mmtt"))"
        New-Item -Path $OutputPath -Type Directory
        Move-Item -Path "$($drive.DeviceID)\*.csv" -Destination $OutputPath
        
        Start-Process https://datazap.me/upload-csv
        Start-Process $OutputPath
        
        $Eject = New-Object -ComObject Shell.Application
        $Eject.NameSpace(17).ParseName($drive.DeviceID).InvokeVerb("Eject")
    }
}

Start-Sleep 2

My next project will be to add something like this under the dash:
https://www.amazon.com/female-panel-...G89MRDVZTMV492

[Tor]

Originally Posted by ermax

Does anyone have working addresses for B01C for these functions:
gear
brake force
steering angle
fuel level

I'm VERY interested in brake force too. Please share if you figure it out.

These two from the other thread:

Gear:

paramname = gear
paramid = 0xFFF895DA
databits = 8

Fuel level:

paramname = FuelLev
paramid = 0xFFF8D28C
isfloat = 1

(Edit: sorry these 2 are for A01G. Hope they can help you forward anyway.)

[ermax]

Originally Posted by Tor

I'm VERY interested in brake force too. Please share if you figure it out.

These two from the other thread:

Gear:

paramname = gear
paramid = 0xFFF895DA
databits = 8

Fuel level:

paramname = FuelLev
paramid = 0xFFF8D28C
isfloat = 1

(Edit: sorry these 2 are for A01G. Hope they can help you forward anyway.)

I tried those already but they didn't work on B01C. I found this cool project on GitHub:
https://github.com/erik-smit/j2534-logger

It is a J2534 proxy dll. It emulates an OBD2 interface and then proxies the commands over to a real ODB2 interface. It logs all the commands to a text file. I tested it in Toyota Techstream and it works. So I am thinking maybe I can use the logs to discover some of the other channels. Techstream does let you log brake force so I know it's possible.

Also, I noticed that Techstream has the ability to log to a proprietary format but after creating the log there is a way to export the log to a CSV file. I had to open the CSV file and remove some stuff from the header and then it imported into datazap perfectly. So maybe you could go that route for your logging. Only problem is you end up with a laptop in the car you would have to secure really well if your tracking it. I have a tiny little netbook that fits perfectly in the glove box but you hear it shift back and forth a tad when transitioning from right to left which would be annoying on the track.

Here is a small sample recorded with Techstream and then exported to CSV:
https://datazap.me/u/ermax/log-1507310738/?log=0&data=2

I was just idled in the driveway so not very interesting.

[Tor]

Originally Posted by ermax

I tried those already but they didn't work on B01C. I found this cool project on GitHub:
https://github.com/erik-smit/j2534-logger

It is a J2534 proxy dll. It emulates an OBD2 interface and then proxies the commands over to a real ODB2 interface. It logs all the commands to a text file. I tested it in Toyota Techstream and it works. So I am thinking maybe I can use the logs to discover some of the other channels. Techstream does let you log brake force so I know it's possible.

Also, I noticed that Techstream has the ability to log to a proprietary format but after creating the log there is a way to export the log to a CSV file. I had to open the CSV file and remove some stuff from the header and then it imported into datazap perfectly. So maybe you could go that route for your logging. Only problem is you end up with a laptop in the car you would have to secure really well if your tracking it. I have a tiny little netbook that fits perfectly in the glove box but you hear it shift back and forth a tad when transitioning from right to left which would be annoying on the track.

Here is a small sample recorded with Techstream and then exported to CSV:
https://datazap.me/u/ermax/log-1507310738/?log=0&data=2

I was just idled in the driveway so not very interesting.

It would be great to be able to log with Tactrix for simplicity. Also a matter of getting it all started which would take a while with a laptop as compared to flicking a switch (switched obd2 extender cable).

The logger sounds interesting. If you have success, perhaps you could write a small how-to guide and I would do it for A01G and share it. Looking at those files in Github, I would have no idea what to do with them.