Author Topic: Dual VE Table Firmware????  (Read 5560 times)

Offline Sprocket

  • Hero Member
  • *****
  • Posts: 867
  • BHP: 29
Dual VE Table Firmware????
« on: September 18, 2007, 12:36:17 am »
I put this topic in this general discussion forum for now as that is all it is at the minuit.

Looking around the files in the Megatune/ firmware package for VEMS, i keep coming across various files and comments of dual table code. Some of this i suspect is actualy megasquirt left overs?? if so why is it still there so late on in the VEMS time line. Anyway ::)

The reson I'm asking about this - with VEMS having dual WBO2 and EGT, dual VE tables would be a logical step, and, would be very useful in  getting the siamese inlet port injection system to work on the Austin Rover A Series engine.

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

Jean Belanger, working the code for Megasquirt in his spare time, Is president of Opal RT Technologies Inc Montreal http://www.opal-rt.com/index.html , the leading provider of distributed real-time simulation and hardware-in-the-loop testing systems So its not entirely a enthusiat project, as such, there is some professional input here.

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. I dont have the time at the moment but 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!! Starting with a dual active table firmware would be one step closer. Does this exist in one form or another?

Here is the general theory of the siamese code, though not by any means the only one or the right one.

For starters, courtesy of Dave Coxon, here 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

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, we 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, 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 for the injection engines with minimal valve over laps for use with Speed/Density metering, which is a bonus.

Please discuss this as at some point i will be coming back to this to actualy have a go at it, more input the better

If we were to get this workable, there is a whole other sales area just waiting for it to happen.

Sprox
« Last Edit: September 18, 2007, 12:44:22 am by Sprocket »

Offline Sprocket

  • Hero Member
  • *****
  • Posts: 867
  • BHP: 29
Re: Dual VE Table Firmware????
« Reply #1 on: September 24, 2007, 09:19:29 pm »
Bit of a grey area then :-\

LOL, why do i always have to complicate things :D

Offline Bat

  • Full Member
  • ***
  • Posts: 169
  • BHP: 8
    • Trucking site
Re: Dual VE Table Firmware????
« Reply #2 on: September 24, 2007, 11:26:20 pm »
Hi,
So what downsides have you encountered with the wet manifold system?
I'm with you on the above....
Cheers,
Gavin :)
VEMs Authorised Installer / Re-seller. K head kits for A series now available!

WB/EGT gauges. Click here for customers write-up 

Visit www.doyouneedabrain.co.uk

Offline Sprocket

  • Hero Member
  • *****
  • Posts: 867
  • BHP: 29
Re: Dual VE Table Firmware????
« Reply #3 on: September 28, 2007, 10:48:49 am »
There seems to be a conflict :o

Trying to gauge interest in this - http://www.turbominis.co.uk/forums/index.php?p=vt&tid=180051

I have spoken to Jean Belanger, and he is coming round to the VEMS, but one thing is still clear that every one hates the Wiki ::)

Offline Bat

  • Full Member
  • ***
  • Posts: 169
  • BHP: 8
    • Trucking site
Re: Dual VE Table Firmware????
« Reply #4 on: September 28, 2007, 06:54:24 pm »
Hi,
Come on spill the beans about the wet manifold!  ::)
I've voted for VEMS!
Although I'm not sure I should make this comment as I've not purchased a VEMS yet, but I will anyway! :o
I think the Wiki is a major setback when trying to persuade someone to use VEMS instaed of MS.
They look at a difficult to navigate/find info Wiki vs. the massive amount of well laid out information and help.
Although in the Mini community we have some Sprox support to make use of, I think people tend to look for "official" support when they are going to spalsh out on an ECU?
Cheers,
Gavin :)
VEMs Authorised Installer / Re-seller. K head kits for A series now available!

WB/EGT gauges. Click here for customers write-up 

Visit www.doyouneedabrain.co.uk

Offline Sprocket

  • Hero Member
  • *****
  • Posts: 867
  • BHP: 29
Re: Dual VE Table Firmware????
« Reply #5 on: September 30, 2007, 02:16:31 pm »
Well the problem with the SPi set up is the Low Z injector. Problem with the wet manifold is the acceleration enrichments. Work is being done on the firmware for the latter, and ive got a peak and hold injector driver board on its way to me to sort out the Low Z injector. other than that nothing. If you were building up a custom set up, packaging on a wet manifold becomes an issue. The MPi manifold is nice and tightly packaged.


Ok so possible way round this, but its by no means cheap. Buy two Genboards and run cylinders 1/4 fueling, all the ignition, stepper control and outputs from one board and then cylinders 2/3 fueling from the second board. I dont know how well the inputs paralleled to the two boards would work. Tuning could get complicated with two PCs, though i suppose you could use the addressable chip to address the boards and maybe just use one pc running two Megatune aplications on the same serial bus????

Injection point can be shifted using the cam sync settings on each genboard, though this is a fixed point, it would get you running.