Solution to MT error w/ VEMS Signature
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.
This indicates old ini file. Download newer MegaTune. (maybe only the ini file changed, but easier to download the whole bundle).
Knock sensor info
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
- true
- but doesn't list a Knock B pinout
- true - not connected. If you really need it, it's possible to connect to it with only removing endplate (an 0805 resistor and capacitor might also be needed, and the wire(s) of course - maybe to a 6.3mm jack mounted on endplate ?). I'd postpone this until everything else works fine.
Easy Therm - Sensor adjustment
For the VR6 the coolent sensor reading is off... I've tried the offset files, but still no luck with getting a decent reading...
So, my plan is to test the sensors, get the proper ohm readings, and then re-compiling the firmware.
I will then make the firmware available.
The Bias Resistor value for the V3.3 boards is: 2.968K Ohm
1.0.73 Firmware related issue with EGO correction/Lambda Target tables
I believe I have found a possible bug in the current version of 1.0.73 firmware (12x12 or 14x16 tables).
I have found that even with EGO correction off, modifying the Target Lambda Table map will change the AFRs. This must be looked into. This is a problem I've confirmed on two separate ECU's/installs running 1.0.73 one car is running 14x16 tables and the other 12x12.
G: it is not a bug!! Lambda table stays lambda table w/o Ego correction too and take a part in fuel calculations. So VE table is closer to real VE of given engine and desired AFR has no influence on its shape. It is great, because if you want change AFR at some load region on already tuned engine, only one table must be changed is Lambda table. My safe way to get VE shape is set Lambda table rich at dangerous areas and after VE table is finished, just find best afr for given engine by changing Lambda table. MembersPage/GintsK
Back to MembersPage/Sascha