Let me know if you succesfully log with the 52360016 rom and what addresses you used to do it.

 

nope i couldnt get the logging to work. now my ecuflash wont work either im stuck with the stock boring tune!!

 

you must be getting and error?

 

the mode23 or evoscan wouldnt log anything when i used the 52360016 but when i tried to flash 52360018 back (my modidfied rom) it wouldnt work. see my other thread if you want more info

 

52370024_Evo_X_SST:

Normal MUT Table
0x3E394
autotransmission MUT table
0x98558 (16x16 items)

Should be the same as for autotransmission IX / VII GTA, I do not know what particular MUT RequestIDs mean or how they scale, but I believe once this information is out some tuning gurus will sort them out

 

I'm having a few issues here that i cant figure out. This is a 2008 US GSR. Im using evoscan v2.6 beta15. My rom id is 52680020. In the zip file attached is my data.xml that evoscan uses, the 52680020.xml file that i modified for mode23 logging and a log of a quick full throttle jab. I stopped the pull because i saw the values were not accurate so it did me no good.

Now to the issues:

1. When i check Mode 23 2-byte rpm and connect, it disconnects right away and in the event log it says: "Error: Conversion from string "&HLC" to type 'Integer' is not valid."
If i deselect this item i can log anything else thats checked except for items dependent upon 2-byte rpm being checked.

2. As you will see, my Mode 23 Throttle Posn reads over 100 when i go WOT. Same thing with the Mode 23 Accel Pedal Posn.

I havent seen anyone else having these problems. Any help would be appreciated. Thanks in advance.

 

Hey I finally got my keyscan USB to comport cable and when I tried hooking it up it didn't work. How did u set it up? Anything special I need to do?

I tried hooking the blue cable from the gauge to all the pins of the cable and nothing would read in hyper terminal. I tried every combination of ground and blue wires touching the pins and nothing. My previous set up involved a choped up com to com cable and then I had a USB to com connecting it to my computer. Hyperterminal read it fine. But evoscan had issues.

Also I tried to log IDC and evoscan would disconnect instantly. Any ideas?

 

Try the attached Data.xml file. This should make APP and TPS closer to 100% at WOT. I think the 2-byte RPM issue may be because of the IDC calc I stuck in the Data.xml file. Hamish hasn't responded to my question about whether "Calc" entries can be placed in the Mode23 area, I haven't had an Evo 10 handy to try it out.

 

lol, Last time I checked my calculator "LC" is not a hexadecimal number. Who set that up for you?

the only valid hex values on a calculator are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F

 

mrfred> you asked about calc? what formula did you use that was wrong? do you use msn messenger? I can help you fix any formulas you have.

Just use the [ ] characters as per usual, it definately still uses the EVAL() function in my code, otherwise the A*x+B would not work.

 

Thanks Ill try it after work.

I was using 2.6 beta 15. I downloaded it from your link in the other thread and used the installer. After it installed, i didnt modify anything. I installed it and within 5 minutes was in my car driving down the road. Clicked to start logging and that is what came up in the error log on the right. I quoted it exactly like it shows up on the error log.

 

I guess I'll have to install messenger. I'll probably try to contact you this evening (in my time zone). I think it will be around midday your time zone.

 

Thanks mrfred! The xml you provided brought my Accel Pedal Posn to around 101, and my TPS to about 96 under WOT. 2byte RPM works when IDC and IPW are not checked. When 2byte RPM, IDC and IPW, i get the same error i listed above:

"Error: Conversion from string "&HLC" to type 'Integer' is not valid."

 

What values do you get for APP and TPS when the car is stationary and idling? If you let me know this, I can fine-tune the APP and TPS conversion formulas a little more.

ok, it looks like EvoScan is not liking the "CALC" command in the Mode23 zone. The "&HLC" indicates that EvoScan is trying to convert "CALC" into an address, e.g. &HCALC. After thinking about it for a second, I've come up with a possible workaround. Try the attached Data.xml file when you get a chance.

 

Here is a log at idle. APP holds steady at 9.611764706, TPS bounces between -2.023529412 and -1.517647059. Ill load the new xml tonight and log it on my way to work tomorrow. I should have something for you by lunch time.