#####  
 ##  ##  
 ##  ##  
  #####  
     ##  
 #####   

  __  __ 
 |  \/  |
 | |\/| |
 | |  | |
 |_|  |_|
         

         
    ##   
         
    ##   
    ##   
    ##   
    ##   
 ####    

 ___   
|  _`\ 
| (_) )
| ,  / 
| |\ \ 
(_) (_)
       
       

  _____ 
 | ____|
 |  _|  
 | |___ 
 |_____|
        

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
'''Powerup''' '''Benchtesting''' * 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 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) ---- '''In-car Testing''' '''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 firmware and config and tables''' '''Make mtt''' <code> perl bin/make_conf.pl global.h etc/config.txt etc/config.mtt perl bin/make_table.pl etc/tables.txt etc/tables.mtt </code> 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). '''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 version'''1.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 seen'''I 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 UPDATE: '''upload strategy I use''' Q: What I do is: * copy the output of mcd and mct from terminal and paste it in the existing config.txt and tables.txt files in the etc directory * then I make changes in those files and save it * I make the mtt files out of it by <code> perl bin/make_conf.pl global.h etc/config.txt etc/config.mtt perl bin/make_table.pl etc/tables.txt etc/tables.mtt </code> * start terminal program and type Man * send the config.mtt file * terminal responds Bye * send tables.mtt file * terminal starts uploading the file because lcd display starts rolling the numbers and then stops suddenly before the end and terminal does not respond anymore, I have to reboot genboard to communicate again '''Other strange thing happens''' *The mcd output is not correct! The output stops suddenly on a line. When i send mcd again '''it stops again but not at the same variables'''. * using a serial cable (DSUB9) with a 6.35mm jack connection in the dashboard, which goes from there(dash) to the EC18 I then soldered the pins with small wires to the corresponding header onto the board ** also, driver version if possible (if using USB/RS232 ) * firmware version=1.0.23 (might be important in this case). '''Check firmware integrity:'''. When you upload the firmware you can supply an option flag to verify that the firmware reads back from the board exactly as it was written. (same program that you used for firmware upload: megaloader / progl.pl, but in verify mode: without the "w" option) ** OK I typed in dosprompt in the firmware dir: ''perl bin/prog.pl vems.hex Etf'' and it responds with everything OK, board says hello, '''verifying was succesful''' * similar behaviour is often caused by bad serial cable: check ground (remove notebook from cigar-lighter and run on battery), and try another USB-RS232 adapter or comm-port. When output stops always at same place, it's unlikely that ground-noise is the cause. But in this case, output stops at different places each time.Yes it stops at different places but very near; it will never stop in the beginning but always far at the end *I can upload the config.mtt file (terminal responds with "Bye") * but I still can't upload the tables.mtt ** note that nothing appears on the terminal during sending tables.mtt (maybe a "Bye" at the end). When I send, I see the LCD display change variables(rolling) but then suddenly stops(lcdrolling stops)and nothing appears on the Terminal I guess you'll need to use MegaTune or upgrade to 1.0.30 or newer firmware. *'''I checked''' the following but no improvement! **'''serialcable is OK''' + soldering is OK **powered the laptop on 220V and not via cigarettelighter **'''groundconnections''' are made as described in the manual **I have installed '''firmware 1.0.23 successful''' *I don't know how to change the com(1) port for my laptop? ** Why does that matter? Just change the device you're using in the terminal program. If you use a USB adapter you can double check which COM port it is presented as to the operating system in the device manager in Windows. *Is there a specific configuration for the Terminal program to use?I use Terminal v1.9b. ** 9600 baud, 8 data bits, no parity bit, 1 stop bit, no flow control. I find that Hyper Terminal that comes with Windows works very well. Note: don't duplicate things. Eg. if you don't understand how to check firmware integrity, ask where it was suggested (not at a different place - when it becomes too big, it can be split to separate section or page, changing the original text to a link.)
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.