Openport 2.0 logging via SD card
Jul 4, 2014, 10:56 AM
#17
Following should be in your logcfg-file:
;----------------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
;------------------------------------------
And then you need to connect your LC-1 to the OP2.0 by the stereo jack.
;----------------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
;------------------------------------------
And then you need to connect your LC-1 to the OP2.0 by the stereo jack.
Jul 4, 2014, 12:08 PM
#18
ok it logs but not the reading for the LC-1 are 0's throughout the entire log. My only guesses are:
1. could it be that i didn't install the beta version of ecu flash and do the licensing thing. do i need to do that? i'm using the latest version (1.44) and not the beta (1.34).
2.is there something in ecuflash that needs to be added to the evo7base or my other rom file (2004 96420008 evolution mt.xml)?
anyone have any ideas other than those that can help pinpoint the problem?
1. could it be that i didn't install the beta version of ecu flash and do the licensing thing. do i need to do that? i'm using the latest version (1.44) and not the beta (1.34).
2.is there something in ecuflash that needs to be added to the evo7base or my other rom file (2004 96420008 evolution mt.xml)?
anyone have any ideas other than those that can help pinpoint the problem?
Jul 22, 2014, 11:23 AM
#21
Evolving Member
Just want to note that in the load formula I posted above, it's setup with a scaling of 1.2
Ensure that is the same value you've inputted in 2 byte to 1 byte load factor. I had mine set to 1.4 in my rom yet 1.2 in the scanner and was wondering why I kept hitting boost cut lol! I was actually hitting much higher loads than what I was logging.
Ensure that is the same value you've inputted in 2 byte to 1 byte load factor. I had mine set to 1.4 in my rom yet 1.2 in the scanner and was wondering why I kept hitting boost cut lol! I was actually hitting much higher loads than what I was logging.
Thread
Thread Starter
Forum
Replies
Last Post
Jonathan Brito
Evo X Electrical / Audio / Security
1
Aug 5, 2016 02:16 AM