History of MembersPage/Norbitron/Trigvrsix
Older Newer
2018-02-12 09:11:10 . . . . catv-86-101-250-44.catv.broadband.hu [minor: formatting, and simple]
2018-02-12 08:22:21 . . . . catv-86-101-250-44.catv.broadband.hu [tested a standard ECU with runout signal]
2018-02-12 05:16:53 . . . . catv-86-101-250-44.catv.broadband.hu [almost certainly wheel runout]
2018-02-01 14:11:46 . . . . 88.119.113.145 [some my own experience]
2018-02-01 12:36:40 . . . . 3EC94A3A.catv.pool.telekom.hu [vrsix trigger error]
2018-02-01 12:30:54 . . . . 3EC94A3A.catv.pool.telekom.hu [vrsix trigger error]


Changes by last author:

Changed:
The battery (+) disconnected and shorted to GND before first cranking and startup. The HIFI audio system has had a big capacitor so it was discharged and sparked. After this the p259 chip has gone. There wasn't 5V on the lm1815 Pin8 and didn't read RPM signal. I changed the p259 chip, rpm shown, engine was started up.
Serious Primary trigger VR wheel "runout" (systematic amplitude variations within 1 rotation) suspected, at 2300 RPM less ptrig error. See InputTrigger/RunOut .

Not this v3/14333 ECU, but a very similar standard VEMS ECU (VR/HALL but sectrig disabled) was tested with a runout primtrig signal:

* 54..100% (and 125% tooth0 amplitude)

** worked perfectly with the factory R37=1M * 220nF (C38), well upto 10kRPM

** Marcell expected it to show trigger error at some RPM.

** Verified with scope that signal did NOT rail (amplitude really changed appr 2x fold each crankperiod ).

----

Russian roulette install

* home-assembled (not benchtested before the field)

** this alone should not be a big problem (although adds to the uncertainty for sure), later benchtests showed that trigger input worked well (tested to 10k RPM)

** even with unusually high missing tooth amplitue [ m582 signal wav]

* installing far from home (on another continent, in USA)

* GND problem => p259 damage

* no scope

* not even soundcard recording of VR signal

* no wiki page at the time of install (this page was created later)

The last 2..3 makes it extremely risky and waste a lot of time, basically impossible to support. In case of any install issue, without scopeshots we are showing darts in the dark, (sometimes making things even worse, and not knowing).

----

The battery (+) disconnected and shorted to GND before first cranking and startup. The HIFI audio system has had a big capacitor so it was discharged and sparked

* => p259 damaged. No 5V on the lm1815 Pin8, RPM=0

** New p259 chip: RPM good, engine started up.

Changed:
"Less tr. error" flag and missfire comes on 1800-2000rpm.
"Less tr. error" flag and misfire at 1800-2000rpm.
Changed:
r181=150K originaly, I changed it to 270K, This was the only thing when i saw some change. The "tr error" came around 2300rpm. I kept the r181=270K and If i changed the r30 from 1k to 33K again. Without different.

I tried to increase the r180 but the "tr error RPM edge come down".

The best setup was: r30=22K, r180=270K.

Originaly lm1815 pin5=4.95V, i jumpered it to 5V and changed the r30 from 1k to 33k again, No result.

R181=150K originally, I changed it to 270K, This was the only improvement: The "tr error" came around 2300rpm

* I kept the r181=270K and If i changed the r30 from 1k to 33K again. Without different.

I tried to increase the R181 but the "tr error" came at lower RPM

The best setup was: r30=22K, r180=270K.

Originally lm1815 pin5=open (measured 4.95V, interestingly), i jumpered pin5=5V and changed R30 from 1k to 33k again, No result.

* also tried 1k pulldown as adviced ?

----

Simple input threshold without noise suppression

HALL input (as a last experiment).

I tried to solder the ECU from VR to HALL as Marcel advised, R30= 1K. Ec18/27 voltage = 2.40V, no rpm signal read when cranking.

This path was abandoned without trying to adjust input threshold to trigger (so engine did not start at all).

Changed:
I tried to solder the ECU from VR to HALL as Marcel adviced, r30= 1K. Ec18/27 voltage = 2.40V, no rpm signal read when cranking.

I tried the "Play trigger" tool but i saw trigger error and wrong rpm reading all the time. same on VR and HALL jumpered ECU Hw settings.

Another possible path (this was not attempted) is to use an NPN inverter (external or internal)

* possibly from the onboard sectrig circuit, easy enough especially that sectrig is not used at all here:

** VR => sectrig and internally connect the NPN inverter output to primtrig (or as an experiment configure "sectrig used as primtrig" before doing the HW mod.):

** with some input bias (eg 900 Ohm sensor and appr 6..7kOhm pullup to +5V) it is possible to set appr +0.55V bias for the NPN inverter, so cranking triggers the HALL input

This is similar to the simple triggerdetection with no noise suppression that simpler circuits use. Usually inferior, but might be the way to go if toothamplitude changes are extreme, but noise is not a problem.

----

Improvised bench-setup

I tried the "Play trigger" tool

* but i saw trigger error and wrong RPM reading all the time.

* same on VR and HALL jumpered ECU Hw settings.

* tried to play wav from audacity ? Perhaps some 3D sound special effect interfered ?

Deleted:
I gave the ECU to Peter in baratka street to test. At first time we saw some weird RPM reading values.... need more testing.
Added:
Tooth 45 time is slightly off indeed, but nothing extreme.

* Wheel is most likely eccentric,

** which cannot be seen from triggerlog, unfortunately, but scopeshot or soundcard recording would show clearly, immediately. Marcell