yep!

Yeh it's pretty difficult to really know if its correct. But as far as I can see from the code its right

 

yea the only reference I have is a similar Evo 9 with the same mods, making a certain amount of power on our dyno on pump 91, with approx the same IDC's.

 

ok I just looked at the MAP reference I talked about b4.

Unfortunately it's not a straight ADC

The formula is:
MAP = ADC_MAP * 2.69 + 0.5

So based on that you get a lot less resolution, and because its only single byte that means your max is very restricted too

 

tephra, have you been able to contact Hamish about this? Or is he MIA as usual......

 

Thanks tephra! Here's a dumb question. What are the units for the MAP formula you posted? I assume the max value ADC_MAP can return is 255, so the max value for MAP is 686.45. How many PSI is that? Also, is ADC_MAP returned from CAN 6-0 (which you posted as the MAP parameter earlier)? Thanks!!

 

SiC - yes on MSN.

LaXGSR - ahhh, I think the JDM3bar is using 0.19347-14.5 to get ADC_MAP into PSIG.

What is returned is ADC_MAP * 2.69 + 0.5.

So as you can see its fairly useless

 

Anyone find any new CAN ID's lately?

What coding would I enter into my XML file to get Boost logging assuming ~14.5 psi was atmospheric? I know it will be clipped at around 22-23 psi but that is fine for spoolup testing.

Thanks!

 

Nothing solid yet, I was working with Hamish last night (let him connect to my car remotely) and he found some bugs, reprogrammed Evoscan, etc. but still far from getting anything solid. He also tried to enable the Mode23 in Evoscan but it didn't want to connect. He said he found the problem with Mode23 but we stopped there last night. Hopefully he'll be back on tonight so I can let him use my car/pc again.

 

lol, EvoScan is 100% based directly from the MUTIII scantool. How do you think it does what it does? thats right, it is information I got directly form the MUTIII scantool. Yes I have a MUTIII scantool available.

 

Anyone is successsfull using evoscan 2.9 for the X using mode 0x21?

(dont tell me to go mode 0x23, i cant right now)

the issues I have

1.- AirTemp/ Coolant temp are the same value??

2.- Load value does not make any sense 4727??

3.- Active WGDC is always 0?

4.- Airflow (g/s) always 0???

5.- According to this log I am running 40Kpa (6PSI) of boost at idle? I should be in vacuum no?

and there is some other params being empty as well..

thanx

Mart

 

You probably have the wrong scalings or MUT addresses. Check them against a normal MUT table (see the ecutuning wiki in my sig) and check the scalings against those for mode23.

You can also compare the address given in the mode23 section against the address that is in your MUT table to see if they are the same and change Evoscan or your MUT as necessary.

 

I am talking about mode 0x21 not 0x23!

Mart

 

I am telling you how to check your addresses for mode 21 against the ones that most peole use for mode 23!

Take a re-read.

 

well, I dont have some madz ida skillz

comparing CAN Pid (0x21) and raw addresses(0x23) is kinda of rough :/

Mart

 

You don't need IDA skills. I has none.

Find the item you are looking for in this table:
http://evoecu.logic.net/wiki/MUT_Requests

Lets try LTFTLo for my rom (52680022). I see it at MUT 0C. Look up the standard MUT request in the MUT table (in EcuFlash).

-I see 804573
-I look in evoscan and see 23804573 for the mode 23 request
-I compare back to mode 21 and should see request ID 0C

The circle goes around, all look correct. If the scalings match between mode 23 and mode 21 then that item is correct.