283 lines
6.6 KiB
Markdown
283 lines
6.6 KiB
Markdown
|
|
See also [Trigger](Trigger)
|
|
|
|
To change your trigger settings, open TunerStudio, Engine->Trigger Configuration
|
|
|
|
[Universal](#universal)
|
|
|
|
[GM](#gm)
|
|
|
|
[Honda](#honda)
|
|
|
|
[Mazda](#mazda)
|
|
|
|
[Nissan](#nissan)
|
|
|
|
[Subaru](#subaru)
|
|
|
|
[Jeep & Renix](#jeep)
|
|
|
|
[Miscelanious](#misc)
|
|
|
|
|
|
## Universal 36/1
|
|
|
|
<a name="universal"/>
|
|
|
|
## 60/2
|
|
|
|
If you also have a CAM sensor somewhere see [VVT](VVT)
|
|
|
|
![60/2](Images/triggers/trigger_8.png)
|
|
|
|
## 36/1
|
|
|
|
![36/1](Images/triggers/trigger_9.png)
|
|
|
|
## 36/2
|
|
|
|
![x](Images/triggers/trigger_48.png)
|
|
|
|
## Bosch Quick Start
|
|
|
|
![x](Images/triggers/trigger_47.png)
|
|
|
|
|
|
<a name="honda"/>
|
|
|
|
## Honda K 1/12
|
|
|
|
![x](Images/triggers/trigger_46.png)
|
|
|
|
## Honda 1+24
|
|
|
|
![x](Images/triggers/trigger_21.png)
|
|
|
|
## Honda CBR600
|
|
|
|
![Honda CBR600](Images/triggers/trigger_28.png)
|
|
|
|
<a name="mazda"/>
|
|
|
|
## Mazda Protege SOHC
|
|
|
|
![Mazda Protege SOHC](Images/triggers/trigger_7.png)
|
|
|
|
## Mazda Miata NA
|
|
Also used on some Mitsubishi
|
|
|
|
![Mazda Miata NA](Images/triggers/trigger_3.png)
|
|
|
|
## Mazda Miata NB
|
|
|
|
![Mazda Miata NB1](Images/triggers/trigger_4.png)
|
|
|
|
## Mazda Protege 1993 DOHC
|
|
|
|
![Mazda Protege 1993 DOHC](Images/triggers/trigger_15.png)
|
|
|
|
## Mazda 121/Ford Aspire
|
|
|
|
![Ford Aspire](Images/triggers/trigger_1.png)
|
|
|
|
<a name="gm"/>
|
|
|
|
## GM 7x
|
|
|
|
![GM 7x](Images/triggers/trigger_5.png)
|
|
|
|
## GM LS 24x
|
|
|
|
![x](Images/triggers/trigger_27.png)
|
|
|
|
## GM 60/2/2/2
|
|
|
|
GM/Daewoo Distributor F8CV
|
|
|
|
![x](Images/triggers/trigger_54.png)
|
|
|
|
<a name="jeep"/>
|
|
|
|
## Jeep 18-2-2-2
|
|
|
|
![Jeep 18-2-2-2](Images/triggers/trigger_37.png)
|
|
|
|
## Renix 44/2/2
|
|
|
|
![x](Images/triggers/trigger_44.png)
|
|
|
|
## Renix 66/2/2/2
|
|
|
|
![x](Images/triggers/trigger_45.png)
|
|
|
|
|
|
<a name="subaru"/>
|
|
|
|
## Subaru 7+6 tooth
|
|
|
|
![Subaru 7+6](Images/triggers/trigger_36.png)
|
|
|
|
## Subaru SVX
|
|
|
|
![x](Images/triggers/trigger_49.png)
|
|
|
|
<a name="suzuki"/>
|
|
|
|
## Suzuki G13B
|
|
|
|
![x](Images/triggers/trigger_66.png)
|
|
|
|
## 36/2/2/2
|
|
|
|
Might also be used on some Daihatsu, Nissan and Miata
|
|
|
|
![36/2/2](Images/triggers/trigger_23.png)
|
|
|
|
## Universal skipped wheel
|
|
A basic wheel - assumes equally spaced teeth with a number of missing teeth.
|
|
Tuner studio allows up to 500 teeth with 500 missing - functional limits are not tested.
|
|
|
|
<a name="misc"/>
|
|
|
|
## Ford Barra VVT
|
|
|
|
![x](Images/triggers/trigger_56.png)
|
|
|
|
## Daihatsu
|
|
|
|
![x](Images/triggers/trigger_6.png)
|
|
|
|
## Ford ST170
|
|
|
|
![x](Images/triggers/trigger_42.png)
|
|
|
|
## One tooth
|
|
|
|
![One Tooth](Images/triggers/trigger_18.png)
|
|
|
|
## Dodge Neon 1995
|
|
|
|
![Dodge Neon 1995](Images/triggers/trigger_2.png)
|
|
|
|
## Dodge Neon 1995 only crankshaft sensor
|
|
|
|
![Dodge Neon 1995 crank only](Images/triggers/trigger_39.png)
|
|
|
|
## Dodge Hemi and SRT4
|
|
|
|
![x](Images/triggers/trigger_30.png)
|
|
|
|
|
|
## Dodge Ram
|
|
|
|
![Dodge Ram](Images/triggers/trigger_19.png)
|
|
|
|
## Dodge Neon 2003
|
|
Chrysler NGC 4 cylinder
|
|
|
|
![Dodge Neon 2003](Images/triggers/trigger_14.png)
|
|
|
|
## Dodge Stratus
|
|
Chrysler NGC 6 cylinder
|
|
|
|
![Dodge Stratus](Images/triggers/trigger_22.png)
|
|
|
|
## Nissan
|
|
|
|
VQ35
|
|
![x](Images/triggers/trigger_58.png)
|
|
![x](Images/triggers/trigger_59.png)
|
|
|
|
|
|
VQ30
|
|
![x](Images/triggers/trigger_60.png)
|
|
|
|
360 slot trigger not ready yet, no test vehicles :(
|
|
|
|
![Nissan](Images/triggers/trigger_24.png)
|
|
|
|
## 1 + 60/2
|
|
|
|
Please use this one only if your CAM sensor position matches this picture exactly. For a CAM which does not match this picture exactly, see above for universal 60/2 with cam input.
|
|
|
|
![1+60/2](Images/triggers/trigger_17.png)
|
|
|
|
## VW 60/2
|
|
VW special understanding of 60/2 with a wide tooth instead of of just missing tooth.
|
|
|
|
See also [Universal True 60/2](All-Supported-Triggers#602)
|
|
|
|
![VW 60/2](Images/triggers/trigger_20.png)
|
|
|
|
## Toyota 2JZ
|
|
|
|
3/34 version
|
|
|
|
![Toyota 2JZ 3/34](Images/triggers/trigger_25.png)
|
|
|
|
1/12 version
|
|
|
|
![Toyota 2JZ 1/12](Images/triggers/trigger_29.png)
|
|
|
|
## TriTach
|
|
|
|
Some older German vehicles
|
|
|
|
![x](Images/triggers/trigger_53.png)
|
|
|
|
## Skoda Favorit
|
|
|
|
![x](Images/triggers/trigger_55.png)
|
|
|
|
## Ford PIP
|
|
|
|
![Ford PIP](Images/triggers/trigger_65.png)
|
|
|
|
|
|
|
|
## Unknown trigger type
|
|
|
|
[Unknown Trigger](Unknown-Trigger)
|
|
|
|
TODO: implement a feature so that trigger could be defined via TunerStudio
|
|
|
|
|
|
If your have an unknown or an unsupported trigger shape, once you've confirmed that trigger events are getting into the software (see "troubleshooting" sections) you need to crank your engine while rusEFI console is connected with Engine Sniffer tab active.
|
|
|
|
With long enough cranking you should get a visual log of your trigger signal, that would give you some idea of what kind of trigger shape you have. Save an image and post it on a forum. It's recommended to remove spark plugs while investigating trigger shape to make your cranking more even.
|
|
|
|
Once preliminary shape of a new trigger is added into rusEFI firmware based on the Engine Sniffer image, second step is getting a more precise recording of the shape with exact angles. This is done with spark plugs removed and Sensor Sniffer mode set to TRIGGER. With long enough cranking a chart of trigger shape would appear on the Sensor Sniffer tab and the console log file (see out/ folder next to rusefi console binaries) would contain the angles. Please post this log file on the forum for the developers to encode the new trigger shape into the software.
|
|
|
|
## How this works
|
|
|
|
Trigger decoding cycle starts at 'synchronization point' - that's the trigger fall or rise event which satisfies the 'synchronization gap' condition. Since trigger synchronization point usually has nothing to do with top dead center #1 (TDC), we have have 'globalTriggerAngleOffset' parameter - that's the offset between synchronization point and TDC.
|
|
|
|
For example, 'set global_trigger_offset_angle 0', TDC is set to synchronization point, the green vertical line is TDC mark:
|
|
|
|
![Offset Angle 0](Images/offset_0.png)
|
|
|
|
Now the real TDC, 'set global_trigger_offset_angle 175' command:
|
|
|
|
![Offset Angle 175](Images/offset_175.png)
|
|
|
|
Note the different location of the green TDC line. Also note how all Injector #1 pulse has moved (injector #3 is the lowest signal on these pictures) - that's because ignition and injection are scheduled based on TDC point.
|
|
|
|
While running ignition is controlled by ignition timing map, you can also offset the whole ignition timing map using 'set ignition_offset' command. Ignition dwell is controlled by dwell time curve.
|
|
|
|
Injection could be offset using 'set injection_offset X' command.
|
|
|
|
While cranking, you can set angle-based ignition instead of timing map & dwell based ignition. In angle-based mode, dwell is defined in crankshaft angle duration and timing is constant. set cranking_charge_angle and set_cranking_timing_angle.
|
|
|
|
|
|
See 'trigger decoding' in http://rusefi.com/docs/html/
|
|
|
|
May, 2020: Subaru SVX added
|
|
|
|
April, 2020: Honda K 12+1 added.
|
|
|
|
April, 2020: Renix 44-2-2 added.
|
|
|
|
Dev note: unit_tests executable produces triggers.txt file - gen_trigger_images.bat reads triggers.txt and produces these .png files. TODO: automate this further?
|
|
|
|
|