| [Start] | [Questions ] | [ Injector] | [Ignition] | [Triger] | [Display] | [Wbo2] | [Config] | [Table] | [Wiring] |
EGO susses
I changed the injector set up and ego_pid_kp=20 all is working now great Marcell.
So way the old settings doesn’t work that is a mystery
Wonder about the firing order you recommend (h0) 02 08 04 01) should is not be (h0) 04 01 02 08 please look at this http://www.vems.hu/wiki/index.php?page=MembersPage%2FpeterJenseninjector.
My plan in the future is to run full sekventiel with cam trigger.
Thanx Peter
Question: 4/1-06
EGO settings and mode of operation.
When I turn on the EGO control then the car runs very lean ??
The VE table is adjust and the car is running well (lambda 1/14,7afr) but when the ecu hit the switch point to active the ego (1500 rpm) then its start to run lean. The lambda table is 1.0 in all the low bins.
Also if I force the lambda table to give more petrol (12 afr) the ego clock megatune stay at the same point no reaction but stay at the lean side.
It seems like something is inverted so ego react the opposites way.
If someone have an idée please write
- firmware version
- 1.0.23 firmware
- mct - as dumped from controller (TerminalProgram Man mct)
- mcd - as dumped from controller (TerminalProgram Man mcd)
- did you calibrate the WBO2 sensor ?
- Yes i did
- wbo2_calibration value ?
- calibration value 165 dicimal
- wbo2 sensor resistance ? (between sensor pin2 and pin6)
- Haven’t measure the resistance in the wbo2
- is the genboard supply voltage sufficient ?
- Yes min 14v
- MegaTune version
- [r028 complete package, with 1.0.23 firmware]
I suspect that
- it's not configured well for WBO2 (beware, driving long with this can deposit carbon on your LSU4 sensor => ruin it)
- or MegaTune lambda table is displayed bad because version used is incompatible with firmware.
Config suspicious items / hints:
- why are you firing all 4 injectors at the same time (h[0]) and twice every cam revolution ?
- h[0]=02 08 04 01 .... # (not 0F ...)
- alternate=03 # not 10 ; but increase cwl, cwh to appr 2x fuel quantity
- divider=01 # not 02
- cranking_thres=03 # = 399 RPM (megatune says 300); not 06 ; 699 RPM is awfully high
- req_fuel=23
- doubling the VE j[] values (so max is around 200, not 100) and half req_fuel would be a good idea for tuning precision. But works this way to. Btw, you seem to have big injectors.
However, these don't explain any strange ego behaviour that you describe. But:
- ego_pid_kp=20 # instead of 01 ; also called as "incredible speed limit"
- ego_lag=01 # instead of 04
will make your EGO (128 times) faster, to near the reasonable value. It was configured so slow that it acted like a very long timeconstant filter (acting according to the average of last minute, not last few hundred msec), which explains the "reversion".
Questions: 5/11-05.
LCD problem
- The DSUB9 connector to the LCD had a bad connection or short-circuit so I cant get any numbers on the display now (worked well before)
- measure every connection for connectivity. End-to-end measurement is best ( relevant LCD pin to onboard pinheader - or DSUB9 if assembled controller is clamped ).
- document exactly your measurements (using pin numbers, colors, measured resistance). Also, link to docs you used in the first place.
- measure neighboring connections for shortcircuit. Also check againt GND (LCD metallic case)
If you apply some hotmelt after testing (at the DSUB9 and where the wires enter the LCD) and use good clearances, it's unlikely to cause problems later.
Repair display
Would it not be a god start to replace the IC1 with a new IC to fix the display
NO !!! SMD unsoldering is 5 times harder than making a proper LCD cable. Make a proper LCD cable first.
- Answer: I made a new display include wiring so of course all the connections are checked.
- I think the problem may be found in the PCB but maybe it is not possible to measure the component there is bad or is there something I can do?
- unfortunately, there is no simple establised way to debug a possibly damaged board. Disable the stepper and test the S259 3..6 outputs (mdh36, mdh46, mdh56, mdh66 commands to reset, and mdhb6, mdhc6, mdhd6, mdhe6 to set), even possible with assembled ECM. Outputs 1 and 2 should work too (available on the LCD header), not sure about outputs 0 and 7.
- You can document how initially connected the bad LCD, so that might help
- FACT
- There is light in the display. But the light is only 2 LEDs, quite independent from the main logic.
- Tried to replace with a new display include wiring and sub D but same negative result
- it would first make sense to make sure the new LCD + wire is correct (with another genboard?)
Remember that the most common mistake is forgetting the LCD contrast. (a 2k4 - or around - resistor between LCDpin1 GND and LCDpin3 contrast). If LCD shows nothing (neither squares nor garbage) this is the problem, almost for sure.