Any known of any succesfull setups for a flywheel based Bosch trigger setup.
Such as Porches and early BMW´s.
Most likely two VR sensors
116 + 1 Trigger
129 + 1 Trigger
130 + 1 Trigger
132 + 1 Trigger
- Gunni
- Are you sure that those 1xx numbers are trigger teeth? -Used to think that those are starter gear teeth and the +1 is the only trigger (?)
- Gunni -
Yes, the starter teeth are trigger teeth for the ecu to know the speed, the one trigger is to located the TCD and then the ecu can know the exact location from the starter teeth.
individual power :
What is the measurement exactly?
- the difference of time spent between 2 pulses exactly 1 event apart (eg. 120 deg in 6cyl, 180 deg in 4 cyl) minus the last similar data
I was thinking that whatever it is now it might be improved upon by having it calculate the time it should take from 0-90° (or an adjustable value) only and then report the delta time as crank angles.
- inside the ECU firmware it is stored in 4 usec resolution. Of course in VT it can be displayed in crankangle (maybe it is already multiplied with RPM, or the ini can be tweaked easily).
- note that there is no "it should take" value, as RPM can change continuously. That's why - as the closest thing - it's displayed compared to last measured value (better than the average of last few).
This would eliminate variation in a complete cycle due to other cylinders and concentrate solely on the firing cylinder. Then cylinders can be compared and misfires extremely clear and potentially knock could be determinable.
- it seems the current implementation already gets as close as possible
TPS accel enrichment :
The scale in Vemstune is what appears to be millivolts against time, but there is no channel that represents this for measurement only an actual dTPS/dTime, it would be ideal to convert the scales to TPS/Time as if one where to replace the TPS with another the tuning wouldn´t have to be replaced as well as being closer on similar engines with different TPS´s.
Lambda heater duty cycle monitoring.
i have on a few occasions had a situation where lambda isn´t read for quite a long time even if engine has been run up to temperature , 10minutes for instance. Any reason to this? I want to be able to monitor the Heater DC% to determine if the heater is actually on or not. Lambda then usually comes in but takes way to long.
Any update on this??
LSU 4.9 support?
Q: Is there support as Vemstune now suggest that there is ?
A: Currently LSU 4.9 is only supported with hardware modifications to v3, we are developing firmware to allow both LSU 4.2 and LSU 4.9 to be used on the same hardware, without modifications. When making sensor choice for current project, use LSU 4.2 until recommended otherwise.
ECU serial 17347
I ordered a M52 PnP.
This ECU has a black connector and a single board inside.
Is this correct for new M52 PnP ECUs?
I ask because when powered on the bench it doesn´t connect via Vemstune. I was only going to do a quick look at it and upload a base map and now I can´t even connect to it.
I have 12v power to pin 49 which is switched input and to 26 which is constant 12V. Grounds are as per M52 wiring.
Anything else that needs 12v for this to turn on?
There is a wiring fuss inside this ECU from VEMS, I´ll have to send it back.
Pin 49 - Switched 12v and Pin 54 are wired together
- are you certain ? (the ECU turns on when fitted to harness ? Withou ignition on ?) Direct wire should not be the case
- Pin49 (anode, diode >| cathode) powers pin54 and pin65 (HALL sensor supply),
- so the ECU should not be powered back from pin54 . (but pin54 would get power if not getting from other source).
Serial communications are intermittent to less than 10% success rate. I´ll be sending it [to ..., check address in shop freshly].