Open Issues ToDo
Q: Has anyone experienced problems with poor table lookup performance?
Bill, im very intrested in this problem, is this something you also see on the pre-compiled (recent) releases ? I know we have had some issues with different avr-gcc versions in the past, make sure you are using the recommended version (see WinAVR), but anyway thanks for the report i will look into this - DB
A guy here in Sweden has reported a similar problem but related to ignition. With a steep ignition map in the idle range he said that he got a strange spark behavior, he claimed a problem with the interpolation but never made a report that allowed us to recreate the problem. I suspect that this can be related. -Jörgen
Jorgen - we too saw the problem initially several months back while trying to use timing controlled idle. Bill
I have installed pre compiled firmware .53. The firmware has a problem interpolating in both x and y as can be seen by
http://www.lolachampcar.com/images/53%20map.pdf
http://www.lolachampcar.com/images/firm53%20rpm.pdf
http://www.lolachampcar.com/images/53%20map%20and%20rpm.pdf
http://www.lolachampcar.com/images/53%20VE%20Table.pdf
I have used unrealistic VE values to highlight the abnormality and to ease my understand of which cell values are being used in the averaging at which times.
if ((engine.rpm * 100) > engine.rpm_vhr) engine.rpm -= 1; this fixes the problem where the index is choosen from an rpm on a cell, say 50 for 5000 which "picks" VE from 5000 and 5500 rpm bins and yet the weighting is based on 4996 rpm and a range of 4500 to 5000 rpm. Put differently, the index and thus VE values are based on rpm while the weighting is based on rpm_VHR and these differ when rpm_VHR is within 100 rpm of a cell location. I have tested this fix and it removed the problem for rpm.
I am still working on the KPA lookup problem.
An example of how CWL, CWH, AWEV, AWEV_Temp..., and AWC affect cranking and afterstart can be found at MembersPage/BillHart/CrankingAfterStart.
Recent Questions:
MembersPage/BillHart/ProblemHistory for older issues that have been resolved.
Projects Underway
MembersPage/BillHart/WinMobileLogger Win Mobile platform to Fat32 memory card logger. Looking for SIPR examples, if any, to ease the adding V3.3 query to Win Mobile code.
- [VR_Emulator] is a parallel port based Op-amp circuit that provides a plus or minus pulse about zero to emulate a VR sensor. You build the Basic routine to generate the crank (and cam)input wave form you need. Drop me a note if you need my QB code as a starter.
- we usually use stereo soundcard nowadays. It has many advantages, like processor overhead is small, amplitude can be varied, code is not hard to port between platforms, and it can even work without any executable (wav-s can be played with standard tools).
MembersPage/BillHart/LoggingDongle anyone interested in a small relatively inexpensive logging dongle?