James' Civic Rebuild Thread + High Power ER Motor Theory
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
Made some awesome progress last night, worked out all of the analog data acquisition stuff, so with a bit more circuit reverse engineering I can work out where all the raw analog values are stored, which will help a lot with getting rid of fuel cut and things Might have fuel cut removed within the next 2 weeks actually. Shame I don't have a going car to test it on
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
Just re-assembled my commented code into a form that can go back into the ECU for the first time and compared it to the file I read off the ECU. The good news is that they are exactly the same, this means I havn't made any errors anywhere while commenting and havn't changed the program at all while tidying it up Good news.
Now when my new chips get here I can get straight into testing...in my driveway
Anyone want to loan me a city.....
Now when my new chips get here I can get straight into testing...in my driveway
Anyone want to loan me a city.....
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
Mike_NZ wrote:I'll be down in Palmy from the 9th - 15th of May for grad, so you can have a play with mine then.
This is some pretty exciting stuff! Good work.
If you can't wait that long... you could fix your car??
Long time no see man, hope its going well
Be mean to try out some stuff on your city then, but I think Ill leave you to play with your own tho
I heard you and Roz had a bit of a chat about my delayed repair, good things take time mate, and this is gonna be real good
-
- Moderator / Donating Member
- Posts: 1217
- Joined: Sat Feb 21, 2004 9:31 am
- Location: Christchurch, New Zealand
bigelboe wrote:Just re-assembled my commented code into a form that can go back into the ECU for the first time and compared it to the file I read off the ECU. The good news is that they are exactly the same, this means I havn't made any errors anywhere while commenting and havn't changed the program at all while tidying it up Good news.
Now when my new chips get here I can get straight into testing...in my driveway
Anyone want to loan me a city.....
I have a couple of spare ecu's you could chip and send back down, but might be a waste if you haven't perfected it
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
HyperBlade wrote:bigelboe wrote:Just re-assembled my commented code into a form that can go back into the ECU for the first time and compared it to the file I read off the ECU. The good news is that they are exactly the same, this means I havn't made any errors anywhere while commenting and havn't changed the program at all while tidying it up Good news.
Now when my new chips get here I can get straight into testing...in my driveway
Anyone want to loan me a city.....
I have a couple of spare ecu's you could chip and send back down, but might be a waste if you haven't perfected it
Yeah I have some spares too, but the changes are going to be pretty minor to start with so it would be really tedious sending ECU's around.
If you could get access to a chip burner I could just post modified Binaries up here for people to try, then youd just have to burn them and poop them in the ECU.
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
Double checked the value and its definately boost cut.
Map sensor B goes from 0-5 Volts, and is read by an 8 bit analog to digital converter. This means it can have 256 different values including zero. So 5/256 = 0.01953 Volts per step, and boost cut happens at like 3.22 Volts so 3.22/0.01953 = 164.864 and the value stored in the routine that I thought was boost cut is 165 so Im positive now Im right now. I should be getting the gear to burn some new chips next week so it will be just in time to try on mikes beast.
Also, now that I know how to stop injection, I can prtty easily implement some other cool features like a lower rev limit for launching, and an actual rev limiter!
Map sensor B goes from 0-5 Volts, and is read by an 8 bit analog to digital converter. This means it can have 256 different values including zero. So 5/256 = 0.01953 Volts per step, and boost cut happens at like 3.22 Volts so 3.22/0.01953 = 164.864 and the value stored in the routine that I thought was boost cut is 165 so Im positive now Im right now. I should be getting the gear to burn some new chips next week so it will be just in time to try on mikes beast.
Also, now that I know how to stop injection, I can prtty easily implement some other cool features like a lower rev limit for launching, and an actual rev limiter!
-
- Forum Addict
- Posts: 609
- Joined: Mon Apr 01, 2002 2:02 am
- Location: Newcastle, NSW Australia
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
Thats an interesting thought, I hadn't considered a different limit for cold running. I could also configure the PGMFI light as a shift lamp
Worked out quite a bit more last night, found all the stuff that works out where in the fuel maps to look, how it decides how many revs its doing and what its boosting etc. Found the code where it checks the inputs from the two map sensors and decides which one to use, and quite importantly I found where all the error codes get set, and how that is handled. It actually does a massive memory dump every time it throws an error code I guess for debugging.
Also found a routine that takes an altitude correction reading when you start the car up, uses Map A to measure atmospheric pressure. So if you are driving somewhere there is a large change in altitude turning your car off and back on part way might make it run better.
Worked out quite a bit more last night, found all the stuff that works out where in the fuel maps to look, how it decides how many revs its doing and what its boosting etc. Found the code where it checks the inputs from the two map sensors and decides which one to use, and quite importantly I found where all the error codes get set, and how that is handled. It actually does a massive memory dump every time it throws an error code I guess for debugging.
Also found a routine that takes an altitude correction reading when you start the car up, uses Map A to measure atmospheric pressure. So if you are driving somewhere there is a large change in altitude turning your car off and back on part way might make it run better.
- James
- Moderator / Donating Member
- Posts: 3092
- Joined: Wed Apr 09, 2003 1:59 pm
- Location: Putaruru
- Contact:
Took a lot of thinking but I finally worked out how it indexes the RPM side of the tuning tables, the RPM Bins it uses are:
500 600 700 800 999 1200 1399 1600 1999 2401 2799 3200 3599 3998 5000 5990
So there is also a column of manifold pressures for each of those RPM's
I can now change those rpms, so If anyone wants to rev their city up to like 7000rpm I can give you Tables for it
Now to work out the MAP side of things so I can get some tuning going for boost pressures higher than 15psi!
500 600 700 800 999 1200 1399 1600 1999 2401 2799 3200 3599 3998 5000 5990
So there is also a column of manifold pressures for each of those RPM's
I can now change those rpms, so If anyone wants to rev their city up to like 7000rpm I can give you Tables for it
Now to work out the MAP side of things so I can get some tuning going for boost pressures higher than 15psi!
-
- Moderator / Donating Member
- Posts: 1217
- Joined: Sat Feb 21, 2004 9:31 am
- Location: Christchurch, New Zealand
Who is online
Users browsing this forum: No registered users and 69 guests