######  
  ##  ## 
  ##  ## 
  #####  
  ##     
 ####    

         
### #### 
 ##  ##  
 ##  ##  
 ##  ##  
 ######  
     ##  
 #####   

     _    
    / \   
   / _ \  
  / ___ \ 
 /_/   \_\
          

         
   ##    
 ######  
   ##    
   ##    
   ##    
    ###  
         

 _______ 
(_____  )
     /'/'
   /'/'  
 /'/'___ 
(_______)
         
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
This page is all about the Siamese port problem experienced by the BL A series engine. This is not the only engine to suffer this problem but it is the only one of this design to have been fitted with fuel injection. The A series engine itself had been in production for over 50 years in various capacities and configurations. Rover streatched out its demise by firstly using the single point throttle body injection system, very similar to the Bosch Monojetronic, almost identical infact. This kept the emissions below the limits of the day. Later developments seen the Multi Point (twin Point) injection system. This is a very clever system that overcomes the siamese port problem of charge stealing. It utilised the Rover MEMS2J ECU used then only on the Rover KV6 series engines with dual lambda and cam sync. This system only ever seen use on the A series and is bespoke to it. Rover patented the siamese port injection design and theories and to date, no other engine has used this system to my knowledge. It was clear that after 2001 the aging 50 year old A series engine with its siamese inlet ports could not meet the ever tightening emissions standards, that production of the Car, the classic Mini, along with the A series engine ceased. So taking into consideration that there are thousands of production Minis fitted with the A series engine having siamese ports and fuel injection from 1992 through to 2001, also noting that the Mini tuning scene is getting ever bigger, with more people coming round to fuel injection rther than ripping it out on stiking a carb on it. I feel there is a reasonable demand to address this issue. History of the a series engine can be found here http://www.austin-rover.co.uk/index.htm?engineaseriesf.htm ---- The siamese port problem Firstly some links for some background There has already been much research and code done for this on the Megasquirt controller, though, the way i see it, is limitted by hardware. Discussion can be found here http://www.turbominis.co.uk/forums/index.php?p=vf&fid=32 here http://www.turbominis.co.uk/forums/index.php?p=vf&fid=33 and here http://www.turbominis.co.uk/forums/index.php?p=vf&fid=29 Most of the work on this so far has been done by Jean Belanger Courtesy of Dave Coxon (turbodave) of http://www.turbominis.co.uk , is the Rover patent appliction, which to my knowledge, the Mini MPi 1997 onwards, was the only car/ engine to run this system http://www.davecoxon.co.uk/A_SERIES_PATENT.PDF Marcel Chichak has done an amazing amount of physical testing with the DTA system, his work can be fond here, and is a very interesting read!! http://www.starchak.ca/index.htm#tech ---- I dont think VEMS is far off actualy working the siamese problem, it just needs the coding. I know nothing of the code side of things, though i can pick things up, its slow, and starting from the very first page of things is where i would have to start. After seeing the down sides of the SPi wet manifold system, though not unsurmountable, port injection does solve certain problems easily. Yet on the siamese ports it interjects other problems. Its also a bit of a challenge. I can see it working on VEMS fairly easily as the hardware is there, Its just the code!! Here is the general theory of the siamese code, though not by any means the only one or the right one. Basics of it are, cylinder pairs 1/2 and 3/4 share the same inlet port (siamese), inlet valve overlap is such that as one valve is starting to close, the other valve is starting to open. The result is, in a port injetion system, as one cylinder is close to the end of drawing on the inlet port, the second cylinder starts to draw on the same port. Getting the right amount of fuel into each cylinder starts to become vague. Rover got round this, 1 suspect, by shifting the injection points for each cylinder into a 'window' of valve opening whereby only one valve is open at any one time Other thoughts on this are perhaps the injection point is the middle of the calculated pulse width with dual tables firing the injector at different intervals (rather than all at the same point in the cycle). Wiring shows four injection drivers crossed over and commoned up to the two injectors, Mpi Crank trigger shows 4 missing teeth, two 180 degrees apart, ignition points? and the other two 180 degrees apart, but the second having a difference of 10 degrees so in reality 170/190 apart, injection points? Cam sync giving TDC#1 cylinder. In such a way that the pulse width looks as though it is one, you could then alter the pulse width between the tables so that the percieved injection point was shifting yet injection point stays the same(The Rover Mini MPi ECU was developed from the MEMSJ2 ECU used on the KV6 engine. This had dual Lambda and presumebly dual VE tables.) This way with dual Lambda pressent, you can tune the VE tables, rather than have dual active Lambda controlling the correction, so that if the middle cylinders are running rich and the outers lean, you can increase VE on the outer cylinders and reduce VE on the inner cylinders to balance out the AFR. In simple terms you have seperated the middle cylinders from the outer cylinders and given them their own VE tables. One other thing that can also help reduce this port robbing situation is the use of a scatter pattern cam, reducing port robbing issues, but not eliminating it. One of which already specificaly designed by Kent cams, the MD274SP, for the injection engines with minimal valve over laps for use with Speed/Density metering. The main problem with the speed denisty air metering is as most will know, large valve overlap cams cause inlet tract pulsing, and this is a major problem with the A series. The kent MD274SP cam is as wild as you can go with speed density on the A series, 246 inlet duration 276 exhaust duration. Not very wild and will give in the region of 100bhp on a 1400cc engine. Nothing special. On a side note, the maximum i have seen from the MPi system is 90bhp< wild cams seriously screw up the sequencial injection strategy. Clearly more room for improvement, the Rover ECU is holding it back!!! Add to that, people are wanting to put a turbo on this system as well!! Using a programable ECU to replicate the fueling strategy, but use Alpha N and to tune acordingly is the way forward. There are clearly some major issues with tuning a system like this such as running a pair of cylinders lean. I dont think there is anyone looking at this problem that doesnt already know this and are aware that setting up on the dyno is a must! ---- I have recently installed two wideband lambda sensors and EGT thermocouples onto the exhaust manifold of my Mini for some research. http://www.turbominis.co.uk/_photos/random-photos/697/4226.jpg One of the main reason I baught the VEMS was that it 'suposedly' has dual channel wideband. This is some what true, the hardware is there, i was advised that two FETS are required for these, and both are installed. Everything hardware wise is there, fair enough, But where is the code/ firmware? All i want to do for now is monitor the data from the second wideband channel, nothing else at this stage. It has been said that the outer two cylinders of the A series engine always runs lean on a carb or SPi set up. I find this difficult to understand, how can this be when the charge is evenly distributed as a mixture. I dont believe the outer cylinders to be running lean, but rather at a reduced VE to the inner cylinders as a result of the charge stealing caused by the valve overlap. ---- I have the hardware, and want the firmware simply to control and monitor the second wideband chanel. Can some one please help by compiling a one off firmware build adding the second wideband channel as a data logging point only. This is the first stage of development. I am more than willing to spend time on this. I have several people that I can fall back on for some of the tuning aspects of this, but need the tools to do it. Firmware is the key ;) ---- Back to MembersPage/Sprocket
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.