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

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

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

 ______  
(  __  \ 
| (  \  )
| |   ) |
| |   | |
| |   ) |
| (__/  )
(______/ 
         

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

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:
The purpose of this page is to document the communication protocol used by MegaTunix and GenBoard. There are much freedom at this stage, both megatunix and the firmware can be modified. First we get mtx and firmware talk the easy way, before we go fancy (with checksum). '''Important topics to decide:''' * Complex protocol as used in the menu OnlineCourse/TextualCommands? - no, only ideal for keyboard and human issued commands. * for runtime logging the way to go is GenBoard/BinaryProtocol The checksum and packet-handling implementation must be clean, and MegaTunix must remain compatible with the other ECMs of course. * Simple binary protocol as used by megasquirt is good for configuration ** Error detection? YES. Finally for everything. ** Use paging to keep the number of commands down? Yes. It does not lower the addressable area, just splitting the address to lower and higher part. Let me note that our tables ('j', 'n', ... are already pages, these must not be reused) ** What do we do about the large config? See below. ''Large config:'' * paging is the trivial way to solve this * DROPPED: Moving parts out to table would work (flash-saving but ugly except maybe for CLT-thingy) With 256 pages, this scheme can be extended even more: The current config (with names) can be splitted into several smaller pages grouped by function, ex. a page for iac related variables etc. But why? Isn't it better to group variables in a way the firmware does not know about (besides the variable name, eg. "iac_..." ? '''Page invariant commands''' There must be some commands that work the same way no matter which page the ECU is at (so when mtx gets disconnected, than another mtx started and connected, it should work): * Identification (see below) * page-selection command (obviously) Note that there is no requirement such as "all pages must be the same length" (eg. padded with FF). '''Identification of the comm protocol''' We have a command that enables identification of the '''firmware's communication protocol'''. This is quite different from * {{mdV}} (firmware version) * or {{mci}} (hardware serial number, that has HW version), because the firmware can change even if the protocol is not changed (config unchanged), and a given board can host totally different firmwares. Also, the "identify yourself" command should be 1-char for compatibility. ''Suggestion'': :{{command: '''S'''}} (textual Signature) :{{answer: '''VEMS Genboard v3, x.y.z'''}} where x.y.z comes from f_version[]. This '''identification should be enough to identify the firmware protocol version'''. Unfortunately because of some historical broken megasquirt firmwares, Dave had to develop a complex interrogation scheme, which is still needed for some outputs of the "S" command. But it should not be needed if * "S" confirms the comm protocol version (firmare is not broken) * '''or''' user specifies "forced firmware version" (in command line option or config file). This must not be default, of course, only if user explicitely and actively acts so (and that way takes responsibility for any resulting incompatibility). '''Realtime variables:''' * No need for raw sensor values, let the ecu take care of conversions with lookup tables etc. Then we don't need the strange scheme with ex. thermistor translation tables in ''both'' ecu and tuning software. * The number of variables are not limited to 22 bytes, but maybe it would be nice to have several smaller realtime streams (instead of a 200 byte stream) depending on what you want to log? Is this possible? * The paging method could be used for realtime variables too, eg. having upto 256 predefined streams of variables. A stream could be the one listed below, or for instance the benchstats variables. * Command used for receiving realtime variables =? Variables part of the realtime stream, please brainstorm (order not determined yet): {{rtc.sec}}\\ {{engine.status}}\\ {{engine.status_ext}}\\ {{engine.rpm_vhr}}\\ {{inj_port[x].pwcalc}}\\ {{engine.ignadv}}\\ {{engine.dwell}}\\ {{engine.kpa250}}\\ {{engine.coolant}}\\ {{engine.mat}}\\ {{engine.tps}}\\ {{engine.batt}}\\ {{corr.ego}}\\ {{corr.air}}\\ {{corr.warm}}\\ {{corr.baro}}\\ {{corr.gammae_1k5}}\\ {{corr.ve_hp}}\\ {{corr.lambda}}\\ {{corr.tpsaccel}}\\ {{corr.tpsfuelcut}}\\ {{corr.overrun}}\\ {{corr.als}}\\ {{iac.position}}\\ {{wbo2.Ip_output}}\\ {{knock.knock_adjust ("average" of all, or individual cylinders?)}}\\ {{egt1, egt2, exhaust backpressure and fuelpressure(We have inputs for those..)}} Note that we do not want to etch the set of runtime variables in stone. We must have a (frame_descriptor) '''structure that allows defining frames with arbitrary content'''. This is not as hard as it sounds, and provides flexibility to avoid the need for a future redesign. Of course a default frame_descriptor can be stored in flash to save SRAM for the common case. Look at GenBoard/BinaryProtocol. '''Page selection command''' The '''paging is achieved with the p<pagenum>''' command. Pagenum can be 0..255, in practice 0..7. Note that binary 0 is used, not '0' !!! No support in MegaTunix for page name like 'l' (table name), so the firmware is made cleverer to map these. * Page size was limited to 256 bytes, but * since v0.6.3 the page size limit is 4096 bytes * an exception to the new 4096 byte limit is a raw memory read (command 'F') which is still in 256 byte pages. ---- A perl model of the protocol, which allows the tuning software to communicate with a virtual GenBoard, is described in OnlineCourse/UartComm '''I want to put this in use against MegaTunix, but I'm stuck:''' which commands are used nowadays besides the 'p' ? (VE/constants) , (Rawmemory readback), and . * Page_Cmd '''p''' mtx => ECM select page number - effects most commands below * VE_Cmd '''w''' mtx => ECM store variable to address (page specific) * '''v''' ECM => mtx : read data from page * Rt_Cmd '''A''' ECM => mtx realtime variables * Raw_Meme_Cmd '''????''' ECM => mtx read RAW memory (takes an argument of an integer which is like a page, the number determins what part of memory you're reading (F should return 256 bytes of data) * Burn_Cmd * Write_Cmd '''W''' currently hardcoded to W, while all others are configurable The above is almost complete ? What about the ones below ? Those shouldn't be needed, right ? * '''L''' ECM => mtx VE/constants (goes hand in hand with page changing command to switch pages to read or write different data) * '''V''' mtx => ECM : write table-data ? * '''n''' mtx => ECM : write table-data ? * '''T''' ECM => mtx : read config data * '''W''' store all config from ECM RAM to ECM non-volatile memory (EEPROM)
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.