So who wants their ECU's "Chromed"?

[Greg E]

well if he is taking care of you then that is different, I just see a lot of people waiting around that could be running happy on v1.

Wraith needs to wait.

...a few more days.

[Kx1984]

Wraith needs to wait.

...a few more days.

[dyter]

I redid the test with Android Torque with mut3 over OBD2 (mode A0)
I create a knock PID A026, almost works, I have a return of the ECU but Torque does not display the result
Today there are no solution for wiew knock on Android, for me KnockSum is the most important preparation before if you want safe your motor

[Greg E]

I redid the test with Android Torque with mut3 over OBD2 (mode A0)
I create a knock PID A026, almost works, I have a return of the ECU but Torque does not display the result
Today there are no solution for wiew knock on Android, for me KnockSum is the most important preparation before if you want safe your motor

The easiest way to make it work is to just change PID 0B to reference knock sum instead of MDP. It's already setup to read the data unscaled. I have to sit down and locate this pointer. Unfortunately I'm scrambling right now on the release of V2 for this week and the NA version of Chrome. All while putting in 60 hour work weeks at my job. It's gonna be a bit before I can sit down and figure this out.

V2 does support the knock CEL which will give you the indication of knock real time on the dash. Even though the concept of Torque is nice, the OBD2 protocol is difficult to manipulate and very slow. This is why I haven't played with it for logging purposes. Evoscan is far superior and this is why I push everyone to use it.

Until someone can come up with a MUT Bluetooth dongle, we have to deal with logging via laptop.

[dyter]

Yes Knock CELL is better for reponse time instead OBD2
I have Tactrix 2.0 with microSD for fast logging

I am eager to try the V2 !

[Greg E]

Ya know I've never played with the microSD logging feature of the cable... One of these days I'll try it out!

[Chris@Rvengeperformance]

I have a thread on that standalone tactrix logging, but it is not up to date with 2.0.

[dyter]

Try this, it's work perfect for me and log all at 8 times / second, it's too fast !


; 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 MUT-II protocol over the K-line, which works
; for many mitsubishis, including the EVO 8 and 9

;----------------mut2----------------

type=mut2

; you can also set an OBD pin to a voltage, ground, or a high impedance state
; the first number is the OBD pin number, the second number is the pin voltage with the following values:
;
; 8000-18000 : voltage in millivolts for OP2 Rev C and earlier
; 5000-25000 : voltage in millivolts for OP2 Rev D and later
; -1 : set pin to high impedance (default state)
; -2 : pull pin to ground
;
; keep in mind that if you are applying a non-zero voltage to more than one pin, all of those voltages
; must be the same

; the following setpinvoltage sets OBD pin 1 to ground, which is needed to enable logging on older Mitsubishis
; it is commented out as it is not needed for newer models (e.g. EVO 8/9)
;

setpinvoltage=1,-2

paramname=TPS
paramid=0x17
scalingrpn=x,0.39215686,*

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

conditionrpn = TPS,10,>
action = start
;
conditionrpn = RPM,7000,>
action = stop

paramname=KnockSum
paramid=0x26

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

paramname=InjPulseWidth
paramid=0x29
scalingrpn=x,0.256,*

paramname=AirFlow
paramid=0x1A
scalingrpn=6.25*x

paramname=2ByteLoadRAW02
paramid=0x02

paramname=2ByteLoadRAW03
paramid=0x03

paramname=FFUELTRIMLOW
paramid=0x0C
scalingrpn=0.1961,x,*,-25,+

paramname=FFUELTRIMMID
paramid=0x0D
scalingrpn=0.1961,x,*,-25,+

paramname=FFUELTRIMHIGH
paramid=0x0E
scalingrpn=0.1961,x,*,-25,+

paramname=FSTFT
paramid=0x0F
scalingrpn=0.1961,x,*,-25,+

paramname=RFUELTRIMLOW
paramid=0x4C
scalingrpn=0.1961,x,*,-25,+

paramname=RFUELTRIMMID
paramid=0x4D
scalingrpn=0.1961,x,*,-25,+

paramname=RFUELTRIMHIGH
paramid=0x4E
scalingrpn=0.1961,x,*,-25,+

paramname=PrimaryO2Front
paramid=0x13
scalingrpn=0.01952,x,*

paramname=PrimaryO2Rear
paramid=0x3E
scalingrpn=0.01952,x,*

;----------------aem----------------
; the "ascii" channel type can listen on any protocol for incoming numeric text
; the default protocolid is 9, which corresponds to the 3/32" jack receive-only serial port
; the default baud rate and setting are 9600,N,8,1. all of these can be changed for other scenarios

; the ascii channel considers anything other than the characters {'0'-'9','+','-','.','E','e'} to be a
; delimiter between different numbers. furthermore, the carriage return and line feed characters are
; considered to mark the beginning of a new row of data. you can sample data from a particular column of
; numbers by choosing a paramid starting at 1 which indicates the column number

; in the case of the AEM UEGO, there is simply one column of data, and it is already scaled appropriately

type=ascii
paramname = AFR
paramid = 1

[iceorphen]

finally ready to install this and i drove myself crazy trying to figure out why the bits wouldnt turn on/off when i put in 00 or 01..


"[" and "]" are my new best friends -.-

[dyter]

My car doesn't cycle to 14.7 at idle, my AFR display 18.6 it's LEANER
At cruise AFR is at 16 - 18
My closed loop don't work correctly why ?
I have nothing changed exept a swap ECU ph1 to VR4 Clone (injector is stock 360cc)

My log: http://mornantautosport.free.fr/3000...s/log0001.xlsx