cool stuff
This commit is contained in:
rusefi
parent
50277fcb62
commit
9c5a27dbfa
|
|
@ -1,4 +1,5 @@
|
|||
# Advanced
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Advanced
|
||||
[Boost Control](#Boost-Control)
|
||||
|
||||
[General Purpose PWM 1](#General-Purpose-PWM-1)
|
||||
|
|
@ -33,83 +34,104 @@
|
|||
|
||||
[FSIO Curve #4](#FSIO-Curve-#4)
|
||||
|
||||
## Boost Control
|
||||
### Boost Control
|
||||
|
||||
## General Purpose PWM 1
|
||||
|
||||
### General Purpose PWM 1
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
On above duty(%): In on-off mode, turn the output on when the table value is above this duty.
|
||||
|
||||
Off below duty(%): In on-off mode, turn the output off when the table value is below this duty.
|
||||
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.\nThis should be a safe value for whatever hardware is connected to prevent damage.
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.
|
||||
This should be a safe value for whatever hardware is connected to prevent damage.
|
||||
|
||||
Load Axis: Selects the load axis to use for the table.
|
||||
|
||||
## General Purpose PWM 2
|
||||
### General Purpose PWM 2
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
On above duty(%): In on-off mode, turn the output on when the table value is above this duty.
|
||||
|
||||
Off below duty(%): In on-off mode, turn the output off when the table value is below this duty.
|
||||
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.\nThis should be a safe value for whatever hardware is connected to prevent damage.
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.
|
||||
This should be a safe value for whatever hardware is connected to prevent damage.
|
||||
|
||||
Load Axis: Selects the load axis to use for the table.
|
||||
|
||||
## General Purpose PWM 3
|
||||
### General Purpose PWM 3
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
On above duty(%): In on-off mode, turn the output on when the table value is above this duty.
|
||||
|
||||
Off below duty(%): In on-off mode, turn the output off when the table value is below this duty.
|
||||
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.\nThis should be a safe value for whatever hardware is connected to prevent damage.
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.
|
||||
This should be a safe value for whatever hardware is connected to prevent damage.
|
||||
|
||||
Load Axis: Selects the load axis to use for the table.
|
||||
|
||||
## General Purpose PWM 4
|
||||
### General Purpose PWM 4
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
On above duty(%): In on-off mode, turn the output on when the table value is above this duty.
|
||||
|
||||
Off below duty(%): In on-off mode, turn the output off when the table value is below this duty.
|
||||
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.\nThis should be a safe value for whatever hardware is connected to prevent damage.
|
||||
Duty if error(%): If an error (with a sensor, etc) is detected, this value is used instead of reading from the table.
|
||||
This should be a safe value for whatever hardware is connected to prevent damage.
|
||||
|
||||
Load Axis: Selects the load axis to use for the table.
|
||||
|
||||
## FSIO inputs
|
||||
### FSIO inputs
|
||||
|
||||
## Aux PID
|
||||
|
||||
### Aux PID
|
||||
|
||||
|
||||
Detailed status in console: Print details into rusEfi console
|
||||
|
||||
## FSIO outputs
|
||||
### FSIO outputs
|
||||
|
||||
## FSIO Table #1
|
||||
|
||||
### FSIO Table #1
|
||||
|
||||
## FSIO Table #2
|
||||
|
||||
### FSIO Table #2
|
||||
|
||||
## FSIO Table #3
|
||||
|
||||
### FSIO Table #3
|
||||
|
||||
## FSIO Table #4
|
||||
|
||||
### FSIO Table #4
|
||||
|
||||
## FSIO Formulas
|
||||
|
||||
### FSIO Formulas
|
||||
|
||||
|
||||
use FSIO #16 for timing adjustment: See fsioTimingAdjustment
|
||||
|
||||
## FSIO Curve #1
|
||||
### FSIO Curve #1
|
||||
|
||||
## FSIO Curve #2
|
||||
|
||||
### FSIO Curve #2
|
||||
|
||||
## FSIO Curve #3
|
||||
|
||||
### FSIO Curve #3
|
||||
|
||||
## FSIO Curve #4
|
||||
|
||||
### FSIO Curve #4
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Base Engine
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Base Engine
|
||||
[Base Engine Settings](#Base-Engine-Settings)
|
||||
|
||||
[Trigger](#Trigger)
|
||||
|
|
@ -19,25 +20,42 @@
|
|||
|
||||
[Status LEDs](#Status-LEDs)
|
||||
|
||||
## Base Engine Settings
|
||||
### Base Engine Settings
|
||||
|
||||
Fuel strategy: This setting controls which fuel quantity control algorithm is used.\nSee also useTPSAdvanceTable\nset algorithm X
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode\n\nset debug_mode X
|
||||
Fuel strategy: This setting controls which fuel quantity control algorithm is used.
|
||||
See also useTPSAdvanceTable
|
||||
set algorithm X
|
||||
|
||||
Fuel strategy: This setting controls which fuel quantity control algorithm is used.\nSee also useTPSAdvanceTable\nset algorithm X
|
||||
Debug mode: See http://rusefi.com/s/debugmode
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode\n\nset debug_mode X
|
||||
set debug_mode X
|
||||
|
||||
Fuel strategy: This setting controls which fuel quantity control algorithm is used.\nSee also useTPSAdvanceTable\nset algorithm X
|
||||
Fuel strategy: This setting controls which fuel quantity control algorithm is used.
|
||||
See also useTPSAdvanceTable
|
||||
set algorithm X
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode\n\nset debug_mode X
|
||||
Debug mode: See http://rusefi.com/s/debugmode
|
||||
|
||||
## Trigger
|
||||
set debug_mode X
|
||||
|
||||
Fuel strategy: This setting controls which fuel quantity control algorithm is used.
|
||||
See also useTPSAdvanceTable
|
||||
set algorithm X
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode
|
||||
|
||||
set debug_mode X
|
||||
|
||||
### Trigger
|
||||
|
||||
Operation mode / speed: 'Some triggers could be mounted differently. Most well-known triggers imply specific sensor setup. 4 stroke with symmetrical crank' is a pretty special case for example on Miata NB2\nSee engineCycle\nset operation_mode X
|
||||
|
||||
use only rising edge: VR sensors are only precise on rising front\nenable trigger_only_front
|
||||
Operation mode / speed: 'Some triggers could be mounted differently. Most well-known triggers imply specific sensor setup. 4 stroke with symmetrical crank' is a pretty special case for example on Miata NB2
|
||||
See engineCycle
|
||||
set operation_mode X
|
||||
|
||||
use only rising edge: VR sensors are only precise on rising front
|
||||
enable trigger_only_front
|
||||
|
||||
VVT use rise front: Use rise or fall signal front
|
||||
|
||||
|
|
@ -45,9 +63,12 @@ print verbose sync details to console: enable trigger_details
|
|||
|
||||
Do not print messages in case of sync error: Sometimes we have a performance issue while printing error
|
||||
|
||||
Operation mode / speed: 'Some triggers could be mounted differently. Most well-known triggers imply specific sensor setup. 4 stroke with symmetrical crank' is a pretty special case for example on Miata NB2\nSee engineCycle\nset operation_mode X
|
||||
Operation mode / speed: 'Some triggers could be mounted differently. Most well-known triggers imply specific sensor setup. 4 stroke with symmetrical crank' is a pretty special case for example on Miata NB2
|
||||
See engineCycle
|
||||
set operation_mode X
|
||||
|
||||
use only rising edge: VR sensors are only precise on rising front\nenable trigger_only_front
|
||||
use only rising edge: VR sensors are only precise on rising front
|
||||
enable trigger_only_front
|
||||
|
||||
VVT use rise front: Use rise or fall signal front
|
||||
|
||||
|
|
@ -55,9 +76,12 @@ print verbose sync details to console: enable trigger_details
|
|||
|
||||
Do not print messages in case of sync error: Sometimes we have a performance issue while printing error
|
||||
|
||||
Operation mode / speed: 'Some triggers could be mounted differently. Most well-known triggers imply specific sensor setup. 4 stroke with symmetrical crank' is a pretty special case for example on Miata NB2\nSee engineCycle\nset operation_mode X
|
||||
Operation mode / speed: 'Some triggers could be mounted differently. Most well-known triggers imply specific sensor setup. 4 stroke with symmetrical crank' is a pretty special case for example on Miata NB2
|
||||
See engineCycle
|
||||
set operation_mode X
|
||||
|
||||
use only rising edge: VR sensors are only precise on rising front\nenable trigger_only_front
|
||||
use only rising edge: VR sensors are only precise on rising front
|
||||
enable trigger_only_front
|
||||
|
||||
VVT use rise front: Use rise or fall signal front
|
||||
|
||||
|
|
@ -65,8 +89,9 @@ print verbose sync details to console: enable trigger_details
|
|||
|
||||
Do not print messages in case of sync error: Sometimes we have a performance issue while printing error
|
||||
|
||||
## Battery and Alternator Settings
|
||||
### Battery and Alternator Settings
|
||||
|
||||
|
||||
vBatt ADC input: This is the processor input pin that the battery voltage circuit is connected to, if you are unsure of what pin to use, check the schematic that corresponds to your PCB.
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
|
@ -91,16 +116,19 @@ Off Above TPS(%): Turns off alternator output above specified TPS, enabling this
|
|||
|
||||
Detailed status in console: Print details into rusEfi console
|
||||
|
||||
## Main relay output
|
||||
### Main relay output
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
## Starter relay output
|
||||
### Starter relay output
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
## Fuel pump rail
|
||||
### Fuel pump rail
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
Absolute Fuel Pressure: If your fuel regulator does not have vacuum line
|
||||
|
|
@ -113,23 +141,27 @@ Pin: This implementation produces one pulse per engine cycle. See also dizzySpar
|
|||
|
||||
Absolute Fuel Pressure: If your fuel regulator does not have vacuum line
|
||||
|
||||
## Fan Settings
|
||||
### Fan Settings
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
## Tachometer output
|
||||
### Tachometer output
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
Rise at trigger index: Trigger cycle index at which we start tach pulse (performance consideration)
|
||||
|
||||
## Check Engine Settings
|
||||
### Check Engine Settings
|
||||
|
||||
|
||||
Pin: This implementation produces one pulse per engine cycle. See also dizzySparkOutputPin.
|
||||
|
||||
## Status LEDs
|
||||
### Status LEDs
|
||||
|
||||
|
||||
Trigger error LED: This pin is used for debugging - snap a logic analyzer on it and see if it's ever high
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Controller
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Controller
|
||||
[ECU stimulator](#ECU-stimulator)
|
||||
|
||||
[Datalogging Settings](#Datalogging-Settings)
|
||||
|
|
@ -45,61 +46,82 @@
|
|||
|
||||
[AntiLag Settings NOT WORKING](#AntiLag-Settings-NOT-WORKING)
|
||||
|
||||
## ECU stimulator
|
||||
### ECU stimulator
|
||||
|
||||
## Datalogging Settings
|
||||
|
||||
### Datalogging Settings
|
||||
|
||||
## Bench Test & Commands
|
||||
|
||||
### Bench Test & Commands
|
||||
|
||||
## Popular vehicles
|
||||
|
||||
### Popular vehicles
|
||||
|
||||
## LCD screen
|
||||
|
||||
### LCD screen
|
||||
|
||||
## Joystick
|
||||
|
||||
### Joystick
|
||||
|
||||
## SPI settings
|
||||
|
||||
### SPI settings
|
||||
|
||||
|
||||
SPI1mosi mode: Modes count be used for 3v<>5v integration using pull-ups/pull-downs etc.
|
||||
|
||||
## rusEfi Console Settings
|
||||
### rusEfi Console Settings
|
||||
|
||||
|
||||
Sensor Sniffer: rusEfi console Sensor Sniffer mode
|
||||
|
||||
Engine Sniffer: This options enables data for 'engine sniffer' tab in console, which comes at some CPU price
|
||||
|
||||
## Connection
|
||||
### Connection
|
||||
|
||||
## TLE8888
|
||||
|
||||
### TLE8888
|
||||
|
||||
## All Pins 1/3
|
||||
|
||||
### All Pins 1/3
|
||||
|
||||
|
||||
Dizzy out Pin: This implementation makes a pulse every time one of the coils is charged, using coil dwell for pulse width. See also tachOutputPin
|
||||
|
||||
Saab CDM knock: Saab Combustion Detection Module knock signal input pin\nalso known as Saab Ion Sensing Module
|
||||
Saab CDM knock: Saab Combustion Detection Module knock signal input pin
|
||||
also known as Saab Ion Sensing Module
|
||||
|
||||
## All Pins 2/3
|
||||
### All Pins 2/3
|
||||
|
||||
## All Pins 3/3
|
||||
|
||||
### All Pins 3/3
|
||||
|
||||
Cam Sync/VVT input: Camshaft input could be used either just for engine phase detection if your trigger shape does not include cam sensor as 'primary' channel, or it could be used for Variable Valve timing on one of the camshafts.\nTODO #660
|
||||
|
||||
Cam Sync/VVT input: Camshaft input could be used either just for engine phase detection if your trigger shape does not include cam sensor as 'primary' channel, or it could be used for Variable Valve timing on one of the camshafts.
|
||||
TODO #660
|
||||
|
||||
vBatt ADC input: This is the processor input pin that the battery voltage circuit is connected to, if you are unsure of what pin to use, check the schematic that corresponds to your PCB.
|
||||
|
||||
FuelLevelSensor: This is the processor pin that your fuel level sensor in connected to. This is a non standard input so will need to be user defined.
|
||||
|
||||
## Experimental/Broken
|
||||
### Experimental/Broken
|
||||
|
||||
## Multispark
|
||||
|
||||
### Multispark
|
||||
|
||||
## GDI Dreams
|
||||
|
||||
### GDI Dreams
|
||||
|
||||
## HIP9011 Settings (knock decoder)
|
||||
|
||||
### HIP9011 Settings (knock decoder)
|
||||
|
||||
## Electronic Throttle Body (beta)
|
||||
|
||||
### Electronic Throttle Body (beta)
|
||||
|
||||
|
||||
Detailed status in console: Print details into rusEfi console
|
||||
|
||||
Disable ETB Motor: Disable the electronic throttle motor for testing.\nThis mode is for testing ETB position sensors, etc without actually driving the throttle.
|
||||
Disable ETB Motor: Disable the electronic throttle motor for testing.
|
||||
This mode is for testing ETB position sensors, etc without actually driving the throttle.
|
||||
|
||||
Two-wire mode: TLE7209 uses two-wire mode. TLE9201 and VNH2SP30 do NOT use two wire mode.
|
||||
|
||||
|
|
@ -109,22 +131,31 @@ Two-wire mode: TLE7209 uses two-wire mode. TLE9201 and VNH2SP30 do NOT use two w
|
|||
|
||||
use ETB for idle: This setting allows the ETB to act as the idle air control valve and move to regulate the airflow at idle.
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode\n\nset debug_mode X
|
||||
Debug mode: See http://rusefi.com/s/debugmode
|
||||
|
||||
set debug_mode X
|
||||
|
||||
use ETB for idle: This setting allows the ETB to act as the idle air control valve and move to regulate the airflow at idle.
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode\n\nset debug_mode X
|
||||
Debug mode: See http://rusefi.com/s/debugmode
|
||||
|
||||
set debug_mode X
|
||||
|
||||
use ETB for idle: This setting allows the ETB to act as the idle air control valve and move to regulate the airflow at idle.
|
||||
|
||||
Debug mode: See http://rusefi.com/s/debugmode\n\nset debug_mode X
|
||||
Debug mode: See http://rusefi.com/s/debugmode
|
||||
|
||||
## Electronic TB Bias Curve
|
||||
set debug_mode X
|
||||
|
||||
### Electronic TB Bias Curve
|
||||
|
||||
## ETB Pedal to TPS
|
||||
|
||||
### ETB Pedal to TPS
|
||||
|
||||
## Launch Control Settings NOT WORKING
|
||||
|
||||
### Launch Control Settings NOT WORKING
|
||||
|
||||
|
||||
Extra Fuel(%): Extra Fuel Added
|
||||
|
||||
Boost Solenoid Duty(%): Duty Cycle for the Boost Solenoid
|
||||
|
|
@ -133,9 +164,11 @@ Smooth Retard Mode: Interpolates the Ignition Retard from 0 to 100% within the R
|
|||
|
||||
Ignition Cut: This is the Cut Mode normally used
|
||||
|
||||
## Rolling Launch Settings NOT WORKING
|
||||
### Rolling Launch Settings NOT WORKING
|
||||
|
||||
## AntiLag Settings NOT WORKING
|
||||
|
||||
### AntiLag Settings NOT WORKING
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Cranking
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Cranking
|
||||
[Cranking Settings](#Cranking-Settings)
|
||||
|
||||
[Cranking Coolant Temperature Multiplier](#Cranking-Coolant-Temperature-Multiplier)
|
||||
|
|
@ -7,11 +8,13 @@
|
|||
|
||||
[Cranking TPS Multiplier](#Cranking-TPS-Multiplier)
|
||||
|
||||
## Cranking Settings
|
||||
### Cranking Settings
|
||||
|
||||
|
||||
Enable cylinder cleanup: When enabled if TPS is held above 95% no fuel is injected while cranking to clear excess fuel from the cylinders.
|
||||
|
||||
Enable faster engine spin-up: Smarter cranking logic.\nSee also startOfCrankingPrimingPulse
|
||||
Enable faster engine spin-up: Smarter cranking logic.
|
||||
See also startOfCrankingPrimingPulse
|
||||
|
||||
Use separate Advance Table for cranking: This activates a separate advance table for cranking conditions, this allows cranking advance to be RPM dependant.
|
||||
|
||||
|
|
@ -31,11 +34,14 @@ Use Advance Corrections for cranking: This enables the various ignition correcti
|
|||
|
||||
Use fixed cranking dwell: If set to true, will use the specified duration for cranking dwell. If set to false, will use the specified dwell angle. Unless you have a really good reason to, leave this set to true to use duration mode.
|
||||
|
||||
## Cranking Coolant Temperature Multiplier
|
||||
### Cranking Coolant Temperature Multiplier
|
||||
|
||||
## Cranking Duration Multiplier
|
||||
|
||||
### Cranking Duration Multiplier
|
||||
|
||||
## Cranking TPS Multiplier
|
||||
|
||||
### Cranking TPS Multiplier
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Fuel
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Fuel
|
||||
[Injection settings](#Injection-settings)
|
||||
|
||||
[Injector dead time](#Injector-dead-time)
|
||||
|
|
@ -23,39 +24,54 @@
|
|||
|
||||
[Engine Load Acceleration Enrichment Taper](#Engine-Load-Acceleration-Enrichment-Taper)
|
||||
|
||||
## Injection settings
|
||||
### Injection settings
|
||||
|
||||
Two wire batch emulation: This is needed if your coils are individually wired and you wish to use batch injection.\nenable two_wire_batch_injection
|
||||
|
||||
Two wire batch emulation: This is needed if your coils are individually wired and you wish to use batch injection.\nenable two_wire_batch_injection
|
||||
Two wire batch emulation: This is needed if your coils are individually wired and you wish to use batch injection.
|
||||
enable two_wire_batch_injection
|
||||
|
||||
Two wire batch emulation: This is needed if your coils are individually wired and you wish to use batch injection.\nenable two_wire_batch_injection
|
||||
Two wire batch emulation: This is needed if your coils are individually wired and you wish to use batch injection.
|
||||
enable two_wire_batch_injection
|
||||
|
||||
## Injector dead time
|
||||
Two wire batch emulation: This is needed if your coils are individually wired and you wish to use batch injection.
|
||||
enable two_wire_batch_injection
|
||||
|
||||
### Injector dead time
|
||||
|
||||
## Fuel short-term closed-loop correction
|
||||
|
||||
### Fuel short-term closed-loop correction
|
||||
|
||||
## Coasting Fuel Cutoff Settings
|
||||
|
||||
### Coasting Fuel Cutoff Settings
|
||||
|
||||
|
||||
Enable Coasting Fuel Cutoff: This setting disables fuel injection while the engine is in overrun, this is useful as a fuel saving measure and to prevent back firing.
|
||||
|
||||
TPS Deactivation Threshold(%): percent between 0 and 100 below which the fuel cut is deactivated, this helps low speed drivability.
|
||||
|
||||
## Fuel Table
|
||||
### Fuel Table
|
||||
|
||||
## Injection Phase
|
||||
|
||||
### Injection Phase
|
||||
|
||||
## Warmup fuel manual Multiplier
|
||||
|
||||
### Warmup fuel manual Multiplier
|
||||
|
||||
## Intake air temperature fuel Multiplier
|
||||
|
||||
### Intake air temperature fuel Multiplier
|
||||
|
||||
## tCharge Settings
|
||||
|
||||
### tCharge Settings
|
||||
|
||||
## Accel/Decel Enrichment
|
||||
|
||||
### Accel/Decel Enrichment
|
||||
|
||||
## TPS/TPS Acceleration Extra Fuel(ms)
|
||||
|
||||
### TPS/TPS Acceleration Extra Fuel(ms)
|
||||
|
||||
## Engine Load Acceleration Enrichment Taper
|
||||
|
||||
### Engine Load Acceleration Enrichment Taper
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Idle
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Idle
|
||||
[Idle settings](#Idle-settings)
|
||||
|
||||
[Idle hardware](#Idle-hardware)
|
||||
|
|
@ -9,8 +10,9 @@
|
|||
|
||||
[Warmup Idle multiplier](#Warmup-Idle-multiplier)
|
||||
|
||||
## Idle settings
|
||||
### Idle settings
|
||||
|
||||
|
||||
use ETB for idle: This setting allows the ETB to act as the idle air control valve and move to regulate the airflow at idle.
|
||||
|
||||
Use separate Ignition Table for idle: This activates a separate ignition timing table for idle conditions, this can help idle stability by using ignition retard and advance either side of the desired idle speed. Extra retard at low idle speeds will prevent stalling and extra advance at high idle speeds can help reduce engine power and slow the idle speed.
|
||||
|
|
@ -33,8 +35,9 @@ PID Extra for low RPM(%): Increases PID reaction for RPM<target by adding extra
|
|||
|
||||
Use IAC PID Multiplier Table: This flag allows to use a special 'PID Multiplier' table (0.0-1.0) to compensate for nonlinear nature of IAC-RPM controller
|
||||
|
||||
## Idle hardware
|
||||
### Idle hardware
|
||||
|
||||
|
||||
Use Stepper: This setting should only be used if you have a stepper motor idle valve and a stepper motor driver installed.
|
||||
|
||||
Two-wire mode: TLE7209 uses two-wire mode. TLE9201 and VNH2SP30 do NOT use two wire mode.
|
||||
|
|
@ -47,11 +50,14 @@ Two-wire mode: TLE7209 uses two-wire mode. TLE9201 and VNH2SP30 do NOT use two w
|
|||
|
||||
Two-wire mode: TLE7209 uses two-wire mode. TLE9201 and VNH2SP30 do NOT use two wire mode.
|
||||
|
||||
## Idle Target RPM
|
||||
### Idle Target RPM
|
||||
|
||||
## Closed-loop idle timing
|
||||
|
||||
### Closed-loop idle timing
|
||||
|
||||
## Warmup Idle multiplier
|
||||
|
||||
### Warmup Idle multiplier
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Ignition
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Ignition
|
||||
[Ignition settings](#Ignition-settings)
|
||||
|
||||
[Dwell](#Dwell)
|
||||
|
|
@ -11,8 +12,9 @@
|
|||
|
||||
[Ignition Intake Air Temp correction](#Ignition-Intake-Air-Temp-correction)
|
||||
|
||||
## Ignition settings
|
||||
### Ignition settings
|
||||
|
||||
|
||||
Two wire wasted: This is needed if your coils are individually wired (COP) and you wish to use batch ignition (wasted spark).
|
||||
|
||||
Timing Mode: Dynamic uses the timing map to decide the ignition timing, Static timing fixes the timing to the value set below (only use for checking static timing).
|
||||
|
|
@ -21,15 +23,20 @@ Use TPS-based Advance Table: This flag allows to use TPS for ignition lookup whi
|
|||
|
||||
Dizzy out Pin: This implementation makes a pulse every time one of the coils is charged, using coil dwell for pulse width. See also tachOutputPin
|
||||
|
||||
## Dwell
|
||||
### Dwell
|
||||
|
||||
## Ignition Cylinder Extra Timing
|
||||
|
||||
### Ignition Cylinder Extra Timing
|
||||
|
||||
## Ignition Table
|
||||
|
||||
### Ignition Table
|
||||
|
||||
## Warmup timing correction
|
||||
|
||||
### Warmup timing correction
|
||||
|
||||
## Ignition Intake Air Temp correction
|
||||
|
||||
### Ignition Intake Air Temp correction
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Sensors
|
||||
# [rusEFI-project](rusEFI project)
|
||||
## Sensors
|
||||
[Trigger Inputs](#Trigger-Inputs)
|
||||
|
||||
[Other Sensor Inputs](#Other-Sensor-Inputs)
|
||||
|
|
@ -39,69 +40,91 @@
|
|||
|
||||
[EGT inputs](#EGT-inputs)
|
||||
|
||||
## Trigger Inputs
|
||||
### Trigger Inputs
|
||||
|
||||
|
||||
Invert Primary: This setting flips the signal from the primary engine speed sensor.
|
||||
|
||||
Invert Secondary: This setting flips the signal from the secondary engine speed sensor.
|
||||
|
||||
Cam Sync/VVT input: Camshaft input could be used either just for engine phase detection if your trigger shape does not include cam sensor as 'primary' channel, or it could be used for Variable Valve timing on one of the camshafts.\nTODO #660
|
||||
Cam Sync/VVT input: Camshaft input could be used either just for engine phase detection if your trigger shape does not include cam sensor as 'primary' channel, or it could be used for Variable Valve timing on one of the camshafts.
|
||||
TODO #660
|
||||
|
||||
## Other Sensor Inputs
|
||||
### Other Sensor Inputs
|
||||
|
||||
|
||||
Throttle Up switch: Throttle Pedal not pressed switch - used on some older vehicles like early Mazda Miata
|
||||
|
||||
## Analog Input Settings
|
||||
### Analog Input Settings
|
||||
|
||||
## CLT sensor
|
||||
|
||||
### CLT sensor
|
||||
|
||||
## IAT sensor
|
||||
|
||||
### IAT sensor
|
||||
|
||||
## aux1 Thermistor Settings
|
||||
|
||||
### aux1 Thermistor Settings
|
||||
|
||||
## aux2 Thermistor Settings
|
||||
|
||||
### aux2 Thermistor Settings
|
||||
|
||||
## TPS
|
||||
|
||||
### TPS
|
||||
|
||||
|
||||
TPS low value detection threshold(%): TPS error detection, what TPS % value is unrealistically low
|
||||
|
||||
TPS high value detection threshold(%): TPS error detection, what TPS % value is unrealistically high
|
||||
|
||||
## Accelerator pedal
|
||||
### Accelerator pedal
|
||||
|
||||
|
||||
Down (WOT) voltage: Pedal in the floor
|
||||
|
||||
## MAP sensor
|
||||
### MAP sensor
|
||||
|
||||
|
||||
Measure Map Only In One Cylinder: Useful for individual intakes
|
||||
|
||||
Measure Map Only In One Cylinder: Useful for individual intakes
|
||||
|
||||
Measure Map Only In One Cylinder: Useful for individual intakes
|
||||
|
||||
## MAP sampling
|
||||
### MAP sampling
|
||||
|
||||
## Baro sensor
|
||||
|
||||
### Baro sensor
|
||||
|
||||
## MAF sensor
|
||||
|
||||
### MAF sensor
|
||||
|
||||
## MAF sensor
|
||||
|
||||
### MAF sensor
|
||||
|
||||
## EGO sensor
|
||||
|
||||
### EGO sensor
|
||||
|
||||
## Narrow to Wideband approximation
|
||||
|
||||
### Narrow to Wideband approximation
|
||||
|
||||
## CJ125 Settings (wbo decoder)
|
||||
|
||||
### CJ125 Settings (wbo decoder)
|
||||
|
||||
|
||||
Is UA input divided?: Is your UA CJ125 output wired to MCU via resistor divider?
|
||||
|
||||
Is UR input divided?: Is your UR CJ125 output wired to MCU via resistor divider?\nLooks like 3v range should be enough, divider generally not needed.
|
||||
Is UR input divided?: Is your UR CJ125 output wired to MCU via resistor divider?
|
||||
Looks like 3v range should be enough, divider generally not needed.
|
||||
|
||||
## Speed sensor
|
||||
### Speed sensor
|
||||
|
||||
## Oil pressure
|
||||
|
||||
### Oil pressure
|
||||
|
||||
## EGT inputs
|
||||
|
||||
### EGT inputs
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
|
|
@ -225,4 +225,4 @@
|
|||
|
||||
|
||||
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:51:28 EDT 2020
|
||||
generated by class com.rusefi.MdGenerator on Fri May 01 14:55:08 EDT 2020
|
||||
|
|
|
|||
Loading…
Reference in New Issue