Technical > Triggering

s14a sr20 trigger

(1/2) > >>

Kamuto:
hello, my friend is trying to start his car with vems + loom adapter, he get's rpm, but can't start it.. can someone take a look at the trigger   log, is it right for that nissan engine? 

this is standart trigger settings from vems menu. 4 window to primary trigger 360 sec trigger, not sure is this correct when it does not shows any sec trigger

jrussell:
That's backwards. On the Nissan engines, the 360 window trigger is the primary and the 4 window is the secondary. There's actually configlets for the Nissan engines in the primary trigger setup window (at the bottom of the window).

Kamuto:

--- Quote from: jrussell on November 01, 2015, 03:21:28 pm ---That's backwards. On the Nissan engines, the 360 window trigger is the primary and the 4 window is the secondary. There's actually configlets for the Nissan engines in the primary trigger setup window (at the bottom of the window).

--- End quote ---
thank you :D that's our mistake :) yes, I used that configlet, just could  not find info on nissans page :)

Kamuto:
sadly nope, I was not wrong,
http://www.vems.hu/wiki/index.php?page=MembersPage%2FFeroNissanTrigger
with 360 connected to primary I'm getting 20000rpm on cranking :)
could it be firmware?
or could it be c103? it's standart at this moment :)

VEMS:
Hello Kamuto,

Connect and setup your Nissan trigger as follows:

* primary trigger goes to the x cyl number window HALL (in your case 4cyl = 4 window).
* secondary trigger goes to the 360 tooth.
* verify window sync size, this is done as follows:
* forcing the ecu in safe mode, easiest todo by changing the prohibit low byte from (xx which is last two number of firmware version) to some other number.
* make a triggerlog cranking the engine 8-10 seconds
* your triggerlog will have both primary and secondary pulses logged (sectrig only inside the primtooth window). As an example here is a picture of one i made during some testing: http://vems.hu/dave/nissan_360_16-12-8-4_syncup_good.png
* take notes of the window sizes, Nissan trigger will sync to the longest window; for example if you Nissan trigger windows are 8-2-2-2 than we need to sync to 8sectrig window -> sectrig ignore should be set to 5-6.
* make sure to put your prohibit low byte back to the previous value to revert the safe mode.
* after window length verifcation and correct configuration make another triggerlog to verify all is wellIf you have any further questions are problem starting after that, please make a sharing report containing both triggerlogs (safe mode with prim and sectrig), triggerlog after longest window calibration and a short vemslog of the cranking sequence. I'll review and come back to you with my findings.

Best regards, Dave

Navigation

[0] Message Index

[#] Next page

Go to full version