(Update - Make sure you read a bit further than the first post. The next few posts, as well as the rest of this long thread, has valuable information about more recent versions, etc)

How To:
Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)

Parts Needed:
- Tactrix Open Port 2.0 Adapter
- microSD Card
- Computer with Interwebs
- mode23 Enabled ROM loaded onto your car
(http://www.evoxforums.com/forums/showthread.php?t=22140)
- (Optional but important- Wideband O2 Sensor. Innovate LC-1 can plug in directly, all others, such as AEM UEGO, require hooking up by a specific method
http://www.evoxforums.com/forums/showthread.php?t=18919)

Tools Required:
- None, actually. It's that cool.

Recommended Number of People:
- 1 is good, but having someone cooking food simultaneously is ideal.

Difficulty:
- 1 out of 10 if you can get through my wordy How To ;)

Time to Complete:
- Minutes to have it running, but you may spend some time adjusting your parameters slightly.

Thanks for Finding Things:
Tephra
(and of course, Colby for the Open Port Adapter and work on the Standalone Logger)

Step by Step Instructions:

0 - NOTE: This is for the BETA release of the standalone logger. It takes some playing with text rather than a shiny GUI. It's difficult to predict the future, but I imagine that this logging ability will be simplified and made much nicer to setup.

1 - Download the required "beta" ECUFlash version. The most updated beta version will be in the first post of this
http://forums.openecu.org/viewtopic.php?f=57&t=4319,
but the direct link to the version I used when this was written was here
http://mail.tactrix.com/ecuflash/ecuflash_1422720_win_beta.exe

2 - Install it, accepting any agreements and driver installations that pop up.

3 - Plug your Open Port cable into a USB port, start up ECUFlash.

4 - Run the Help -> Licensing to force a firmware update of your adapter. Once completed, you can close every open window.

5 - Unplug your cable and insert the microSD card into the slot on the adapter.

http://i606.photobucket.com/albums/tt142/xprimnt/AFR%20HowTo/Cable.jpg

6 - Plug the cable back in. With the microSD card installed, it acts as a card reader, so the microSD card will show up in My Computer (or Finder for us OSX users). Ensure the card is formatted as FAT16 or FAT32. Open up the empty drive. If it's not empty, make it so.

From this point on, the principle is simple: the adapter will take parameters indicated by a "logcfg.txt" file located at the root of the microSD and will request those parameters from the ECU. The resulting responses are recorded to the SD card.

Save the attached logcfg.txt (http://www.evoxforums.com/forums/attachment.php?attachmentid=10542&stc=1&d=1263940391) file to use as a template and make changes as you see fit. I have commented out EVERY parameter except RPM, so remove the ";"'s in front of the ones you want to log. I'm hoping that people will contribute parameters in the discussion of this "How To" thread, so check there if you're missing anything. While I have some parameters, I can only confirm that they work for my car - USDM 526800xx series. I'm pretty sure all of the ones I use are also good for USDM MRs as well. However, if you're on a different ROM series, it's very simple to figure out what you would put in the logcfg if you have EvoScan working well. Find the parameter you'd like to log, right click the item and look at it's properties. The address, evaluation and ResponseBytes are the important pieces of information.

7 - Parameters
For North American people, the attached logcfg.txt will likely be more than enough. However, if the addresses for USDM Mode 23 don't work with your car, you may need to do some work. In addition, as more address come to light, you may wish to add them.

The address can be copied over to a paramid (if it starts with "23"xxxxxxx, use 0x instead of 23 - For Example, 23808a07 becomes 0x808a07).

The evaluation needs to be formatted into a "scalingrpn". Look at a few examples (check the attached logcfg) to get the hang of it, but the basic idea is to simplify as much as possible first, then put it in. Just ask if you need help!

If ResponseBytes is 1, nothing needs to be done.
For Example:

paramname=Timing
paramid=0x808a07
scalingrpn=x,20,-


If ResponseBytes is 2, add "databits=16".
For Example:

paramname=RPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*


8 - Triggers

Now the fun stuff. This section allows you to specify WHEN you want the adapter to start logging. Unfortunately, I only have confirmed USDM ROM triggers, but if you have something that doesn't work, get in touch with me and I'll try to find the address. Obviously, choose one method and put it in your logcfg.

Log All the Time
If nothing is specified (or everything is commented out), the logging will start when the car is turned on, and stop when the car is off. This is great for track days, finding out your LTFTs, or just because you don't want to fiddle with buttons. This is also good because it doesn't require any additional logged parameters, so this is what to use if you want the fastest of fast logging.

Log When Cruise Control is On
Whenever your "Cruise" light is on, the adapter is logging. This is definitely my choice, although it technically does require a logging slot to record the status of the Cruise flag. I have to give Tephra a HUGE thanks for digging through and finding this address, all I did was test a couple things out.

Insert these into your logcfg.txt (they're already in the attached one, just uncomment the needed fields). If you find the response slow, remove the "priority=2" line.


paramname=CruiseLight
paramid= 0x8045C5
databits=1
offsetbits=5
isvisible=0
priority=2

conditionrpn = CruiseLight,1,==
action = start

conditionrpn = CruiseLight,0,==
action = stop


Log When Cruise Control is Held Down
The adapter is only logging as you are holding down the Cruise On/Off switch. It is independent of the "Cruise Light", just keep holding it down. Again, if you find the response slow, remove the "priority=2" line.

Insert these into your logcfg.txt

paramname=CruiseMomentary
paramid= 0x80AB1E
databits=1
offsetbits=1
isvisible=0
priority=2

conditionrpn = CruiseMomentary,1,==
action = start

conditionrpn = CruiseMomentary,0,==
action = stop


9 - AFR Logging

Innovate LC-1
Disclaimer - I don't have one, so I haven't tested it yet.

- Make sure that "paramname = inno.afr" is not commented at the bottom of the logcfg

- Plug in your 3/32" cable into the jack of the Open Port adapter and connect the other end to your wideband connector.

- If everything is calibrated properly, you should have AFRs logged!

AFR via Rear O2 ADC

- If you've followed my other guide on how to set this up (http://www.evoxforums.com/forums/showthread.php?t=18919), you can use this:

My Specific AEM UEGO Setup

paramname=RearO2AFR
paramid=0x80934e
databits=16
scalingrpn=x,0.008671875,*,10,+


You WILL HAVE TO CHANGE THE SCALING to match your specific setup. Even between AEM UEGO gauges, the Eval in EvoScan will be different. Mine is "2*(4.44*x/1024)+10", which simplified to the above scaling. Since you will have a different ground voltage, you need to calibrate it yourself as I mentioned in the other How To. Don't assume my calculation will work, it's only there as an example. Had I known that this logger was going to be released, I would have used an LC-1 for my car :).

10 - Done! Plug in the adapter to your car. Make sure it blinks properly during logging: Red and Green often (Request and Response, looks orange/yellow) with the occasional blue (write to card). If it is doing the multicolour fade thing, something is wrong with your cfg file.

REMEMBER THIS - If you leave the adapter plugged in, it continues to use power even when not logging. Unplug it when you're done to avoid draining the battery.

11 - To get your logged parameters, just plug in the adapter (with the microSD card plugged in) to your computer. I suppose you could use a card reader instead, but I don't have one :). Pull the CSV files off and analyze to your heart's content!

I thought I'd post up the actual contents of the logcfg.txt sample, in case anyone is having problems downloading it. If you need to, just copy this into a blank text file and name it logcfg. Make sure the resulting file is logcfg.txt, not logcfg.txt.txt ;)


; uncomment the line below to minimize the information written to logcfg.out
; this will greatly decrease the startup time to begin logging if you already
; have a working logcfg.txt without any problems
;
; debug=noout

; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work

; this sample logs using the KWP2000 ReadMemoryAddress command over the ISO15765, which works
; for CAN based mitsubishis that have had their ROMs modified to allow the use of this command.
; this command is also known as "mode23" on some forums. since this command reads directly from
; ECU memory, the paramid addresses used are different for different ROM versions. the following
; example is for the USDM EVO X ROMs in the 526800xx series.

;----------------mrmacan evox----------------
; log channel settings
type=mrmacan

;-------------parameters-------------

paramname=RPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*

;paramname=PSIG
;paramid=0x80871a
;databits=16
;scalingrpn=x,0.0483675,*,14.5,-

;paramname=Timing
;paramid=0x808a07
;scalingrpn=x,20,-

;paramname=Knock
;paramid=0x808a4b

;paramname=LoadFuel
;paramid=0x80876e
;databits=16
;scalingrpn=x,0.3125,*

;paramname=IPW
;paramid=0x80a944
;databits=16
;scalingrpn=x,0.001,*

;paramname=TPS
;paramid=0x8086f9
;scalingrpn=x,32,-,0.505882,*
;priority=2

;paramname=MAF_Airflow_gs
;paramid=0x8087e0
;databits=16
;scalingrpn=x,0.02,*
;priority=2

;paramname=Speed_mph
;paramid=0x8087e7
;scalingrpn=x,1.26,*
;priority=2

;paramname=ActiveWGDC
;paramid=0x808b53
;scalingrpn=x,0.5,*

;paramname=WGDC_Correction
;paramid=0x808b51
;scalingrpn=x,0.5,*,64,-

;paramname=PassiveWGDC
;paramid=0x80a53f
;scalingrpn=x,0.5,*

;paramname=LTFT_Idle
;paramid=0x804573
;scalingrpn=x,0.1953125,*,25,-
;priority=2

;paramname=LTFT_Cruise
;paramid=0x804575
;scalingrpn=x,0.1953125,*,25,-
;priority=2

;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+

;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

;paramname=CruiseLight
;paramid= 0x8045C5
;databits=1
;offsetbits=5
;isvisible=0
;priority=2

;conditionrpn = CruiseLight,1,==
;action = start

;conditionrpn = CruiseLight,0,==
;action = stop



;----------------inno----------------
type=inno
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.

;paramname = inno.afr
;paramname = inno.lambda

UPDATE:

As some people have figured out, the newest beta has changed a few things, including the way "priority" is handled. Also, if EvoScan stopped working for you, check http://www.evoxforums.com/forums/showthread.php?t=31927 .

I've attached my current configuration that seems to work well. LC-1 users, take note of the logging changes.

;paramname=PSIG
;paramid=0x80871a
;databits=16
;scalingrpn=x,0.0483675,*,14.5,-

Make sure you change this ^^^ to your elevation. Mine is 12.4
I understand some of this and how its going to work but how come when I look at scalingrpn it sometimes not the same as your address in .txt file.

x*10/32 is Load fuel in evoscan but yours is x,0.3125,* How does that work? I might have just went way over my head lol.

10/32 = 0.3125

Good points, and good questions.

The PSIG / Boost should be changed, you are absolutely correct. Mine is 13.6.


As for the other question, it's simply a formatting issue. I'll use an example:

If I wanted to write x + 2 in RPN format (as used by the logger), it would be x,2,+

Hopefully that's simple enough to make sense.

As for your example of Load Fuel, (10/32) = 0.3125.

To simplify it and make it less calculations for the little Open Port adapter, x*0.3125 is easier.

Good info. Way to put forth effort to help others.

great post, bookmarked, etc!

Okay cool I understand now. Thanks man and to tephra!

BTW, I have an LC-1, so I'll verify that that's working too.

OK I got the logging to work, but I don't have the right 3/32" male <--> male cable to hook it up. I'll track one down tomorrow and definitely give it a shot.

A+++ post ;)

^ Make sure it's stereo with a ground (2 black lines + ground contact). Any decent electronics store should have it.

ya, altex (local electronics store) has it for $4. There's nothing at rat shack ("you've got questions, we've got dumb looks") that's $4 any more... it's always the $2000 gold plated monster crap these days :(

A quick search on radioshack.com returns nothing like what I need...

The nice thing about logging this way is that it's very similar to the accessport at this point. I've got the ODB port rerouted to my glove box, so I typically leave my tactrix cable attached to it in there. Now it'll actually be doing something useful :)

Got the cable this morning and the innovate LC-1 integration works like a champ.

Awesome.

I'm jealous at how easy the LC1 hookup would have been. I mean, seriously... Awesome.


Well, enjoy!

just wanted to say thinks for the effort. i tested it last night and i am stoked how well it worked. I just need to run the white aem wire this weekend.

The nice thing about logging this way is that it's very similar to the accessport at this point. I've got the ODB port rerouted to my glove box, so I typically leave my tactrix cable attached to it in there. Now it'll actually be doing something useful :)


Thats exactly how i have mine setup :) It'll be great to only have to use one USB connection for the Tactrix and not need the 2nd for the LC-1 any more! Totally trying this tonight :D

