Marcell,please call me when you finished my new ECU.
- Wiring complete,sensors working,i can see the gauges in Megatune,but there is no RPM signal yet (can wrong calibration (60-2 instead of 5 window) cause this?)
- primary_trigger=FF (or FE if falling edge is used). The primary_trigger=01 is for multitooth (eg 60-2 missing-tooth) setup
- secondary_trigger=02
- TPS reads 10% after calibration,is this normal?
- of course NOT! increase tps_low
wishes for next v3.x ECM
- tachometer output (weryimportant for 5 coil config)
- primary trigger: VR crank 60-2 (changeable to HALL with dip switch if possible, so only the endplate needs to be removed)
- High voltage flyback (2+6diode)
- All 8 ignition/injector channels
- EGT and Knock
- 4bar MAP sensor onboard
- Programmable Shift light output (a p259 channel)
- baro (altitude) compensation: MAP measurement at startup. Separate baro sensor is not justified when you have WBO2: when we tune at (say) 200m above sea level, we add +10% fuel in the VE table, so ego_correction=-10% (-25 on display) that is good to appr. 5000m, and normally the WBO2 based ego correction will take away as much of the extra fuel as necessary.
under investigation:
- WBO2 analog output (for DVM or other ECM), eg.
- lambda=0.6 .. 1.45 => 0.6V .. 1.45V
- 1.45V .. 1.499V not used
- O2%=15..21% => 1.5V .. 2.1V (or should it be max 1.96V so the DVM can be left in 2V mode? maybe configurable)
- below < 0.55V: measurement error (eg. WBO2 sensor not heated). Alternatively this condition could be mapped to >2.5V for better margin, but when WBO2 controller is unpowered, 0V is "easier" to maintain
- Warning light output: activates when any measured data (that I list here) exceeeds it's programmable warning treshold:
- CLT: engine too hot
- EGT: exhaust too hot
- MAP: boost too high (BoostController misconfigured, or pneumatic problem)
- ...
Problem after engine was put back:
- 4 out of 10 startup is unsuccesful. LCD displays silly things and car runs like shit! Sometimes after succesfull starting LCD displays some kind of table data instead of realtime datas (as usually), but no keyboard is connected.
- you forgot to mention that this was after you pulled the engine and the ECM was also away for weeks. Check what could have been misconnected, or damaged. Check GND, GND5 and flyback too. Try to disconnect the LCD (maybe VCC occasionally shorts to GND in the LCD ?)
- Check firmware version (a report is neglected without this information and impossible to help)
- and verify firmware integrity
- or reflash with a new firmware
- check the config (publish mcd, mct: a report is neglected without this information and impossible to help) and compare with old known-good config
- logs can also help to identify the problem