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

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

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

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

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

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:
||MembersPage/Sascha/SchnellEthritysix||MembersPage/Sascha|| === Planned ECU mods === ---- '''Want to add''' *2nd wheel speed for traction - can someone make a basic diagram how it should be done? *Input Multiplex - again basic diagram would be nice for mods to the ECU required to run the multiplexer *CAN BUS (when software is available to be able to add our own addresses?) *PWM FAN control with VW J293 module - can anyone verify what modules are compatible? Like: 8E0959501AB 8E0959501K 8E0959501AG E0959501AG?? ** The VW J293 from a Mk5 Golf is known good. ** But when mounting to a BMW why not use a Temic PWM controlled fan from for instance a e46 m54 engine? *** Unfortunately I don't believe I have the space with the 3 row Z3M rad between the water pump. '''Is it possible to configure 3rd trigger to use as freq. input for Ethanol content sensor instead of tying up wheel speed inputs?''' ---- '''Added 2nd serial port => perfect communication to Afreshtiny (after configuring according to instructions) ... SOLVED''' I've added a connection to the 2nd serial port on my ECU to be able to drive my AfreshTiny without having to disconnect every time the main COM port to tune. Checklist (kept, just in case someone has problem configuring) * so it was not ordered that way, but '''home-modified => details please''' (turned out HW was correct) * first scope, or measure DC voltage on the ECU TX (DSUB9 female pin2), normally -7V when idle, and lower absolute value like -6V when transmitting). ** If not negative, than perhaps the ECU RX was accidentally connected instead (TX/RX swapped ?) AfreshTiny was first completely unresponsive and showed no data (SOLVED, fixed by configuration). * Checklist was: to detail ** your HW setup ** your measurements ** your round config ** your ECU config (in case the "A3" bytes are not seen in PC TerminalProgram at 19200,8n1 baudrate) * Is there something to enable? ** yes, in VEMS round: AIM capable firmware (does it show 0.5.x indicating AIM capability ?) ** 2nd serial in ECU firmware, see BroadcastDatastreamAim ''Configure 2nd UART to send "5 byte stream"'' FW: 1.2.38 * sniff RS232 stream (connect to PC and read with terminal, or linux screen command). ** with the matching baudrate (19200,8n1 if GPS baudrate is configured 19200 as recommended for VEMS round ) you should see many A3 (appr every 5th byte), as a clear sign of AIM stream being transmitted * '''we will review your exact configs''' ('''you forgot to show us''', so we can hardly tell what you did wrong ) ** '''perhaps baudrate is misconfigured ?''' ** in VT, logging, temporarily enable the necessary flags (like SD byte stuffing), configure "GPS baud rate" ** in the end, disable SD byte stuffing (and possibly SD logging altogether, configure knock input channels if necessary) Sorry I forgot to update as I was enjoying the 2nd COM for two days now. Issue was related to (obviously) not immediately seeing (finding) the circumstances required to correctly enable the 2nd COM in VT. Apologies! Described here: BroadcastDatastreamAim Specifically this part: ---- '''Configure 2nd UART to send "5 byte stream" with datacontent matching the AIM ''' (but currently no wasted gaps) '''Requirements''' * Newest 1.2.35 firmware (compile time after 2016-07-14) '''Configuration (VemsTune checklist)''' * VT -> Ecu Calibration: ** iButton anti theft: disabled ** prohibit/iButton2 high byte: 8 ** prohibit/iButton2 low byte: 1 * VT ->Ecu Logger -> Ecu Log Settings: ** GPS Log '''Baud rate: 19200''' (actually 2nd serial port baudrate; in old VT if this entry is greyed out => temporarily enable bytestuffing) ** Ecu log use byte stuffed format: disabled ** Automatic GPS Log to SD card on main serial port : disabled ** SD Card Trigger Log: disabled * VT->Outputs->Display Settings: ** AIM disable => send via 2nd serial if 2nd serial is free (renamed accordingly in VT 2016-07-..) ** AIM enabled => send via 1st serial (as traditionally), respecting the "teletype restriction" (even those receivers should pick it up that do not understand the bytesequence without the wasted gaps) *** but only when VT -> Ecu Calibration: *** prohibit/iButton2 high byte: '''NOT 8 ; make sure this value is NOT 8 (eg. 255 is fine) before enabling AIM''' ---- After following the instructions, the AfreshTiny started to work immediately.
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.