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

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

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

         
         
 # ###   
 ##   #  
 #       
 #       
 #       
         

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

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:
so I got first aim2can devices, how can I configure them? * or they have some kind default configuration? ** yes, feed AIM stream from v3 (1st or 2nd RS232 port; or from PC) ** make sure the CAN bus is terminated properly (120 Ohm on both ends); *** The device termination can be measured with DVM (eg. typical 120 Ohm, but sometimes 240 Ohm for compatibility with some BMW app that uses 2 terminating devices on each end 240/2=120 Ohm effectively). ** emitting CAN data for dash (feed to CAN-receiver or CAN logger) ** if need more CAN-ID messages, see CanBus and specify required message data on your project page ** after a certain number of messages specified, implemented and tested, we make the device easily configurable. (to make sure the conversions / formulas / ranges are sufficient) There might be many CAN-bus systems in a vehicle. Please make sure not to adversely effect critical systems eg. ABS. ---- Some '''test AIM streams would be nice, eg. with constant for a few seconds, than artificial step''' (RPM, wheelspeed, MAP, TPS data), so any conversion (eg. the wheelspeed in 0.1 km/h or mph or other units) are easier to notice (calibration or verification with continuously varying data is more challanging). ---- so what is default configuration? ID's and other stuff? ---- Implementation according to http://www.vems.hu/files/MembersPage/NanassyPeter/AIM_support/AIM-ECU%20protocol.pdf page#1 * While AIM CAN allows any CAN id, quoting spec: "The packets of data do not contain a specific identifier, they are just in a predefined order" * we implemented CAN id's 0x6f0 - 0x6f5 for the full set, this still conforms to AIM spec. ** Example: id 0x6f0 contains the first 4 channels (2 data bytes each) RPM, Wheelspeed, Oil Pressure, Oil Temperature. id 0x6f1 contains next 4 channels (and so on) thank you, will try to feed this to '''motec c125''' soon ------ so after like 10hr's of playing with the '''motec dash''' I came for advice to motec forum.. after that it took like 5 minutes to define everything and get it working. [http://www.motec.com/forum/viewtopic.php?f=70&t=3703&p=16790&sid=e1a5945ee82ec93528a9e8c2cbca419f#p16790 motec forum link] * If you can get the first message working correctly then you have the hard bit sorted. ** Simply '''create a new receive template with the next address in the list''' and setup the channels as required. ** You have 4 different addresses being sent from the ECU so you should end up with 4 receive templates in the dash.
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.