Just recieved the VEMS unit... Was very impressed by the quality of everything, it was all very professional.
Going to be reading over the documentation/manual once again (I've read it at least 10+ times) but I want to make sure it gets done the first time. Then I'm going to cross-reference to the factory wiring harness what needs to be connected and what can be removed.
The project is a 1991 VW Passat Wagon with a VR6 swap, that is currently turbocharged using factory engine management that has a custom dyno tuned chip.
It is an OBD1 motor originally from a Corrado (so yes it has a dizzy). For now, I will be using the dizzy, but along with that I will be using all the factory sesors to have fully sequential injection (so that means using the VR crank sensor on the 60-2 wheel allong with the 1 window dizzy with the hal sensor in the distributor). If anything I will be going at least semi-sequential at the beginning.
Got the VEMS ECU to boot up with the LCD attached. Working like a charm. Inital wiring will start hopefully tomorrow!
Started on the pre-wiring of the VEMS ECU, have almost everything connected. Once I had the DSUB (COM PORT CABLE) connected, I decided to see if I could connect to Mega Tune... I downloaded the newest version, and the last stable version and with both I'm getting errors from Megatune that the signature is not the same.
The firmware that was shipped with my VEMS unit was 1.0.38. I then attempted to up/downgrade the firmware versions until I wasn't getting this error anymore, and now with 1.0.32 it seems to be ok. But the more I look through the WIKI the more I find people being able to use the newest 1.0.38 firmware, yet I'm not.
Q: Can anyone point me into the proper direction so that I can get megatune to run with the 1.0.38 version of the firmware? I tried the 1.0.23 version which I'm guessing is the last "stable" version according to the FirwareChanges WIKI, but the LCD comes out all screwed up.
A: Start MegaTune either way, even if it complains about the "signature". Go the menu : Settings -> Basic Settings. Now check that your "Map Range Unit" and "Table kPa Unit" are set correctly.
Thank you for the quick reply! But I have told MegaTune that my Map Range is 400 kpa (as I have a 4Bar onboard MAP), but am unable to find the Table kPa Unit you are talking about under Basic Settings. BTW, I'm using/tried MegaTune version(s): MegaTune2.25b654 and MegaTune2.25b748.
I _think_ that MegaTune2.25b748 is old, you could try the version in: http://www.vems.se/UserFiles/File/VemsMT1.0.36.zip that is what almost everyone here in Sweden is using. -Jörgen
Q: Could it be that I need a different MegaTune ini file? The strange thing is that with firmware 1.0.32 all is well, and I don't get this error, but as soon as I uprage to anything newer (up to 1.0.38) I have this problem.
This is the exact error I'm getting from MegaTune, so hopefully that will shine some more light on my problem for you. Thanks!
MegaTune error:
Controller code version does not match signature in vemsv3.ini.
Expected "0x32" (found in ini file)
Recieved "VEMS v1.0 12x12 kpa=1,9" (from controller)
Table corruption may occur, this is usually a very serious problem.
Also another Q: When connecting knock sensor(s), the VR6 has two, could I connect both to one channel on the VEMS (ch 0)?
As in the VEMS manual (chapter 9.9) it says that Knock A (channel 0) is the one that commonly used, and that Knock B (channel 1) isn't. And that Knock A has a pinout on EC18pin3, but doesn't list a Knock B pinout.