Hope someone can help, my wideband worked fine then a day later im getting this error. AEM ERROR: conversion from string "1v.7" to type "Double" is not valid. the "1v.7" will change as the numbers on the wideband itself changes. Also in evo scan it will come up right for a split second then nothing. i checked the wiring, tried another laptop, uninstalled and reinstalled evoscan and still the same error. Any help would be great

 

up!! help please!

 

Just wanted to update that I figured out my problem with 2-Byte Load and finally had a chance to log and prove it. I changed the 2-Byte Load formula (0.3125*x) in EvoScan with the formula for 2-Byte RPM (1000*x/256). Felt like an idiot when I figured that out.

 

Question: How does the ecu determine when to switch from the high to low octane maps? Based on knock i would imagine.... If so, what and where is that threshold? I am on SD using Rom 941…
Thanks in advance!

 

It is not an on/off switch. The ecu will begin to interpolate between the high and low maps if you have prolonged knock. This percentage is logged via the octane flag. At 100% it is using the full high octane map. As it drops down in percentage that is the percentage of the low octane map that it is using.

So at any given rpm/load cell if your high octane map shows 20 timing and low shows 10 and the octane flag is reading 80% then your actual timing should be around 18 plus whatever timing is being pulled at the time due to the knock (roughly 1 degree for every 3 counts) so if your hitting 9 counts at this point then that would drop you down another 3 degrees so roughly 15.

 

I have downloaded and installed almost every version of evoscan and about to give up on trying to get DTC's with it. I Installed and uninstalled them trying just about everything I can find on the internet. I am now out of luck I guess.

Info: Initialize Vehicle ECU...
Info: OBDII Connecting...
Info: Initializing At 5 baud...
Info: Timer: -14.7967999999998ms
Info: PC CPU 5baudrate 1824ms
Info: QPFreq: 1558857
Info: CPU Timer Factor Applied: 0
Info: Initialization Complete...
Info: OBDII Sync Byte Received.
Info: Keybyte Response: 0x08 0x08
Info: Waiting for vehicle ecu...
Info: Arithmetic operation resulted in an overflow.
Info: Check DTCs Complete.

Arithmetic operation resulted in an overflow.


___________________________________

This is what I get every time. New 1.3u cable that is connected I have read and flashed the new tune to the ecu.

Anyone?

Thanks
Tim
CAN WE GET A %&#*$ FIX FOR EVOSCAN V2.9!

 

03lances, thx for the input!

On a side note, my evoscan alot of times skips the data its suppose to record...for example...i do a 3rd gear pull from 3 to 7k and it only records upto 5k...any idea what maybe the issue? loose connection maybe? anything on the software side need adjustment?
Thx

 

hello jack
first i want to know what is tephra mod? and i have a problem logging load,A/F ratio, and boost on my evoscan what i understood the i have copy/paste an xml that have that options can you please help me with it? my rom ID is 88590014 USDM evo 9

thank you

 

For load, try using the following in your evoscan Display=Load1Byte, request = 41, function = 1.5*x
For AFR, you will need a wideband sensor, and you will need to log it thru the ecu (OBD port) or hard-wire it into a USB serial cable ...etc
Boost, you will need one of those omni 3 or 4 bar sensors (or other brands) to be able to log thru evoscan.

I also recommend you checking out this series of videos that explains some of the stuff if not all mentioned above.


https://www.evolutionm.net/forums/ec...hramod-v7.html
https://www.evolutionm.net/forums/ec...ging-help.html
https://www.evolutionm.net/forums/ge...-aem-uego.html
https://www.evolutionm.net/forums/ec...og-output.html
https://www.evolutionm.net/forums/ec...-load-log.html
https://www.evolutionm.net/forums/ec...evo-8-9-a.html

 

thanx alot detroit pistins
but the post u posted about the tephra mod i cant find my rom ID can i use any one similar ??

 

I think you can use 88590715.

 

Yep, 8859 would be the way to go with the USDM 9's

 

Really late reply on this sorry. If it randomly cuts off I would say a loose connection or possibly a driver (computer driver not you ) issue when connected and logging.

 

I ended up figuring out the issue, it was hitting the "space bar" on the keyboard too quickly after finishing the run. I guess I needed to give it few more seconds to buffer the data before saving.

ps. for those that didn't know, hitting the space bar is another way to stop logging.

 

thank all for you help