6 cyl 2jz Toyota with ETC - Norway
Log with the strange behaviour would be of utmost importance. (preferrably with annotations like at ... sec happens ...)
The .vemslog file contains an immense amount of information (especially with 60-2 or 36-2 trigger, even per cylinder behavior). We cannot analyze the engine behavior from hearsay.
Because of the ETC, it is really important to sort this, and overview of the full install/setup is needed.
oid11617 (repair /upgrade).
Project URL provided: no (this was created later to facilitate progress).
On short paper, he requests to test inj and ign (logiclevel) outputs (every input and output passes tests).
At higher output engine does not work OK (maybe leans out ?)
ECU in/out seem to work OK.
HW Testing
We tested the v3/10001 multiple times, and a bit puzzled.
It passes output and input functional tests.
- Although these tests methods are primarily made for manufacturing (component, solder) defects, not for possibly external induced device damage, it usually shows any such problems clearly.
So the whole setup needs review.
We see a config inside, abstract:
- 6 cyl ( 6cyl 2jz Toyota acc. to orig oid)
- 6 logiclevel ign outputs
- 36-2 with camsync
- ETC enabled (seems intentional, orig oid had bridgeoutputdriver !)
- SD card logging is disabled. There is a 19 sec log, leftover from manufacturing. Unfortunately no log to review.
We will review the wiring setup carefully (ground, flyback, ... thickness and wire colors would be useful in the same table), and compare with the config we have (or any config or log provided on same thematical page). Log with the strange behaviour would be of utmost importance.
Reviewing ecu vemscfg (not much use without vemslog, or any setup details)
Some ETC misconfiguration present. See [VT ETC help]
- ETC integral window curve bad setup
- error threshold 5v (disabled), tps1/tps2 calibration curve not filed (prolly not connected); pps1 has narrow range,
- most likely using pps2 as pps1 (also bad), pps2 calibration curve confirms (filled 0.6-4.08 range)
- fuel wise, the deadtime table is filled with quite high values, seems to have forgotten to substract closing time;
- req fuel is tad high but compensated by scaled down (bad resolution) ve table (otherwise could be okay-ish)
- Dave says: if he provides a vemslog i can do a more thorough review
Leaning out on high power can be so many other things:
- like alternator low capacity (dropping voltage at high rpm)
- fuel pump to small, pressure dropping
- regulator problem
- ...
v3/10001 Orig specs
1 x ECU VEMS V3
- 1-wire interface: no
- EGT input: 1
- Flyback: HighZ-only 30V flyback
- ignition driver: 2+6
- Knock input channels: 0
- LCD connection: no
- MAP connection: 400 kPa simplenipple
- mounting-style: flanged case
- primary_trigger: EC36/27 VR
- secondary_trigger: EC36/13VR
- Service: normal
- withSDcard: removable
1 x MAT sensor
5 x Bluetooth-RS232 adapter
- With wire: Wired-in 12V Dual USB Power Supp
Orig order request confirms ETC application:
We will probably use all analog inputs here so:
- ETC = 3 without pullup + tps input.
- ALS on/off with pullup
- Oil-pressure 3pin = without pullup
- oiletemp = with pulluo
- launch on/off = with pullup
- EGT 1x
Please configure BridgeOutputDriver with 2 pushpull + 4 highside drivers.
Please equip VEMS ECU with flying loom connector for BridgeOutputDriver with 4 highside drivers, and min 3+1 analog inputs on EC18