rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

manual fixing

This commit is contained in:
David Holdeman 2021-02-15 22:43:25 -06:00
parent eba0dcd90e
commit 2d5b274036
12 changed files with 18 additions and 78 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Components/MAX232.md
View File

@ -2,6 +2,6 @@ MAX232 chip - dual 232 driver - could be used to stimulate VR sensing circuits
![MAX232 Pinout](Images/max232_pinout.png) ![MAX232 Pinout](Images/max232_pinout.png)
![MAX232 Application Information](Images/max232_appinfo.png) ![MAX232 Application Information](Images/max232-appinfo.png)
![MAX232 on a Breadboard](Images/max232_breadboard.png) ![MAX232 on a Breadboard](Images/max232_breadboard.jpg)

4
Fuel/Fuel_Control/Acceleration/X-tau-Wall-Wetting.md
View File

@ -64,9 +64,9 @@ Good tuning of the X-tau system relies on taking logs and some trial and error t
# Old info # Old info
![config](ww_sample_config.jpg) ![config](X-tau-Wall-Wetting)
![log](ww_log.jpg) ![log](./Overview/wall_wetting/wall_wetting_log.jpg)
This is about 1 second worth of log, during a 2-3-4 shift at low-ish RPM, but near wide open throttle. Worst case scenario for AE! This is about 1 second worth of log, during a 2-3-4 shift at low-ish RPM, but near wide open throttle. Worst case scenario for AE!

4
Fuel/Pages-Fuel.md
View File

@ -19,7 +19,7 @@
<details><summary><u>Acceleration</u></summary> <details><summary><u>Acceleration</u></summary>
* [Overview](Acceleration-Compensation) * [Overview](Acceleration-Compensation)
* [X-Tau Wall Wetting](X-tau_Wall_Wetting) * [X-Tau Wall Wetting](X-tau-Wall-Wetting)
* TPS. - Coming Soon * TPS. - Coming Soon
</details> </details>
@ -35,7 +35,7 @@
<details><summary><u>Fuel Hardware</u></summary> <details><summary><u>Fuel Hardware</u></summary>
* [Converting from Carb](how-to-convert-from-carburetor-to-EFI) * [Converting from Carb](how-to-convert-from-carburetor-to-EFI)
* [GDI Status](GDI_Status) * [GDI Status](./FAQ/GDI-status.md)
* [Basic Injector wiring](FAQ-Basic-Wiring-and-Connections) * [Basic Injector wiring](FAQ-Basic-Wiring-and-Connections)
* [Fuel injectors](Fuel-Injectors) * [Fuel injectors](Fuel-Injectors)

4
Hardware/PNP-Board-Disambiguation.md
View File

@ -4,7 +4,7 @@
This is our 72 pin MRE board or a Proteus based version, the info on these boards can be found below: This is our 72 pin MRE board or a Proteus based version, the info on these boards can be found below:
[MRE Version](MREAdapter72) [MRE Version](MREAdapter72)
[Proteus Version](ProteusAdaptor72.md) [Proteus Version](ProteusAdapter72)
--- ---
@ -14,4 +14,4 @@ This is the upcoming 55 pin MRE board
[MRE Version](MREAdapter55) [MRE Version](MREAdapter55)
## Miata NA ## Miata NA

6
Hardware/Pages-Hardware.md
View File

@ -30,7 +30,7 @@
* [MRE Manual](microRusEFI-Manual) * [MRE Manual](microRusEFI-Manual)
* [MRE main page](Hardware-microRusEFI) * [MRE main page](Hardware-microRusEFI)
* [MRE wiring](Hardware_microRusEFI-wiring) * [MRE wiring](Hardware-microRusEFI-wiring)
* [MRE Kit instructions](Hardware-microRusEFI-kit-instructions) * [MRE Kit instructions](Hardware-microRusEFI-kit-instructions)
* [MRE Hardware checks](Hardware-microRusEFI-hardware-checks) * [MRE Hardware checks](Hardware-microRusEFI-hardware-checks)
* [MRE DIY TLDR](microRusEFI-DIY-TLDR) * [MRE DIY TLDR](microRusEFI-DIY-TLDR)
@ -57,7 +57,7 @@
<details><summary><u>Prometheus</u></summary> <details><summary><u>Prometheus</u></summary>
* [Prometheus Overview](Hardware-Prometheus) * [Prometheus Overview](Hardware-Prometheus)
* [Prometheus wiring diagram](Prometeus-wiring-diagram.cdr) * [Prometheus wiring diagram](Hardware/Prometheus/Prometheus_wiring_diagram.cdr)
</details> </details>
@ -68,4 +68,4 @@
* [Proteus v0.2 wiring](Hardware-Proteus-Wiring-v02) * [Proteus v0.2 wiring](Hardware-Proteus-Wiring-v02)
* [Proteus v0.3 wiring](Hardware-Proteus-Wiring-v03) * [Proteus v0.3 wiring](Hardware-Proteus-Wiring-v03)
</details> </details>

4
Hardware/microrusefi/microRusEFI-Manual.md
View File