simply awesome!! this is great!

simply awesome!! this is great!
mitsu's warranty and customer service makes me with i never bout and evo..

the evo community completely negates that make make me happy every time i take her for a drive.

Got the cable this morning and the innovate LC-1 integration works like a champ.


What cable did you get? I want to try this tomorrow. =)

You sure its a 3/32 stereo cable? The LC-1 cable is 2.5mm stereo. Tactrix says they use a 2.5mm as well.

Same thing ;)

<EDIT>
So I just checked my logs...the only thing that ACTUALLY logs is TPS. The rest of the parameters are not working! So...this leads me to believe that something else is the problem and NOT necessarily the triggers etc.

I just verified the CruiseLight Addess with EVOScan and it IS correct for MRs. It is bit 5 that toggles 0 to 1. I'm not sure why the standalone SD card logging is not working...but its not :-P
</EDIT>

Ok...I can confirm that the CruiseLight Address does NOT, I repeat, does NOT work for MR. Well, at least on my CDN MR with ROM ID 21. I didn't quite go through and log each and every individual bit to see if it changed...actually, I changed databits = 1 to 16 in hopes that it would log the whole value, (2 bytes), to see if any of the bits toggled. Nada.

Other than that...oh, I'll try the Momentary CruiseLight in a few minutes.

Thanks!
verkion

I was able to get mine to work on my car. I just need to find the damn adapter to log the LC-1...

I got everything to try this now but can't find time to do anything right now. I got the adapters at radio shack ( I know but only store in town) but had buy adapters and cable because they don't just have the 3/32 or 2.5mm cable.

If you get a chance can you link me to what you bought.... Radio Shack is not what it once was.

Adapters part #274-373 (3/32 or 2.5mm to 1/8 or 3.5mm male to female) 1 each $5.99.
Cable is part #42-540 (1/8 or 3.55mm male to male also receipt showing #420-0540 but box show the other) $7.99

Total was $20.97

The interwebs is not just a fad guys.

http://www.cableclub.com/25mm-stereo-male-male-mini-plug-patch-cable-p-993.html?osCsid=38d5df32c99a6c8327bc91b3d442700e


verkion, I'll test on an MR as soon as I can. It's weird.

Kick right nuts!!!!!! LOL damn Radio shack!!!! ohh well.... You know reason I bought it like that instead of ordering it is, I was planning on doing it over weekend then it snowed and the wife had to work and I had little one.

But mines is BLUE!!! lol!

I was able to get mine to work on my car. I just need to find the damn adapter to log the LC-1...

$4
http://www.altex.com/2.5mm-Shielded-Male-to-Male-Stereo-Cable---6-70-206-P143128.aspx

They are local to me so I just picked it up.

Okay works great! The only thing is my LC-1 not right. Check it out.

And if I don't plug the lc-1 in looks like log10.

Also add Gauge reads right. Can the Adapter I'm using cause this issue? adapter 2.5-3.5mm then 3.5mm cable back to 3.5mm-2.5mm adapter into openport.

Okay works great! The only thing is my LC-1 not right. Check it out.

And if I don't plug the lc-1 in looks like log10.

http://forums.openecu.org/viewtopic.php?f=57&t=4319&p=22676&hilit=afr#p22676

If it were me, I'd just log lamda and multiply by 14.7. However, you can apparently fix it with the "LC1 Tool" or something.

I never used LC-1 tool, got software but think it would throw my gauge off then. (Hell I don't know lol) Not problem multiply in excel. I'm not smart at all when comes to this sh*t. But will say this thing logs VERY fast one millisecond is dope! Thanks again guys.

he has both innovate lines uncommented out in his config txt file.

as soon as he figures out the right way he'll be in business :)

Just got a chance test it (My 6 month old son is sick as dog.) all again and nothing.... I tried all the ways goofygrin and nothing. Here are the logs. But I can just do it in excel so not real big deal to me just be nice see it come out of log file that way.

Well, use the software. It was a documented problem, which can be fixed with the software. It won't mess up your gauge.

Or, wait until colby releases a new version!

Cool thanks man! Still pimp all way and fast! So no biggy.

here's my config (pardon the mixed end line characters, the issue with running a mix of OS's).

If this doesn't work for you then you have something else broken.

Yeah does not work.

You have likely zapped the config on your LC-1. I did this too by plugging in the jumper cable while the car was running.

You need to hook the LC-1 to your laptop and go into the config and retell it to be Gasoline 14.7. This is one of the issues with the LC-1.

This is why the lambda works (lambda is lambda, regardless of the fuel) but AFR doesn't.

Also for those looking for the 2.5m male to male connector, I found one in my LC-1 box... so maybe you have one also.

Okay my son went to sleep so I went out and changed my LC-1 to 14.7 and works like champ! Thanks goofygrin your okay I don't care what they say.

You know I don't remember if I did plug it in there while it was on but will remember not too!

^ Thought that was what it needed.

Good stuff, let us know if it reverts back to it's messed up state. I'm curious as to how often it happens.

I never played with that software before till now but not hard to do just went to custom setting (Gas 14.7 is not in dropped down menu) typed in 14.7 and came up for gas and saved.

But yes I will keep you updated see if anything happens.

you WILL need to recalibrate the sensor if you have zapped the gas type..

BOTH HEATER AND FREE AIR..

LC1 is a bitch like that, 1 reason why I like reading the output via analogue, now stoopid serial cable to screw up :)

Ahhh.. I did zap it then... I notice for some reason my air/fuel was way the F off and had do fresh air calibration. Needed it done anyways lol.

Damn LC1 is high maintenance... lol i need to recalibrate

the trick with the LC1:

1) use the MFI relay for power supply - that way you get a half decent voltage while cranking (instead of all over the place)

2) either leave the serial connection, OR disconnected forever...

3) ensure you have the most recent firmware (from 2 years ago) - that stops accidental recal's

actually I and a lot of other people have a ton of problems with the 1.1a firmware. I reverted to the 1.0a and have had very few issues (like none that weren't caused by me) since.

Here is the IDC if your don't want to do math.
NOTE/Update if you want IDC you have make sure that the IPW is uncommented ; or you can't log anything.

paramname=IDC
paramid=0X808746
databits=16
scalingrpn=IPW,RPM,*,1200,/

And for sh*ts and grins.

Manifold Air Temp

paramname=MATS
paramid=0X80865F
scalingrpn=x,1.8,*,40,-

Intake Air Temp

paramname=IATS
paramid=0X808659
scalingrpn=x,1.8,*,40,-

Coolant Temp

paramname=CTS
paramid=0X80863F
scalingrpn=x,1.8,*,40,-

Battery

paramname=Battery
paramid=0x8086EF
scalingrpn=x,18.75,*,255,/

Boost Error

paramname=BoostError
paramid=0x808B50
scalingrpn=x,128,-,2,/


Have not tested this one but should work. (For MR guys I think.)

Gear in use

paramname=Gear
paramid=0x80886E
databits=16
scalingrpn=x,22.6,/

Updated ^^^^

Good man!

Yeah work is slow and its snowing so got my car beside me in shop and laptop so thought I would test it all and all is good.

Anything else we need to log?

Okay little more


Mivec Intake Target

paramname=Intake MIVEC Target
paramid=0x80942E
databits=16
scalingrpn=x,4096,-,0.01953125,*

Mivec Intake Actual

paramname=Intake MIVEC Actual
paramid=0x809466
databits=16
scalingrpn=x,4096,-,0.01953125,*

Mivec Exhaust Target

paramname=Exhaust MIVEC Target
paramid=0x80943A
databits=16
scalingrpn=x,4096,-,0.01953125,*

Mivec Exhaust Actual

paramname=Exhaust MIVEC Actual
paramid=0x809472
databits=16
scalingrpn=x,4096,-,0.01953125,*


They work for me!

MAF Volts
paramname=MAF
paramid=0x808F50
databits=16
scalingrpn=x,0.004882813,*

log seems to work - look good to everyone?

use scalingrpn=x,1023,/,5,* instead :)

or x,0.0048875855,*

But does it really matter in this case? The simpler the RPN the quicker the OP2 works, no?


Which leads me to daydreaming of the future... KnockCEL and Standalone logging. Ahh, I can't wait :)

yeah I dont think speed matters, and I like to be verbose, because then people understand where the numbers are coming from...

my current file is below. it should have all the new definitions added

; uncomment the line below to minimize the information written to logcfg.out
; this will greatly decrease the startup time to begin logging if you already
; have a working logcfg.txt without any problems
;
; debug=noout

; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work

; this sample logs using the KWP2000 ReadMemoryAddress command over the ISO15765, which works
; for CAN based mitsubishis that have had their ROMs modified to allow the use of this command.
; this command is also known as "mode23" on some forums. since this command reads directly from
; ECU memory, the paramid addresses used are different for different ROM versions. the following
; example is for the USDM EVO X ROMs in the 526800xx series.

;----------------mrmacan evox----------------
; log channel settings
type=mrmacan

;-------------parameters-------------
paramname=RPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*

paramname=PSIG
paramid=0x80871a
databits=16
scalingrpn=x,0.0483675,*,14.5,-

paramname=Timing
paramid=0x808a07
scalingrpn=x,20,-

paramname=Knock
paramid=0x808a4b

paramname=LoadFuel
paramid=0x80876e
databits=16
scalingrpn=x,0.3125,*

paramname=IPW
paramid=0x80a944
databits=16
scalingrpn=x,0.001,*

paramname=TPS
paramid=0x8086f9
scalingrpn=x,32,-,0.505882,*
priority=2

paramname=MAF_Airflow_gs
paramid=0x8087e0
databits=16
scalingrpn=x,0.02,*
priority=2

;MAF Volts
;paramname=MAF
;paramid=0x808F50
;databits=16
;scalingrpn=x,1023,/,5,*
;priority=2

;paramname=Speed_mph
;paramid=0x8087e7
;scalingrpn=x,1.26,*
;priority=2

paramname=ActiveWGDC
paramid=0x808b53
scalingrpn=x,0.5,*

paramname=WGDC_Correction
paramid=0x808b51
scalingrpn=x,0.5,*,64,-

paramname=PassiveWGDC
paramid=0x80a53f
scalingrpn=x,0.5,*

paramname=LTFT_Idle
paramid=0x804573
scalingrpn=x,0.1953125,*,25,-
priority=2

paramname=LTFT_Cruise
paramid=0x804575
scalingrpn=x,0.1953125,*,25,-
priority=2

paramname=IDC
paramid=0X808746
databits=16
scalingrpn=IPW,RPM,*,1200,/

;paramname=MATS
;paramid=0X80865F
;scalingrpn=x,1.8,*,40,-
;priority=2

;paramname=IATS
;paramid=0X808659
;scalingrpn=x,1.8,*,40,-
;priority=2

;Coolant temp
;paramname=CTS
;paramid=0X80863F
;scalingrpn=x,1.8,*,40,-
;priority=2

;paramname=Battery
;paramid=0x8086EF
;scalingrpn=x,18.75,*,255,/
;priority=2

paramname=BoostError
paramid=0x808B50
scalingrpn=x,128,-,2,/

;Mivec Intake Target
paramname=Intake MIVEC Target
paramid=0x80942E
databits=16
scalingrpn=x,4096,-,0.01953125,*

;Mivec Intake Actual
paramname=Intake MIVEC Actual
paramid=0x809466
databits=16
scalingrpn=x,4096,-,0.01953125,*

;Mivec Exhaust Target
paramname=Exhaust MIVEC Target
paramid=0x80943A
databits=16
scalingrpn=x,4096,-,0.01953125,*

;Mivec Exhaust Actual
paramname=Exhaust MIVEC Actual
paramid=0x809472
databits=16
scalingrpn=x,4096,-,0.01953125,*

;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+

;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

paramname=CruiseLight
paramid= 0x8045C5
databits=1
offsetbits=5
isvisible=0
priority=2

conditionrpn = CruiseLight,1,==
action = start

conditionrpn = CruiseLight,0,==
action = stop



;----------------inno----------------
type=inno
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.

;paramname = inno.afr
;paramname = inno.lambda

Thank you for the Coolant Temp one! Here is what i came up with for STFT. I'm in the process of following Hollywood's thread to adjust for my AEM intake..

;paramname=STFT
;paramid=0x808898
;scalingrpn=x,0.1953125,*,25,-
;priority=2

I'm sure this is something simple i am missing... but i can't log my LC-1. All i get is a constant value of 255. While in the car i hooked up serial/usb to logworks and it was reading AFR just fine. Then i tried evoscan mode23 evo x logging and it logged my LC-1 ok as well. I'm using the 2.5mm to 2.5mm male to male cable that came with my LC-1.

Has anyone experienced this? Any advice?
edit = fixed: note to self: do not accidently delete 'type=inno' while making your logcfg file look 'cleaner'....

http://www.evoxforums.com/forums/showthread.php?t=25508&page=4

Pages 4-5...

I emailed this to tephra, but some of you might also know:

I'm tossing a GUI together to create the config files for stand along
sd card logging. the 2 triggers i found are cruiselight on and cruise
held down. are you aware if these locations are consistent across
roms? i know it works for me with romid 15 just fine but i don't know
about the JDM roms & the 2010 evox/ra


paramname=CruiseLight
paramid= 0x8045C5
databits=1
offsetbits=5
isvisible=0
priority=2

paramname=CruiseMomentary
paramid= 0x80AB1E
databits=1
offsetbits=1
isvisible=0
priority=2


Thanks in advance

EDIT EDIT EDIT
response from Tephra:
Nah they have different addresses on different ROMID's..

Which is a PITA :)

Cheers
D.
meh i guess i can just hide the cruise trigger for the other models for now

as per email:

Nah different memory locations per ROMID...

Just of note newcomer, before you get too far:

The standalone logger, including some of the parameters has recently changed. Priority and some other things have changed. Check the linked thread.

I'll eventually update the first post :)

Just of note newcomer, before you get too far:

The standalone logger, including some of the parameters has recently changed. Priority and some other things have changed. Check the linked thread.

I'll eventually update the first post :)

which linked thread?

i'm using the evoscan definition xml to build everything. here is a very early screen grab:

http://jessenewcomer.com/rng/logger.png

http://forums.openecu.org/viewtopic.php?f=57&t=4319

config file worked the same without having to change anything. cruise toggle worked without a hitch.

however the new beta broke evoscan, anyone have a ticket submitted to Hamish as a heads up?

i'll have to code in the ability to place selected data points into the new sample groups. the rest isn't much much different for us. i just got sick of opening the txtfile and searching for the data points i want to toggle on and off

hmm I was once able to get the toggle to work... it doesn't anymore... so I am stumped.

config file worked the same without having to change anything. cruise toggle worked without a hitch.

however the new beta broke evoscan, anyone have a ticket submitted to Hamish as a heads up?

i'll have to code in the ability to place selected data points into the new sample groups. the rest isn't much much different for us. i just got sick of opening the txtfile and searching for the data points i want to toggle on and off

I think the only big thing from a configuration standpoint is the priority change. Also, having added options such as "restarting the time stamp on each log", etc would be good to include in a program like you're making.

Wasn't aware of any EvoScan problems, I've only really been using this lately...

X - u using the new sampgroups?

the tactrix cable used to show up as a com port, now it is listed in its own group called "Vehicle PassThru Interfaces"

X - u using the new sampgroups?

I will be tomorrow. I just updated my cfg to use some of the new stuff. It's not a huge change anyway.

Though, I didn't realize it messes with EvoScan... That's unfortunate.

yeah sampgroups are pretty good.. i am logging SO much stuff now :)

Sweet, glad to hear!

Just to clarify, with the sampgroups, it's not a "priority" thing, right? It's just a label, so it doesn't matter the order. However, if you have lots of items in one sampgroup, that's a "low priority" way, right?

So, if I wanted to do important things, they get their own sampgroup?

Example:

Sampgroup1
RPM

Sampgroup2
PSI

Sampgroup3
WGDC

Sampgroup4
TPS
Speed
MAF Airflow
Other Low Priority Things

this is from the subie file:

; Notice that the next 3 parameters have a "sampgroup = 1" setting.
; There are 15 sample groups (1 - 15) that you can assign parameters to.
; Any parameters assigned to a sample group will be alternately logged in a single
; timeslot at a lower speed, the speed being 1 / N that of the sampling interval -
; where N is the number of parameters in the sample group. In this example, these
; 3 parameters will be logged at 1/3 the speed, but will also use 1/3 of the communications
; to the ECU, allowing you to log everything else faster.
; Since you can make up multiple sample groups, you can fine tune how fast different kinds of
; parameters are logged.

yeah... i have 2 sampgroups

1 = tps + wgdc + ipw
2 = ect/maf iat/mat/speed/other stuff i can't remember

everything else is not in a sampgroup...(or sampgroup 0)

Oh, here this thread is!!! Guess I should be browsing this section a little more now that I've ditched the AP :)

Awesome post Xprimnt^^ and thanks for the help finding all the stuff I needed in Radio Shack..

(was it just me or was that dude working there seriously creepy??)

Haha, thanks weebles.

Yeah, the Radio Shack guy was a bit too friendly for my taste. Weird.

Just as a heads up, the newest beta ECUFlash breaks Evoscan logging, so even though I was all excited to get the stuff for you, you might want to wait a minute. The OpenPort logging works even better now (sampgroups are much better than priority), but you might need Evoscan for a bit.

im sure hamish will fix it, my logger still works - so its probably something dumb :)

DAmn can anyone help me out how do i revert back to my old drivers... This sucks...

I cant log using evoscan now... and when i try to do the stand alone logger, it logs for ten rows and that is it... The stupid cruise on off does not even have an effect.

I have attached my Log CFG... maybe someone can help with both these issues.

Sorry Rogue, apparently iPhones can't read txt files :bowlol:

For now, change the cfg file so that the debug noout is commented. It's near the top. Then, you might be able to see where it's getting stuck by reading the out file.

what about reverting my tactrix to and old load

Ok I may have fixed it... I uninstalled the pas through driver... I will test shortly.

Ok i see it as a come port now......

Honestly, I haven't tried.

I know how to revert the drivers (remove Programs), and I guess you could install the older version, but I'm not sure if it will (if it has to) revert the firmware.

I'd personally just get the standalone logging working again, and wait until Hamish fixes it. I've opened a ticket, but if anybody knows a better way to contact him, I think that would be faster...

rogue...

try removing the inno type down the bottom.

i think having multiple type/channels causes this problem..

for some debugging, colby got me to add the battery voltage from the op20 itself... I only got 1 log file for 6 drives, 15 rows long.

thats the only change i made...

I'll update the first post with new details as soon as I can confirm EvoScan is working.

