Notices

Evo X Logging

Thread Tools
 
Search this Thread
 
Old Jul 15, 2009, 01:55 PM
  #541  
Evolved Member
iTrader: (6)
 
nj1266's Avatar
 
Join Date: Nov 2004
Location: USA
Posts: 3,254
Likes: 0
Received 13 Likes on 3 Posts
Originally Posted by tephra
As posted in the other thread:

MAF airflow in g/s:

530400xx: 0x8087d8 (2byte)
526800xx: 0x8087e0 (2byte)

Formula is x * 2 / 100
Tephra or mrfred

Do you have the complete code in lb/min to include this in Evoscan mode 23? This is for the USDM models.

Thanks

PS: I want to thank you both for mode23 logging. It works like a charm. I have stopped using my beloved PCMScan to tune Evo Xs
Old Jul 15, 2009, 01:55 PM
  #542  
Evolved Member
iTrader: (6)
 
nj1266's Avatar
 
Join Date: Nov 2004
Location: USA
Posts: 3,254
Likes: 0
Received 13 Likes on 3 Posts
Evo4mad PLEASE fix the LM-1 wideband glitch in Evoscan ver 2.5/2.6. Everytime I lift off the gas for an extended period of time the LM-1 logging via Evoscan stops and never comes back. I have to re-start the log to get it to work again. I have told you about this a long time ago. I am currently logging with ZT2 and I prefer to log with the LM-1.
Old Jul 15, 2009, 04:05 PM
  #543  
Evolved Member
 
LaXGSR's Avatar
 
Join Date: Apr 2009
Location: US
Posts: 536
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by nj1266
Tephra or mrfred

Do you have the complete code in lb/min to include this in Evoscan mode 23? This is for the USDM models.

Thanks

PS: I want to thank you both for mode23 logging. It works like a charm. I have stopped using my beloved PCMScan to tune Evo Xs
The conversion from g/s to lb/min is 0.1323, so just multiply by that in the formula. Or to simplify, just use x * 0.002646 to get airflow in lb/min. I'd be very curious to see how much airflow you are logging just to double check it's the right formula.
Old Jul 15, 2009, 06:59 PM
  #544  
Evolved Member
iTrader: (6)
 
nj1266's Avatar
 
Join Date: Nov 2004
Location: USA
Posts: 3,254
Likes: 0
Received 13 Likes on 3 Posts
Originally Posted by LaXGSR
The conversion from g/s to lb/min is 0.1323, so just multiply by that in the formula. Or to simplify, just use x * 0.002646 to get airflow in lb/min. I'd be very curious to see how much airflow you are logging just to double check it's the right formula.
Do you have the FULL code that needs to be entered in the xml file? I do not know what to put in the xml file.

For example the formula for timing is this

<DataListItem DataLog="N" Color="" Display="Mode23 TimingAdv" LogReference="Mode23TimingAdv" RequestID="23808a07" Eval="x-20" Unit="deg" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-15" GaugeMax="50" ChartMin="-15" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

What would the formula for airflow in lb/min be?

Thanks

Last edited by nj1266; Jul 15, 2009 at 07:12 PM.
Old Jul 16, 2009, 08:08 AM
  #545  
Evolved Member
 
acamus's Avatar
 
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes on 2 Posts
MUT initialization in CT9A returns 4 bytes:
0x00 0x55 0xEF 0x85

MUT init reply bytes' locations in 53040010:
0000E300 ECHO_REPLY 0x00 - presumably
00040F84 Sync word 0x55
00040FC4 KeyWord #1 0xEF
00041034 KeyWord #2 0x85

so whole trick to get MUT communication is hidden in this code
Code:
00040D3C                 lduh    R0, @((pin83_changing_counter - unk_80C000), fp) 
00040D40                 cmp     R1, R1          
00040D42                 ldi8    R1, #1          
00040D44                 subx    R0, R1          ; r0 = r0 - 1 - C
00040D44                                         ; C = 1 if r0 < 0
00040D46                 bc.s    loc_40D8C       
00040D48                 subx    R0, R1          
00040D4A                 bc.s    loc_40DD0      
00040D4C                 subx    R0, R1          
00040D4E                 bc.s    loc_40DFC       
00040D50                 subx    R0, R1 || nop   
00040D54                 bc.l    loc_40F84       
00040D58                 subx    R0, R1 || nop   
00040D5C                 bc.l    loc_40FB0       
00040D60                 subx    R0, R1 || nop   
00040D64                 bc.l    loc_40FBC       
00040D68                 subx    R0, R1 || nop   
00040D6C                 bc.l    loc_40FFC       
00040D70                 subx    R0, R1 || nop   
00040D74                 bc.l    loc_41010       
00040D78                 subx    R0, R1 || nop   
00040D7C                 bc.l    loc_41080       
00040D80                 subx    R0, R1 || nop   
00040D84                 bc.l    loc_410B0       
00040D88                 bra.l   set_808c7c_to_0
Now who will be the first to sort/try it out?
I bet on tephra, but hamish is my second candidate

