Jump to content


  • Content count

  • Donations

  • Joined

  • Last visited

About obe

  • Rank

Profile Information

  • Gender
  1. EFI issue. K3.

    I notice you've got your throttle percentages quite large per load site, presumably you have small butterflies? If you find you're driving around alot on cruise between throttle 0 and 1 you can usefully reduce the initial percentages to say 2 percent between load sites for the first 3 or 4 throttle sites and gain a lot of extra resolution (if your throttle butterflies need it). You have the rpm sites at 200rpm initially, that's good for refining the map over small rpm changes, but your speed integer of 32 means that the adaption only occurs whilst the crosshair cursor is in the middle of a cell. This means you probably only have something like a 50rpm spread over which adaption is being learned, and the rpm scatter is likely to take the rpm outside those learning limits so set the speed_int to 127 and that will allow learning over the full width of each cell. You can turning on adaption for idle too rather than leaving it closed loop / not learning. Set the load_int to say 80 which allows learning though most of the throttle travel in any given cell, but not at the edges of the cell (I suggest this because f your 5 percent load site increments, that's quite a wide spread, but I'm used to large butterflies with a high rate of change of airflow per degree). Set the target afr to 0.5 to begin with, that means that if the afr reached during fuel trimming is 0.5afr rich OR weak of the target then an adaption number will be stored. This will give a coarse learned fuel map .. you can reduce that later as you refine your map based on the adaptions learned. I send cars out with the AFR target at 0.1 afr once the fuel map is nicely refined. I also set the after start delay to 60 seconds on the basis I dont want any adaptions occuring until I know the engine has stabilised after a startup. Hot fuel being purged from the engine bay and other heat soak and after-start fuelling stuff can influence the learned values so you want adaption to only take place when you know the engine bay and fuel system has had cool fuel and air through it after a hot restart. Similarly if your normal engine run temp is something like 80deg you can stop adaption until say 75deg, that way you don't have the influence of any warmup trimming taking place. You still have 7 percent of injection correction in your coolant table at 60 degrees, so best plan is to wait until youre close to thermostat temp before allowing adaption. Any fuelling changes that need to be made to the warm up tables then only occur in open loop operation and can't influence the adaptive table. There's a lot to look at, including the lambda signal smoothing and position of the lambda which influence what gain you might choose to use. If you're ever on your way south near sheffield let me know and I can talk you through some thing face to face which is always easier than trying to explain stuff on the net! Happy tuning though .. the emerald is quite intuitive really once you get to grips with it.
  2. EFI issue. K3.

    As regards your wish to run MAP sensing for load .. that's fine, but TPS is a far faster way to map the ecu esepcially if you want to visit a dyno and pay for mapping hours. As mentioned previously, every time you revisit a particular throttle position and rpm site the airflow is the same as the last time you visited it. Smilarly every time you revisit a particular manifold vacuum and rpm site the airflow is the same as last time you visited it. If it wasn't you'd never be able to map the fuel or ignition tables at all, the values required in each cell would be different if the "load" varied every time you revisited a particular cell. In actual fact the "load" is exactly the same each time you revisit any particular cell in the map. Are you UK based?
  3. EFI issue. K3.

    Reducing your rpm slots to 200rpm is a good move especially at say sub 3000rpm, but that will slow down your adaptive table learning unless you increase the allowed load site threshold. I suggest you set the load and rpm allowable threshold to 127 which will allow learning whilst you're anywhere inside a given load cell and give you a fair but coarsely adapted map, but at least will get you lots of cells populated in the adaptive table Also allow a wide afr tolerance, say 0.5afr. The way the emerald learns it's values is the ecu has to trim the mixture and then only when the mixture is within the allowed afr range will a value be learned. This means that you need to spend lots of time at any one rpm/throttle site for it to learn anything useful even with the allowable limits set very wide. Once you've got a fuel map that's trimmed up over as many sites as possible you can then reduce the afr allowed range to say 0.1afr, and the loadcell threshold to say 32 and then the ecu will refine your coarse map even further.
  4. EFI issue. K3.

    Point taken about time spent at any one load site .. especially important if you hold a load site for a length of time and the resulting chamber temperature increase brings about pinking which you'd previously missed if you were travelling through the load sites quickly. Fair point well made. On the dyno of course it's very easy to hold a load site and dial in the fuel and ignition required .. one point I often see with regards to timing (especially distributors) is to hold the car uphill and swing the dizzy until it pinks, then retard slightly. This is likely to put you too far advanced even if you retard it slightly from the point of pinking. By the time the engine is pinking you're already well past the minimum best timing to make the power. In the absence of any test equipment though it's likely the best method for many people and has been used for decades for setting up timing of course
  5. EFI issue. K3.

    Hi all first post so bear with me on forum etiquette etc please You don't need MAP sensor to get the engine running properly, TPS is an excellent way to map the car and far quicker and easier to get a very good base map on TPS than using a MAP sensor. You do need a good throttle spindle to TPS sensor mechanism though, any play in the system will result in airflow changes that aren't picked up as a throttle signal change at the ECU. This is a particular issue at small throttle positions where rate of change of airflow is at its greatest. I have a dislike for innovate widebands, too unreliable. My preference is for AEM .. 180 pounds off ebay and so reliable actually map using one on my dyno. On the subject of load, whenever you visit any combination of throttle angle v revs the airflow is the same as the last time you visited it (atmospheric conditions excepted) , whether you're going uphill or downhill is irrelevant . Hello to all