_     
 | |    
 | |    
 | |___ 
 |_____|
        

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

         
|\     /|
| )   ( |
| |   | |
( (   ) )
 \ \_/ / 
  \   /  
   \_/   
         

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

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

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:
I use a datalogger and dash from the company '''Race Technology''', labelled "Vems interface" * '''requires reflash of the interface''', after that '''THE RACE TECHNOLOGY VEMS INTERFACE IS NOW WORKING CORRECTLY, AND READS THE AIM SIGNAL FROM THE V3''' ** the reflash was provided by Race Technology (thanx) ** can we publish the firmware that is required for the [http://www.race-technology.com/dash2_2_31.html Race-Tech Dash2] display ? There were a couple of disappointed Race-Tech owners who gave up, and will be very happy to be able to use it finally. One dash-2 owner kindly offered his device for testing. ---- '''Protocol details''' * VEMS firmware sends data via [http://www.vems.hu/files/MembersPage/NanassyPeter/AIM_support/AIM-ECU_protocol.pdf AIM protocol], ** the scalers were made according to [http://www.vems.hu/files/MembersPage/NanassyPeter/AIM_support/AIM-ECU%20protocol.pdf AIM-protocol.pdf] with only minor corrections to match the Race-Tech Motec interface (which was found to deviate slightly from the protocol.pdf, eg wheelspeed 10x multiplier). ---- Other channels: Example of data streamed from my v3: http://www.vems.hu/files/HankMoody/aim-new%20hypertrm.TXT It seems there are more channels streaming from my v3! I also see activity on channels 224-229 in my data. What are theese channels used for? * '''I also see action on channel 133, what is that used for?''' ** '''GPSSPEED''' is sent via channel-133 (5+128 if you like... 5 is traditional wheelspeed) ** valid when nmea-GPS is connected ** Of course, GPSSPEED might be different from wheelspeed: likely more precise on the average (not depending on user calibration and tire pressure), but filtered more agressively, slower response. * 224-229 are AIM_OUT_0 .. AIM_OUT_5, custom outputs ** eg. boostcontrol solenoid output channel, idle solenoid output channel can be actuated by other device, say, round if configured so (very useful on V8 where ++ number of outputs help) ** .. channel=Xe where (X=0..5) ** disable outputs by i7, not by i6 (unless you know what you are doing) ** we'll review your vemscfg in this respect ** however any AIM receivers just neglect the channels they don't know. Chance is 0.00% that disabling 224-229 will get Race-Tech working if it does not work with 224-229 transmitted. ---- Im running v3 firmware 1.1.96 Some of the channels within the AIM datasream are correct. * TPS displayed good (AIM channel 45) * RPM (sent by VEMS in AIM channel 1). '''Examples sniffed in hex from terminal''' - shows vems firmware sends correctly: ** (03EB=) 1003RPM - 01 A3 03 EB 92 ** (07D6=) 2006RPM - 01 A3 07 D6 81 * [http://www.race-technology.com/wiki/index.php/ECUType/VEMSECU VEMS-ecu interface] ** it says "Note: AIM protocol used" but it obviously is not using the [http://www.aimsports.com/products/mxl-chooser.html AIM - RS232 protocol] that v3 properly sends (when enabled) ** it also says conflicting info at the same place: "The VEMS ECU outputs 56 byte sequence of data at 19200bps baud rate." - this suggests the Race-Tech display does NOT actually use AIM, but '''relies on the 'A' command''' that old firmwares (before 1.1.96) used for sending real-time data to VemsTune and megatune. (offsets found in global.h and megatune.ini, and everyone knows runtime data sending works, but for longterm compatibility AIM-RS232 is a much better choice to rely on). ** new v3 firmwares (eg. 1.2.x) only act on CRC-protected commands ("triggerframe protocol") to prevent corruption (due to serial noise). In other words it does NOT reply at all on non-CRC-protected commands like the 'A' command.
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.