LC-1 logging has changed too, for those that are trying to figure out what is going on. Either look in the example logging files with the new beta (it's described in the subaru adc one) or wait until I update the first post!

I've opened a ticket, but if anybody knows a better way to contact him, I think that would be faster...
i posted over on evom. it seems a few people have been working closely with him to get 2.7 final out. i have the final beta... but now its broke :freak:
i got a SES today too, but i think its from the rear 02 logging mod.

With P0139 disabled?

i posted over on evom. it seems a few people have been working closely with him to get 2.7 final out. i have the final beta... but now its broke :freak:
i got a SES today too, but i think its from the rear 02 logging mod.


Send me your map... i just fixed all this crap with my car... no CELS now.

With P0139 disabled?

Send me your map... i just fixed all this crap with my car... no CELS now.
it didn't show up for the 1st 2 days :D
i am sure that is what it is but i can't pull cels/ses with my cable since its now flashed with the latest beta. i'll hit up advanced on my way home tomorrow and get it pulled. I'll be able to disable it but i was wishfully hoping it wouldn't pop up. regardless i love having it logging through the ecu now. so much nicer than a separate usb cable!

Hamish is now aware of the issue...

Colby is aware of the "multiple types" issue in the latest beta now too..

Got my LC-1 logging but it logs really high numbers (all between 50 and 70).. What do I need to change in the logcfg ??

Hmm. Maybe I guessed wrong? I thought the new setup was correct for the new LC1 stuff, but I could be wrong.

Here's the LC-1 Documentation:



;----------------inno----------------
type=inno
; log from an innovate MTS bus via the 3/32" jack
; multiple LC-1 and other MTS devices (e.g. TC-4) are supported
;
; each MTS parameter has a special parameter ID:
;
; paramid parameter
; 0x0101 LC-1 #1 AFR
; 0x0102 LC-1 #1 lambda
; 0x0201 LC-1 #2 AFR
; 0x0202 LC-1 #2 lambda
; 0x0301 LC-1 #3 AFR
; 0x0302 LC-1 #4 lambda
; (etc)
;
; 0x0001 aux #1 data (e.g. TC-4 #1 channel 1)
; 0x0002 aux #2 data (e.g. TC-4 #1 channel 2)
; 0x0003 aux #3 data (e.g. TC-4 #1 channel 3)
; 0x0004 aux #4 data (e.g. TC-4 #1 channel 4)
; 0x0005 aux #5 data (e.g. TC-4 #2 channel 1)
; (etc)

; the LC-1 parameters are already scaled correctly and require no scalingrpn setting
; however, the LC-1 is known to lose its stored AFR multiplier, so we recommend calculating
; AFR from lambda like this

;paramname = mylc1.afr
;paramid = 0x0102 ; get lambda from first LC-1
;scalingrpn = x,14.7,* ; scale to an AFR




Try the scalingrpn in your cfg as just x, let us know what you have. If it is still funky, try the other paramid (0x0101) with x, see if any of them work.

Sweet I'll try that tonight. Just got a new map to log so having my AFR's on there this time would be a huge help.

Damn gone for a week and new shit happens. WTF! lol. Will keep watching.

Just an X the logs were reading 4.5~ or so... hmmmm and changing the paramid didn't help.. it read 1.## when I did that.

Which paramid read ~1?

That's what we're looking for (Lambda)

Using this it read around 1..

paramname = mylc1.afr
paramid = 0x0101
scalingrpn = x


I also figured out that using the normal parameter it comes with I just need to divide the lc1 afr by 5 and that's the right reading.

Try the paramid as above, but with the scalingrpn as

x,14.7,*

Try the paramid as above, but with the scalingrpn as

x,14.7,*

You rule. :rock:

paramname = mylc1.afr
paramid = 0x0101
scalingrpn = x,14.7,*


^^works like a charm.

Ok guys, figured out what was going on with EvoScan not working.

The new beta has a new op20pt32.dll which it keeps in the system32 folder. However, EvoScan keeps its own op20pt32.dll in its program folder. EvoScan preferentially uses its own, which is now out of date and will not work with the new firmware.

The solution? Delete the op20pt32.dll from the EvoScan folder :)

Mine evoscan works fine. Never had a problem. Beta 2.7.

Did you update to the newest firmware? Change your logging cfg? etc etc

That's where we ran into problems, though it's all good now :)

Ok guys, figured out what was going on with EvoScan not working.

The new beta has a new op20pt32.dll which it keeps in the system32 folder. However, EvoScan keeps its own op20pt32.dll in its program folder. EvoScan preferentially uses its own, which is now out of date and will not work with the new firmware.

The solution? Delete the op20pt32.dll from the EvoScan folder :)
you the man..
testing it out on my way to work!

verified on the way to work, worked like a charm.

also figured out why i lost spool! loosened the wastegate back to stock when i got a new bov... silly me, tightened that bish all the way back up! over boost here i come

Haha, good luck!

verified on the way to work, worked like a charm.

also figured out why i lost spool! loosened the wastegate back to stock when i got a new bov... silly me, tightened that bish all the way back up! over boost here i come

Why did you do that?

Yeah Updated the OP and but already had Beta 2.7 Ecuflash. I'm not fcking with it I'll leave it how it is. Everything works lol.

Why did you do that?
new bov was holding boost flat so i figured i didn't need all the preload anymore. lesson learned i guess. i now need to turn my duty cycles way down again. i am estimating i dropped 20% on my duty cycles now that my bov doesn't leak

Yea when I put my aps BOV in, lol I over boosted and my wastegate was not very tight.

So I finally got this to work (big thanks to weebles and xPRimNT), but I can't get the LC-1 to work.
Link to my original post:
http://www.evoxforums.com/forums/showthread.php?t=29450

Here is my log.cfg:

;----------------inno----------------
type=inno
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.

paramname = mylc1.afr
paramid = 0x0101
scalingrpn = x,14.7,*

It will log everything else, but the values in the mylc1.afr column all read as "0". It did the same when I tried to log directly into evoscan....

I've read here that others have experienced the same problem, but with the LM-1. I at least get a value in the column...(http://forums.evolutionm.net/evo-x-engine-management-tuning-forums/469325-logging-beta-standalone-tactrix-cable-logger-no-more-computer.html)

So here's what Weebles and I have so far:

Here are some pieces of the puzzle:

Windows 7
Evoscan 2.6
"OUT" connected via 2.5mm serial port and linked to Tactrix-seated properly
"IN" 2.5mm serial port from LC-1 is plugged-seated properly
Logging attempt done when 02 sensor is hot/LC-1 sensor light is "steady on"
02 has been calibrated properly (but I will attempt again)
Engine is ON with logging attempt


Strange that I can not use his log.cfg file. I still get "0" in the lc-1 column...

Any help is most appreciated. I am running out of ideas. It is installed properly, but I am going to check it over again and perhaps overemphasize the grounding.

bump for ideas...

Sorry for the stupid question, but can anybody describe what this actual shows?;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+Does this have to be used with an Innovate LC-1 wideband? Or is this whatever signal the OEM O2 sensor is getting, after-cat?

Sorry for the stupid question, but can anybody describe what this actual shows?;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+Does this have to be used with an Innovate LC-1 wideband? Or is this whatever signal the OEM O2 sensor is getting, after-cat?

that is the location (0x80934e) to log the signal from the rear02 sensor (yellow wire). that does not log real a/f without installing a true wide band 02 sensor and properly configuring the formula.

edit: scalingrpn=x,0.008671875,*,10,+ is the formula i am using for my aem uego

;paramname = inno.afr
;paramname = inno.lambda
^This is for LC-1.

That one goes to yellow wire.

Never mind! Newcomer is fast!

Never mind! Newcomer is fast!
have you been talking to my wife? :wackoff:

Lol! forumla breaks down like this.

scalingrpn=x,0.008671875,*,10,+

Goes like this.

x (is number ecu or whatever is coming into the op2)
then it will times its by 0.008671875 then add 10 to it and equal the value.

Always skips back and forth so the X will times, scalingrpn=x,0.008671875,*,10,+
then that value you will add 10 to it. scalingrpn=x,0.008671875,*,10,+

then that is your total value.

;paramname = inno.afr
;paramname = inno.lambda
^This is for LC-1.

That one goes to yellow wire.

Never mind! Newcomer is fast!

Also keep in mind that the lc1 logging has changed in the newest one. No more inno.afr, etc.


But yes, the rear o2 is for those that have a wb wires into the rear o2 sensor location.

Think I'll just use what keeps working for me lol. I forgot it all changed now.

The new one lets you take lambda as a calculation, so you can do lambda*14.7. Handy if it had been giving you trouble.

But I agree, stick to what works.

Lol! forumla breaks down like this.

scalingrpn=x,0.008671875,*,10,+

Goes like this.

x (is number ecu or whatever is coming into the op2)
then it will times its by 0.008671875 then add 10 to it and equal the value.

Always skips back and forth so the X will times, scalingrpn=x,0.008671875,*,10,+
then that value you will add 10 to it. scalingrpn=x,0.008671875,*,10,+

then that is your total value.

Ahh Reverse Polish notation at it's best.

p.s. wiki Reverse Polish Notation if you want to know more.

Lol! forumla breaks down like this.
Thank you. Makes sense.

Does swapping out the factory O2 sensor with a wideband O2 sensor and wiring it in the factory harness work? Then would it properly display/log AFR?

So basically you can have a digital readout if the tactrix is connected to a carputer? Just hypothetical, I already have a ZT-2 that I just need to run the wires into the cabin for...

I know it works something like that, but I just run LC-1. One of the other "nerds" will know, lol!

Thank you. Makes sense.

Does swapping out the factory O2 sensor with a wideband O2 sensor and wiring it in the factory harness work? Then would it properly display/log AFR?

So basically you can have a digital readout if the tactrix is connected to a carputer? Just hypothetical, I already have a ZT-2 that I just need to run the wires into the cabin for...

yes, there is a how-to on how to do it.

use the same memory address that was already posted and add "23" to the front of it

Yep!

http://www.evoxforums.com/forums/attachment.php?attachmentid=8812&d=1257266023

Oh I was kinda meaning something different... I already have a Zeitronix wideband so I'm not installing an AEM Uego or Innovate LC-1, I was more thinking along the lines of trading the OEM O2 sensor for a wideband O2 sensor and then logging through the Tactrix microSD logs.

I can already hook up a laptop to the Zeitronix ZT-2 and log quite a few things including boost and AFR, but I was hoping to get that all through the microSD on the Tactrix without having to install a redundant AFR gauge (like the LC-1 or AEM Uego ON TOP of already having the Zeitronix ZT-2).

Thanks though, I'll just log through the ZT-2 and combine the log with what the Tactrix microSD logs. :computermad:

^ You can still do it, don't give up yet!

The ZT-2 must have an analog out... It doesn't matter what kind of WB you have tied into the rear O2 sensor. Read my OTHER HowTo, on Rear O2 ADC Logging.

The only thing that will be different is the equation used. Of course, I haven't looked into the ZT2 to see what the analog output (if any) is, but it should work.

yeh... tap the rear02 with the zt2 analogue output..

thats what all the cool people do anyways :D hehe

Awesome, thanks! I'll just have to modify the formula to fit whatever output the ZT-2 gives? (I think 0-5V...?)

I should be able to figure it out from all the how-to's you guys have been so generous to give :thumbup:

I just got this working for the 2010 Evo X GSR (55570005 ROM)

Here is my file:
; uncomment the line below to minimize the information written to logcfg.out
; this will greatly decrease the startup time to begin logging if you already
; have a working logcfg.txt without any problems
;
; debug=noout

; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work

; this sample logs using the KWP2000 ReadMemoryAddress command over the ISO15765, which works
; for CAN based mitsubishis that have had their ROMs modified to allow the use of this command.
; this command is also known as "mode23" on some forums. since this command reads directly from
; ECU memory, the paramid addresses used are different for different ROM versions. the following
; example is for the USDM 2010 EVO X ROMs with 55570005 ROM id.

;----------------mrmacan evox----------------
; log channel settings
type=mrmacan

;-------------parameters-------------

paramname=RPM
paramid=0x808763
scalingrpn=x,31.25,*