@ -10,7 +10,7 @@
[HOWTO program rusEFI using DFU](https://www.youtube.com/watch?v=VdvXYgv_acg) [HOWTO program rusEFI using DFU](https://www.youtube.com/watch?v=VdvXYgv_acg)
[See also Kit Instructions](Hardware-microRusEfi_kit_instructions) [See also Kit Instructions](Hardware-microRusEFI-kit-instructions)
## HOWTO update microRusEFI Firmware ## HOWTO update microRusEFI Firmware
@ -121,4 +121,4 @@ At this point you need to power rusEfi device off/on and new firmware version wo
New firmware version could be confirmed in rusEfi window title - both console and firmware versions are displayed there. New firmware version could be confirmed in rusEfi window title - both console and firmware versions are displayed there.
![img](Support/console_showing_firmware_version.png) ![img](Support/console_showing_firmware_version.png)

60
Hardware/microrusefi/microRusEfi_connectors/Hardware_microRusEfi_connectors.md
View File

@ -1,60 +0,0 @@
Harness donor:
US: 2007+ Nissan Altima & 2007+ Nissan Sentra
Harness side socket.
"Removable front key" style.
Left from China, Right removed from Nissan Sentra.
![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_removable_key_China_and_Nissan_harness_socket.jpg)
Removed from Nissan Sentra - square terminals.
Left large terminal. Right small pin terminal.
![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_Nissan_crimped_terminals.jpg)
PCB side: [Molex 48 pin PCB plug](https://www.mouser.com/datasheet/2/276/5007620481_PCB_HEADERS-179151.pdf) 5007620481 500762-0481
PCB side "grey": 5007620482 500762-0482 (we have not use this one so far)
PCB side "brown": 5007620483 500762-0483 (Compatible with Lada & Nissan ECU plug)
Wire cap 643201301
Harness side connector 64320-1311 or 64320-3311. Blind plugs 64325-1010 and 64325-1023.
TODO investigate Flat case option 36638-0002
From Mouser, Molex.
Left large pin 64323-1039.
Right small pin 64322-1039.
todo
"Side clip" style harness socket, both from China.
![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_side_clip_China_harness_socket.jpg)
Terminals
J-48817-232
# Lada as harness donor
Complete used harness for Lada could be acquired pretty cheap in some parts of the world. On same Lada vehicles ECU
is in the cabin (unline Nissan ECU in dirty engine bay) so we get pretty clean crimped connector with about 30 wires already in
it. The missing wires could be taken from the smaller ECU connector.
With a utility knife you need to cut 4 keys from inside the male part to mate default microRusEfi connector with a brown plug. Two center keys could be left
as is.
![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_helping_black_plug_with_brown.jpg)
![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness.jpg)

2
Technical/Launch-Control.md
View File

@ -3,4 +3,4 @@ into road racing so launch is a bit off the radar :(
See also https://rusefi.com/forum/viewtopic.php?t=871 See also https://rusefi.com/forum/viewtopic.php?t=871
See also [Feature Requests Feature Bounty Program](Feature_Requests_Feature_Bounty_Program) See also [Feature Requests Feature Bounty Program](Feature-Requests-the-Feature-Bounty-Program)

2
Technical/STM32F4Discovery-Repair.md
View File

@ -111,7 +111,7 @@ You plug discovery into a powered mini USB cable and discovery is totally dark
## Scenario: A drop of life ## Scenario: A drop of life
![Weak](Images/weak.png) ![Weak](Images/weak.jpg)
You plug discovery into a powered mini USB cable and there is bit of light on LD2 but nothing on LD1. You plug discovery into a powered mini USB cable and there is bit of light on LD2 but nothing on LD1.

2
Triggers/Trigger.md
View File

@ -28,7 +28,7 @@ Type `enable trigger_details` in rusEfi console to enable verbose synchronizatio
Enable Trigger Counters Enable Trigger Counters
![Trigger Counter in Base Engine Settings](Images/trigger_counter.png) ![Trigger Counter in Base Engine Settings](Images/trigger_counters.png)
Channel #1 counter would be "debug i1" gauge and channel #2 is "debug i2". These values should go up if you are cranking and that confirms that the events are being registered by rusEfi firmware. Channel #1 counter would be "debug i1" gauge and channel #2 is "debug i2". These values should go up if you are cranking and that confirms that the events are being registered by rusEfi firmware.

2
Vehicles/Honda-Prelude-1993.md
View File

@ -1,4 +1,4 @@
See also [Honda Accord 1995](Honda Accord 1995) See also [Honda Accord 1995](Honda-Accord-1995)
![Connector Face](Images/Honda_prelude_connector.png) ![Connector Face](Images/Honda_prelude_connector.png)

2
Vehicles/Hyundai-Accent-2001.md
View File

@ -8,6 +8,6 @@
![Wiring Diagram](Images/2001_accent_1_5_part1.png) ![Wiring Diagram](Images/2001_accent_1_5_part1.png)
![Wiring Diagram](Images/Image:2001_accent_1_5_part2.png) ![Wiring Diagram](Images/2001_accent_1_5_part2.png)
![Wiring Diagram](Images/2001_accent_1_5_part3.png) ![Wiring Diagram](Images/2001_accent_1_5_part3.png)