5cyl 2.5L double VVT engine volvo/ford engine model: ...
CAM HALL/HALL:
Secondary trigger sensor on Exhaust camshaft
Third trigger(exhaust) sensor on the intake camshaft.
VVT solenoids was disconnected when i recorded the triggerlog.
Now i have just LESSSECTRIG error.
Here is the triggerlog. http://www.vems.hu/files/Norbitron/GM/riseandfall.triggerlog
Triggerlog review
Hello Norby,
I have reviewed your triggerlog, the sectrig pulses are all evenly spaced even with filtering this would not work (with 4 pulses per cam rotation), please make another triggerlog with secondary trigger edge inverted (so change from rising -> falling or falling to rising). Than make another triggerlog 8-10 seconds cranking no ign and inj fuse.
Best regards, Dave
Hello Dave!
Here is the new triggerlog, changed from falling to rising both camshaft trigger.
http://www.vems.hu/files/Norbitron/16Vbuild/risingcrank.triggerlog
Thanks
Norbi
What secondary trigger settings should i use for this?
There are 22tooth From 0th prtrig tooth to first sectrig pulse, second pulse from 0th tooth at 52nd primtrig tooth.
Other problem
When Motronic trigger input connected parallel to VEMS EC36/27 and switch=ON and engine rpm=0 the ETC noise can cause RPM signal fluctation. If i cranking or the engine is running this isn't cause any problem.
Primary VR
- Later it was changed to a new honeywheel 1gt101dc HALL sensor from WebShop .
- does the HALL sensor really sense the VR wheel ? That could explain the symptoms, swapping in HALL sensor with the VR wheel sounds like the wrong track
- Or, if some custom wheel... what is the wheel like, exactly ?
- 60-2 big diameter wheel on flywheel.
- maybe it has runout, or some asymetry ? (slanted, or sg...?)
- Or, if some custom wheel... what is the wheel like, exactly ?
- does the HALL sensor really sense the VR wheel ? That could explain the symptoms, swapping in HALL sensor with the VR wheel sounds like the wrong track
- a VR sensor in place of the 1gt101dc (put back the original) could reveal when captured with oscilloscope (not just VEMS InputTrigger/TriggerLog).
- anyone could suggest some engine/car models with a mechanically compatible VR sensor, or sg. close ? Seems like this very engine also, what is the original engine model ? The engine is a VOLVO 2.5 5cylinder 20VT Engine in a Ford Focus ST.
The VR scope captures:
Cranking with VEMS and MOTRONIC
Cranking with VEMS
IDLE with VEMS+MOTRONIC(bit lower idle)
IDLE with VEMS:
CAM HALL/HALL
Fuel pressure sensor
Outside 12V 400kpa MAP
5*coil on plug, drive by +5V logic level.
Drive by wire throttle body
New Intake and IAT sensor, separated from Motronic.
Crank sensor has shielded cable, the shield connected to GND on 1 point.
VEMS and Motronic has a shared Primary trigger signal. VEMS originally had 27k pullup resistor.(pullup resistor uninstalled)
Motronic primary trigger input voltage is 2.46V to GND
Before first start i made two triggerlog, One when motronic connected and one without. Without motronic: seemed good. TDC delay was set up. Started easily. It was running fine, But trigger error flag was on everytime. After this i disconnected the motronic, started easily again but nothing changed... Triggerlogs (captured with 115200 baud ?) seems like a sh..t. when the engine running(also with 1 or 2 ECU, it doesn't matter)
Engine can be revved up to 7krpm without missfire. Maybe there was some small missfire but it was revving up easily.
Some strange symptons:
When crank sensor connected to both ECU, and I'm playing the throttle (drive by wire), the VEMS shows CRANKING flag, Fuel pump on, and sometimes open the injectors and sparking the coils randomly, Sometimes it showed 10-6500RPM on RPM gauge when i moving the Throttle. It seems shield problem.... but i checked many times and it must be good. When motronic ecu disconnected this problem aren't.
I measured the VR sensor resistance: 130ohm...it seems very very low. I tought this is the problem.
- Any VR scopeshots ? Those would be interesting.
- If VR signal does not cross 0mV, a resistor divider toward -8V could help as an experiment:
- eg 4k7 between VR input and -8V (available on LCD pinheader inside the ECU),
- and 1k between VR input and VR signal.
- If VR signal does not cross 0mV, a resistor divider toward -8V could help as an experiment:
I put out the sensor and seemed It has same house like 1GT101DC HALL sensor. I installed this HALL sensor and changed the VEMS(solder the jumpers and R30=2k7 pullup resistor) and the shielded cable pinout for HALL sensor. The cable still shielded.
So HALL sensor sensing the factory VR wheel ? Seems like the bad direction, That is not a good combination, it might not work !
I recorded a triggerlog when cranking, and on idle. It seems also sh..t when the engine is running. Very strange because this is a HALL sensor with shield from sensor to ECU connector...
VEMS Power GNDs and sensor GND points connected like you always recommend. I connected the GND point on the cylinder head at firts time and after tried on battery - but didn't help.
The engine's GND cable are strong, cranking fast and powerfully.
The other sensor signals seems good. There aren't fluctation....Maybe when the engine running the 5V analogs are dropping 0.01V.
I tried to run the engine without ETC controller(without high frequency/high current), hold the valve manually but the triggers also bad.
I checked the HALL sensor signal with oscilloscope and it seems very very bad on idle. I didn't check the VR signal with scope.
And an other perception: I measured +0.02V between every sensor's GND pin and GND(cylinder head or battery - )
I can't reving the engine up from 5500rpm with HALL sensor. When the fuel tank empty... you can see it on the log file.
files:
5V supply change and acceleration enrichment failure when ETC PID works...)
VR IDLE: http://www.vems.hu/files/Norbitron/GM/VRIDLE.triggerlog
VR Cranking disconnected ETC: http://www.vems.hu/files/Norbitron/GM/VRCRANKING.triggerlog
VR CRANKING with connected ETC: http://www.vems.hu/files/Norbitron/GM/VRCRANKETC.triggerlog
HALL stop at 5k5rpm: http://www.vems.hu/files/Norbitron/GM/STOP5K5.vemslog
HALL sensor IDLE: http://www.vems.hu/files/Norbitron/GM/HALLIDLE.triggerlog
HALL sensor cranking: http://www.vems.hu/files/Norbitron/GM/HALLCRANK.triggerlog
Scope of HALL signal. 