MembersPage/TrifanCatalin (2013-01-08 17:41:53)

Using Vemstune 1.3.1 ,VEMS 3.6 (written on the order receipt and mainboard) but Vemstune recognise it like v3.3 (firmware and bootloader is same for all, so that is OK), firmware 1.2.2.

Engine code: S50B32

Specs:

Started the engine in stock form, nothing changed, i only attached my ecu adapter socket to the car's original ecu socket.

I wanted , for the start to verify vanos functionality.

I have problems in getting a stable secondary and third trigger, also, secondary and third triggers tries to follow target cam advance maps, but not with very good success. I have manually put cams in max advance and retard position , and took note of them, after that i have made cam target maps.I have attached leds to solenoid outputs, and they are very unstable, even if in close proximity of cam target. I suspect an unstable trigger signals.

I attach two trigger logs, one only cranking and one at idle, a config file, and a log.

[Uploaded files location]

In the Vemslog you will see also, that around 1800-2000 rpm, i have very nasty fuelcut, i don't know the cause.

Use higher baudrate, like 115200 in triggerlog to raise the max RPM where it can capture all pulses

I am not very sure about VR sensors polarity, i have tried everything, and i do not have a oscilloscope to verify them.

Also a have seen in a DTA wiring instructions, that the Crank and exhaust cam (secondary trigger for vems) has the same polarity, but the intake cam sensor (third trigger) has inverse polarity. Can anyone confirm me that?