paramname=PSIG
paramid=0x80872e
databits=16
scalingrpn=x,0.0483675,*,14.5,-

;paramname=Timing
;paramid=0x808a1f
;scalingrpn=x,20,-

paramname=Knock
paramid=0x808a63

paramname=LoadFuel
paramid=0x808784
databits=16
scalingrpn=x,0.3125,*

;paramname=IPW
;paramid=0x80aa88
;databits=16
;scalingrpn=x,0.001,*

paramname=TPS
paramid=0x80870d
scalingrpn=x,32,-,0.505882,*
priority=2

;Unknown offset
;paramname=MAF_Airflow_gs
;paramid=0x8087e0
;databits=16
;scalingrpn=x,0.02,*
;priority=2

;paramname=Speed_mph
;paramid=0x8087ff
;scalingrpn=x,1.26,*
;priority=2

;Interpolated
;paramname=ActiveWGDC
;paramid=0x808b6b
;scalingrpn=x,0.5,*

;Interpolated
;paramname=WGDC_Correction
;paramid=0x808b69
;scalingrpn=x,0.5,*,64,-

;Interpolated
;paramname=PassiveWGDC
;paramid=0x80a557
;scalingrpn=x,0.5,*

;paramname=STFT
;paramid=0x8088B0
;scalingrpn=x,0.1953125,*,25,-
;priority=2

;paramname=LTFT_Idle
;paramid=0x804573
;scalingrpn=x,0.1953125,*,25,-
;priority=2

;paramname=LTFT_Cruise
;paramid=0x804575
;scalingrpn=x,0.1953125,*,25,-
;priority=2

:unknown
;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+

;paramname=ManifoldAirTemp
;paramid=0x808672
;databits=16
;scalingrpn=x,1.8,*,48,-

;paramname=IntakeAirTemp
;paramid=0x80866D
;scalingrpn=x,1.8,*,48,-

;paramname=CoolantAirTemp
;paramid=0x808663
;scalingrpn=x,1.8,*,48,-

;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

;paramname=CruiseLight
;paramid= 0x8045C5
;databits=1
;offsetbits=5
;isvisible=0
;priority=2

;conditionrpn = CruiseLight,1,==
;action = start

;conditionrpn = CruiseLight,0,==
;action = stop



;----------------inno----------------
type=inno
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.

;paramname = inno.afr
;paramname = inno.lambda



The ones labeled "Interpolated" or "Unknown", are just that and are untested.

I'd love to have more logging parameters for the 2010. But I'm not sure where to find them.

It would be awesome if Tephra or someone could get me the address for CruiseLight and / or CruiseMomentary so I can use the trigger.

Thanks Golden, I'm sure that will help others out.


On a related note, I've updated the 3rd post with my current configuration (most recent beta).

Do you have to remove the memory card to log with EvoScan? Mine is set up to log whenever the OpenPort 2.0 is plugged in to my car. Can I simply rename logcfg.txt file to prevent logging?

I don't want to loose this memory card. It's smaller than my fingernail.

Do you have to remove the memory card to log with EvoScan? Mine is set up to log whenever the OpenPort 2.0 is plugged in to my car. Can I simply rename logcfg.txt file to prevent logging?

I don't want to loose this memory card. It's smaller than my fingernail.



Try it a few times so you know how it works specifically. Essentially, when you have a USB cable plugged into the OP, the logger is deactivated. Watch the LEDs, you'll notice them change from "logging (red/green with occasional blue) to "inactive (multicolored)".

Oh, I see. That's awesome. I'm so glad I switched over. :D

I'd love to have more logging parameters for the 2010. But I'm not sure where to find them.

Here are a few that Bryan@Gst posted in case they are not in your file. (http://www.evoxforums.com/forums/showpost.php?p=451530&postcount=10)

anything your correctly logging in evoscan has the addresses & formulas you need. just remove the "23" off of the front of the address. I havn't looked at the latest evoscan parameters to see if any more were added for the 2010

Here are a few that Bryan@Gst posted in case they are not in your file. (http://www.evoxforums.com/forums/showpost.php?p=451530&postcount=10)

anything your correctly logging in evoscan has the addresses & formulas you need. just remove the "23" off of the front of the address. I havn't looked at the latest evoscan parameters to see if any more were added for the 2010


I have, and there are none. I already figured out the removal of 23. Thats how I got all the values I posted above.

Oh, and if anyone grabbed my file above, I had RPM messed up, but I'm editing it now to fix it.

From anybody's experience with the manifold air temp and intake air temp, were they useful? Are they relevant? Like if I change something around, maybe throw in a teflon intake manifold gasket to reduce heat soak and then use these air temp logs to see any changes, will that be usable data? Or are those logs just for shits n giggles?

Thanks to all of those who have helped answer a ton of questions in this thread, I've gotten the standalone logging to work perfectly and I owe it to Tephra and his geek-squad here.

i log ECT/MAT/IAT but I log them at a lower priority... here is my log cfg:


type=mrmacan

zerosampletime = 1
fillmissingsamples = 0

paramname=RPM
paramid=0x80873e
databits=16
scalingrpn=x,1000,*,256,/

paramname=PSIG
paramid=0x808712
databits=16
scalingrpn=x,4,/,0.19347,*,14.5,-

paramname=TimingAdv
paramid=0x8089ff
scalingrpn=x,20,-

paramname=KnockSum
paramid=0x808a43
scalingrpn=x

paramname=Load
paramid=0x808766
databits=16
scalingrpn=x,10,*,32,/

paramname=IPW
paramid=0x80a934
databits=16
scalingrpn=x,1000,/

paramname=TPS
paramid=0x8086f1
scalingrpn=x,100,*,256,/
sampgroup=1

paramname=AFR
paramid=0x809346
databits=16
scalingrpn=x,1023,/,5.99,*,10,+

paramname=ActiveWGDC
paramid=0x808b4b
scalingrpn=x,2,/
sampgroup=1

paramname=FuelTrim_Current
paramid=0x8088A1
scalingrpn=x,0.1953125,*,25,-
sampgroup=2

paramname=ECT
paramid=0x808637
scalingrpn=x,40,-
sampgroup=2

paramname=MAT
paramid=0x808656
scalingrpn=x,40,-
databits=16
sampgroup=2

paramname=MAFIAT
paramid=0x808650
scalingrpn=x,40,-
databits=16
sampgroup=2

paramname=Speed
paramid=0x8087DE
scalingrpn=x,2,*
databits=16
sampgroup=2

paramname=TephraMod_Flags
paramid=0x80b000
scalingrpn=x
databits=8
sampgroup=2


This gives me 1 row every 0.1 second exactly, you can see I am using sampgroup 1 for TPS+ActiveWGDC and sampgroup 2 for a bunch of other things... stuff that I dont care about being updated every row..

Is Samplegroup = 1 implied, or is it a zero based scale?

No samplegroup is implied :)

From anybody's experience with the manifold air temp and intake air temp, were they useful? Are they relevant? Like if I change something around, maybe throw in a teflon intake manifold gasket to reduce heat soak and then use these air temp logs to see any changes, will that be usable data? Or are those logs just for shits n giggles?
they both work well. i did some temp testing with SSPs intake gasket set and noticed a nice drop in temperatures just from the gaskets.
http://www.evoxforums.com/forums/showthread.php?t=28044
intake air temp was relatively stable as it didn't suffer from heat soak like the manifold does.

Wanted to get some auto knock logging based off the same trigger logic for the knock light. I went out and tested this and it works pretty well. If there is another load value that already takes into account the IATS please let me know, I would much rather have one trigger. I believe they can be combined logically but I was unable to find grouping syntax for the logical operators.

;-------------parameters-------------

paramname=Knock
paramid=0x808a4b

paramname=IATS
paramid=0X808659
scalingrpn=x,1.8,*,50,-
priority=2

paramname=LoadTiming+
paramid=0x808774
databits=16
scalingrpn=x,0.3125,*

paramname=LoadTiming-
paramid=0x808F70
databits=16
scalingrpn=x,0.3125,*

;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

paramname=CruiseLight
paramid= 0x8045C5
databits=1
offsetbits=5
isvisible=0
priority=2

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

;Knock Trigger 1
conditionrpn = Knock,1,>,IATS,75,>,&&,LoadTiming+,120,>,&&
action = start
conditionrpn = Knock,0,==
action = stop

;Knock Trigger 2
conditionrpn = Knock,1,>,IATS,75,<=,&&,LoadTiming-,120,>,&&
action = start
conditionrpn = Knock,0,==
action = stop

I tried this a while back. You end up with a new file every time it knocks. My only issue with it was I wanted more logged when it knocked.

I think Tephra once said that with a 2 GB card, you can log everything for a year before running out of space.


Also, the eval lines are fairly slow on this thing. A couple of these lines:
Knock,1,>,IATS,75,<=,&&,LoadTiming-,120,>,&&
can really slow it down.

I tried this a while back. You end up with a new file every time it knocks. My only issue with it was I wanted more logged when it knocked.

I think Tephra once said that with a 2 GB card, you can log everything for a year before running out of space.


Also, the eval lines are fairly slow on this thing. A couple of these lines:
Knock,1,>,IATS,75,<=,&&,LoadTiming-,120,>,&&
can really slow it down.

Yeah, I am only running these to catch some knock over an extended period of time, granted if there is any at all. You are correct about having a seperate file though but that can be merged easily enough. I find it is a bit more useful than doing pulls to check for knock, just let it run for a week, merge it, and go from there. I think to many put to much merit in the speed of the logging. I agree that during tuning you need the best resolution possible, but when collecting a large data sample the speed really doesn't matter. If I miss a data point, I am sure over a week the data I do have will make up for it. :nerd:

It has to be reading from the ECU when a knock happens. Otherwise you won't know. So speed is highly important.

Here is and example.
Lets say that logging Style A does 20 per second and Style B does 2 per second.

Here is a log with time stamps and a display of when each Style read form the ECU.

Log goes: A read, B read, Time Stamp, Knock Counts

A, B, 1.00, 0
A, _, 1.05, 4
A, _, 1.10, 4
A, _, 1.15, 4
A, _, 1.20, 4
A, _, 1.25, 4
A, _, 1.30, 4
A, _, 1.35, 0
A, _, 1.40, 0
A, _, 1.45, 0
A, B, 1.50, 0
A, _, 1.55, 0
A, _, 1.60, 2
A, _, 1.65, 2
A, _, 1.70, 4
A, _, 1.75, 4
A, _, 1.80, 8
A, _, 1.85, 8
A, _, 1.90, 8
A, _, 1.95, 4
A, B, 2.00, 0
A, _, 2.05, 0
A, _, 2.10, 0
A, _, 2.15, 0
A, _, 2.20, 0

Granted, this is a worse case senerio, but Style B would show no knocks at all.
A, B, 1.00, 0
A, B, 1.50, 0
A, B, 2.00, 0

It has to be reading from the ECU when a knock happens. Otherwise you won't know. So speed is highly important.

Here is and example.
Lets say that logging Style A does 20 per second and Style B does 2 per second.

Here is a log with time stamps and a display of when each Style read form the ECU.

Log goes: A read, B read, Time Stamp, Knock Counts

A, B, 1.00, 0
A, _, 1.05, 4
A, _, 1.10, 4
A, _, 1.15, 4
A, _, 1.20, 4
A, _, 1.25, 4
A, _, 1.30, 4
A, _, 1.35, 0
A, _, 1.40, 0
A, _, 1.45, 0
A, B, 1.50, 0
A, _, 1.55, 0
A, _, 1.60, 2
A, _, 1.65, 2
A, _, 1.70, 4
A, _, 1.75, 4
A, _, 1.80, 8
A, _, 1.85, 8
A, _, 1.90, 8
A, _, 1.95, 4
A, B, 2.00, 0
A, _, 2.05, 0
A, _, 2.10, 0
A, _, 2.15, 0
A, _, 2.20, 0

Granted, this is a worse case senerio, but Style B would show no knocks at all.
A, B, 1.00, 0
A, B, 1.50, 0
A, B, 2.00, 0

So far I have run this concurrently with push button logging and I get the same exact entries for knock in the knock files as in the 3rd gear pull log file. Also, the times with and without the knock trigger in place on 3rd gear pull logs has the same amount of samples. I have done it about a dozen times, I get the same +/- 1 or 2 lines in my log files with and without the triggers. So I guess what I am saying is I don't see that 2 triggers is really affecting anything. I am sure there is a magic number that does but 2 isn't causing any missed entries for me.

Ahh, that is good. That is an answer I like. "I tested it, it doesn't go slower."

I was just talking about your statment:
"I agree that during tuning you need the best resolution possible, but when collecting a large data sample the speed really doesn't matter."

And I was trying to show that speed does matter. ;)

Ahh, that is good. That is an answer I like. "I tested it, it doesn't go slower."

I was just talking about your statment:
"I agree that during tuning you need the best resolution possible, but when collecting a large data sample the speed really doesn't matter."

And I was trying to show that speed does matter. ;)

Yeah, I didn't notice any appreciable decrease in speed due to the triggers.

I'm saying that I like that you tested it to see if it was slower. :)

I'm saying that I like that you tested it to see if it was slower. :)

Gotcha! ;)

I have looked everywhere but probably not using the right word or phrase. Does anyone know whether the stereo plug on the Tactrix is analog or digital?

Analog. 2.5mm.

It's not a Toslink/Minidigital.

Analog. 2.5mm.

It's not a Toslink/Minidigital.

Thanks!

Does anyone know if it is possible to get the standalone logging to have a more precise time scale like in the Evoscan logs, i.e., LogEntrySeconds? I wired up my ECU ADC to my wideband and everything works great but Virtual Dyno cannot plot the run worth shit because the only time scale in the logs is <time> which doesn't provide a smooth graph at all due to the lack of resolution. It looks like a set of bear teeth when plotted.

Thanks!

Log less items. :)

Log less items. :)

I get 92 data points for both OpenPort and Evoscan in my logs, logging the same items. Time scale is 8 seconds for the run on both. I cannot log less, as I am only logging AFR, Boost, RPM, fuel load, and TPS. At each point in both logs I am at the same approxiate RPM for each time stamp. For some reason VDR doesn't like the format of the time and pukes. I can overlay my seconds column from Evoscan log over the OpenPort log and it looks perfect (keeping in mind when they are superimposed on each other in Excel they damn near match perfectly with respect to time, value, and position.

Analog. 2.5mm.

It's not a Toslink/Minidigital.

Caveat: The port is designed to receive serial communication (from LC1, and now AEM or other ASCII serial data streams) not a 0-5V signal.

How do you compute for the scaling for elevation in boost? I live 160 feet above sea level.

And being the nub that I am, I assume you don't need to purchase EvoScan anymore to get this working properly since it's a stand-alone logger, correct?

How do you compute for the scaling for elevation in boost? I live 160 feet above sea level.
http://www.evoxforums.com/forums/showthread.php?t=33319&highlight=boost

And being the nub that I am, I assume you don't need to purchase EvoScan anymore to get this working properly since it's a stand-alone logger, correct?
technically not to log the data points; but while tuning i used evoscan so i can't watch the data realtime not to mention it can do dtc codes and maptraces as well as a bunch of other cool stuff.

http://www.evoxforums.com/forums/showthread.php?t=33319&highlight=boost

Cool thanks!

technically not to log the data points; but while tuning i used evoscan so i can't watch the data realtime not to mention it can do dtc codes and maptraces as well as a bunch of other cool stuff.

I guess I need to get evoscan still. I just like the idea of not having a laptop beside you just to log. Thanks again!

Just as a note, in the thread newcomer linked, I have some information on one of the later pages. It includes the simple way to do it and the fancy way of doing it with realtime baro compensation.

And yes, you don't need EvoScan.

I only log with EvoScan... I love it. :)

Just as a note, in the thread newcomer linked, I have some information on one of the later pages. It includes the simple way to do it and the fancy way of doing it with realtime baro compensation.

Alrighty, will read through the entire thread. Thanks!

And yes, you don't need EvoScan.

I only log with EvoScan... I love it. :)

Haha! So do you prefer EvoScan over the stand-alone logging? I mean, it's still in its beta stages, but I'm looking for a long-term goal here.

Yes I like EvoScan better. More because I have the laptop do the logging and EvoScan logs at a much higher resolution (speed). More data = easier to tune.

I believe Tephra logs 24/7 with his stand alone. That way he can look at what was happening in his car whenever he wants.

Yes I like EvoScan better. More because I have the laptop do the logging and EvoScan logs at a much higher resolution (speed). More data = easier to tune.

I believe Tephra logs 24/7 with his stand alone. That way he can look at what was happening in his car whenever he wants.

Oh I see. Good to know. I guess I can put it this way:

Tuning: evoscan
Daily observation: stand-alone

Thanks fellas!

Oh I see. Good to know. I guess I can put it this way:

Tuning: evoscan
Daily observation: stand-alone

Thanks fellas!

Standalone is also nice for casual track users that don't want to mess with a laptop but may want to monitor what the car is doing on track.

I need help getting this working on my car. I follow xprimnt instructions but can't get it to log. The only output I get is the attached file. Can anybody help me with this.

I have a 2009 World Market EVO X MR with ROM ID 54070007

It would be awesome if Tephra or someone could get me the address for CruiseLight and / or CruiseMomentary so I can use the trigger.

Has this been found yet?

- Bryan

Yes I have it. I posted it up in my 55570005 thread if you look closely. Hint: Standalone file. lol

I have both the toggle of the button and the cruise control on/off. (Button is momentary, Cruise is a toggle)

238045C5 (cruise) and 2380AC62 (button) for 2010's.

Yes I have it. I posted it up in my 55570005 thread if you look closely. Hint: Standalone file. lol

I have both the toggle of the button and the cruise control on/off. (Button is momentary, Cruise is a toggle)

238045C5 (cruise) and 2380AC62 (button) for 2010's.

Awesome thank you! Now I just need CAN address logging and I'll be a happy man!

- Bryan

Sorry, I know nothing about the CAN stuff, as I don't use it.

Hi folks.

While on the OpenECU forums, I came across an alternative method of logging my wideband analog 0-5V when using the Tactrix OP2.0 standalone logger.

Instead of using one of the vehicle's ECU ADC inputs (eg. disabling rear o2 sensor), the OP2.0 itself can be configured to do the job. It can sample voltage on OBD-II Pin 8. Apparently, this pin is unused, so it's a completely free analog logging input there for the taking.

Note that I didn't work this out or "discover" it. See below for original references. As this information doesn't seem to have made it across to the Evo/Ralliart owner space, here it is at last.


The original posts from dschultz... are here, on the RomRaider and OpenECU forums...

http://forums.openecu.org/viewtopic.php?f=2&t=4790 (http://forums.openecu.org/viewtopic.php?f=2&t=4790)
http://www.romraider.com/forum/viewt...hp?f=15&t=6512 (http://www.romraider.com/forum/viewt...hp?f=15&t=6512)

I've successfully got this working - very easy. My Innovate LC-1 analog output is now being directly logged by the OP2.0 standalone. All other OP2.0 operations are 100% unaffected - ECU reading, writing, EvoScan logging are all untouched.


Here's what you need to do...


First off, in the microSD card's "logcfg.txt" file, add a "type=adc" config entry. Here's an example...


;----------------adc----------------
type=adc ; log from built in ADC channels

paramname=volts
paramid=8 ; paramid is pin number on OBD connector
; valid pins are 8 and 16
; values are pre-scaled to millivolts
scalingrpn=x,0.001,* ; here we scale to volts


Next, you need to splice the analog output you want to sample into the OBD-II Pin 8, so the OpenPort 2.0 box can "see" it. I did it the way it was described in one of the above links - just opened up my extension cable (purchased from Tactrix). I verified the green wire was Pin 8, cut it, and soldered a connecter inline. I guess another valid approach would be to patch in at the vehicle's OBD-II port.


Next, if you have to, reconfigure the device being logged to produce appropriate output voltage. For my LC-1, that was simply a matter of using LMProgrammer to define the required voltage output for the AFR/lambda range.


And that was about it, really. When you start the car, the OP2.0 kicks off its microSD logging, and you'll get a new column in the .csv. Values will be scaled as per your "scalingrpn" definition in "logcfg.txt". You can make it an AFR-style value, or lambda, or whatever. The above example just logs volts.

Hope this helps!

Cheers,

Rich

While on the OpenECU forums, I came across an alternative method of logging my wideband analog 0-5V when using the Tactrix OP2.0 standalone logger.

Instead of using one of the vehicle's ECU ADC inputs (eg. disabling rear o2 sensor), the OP2.0 itself can be configured to do the job. It can sample voltage on OBD-II Pin 8. Apparently, this pin is unused, so it's a completely free analog logging input there for the taking.



Awesome! Wish I had known about this before I cut my rear 02 sensor out. Guess I'll be putting that back and setting this up. :duh:

Awesome! Wish I had known about this before I cut my rear 02 sensor out. Guess I'll be putting that back and setting this up. :duh:

Why you would want to preserve the stock rear O2 is another question. I personally like the stock rear O2 override, much easier and requires less to log. I can use so many off the shelf logging apps for my iPhone that can get access to my fueling. Nice attempt though, but you are limiting logging to only the OpenPort...

Hey guys,

I'm attempting this tonight, but despite searching I can't find anything for the references for 5305009 for the cruise logging.

Also do the references for the logging items change per rom id? Or are they same same as how Evoscan?

Cheers,

yeh they change, but you can grab the addresses from EvoScan, just strip the leading 23...

ie RPM should be 0x80873E

Thanks Tephra.

What about the address to enable logging via the cruise control switches? Anyone got that?

8045C5 is pretty consistent across all roms. Isn't it in the write up?