Last edited by acamus; Nov 4, 2009 at 10:05 PM.
Old Jul 16, 2009, 08:23 AM
  #546  
Evolved Member
 
LaXGSR's Avatar
 
Join Date: Apr 2009
Location: US
Posts: 536
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by nj1266
Do you have the FULL code that needs to be entered in the xml file? I do not know what to put in the xml file.

For example the formula for timing is this

<DataListItem DataLog="N" Color="" Display="Mode23 TimingAdv" LogReference="Mode23TimingAdv" RequestID="23808a07" Eval="x-20" Unit="deg" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-15" GaugeMax="50" ChartMin="-15" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

What would the formula for airflow in lb/min be?

Thanks
Here ya go...let me know how this works:

<DataListItem DataLog="N" Color="" Display="Mode23 Airflow" LogReference="Mode23Airflow" RequestID="238087e0" Eval="x*0.002646" Unit="lb/min" MetricEval="" MetricUnit="" ResponseBytes="2" GaugeMin="0" GaugeMax="50" ChartMin="0" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
Old Jul 16, 2009, 12:05 PM
  #547  
Evolved Member
iTrader: (6)
 
nj1266's Avatar
 
Join Date: Nov 2004
Location: USA
Posts: 3,254
Likes: 0
Received 13 Likes on 3 Posts
Originally Posted by LaXGSR
Here ya go...let me know how this works:

<DataListItem DataLog="N" Color="" Display="Mode23 Airflow" LogReference="Mode23Airflow" RequestID="238087e0" Eval="x*0.002646" Unit="lb/min" MetricEval="" MetricUnit="" ResponseBytes="2" GaugeMin="0" GaugeMax="50" ChartMin="0" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
Thank you sir for your help.
Old Jul 16, 2009, 03:40 PM
  #548  
Evolved Member
 
LaXGSR's Avatar
 
Join Date: Apr 2009
Location: US
Posts: 536
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by nj1266
Thank you sir for your help.
No prob! Hope you get some good results...
Old Jul 16, 2009, 04:20 PM
  #549  
EvoM Guru
Thread Starter
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
acamus - yeah I couldn't work that init code out...
Old Jul 16, 2009, 09:58 PM
  #550  
Evolved Member
 
acamus's Avatar
 
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes on 2 Posts
I do not know what edge detection is used raising/falling or both?

Presuming that changing counter is what the name is saying and only one side edge detection,
one has to send 0xAA 0xAA 0xAA 0xAA 0xAA, in order to get to the last line of above code.


So init reply shall look like 0xAA 0x55 0xEF 0x85.

What line is pin83 actually OBD PIN 7 or OBD PIN 8?
Unfortunately I do not have the ECU to play with, it is based only on disassy.

Last edited by acamus; Jul 16, 2009 at 10:47 PM.
Old Jul 16, 2009, 10:18 PM
  #551  
EvoM Guru
Thread Starter
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
K-Line
Old Jul 16, 2009, 10:43 PM
  #552  
Evolved Member
 
acamus's Avatar
 
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes on 2 Posts
If I would have the ECU, I would write application that is sending init codes 0xYY running from 00-FF, and observe the reply,
once I would get 0xYY 0x55 0xEF 0x85 reply that would be the init code.

Btw. I know we have the solution already, but I am trying to find the clean solution, working without Mode23 patch.

Last edited by acamus; Jul 16, 2009 at 10:47 PM.
Old Jul 16, 2009, 10:47 PM
  #553  
EvoM Guru
Thread Starter
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
yes Hamish tried that...

I actually think the "reflash" pin needs to be enabled for some advanced debuging (read mode23, reflashing, serial MUT, etc)...
Old Jul 16, 2009, 10:53 PM
  #554  
Evolved Member
 
acamus's Avatar
 
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes on 2 Posts
Tephra, you know we are so close, it is only one step to get it working,
I have been looking at the MUT code, it is exactly same just built for different processor.

Have you found variable that holds the L-line, reflash,
does it appear in that init routine?
Old Jul 16, 2009, 10:57 PM
  #555  
EvoM Guru
Thread Starter
iTrader: (6)
 
tephra's Avatar
 
Join Date: Feb 2007
Location: Melbourne, Australia
Posts: 9,486
Received 66 Likes on 42 Posts
I don't think its "L-Line"

If you trace back the mode23 stuff you will see it requires OBD-Debug (Mode0x10) to be set first.

AND then ontop it requires something else to be set, this can be traced back to a I/O pin - I think its in my disasm I sent you...

Trouble is I can't set a voltage on OBD PIN8 (the only other pin hooked to the ECU) because OBD Pin8 isn't a valid choice in J2345... weird!


Quick Reply: Evo X Logging



All times are GMT -7. The time now is 10:23 PM.