Mitsubishi Lancer Evolution Forum banner

261 - 280 of 300 Posts

·
Registered
Joined
·
1,595 Posts
i changed my sd card and now i am getting a logcfg.out file but no logs.

any ideas?
Open the logcfg.out file with notepad or wordpad and see if there's any errors in there. If you log with evoscan I'd make sure that the parameters defined in the logcfg file match the addresses in evoscan.
 

·
Registered
Joined
·
934 Posts
Here is my .out file.

015: type=mrmacan
: name[type,8] value[mrmacan,0,0.000000]
016: ;-------------parameters-------------
017: paramname=RPM
: name[paramname,16] value[RPM,0,0.000000]
018: paramid=0x80875C
: name[paramid,17] value[0x80875C,8423260,0.000000]
019: databits=16
: name[databits,22] value[16,16,16.000000]
020: scalingrpn=x,3.90625,*
: name[scalingrpn,18] value[x,3.90625,*,0,0.000000]
021: paramname=LoadFuel
: name[paramname,16] value[LoadFuel,0,0.000000]
022: paramid=0x808784
: name[paramid,17] value[0x808784,8423300,0.000000]
023: databits=16
: name[databits,22] value[16,16,16.000000]
024: scalingrpn=x,0.3125,*
: name[scalingrpn,18] value[x,0.3125,*,0,0.000000]
025: ;paramname=LoadMivecTiming
026: ;paramid=0x80878A
027: ;databits=16
028: ;scalingrpn=x,0.3125,*
029: paramname=Timing
: name[paramname,16] value[Timing,0,0.000000]
030: paramid=0x808A1F
: name[paramid,17] value[0x808A1F,8423967,0.000000]
031: scalingrpn=x,20,-
: name[scalingrpn,18] value[x,20,-,0,0.000000]
032: ;paramname=Barometer
033: ;paramid=0x80AA4D
034: ;scalingrpn=x,0.07252,*
035: ;paramname=PSIG
036: ;paramid=0x80872e
037: ;databits=16
038: ;scalingrpn=x,0.0483675,*,14.5,-
039: paramname=PSIG
: name[paramname,16] value[PSIG,0,0.000000]
040: paramid=0x80872e
: name[paramid,17] value[0x80872e,8423214,0.000000]
041: databits=16
: name[databits,22] value[16,16,16.000000]
042: scalingrpn=x,0.058575,*,14.94948,-
: name[scalingrpn,18] value[x,0.058575,*,14.94948,-,0,0.000000]
043: paramname=Knock
: name[paramname,16] value[Knock,0,0.000000]
044: paramid=0x808A63
: name[paramid,17] value[0x808A63,8424035,0.000000]
045: ;paramname=AFRMap
046: ;paramid=0x80890D
047: ;scalingrpn=1881.6,x,/
048: ;paramname=AccelPedalPosition
049: ;paramid=0x8095FD
050: ;scalingrpn=x,32,-,0.5059,*
051: paramname=TPS
: name[paramname,16] value[TPS,0,0.000000]
052: paramid=0x80870D
: name[paramid,17] value[0x80870D,8423181,0.000000]
053: scalingrpn=x,0.392157,*
: name[scalingrpn,18] value[x,0.392157,*,0,0.000000]
054: ;paramname=MAFCalcs
055: ;paramid=0x808F88
056: ;databits=16
057: ;scalingrp=x,0.006104,*
058: paramname=MAPCalcs
: name[paramname,16] value[MAPCalcs,0,0.000000]
059: paramid=0x8087CE
: name[paramid,17] value[0x8087CE,8423374,0.000000]
060: databits=16
: name[databits,22] value[16,16,16.000000]
061: scalingrp=x,0.006104,*
: name[scalingrp,0] value[x,0.006104,*,0,0.000000]
unrecognized option [scalingrp] at line 61


I am using the same definitions as what i had last year.
 

·
Registered
Joined
·
2,903 Posts
Discussion Starter #263
It's telling you what is wrong!

It should be scalingrpn, not scalingrp for your MAF and MAPCalcs.
 

·
Registered
Joined
·
934 Posts
that is the only thing wrong?

Edit:

That is the only thing wrong with it. Its working now.
 

·
Registered
Joined
·
1,421 Posts
Hey guys,