Yeah, just asking since the guide says that reference is only confirmed for USDM roms and I'm upside down in Australia ;)

Oh.. your location makes it seem like you are in the US. WA = Washington around here... though I did type Perth, WA into googe maps and it seems to know the difference.

Hi everyone!

I have read all 19 pages of the topic and found out that I need a certain text file for my ROM 52370024, am I right?
One thing I did not understand - what specific file from the folder samples / loging I need to rename: "Mitsui CAN" or "OBD CAN mod 01 22 23"?
The correct address of the parameters I needed, can be taken from Evoscan? (highlighted in red)
http://imglink.ru/thumbnails/06-03-11/8a357e9243a7db785ee6dd5ad7a63304.jpg (http://imglink.ru/show-image.php?id=48b6b90a66bb7dc1abec6e1e4dd33ec4)

Those addresses are for the 2010 USDM cars. All the roms that start with 55.

You need:

23808766 Load
2380873E 2ByteRPM
23808712 PSIG / Boost
23808A43 Knock Sum
23808890 STFT
23804573 LFTF Idle
23804575 LTFT Cruise
238088A1 LTFT in use
2380876C Load (MIVEC) and (Timing if IAT GT 75F)
238086F1 TPS
238094F9 Accel Pedel Position
238089FF TimingAdv
23808B4B ActiveWGDC
23808651 Intake Air Temp
23808637 Coolant Temp
23808657 Manifold Air Temp
2380A934 IPW
23808F48 MAF Volts
23809422 INVVT (Target)
2380942E EXVVT (Target)
2380945A INVVT (Actual)
23809466 EXVVT (Actual)
238087DF Speed
238086E7 Battery
2380A8F9 Barometer
23808A49 knock_adc_processed
2380A92B knock_base
2380A927 knock_var
2380A92D knock_change
23808A57 knock_dynamics
2380812D knock_flag
23808661 Front O2
23808665 Rear O2
238045C5 Cruise Light
23808B49 WGDC Correction


Take off the "23" on all those if you are using the stand alone logger.

Thanks Michael!

But which txt I must rename?
So, I need just take off 23 or replace it with 0x...?

Are you doing Stand Alone logging or EvoScan logging?

Standalone Tactrix OP2.0

Just get a copy of someones logcfg.txt. There is one in this thread, and I have one posted in the 55570005 thread.

Then change each line to an address that matches your rom. Here is an example from my logcfg.txt.


;-------------parameters-------------

paramname=RPM
paramid=0x80875C
databits=16
scalingrpn=x,3.90625,*

paramname=LoadFuel
paramid=0x808784
databits=16
scalingrpn=x,0.3125,*


Changed to:


;-------------parameters-------------

paramname=RPM
paramid=0x80873E
databits=16
scalingrpn=x,3.90625,*

paramname=LoadFuel
paramid=0x808766
databits=16
scalingrpn=x,0.3125,*

Just get a copy of someones logcfg.txt. There is one in this thread, and I have one posted in the 55570005 thread.

Then change each line to an address that matches your rom. Here is an example from my logcfg.txt.


;-------------parameters-------------

paramname=RPM
paramid=0x80875C
databits=16
scalingrpn=x,3.90625,*

paramname=LoadFuel
paramid=0x808784
databits=16
scalingrpn=x,0.3125,*


Changed to:


;-------------parameters-------------

paramname=RPM
paramid=0x80873E
databits=16
scalingrpn=x,3.90625,*

paramname=LoadFuel
paramid=0x808766
databits=16
scalingrpn=x,0.3125,*

Thanks Michael!

I tried logging, but it seems that something is wrong.
I enclose logcfg * txt, and the three resulting files.
Please take a look.

Is your rom in mode 23?

Is your rom in mode 23?
Of course!

Have you been able to log the car with EvoScan? Those logs look like it is reading bogus values that never change.

Can this be added to the stand alone file? What would the parameters be for the below? I have an 08 MR.

<DataListItem DataLog="N" Color="" Display="LTFT High" LogReference="LTFT High" RequestID="238088A9" Eval="(0.1953125*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

paramname=LTFT_High
paramid=0x8089A9
scalingrpn=x,0.1953125,*,25,-

Thanks Golden.

sub'd. i just did this on my openport. gonna try it tomorrow.

Can the openport 2.0 adapter handle SDHC (High Capacity) memory cards? I am thinking i am going to get a 8 GB High Capacity Class 6 micro SD card.

Can the openport 2.0 adapter handle SDHC (High Capacity) memory cards? I am thinking i am going to get a 8 GB High Capacity Class 6 micro SD card.

Not a direct answer to your question, but you could log for years without ever having to delete a log with a 2GB card.

I used an 8 GB card with not problem.

I used an 8 GB card with not problem.

Awesome, i already bought one online. I have an LC-1. Can it connect to the openport via 2.5mm stereo connection or should i run it through my rear o2 sensor?

Can it connect to the openport via 2.5mm stereo connection or should i run it through my rear o2 sensor?

Yes, and yes.

either or..

serial connectivity is good for easy of use and you dont need to worry about voltage differentials

analog(rear02) connectivity is good for logging speed but you need to do some voltage checking in lmprogrammer before considering it "good to go"

either or..

serial connectivity is good for easy of use and you dont need to worry about voltage differentials

analog(rear02) connectivity is good for logging speed but you need to do some voltage checking in lmprogrammer before considering it "good to go"

How much faster is the analog connectivity (samples/second)?

I think serial limits you to like 12 samples/second

whereas analog is instant, well as fast as you can poll the ECU/op20...

So go with logging through the rear o2 (analog) then. What do i have to change for the output of the analog in the LC-1?

Does anyone know if I would be able to log my AEM wideband via serial connector if I used a serial to 2.5mm cable such as this: http://www.m2cables.us.com/Serial-Cable-DB9-Female-to-2-5mm-Plug-UL-p/m2pcm-2233-06.htm along with a male-to-male serial adapter?

So go with logging through the rear o2 (analog) then. What do i have to change for the output of the analog in the LC-1?

You have to wire it up correctly obviously.

and then I like to run an AFR range of 10.0:1 (0v) -> 15.99:1 (5v)

however as a precaution before I rely on the numbers I go through each voltage and make sure im getting the right voltage in EvoScan...

ie set the analog output to 0v, then 1v, then 2v, then 3v, then 4v, then 5v. And each step log in evoscan to make sure its giving you that voltage.

if its not then you know there is a grounding/offset problem... that you need to solve before using the analog method

You have to wire it up correctly obviously.

and then I like to run an AFR range of 10.0:1 (0v) -> 15.99:1 (5v)

however as a precaution before I rely on the numbers I go through each voltage and make sure im getting the right voltage in EvoScan...

ie set the analog output to 0v, then 1v, then 2v, then 3v, then 4v, then 5v. And each step log in evoscan to make sure its giving you that voltage.

if its not then you know there is a grounding/offset problem... that you need to solve before using the analog method

Thank you this is the info i was looking for. I have had so many problems with my lc-1. I actually had to send it back and they sent me a new one. You really gotta have a good ground with the lc-1 for it to work properly. It seems to be working correctly now or atleast i hope. I just got my car tuned with a FP red. The tune still needs some tweaking in the partial throttle areas tho.

So from 0v to 5v the AFR should be linear?

You have to wire it up correctly obviously.

and then I like to run an AFR range of 10.0:1 (0v) -> 15.99:1 (5v)

however as a precaution before I rely on the numbers I go through each voltage and make sure im getting the right voltage in EvoScan...

ie set the analog output to 0v, then 1v, then 2v, then 3v, then 4v, then 5v. And each step log in evoscan to make sure its giving you that voltage.

if its not then you know there is a grounding/offset problem... that you need to solve before using the analog method

So you dont have a gauge hooked up to the wideband? Since your hooking the wideband signal up to the rear 02 sensor? Can we hook the analog 1 signal up to the rear o2 sensor (.1v - 1v)?

LC1 has 3 outputs, serial, analog1, analog2

so I could have a gauge AND rear02 hooked up if I want.

rear02 accepts a 5v signal

LC1 has 3 outputs, serial, analog1, analog2

so I could have a gauge AND rear02 hooked up if I want.

rear02 accepts a 5v signal

Oh thank you. Right now my 5v signal is hooked up to my gauge and the narrowband signal is hooked up to my rear O2 sensor. How would i hook up my gauge and my rear O2 sensor then if my rear O2 sensor requires the same signal as my gauge (5V)?

use LMProgrammer (part of logworks tools)

to reprogram the analog output to something useful :)

keep em seperate

use LMProgrammer (part of logworks tools)

to reprogram the analog output to something useful :)

keep em seperate

Hook the narrowband signal (.1v - 1v) (analog 1) to the gauge after i program the output (.1v=10.00 & 1V=16.99)?

nah I dont know what the gauge expects.. so dont touch the gauge analog signal...

nah I dont know what the gauge expects.. so dont touch the gauge analog signal...

Alright well i am lost now haha.

This comes from the lc-1 manual:
A. Interface and power cables with 6 stripped ends*:
a. Red 12V supply
b. Blue Heater Ground
c. White System Ground
d. Yellow Analog out 1, narrowband signal
e. Brown Analog out 2, 5V, wideband signal
f. Black Calibration wire
B. Serial In connection, 2.5mm stereo (female) marked as IN
C. Serial Out connection, 2.5 mm stereo (female) marked as OUT.

Right now, i have the brown wire (analog out 2, 5v) going to my AFR gauge and the serial out going to my laptop. How can i hook my LC-1 up to my rear 02 sensor and my AFR gauge if i have to use the same Analog 2 output? Just splice the connection? Wouldnt that mess with the voltage?

so use the yellow wire, but reprogram it in LMProgrammer to be a 5v output...

so use the yellow wire, but reprogram it in LMProgrammer to be a 5v output...

Oh shit my bad, i didnt realize you could change the voltage output. Sorry for my ignorance. Thanks Tephra!

no problems..

tree/forest and all that :)

great info thanks !

nice

just received my openport 2.0 in the mail today, ran it on my 2010 gsr and it doesnt recognize the rom image. i used the beta that was listed in the beginning of this thread. is there something im missing here? i checked and re-read and i dont think i am.

could this be the problem? "IMPORTANT - the OP2 now uses a custom driver I wrote for better speed and stability than the Microsoft usbser.sys driver. This allows for reduced latency and a cleaner installation as well. *** This means that initially you must do a full EcuFlash and J2534 / driver install so that all of these components will work together. OLDER ECUFLASH AND OP20PT32.DLL VERSIONS WILL NOT WORK WITH THE DRIVER. **"

just received my openport 2.0 in the mail today, ran it on my 2010 gsr and it doesnt recognize the rom image. i used the beta that was listed in the beginning of this thread. is there something im missing here? i checked and re-read and i dont think i am."

Do you have the correct definition files downloaded? if not go to goldenevo.com and download them to your rom folder in ecuflash program files

