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

 _    _ 
( )  ( )
`\`\/'/'
  >  <  
 /'/\`\ 
(_)  (_)
        
        

  ___  
 / _ \ 
/ /_\ \
|  _  |
| | | |
\_| |_/
       
       

 _____ 
/  ___|
\ `--. 
 `--. \
/\__/ /
\____/ 
       
       

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

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:
'''What's working?''' '''Config and tables''' * tables ECM => mtx look OK * tables mtx => ECM look OK * 3D look OK (on win and Linux) * warmup related config ECM => mtx look OK * warmup related config mtx => ECM look OK * rpm and kpa bins ECM => mtx direction look OK * rpm and kpa bins mtx => ECM direction look OK, except the highest index (07), that is not saved. '''Runtime variables''' * O2 looks OK (after WideBand sensor is warmed up) * CLT and MAT look OK * warmup correction (enrichment) look OK * TPS shows the raw reading, not engine.tps * '''MAP is bad''' * where is the RPM shown? Should be shown on the runtime screen I guess * Otherwise the RPM reading is OK, the dot moves on the 3D screen in the RPM direction (not in the MAP direction though, since MAP reading is bad) '''What needs to be tested''' * please add here ---- '''Test environment''' A dummy perl script that understands * store * retreive * paging (with configurable page-lengths) commands is enough to test MegaTunix communications (without any hardware). Should there be any communication problem, it shows if problem is in firmware's communication part or MegaTunix. After playing a bit with MegaTunix and real GenBoard, it seems to me that talking to perl won't be needed that much. If we use the detailed debug of megatunix, it should be clear what's happening. However using a '''2nd serial port would be nice'''. It sucks to exit MegaTunix all the time, just to check the results in a TerminalProgram. Another option is to '''ask the Manmctbye and Manmcdbye from within MegaTunix and print/save results'''. I modified one of Mik's Perl scripts to talk to the Genboard and send the p1v, p2v, p3v, p4v, etc. commands and see the result. We can't get MegaTunix to work correct until this returns valid data. From what I have seen in my initial test, the low number pages are good, the 4..6 pages are bad. 7 I'm not sure about... I'm concerned most about 4..6 right now for tuning purposes. firmware/bin/ecu_talk.pl in CVS. -Jason -> Jason, i took a look at your script, modified it slightly, and tested operation against vems emulator; all pages checked out. - DB
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.