I've tried every LC1 setup ive seen in this thread and cannot get it to log. My LC1 is set up and wired the exact same as weebles but the coding he used didnt work so we tried the rest of them with no luck.

I am also getting .out file but it didnt list an issue like it did for rrkpitt15.

I notice the number changes at the end of the paramid from 1 to 2 and that worked for some of you guys. Can i just start changing that number to see if it works or is that just a waste of time?

Im quite the noob when its comes to this formula/logging shite!

Thanks in advance for any help!

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


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

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

·
Registered
Joined
·
653 Posts
I also failed to get my LC-1 logging like that, standalone. I spent ages. It could possibly have something to do with the OP2.0 firmware revision I'm running... or I could just be a donkey.

In the end, I gave up on serial digital logging standalone, and instead wired up "pin 8" analogue, and logged via the OP2.0 inbuilt ADC. There are threads/posts about it around the traps... over there on EvoM, and right here on EvoX (post #168 in this very thread).

Rich
 

·
Registered
Joined
·
1,421 Posts
Hey Richard thanks for the info! finally got around to setting this up last night. I was able to get the OP 2.0 to read my LC1 but the #'s are off... did some reading and it appers to be a formula issue.

I had tried this set up from your original post below and it logs great just the #'s are not in AFR. I opened up LMprogrammer and attempted to change the voltage like you mention in your post and fucked it right up lol. Had to recal just to get the gauge to read properlly again. I Read through the openecu link and tried another formula in the OP2.0 and the #'s changed but stil not the correct AFR values.

I have attached a log to show that it is reading and getting lots of data but the formula calc must be off or something. Can you have a quick look? The attached log is using the x,0.002,*,9.6,+ formula.

Thanks for any and all help!

;----------------adc----------------
type=adc ; log from built in ADC channels
paramname=AFR
paramid=8 ; paramid is pin number on OBD connector
; valid pins are 8 and 16
; values are pre-scaled to millivolts
scalingrpn=x,0.002,*,9.6,+ ; here we scale to volts



;----------------adc----------------
type=adc
; log from built in ADC channels
paramname=voltsparamid=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
 

Attachments

·
Registered
Joined
·
1,421 Posts
So i was able to get the formula set up and it appers to be loggin correctly. upon further inspection of the log my AFR's are not flucuating as they should in the log when thorttle is applied.

i will try and mess around with your voltage set up in LMprogrammer and let you knw if i sort it out

Thanks!
 

·
Registered
Joined
·
653 Posts
Good luck!

Rich
 

·
Registered
Joined
·
6,693 Posts
I got the inno stuff to work on my first try for a customer. Note that he has a special cable that plugs the innovate into the tactrix. (I have never seen the setup in person.)

I put the following in his config:

;----------------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 lambda
; 0x0102 LC-1 #1 AFR
; 0x0201 LC-1 #2 lambda
; 0x0202 LC-1 #2 AFR
; 0x0301 LC-1 #3 lambda
; 0x0302 LC-1 #4 AFR
; (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 = 0x0101 ; get lambda from first LC-1
scalingrpn = x,14.7,* ; scale to an AFR

; since the MTS bus does not describe the contents of the aux channels, you need to know what they are
; and how to scale them. in this example we assume you have a TC-4 connected and you want to view the
; thermocouple readings in celsius, two of which are in the EGT mode, two in CHT mode

;paramname = mytc4.egt1
;paramid = 0x0001
;scalingrpn = x,1.06842619,*

;paramname = mytc4.egt2
;paramid = 0x0002
;scalingrpn = x,1.06842619,*

;paramname = mytc4.cht1
;paramid = 0x0003
;scalingrpn = x,0.293255131,*

;paramname = mytc4.cht2
;paramid = 0x0004
;scalingrpn = x,0.293255131,*
 

·
Registered
Joined
·
2,903 Posts
Discussion Starter #273
I have recently been using AEM serial logging through the 2.5mm port in the Tactrix.

Which is probably something I should write up as well, since it is pretty nice to have. The LC1 works as well, as it can take the actual serial output from the gauge and add it to the logs.
 

·
Registered
Joined
·
120 Posts
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://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...

Code:
;----------------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
CAn you elaborate on this process just a tiny bit? I have an obd2 extension cable, should i merely cut open the shielding, find which wire is connecting the 8 pin and then just cut it and tap into the TACTRIX side of the cable? Also it looks like pin 8 is unused for subies but what about our cars? are you certain that pin 8 is the proper pin to use?
 

·
Registered
Joined
·
653 Posts
The way you explained it is exactly the way I did it - i patched in via the OBD extension cable. Pin 8 seems to be unused on our vehicles, so is free for this logging style.

Rich
 

·
Registered
Joined
·
120 Posts
The way you explained it is exactly the way I did it - i patched in via the OBD extension cable. Pin 8 seems to be unused on our vehicles, so is free for this logging style.

Rich
Ive located pin 8 and will splice into it with my LC1 output wire, can you provide me with the code to make it log AFR value rather than volts?

And do i need to use lm programmer? I have the output voltage setup for my DB gauge so can i just put the scaling values the same in logcfg.tx?

Heres my DB gauge scaling- 0v = 7.35 A/F and 5v = 22.39 A/F
 

·
Registered
Joined
·
653 Posts
Sounds like you're almost there!

There are two analog outputs from the LC-1. You can scale each one differently in LM-Programmer.

I wouldn't use 7:1 -> 22:1 or your accuracy will be junk. The OP2.0 adc is a bit jiggly. What I did was program...

0V = 10.0:1
5V = 15.0:1

...with this in the "logcfg.txt":

Code:
;----------------adc----------------

type=adc                     ; log from built-in ADC channels

paramname=WideBandAF
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,*,10.05,+ ; Here we scale from millivolts to AFR.
                             ;
                             ; The LC-1 is configured to output:
                             ; 0V = 10:1
                             ; 5V = 15:1
                             ; 
                             ; Includes a 0.05V "fudge factor", as the OP2.0
                             ; ADC reading is ever so slightly low.

;--------------------------------
If you look carefully, I've actually got the OP2.0 interpreting "plus 10.05" instead of "plus 10.00". I decided to do this after doing a simple calibration check...


I went into LM-Programmer, and configured the LC-1 to output 0.00V for ALL mixtures. I then read the voltage at the OP2.0 via standalone logging.

I repeated this for 1.00V, 2.00V, 3.00V, 4.00V and 5.00V to verify for certain that my REAL readings matched expectations. You may not need to go so obsessive-compulsive, lol. Just try 0V, 2.5V, 5V. ;)

From your logfile output, you'll then see how to tweak your evaluation formula so that the correct AFR appears in your logfiles.


As I noted, the OP2.0 ADC circuit isn't stupidly accurate. The best I can hope for is +/- 0.1 AFR, but that's good enough. With a broader AFR range (eg. 7:1 to 22:1) it would be far less accurate. That's why I went 10-15.

Hope this helps!

Rich
 

·
Registered
Joined
·
120 Posts
Couple questions, if you do 10-15 you wont see any values above/below those values, so afr logging will only be useful for wot tuning for the most part correct?

How would the text file look if i kept my parameters the same? I am not sure i have the correct cable/drivers to hook up lm programmer at the moment but would like to get logging asap so for now i may just run with my current values. the only 2 values in your text file scalingrpn i see are .001 and 10.05, o would i substitute my values and do stomehing like this?
Code:
;----------------adc----------------

type=adc                     ; log from built-in ADC channels

paramname=WideBandAF
paramid=8                    ; paramid is pin number on OBD connector.
                             ; Valid pins are 8 and 16.
                             ; values are pre-scaled to millivolts.
scalingrpn=[B]x,0.003,*,7.35[/B],+ ; Here we scale from millivolts to AFR.
                             ;
                             ; The LC-1 is configured to output:
                             ; 0V = 10:1
                             ; 5V = 15:1
                             ; 
                             ; Includes a 0.05V "fudge factor", as the OP2.0
                             ; ADC reading is ever so slightly low.

;--------------------------------
 

·
Registered
Joined
·
653 Posts
Code:
scalingrpn=[B]x,0.003,*,7.35[/B],+ ; Here we scale from millivolts to AFR.
Yes, that should work! But you may have more jitter in the graph than you'd like. It'll do for a starting point.

AFR from 10.0:1 to 15.0:1 is all you'll ever need, even for part-throttle. Can't see why you'd want to see leaner. If you do need to see leaner, go for something like 10.0:1 to 20.0:1 - keep the range as tight as you can for more accurate logging.

Best of luck!

Rich
 
261 - 280 of 300 Posts
Top