Race Technology

Hi there,

I use Dash2 and Video4 units in my car. It's connected to my Vems ECU with the race technology "Vems serial interface". The interface does not read the datastream from the ECU correctly. I've been in contact with race technology before, but haven't got any answers in a long time now! I've been asking the same questions to the developers of the Vems ECU and they confirmed me that the race technology Vems ECU interface does not work correctly. Here is a link to the topic: http://www.vems.hu/wiki/index.php?page= ... oody%2FAIM

They informed me that I need a race technology Mo-Tec interface, not the Vems interface, eventhough I use the Vems ECU. The Vems ECU is setup to use the same datastream as the Mo-Tec ECU's. Is there any way I can reflash my existing Vems interface to make it use the Mo-Tec protocols?

Thanks,

The VEMS ECU interface we have is designed to work with the following protocol:

>
> 1) The standard baudrate is 9600 (can be changed).
>
> 2) Send character 'A' to VEMS over the serial port
>
> 3) Now VEMS will send 49 characters.
>
> Here is a list in the order of their arrival:
>
> secl = scalar, U08, 0, "sec", 1.000, 0.000
> squirt = scalar, U08, 1, "bits", 1.000, 0.000
> engine = scalar, U08, 2, "bits", 1.000, 0.000
> barometer = scalar, U08, 3, "ADC", 1.000, 0.000
> mapADC = scalar, U16, 4, "Pa", 1.000, 0.000
> matADC = scalar, U08, 6, "ADC", 1.000, 0.000
> cltADC = scalar, U08, 7, "ADC", 1.000, 0.000
> tpsADC = scalar, U08, 8, "ADC", 1.000, 0.000
> batADC = scalar, U08, 9, "ADC", 1.000, 0.000
> egoADC = scalar, U08, 10, "ADC", 1.000, 0.000
> egoCorrection = scalar, U08, 11, "%", 1.000, 0.000
> airCorrection = scalar, U08, 12, "%", 1.000, 0.000
> warmupEnrich = scalar, U08, 13, "%", 1.000, 0.000
> rpmVHR = scalar, U16 14, "rpm", 1.000, 0.000
> pulseWidth = scalar, U08, 16, "ms", 0.100, 0.000
> accelEnrich = scalar, U08, 17, "%", 1.000, 0.000
> baroCorrection = scalar, U08, 18, "%", 1.000, 0.000
> gammaEnrich = scalar, U08, 19, "%", 1.000, 0.000
> veCurr = scalar, U08, 20, "%", 1.000, 0.000
> INTdwell = scalar, U08, 21, "mS", 1.000, 0.000
> INTspark = scalar, U08, 22, "", 1.000, 0.000
> iacPos = scalar, U08, 23, "%", 1.000, 0.000
> egt1ADC = scalar, U16, 24, "Deg", 1.000, 0.000
> egt2ADC = scalar, U16, 26, "Deg", 1.000, 0.000
> ebpADC = scalar, U16, 28, "Deg", 1.000, 0.000
> fpADC = scalar, U16, 30, "Deg", 1.000, 0.000
> misc1ADC = scalar, U16, 32, "Deg", 1.000, 0.000
> misc2ADC = scalar, U16, 34, "Deg", 1.000, 0.000
> misc3ADC = scalar, U16, 36, "Deg", 1.000, 0.000
> misc4ADC = scalar, U16, 38, "Deg", 1.000, 0.000
> latgtADC = scalar, U08, 40, "", 1.000, 0.000
> knock_cyl_0_knock_val=scalar, U16, 41, "", 1.000, 0.000
> knock_cyl_0_noise_val=scalar, U16, 43, "", 1.000, 0.000
> knock_cyl_0_adjust=scalar, U08, 45, "Deg", 0.250, 0.000
> knock_cyl_0_state = scalar, U08, 46, "", 1.000, 0.000
> status1 = scalar, U08, 47, "", 1.000, 0.000
>

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.

I have contacted VEMS and asked for clarification on ECU setup and which versions of the ECU firmware this is compatible with.

Martin

Hi Martin,
Thanks for your reply.
I believe that you are correct regarding the info on the interface. Kieran told me earlier that the Race Technology Vems interface is build for this protocol (AIM signal):
http://www.vems.hu/files/MembersPage/Na ... otocol.pdf

However I believe that he is wrong and you are correct. Because it's possible to turn the above protocol (AIM) on and off in the ECU. When I enable the AIM signal, nothing is working at all, and the dash just shows random wrong data on all channels. When I disable the AIM signal in the ECU, i can (very random) sometimes get the rpm and throttle pos. channel working.

The developers of VEMS told me that the AIM signal is much better for datalogging etc. because it's much more stable. The AIM signal is streamed out of the VEMS without the need of the "A" command to trigger the datastream.

The signal from my ECU matches the protocol in the before mentioned pdf. The only difference is that there also seems to be data on channels 224-229, although they are not mentioned in the pdf.
Isn't it possible to make an interface reflash to make it work with the AIM-signal in the pdf?

The issues with the Vems interface have now been solved. Race Technology provided me with a reflash file, which made the interface use the AIM signal from the Vems ECU and now everything works perfect.

Hi,

I bump this thread because I have the same problem as cerixen.

I have a Vems V3 with a RT serial interface hooked up to a Dash-2.

When I enable AIM data in the VEMS i get data presented in the DASH 2 display. The values are static and not correct at all.
If i uncheck AIM data (in VEMS GUI) I get no data at all presented in the Dash.

help is appreciated

Regards
Markus

Have the same problem as Marcus with my dash2pro and vems ecu

But i dont know if the problem is with the dash og ecu..

Martin