Lint (#360)
* auto fixes * started fixing * more fixing * lint with gha * and more fixing * and even more fixing * and even more fixing yet * fix home * am idiot * fix workflow name
This commit is contained in:
David Holdeman
GitHub
parent
6e72ca6b6b
commit
e560445e51
|
|
@ -0,0 +1,20 @@
|
|||
name: Lint
|
||||
|
||||
on:
|
||||
pull_request
|
||||
|
||||
jobs:
|
||||
lint:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Check out repo
|
||||
uses: actions/checkout@v2
|
||||
|
||||
- name: Install Markdownlint-cli
|
||||
run: |
|
||||
npm install -g markdownlint-cli
|
||||
|
||||
- name: Lint
|
||||
run: |
|
||||
markdownlint -i _* --disable MD033 MD034 MD013 MD024 MD036 -- .
|
||||
|
|
@ -1,3 +1,4 @@
|
|||
# 1995 Mitsubishi 3000GT
|
||||
|
||||
|
||||
|
||||
|
|
@ -5,14 +6,14 @@
|
|||
|
||||
|
||||
|
||||
# Charging
|
||||
## Charging
|
||||
|
||||
|
||||
|
||||
# Starting w/o Theft
|
||||
## Starting w/o Theft
|
||||
|
||||
|
||||
|
||||
# Starting with Theft
|
||||
## Starting with Theft
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 1997 Mercedes-Benz E320
|
||||
|
||||
M104 wasted spark
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
# 1999 Mercedes-Benz E320
|
||||
|
||||
|
||||
|
||||
[Mercedes-Benz M112 Engine - Wikipedia]](<https://en.wikipedia.org/wiki/Mercedes-Benz_M112_engine>)
|
||||
|
||||
# 99 E320
|
||||
## 99 E320
|
||||
|
||||
| Connector/ Pin Number | OEM Color | Name / Function |
|
||||
| --------------------- |------- |---------------- |
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
# 1999 Mercedes-Benz E430
|
||||
|
||||
|
||||
|
||||
[Mercedes-Benz M113 Engine - Wikipedia]](<https://en.wikipedia.org/wiki/Mercedes-Benz_M113_engine>)
|
||||
|
||||
# 99 E430
|
||||
## 99 E430
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
# 2000 Mercedes-Benz S430
|
||||
|
||||
|
||||
|
||||
[Mercedes-Benz M113 Engine - Wikipedia]](<https://en.wikipedia.org/wiki/Mercedes-Benz_M113_engine>)
|
||||
|
||||
# 2000 S430
|
||||
## 2000 S430
|
||||
|
||||
| Connector/ Pin Number | OEM Color | Name / Function |
|
||||
| --------------------- |------- |---------------- |
|
||||
|
|
@ -21,7 +23,7 @@
|
|||
|
||||
|
||||
|
||||
# 2000 S500
|
||||
## 2000 S500
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 2002 Audi Allroad
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 2002 VW Passat
|
||||
|
||||
| Pin Number | Color | Type | Function |
|
||||
| ----------:|:-------- | ------- |:---------------------------------------------------- |
|
||||
| 1 | ? | gnd | GND |
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# 2004 Porsche Cayenne
|
||||
|
||||
[page-1](OEM-Docs/VAG/2004-cayenne-3.2-1.pdf)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 2010 Audi TT
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
# Mitsubishi 3000GT
|
||||
|
||||
[Engine Control Module (ECM) Terminal Voltage Inspection Mitsubishi 3000GT & Dodge Stealth](http://www.stealth316.com/2-ecu-terminals.htm)
|
||||
|
||||
[Pinout Spreadsheet](https://docs.google.com/spreadsheets/d/1ZlcC5cdCwjYoV-z49MNaa9zpLiu_ZYBIx5H-j0F6QpI)
|
||||
|
||||
# 1994
|
||||
## 1994
|
||||
|
||||
DOHC Non-turbo California: 1994 to 1997
|
||||
|
||||
|
|
@ -34,7 +36,7 @@ DOHC Turbo: 1994 to 1997
|
|||
|
||||
|
||||
|
||||
# 1996-1997
|
||||
## 1996-1997
|
||||
|
||||
### 96-1
|
||||
|
||||
|
|
|
|||
7
ASIC.md
7
ASIC.md
|
|
@ -1,7 +1,8 @@
|
|||
# ASIC
|
||||
|
||||
Overview of state of integration between rusEFI and all kinds of ASICs.
|
||||
|
||||
# Low side+
|
||||
## Low side+
|
||||
|
||||
### Mostly implemented
|
||||
|
||||
|
|
@ -20,14 +21,14 @@ Overview of state of integration between rusEFI and all kinds of ASICs.
|
|||
| PT2000 | Low impedance (fast) solenoid control: GDI | We only have dev board, no code |
|
||||
| | | |
|
||||
|
||||
# Sensors
|
||||
## Sensors
|
||||
|
||||
| Part | Function | Notes |
|
||||
|------|----------|--------------|
|
||||
| LPS25HB | Barometric pressure sensor | Installed on Proteus v0.5+ |
|
||||
| | | |
|
||||
|
||||
# Misc
|
||||
## Misc
|
||||
|
||||
### Implemented but known limitations
|
||||
|
||||
|
|
|
|||
|
|
@ -11,17 +11,17 @@ rusEFI has implemented several strategies that attempt to compensate for this ph
|
|||
It is important to note that the Acceleration Compensation is not intended to increase the amount of fuel in order to increase power during acceleration - that is the purpose of the AFR table or VE table, whereas this compensation is purely intended to correct for the fuel dropping out of suspension.
|
||||
N.B. This is also why I refer to it as "Acceleration Compensation" rather than "Acceleration Enrichment", as the second term implies the wrong purpose.
|
||||
|
||||
# TPS based
|
||||
## TPS based
|
||||
|
||||
The simplest method, this uses the change in TPS position over time to decide on an additional quantity of fuel to inject.
|
||||
It is most similar to a carburetors accelerator pump in operation.
|
||||
|
||||
# Wall Wetting
|
||||
## Wall Wetting
|
||||
|
||||
This is a more sophisticated method that was developed in the 1980s by the Ford Motor Company. It uses a simple model to estimate the amount of fuel that is dropping out of suspension and the time it takes to re-evaporate.
|
||||
This is a more accurate method but requires a little more knowledge to tune.
|
||||
|
||||
# Engine Load based
|
||||
## Engine Load based
|
||||
|
||||
[//]: # "To do by someone with more understanding of this implementation"
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,3 @@
|
|||
# Accelerometer
|
||||
|
||||
[STM32 F4 SPI Accelerometer](http://00xnor.blogspot.com/2014/03/stm32-f4-spi-accelerometer.html)
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
# Acura RSX
|
||||
|
||||
# 2003
|
||||
## 2003
|
||||
|
||||
[2003-acura-rsx-type-R.pdf](https://github.com/rusefi/rusefi_documentation/raw/master/OEM-Docs/Honda/2003-acura-rsx-type-R.pdf)
|
||||
|
||||
# 2005
|
||||
## 2005
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Acura TSX
|
||||
|
||||
# 2005
|
||||
## 2005
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Adaptive Suspension
|
||||
|
||||
[Shock Dyno](Shock-Dyno.md)
|
||||
|
||||
[ArsTechnica: DSC Sport’s active shocks in action](https://arstechnica.com/cars/2015/07/the-future-of-car-suspension-is-here-dsc-sports-active-shocks-in-action/)
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ Honda K Exhaust Camshaft
|
|||
|
||||
### Mazda Miata NA
|
||||
|
||||
Also used on some Mitsubishi like 4g18 4g93
|
||||
Also used on some Mitsubishi like 4g18 4g93
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,13 +10,13 @@ An example of this would be ITBs.
|
|||
It is not suggested that this method is used with rusEFI as we have implemented very good windowing and smoothing of MAP sensor signals, which allows for the speed density method to be used reliably on systems where it would not traditionally function well.
|
||||
However we are aware that there are many users that would still prefer to use this method so it has been provided.
|
||||
|
||||
# The detail
|
||||
## The detail
|
||||
|
||||
fuel_squirt_duration = injector_lag_curve_lookup(V_BATT) + warm_up_curve_lookup(COOLANT_TEMPERATURE) *intake_air_correction_curve_lookup(INTAKE_AIR_TEMP)* fuel_table_lookup(RPM, TPS)
|
||||
|
||||
Where TPS is the reading at the start of engine cycle
|
||||
|
||||
# How to tune
|
||||
## How to tune
|
||||
|
||||
The AlphaN system in rusEFI can be tuned in the same way as all other standalone ECUs, it is simply a case of inputting the required fuel values in the main fuel table.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# AlphaX 2Chan
|
||||
|
||||
[AlphaX](https://www.alphaxpr.com/)
|
||||
|
||||
[Download release firmware](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_alphax-2chan.zip)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# AlphaX 4Chan
|
||||
|
||||
[AlphaX](https://www.alphaxpr.com/)
|
||||
|
||||
[Download release firmware](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_alphax-4chan.zip)
|
||||
|
|
@ -28,7 +30,8 @@
|
|||
|
||||
## Changelog
|
||||
|
||||
rev E:
|
||||
rev E:
|
||||
|
||||
* SD card fixed
|
||||
* [CRANKs/CAMs input hookup points](https://github.com/rusefi/alphax-4chan/issues/61)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# AlphaX 8Chan
|
||||
|
||||
[Interactive Pinout](https://rusefi.com/docs/pinouts/hellen/alphax-8chan/)
|
||||
|
||||
[Issue tracker & hardware files](https://github.com/rusefi/alphax-8chan)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Artem Miata Readme
|
||||
|
||||
Based on
|
||||
|
||||
nb2-happy-warmup-idle.csv
|
||||
|
|
|
|||
|
|
@ -1 +1,3 @@
|
|||
# Atlas Manual
|
||||
|
||||
Hello [https://github.com/mck1117/atlas](https://github.com/mck1117/atlas)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Audi 2006 A4 B7 Quattro 2.0 TFSI
|
||||
# Audi 2006 A4 B7 Quattro 2.0 TFSI
|
||||
|
||||
[154 pin Connector](OEM-connectors#154-pin)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
```
|
||||
# B6 Temp
|
||||
|
||||
```lua
|
||||
|
||||
-- 640
|
||||
MOTOR_1 = 0x280
|
||||
|
|
|
|||
11
BMW-N73.md
11
BMW-N73.md
|
|
@ -1,8 +1,7 @@
|
|||
# BMW N73
|
||||
|
||||
[rusEFI 2004 BMW 760 forum thread](https://rusefi.com/forum/viewtopic.php?f=2&t=1845)
|
||||
|
||||
# N73
|
||||
|
||||
BMW 760 12 cylinders
|
||||
See [BMW-e65](BMW-e65)
|
||||
|
||||
|
|
@ -26,7 +25,7 @@ x2 HDEV fuel injection module 7506280 [121 pin connector](OEM-connectors#121)
|
|||
|
||||
|
||||
|
||||
# HDEV
|
||||
## HDEV
|
||||
|
||||
Injector #1 + #118
|
||||
|
||||
|
|
@ -57,11 +56,11 @@ CAS 61326922329
|
|||
Programming keywords:
|
||||
ISTA ICON
|
||||
|
||||
# Starting
|
||||
## Starting
|
||||
|
||||
|
||||
|
||||
# Data Lines
|
||||
## Data Lines
|
||||
|
||||
|
||||
|
||||
|
|
@ -69,7 +68,7 @@ ISTA ICON
|
|||
|
||||
|
||||
|
||||
# Anti Theft
|
||||
## Anti Theft
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# 1996 BMW E38 750
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# BMW e38 750
|
||||
|
||||
[M73 engine](https://en.wikipedia.org/wiki/BMW_M73)
|
||||
|
||||
[HOWTO-M73-v12-on-Proteus](HOWTO-M73-v12-on-Proteus)
|
||||
|
|
@ -26,13 +28,13 @@ ECU#4
|
|||
ECU#5
|
||||
|
||||
|
||||
# EML
|
||||
## EML
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
# TCU
|
||||
## TCU
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# BMW e38 Part Numbers
|
||||
|
||||
* 61.35-8 382 455 "Anti Theft Control Module"
|
||||
* 34.52-1 164 245 "Acceleration Turn Speed Sensor" 34521164245
|
||||
* 61.35-8 378 631 "General Body Control"
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
# BMW 7 Series (E38)
|
||||
|
||||
[BMW 7 Series (E38) - Wikipedia]](<https://en.wikipedia.org/wiki/BMW_7_Series_(E38>))
|
||||
|
||||
# 2000 740
|
||||
## 2000 740
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
# BMW 5 Series (E39)
|
||||
|
||||
[BMW 5 Series (E39) - Wikipedia]](<https://en.wikipedia.org/wiki/BMW_5_Series_(E39>))
|
||||
|
||||
# 1999 528
|
||||
## 1999 528
|
||||
|
||||
|
||||
|
||||
|
|
@ -26,7 +27,7 @@
|
|||
| | | |
|
||||
| | | |
|
||||
|
||||
# 2001 540
|
||||
## 2001 540
|
||||
|
||||
[BMW M62 - Wikipedia]](<https://en.wikipedia.org/wiki/BMW_M62>)
|
||||
|
||||
|
|
|
|||
14
BMW-e46.md
14
BMW-e46.md
|
|
@ -1,6 +1,6 @@
|
|||
# BMW e46
|
||||
|
||||
# 325
|
||||
## 325
|
||||
|
||||
|
||||
|
||||
|
|
@ -10,9 +10,9 @@
|
|||
|
||||
|
||||
|
||||
# M3
|
||||
## M3
|
||||
|
||||
## 2002 M3
|
||||
### 2002 M3
|
||||
|
||||
|
||||
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
|
||||
|
||||
|
||||
## 2004 M3
|
||||
### 2004 M3
|
||||
|
||||
|
||||
|
||||
|
|
@ -30,7 +30,7 @@
|
|||
|
||||
|
||||
|
||||
## 2004 330
|
||||
### 2004 330
|
||||
|
||||
|
||||
|
||||
|
|
@ -45,11 +45,11 @@
|
|||
| 7 | RED | +12v Hot all times |
|
||||
| | | |
|
||||
|
||||
# Trunk
|
||||
## Trunk
|
||||
|
||||
|
||||
|
||||
# ECU Pcb
|
||||
## ECU Pcb
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# BMW e53
|
||||
|
||||
# 2001 x5 3.0
|
||||
## 2001 x5 3.0
|
||||
|
||||
|
||||
|
||||
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
|
||||
|
||||
# 2001 x5 4.4
|
||||
## 2001 x5 4.4
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,8 @@
|
|||
# BMW E65
|
||||
|
||||
Production 2001 – 2008
|
||||
|
||||
# 750 8 cylinders
|
||||
## 750 8 cylinders
|
||||
|
||||
|
||||
|
||||
|
|
@ -30,11 +31,11 @@ Production 2001 – 2008
|
|||
| | | |
|
||||
| | | |
|
||||
|
||||
# 760 12 cylinders
|
||||
## 760 12 cylinders
|
||||
|
||||
See [BMW-N73](BMW-N73)
|
||||
|
||||
##### HOWTO videos
|
||||
## HOWTO videos
|
||||
|
||||
[Console removal](https://www.youtube.com/watch?v=pGAeodWa_i4)
|
||||
|
||||
|
|
@ -51,7 +52,7 @@ SRS module controls fuel pump
|
|||
|
||||
[User Manual](OEM-Docs/Bmw/2003_7_Series_e65/2004_Manual_7_Series.pdf)
|
||||
|
||||
# Transmission
|
||||
## Transmission
|
||||
|
||||
[6 Speed Transmission mechatronic sleeve replacement](OEM-Docs/Bmw/2003_7_Series_e65/6_speed_sleeve_replacement.pdf)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
"Does this come with a base map?"
|
||||
# Does this come with a base map?
|
||||
|
||||
We are of the opinion that basemaps are only useful to help you load your project on a trailer in order to get to your tuning shop. In this regard more or less any map would get your project vehicle on the trailer :)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
== HC-06 Bluetooth Module serial RS232 TTL ==
|
||||
# HC-06 Bluetooth Module serial RS232 TTL
|
||||
|
||||
On start, HC-06 accepts AT commands @ 9600.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Breakout Board Enclosures
|
||||
|
||||
At the moment all rusEFI breakout board enclosures are still orange. Black is planned for one day soon.
|
||||
|
||||
We use Fused deposition modeling with ABS 4% glass fiber plastic.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Build Server and Automation
|
||||
|
||||
Github Actions is currently in charge of:
|
||||
|
||||
* Firmware Builds: continuous integration publishing at [https://rusefi.com/build_server/](https://rusefi.com/build_server/)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
## HOWTO use custom build of rusEFI for CAN bus sniffing
|
||||
# HOWTO use custom build of rusEFI for CAN bus sniffing
|
||||
|
||||
In this HOWTO I will explain how to see raw CAN message flow with less than $30 in hardware & some free software.
|
||||
|
||||
|
|
@ -6,15 +6,15 @@ In this HOWTO I will explain how to see raw CAN message flow with less than $30
|
|||
|
||||
1. Get an [STM32F4DISCOVERY](http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419) micro-controller board - there are 'Order Now' buttons at the bottom of the official page.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Get an [SN65HVD230 CAN Board](http://www.wvshare.com/product/SN65HVD230-CAN-Board.htm)
|
||||
|
||||
|
||||
|
||||
|
||||
3. Get a "OBD2 16-Pin Male to Female Diagnostic Extension Cable" on eBay
|
||||
|
||||
|
||||
|
||||
|
||||
4. Get a microUSB cable (one which comes with any Android phone)
|
||||
|
||||
|
|
@ -44,30 +44,30 @@ Hardware is ready!
|
|||
|
||||
2. Firmware: download and unzip [rusefi_can_sniffer.zip](http://rusefi.com/images/forum_posts/CAN/rusefi_can_sniffer.zip)
|
||||
|
||||
2. Uploading the firmware: Connect stm32f4discovery to your laptop using a mini-USB cable (one should come with the board), install driver, start St-Link Utility.
|
||||
3. Uploading the firmware: Connect stm32f4discovery to your laptop using a mini-USB cable (one should come with the board), install driver, start St-Link Utility.
|
||||
|
||||
|
||||
|
||||
|
||||
click 'Target'>'Program...'
|
||||
click 'Target'>'Program...'
|
||||
|
||||
|
||||
|
||||
|
||||
Point the utility to the rusefi_can_sniffer.hex file and hit 'Start'
|
||||
Point the utility to the rusefi_can_sniffer.hex file and hit 'Start'
|
||||
|
||||
Close ST Link Utility.
|
||||
Close ST Link Utility.
|
||||
|
||||
3. Now it's time to connect the micro USB cable. Keep miniUSB cable connected - you should have two USB cables connected. When you do this for the first time your Windows would prompt for drivers, you should download & install [virtual COM driver](http://www.st.com/web/en/catalog/tools/PF257938)
|
||||
4. Now it's time to connect the micro USB cable. Keep miniUSB cable connected - you should have two USB cables connected. When you do this for the first time your Windows would prompt for drivers, you should download & install [virtual COM driver](http://www.st.com/web/en/catalog/tools/PF257938)
|
||||
|
||||
Once the driver is installed, you can verify serial connectivity by opening your Device Manager - we are expecting to see a Virtual COM Port.
|
||||
|
||||
Once the driver is installed, you can verify serial connectivity by opening your Device Manager - we are expecting to see a Virtual COM Port.
|
||||
|
||||
|
||||
Remember the number of the COM port.
|
||||
Remember the number of the COM port.
|
||||
|
||||
4. Download and launch [Putty](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) telnet application.
|
||||
5. Download and launch [Putty](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) telnet application.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Now connect the obd connector to your vehicle and you should see the CAN messages flowing in putty.
|
||||
|
||||
Now connect the obd connector to your vehicle and you should see the CAN messages flowing in putty.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,54 +1,55 @@
|
|||
# CAN Decoding Hints
|
||||
|
||||
Text format CAN traces preferred. Please name files according to scenarios.
|
||||
|
||||
# Ignition on
|
||||
## Ignition on
|
||||
|
||||
Start trace recording, turn ignition key/wake up car, turn key off, record until CAN traffic stops or 30 seconds whatever happens first. Stop trace recording.
|
||||
|
||||
# Brake Pedal
|
||||
## Brake Pedal
|
||||
|
||||
Ignition key ON, engine OFF. Tap and hold breaks five times.
|
||||
|
||||
# TPS/PPS sweep
|
||||
## TPS/PPS sweep
|
||||
|
||||
Ignition key ON, engine OFF. Press pedal all the way down fast, complexly release fast, press all way down slowly, complexly release slowly, repeat from start two more times.
|
||||
|
||||
# PPS sweep with TPS disengages
|
||||
## PPS sweep with TPS disengages
|
||||
|
||||
Open hood, unhook TPS sensor plug. Repeat "TPS/PPS sweep"
|
||||
|
||||
# 30 seconds of idle
|
||||
## 30 seconds of idle
|
||||
|
||||
Record 30 seconds of car idling
|
||||
|
||||
# Idle with CLT removed
|
||||
## Idle with CLT removed
|
||||
|
||||
Idle, Unplug and plug coolant sensor
|
||||
|
||||
# Wheels in the air
|
||||
## Wheels in the air
|
||||
|
||||
Raise car, turn wheels manually while ignition ON or idle.
|
||||
|
||||
# PR Special
|
||||
## PR Special
|
||||
|
||||
Idle, Turn A/C on and off a few times
|
||||
|
||||
# Change gears while parked idling
|
||||
## Change gears while parked idling
|
||||
|
||||
Press brake pedal, engage R, engage D, engage R, engage D, engage R, engage D.
|
||||
|
||||
# Revving while parked
|
||||
## Revving while parked
|
||||
|
||||
Rev engine slowly to 3000 RPM, rev engine quickly, rev engine slowly to 3000 RPM, rev engine quickly.
|
||||
|
||||
# 20 mph in 1st gear
|
||||
## 20 mph in 1st gear
|
||||
|
||||
If you have "1" selector accelerate to 20 mph/32kmh and drive for hundred meters.
|
||||
|
||||
# 20 mph in 2st gear
|
||||
## 20 mph in 2st gear
|
||||
|
||||
If you have "2" selector accelerate to 20 mph/32kmh and drive for hundred meters.
|
||||
|
||||
# 20 mph in 3st gear
|
||||
## 20 mph in 3st gear
|
||||
|
||||
If you have "3" selector accelerate to 20 mph/32kmh and drive for hundred meters.
|
||||
|
||||
|
|
|
|||
6
CAN.md
6
CAN.md
|
|
@ -1,4 +1,4 @@
|
|||
Overview of CAN usage and IDs used by rusEFI
|
||||
# Overview of CAN usage and IDs used by rusEFI
|
||||
|
||||
* rusEFI WBO two way communication 0xEF50000 0x190
|
||||
* rusEFI WBO bootloader
|
||||
|
|
@ -8,11 +8,11 @@ Overview of CAN usage and IDs used by rusEFI
|
|||
* rusEFI CAN GPIO
|
||||
* rusEFI [TS over CAN](TS-over-CAN) 0x100 0x102
|
||||
|
||||
# Software
|
||||
## Software
|
||||
|
||||
[Man-in-the-middle](Man-in-the-middle)
|
||||
|
||||
# Hardware options
|
||||
## Hardware options
|
||||
|
||||
[fake looking like Vasya](https://rusefi.com/forum/viewtopic.php?f=13&t=2243)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# CL4490
|
||||
|
||||
[CL4490 Series](https://www.lairdtech.com/products/cl4490-series)
|
||||
|
||||
Support 800-492-2320 ext 3
|
||||
|
|
@ -10,8 +12,6 @@ CTS/RTS recommended by support, DCD being required is a surprise.
|
|||
|
||||
[CL4490 UART pins - Forum](http://rusefi.com/forum/viewtopic.php?f=4&t=1226&hilit=rs232#p25672)
|
||||
|
||||
======================
|
||||
Product: CL4490 automatically switch to AC4490 on "Read Radio"
|
||||
======================
|
||||
|
||||
Configuration/Test Utility can "open" port without radio attached
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 1998 Chevrolet Blazer S10 V6
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
# Chip Shortage: Parts Interchange
|
||||
|
||||
todo organize these notes better
|
||||
|
||||
# Proteus
|
||||
## Proteus
|
||||
|
||||
[Proteus Stock issues - Forum](https://rusefi.com/forum/viewtopic.php?p=41539#p41539)
|
||||
|
||||
|
|
@ -10,7 +12,7 @@ BM2LC105FJ-C BM2LC120FJ are replacement for VNLD5160
|
|||
|
||||
MCP6004T-I/ST: MCP6004T-E/ST
|
||||
|
||||
## Proteus MCU options
|
||||
### Proteus MCU options
|
||||
|
||||
Requirements:
|
||||
|
||||
|
|
@ -19,7 +21,7 @@ Requirements:
|
|||
- STM32F4: Known working is any F427/F429. 256KB RAM required. 1MB or 2MB acceptable.
|
||||
- STM32F7: Known working is F767. 1MB or 2MB acceptable.
|
||||
|
||||
# Hellen
|
||||
## Hellen
|
||||
|
||||
See also [Hellen JLC fabrication component substitution options](https://github.com/andreika-git/hellen-one/wiki/JLC-fabrication-component-substitution-options)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Code Style Guidelines
|
||||
|
||||
* Reduce visibility where possible
|
||||
|
||||
* Avoid magic constants
|
||||
|
|
@ -10,7 +12,7 @@ We make with -std=c++11 see [the Makefile](https://github.com/rusefi/rusefi/blob
|
|||
|
||||
Only the simplest, two-line if/for/while should not have the curly brackets. Anything more than two lines should have {}.
|
||||
|
||||
```
|
||||
```c
|
||||
if (plain_condition)
|
||||
oneLineStatement();
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Connector Mapping
|
||||
|
||||
rusEFI connector mapping is a framework which takes ECU connector photo and pinout metadata file in [YAML](https://en.wikipedia.org/wiki/YAML) format and produces [interactive pinouts](https://rusefi.com/docs/pinouts/), PDF and TunerStudio project .ini.
|
||||
|
||||
Input files are located in "connectors" folder of corresponding board configuration folder, for example: [firmware/config/boards/microrusefi/connectors](https://github.com/rusefi/rusefi/tree/master/firmware/config/boards/microrusefi/connectors)
|
||||
|
|
@ -27,6 +29,6 @@ The 'info' section contains information which is used to generate the interactiv
|
|||
|
||||
The generation of the interactive pinouts is invoked nightly or could be requested on demand.
|
||||
|
||||
# Best Practices
|
||||
## Best Practices
|
||||
|
||||
YAML is all about space indentation. [http://www.yamllint.com/](http://www.yamllint.com/) is a great online YAML validator.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ To get the console working follow the below procedure, which assumes you have lo
|
|||
* '''Linux'''
|
||||
* ''Ubuntu (11.10)'' - plug in the "console" USB cable, then check the message log with this command.
|
||||
|
||||
```
|
||||
```shell
|
||||
$ dmesg
|
||||
...
|
||||
[10572.620088] usb 5-1: new full speed USB device number 5 using uhci_hcd
|
||||
|
|
@ -59,11 +59,11 @@ Currently analog chart can display one of these two things
|
|||
|
||||
1. trigger signal shape. the value consists of the trigger signal index and fall/rise type of the event
|
||||
|
||||
`set_analog_chart_mode 1`
|
||||
`set_analog_chart_mode 1`
|
||||
|
||||
2. MAP sensor signal
|
||||
|
||||
`set_analog_chart_mode 2`
|
||||
`set_analog_chart_mode 2`
|
||||
|
||||
## Digital Chart
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Contributors: Please Work Smart
|
||||
|
||||
In our reality we have to really work smart not work hard.
|
||||
|
||||
Any repetitive user support request has to be addresses strategically
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# Cylinder Pressure Sensor Glow Plug
|
||||
|
||||
Using most globally availbale as used on tons of VAG Diesel engines PSG007 - 03L905061G, 03L905061F, 03L905061
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Debug Fields
|
||||
|
||||
Debug fields is an advanced troubleshooting feature allowing one to monitor internal state of some rusEFI subsystems. In an ideal world we would be always saving all these data points, in reality we need to only save those while troubleshooting something specific.
|
||||
|
||||
`set debug_mode CODE`
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Debug Mode
|
||||
|
||||
THIS CONCEPT IS ON THE WAY OUT
|
||||
|
||||
See <https://github.com/rusefi/rusefi/issues/3614>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
|
||||
# Deucalion UART
|
||||
|
||||
|
||||
|
||||
From right to left:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Dev Console Commands
|
||||
|
||||
## Tuner Studio
|
||||
|
||||
|Command|Number Of Parameters|Description|
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Dev Console Implementation
|
||||
|
||||
## human readable protocol
|
||||
|
||||
A typical line in rusEFI human-readable protocol look like
|
||||
|
|
|
|||
|
|
@ -1,16 +1,18 @@
|
|||
# Maybe prerequisite
|
||||
# Long Term Support Project
|
||||
|
||||
## Maybe prerequisite
|
||||
|
||||
Nathan wonders what the hell does current automation even do. Could this be clarified with minor code comments on top of key files?
|
||||
Nathan reminds that some code generation could/should be integrated into Makefile. Some documentation in <https://github.com/rusefi/rusefi/blob/master/firmware/config/boards/readme.md>
|
||||
|
||||
# Current state
|
||||
## Current state
|
||||
|
||||
* Manual github "latest" release (1. Manual full build without skips, 2. manual download from build server, 3. manual release upload)
|
||||
* Automated master branch snapshot upload
|
||||
* Console can update to master snapshot
|
||||
* Bundle .zip has confusing folder name with timestamp
|
||||
|
||||
# Desired state
|
||||
## Desired state
|
||||
|
||||
* How does github fit with non-linear release flow?
|
||||
* More automated github release process?
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Development Quality Control
|
||||
|
||||
We love our engines and we want them to live a long & happy life. That's why we have a three-tier quality assurance process:
|
||||
|
||||
* Continuous Integration: Unit testing with [Github Actions](<https://github.com/rusefi/rusefi/actions>? query=workflow%3A%22Unit+Test+CI%22) see unit_tests
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
# Developer Quick Start
|
||||
|
||||
STM32F407 firmware
|
||||
|
||||
```
|
||||
```shell
|
||||
git clone --recurse-submodules https://github.com/rusefi/rusefi
|
||||
cd firmware
|
||||
make
|
||||
|
|
|
|||
16
Dev-Tips.md
16
Dev-Tips.md
|
|
@ -1,4 +1,6 @@
|
|||
### GPIO
|
||||
# Developer Tips
|
||||
|
||||
## GPIO
|
||||
|
||||
[efiSetPadMode()](https://rusefi.com/docs/html/io__pins_8cpp.html#a4bd76c1e23f3126d720239707dbcbaaf)
|
||||
[efiReadPin()](https://rusefi.com/docs/html/io__pins_8cpp.html#a6df3ebf4716cb8e2a42f45f6fa7e3afe)
|
||||
|
|
@ -10,7 +12,7 @@ applyNewHardwareSettings() in hw_layer/hardware.cpp
|
|||
incrementGlobalConfigurationVersion() in controllers/algo/engine_configuration.cpp
|
||||
unregisterPins() in controllers/system/efi_gpio.cpp
|
||||
|
||||
### General how-do-I-do-this
|
||||
## General how-do-I-do-this
|
||||
|
||||
most stuff is initiated in engine_controller.cpp
|
||||
|
||||
|
|
@ -27,17 +29,17 @@ US2MS(NT2US()) will convert in the other direction.
|
|||
For logging, use [scheduleMsg()](https://rusefi.com/docs/html/loggingcentral_8h.html#a0da1724993b78c84530d681d254b59a2)
|
||||
sharedLogger is a generally available logger object, which is passed (by reference) to scheduleMsg.
|
||||
|
||||
### Discovery pinout with usable pins
|
||||
## Discovery pinout with usable pins
|
||||
|
||||
[stm32f4 discovery pinout with functions](https://docs.google.com/spreadsheets/d/1pnU3Migcc7JEezvpVt3TcVCbuE5dIXXwrYFGZI97GNM/edit#gid=0)
|
||||
|
||||
### Debugging
|
||||
## Debugging
|
||||
|
||||
[GDB and OpenOCD](http://www.openocd.org/doc/html/GDB-and-OpenOCD.html)
|
||||
|
||||
Using openocd and gdb on STM32F407G-DISC1 requires modifying stm32f4discovery.cfg to source stmlink-v2-1.cfg
|
||||
|
||||
```
|
||||
```shell
|
||||
openocd -f /usr/share/openocd/scripts/board/stm32f4discovery1.cfg
|
||||
arm-none-eabi-gdb rusefi.elf
|
||||
tar ext :3333
|
||||
|
|
@ -47,13 +49,13 @@ load
|
|||
c
|
||||
```
|
||||
|
||||
### Errors
|
||||
## Errors
|
||||
|
||||
`cannot move location counter backwards (from 0000000020020018 to 0000000020020000)`
|
||||
This means that rusEFI is out of memory.
|
||||
Down at the end of engine_controller.cpp there's a dummy array that keeps track of how much free space we have. You can shrink that to give your code room to fit.
|
||||
|
||||
### Testing
|
||||
## Testing
|
||||
|
||||
All tests are run in one instance, but each test gets its own EngineTestHelper, which calls commonInitEngineController, so your objects need to gracefully handle being initiated multiple times.
|
||||
For CONFIG(...) to work in tests, you need a DECLARE_ENGINE_PTR; in the class declaration, then an INJECT_ENGINE_REFERENCE(&myObject), at some point during init.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Performance Tracing
|
||||
|
||||
rusEFI has build-in provisions for performance tracing
|
||||
|
||||
Whenever certain events occur, a few things are logged to a buffer:
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Developing On Linux
|
||||
|
||||
# Compiling
|
||||
## Compiling
|
||||
|
||||
Download the latest ARM GCC from ARM itself: [ARM GCC toolchain](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads)
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ TODO: You probably need to install additional packages but I don't remember what
|
|||
|
||||
Then to compile the firmware,
|
||||
|
||||
```
|
||||
```shell
|
||||
cd firmware
|
||||
make PROJECT_BOARD=nucleo_h743 PROJECT_CPU=ARCH_STM32H7 -j4
|
||||
```
|
||||
|
|
@ -19,23 +19,23 @@ Edit according to your environment.
|
|||
|
||||
To compile the simulator,
|
||||
|
||||
```
|
||||
```shell
|
||||
cd simulator
|
||||
./compile.sh
|
||||
```
|
||||
|
||||
To compile the unit tests,
|
||||
|
||||
```
|
||||
```shell
|
||||
cd unit_tests
|
||||
make -j4
|
||||
```
|
||||
|
||||
# Working with STM32 Dev/Nucleo boards
|
||||
## Working with STM32 Dev/Nucleo boards
|
||||
|
||||
These boards are convenient as they include an ST-Link onboard which aids debugging. I believe the main difference is a Development board includes a bunch of peripherals that you may or may not care about, while a Nucleo board is much more stripped down. Some (all?) boards will be powered when you connect to the ST-Link USB board. The ST-Link will include, among other things, a virtual com port, which can be used to run either the console or TunerStudio. However, by default the ports are not accessible by regular users. You can solve this with:
|
||||
|
||||
```
|
||||
```shell
|
||||
sudo chmod 666 /dev/ttyACM*
|
||||
```
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ To get started, plug the ST-Link side of the dev board into your computer. Gene
|
|||
|
||||
OpenOCD can be left running in the background while you develop in other windows. It will provide a GDB server, a telnet connection for issuing commands, and a TCL interface. We'll just ignore the last one for now. To start OpenOCD, you need to pass in a board configuration file. Luckily they exist for most any off the shelf board you care about.
|
||||
|
||||
```
|
||||
```shell
|
||||
sudo ~/openocd/xpack-openocd-0.11.0-2/bin/openocd -f ~/openocd/xpack-openocd-0.11.0-2/scripts/board/st_nucleo_h743zi.cfg
|
||||
```
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ Adjust as necessary; you may need `sudo` if you don't normally have access to US
|
|||
|
||||
To reprogram, simply do:
|
||||
|
||||
```
|
||||
```shell
|
||||
telnet localhost 4444
|
||||
program build/rusefi.elf reset
|
||||
exit
|
||||
|
|
@ -66,7 +66,7 @@ exit
|
|||
|
||||
Or, if you prefer a one-liner:
|
||||
|
||||
```
|
||||
```shell
|
||||
(echo "program build/rusefi.elf reset"; echo exit) | nc localhost 4444
|
||||
```
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ Conveniently, OpenOCD will retain a history of commands, allowing you to use up-
|
|||
|
||||
On a nucleo-h743, I don't seem to get much indication this worked, but if you connect via gdb:
|
||||
|
||||
```
|
||||
```shell
|
||||
gdb build/rusefi.elf
|
||||
target remote :3333
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Digital Dash
|
||||
|
||||
We have 4 versions of Digital Dash currently
|
||||
|
||||
A-- The Quickest and easiest Digital Dash is TunerStudioMS... And is described Below
|
||||
|
|
@ -8,13 +10,13 @@ C-- Third is a Custom Digital Gauge cluster... [Link HERE](https://customgt6.com
|
|||
|
||||
D— Fourth is Android tablet or phone running the [Real Dash](http://realdash.net/index.php) App
|
||||
|
||||
# How to set up a Raspberry Pi with TunerStudio as a Digital Dash
|
||||
## How to set up a Raspberry Pi with TunerStudio as a Digital Dash
|
||||
|
||||
Click the image to watch a video of a Raspberry Pi rusEFI connected display. Early "proof of concept"
|
||||
|
||||
[](https://www.youtube.com/watch?v=a0mdhANrIhw "PiDash rusEFI")
|
||||
|
||||
# Hardware Needed
|
||||
## Hardware Needed
|
||||
|
||||
Component|Link
|
||||
-------|----------
|
||||
|
|
@ -29,17 +31,17 @@ Controls|[Keyboard and Mouse](https://www.amazon.com/Logitech-Wireless-Keyboard-
|
|||
|
||||
2. Extract to your home directory
|
||||
|
||||
a. Default home directory is "pi", open terminal and type: "ls /home/pi/TunerStudioMS" (if your home directory isnt "pi" change to match your home directory)
|
||||
a. Default home directory is "pi", open terminal and type: "ls /home/pi/TunerStudioMS" (if your home directory isnt "pi" change to match your home directory)
|
||||
|
||||
b. Ensure that "TunerStudio.sh" shows up in the results. If it is not, re-install
|
||||
b. Ensure that "TunerStudio.sh" shows up in the results. If it is not, re-install
|
||||
|
||||
Note: you MAY need to install JAVA... if so, type
|
||||
Note: you MAY need to install JAVA... if so, type
|
||||
|
||||
`sudo apt-get install openjdk-8-jre`
|
||||
`sudo apt-get install openjdk-8-jre`
|
||||
|
||||
To set default Java runtime
|
||||
To set default Java runtime
|
||||
|
||||
`sudo update-alternatives --config java`
|
||||
`sudo update-alternatives --config java`
|
||||
|
||||
3. Create link to start TunerStudio:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
### Install firmware on Frankenstein, Frankenso, and Discovery
|
||||
# Install firmware on Frankenstein, Frankenso, and Discovery
|
||||
|
||||
1. Connect the stm32f4discovery ('brain board') to the IO board, place jumpers like XYZ, then connect to a PC with a mini-USB cable. Mini-USB cable is used to power and to program the brain board. See below procedure found [here](http://rusefi.com/forum/viewtopic.php?f=5&t=210&start=23)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 2003 Dodge Neon
|
||||
|
||||
[1995-2005 Neon T350/T350HD Transaxle Cross-Reference Guide](http://www.neons.org/forumdodge/trans.htm)
|
||||
|
||||
Bosch 0280-155-976 injectors
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# 1996 Dodge Ram 1500
|
||||
|
||||
|
||||
|
||||
[1996 Dodge RAM 1500 V8 - Forum](http://rusefi.com/forum/viewtopic.php?f=3&t=864)
|
||||
|
|
|
|||
17
Download.md
17
Download.md
|
|
@ -1,8 +1,11 @@
|
|||
# Download
|
||||
|
||||
rusEFI offers complete software download bundles for multiple supported microcontrollers and boards.
|
||||
|
||||
# IMPORTANT NOTE: TunerStudio v3.1.04 or later is REQUIRED! Please double check the version before updating your firmware, or your settings could be lost when updating
|
||||
**IMPORTANT NOTE: TunerStudio v3.1.04 or later is REQUIRED!
|
||||
Please double check the version before updating your firmware, or your settings could be lost when updating**
|
||||
|
||||
### Common Boards
|
||||
## Common Boards
|
||||
|
||||
[microRusEFI 0.4 and newer (STM32F4)](microRusEFI-Manual#software)
|
||||
|
||||
|
|
@ -10,7 +13,7 @@ rusEFI offers complete software download bundles for multiple supported microcon
|
|||
|
||||
[STM32 Discovery Release](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_default.zip)
|
||||
|
||||
### Hellen Family Boards
|
||||
## Hellen Family Boards
|
||||
|
||||
[Nissan 121 pin](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_hellen121nissan.zip)
|
||||
|
||||
|
|
@ -22,7 +25,7 @@ rusEFI offers complete software download bundles for multiple supported microcon
|
|||
|
||||
[Miata NA6 64 pin](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_hellenNA6.zip)
|
||||
|
||||
### Uncommon Boards
|
||||
## Uncommon Boards
|
||||
|
||||
[Discovery stm32f407 bundle](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle.zip)
|
||||
|
||||
|
|
@ -32,13 +35,13 @@ rusEFI offers complete software download bundles for multiple supported microcon
|
|||
|
||||
[Proteus 0.2 and older (STM32F7)](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_proteus_legacy.zip)
|
||||
|
||||
# Advanced
|
||||
## Advanced
|
||||
|
||||
[Older Releases](https://github.com/rusefi/rusefi/releases/)
|
||||
|
||||
[Snapshot builds](https://rusefi.com/build_server/)
|
||||
|
||||
# [Quick Start](HOWTO-quick-start)
|
||||
**[Quick Start](HOWTO-quick-start)**
|
||||
|
||||
[Choose Your Own Adventure](Try-It)
|
||||
|
||||
|
|
@ -46,6 +49,6 @@ rusEFI offers complete software download bundles for multiple supported microcon
|
|||
|
||||
## FAQ
|
||||
|
||||
# Q: I see something interesting was just changed in the firmware? How do I use latest version?
|
||||
**Q: I see something interesting was just changed in the firmware? How do I use latest version?**
|
||||
|
||||
A: Most snapshot builds take about 30 minutes to get updated on at [Snapshot builds](https://rusefi.com/build_server/)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# E65 CAN bus
|
||||
|
||||
First priority to control 6HP26 gearbox
|
||||
|
||||
[Forum Thread](https://rusefi.com/forum/viewtopic.php?f=2&t=2241)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Ecotec
|
||||
# Ecotec
|
||||
|
||||
[Ecotec Miata How-to](https://www.ecotecmiata.ca/how-to)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +1,18 @@
|
|||
## _WARNING: An electronic throttle, if misconfigured or damaged, has the ability to open the throttle without your foot on the pedal, potentially leading to engine damage [or a crash](https://en.wikipedia.org/wiki/2009%E2%80%9311_Toyota_vehicle_recalls). Proceed with caution!_
|
||||
# Electronic Throttle Body Configuration Guide
|
||||
|
||||
# Wiring
|
||||
***WARNING: An electronic throttle, if misconfigured or damaged, has the ability to open the throttle without your foot on the pedal, potentially leading to engine damage [or a crash](https://en.wikipedia.org/wiki/2009%E2%80%9311_Toyota_vehicle_recalls). Proceed with caution!***
|
||||
|
||||
## Throttle Position Sensors
|
||||
## Wiring
|
||||
|
||||
### Throttle Position Sensors
|
||||
|
||||
Electronic throttles always have two redundant throttle position signals (TPS). The exact relationship between them is not restricted, but it is required that there are two signals present.
|
||||
|
||||
## Accelerator Pedal
|
||||
### Accelerator Pedal
|
||||
|
||||
Similar to TPS, accelerator pedals have two or three redundant position signals. If you have three, leave one unconnected as rusEFI only requires two.
|
||||
|
||||
## Motor
|
||||
### Motor
|
||||
|
||||
rusEFI supports electronic throttles that use brushed DC motors. This includes nearly all modern throttles, but excludes some very early ETB implementations (BMW, Toyota) that used a stepper motor instead.
|
||||
|
||||
|
|
@ -18,13 +20,13 @@ Brushed DC motors have two wires. When connected to power one way the throttle
|
|||
|
||||
Most throttles have one connector that contains both the position sensors and motor, but some use separate connectors. Electrically they are the same either way.
|
||||
|
||||
# Basic Setup
|
||||
## Basic Setup
|
||||
|
||||
## Calibrate Sensors
|
||||
### Calibrate Sensors
|
||||
|
||||
### Pedal position sensor
|
||||
#### Pedal position sensor
|
||||
|
||||
In TunerStudio, open the _"Accelerator pedal"_ window from the _Sensors_ menu.
|
||||
In TunerStudio, open the *"Accelerator pedal"* window from the *Sensors* menu.
|
||||
|
||||
1. Select the channels wired to your primary and secondary redundant pedal sensors. Using both is a safety concern: this lets rusEFI detect a broken or shorted wire or failed sensor.
|
||||
2. Restart the ECU: disconnect USB, and cycle the ignition off, then back on, and reconnect USB.
|
||||
|
|
@ -33,29 +35,29 @@ In TunerStudio, open the _"Accelerator pedal"_ window from the _Sensors_ menu.
|
|||
5. Repeat with the pedal pressed all the way to the floor.
|
||||
6. Press BURN, and ensure that the "Throttle pedal position" gauge moves smoothly to match the pedal's position.
|
||||
|
||||
### Throttle position sensor
|
||||
#### Throttle position sensor
|
||||
|
||||
In TunerStudio, open the _"TPS"_ window from the _Sensors_ menu.
|
||||
In TunerStudio, open the *"TPS"* window from the *Sensors* menu.
|
||||
|
||||
1. Remove intake plumbing such that you can see and touch the throttle plate in the throttle body to confirm proper operation.
|
||||
2. Select the channels wired to your primary and secondary redundant throttle position sensors. Using both is a safety concern: this lets rusEFI detect a broken or shorted wire or failed sensor.
|
||||
3. Restart the ECU: disconnect USB, and cycle the ignition off, then back on, and reconnect USB.
|
||||
4. Push the "auto calibrate ETB 1" button. The throttle should first OPEN, then CLOSE. If it does the inverse, your throttle motor is wired backwards, and ETB+ and ETB- wires must be physically swapped.
|
||||
6. Press BURN. Ensure that the TPS gauge reads correctly for the full range of throttle positions.
|
||||
5. Press BURN. Ensure that the TPS gauge reads correctly for the full range of throttle positions.
|
||||
|
||||
Repeat this process for the second throttle, if present.
|
||||
|
||||
# Throttle Tuning
|
||||
## Throttle Tuning
|
||||
|
||||
See [Tuning ETB PID - Forum](https://rusefi.com/forum/viewtopic.php?f=5&t=592&start=150#p32044)
|
||||
|
||||
[rusEFI ETB PID Autotune - Video](https://www.youtube.com/watch?v=USU0nnekokA)
|
||||
|
||||
## Autotune PID
|
||||
### Autotune PID
|
||||
|
||||
rusEFI includes PID auto-tuning software that can help generate a starting point for your PID settings. It is often good enough that no further tuning is required for good performance.
|
||||
|
||||
### _Ensure the engine is off! Do not attempt to start the engine during this process!_
|
||||
#### *Ensure the engine is off! Do not attempt to start the engine during this process!*
|
||||
|
||||
1. Ensure your electronic throttle roughly tracks the target position. Speed or perfection is not required, but it should at least work. Confirm this by checking that the gauge "ETB position error" displays small values while moving the throttle around gently (a few percent is fine, so long as it trends towards zero if you stop moving). If not, revisit the basic configuration steps above.
|
||||
2. Press `Start ETB PID Autotune` button. The throttle will begin oscillating around 50% position: this is normal.
|
||||
|
|
@ -63,13 +65,13 @@ rusEFI includes PID auto-tuning software that can help generate a starting point
|
|||
|
||||
*Note: to see additional detail about the autotuning process, the [debug mode](Debug-Mode) `ETB Autotune` and gauges Ku, Tu, Kp, Ki, Kd (in debug menu) (todo: add screenshot) may be interesting*
|
||||
|
||||
## Tune Bias Table
|
||||
### Tune Bias Table
|
||||
|
||||
Also known as a "feed forward" term, bias curve serves to offset the throttle's return spring. The table stores how much PWM duty cycle is required to hold the throttle at that particular throttle position against the spring. Since the spring pushes towards ~5-20%, the value will be negative when below the neutral point, and positive above it, transitioning steeply as it passes the neutral point of the spring.
|
||||
|
||||
We are interested in positions like 0, between-0-and-default, default, a bit open, a bit more open, 50% open, wide open,
|
||||
|
||||
## Configure Pedal Map
|
||||
### Configure Pedal Map
|
||||
|
||||
The pedal map allows you to configure how the electronic throttle's position responds to driver input on the accelerator pedal. Since engines with electronic throttles often have oversized throttles (because they can), this table is required to make the accelerator less sensitive for small openings, as this hurts drivability.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
## _WARNING: An electronic throttle, if misconfigured or damaged, has the ability to open the throttle without your foot on the pedal, potentially leading to engine damage [or a crash](https://en.wikipedia.org/wiki/2009%E2%80%9311_Toyota_vehicle_recalls). Proceed with caution!_
|
||||
# Electronic Throttle Body
|
||||
|
||||
***WARNING: An electronic throttle, if misconfigured or damaged, has the ability to open the throttle without your foot on the pedal, potentially leading to engine damage [or a crash](https://en.wikipedia.org/wiki/2009%E2%80%9311_Toyota_vehicle_recalls). Proceed with caution!***
|
||||
|
||||
See also [Vault Of Electronic Throttle Bodies ETB](Vault-Of-Electronic-Throttle-Bodies-ETB)
|
||||
|
||||
|
|
@ -11,11 +13,11 @@ There are several benefits by allowing the ECU to control the position of the th
|
|||
- No need to route a cable to the throttle
|
||||
- Programmable throttle target curve/nonlinearity to improve drivability with a large throttle on a small engine
|
||||
|
||||
# Configuration and Setup Guide
|
||||
## Configuration and Setup Guide
|
||||
|
||||
[See configuration guide here.](Electronic-Throttle-Body-Configuration-Guide)
|
||||
|
||||
# Theory of Operation
|
||||
## Theory of Operation
|
||||
|
||||
Electronic throttles typically consist of:
|
||||
|
||||
|
|
@ -49,7 +51,7 @@ PWM on both direction pins, one for forward another one for reverse.
|
|||
|
||||
TLE7209 is an example of two-wire mode.
|
||||
|
||||
# Pinouts
|
||||
## Pinouts
|
||||
|
||||
See [broken link](https://raw.githubusercontent.com/wiki/rusefi/rusefi_documentation/oem_docs/VAG/Bosch_0280750009_pinout.jpg) for
|
||||
personal choice of colors for VAG ETB.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Engine Types
|
||||
|
||||
Update 2017: things are much more settled these days, at least 6 months without an incompatible configuration format change.
|
||||
|
||||
The best way to configure rusEFI according to your engine setup is via Tuner Studio - there are not many settings there, it should be to some expend self-explanatory. In case of any questions your best chance at the moment is to ask questions on the forum - there are still not enough walk-troughs and articles.
|
||||
|
|
|
|||
|
|
@ -1 +1,3 @@
|
|||
# OBD Error Codes
|
||||
|
||||
See [OBD Error Codes header](https://github.com/rusefi/rusefi/blob/master/firmware/controllers/algo/obd_error_codes.h)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# F7 Requires Full Erase
|
||||
|
||||
While most rusEFI units support incremental firmware update while keeping settings intact we are facing unexplained issue with some F7 Proteus units. Those units require full erase prior to software update.
|
||||
|
||||
Step 1: enter DFU
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# FAQ: Basic Wiring and Connections
|
||||
|
||||
# Intro
|
||||
## Intro
|
||||
|
||||
This page contains information about how to hook up to rusEFI hardware, in general. It's not intended to be a guide to a specific hardware variant - rather, how to figure out what you're going to need to run the different kinds of hardware you'd find in an engine bay.
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,3 @@
|
|||
# Flipped VR Wires
|
||||
|
||||
See [Trigger-Configuration-Guide](Trigger-Configuration-Guide)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Unsaved Changes Indicator
|
||||
|
||||
Q: what does "unsaved changed" indicator mean?
|
||||
|
||||
A: Most rusEFI units cannot save calibration into internal storage while engine is running.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Feature Requests: The Feature Bounty Program
|
||||
|
||||
The challenge of rusEFI as of 2020 is the fact that hardware is way ahead of software at this point. With just a few programmers and the complexity of the project, it would be a while until normal users would be benefiting from rusEFI because of the complexity and knowledge required.
|
||||
|
||||
But if for any reason you would prefer to use rusEFI and look for any specific feature, money can probably help you!
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# Firmware Update via CAN
|
||||
|
||||
## technical info
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,3 @@
|
|||
# First Engine Start
|
||||
|
||||
Please see here: [HOWTO Get Running](HOWTO-Get-Running.md)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Flex Fuel
|
||||
|
||||
## Sensor and Wiring
|
||||
|
||||
The following Sensors are known to work
|
||||
|
|
@ -12,7 +14,7 @@ GM part numbers
|
|||
|
||||
The Pinout is shown below
|
||||
|
||||
|
||||
|
||||
|
||||
## Sensor Setup
|
||||
|
||||
|
|
@ -20,7 +22,7 @@ Connect your sensor to a digital input on the ECU. Then, pick the pin in TunerSt
|
|||
|
||||
(technical details - we expect a pull-up on the ECU, about 3K, somewhere 1K to 5K)
|
||||
|
||||
|
||||
|
||||
|
||||
## Fueling Setup
|
||||
|
||||
|
|
@ -30,7 +32,7 @@ That's it! The firmware will now automatically vary the fuel's stoichiometric ra
|
|||
|
||||
**It's recommended to switch to lambda mode (`File -> Vehicle Projects -> Project Properties -> Settings -> Lambda Display`), as the target lambda table is multiplied by the current stoichiometric ratio to get the target air/fuel ratio.**
|
||||
|
||||
|
||||
|
||||
|
||||
## Ignition Timing
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Frankenso Hall Input
|
||||
|
||||
## Typical Hall
|
||||
|
||||
For example, Mazda distributor sensors.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Frankenso Hand-Soldering Step-by-Step
|
||||
|
||||
This page is dedicated to my experience with Frankenso 0.5 board, especially manual soldering and bringing it to life.
|
||||
|
||||
## Prerequisites
|
||||
|
|
|
|||
|
|
@ -1,10 +1,12 @@
|
|||
## LEGACY CONTENT, please use BeerMoneyMotorsports Miata ECU
|
||||
# Frankenso Mazda Miata NA6 PNP Board Wiring
|
||||
|
||||
**LEGACY CONTENT, please use BeerMoneyMotorsports Miata ECU**
|
||||
|
||||
|
||||
|
||||
[Frankenso Board Technical Details](Hardware-Frankenso#default-pinout)
|
||||
|
||||
# Board Jumper Wires
|
||||
## Board Jumper Wires
|
||||
|
||||
| # & Color | From | To | Function | |
|
||||
|------|------|----|-------|---|
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# Frankenso Mazda Miata NA6 PNP
|
||||
|
||||
The [Frankenso](Hardware-Frankenso) board was designed to be used on Mazda Miata NA6 as a plug-and-play solution.
|
||||
|
||||
|
|
@ -19,7 +20,7 @@ Stage 0 + External wide band controller, wide band oxygen sensor, external MAP s
|
|||
|
||||
Stage 1 + TPS
|
||||
|
||||
#### Bench testing options
|
||||
## Bench testing options
|
||||
|
||||
On NA6 Spark #1 and Spark #3 would audibly click if you use bench Spark Test button.
|
||||
Because of wasted spark wiring Spark #2 and Spark #4 are not expected to click.
|
||||
|
|
@ -31,7 +32,7 @@ All you need is a relatively quiet surroundings and you would hear both spark an
|
|||
are louder, spark is less loud but also totally audible. Both Test buttons are expected to
|
||||
produce three clicks a second after you press the button in the software.
|
||||
|
||||
#### Wideband O2 sensor wire WBO
|
||||
## Wideband O2 sensor wire WBO
|
||||
|
||||
You would really need a wideband sensor. Here is the middle plug pinout to wire an external wideband controller - +12v would feed external controller and analog output signal would provide rusEFI ECU with air/fuel ratio information.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Frankenso VR Input
|
||||
|
||||
## Typical VR application
|
||||
|
||||
For example, 1995 Honda Accord (and most OBD-I Honda vehicle), 2003 Dodge Neon.
|
||||
|
|
|
|||
10
Frankenso.md
10
Frankenso.md
|
|
@ -1,8 +1,8 @@
|
|||
**red 2003 VVT test mule Miata NB2 #27**
|
||||
# Red 2003 VVT test mule Miata NB2 #27
|
||||
|
||||
[red 2003 VVT test mule Miata NB2 - Forum](https://rusefi.com/forum/viewtopic.php?f=3&t=1095)
|
||||
|
||||
[PCB front](installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_front.jpg)
|
||||
[PCB back](installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_back.jpg)
|
||||
[ECU Plug Latch](installations/MazdaMiataNB2_Frankenso/nb2_ecu_plugs_latch.jpg)
|
||||
[ECU pins](installations/MazdaMiataNB2_Frankenso/NB2_Miata_ECU_Connectors_Add-Ons.png)
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Frankenstein Pinout
|
||||
|
||||
## P1
|
||||
|
||||
|def|pin|pin|def
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
## Fuel injector info
|
||||
# Fuel injector info
|
||||
|
||||
### Fuel injectors
|
||||
## Fuel injectors
|
||||
|
||||
As of May 2020, only saturated (high impedance, >8 ohms) port injectors are supported.
|
||||
All hardware variants are built around the concept of one ECU pin controlling one fuel injector. The use of multiple injectors on one ECU output must be very carefully evaluated to avoid overloading drivers. One injector may also be used for all cylinders("single point"). A pair of injectors can be wired together and fired simultaneously, as in 4 pairs of injectors on a V8. It's possible but not intuitive to configure two banks of multiple cylinders of injectors alternating fire. It is recommended to use one injector per cylinder. As of May 2020, staged injection with multiple injectors per cylinder is possible in hardware but the software is not yet ready.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ The Air Fuel Ratio (AFR) is controlled by how much fuel is delivered to the cyli
|
|||
|
||||
Most people who are installing tune-able ECU's like rusEFI are looking for more power at the track. However your fuel weight advantage is also commonly important. So it is common that an engine will be tuned for peak power when over a certain load, and peak economy when at a cruise load. OEM's are often concerned with minimal environmental impact, so they may tune to a different AFR. Once you have decided on what your AFR strategy is going to be, you'll have to tune rusEFI to deliver that strategy. As well you will probably use a wide band oxygen sensor to measure your AFR and ensure that you are meeting your desired AFR target.
|
||||
|
||||
# Supported fuel control algorithms
|
||||
## Supported fuel control algorithms
|
||||
|
||||
rusEFI supports mono, individual/sequential and batched fuel injection using one of the following fuel control algorithms:
|
||||
|
||||
|
|
@ -145,14 +145,14 @@ In future more adjustments may be needed- for example at low rpms a throttle tha
|
|||
|
||||
1. Come up with a strategy on how to deal with cumulative effects. Example: Push down on the gas pedal. What if that process takes longer than one engine rotation?
|
||||
|
||||
**Example:**
|
||||
| Rotation in deg | Throttle Pos | Addtl. fuel current | Addtl. Fuel Taper
|
||||
| - | - | - | - |
|
||||
| 0 | 0 | 0 | 0 |
|
||||
| 360 | 2 | 13 | 0 |
|
||||
| 720 | 4 | 5 | 8 |
|
||||
**Example:**
|
||||
| Rotation in deg | Throttle Pos | Addtl. fuel current | Addtl. Fuel Taper
|
||||
| - | - | - | - |
|
||||
| 0 | 0 | 0 | 0 |
|
||||
| 360 | 2 | 13 | 0 |
|
||||
| 720 | 4 | 5 | 8 |
|
||||
|
||||
Should the fuel from the current change and the previous taper be added up? Or averaged? Or should the latest change completely override the previous change?
|
||||
Should the fuel from the current change and the previous taper be added up? Or averaged? Or should the latest change completely override the previous change?
|
||||
|
||||
2. Deal with warming up. During warmup more additional fuel is needed. We need a setting to adjust for that.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Future Features
|
||||
|
||||
This is a bundle of all our discussed but no time to do ideas.
|
||||
|
||||
- MS DBW extension mode - Simple mode to can interface with a MS unit and provide drive by wire capability.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# GDI Status
|
||||
|
||||
TL,DR: we had car [starting/idling - Video](https://youtu.be/JB2RnAJJSOk) using a [plywood board - Forum](https://rusefi.com/forum/download/file.php?id=6429) we have postponed GDI progress until funding or qualified contributor joins the game.
|
||||
|
||||
[Forum thread for test mule](https://rusefi.com/forum/viewtopic.php?f=3&t=1631)
|
||||
|
|
|
|||
2
GDI4.md
2
GDI4.md
|
|
@ -15,7 +15,7 @@
|
|||
|
||||
|
||||
|
||||
# Changelog
|
||||
## Changelog
|
||||
|
||||
rev C:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# GM E38
|
||||
|
||||
[Schematics rev a](Hardware/Hellen/hellen-gm-e38-a-schematic.pdf)
|
||||
|
||||
mc123 black 73 31387-2014 and grey 80 31387-4009.
|
||||
|
|
|
|||
138
GM-E67.md
138
GM-E67.md
|
|
@ -1,3 +1,5 @@
|
|||
# GM E67
|
||||
|
||||
[Schematics rev b](Hardware/Hellen/hellen-gm-e67-b-schematic.pdf) [iBom rev b](https://rusefi.com/docs/ibom/hellen-gm-e67-b-ibom.html)
|
||||
|
||||
[Pinout](https://rusefi.com/docs/pinouts/hellen/hellen-gm-e67/)
|
||||
|
|
@ -12,7 +14,7 @@
|
|||
|
||||
mx123 molex. 56 pin blue 31386-2020. 73 pin black 31387-2014. 73 pin grey 31387-2002
|
||||
|
||||
# Alternator
|
||||
## Alternator
|
||||
|
||||
[OEM-Docs/GM/e67-CTSV.Charging.pdf](OEM-Docs/GM/e67-CTSV.Charging.pdf)
|
||||
|
||||
|
|
@ -20,7 +22,7 @@ mx123 molex. 56 pin blue 31386-2020. 73 pin black 31387-2014. 73 pin grey 31387-
|
|||
|
||||
[OEM-Docs/GM/e67-TBSS.Charging.pdf](OEM-Docs/GM/e67-TBSS.Charging.pdf)
|
||||
|
||||
# Vehicles
|
||||
## Vehicles
|
||||
|
||||
[LS9 crate](OEM-Docs/GM/ls9-crate-engine-control-system-19354338.pdf)
|
||||
|
||||
|
|
@ -38,70 +40,68 @@ mx123 molex. 56 pin blue 31386-2020. 73 pin black 31387-2014. 73 pin grey 31387-
|
|||
|
||||
Gen IV V8, V6, L4 E67 ECM – Stream E67
|
||||
|
||||
```
|
||||
V8 Cars
|
||||
08 Buick Allure 5.3L
|
||||
08-09 Buick Lacrosse 5.3L
|
||||
06-09 Buick Lucerne 4.6L
|
||||
06-07 Cadillac CTS-V 6.0L
|
||||
08-15 Cadillac CTS-V 6.2L
|
||||
06-09 Cadillac DTS 4.6L
|
||||
06-10 Cadillac STS 4.4L, 4.6L
|
||||
06-09 Cadillac XLR 4.4L, 4.6L
|
||||
12-15 Chevrolet Camaro 6.2L
|
||||
10-13 Chevrolet Corvette ZR1 6.2L
|
||||
07-09 Chevrolet Impala SS 5.3L
|
||||
07 Chevrolet Monte Carlo SS 5.3L
|
||||
13-15 Holden HSV GTS (S/C) 6.2L
|
||||
07 Pontiac Grand Prix 5.3L
|
||||
V6 Cars
|
||||
06 Chevrolet Impala 3.9L
|
||||
09 Chevrolet Impala 3.5L
|
||||
06 Chevrolet Malibu 3.9L
|
||||
08-11 Chevrolet Malibu 3.5L, 3.6L (not DI)
|
||||
12 Chevrolet Malibu LTZ 3.6L
|
||||
06-08 Chevrolet Monte Carlo 3.9L
|
||||
07-08 Chevrolet Monte Carlo 3.5L
|
||||
06-09 Pontiac G6 3.6L, 3.9L (not DI)
|
||||
07-09 Pontiac G6 3.5L
|
||||
07-09 Saturn Aura 3.6L (not DI)
|
||||
06-07 Chevrolet Cobalt 2.4L
|
||||
06-07 Chevrolet HHR 2.2L, 2.4L
|
||||
08 Chevrolet Malibu 2.4L
|
||||
08-09 Chevrolet Malibu – Hybrid 2.4L
|
||||
07 Pontiac G5 GT 2.4L
|
||||
06-07 Pontiac G6 2.4L
|
||||
06 Pontiac Pursuit 2.4L
|
||||
06-07 Pontiac Solstice 2.4L
|
||||
06-07 Saturn Aura 2.4L
|
||||
08-09 Saturn Aura – Hybrid 2.4L
|
||||
06-07 Saturn Ion 2.2L, 2.4L
|
||||
07 Saturn Sky 2.4L
|
||||
SUV’s
|
||||
08 Buick Enclave 3.6L (not DI)
|
||||
07 Buick Rainier 5.3L
|
||||
09 Cadillac Escalade – Hybrid 6.0L
|
||||
07-09 Cadillac SRX 4.6L
|
||||
08-09 Chevrolet Tahoe – Hybrid 6.0L
|
||||
07-09 Chevrolet Trailblazer (4.2L 08-09 only) 4.2L, 5.3L, 6.0L
|
||||
07-08 GMC Arcadia 3.6L (not DI)
|
||||
07-08 GMC Envoy (4.2L 08-09 only) 4.2L, 5.3L, 6.0L
|
||||
08-09 GMC Yukon – Hybrid 6.0L
|
||||
08-10 Hummer H3 3.7L, 5.3L
|
||||
08 Isuzu Ascender 3.6L (not DI)
|
||||
07-09 Saab 9-7X (4.2L 08-09 only) 4.2L, 5.3L
|
||||
07-08 Saturn Outlook 3.6L (not DI)
|
||||
07-08 Saturn Vue 2.4L, 3.6L (not DI)
|
||||
08-09 Saturn Vue – Hybrid 2.4L
|
||||
Vans
|
||||
06-07 Buick Terraza 3.9L
|
||||
06-08 Chevrolet Uplander 3.9L
|
||||
06-08 Pontiac Montana 3.9L
|
||||
06-07 Saturn Relay 3.9L
|
||||
Trucks
|
||||
08-12 Chevrolet Colorado 2.9L, 3.7L, 5.3L
|
||||
08-12 GMC Canyon 2.9L, 3.7L, 5.3L
|
||||
08-09 Isuzu i-Series 2.9L, 3.7L
|
||||
Non Production Vehicles
|
||||
07-15 GM Performance Parts E67 ECM 6.0L, 6.2L, 7.0L
|
||||
```
|
||||
V8 Cars
|
||||
08 Buick Allure 5.3L
|
||||
08-09 Buick Lacrosse 5.3L
|
||||
06-09 Buick Lucerne 4.6L
|
||||
06-07 Cadillac CTS-V 6.0L
|
||||
08-15 Cadillac CTS-V 6.2L
|
||||
06-09 Cadillac DTS 4.6L
|
||||
06-10 Cadillac STS 4.4L, 4.6L
|
||||
06-09 Cadillac XLR 4.4L, 4.6L
|
||||
12-15 Chevrolet Camaro 6.2L
|
||||
10-13 Chevrolet Corvette ZR1 6.2L
|
||||
07-09 Chevrolet Impala SS 5.3L
|
||||
07 Chevrolet Monte Carlo SS 5.3L
|
||||
13-15 Holden HSV GTS (S/C) 6.2L
|
||||
07 Pontiac Grand Prix 5.3L
|
||||
V6 Cars
|
||||
06 Chevrolet Impala 3.9L
|
||||
09 Chevrolet Impala 3.5L
|
||||
06 Chevrolet Malibu 3.9L
|
||||
08-11 Chevrolet Malibu 3.5L, 3.6L (not DI)
|
||||
12 Chevrolet Malibu LTZ 3.6L
|
||||
06-08 Chevrolet Monte Carlo 3.9L
|
||||
07-08 Chevrolet Monte Carlo 3.5L
|
||||
06-09 Pontiac G6 3.6L, 3.9L (not DI)
|
||||
07-09 Pontiac G6 3.5L
|
||||
07-09 Saturn Aura 3.6L (not DI)
|
||||
06-07 Chevrolet Cobalt 2.4L
|
||||
06-07 Chevrolet HHR 2.2L, 2.4L
|
||||
08 Chevrolet Malibu 2.4L
|
||||
08-09 Chevrolet Malibu – Hybrid 2.4L
|
||||
07 Pontiac G5 GT 2.4L
|
||||
06-07 Pontiac G6 2.4L
|
||||
06 Pontiac Pursuit 2.4L
|
||||
06-07 Pontiac Solstice 2.4L
|
||||
06-07 Saturn Aura 2.4L
|
||||
08-09 Saturn Aura – Hybrid 2.4L
|
||||
06-07 Saturn Ion 2.2L, 2.4L
|
||||
07 Saturn Sky 2.4L
|
||||
SUV’s
|
||||
08 Buick Enclave 3.6L (not DI)
|
||||
07 Buick Rainier 5.3L
|
||||
09 Cadillac Escalade – Hybrid 6.0L
|
||||
07-09 Cadillac SRX 4.6L
|
||||
08-09 Chevrolet Tahoe – Hybrid 6.0L
|
||||
07-09 Chevrolet Trailblazer (4.2L 08-09 only) 4.2L, 5.3L, 6.0L
|
||||
07-08 GMC Arcadia 3.6L (not DI)
|
||||
07-08 GMC Envoy (4.2L 08-09 only) 4.2L, 5.3L, 6.0L
|
||||
08-09 GMC Yukon – Hybrid 6.0L
|
||||
08-10 Hummer H3 3.7L, 5.3L
|
||||
08 Isuzu Ascender 3.6L (not DI)
|
||||
07-09 Saab 9-7X (4.2L 08-09 only) 4.2L, 5.3L
|
||||
07-08 Saturn Outlook 3.6L (not DI)
|
||||
07-08 Saturn Vue 2.4L, 3.6L (not DI)
|
||||
08-09 Saturn Vue – Hybrid 2.4L
|
||||
Vans
|
||||
06-07 Buick Terraza 3.9L
|
||||
06-08 Chevrolet Uplander 3.9L
|
||||
06-08 Pontiac Montana 3.9L
|
||||
06-07 Saturn Relay 3.9L
|
||||
Trucks
|
||||
08-12 Chevrolet Colorado 2.9L, 3.7L, 5.3L
|
||||
08-12 GMC Canyon 2.9L, 3.7L, 5.3L
|
||||
08-09 Isuzu i-Series 2.9L, 3.7L
|
||||
Non Production Vehicles
|
||||
07-15 GM Performance Parts E67 ECM 6.0L, 6.2L, 7.0L
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# GM MAP Sensor
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Gen 4 LS
|
||||
|
||||
<https://github.com/rusefi/rusefi/wiki/GM-E38>
|
||||
|
||||
<https://github.com/rusefi/rusefi/wiki/GM-E67>
|
||||
|
|
@ -20,11 +22,11 @@ All PowerPC. There are early (2006-2009) and late (2010-2013) models of each whi
|
|||
|
||||
If I had to make an educated guess, GM used the E67 for their GMPP (GM Performance Parts) control packs because they had more of them left over. The E38 was the more popular application by far.
|
||||
|
||||
# e67
|
||||
## e67
|
||||
|
||||
<https://github.com/rusefi/rusefi/wiki/GM-E67>
|
||||
|
||||
# e38 2007 Tahoe 5.3
|
||||
## e38 2007 Tahoe 5.3
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Gen 5 LS
|
||||
|
||||
E39
|
||||
|
||||
E92
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue