status of 2 byte load?
Apr 1, 2007, 09:22 AM
#167
Well, thanks to Eric I got the Rom patched and the ability to log the 2 byte load. I added the formulas to the logworks xml file and logged both the LoadCalc and the 2 byte load to see the difference.
In one of the logs I got a spike similar to the one Tephra posted about. But mine was at peak boost/torque. The other two logs I did were spikeless.
There is not that much of a difference in the numbers between the LoadCalc and the 2 byte load. The 2 byte load is in blue and the LoadCalc is in green. I am assuming that I did this correctly.
In one of the logs I got a spike similar to the one Tephra posted about. But mine was at peak boost/torque. The other two logs I did were spikeless.
There is not that much of a difference in the numbers between the LoadCalc and the 2 byte load. The 2 byte load is in blue and the LoadCalc is in green. I am assuming that I did this correctly.
Apr 1, 2007, 03:14 PM
#168
I finally had a chance to do a thorough comparison between 2-byte load and LoadCalc.
Below are the results of 5 logs that I did between yesterday and today. They are done at the same place and under somewhat similar weather conditions. The horizontal axis is the 2 byte load (ECU_Load) and the vertical axis is the rpm. The chart content is the LoadCalc. The numbers in the hexes are averaged and not the Maximum numbers.
You will note that the differences between LoadCalc and the 2 byte load ar not that large. At around 3500-4000 rpm the differences are bigger between the two loads, but as the rpms increase the differences decline.
Below are the results of 5 logs that I did between yesterday and today. They are done at the same place and under somewhat similar weather conditions. The horizontal axis is the 2 byte load (ECU_Load) and the vertical axis is the rpm. The chart content is the LoadCalc. The numbers in the hexes are averaged and not the Maximum numbers.
You will note that the differences between LoadCalc and the 2 byte load ar not that large. At around 3500-4000 rpm the differences are bigger between the two loads, but as the rpms increase the differences decline.
Apr 2, 2007, 04:41 PM
#172
Evolving Member
Join Date: Dec 2006
Posts: 276
Likes: 0
Received 0 Likes
on
0 Posts
-jjf
Apr 2, 2007, 05:05 PM
#173
http://www.innovatemotorsports.com/f...&postcount=110
At that time the Evoscan formual was the one to sue Battery voltage. Now MJ is using it in his logger as well.
Here is the formula
?Injector Scaling = inj_scale[513]
?i Name of Battery Voltage channel = battery[Battery_Voltage]
?i Name of Injector Pulse Width channel = inj_pulse[Fuel_Injector_Pulse_Width]
?i Name of AFR MAP channel = afrmap[AFR_MAP]
# injector latency
inj_latency = (-0.1026*battery)+1.8741
# engine load
calcload = 5 * inj_scale * (inj_pulse - inj_latency) / afrmap
MC(LoadCalc;%;0;500) = calcload
MJ is this the same as the latest one you have in your logger.
Apr 3, 2007, 08:43 AM
#174
Newbie
Join Date: Feb 2004
Location: Prescott AZ
Posts: 69
Likes: 0
Received 0 Likes
on
0 Posts
For those confused by the last 12 pages of this post, read this: https://www.evolutionm.net/forums/sh...92&postcount=1
Last edited by Titanium; Apr 3, 2007 at 08:51 AM.
Jul 11, 2007, 12:15 AM
#175
Hey MalibuJack, great work with MitsuLogger and all the other info you've contributed. I was looking at the Load Ignition and Load2 AFR in the requestID.xml file which use RequestID's 00 and 01, which I also use for the 2 byte loads. The Load Ignition and Load2 AFR by default are not logged. Is it ok for me to leave those in the file and also my 2 byte load request ID's, also 00 and 01, or will there be a conflict? If so, I will just comment out one or the other. Thanks!
Jul 11, 2007, 09:10 AM
#176
Evolved Member
iTrader: (38)
Join Date: Aug 2005
Location: NorCal
Posts: 555
Likes: 0
Received 0 Likes
on
0 Posts
Jul 11, 2007, 09:29 AM
#177
Got to agree with you 100%. I haven;t logged load calc since I got the 2 byte working. I did use it too the loadcalc to see difference with the cams since I didn't have any logs of the car without cams with 2 byte. Besides that I dont check it anymore at all
