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

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

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

  _  __
 | |/ /
 | ' / 
 |  <  
 | . \ 
 |_|\_\
       
       

 __     __
 \ \   / /
  \ \_/ / 
   \   /  
    | |   
    |_|   
          
          

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:
'''VEMS uses the PS2 clock signal to receive 0/5V wheelspeed1 frequency signal.''' Became very popular, so 2nd wheelspeed input was also implemented in software (if you need 2, request "2 wheelspeed inputs" in the order comment, see below). * '''It is recommended to set calibration=0 when not used !''' (for both wheelspeed1 and wheelspeed2) * use rising edge ("both edge") should probably never be used * See related terms and calibration values in [http://www.vems.hu/manual/vemstune/help2/htmls/v3/v3_speed_sensor.html v3 help]. ---- '''Protected connection of wheelspeed 1''' - suitable for HALL sensor that pulls to GND, or 0/5V or 0/12V signal. The circuit installed by default (wheelspeed input=EC18/8) when controller is ordered with PS2=NO (which is the recommended default): http://vems.hu/download/v3/doc/assembly/v3_protected_wheel_speed_connection.png Note: * For wheelspeed input to work, the "non-PS2" or "wheelspeed" firmware must be uploaded ** Because the PS2 firmware uses the PS2 port for keyboard, and launch-RPM is time-based (not wheelspeed). * VT must be always newer than firmware - preferrably use recent VemsTune [http://shop.vems.hu/catalog/wheelspeed-cable-p-143.html PS2 wheelspeed cable] might come very handy for a controller ordered with PS2 (either accidentally or in the past: because PS2=NO is a better option !) * so ordering assembled controller without PS2 is better, since than EC18/8 is wheelspeed input by default (since 2010, see attached paper or test with 0/5V frequency signal) - with internal pullup and some protection.. ** DSUB9 connector is included with the PS2-wheelspeed cable, but you might need a connector for your wheelspeed signal (or tap some wire: but it's counterrecommended to tap ABS signal: WhatEverYouDoYouDoItAtYourOwnRisk). For an audi quattro 6 speed gearbox (reed-switch at the front-left wheel shaft, at least in ours) a [http://shop.vems.hu/catalog/injector-connector-p-87.html 3 pin AMP connector] also needed (only pin2,3 used). '''Warning: Sensitive pin''' PS2 clock input is a direct CPU pin. It is very sensitive. Either static electricity or 12V will damage the main processor immediately. Customers are advised to request in the WebShop order note: * '''PS2 clock wheelspeed input on EC18/8''' ** This is standard since 2010 unless you request otherwise (in the order note). * 4k7 pullup to +5V * 4k7 and 5V1 zener protection on the processor pin * MembersPage/GergelyLezsak/AssemblyThreePointFive shows the minimum recommended pullup resistor and zener protection for wheelspeed1 input: http://www.vems.hu/files/GergelyLezsak/v35pics/17_PS2CLKpullup.jpg http://www.vems.hu/files/GergelyLezsak/v35pics/16_PS2zener.jpg With the 5V1 zener it is less likely to damage it, and an open-collector HALL sensor or a VR signal and a simple NPN inverter (same as CamHALLInverter) can be used to drive the signal (LM1815 is not necessary for this, although that would work too). Care is still needed of course. ---- '''Second Wheelspeed input''' Implemented in Firmware 1.1.84. Available only in non-PS2 firmwares. Connection is on the processor SCL pin, need protection and pullup resistors. If needed, ask in order comment : protected second wheelspeed input on processor SCL pin ---- '''Configuration''' * sensor calibration set the frequency which can measured at 100km/h * egde for sensor : set where the ecu will measure ( use both if sensor signal has 50% duty cycle) * minimum period : anti noise protection * sensor divider : the signal can divide for high frequency sensors ---- '''Wheelspeed data usage''' * logging wheelspeed to notebook, or SDcard * sending to AfreshTiny/AimDisplay for well-visible display * boostcontrol - gear dependent boost * '''launchcontrol - wheelspeed dependent rpm-limit''' ---- '''Launchcontrol''' The good old initial launch behaviour with retard and launch-enrichment is still there. But after reaching the first entry in an '''8 entry table (array)''', no retard, no enrichment: 2x8 bytes for '''wheelspeed => RPMlimit'''. Firmware uses interpolation for smooth transitions between table-points. RPMlimit is in 100 RPM unit. wheelspeed is the unit of your choice. Usually: * km/h * or mph * or any other. It really just depends on calibration The same table is time => RPMlimit for the PS2 firmware where wheelspeed is not available. Time is in 64 msec unit. The first and last bin in the table are somewhat special: * Before the first entry is reached, the good old one-value RPMlimit set in config is used and retard and enrichment is applied "Launch RPM vs Road Speed" screen: http://www.vems.hu/files/KevinBlack/VT%20Launch%20RPM%20vs.%20Speed.JPG Note: the '''"launch-active" flag''' in VemsTune only '''lights up when the RPM-limit is reached (not when the button is pressed - this can be confusing)'''. So if you want to test an analog input switchbutton, configure the ALS input to that pin to see that it lights up. ---- '''Temporary note''' - for .ini file tweakers. This section should be cleaned up when these are deployed in both MegaTune and VemsTune 2009-05-xx releases. Direct commands for page15 (launchcontrol wheelspeed=>launchRPMlimit) read/write are [] brackets. * Offset 0..7 are RPM (unit=100 RPM) * offset 8..15 is the wheelspeed (unit of your choice, depends on calibration) Check the mct dump to see if s[0]= and s[1]=... values are set as you expect. ---- '''LaunchRPM vs. Wheelspeed Curve Questions from Kevin''' * How exactly is it activated? Does the analog input need to be used at all? ** yes, to go to launch mode you always need to activate with an analog input. * Or can this rpm curve be enabled permanently so it does not use up the analog input? ** currently there is a launchinput="disabled" but there is unfortunately no "always enabled" setting (same could be useful for ALS too). * Is it possible to have the Launch RPM appear in the Data Logs? ** the RPM appears in the data-log, and sparkcut directly correlates to the difference between real-RPM and launch-RPM * The "Disable Launch Curve" selection box looks to have bugs, it is blank, should say "Enabled". If you select "Disabled" it does not allow you to go back and enable it again. ** we'll look into this. The launch curve is (IIRC) technically disabled by 0 (speed) in the last entry. Than the (1-entry) launch_RPM setting takes effect. ---- '''REST OF THE PAGE IS BRAINSTORMING''' '''Freq to voltage''' - could also be used if more than 2 wheelspeed inputs required [http://www.elfa.se/pdf/73/731/07312713.pdf LM2917] (see appnote) frequency to voltage converter to get wheelspeed info (on display, logging, anytrim, ...).
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.