1) OK, I think I have a good idea of what all would be going on in it. Thanks. Now I just need to call a couple of the local tuners in my area and see how comfortable they are with VEMS since the whole reason I am going stand-alone is that none of the local guys can deal with M1.7 and my WOT maps need some work (and I want better throttle response, but that's secondary).
2) Understood. I think that throttle response HAS to improve with a more modern ECU. The 1995 US-spec M3 I drove has a similar plenum/TB setup and the response is like lightning in comparison.
3) That's what I figured. Since this sounds like it will be a custom PCB, would it be possible to run some WBO2 traces either to the factory pins or to 5 unused ones and have jumper headers inside for the customer to choose with?
4) Indeed, it is an old and simple system. No CANBUS nonsense, just analog signals really. I have scoped a bunch of other stuff including the Motronic's tach output signal, the fuel rate output signal and the vehicle speed input signal. One of my goals with whatever stand-alone I go with is to have the instrument cluster be fully functional (and yes, I am aware that the MPG gauge is sort of superfluous lol...but I am going for a very OEM++ type build). Since VEMS has lots of spare outputs, how hard would the following 2 signals be to generate for the instrument cluster?
--1) Tach signal: Signal is idle at ground, goes to 9.0V for 1.4ms twice per crank revolution. So, two 1.4m high-pulses per revolution. Can VEMS be programmed to do this? The voltage may or may not be important, so I will mes with a signal generator and see if 5V and/or 12V pulses work properly too.
--2) Fuel consumption rate: Signal is idle at 8.1V, goes to ground for 1.6ms after each injector firing event ends. So, one 1.6ms low-pulse per injector event. Can VEMS do something like this with a spare GPIO? Again, not sure how important the voltage is and I can confirm with a signal generator.
5) What sort of Check Engine Light control ability does VEMS have? In CA, they check to see if the CEL turns on in accessory mode, and that it is off when the car is running, so I need it to appear to be working if I want to be able to register the car lol.
At this point I know that I am being a pain, so no worries if all of this is superfluous. It's obviously not required to make an M42 run well with VEMS, and it also means a lot more PCB layout effort for you. I'm sort of anal about wiring and that sort of thing, and it is highly likely that I will just need to build my own "PnP" stand-alone ECU from either a VEMS board, or MS3Pro.
Here are some general ideas for nice-to-have features (in my OCD mind anyway):
a) 2 additional injector outputs connected to the 5mm JP pins adjacent to the 2 factory ones so that people that want to run sequential just need to crimp some JPT terminals and run a couple of wires. Then it just becomes a software setting to use those.
b) Fuel rate output pin on the connector hooked up to a spare GPIO for those that want to mess with it.
c) Tach output pin on the connector hooked up to a spare GPIO for those that want to mess with it.
d) Vehicle speed input is connected (web searches indicate that the factory E30 signal is no problem)
d) Traces and jumpers for the option of running the WBO2 through the factory harness (and the user has to install the extra JPT terminal and wire).
e) All other spare Inputs / GPIO's / driver outputs connected to unused 2.8mm and 5mm (drivers) JPT pins.
Thanks again for all of the time to deal with my nagging, and more so for actually working to bring M42'ers a PnP solution. As it is now, it sounds like what you are planning will be great for 95% of M42 guys that want stand-alone solutions!