Load found on Evo
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
I looked for a zone that tripped up as the airflow reading clipped at max - ie a "high" byte for the airflow reading and couldn't find one. I also think from what I've seen that the bytes will be in the low-high order and adjacent at least with request IDs.
Originally Posted by jcsbanks
I wonder if you're logging wastegate duty cycle then at the same address? What other items would show this pattern I wonder?
My data.xml file just polls every location from 00-3F and puts them in columns with the same label, someone else needs to log the same I think on the other model variants. I'll post up the file in 5 hours when I'm home as it will save a bit of time (or a macro for you clever people, I just used cut and paste a lot and changed all the numbers LOL). When you have all 64 of them in a table you can get rid of the ones that don't move in a "loadish"
manner and we can start to home in on the values?
I love this stuff
My data.xml file just polls every location from 00-3F and puts them in columns with the same label, someone else needs to log the same I think on the other model variants. I'll post up the file in 5 hours when I'm home as it will save a bit of time (or a macro for you clever people, I just used cut and paste a lot and changed all the numbers LOL). When you have all 64 of them in a table you can get rid of the ones that don't move in a "loadish"
manner and we can start to home in on the values?I love this stuff
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Needn't post mine now, that will do nicely
Just been out and collected more logs. I'm still pretty convinced this fits for my car. The only place it doesn't really work is on over-run where you'd expect it to come to 20 or 30 on the load, and indeed the "load" figure I'm logging does, but the ignition timing doesn't come up that far. I suspect there are some over-run timing tables that we're not seeing. There appear to be some compensations during spool up as well, but timing being run usually is within one load zone's value, and often a direct hit.
Just been out and collected more logs. I'm still pretty convinced this fits for my car. The only place it doesn't really work is on over-run where you'd expect it to come to 20 or 30 on the load, and indeed the "load" figure I'm logging does, but the ignition timing doesn't come up that far. I suspect there are some over-run timing tables that we're not seeing. There appear to be some compensations during spool up as well, but timing being run usually is within one load zone's value, and often a direct hit.
John, I wonder if some of the difference is your JDM ECU. It has tables that no american ECU I have seen does. 4 HOT maps, the lean spool engage/disable, Maybe thats some of this difference?
Originally Posted by jcsbanks
Maybe Aaron, maybe also the American ECUs do have some of these tables...
That definitely looks like load or something very similar, like a mass airlfow/rev. But, I don't think the ECU outputs a mass airflow/rev value.
That's either load or something very closely related.
Hopefully I will get a chance to do this on my 05 today and see what I get.
Eric
That's either load or something very closely related.
Hopefully I will get a chance to do this on my 05 today and see what I get.
Eric
I'm not sure if you guys know Java or have ever looked at the DSMLink source code, but here is one of the Java files that sets up the ECU locations for the DSM.
The calc routines are then all separate files, like airflow/rev, mass airflow, etc.
Someone take a look at this and tell me what you think:
Eric
The calc routines are then all separate files, like airflow/rev, mass airflow, etc.
Someone take a look at this and tell me what you think:
Eric
Originally Posted by bez_bashni
It doesnt work on EVO.
It sure does. I know of about 10 people that use it.
The reason I posted the file was to see if any of the addresses correlated with the Evo ECU.
Eric