Question, ECU load determining accuracy
The "load" value that was in the xml was actually what I'd found previously, but it turned out it was my JDM/UK IX 3 bar map sensor! Gives a very close reading to load which is why it puzzled me!
The new load estimate as detailed in this thread cannot be done in the xml file as it cross references two data items. So Excel it is, and once verified or improved/replaced, MalibuJack may put it in his log reader I guess.
The new load estimate as detailed in this thread cannot be done in the xml file as it cross references two data items. So Excel it is, and once verified or improved/replaced, MalibuJack may put it in his log reader I guess.
-= HINT =-
If you're tired of checking/unchecking various boxes in Evoscan everytime you startup, open up the DATA.XML file using Notepad, then find the lines that are for parameters that you normally don't log and change DataLog="Y" to DataLog="N" for those parameters.
l8r)
If you're tired of checking/unchecking various boxes in Evoscan everytime you startup, open up the DATA.XML file using Notepad, then find the lines that are for parameters that you normally don't log and change DataLog="Y" to DataLog="N" for those parameters.
l8r)
Originally Posted by A418t81
Wait, I thought that the "load" value thats added with this XML WAS the calculated value and that AFRMAP was the decimal value. Do we still need to plug into Excel?
Originally Posted by MalibuJack
That load value is from an earlier thread.. It turned out that was the Map sensor.. Load would still have to be calculated using Excel, but when I release the new version of my log analyzer (the one that converts the files to work with data log lab) it will do the calculation for you, then it will be in the output file so you can look at it with something usable like Data log lab, or Excel..
Originally Posted by Ludikraut
-= HINT =-
If you're tired of checking/unchecking various boxes in Evoscan everytime you startup, open up the DATA.XML file using Notepad, then find the lines that are for parameters that you normally don't log and change DataLog="Y" to DataLog="N" for those parameters.
l8r)
If you're tired of checking/unchecking various boxes in Evoscan everytime you startup, open up the DATA.XML file using Notepad, then find the lines that are for parameters that you normally don't log and change DataLog="Y" to DataLog="N" for those parameters.
l8r)
Thanks so very much for this. I was getting so annoyed having to check and uncheck the boxes.
Originally Posted by MalibuJack
No it can occurr of the boost spikes at lower RPM..
note: this is with ~21-22psi of boost.
Last edited by ST; Aug 25, 2006 at 09:52 AM.
In order for the new formulas to give me load values that seem to be in the correct ballpark, I have to:
a.) adjust the constant to 3100 in Excel if using calculated load = abs(3100 * (IPW-0.4) / AFRMAP)
b.) adjust the constant to 3000 in Excel if using calculated load = abs(3000 * IPW / AFRMAP)
l8r)
a.) adjust the constant to 3100 in Excel if using calculated load = abs(3100 * (IPW-0.4) / AFRMAP)
b.) adjust the constant to 3000 in Excel if using calculated load = abs(3000 * IPW / AFRMAP)
l8r)
The new Data.xml file that Malibu posted is not working for me. I removed the original file and added the one from malibu, but everytime I run Evoscan with it I get and error message and the logging session starts and ends with no data logged. When I switch back to the original Data.xml file Evoscan works like before. I have no idea what is going on. Any help?
I've been looking at my latest set of logs, and the IPW based load calculations are nowhere near accurate enough, IMO. Even with adjusting the "constant", it still tends to be +/- 20% from the actual load on my car.
l8r)
l8r)
Originally Posted by nj1266
The new Data.xml file that Malibu posted is not working for me. I removed the original file and added the one from malibu, but everytime I run Evoscan with it I get and error message and the logging session starts and ends with no data logged. When I switch back to the original Data.xml file Evoscan works like before. I have no idea what is going on. Any help?




(just kidding).