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

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

       
/'\_/`\
|     |
| (_) |
| | | |
(_) (_)
       
       

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

   ____  
  / __ \ 
 | |  | |
 | |  | |
 | |__| |
  \____/ 
         
         

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:
Current state: Used MembersPage/PhatBob/UserGuide I'm using a BMW M20 6 cylinder engine simular to MembersPage/GergelyLezsak It uses the following sensors and injectors: *440CC injectors *Stock single coil distributer *VEMS Internal Map sensor (working) *VEMS shop IAT sensor (values below) *WB02 5057 sensor (working) *Other CLT sensor (values below) *Volvo TPS sensor (working) *Stock VR sensor (working) I've downloaded the [VemsMT1.0.30rc3.zip] package and updated the firmware using UploadFirmware.bat. All sensors are connected and need to be calibrated. This is where the problems start: ---- '''IAT and CLT:''' Remember to publish battery calibration so we know AREF (287 or 256) for proper temperature table selection (that also precise at very low temp) I downloaded EasyTherm and filled in my three reference points: CLT: ; -2 6500 ; 20 2500 ; 160 50 IAT: ; 0 5000 ; 20 2200 ; 100 300 See EasyTherm cltfactor_2400_287.hex and airXfactor_2252_287.hex seems close (for above data) that can be applied to vems.hex with hexpatch.exe (that upload the patched vems.hex and there you go!). '''You don't need to change MegaTune and forget these three files''' (and related actions): *airdenfactor.inc *matfactor.inc *thermfactor.inc These three files now contain the right sensor resistance/temperature tables. So both my Firmware and Megatune needs to be updated. I found the same files in the following folders: VemsMT1.0.30rc3\VemsMT1.0.30rc3\MegaTune2.25b748\mtCfg VemsMT1.0.30rc3\VemsMT1.0.30rc3\firmware\inc So I figured I needed to replace these files and unload the firmware again, using Upload-Firmware.bat This didn't work so I also tried using Tempsensor-upload.bat. This also didn't work. I checked-out EasyTherm but don't understand what I need to do. Can someone explain this to me in plain English I just don't understand the short talk on the Wiki as I don't understand the basics. For excample: hexpatch.exe vems.hex < airXfactor_3000_287.hex > vems_1.0.30_airXfactor_3000_287.hex I understand this should be in Cprompt. *I now understand I need to select a .hex file. Can someone help me with that? How can I get that file uploaded to the AVR? Is that possible with Upload_tempsensor.bat when I replace the .hex file here: *VemsMT1.0.30rc3\VemsMT1.0.30rc3\MegaTune2.25b748\mtCfg *VemsMT1.0.30rc3\VemsMT1.0.30rc3\firmware\inc ---- *See EasyTherm on how to upload table with hexpatch.exe. With your temperature measurements (or sensor resistance at 1..2 temperature points) documented allows others to point to the best ntc curve (like 2700_287). For best result, do the battery calibration and publish the related config variable. I don't know how the battery calibration is being done. I'll try to find out. ---- *If the engine is like MembersPage/GergelyLezsak you can focus on the differences (if no differences, you can reuse the setup - including config - as is, right ?) There are differences. But how can I reuse his setup? I don't know what files I should put in what place.
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.