Powerup
Some issues here:
21/10/2005 Firmware 1.0.19 (from MegaTune r027 pack) succesfully uploaded!
Q: What should be the configuration for the TPS? I still have 56% when throttle is closed.
A: In MegaTune, go to the menu Tools -> Calibrate TPS and get the values for idle and WOT. Enter those in Settings -> Basic Settings window. You can use a narrower range of values to ensure that there is no movement due to a noisy signal (there should be no noise). Experiment and you'll understand.OK
Q: When in Megatune, the last 6 or 7 redbullets on the bottom of the screen disappear for a millisecond from time to time and meanwhile also the values(needles) drop to zero???? Is this a bad contact somewhere?
A: Check that you have a matching megatune vemsv3.ini with your current firmware version, either that is the problem or a bad serial conn.. You can probably see a RESET counter increasing in the lower left corner of the main screen..
OK changed vemsv3.ini from new firmware to Megatune directory and problem is solved! Thanks Emil!
Make mtt
Q: I can't make mtt files out of the config.txt and tables.txt files . When issuing a "make mtt" the prompt responds there is no such command or file? The dos-prompt started in the etc, or the firmware root directory ?
Try to run the same command that "make mtt" runs:\nÿ1ÿ
Just make sure the files exist in the specified location (relative to current working directory) and that's all. These commands depend on PERL, but only standart PERL libraries are needed, nothing special (like the Serial.pm for bin/prog.pl).
Make sure the global.h matches your firmware installed on the ECM. To be sure, run this from the firmware directory that you installed "vems.hex" from.
Also, you can check the MegaTune release package, many people are now using the .bat files because those do not rely on PERL (and PERL libraries).
Problem solved
- Tried testing channels with mdh command in terminal
- mdhd7 or others (like mdh87, mdh97, mdhc7 ?) are not giving a ground signal to an attached LED.OK! This was exactly the problem. I connected a relay to pin 15 and +12v and it clicked when mdhd7!
- exactly write what you do and measure, including
- the used ECxx pins (see GenBoard/Manual/DigitalOut/Table )
- DVM mode, and reference used for measurement (20V, measured with respect to +12V in this case)
- measured values
- exactly write what you do and measure, including
If there was no torture (like running injectors without GND5 or flyback), the P259 should work. Thanks Marcell. I thought that those channels give an groundsignal for a led too. But this isn't the case.
- Can I test the coil output with a relay?
- yes, you can even drive a relay. When the IGBT switches off, the flyback voltage will be 400V (cannot be small because that would prevent ignition), don't touch it! It's a good idea to use diode flyback (towards the relay supply) in this case, to push down the clamping voltage and voltage spikes (that mean noise and potential danger to human if touching it).
- But we normally use LEDs (with series resistor) or 12V lamps for testing.
- How can I assign my 4 injectors to a known channel which I can test with a mdh command? I've read the digitalout section but this is very confusing for me.
- fill in the h[0]; eg. h[0]=01 02 04 08 10 20 40 80 means a 1-to-1 mapping mdh80/mdh00 switches inj-channel0)
IAT
Q: Values off ntc-sensor in megatune seem to be incorrect:
1.while driving: 20°C
2.while standing still: 23°C
3.outside temp: 2°C
heatsoak isn't an issue I guess because off the close values in 1 and 2? Is there any calibration necessary?
- What does VEMS say that the IAT is on the display? 23°C in megatune
- Where is it mounted? (Picture would be great)in TB like this one http://www.vems.hu/wiki/index.php?page=GenBoard%2FManual%2FIntakeAirTemperature
- How long do you wait while standing still to get the reading?5min
- You can calibrate your own sensor with EasyTherm, at the moment that requires a firmware recompile.
- I assume you are expecting the IAT to read 2c when the car is running? If so, it wont, unless you have the sensor really far away from the engine which isnt really the best place for it. FYI temp here today was 0c and 1 car that I had hooked up on the scan tool at work that was warmed up and idling read 25c on the scan tool.OK but I expect alot lower while driving,like 10°C or so?
- Checked another one. Outside 4c, idling outside iat was 27c, driving was 21c. The sensor on it is located in the air filter housing, no where near as close to the motor as yours is. I say all is normal. This should be OK then. Thanks
uploading tables on genboard
Q: I have a problem uploading the tables.mtt file onto the board.
When I issue the sendfile command in Terminal program, the board starts to upload it into the memory(because I see the characters appearing on the LCD) but then stops (no "bye" appears)and doesn't go any further. I have to restart the board to communicate with the board again. I did succesfully uploaded the config and the tables a while ago. What can this be?
This doesn't sound normal. Maybe the uploaded table is bigger than the table-size of the firmware you are using? Some basic info is needed to make investigation feasible.
Make a zipfile of the following:
- firmware firmware 1.0.23
- global.h created friday, october 28,2005
- tables.txt created wednesday, october5,2005
- tables.mtt created wednesday, january 04, 2006
- config.txt created friday, october07, 2005
- mcd.txt - as dumped from genboard
- mct.txt - as dumped from genboard
describe:
- firmware version1.0.23 package
- what is the point the upload stops ?
- what's displayed ?'''6A 6A 6A is the end in the table'
- what TerminalProgram are you using ? Terminal.exe
- how did you make the tables.mtt from the tables.txt ?by typing perl bin/make_table.pl etc/tables.txt etc/tables.mtt in dosprompt
- make sure you publish the requested files zipped so the timestamps are seenI have no communication between this computer and the laptop so I can't transfer files from the laptop to this memberspage
Next week I will have a router between my laptop and my internetcomputer and can display the behaviour of the upload problem better.
Files to check for version (or replace with known):
- VEMS.hex
- global.h
- MegaTune vemsv3.ini (rather the whole megatune install
- When I installed the newer(1.0.23)firmware I had to copy the vems.ini file and the global.h file to the new firmware
- this cannot be right! You should carry vems.hex and global.h together; only changing global.h will get it incompatible. There is no vems.ini file at all.sorry I meant vemsv3.ini
- Can I simply delete any existing firmwarepackage and install a completely new one from zero?
- yes, it should work
UPDATE:
- I installed the older firmware package mt-r027 with version 1.0.19 back again. --> succesfully uploaded
- I tried to upload the existing(in etc directory) tables.mtt but it stops and blocks. Now I am sure global.h, vemsv3.ini and vems.hex are from the own mt-r027 package so this should be OK?