i dont think i do - it said it didnt recognize my rom from the current list of definitions. since i didnt download any additional def's - i probably dont. lol
ill go there now and check - i just so happened to have bookmarked that site a couple weeks ago when i was researching this. :)

use goldens ROM id finder

use goldens ROM id finder
now THAT, i dont see... i see all the definitions and i found the one for my car and am about to paste it into the metadata folder, but i dont see an id finder...

now THAT, i dont see... i see all the definitions and i found the one for my car and am about to paste it into the metadata folder, but i dont see an id finder...

http://goldenevo.com/romcheck.php

cool! thanks!

ok, so just ran ecuflash and came up with this as the very last line. [20:22:23.928] Unable to find parent metadata 55570005

thats the one from golden evo. however, it did pull up all my info under rom info this time. it wouldnt do that before.


ok edit** i downloaded the base, which was 55570005 and saved that to the folder instead and it worked perfect. now to go do mode 23 and the rest.
im excited! lol i feel like a kid with a new toy.

Those addresses are for the 2010 USDM cars. All the roms that start with 55.

You need:

23808766 Load
2380873E 2ByteRPM
23808712 PSIG / Boost
23808A43 Knock Sum
23808890 STFT
23804573 LFTF Idle
23804575 LTFT Cruise
238088A1 LTFT in use
2380876C Load (MIVEC) and (Timing if IAT GT 75F)
238086F1 TPS
238094F9 Accel Pedel Position
238089FF TimingAdv
23808B4B ActiveWGDC
23808651 Intake Air Temp
23808637 Coolant Temp
23808657 Manifold Air Temp
2380A934 IPW
23808F48 MAF Volts
23809422 INVVT (Target)
2380942E EXVVT (Target)
2380945A INVVT (Actual)
23809466 EXVVT (Actual)
238087DF Speed
238086E7 Battery
2380A8F9 Barometer
23808A49 knock_adc_processed
2380A92B knock_base
2380A927 knock_var
2380A92D knock_change
23808A57 knock_dynamics
2380812D knock_flag
23808661 Front O2
23808665 Rear O2
238045C5 Cruise Light
23808B49 WGDC Correction


Take off the "23" on all those if you are using the stand alone logger.

Where/how would I get a list of the above logging addresses for the most recent 2008 USDM MR ROM, #52690024? Using Mode 23, btw.

Thanks!

Those come in EvoScan. But if you want a list like that for any rom, feel free to email me.
golden at goldenevo.com

Email sent.

So if I use the beta version of ECUFlash, and upgrade the firmware of the tactrix cable, will I still be able to log with a laptop using EvoScan? I guess I'm asking if I'd be able to use standalone logging as well as laptop logging.

So if I use the beta version of ECUFlash, and upgrade the firmware of the tactrix cable, will I still be able to log with a laptop using EvoScan? I guess I'm asking if I'd be able to use standalone logging as well as laptop logging.


My computer might just be acting weird but after I installed the beta Ecuflash and updated the firmware my stable version of Ecuflash could no longer see the OpenPort and neither could EvoScan. I haven't figured out if there is a way to downgrade the firmware or not ....

I'm getting incorrect values even though my evoscan settings match the logcfg on a 2011 GSR rom: 56890009 using mode23. Should I try turning off mode 23?

Hi folks.

While on the OpenECU forums, I came across an alternative method of logging my wideband analog 0-5V when using the Tactrix OP2.0 standalone logger.

Instead of using one of the vehicle's ECU ADC inputs (eg. disabling rear o2 sensor), the OP2.0 itself can be configured to do the job. It can sample voltage on OBD-II Pin 8. Apparently, this pin is unused, so it's a completely free analog logging input there for the taking.

Note that I didn't work this out or "discover" it. See below for original references. As this information doesn't seem to have made it across to the Evo/Ralliart owner space, here it is at last.


The original posts from dschultz... are here, on the RomRaider and OpenECU forums...

Hope this helps!

Cheers,

Rich

Would this work with any AFR with a serial data output, such as an AEM UEGO?

Would this work with any AFR with a serial data output, such as an AEM UEGO?

No,

But if you're looking for serial and standalone, you can use the mini jack port.

No,

But if you're looking for serial and standalone, you can use the mini jack port.

Oh, well that seems even easier then. I'd just need a serial to 2.5mm jack and I can log AFR to the sdcard along with all the other ECU parameters? Sorry, newb here learning all I can.

Anyone successfully logging a 2010 SE ROM with the stand alone logger?
I used the logcfg.txt file at the beginning of the thread and got it to log but the addresses were wrong so the values were whacky. I plugged in the values that I saw in evoscan and now I get nothing when I try to log...

Here's what I have in my logcfg.txt file


; uncomment the line below to minimize the information written to logcfg.out
; this will greatly decrease the startup time to begin logging if you already
; have a working logcfg.txt without any problems
;
; debug=noout

; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work

; this sample logs using the KWP2000 ReadMemoryAddress command over the ISO15765, which works
; for CAN based mitsubishis that have had their ROMs modified to allow the use of this command.
; this command is also known as "mode23" on some forums. since this command reads directly from
; ECU memory, the paramid addresses used are different for different ROM versions. the following
; example is for the USDM EVO X ROMs in the 526800xx series.




paramname=RPM
paramid=0x80875C
databits=16
scalingrpn=x,3.90625,*

;paramname=PSIG
;paramid=0x80872e
;databits=16
;scalingrpn=x,0.0483675,*,14.5,-

;paramname=Timing
;paramid=0x808A1F
;scalingrpn=x,20,-

paramname=Knock
paramid=0x808a63

;paramname=LoadFuel
;paramid=0x808784
;databits=16
;scalingrpn=x,0.3125,*

;paramname=IPW
;paramid=0x80aa88
;databits=16
;scalingrpn=x,0.001,*
;sampgroup=1

paramname=TPS
paramid=0x80870D
scalingrpn=x,100,255,*
sampgroup=1

;paramname=MAF_Airflow_gs
;paramid=0x8087f8
;databits=16
;scalingrpn=x,0.02,*
;sampgroup=2

;paramname=MAF_Volts
;paramid=0x808F50
;databits=16
;scalingrpn=x,0.0048875855,*


paramname=Speed_mph
paramid=0x808F78
scalingrpn=x,1.243,*
sampgroup=2

;paramname=ActiveWGDC
;paramid=0x808b53
;scalingrpn=x,0.5,*
;sampgroup=1

;paramname=WGDC_Correction
;paramid=0x808b51
;scalingrpn=x,0.5,*,64,-

;paramname=LTFT_Idle
;paramid=0x804573
;scalingrpn=x,0.1953125,*,25,-
;sampgroup=2

;paramname=LTFT_Cruise
;paramid=0x804575
;scalingrpn=x,0.1953125,*,25,-
;sampgroup=2

;paramname=STFT
;paramid=0x808898
;scalingrpn=x,0.1953125,*,25,-
;priority=2

;paramname=RearO2AFR
;paramid=0x80934e
;databits=16
;scalingrpn=x,0.008671875,*,10,+

;paramname=IAT
;paramid=0x80866d
;scalingrpn=x,1.8,*,48,-
;sampgroup=2

;paramname=CTS
;paramid=0x80863F
;scalingrpn=x,1.8,*,40,-
;sampgroup=2

;paramname=IDC
;paramid=0X808746
;databits=16
;scalingrpn=IPW,RPM,*,1200,/

;paramname=MATS
;paramid=0X808672
;scalingrpn=x,1.8,*,48,-

;paramname=Battery
;paramid=0x8086EF
;scalingrpn=x,18.75,*,255,/

;paramname=BoostError
;paramid=0x808B50
;scalingrpn=x,128,-,2,/

paramname=Gear
paramid=0x80886E
databits=16
scalingrpn=x,22.6,/

;paramname=IntakeMIVECTarget
;paramid=0x80942E
;databits=16
;scalingrpn=x,4096,-,0.01953125,*

;paramname=IntakeMIVECActual
;paramid=0x809466
;databits=16
;scalingrpn=x,4096,-,0.01953125,*

;paramname=ExhaustMIVECTarget
;paramid=0x80943A
;databits=16
;scalingrpn=x,4096,-,0.01953125,*

;paramname=ExhaustMIVECActual
;paramid=0x809472
;databits=16
;scalingrpn=x,4096,-,0.01953125,*
;-------------triggers---------------
;
; note that parameters must be previously defined
; before defining triggers using them
;
; triggers allow you to control when logging starts and stops
; this example sets up triggers such that logging only occurs
; when the engine is running (RPM > 0)
;
; triggers consist of some evaluation of the form [trigparam] [condition] [value]
; and a resulting action which is done if the evaluation is true

;paramname=CruiseLight
;paramid= 0x8045C5
;databits=1
;offsetbits=5
;isvisible=0
;priority=2

;conditionrpn = CruiseLight,1,==
;action = start

;conditionrpn = CruiseLight,0,==
;action = stop



;----------------inno----------------
type=inno
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.

;paramname = inno.afr
;paramname = inno.lambda

You have to uncomment (remove the semicolons) the trigger lines otherwise it'll never start logging:

paramname=CruiseLight
paramid= 0x8045C5
databits=1
offsetbits=5
isvisible=0
priority=2

conditionrpn = CruiseLight,1,==
action = start

conditionrpn = CruiseLight,0,==
action = stop

^ right that is if I want to log off the cruise control...I just want the logging to be constant if I have the cable plugged in...

Sent from my DROIDX using AutoGuide.Com Free App

^ right that is if I want to log off the cruise control...I just want the logging to be constant if I have the cable plugged in...

Sent from my DROIDX using AutoGuide.Com Free App
I'm pretty sure you will still need to set some kind of trigger, even if it's something like rpm > 0

^ from the OP:

8 - Triggers

Now the fun stuff. This section allows you to specify WHEN you want the adapter to start logging. Unfortunately, I only have confirmed USDM ROM triggers, but if you have something that doesn't work, get in touch with me and I'll try to find the address. Obviously, choose one method and put it in your logcfg.

Log All the Time
If nothing is specified (or everything is commented out), the logging will start when the car is turned on, and stop when the car is off. This is great for track days, finding out your LTFTs, or just because you don't want to fiddle with buttons. This is also good because it doesn't require any additional logged parameters, so this is what to use if you want the fastest of fast logging.

^ from the OP:

8 - Triggers

Now the fun stuff. This section allows you to specify WHEN you want the adapter to start logging. Unfortunately, I only have confirmed USDM ROM triggers, but if you have something that doesn't work, get in touch with me and I'll try to find the address. Obviously, choose one method and put it in your logcfg.

Log All the Time
If nothing is specified (or everything is commented out), the logging will start when the car is turned on, and stop when the car is off. This is great for track days, finding out your LTFTs, or just because you don't want to fiddle with buttons. This is also good because it doesn't require any additional logged parameters, so this is what to use if you want the fastest of fast logging.

In that case uncomment the debug=noout line and it should create a file that will tell you what's wrong