Vems v3.2 megatune
The ECU stops reading the PW, RPM and duty cycle after about 10secs on cranking, what causes this?
![vems v3.2 megatune vems v3.2 megatune](https://www.diyautotune.com/wp-content/uploads/wue.png)
However it still does not fire and removing a ignition lead and spark plug and earthing to the ending confirms that there is no spark. Is the VR sensor affected by the aluminium shroud?ĭoes the shield from the VR sensor need to connect to pin 7 rather than ground? SAW is a straight connection from ECU to EDIS module. The shield of the cable is connected to ground. The other wire of the pair is connected to pin 7 on the EDIS. The PIP wire from the ECU is connected to pin 1, there is a pair of cables within a shielded cable. The shielded cable is connected to ground, Does this need to pin 7. The wires from the VR sensor are connected to the correct pins on the EDIS module. I have a Ford Transit trigger wheel and the VR sensor (this is mounted in an aluminium housing the actual head of the VR sensor is surrounded by aluminium) is located with the smallest gap as possible. I have used the tooth and trigger logger on the diagonistics function on TS, and it indicates no missing tooth. When I turn the ignition key, the rpm number indicates over 20000rpm! And then drops to 0 rpm where by it stays reading 0. I have MAT, Coolant temp and MAP pressure working ok. The only difference is that there also seems to be data on channels 224-229, although they are not mentioned in the pdf.I have just wired up ms1 extra to a rover v8, however using Tunerstudio I can not get a true rpm signal. The signal from my ECU matches the protocol in the before mentioned pdf. The AIM signal is streamed out of the VEMS without the need of the "A" command to trigger the datastream. The developers of VEMS told me that the AIM signal is much better for datalogging etc. When I disable the AIM signal in the ECU, i can (very random) sometimes get the rpm and throttle pos. When I enable the AIM signal, nothing is working at all, and the dash just shows random wrong data on all channels. Because it's possible to turn the above protocol (AIM) on and off in the ECU. However I believe that he is wrong and you are correct. Kieran told me earlier that the Race Technology Vems interface is build for this protocol (AIM signal): I believe that you are correct regarding the info on the interface. I have contacted VEMS and asked for clarification on ECU setup and which versions of the ECU firmware this is compatible with.
![vems v3.2 megatune vems v3.2 megatune](https://i.imgur.com/4b5WrLAh.jpg)
What I am not clear on is which version of your ECUs this works with, and if there is any particular setup which is required by the user to configure the ECU.
![vems v3.2 megatune vems v3.2 megatune](http://docplayer.net/docs-images/66/55568939/images/39-0.jpg)
> Here is a list in the order of their arrival:
![vems v3.2 megatune vems v3.2 megatune](http://www.vems.hu/manual/html/images/ConnectingLCD.png)
#VEMS V3.2 MEGATUNE SERIAL#
> 2) Send character 'A' to VEMS over the serial port > 1) The standard baudrate is 9600 (can be changed). The VEMS ECU interface we have is designed to work with the following protocol: