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

  _____ 
 | ____|
 |  _|  
 | |___ 
 |_____|
        

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

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

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

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:
General Questions ---- Order 17504 date. 7 April 2022 We need a update on order 17504 VEMS motronic88 - Model: M50 NonVanos-92 When will this order be sent out? Thank you Peter Update 25/5-2022 Order received today Case closed ---- 03-05-2021 Need help to lock 0x3c ECU NR. 9155 dp engineering Trying to lock the avr 128 but i get error. VT says YOUR ECU IS NOT LOCKED Haw can i fix that? C:\Users\Peter\Documents\bootISP\avrdude> avrdude -c usbtiny -p m128 -U lfuse:w:0x2f:m -U hfuse:w:0xc4:m -U efuse:w:0xff:m -U lock:w:0x3c:m avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e9702 avrdude: reading input file "0x2f" avrdude: writing lfuse (1 bytes): Writing | ################################################## | 100% 0.01s avrdude: 1 bytes of lfuse written avrdude: verifying lfuse memory against 0x2f: avrdude: load data lfuse data from input file 0x2f: avrdude: input file 0x2f contains 1 bytes avrdude: reading on-chip lfuse data: Reading | ################################################## | 100% 0.02s avrdude: verifying ... avrdude: 1 bytes of lfuse verified avrdude: reading input file "0xc4" avrdude: writing hfuse (1 bytes): Writing | ################################################## | 100% 0.02s avrdude: 1 bytes of hfuse written avrdude: verifying hfuse memory against 0xc4: avrdude: load data hfuse data from input file 0xc4: avrdude: input file 0xc4 contains 1 bytes avrdude: reading on-chip hfuse data: Reading | ################################################## | 100% 0.02s avrdude: verifying ... avrdude: 1 bytes of hfuse verified avrdude: reading input file "0xff" avrdude: writing efuse (1 bytes): Writing | ################################################## | 100% 0.00s avrdude: 1 bytes of efuse written avrdude: verifying efuse memory against 0xff: avrdude: load data efuse data from input file 0xff: avrdude: input file 0xff contains 1 bytes avrdude: reading on-chip efuse data: Reading | ################################################## | 100% 0.02s avrdude: verifying ... avrdude: 1 bytes of efuse verified avrdude: reading input file "0x3c" avrdude: writing lock (1 bytes): Writing | | 0% 0.00s ***failed; Writing | ################################################## | 100% 0.10s avrdude: 1 bytes of lock written avrdude: verifying lock memory against 0x3c: avrdude: load data lock data from input file 0x3c: avrdude: input file 0x3c contains 1 bytes avrdude: reading on-chip lock data: Reading | ################################################## | 100% -0.00s avrdude: verifying ... avrdude: verification error, first mismatch at byte 0x0000 0x2c != 0x3c avrdude: verification error; content mismatch avrdude: safemode: Fuses OK (E:FF, H:C4, L:2F) avrdude done. Thank you. ---- 04/08-2019 Bluetooth No communication Did buy a new android 8 car radio and will install vems display. I can´t get connection to vems BT. The car radio can see the BT module but not make the connection. Then i tested a old China 2x sub 9 pin module and it worked fine. Is there any AT commands i could try? Vems BT module A226 * If connecting PC DSUB9M to DSUB9M of BT-RS232 module, "cross" cable (2-3 3-2 5-5) is needed (TX=>RX), not a straight-through cable ** you can check the bytes sent from android (if connected)... * If issued in the first few (30?) sec after powerup, some commands can be used to reconfigure or check config ** AT+PIN (try baudrate other than 19200,8n1 if you suspect it might have been changed accidentally) ** AT+BAUD5 * See ((RS232 Signal Level)) ---- 2019-03-20 Round. '''Q''': How to connect rpm * We have a distributor with build in amp. goes directly to the ign coil. * Can we connect directly to the coil '''A''': Instructions on Round RPM input connection can be found on: http://vems.hu/vt/help/round/round_rpm_input_settings.html * connecting to coil is not recommended, the round RPM input is not HV capable. * if a diode is fitted so only the low side switching is passed to round RPM input and HV is blocked, the coil signal can be used * coil- signal -> (stripe)diode -> round rpm input dsub15-pin#10, use a fast rectifier diode to block the HV current. '''Q''': Also we like to connect a analog sensor 0-100 Psi. Trayed the analog wizard but i did not change the values. * What to type in input calibration? * What to type in input Offset? * I like the display to show 0.00 - 6.xx BAR '''A''': Instructions for analog input calibration for Round can be found on: http://vems.hu/vt/help/round/round_analog_input_settings.html TNX Peter ---- 2018-06-25 * Uploaded 1.2.31 * Made a new wiring harness. ** Now i have no lambda data while driving. (EGO call. ?) * Should i try a LSU 4.2 ? I have reviewed your log '''[http://www.vems.hu/files/MembersPage/PeterJensen/S2/v3.3_u010045-2018.06.25-21.45.36_31.vemslog v3.3_u010045-2018.06.25-21.45.36_31.vemslog]''', you are not getting lambda reading beacause there is still a problem with the heater and pump control as i explained before (but it seems to have gotten worse now, Ri is not measuring at all). * If the loom is new and doublechecked * quickest WB hardware test: test '''100 ohm between nernst and pump-''' (4V), '''also 100 ohm between nernst and pump+''' ** and capture vemslog (RPM=0): start heater in "free air calibration" dialog. * if no conclusion from vemslog review, fire a repair request in webshop to get the ecu diagnosed. ---- 2018-06-23 Lambda EGO flag is flashing Sensor is new 4.9 Sensor cal. log http://www.vems.hu/files/MembersPage/PeterJensen/S2/v3.3_u010045-2018.06.23-07.52.06.vemslog ---- Hello Peter, I have reviewed your wbo2 warmup log, there is indeed a problem there. Both the Ri and Nerst Dc measurement are oscillating around target not stable like needed and control actuation seems to act in bang-bang fashion. To rule out any firmware problem (you are running 1.2.33 which is marked internal, not even testing; see GenBoard/UnderDevelopment/FirmwareChanges) i would recommend you upgrade firmware to the latest released which is 1.2.38. Could you take another log of wbo2 calibration using this firmware ? Thanks! I'll review and provide hints on next steps after. Best regards, Dave ---- 21-6-2018 Lambda EGO flag is flashing Seen that EGO correction is not constand. Cant see why LSU 4.9 ECU Audi 3b PnP Log can be find her http://www.vems.hu/files/MembersPage/PeterJensen/v3.3_u010045-2018.06.20-18.05.25.vemslog Hello Peter, To get an idea whats going on, could you make a vemslog of wbo2 calibration running (no need to take sensor out of the exhaust, just make sure the sensor is cold when starting the calibration) after starting let the log run for at least 5 minutes. Please link the log here so i can review, we'll work from there; Thanks! Best regards, Dave ---- 11-06-2018 Problem solved Serial connection I replaced max232 and it is now working aging. Thank you for great support 2018-05-29 Need Help: ECU runs but '''no serial connection''' (MAX232 problem suspected if wiring has good ground and no intermittent RX/TX problem). End user had problems connecting to ecu. We have tested on 5 pc and many usb to serial connectors. Problem started as a small issue but got worse over the time and now we have total lost any kind of connection. '''ECU 17956''' The ecu is '''running nice in the testbench''' but no communications. You can measure and check outside connection and disassemble if that does not solve. Do you have a '''spare ST232D or MAX232 (SOIC16) IC''' already ? I really need to get his car up and running so please help. * If you carefully checked connection TX, RX and GND ground connections (really, do not just assume that connections are good because it worked before; sometimes it communicates with insufficient ground, or intermittent conn causes very same symptom) ** we send MAX232 '''(or ST232D) for no extra charge for fastest solution''' *** a hot-air blower and a small piece of Al foil needed to make a rectangular window around the chip to protect surroundings (remove the chip with tweezer gently, with "no force", only after really melted) *** 99% that MAX232 chip replacement solves the problem, if connections are really good). +100 EUR (off listprice next purchase) if solved on site ---- 30/1-2018 Haw to connect flex fuel sensor to pcb 3.8 ECU 9952 How to connect GenBoard/VerThree/FlexFuel sensor to the "SCL" of v3.8 pcb * note: 2nd wheelspeed available on pin if ECU ordered with 2nd wheelspeed, eg EC10/pin6 below (or is that a separate project ? Please never mix different projects on same page, please create separate page) ** check the paper docs received with the device. ** Safe to feed frequency or other 0-5V signal with 1k to unknown EC10 or other pins (and see wheelspeed [http://www.vems.hu/vt/help/v3/v3_analog_input_calibration.html analog input] reactions in VemsTune) See GenBoard/VerThree/Schematic to connect to port SCL * check in the schematic which AVR pin, and measure if at least the protection resistor is there. [http://www.vemssupport.com/forum/index.php?topic=2499.0 On v3.8 filter and protection is embedded in PCB] * see InputTrigger/WheelSpeed '''Second Wheelspeed input''' and any references, eg. SubaruEj * Note: normally wheel speed 2 is wired to EC36 pin 30 ** this pin also goes to p259 ** no NEED to cut the p259 trace, the p259 output does NOT pull to GND (or do anything) if not activated. ** so wiring SCL to EC36 pin 30 can be done without tracecut. ** only start any such modification if willing to follow the schematic to verify any hint, and avoid static electricity damage http://www.vems.hu/files/MembersPage/PeterJensen/wheelspeed2.jpg http://www.vems.hu/files/MembersPage/PeterJensen/wheelspeed2_back.jpg ---- '''BMW 88 pin Boost valve''' We need to connect a '''N75 boost valve''' to this 88 pin ecu but what pin will we connect to? '''Econoseal 10 pin connector''' Pin 8 and 9 Extra output with flyback. * What does it mean ? (p259 or inj-FET or what ?) ** exactly as written, same as in VemsTune * so in VemsTune, outputs menu select boost control and '''choose''' ** '''Extra output 5''' if you connected to "Extra output 5" ** '''Extra output 6''' if you connected to "Extra output 6" http://www.vems.hu/files/MembersPage/PeterJensen/51731635411_2.jpg ---- Round only AIM Hi Setting up aim coolant temperature something goes wrong while temp goes form 99 to 100 degrees. Should be 100 but at the display i can see number 180. I have used the predefined values and working great until it gets to 100 degrees. Firmware version 0.5.3
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.