Fix Links (#89)
* fix hyphen links * manual fix * testing * main dir links * other dirs * fix links
This commit is contained in:
David Holdeman
GitHub
parent
c4adf16a32
commit
d07713dafb
|
|
@ -95,7 +95,7 @@ Chrysler NGC 6 cylinder
|
|||
|
||||
## Universal True 60/2
|
||||
|
||||
If you also have a CAM sensor somewhere see https://rusefi.com/wiki/index.php?title=Manual:Software:VVT
|
||||
If you also have a CAM sensor somewhere see [VVT](VVT)
|
||||
|
||||
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ Please use this one only if your CAM sensor position matches this picture exactl
|
|||
## VW 60/2
|
||||
VW special understanding of 60/2 with a wide tooth instead of of just missing tooth.
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Manual:Software:Trigger#Universal_True_60.2F2
|
||||
See also [Universal True 60/2](All-Supported-Triggers#universal-true-602)
|
||||
|
||||
|
||||
|
||||
|
|
@ -152,8 +152,7 @@ See also https://rusefi.com/wiki/index.php?title=Manual:Software:Trigger#Univers
|
|||
|
||||
## Unknown trigger type
|
||||
|
||||
Manual:Software:UnknownTrigger
|
||||
|
||||
[Unknown Trigger](Unknown-Trigger)
|
||||
|
||||
TODO: implement a feature so that trigger could be defined via TunerStudio
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Uses breakout module noted here http://rusefi.com/forum/viewtopic.php?f=4&t=454
|
|||
* Cut OEM harness for the crank angle wire(s), put the leads to the breakout module, use the fuse to simple pass the signal through the breakout module, and verify that the OEM engine is operational.
|
||||
* Connect rusEFI cam and/or crank to breakout module.
|
||||
* Install 2nd fuse to connect both OEM control unit and rusEFI. Take note that VR signals may be loaded and may be problematic at low RPM with this approach. Or it may simply work. Give it a try and see what happens. If it doesn't start with both connected, try starting the engine with rusEFI jumper removed, then after started install rusEFI jumper.
|
||||
* Capture crank signals via dev console. [http://rusefi.com/wiki/index.php?title=Manual:Software:User/en#Dev_Console dev console]
|
||||
* Capture crank signals via [dev console](Console).
|
||||
* Either configure rusEFI to use the proper crank decoder, or get a decoder developed from the dev console logs, then configure rusEFI to use the proper decoder.
|
||||
* See reliable RPM values displayed on the gauge, and noise free crank signals.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,10 +5,10 @@ rusefi firmwave currently supports two protocols for ECU monitoring & control
|
|||
1. human-readable native protocol - connect to the ECU using HyperTerminal. This used to be protocol rusEfi console was using but not any more, we are moving towards not having text protocol enabled by default.
|
||||
|
||||
|
||||
[List of commands](http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands)
|
||||
[List of commands](Dev-Console-Commands)
|
||||
|
||||
|
||||
[Java console code overview](http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_implementation)
|
||||
[Java console code overview](Dev-Console-Implementation)
|
||||
|
||||
|
||||
2. binary protocol for integration with rusEfi console or http://www.tunerstudio.com/ tuning software
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ rusEFI Console command:
|
|||
|
||||
<details><summary>More...</summary>
|
||||
|
||||
To adjust cranking fuel, use ```set cranking_fuel XXX``` command, where XXX is the number of total fuel squirt duration in milliseconds. See also http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Fuel_Control
|
||||
To adjust cranking fuel, use ```set cranking_fuel XXX``` command, where XXX is the number of total fuel squirt duration in milliseconds. See also [Console Commands - Fuel Control](Dev-Console-Commands#fuel-control)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -188,7 +188,3 @@ Typical 4 cylinder engine with 200 cc/min injectors, sequential injection, base
|
|||
|
||||
|
||||
For 1.6 Honda cranking settings see https://rusefi.com/forum/download/file.php?id=4536 (note that "base fuel" = 1 is recommended these days, with a corresponding change to cranking temperature multiplier)
|
||||
|
||||
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control#Fuel_control_during_cranking
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ It is due to these distractions (and the fact that some times out Devs also have
|
|||
|
||||
What this means is we politely request that people try not to ask easily answered questions to the Devs and keep feature requests to a minimum for now.
|
||||
|
||||
There are details of our plans for fuel strategy improvements [at this link](Roadmap_Fuel) as well as a comprehensive list of existing features and ones that are in development [here](Dev_Status)
|
||||
There are details of our plans for fuel strategy improvements [at this link](Roadmap-Fuel) as well as a comprehensive list of existing features and ones that are in development [here](Dev-Status)
|
||||
If your idea does not already appear there then consider making a Github ticket but please have a think if that feature would really add to rusEFI and if it needs to be done ASAP. If not then please tag the ticket as a future feature and low priority.
|
||||
|
||||
Most simple questions can be answered by [searching the wiki](HOWTO-Search-on-rusEFI-wiki) or by [searching the forum](https://rusefi.com/forum/search.php)
|
||||
|
|
|
|||
|
|
@ -3,4 +3,4 @@ Debug fields is an advanced troubleshooting feature allowing one to monitor the
|
|||
In TunerStudio, select "Base Engine Settings -> Debug Mode" and use the gauges from "Debug" category.
|
||||
|
||||
|
||||
See https://rusefi.com/wiki/index.php?title=Manual:Debug_fields
|
||||
See [Debug Fields](Debug-Fields)
|
||||
|
|
|
|||
|
|
@ -141,7 +141,7 @@ set fuel_pump_pin_mode: 1 parameters,
|
|||
set malfunction_indicator_pin_mode: 1 parameters,
|
||||
|
||||
## Fuel Control
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control
|
||||
See also [Fuel Overview](Fuel-Overview)
|
||||
|
||||
set_whole_fuel_map: 1 parameter: global value for the whole fuel map, in ms
|
||||
|
||||
|
|
@ -215,12 +215,10 @@ for example, `set tps_accel_multiplier 2.0` This coefficient controls how much e
|
|||
set tps_accel_threshold X
|
||||
for example, `set tps_accel_threshold 10` Ignore change below X % tps
|
||||
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control#delta.28TPS.29
|
||||
|
||||
set suckedOffCoef 0.4
|
||||
set addedToWallCoef 0.2
|
||||
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control#wall_wetting
|
||||
See [Wall Wetting](X-tau-Wall-Wetting)
|
||||
|
||||
## Timing Control
|
||||
|
||||
|
|
@ -241,7 +239,7 @@ set timing_mode: 1 parameters,
|
|||
|
||||
## Idle Control
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:Idle_control
|
||||
See also [Idle Control](Idle-Control)
|
||||
|
||||
set idle_rpm PRM
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
### This is a **DEVELOPERS** manual. For the user manual please see https://rusefi.com/wiki/index.php?title=Manual:Hardware:User/en
|
||||
### This is a **DEVELOPERS** manual. For the user manual please see [Hardware](Hardware)
|
||||
|
||||
## Summary
|
||||
This page is a general guide for hardware items and
|
||||
|
|
@ -51,13 +51,11 @@ Resistors should be listed like this 100R or 2k2
|
|||
---
|
||||
|
||||
## PCB design rules
|
||||
- See http://rusefi.com/wiki/index.php?title=Manual:Hardware:PCB_design_rules
|
||||
|
||||
- See [PCB Design Rules](PCB-Design-Rules)
|
||||
---
|
||||
|
||||
## Links to specific hardware projects
|
||||
#### - Frankenso
|
||||
http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board
|
||||
#### - [Frankenso](Hardware-Frankenso)
|
||||
|
||||
|
||||
#### - Brain board
|
||||
|
|
@ -102,13 +100,13 @@ Found in this thread [link](http://rusefi.com/forum/viewtopic.php?f=3&t=360&star
|
|||
---
|
||||
|
||||
## Misc
|
||||
http://rusefi.com/wiki/index.php?title=Manual:Hardware:CAN_sniffer
|
||||
[CAN Sniffer](CAN-Sniffer)
|
||||
|
||||
[Vehicle:Mini_Cooper_2003](https://rusefi.com/wiki/index.php?title=Vehicle:Mini_Cooper_2003)
|
||||
[Mini Cooper 2003](Mini-Cooper-2003)
|
||||
|
||||
[Vehicle:Saturn_Ion_2004](https://rusefi.com/wiki/index.php?title=Vehicle:Saturn_Ion_2004)
|
||||
[Saturn Ion 2004](Saturn-Ion-2004)
|
||||
|
||||
[Vehicle:Hyundai_Elantra_2004](https://rusefi.com/wiki/index.php?title=Vehicle:Hyundai_Elantra_2004)
|
||||
[Hyundai Elantra 2004](Hyundai-Elantra-2004)
|
||||
|
||||
[176122-6 ECU connector board](http://rusefi.com/forum/viewtopic.php?f=4&t=507)
|
||||
|
||||
|
|
@ -120,4 +118,4 @@ http://rusefi.com/wiki/index.php?title=Manual:Hardware:CAN_sniffer
|
|||
|
||||
[2003 dodge Neon test mule](https://rusefi.com/forum/viewtopic.php?f=3&t=696)
|
||||
|
||||
[Connector boards](https://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors)
|
||||
[Connector boards](OEM-Connectors)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,6 @@ We love our engines and we want them to live a long & happy life. That's why we
|
|||
|
||||
* Continuous Integration: Unit testing with [Github Actions](https://github.com/rusefi/rusefi/actions?query=workflow%3A%22Unit+Test+CI%22)
|
||||
* built-in trigger signal simulation
|
||||
* [Simulator](Virtual_simulator)
|
||||
* [Simulator](Virtual-simulator)
|
||||
|
||||
For current coverage report see https://rusefi.com/docs/unit_tests_coverage/
|
||||
|
|
|
|||
12
Download.md
12
Download.md
|
|
@ -16,16 +16,10 @@ rusEfi offers complete software download bundles for multiple supported microcon
|
|||
|
||||
[Proteus v0.2 and older (STM32F7)](https://rusefi.com/build_server/rusefi_bundle_proteus_f7.zip)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
More at https://rusefi.com/build_server/
|
||||
|
||||
# [Quick Start](HOWTO_quick_start)
|
||||
# [Quick Start](HOWTO-quick-start)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Software:Simulator
|
||||
[Choos Your Own Adventure](Try-It)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Try_It
|
||||
[Virtual Simulator](Virtual-simulator)
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ Unipolar stepper valves are not supported by any hardware variants at this time.
|
|||
|
||||
### Drive by Wire support
|
||||
|
||||
Logic exists in the firmware to control a drive by wire throttle body, including using it to idle. A single H-bridge is required to control a single DBW throttle body. Multiple DBW throttle bodies can be simultaneously controlled as long as sufficient H-bridge drivers exist to control them. A drive by wire pedal (Accelerator Pedal Position / APP) is generally used to provide input from the driver. Want to know more? here is a [HOWTO](HOWTO_electronic_throttle_body) you should read.
|
||||
Logic exists in the firmware to control a drive by wire throttle body, including using it to idle. A single H-bridge is required to control a single DBW throttle body. Multiple DBW throttle bodies can be simultaneously controlled as long as sufficient H-bridge drivers exist to control them. A drive by wire pedal (Accelerator Pedal Position / APP) is generally used to provide input from the driver. Want to know more? here is a [HOWTO](HOWTO-electronic-throttle-body) you should read.
|
||||
|
||||
|
||||
### Main Relay support
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Most more modern ignition coils are smart for these exact reasons and in order t
|
|||
## You made your point but what coils do I need?
|
||||
|
||||
That all depends if you want to buy new coils or already have some. In general we would advise to buy "smart coils" but we are also big fans of working with what you have or raiding the junk yard (read this as we are tight).
|
||||
We have attempted to compile a list of coils [here.](Vault_Of_Ignition_Parts)
|
||||
We have attempted to compile a list of coils [here.](Vault-Of-Ignition-Parts)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ Ok, this question needs tackling in several parts, please pick the option you ne
|
|||
<details><summary><u>I want to buy new coils</u></summary>
|
||||
|
||||
If you are looking to buy new coils then we would recommend taking a look at the list of Ignition coils that have been tried with rusEFI.
|
||||
[List of ignition coils](Vault_Of_Ignition_Parts)
|
||||
[List of ignition coils](Vault-Of-Ignition-Parts)
|
||||
In general though we recommend trying to get a tried and tested solution and getting coils that are easily available in your local area.
|
||||
There are lots of tried and tested options that can be found by [**searching the forum.**](https://rusefi.com/forum/search.php)
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ You will need to source an external ignition module to go between the ECU and th
|
|||
These are generally quite cheap and can be found on some cars in the junk yard. We also made our own simple module [here](fix link)
|
||||
|
||||
There are some tested Ignition modules on the Ignition components list and some can be found by [**searching the forum.**](https://rusefi.com/forum/search.php)
|
||||
[List of ignition components](Vault_Of_Ignition_Parts)
|
||||
[List of ignition components](Vault-Of-Ignition-Parts)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -83,7 +83,7 @@ These are not to be confused with the EDIS module that some ECUs require that is
|
|||
Lots of users have already had to tackle this issue so there is a host of options that can be found by [**searching the forum.**](https://rusefi.com/forum/search.php)
|
||||
|
||||
There are several available modules some are listed on the Ignition components list.
|
||||
[List of ignition components](Vault_Of_Ignition_Parts)
|
||||
[List of ignition components](Vault-Of-Ignition-Parts)
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -15,6 +15,6 @@ Testing coverage open tickets: https://github.com/rusefi/rusefi/labels/automated
|
|||
|
||||
All open tickets: https://github.com/rusefi/rusefi/issues
|
||||
|
||||
See https://rusefi.com/wiki/index.php?title=Manual:Try_It for how to work on rusEfi code with zero or minimal hardware.
|
||||
See [Try It](Try It) for how to work on rusEfi code with zero or minimal hardware.
|
||||
|
||||
[Click here for a Q&A on source code.](http://rusefi.com/forum/viewtopic.php?f=5&t=10)
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ rusEfi has auto-tuning software that can help generate a starting point for your
|
|||
### _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. It doesn't have to be perfect or super fast, 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).
|
||||
2. Set [debug mode](Debug_Mode) to ETB autotune and add gauges Ku, Tu, Kp, Ki, Kd (in debug menu) (todo: add screenshot)
|
||||
2. Set [debug mode](Debug-Mode) to ETB autotune and add gauges Ku, Tu, Kp, Ki, Kd (in debug menu) (todo: add screenshot)
|
||||
3. Using the accelerator pedal, hold the throttle at approximately 50% open.
|
||||
4. Press `ETB PID Autotune` button. The throttle will begin oscillating around the target: this is normal.
|
||||
5. Observe the estimated PID parameters on gauges Kp, Ki, Kd
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ rusEFI hardware and software have been designed to work with all three of these
|
|||
|
||||
## Configuration & Tuning
|
||||
|
||||
[See configuration guide here.](HOWTO_electronic_throttle_body_configuration)
|
||||
[See configuration guide here.](HOWTO-electronic-throttle-body-configuration)
|
||||
|
||||
## Hardware Configuration
|
||||
|
||||
|
|
|
|||
8
FSIO.md
8
FSIO.md
|
|
@ -331,8 +331,10 @@ useFSIO13ForIdleMinValue:false
|
|||
|
||||
---
|
||||
|
||||
## See aslo
|
||||
set debug_mode 23 https://rusefi.com//wiki/index.php?title=Manual:Debug_fields
|
||||
## See also
|
||||
set debug_mode 23
|
||||
|
||||
[Debug Fields](Debug-Fields)
|
||||
|
||||
https://www.youtube.com/watch?v=nrIrtdn-Nc0
|
||||
|
||||
|
|
@ -341,4 +343,4 @@ https://www.youtube.com/watch?v=eA4clVtklZ8
|
|||
---
|
||||
|
||||
## Pin naming usability issue
|
||||
We have a usability feature with microRusEfi where stm32 pin names are hidden from users. Unfortunately for FSIO these smt32 pin names are needed. Those are visible in https://github.com/rusefi/rusefi/blob/master/firmware/config/boards/microrusefi/mapping.yaml
|
||||
We have a usability feature with microRusEfi where stm32 pin names are hidden from users. Unfortunately for FSIO these smt32 pin names are needed. Those are visible in https://github.com/rusefi/rusefi/blob/master/firmware/config/boards/microrusefi/mapping.yaml
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Please see here: https://rusefi.com/wiki/index.php?title=Manual:First_engine_start
|
||||
Please see here: [HOWTO Get Running](HOWTO-Get-Running)
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ For example, Mazda distributor sensors.
|
|||
|
||||
|
||||
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Default_Pinout
|
||||
See [Frankenso Default Pinout](Hardware-Frankenso#default-pinout)
|
||||
|
||||
Use Trigger #1 N for first sensor signal & Trigger #2 N for second trigger with 1K pull-up configuration
|
||||
|
||||
|
|
@ -14,7 +14,7 @@ Leave Trigger #1 P & Trigger #2 P wires disconnected
|
|||
|
||||
## Bench testing Mazda Hall
|
||||
|
||||
Test 1.1: Expected resistance between +5v wire and Trigger #1 N wire: 1K (See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Default_Pinout)
|
||||
Test 1.1: Expected resistance between +5v wire and Trigger #1 N wire: 1K (See [Frankenso Default Pinout](Hardware-Frankenso#default-pinout))
|
||||
|
||||
Test 1.2: Expected resistance between +5v wire and Trigger #2 N wire: 1K
|
||||
|
||||
|
|
@ -22,8 +22,8 @@ Test 1.3: ground/unground Trigger #1 N wire, should see event counter in `trigge
|
|||
|
||||
Test 1.4: ground/unground Trigger #2 N wire, should see event counter in `triggerinfo` go up
|
||||
|
||||
Goto board info: http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#VR_Input
|
||||
Goto board info: [Frankenso VR Input](Hardware-Frankenso#vr-input)
|
||||
|
||||
|
||||
|
||||
PS: technically MAX9926 is not really needed for Hall processing, two channels on the op-amp would do the job just fine and Frankenso has all the jumpers provisioned to make this happen on channels #9 and #11. See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board/ru#Step_2a:_Hall_sensor_input
|
||||
PS: technically MAX9926 is not really needed for Hall processing, two channels on the op-amp would do the job just fine and Frankenso has all the jumpers provisioned to make this happen on channels #9 and #11. See [Frankenso Cam/Crank Input](Hardware-Frankenso#camcrank-input)
|
||||
|
|
|
|||
|
|
@ -23,4 +23,4 @@ Then flip the battery and hold Battery+ to Trigger #2 P and touch Battery- with
|
|||
Should see event counter in ''triggerinfo'' go up
|
||||
|
||||
|
||||
Goto board info: http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#VR_Input
|
||||
Goto board info: [Frankenso VR Input](Hardware-Frankenso#vr-input)
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Acceleration_Compensation
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control
|
||||
See also [Fuel Overview](Fuel-Overview)
|
||||
|
||||
Acceleration Compensation is required in an EFI system to modify the fuel injection to compensate for the deviation in AFR caused by the change of conditions in the inlet manifold.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,9 +18,9 @@ Once you have a plan, you can start making a bill of materials. You'll likely be
|
|||
|
||||
We should offer some notes about crimps, how to verify a good crimp, things like that.
|
||||
|
||||
[Frankenso](Hardware_Frankenso)
|
||||
[Frankenso](Hardware-Frankenso)
|
||||
|
||||
[Frankenstein](Hardware_Frankenstein)
|
||||
[Frankenstein](Hardware-Frankenstein)
|
||||
|
||||
## Preparing your engine
|
||||
|
||||
|
|
@ -92,9 +92,9 @@ Both rusEfi console and TS allows you to test if rusEfi properly controls things
|
|||
|
||||
Your tuning software should show correct cranking RPM, usually between 150 and 300 with a fully-charged battery.
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:Trigger
|
||||
See also [Trigger](Trigger)
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger
|
||||
See also [Trigger Hardware](Trigger-Hardware)
|
||||
|
||||
## Confirm TDC position
|
||||
Assuming you have the hardware ready to spark we now need to find your TDC position - we know trigger shape but we do not know the trigger wheel position in relation to TDC#1 (Top Dead Center, cylinder #1).
|
||||
|
|
@ -115,10 +115,10 @@ Engine would start rich, as long as it's not too rich, as long as you have close
|
|||
|
||||
To adjust cranking timing, use `set cranking_timing_angle XXX` command, where XXX is timing advance angle in relation to your trigger synchronization point. Please note that trigger synchronization point often does not match TDC, so just try different values between 0 and 720. For example, try 0, then 20, then 40 etc. Use `showconfig` to see current setting.
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Timing_Control
|
||||
See also [Console Timing Commands](Dev-Console-Commands#timing-control)
|
||||
|
||||
|
||||
To adjust cranking fuel, use `set cranking_fuel XXX` command, where XXX is number of total fuel squirt duration in milliseconds. See also http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Fuel_Control
|
||||
To adjust cranking fuel, use `set cranking_fuel XXX` command, where XXX is number of total fuel squirt duration in milliseconds. See also [Console Fuel Commands](Dev-Console-Commands#fuel-control)
|
||||
|
||||
## running parameters
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ For first run I suggest running based on MAF sensor - even if you do not have MA
|
|||
|
||||
To adjust running timing for your first run, use `set_whole_timing_map XXX` command, where XXX is your timing advance.
|
||||
|
||||
To adjust running fuel for your first run, use `set_whole_fuel_map XXX` command, where XXX is number of total fuel squirt duration in milliseconds. This value is usually between 3 and 12. See also http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Fuel_Control
|
||||
To adjust running fuel for your first run, use `set_whole_fuel_map XXX` command, where XXX is number of total fuel squirt duration in milliseconds. This value is usually between 3 and 12. See also [Console Fuel Commands](Dev-Console-Commands#fuel-control)
|
||||
|
||||
One plain MAF workk next step is running with proper MAP sensor calibration & flow rate setting.
|
||||
|
||||
|
|
@ -142,9 +142,9 @@ There are three ways to produce similar logs - the intention is for these three
|
|||
|
||||
See also https://svn.code.sf.net/p/rusefi/code/trunk/firmware/console/binary/tunerstudio_configuration.h
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Error_codes
|
||||
See also [Error Codes](Error-Codes)
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Debug_fields
|
||||
See also [Debug Fields](Debug-Fields)
|
||||
|
||||
## External links
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
[M73 wiring diagram](BMW_e38_750)
|
||||
[M73 wiring diagram](BMW-e38-750)
|
||||
|
||||
~6 wires are different between [Proteus 0.2](https://github.com/rusefi/rusefi/wiki/Hardware_Proteus_Wiring_v02) and [Proteus 0.3](https://github.com/rusefi/rusefi/wiki/Hardware_Proteus_Wiring_v03) - all on the 23 pin plug.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!-- this URL us hard-coded in rusEFI console splash screen MAKE SURE NOT TO RENAME -->
|
||||
|
||||
For DFU see [HOWTO_DFU](HOWTO_DFU)
|
||||
For DFU see [HOWTO-DFU](HOWTO-DFU)
|
||||
|
||||
|
||||
ST-LINK is an advanced mode of firmware update which requires ST-LINK device, either external or build-in like on Discovery/Nucleo board.
|
||||
|
|
@ -3,10 +3,10 @@
|
|||
|
||||
The weakest point of rusEfi is documentation. If you've played with rusEfi for any time chances are you have help improve the documentation.
|
||||
|
||||
[Click here for more details](HOWTO_contribute_to_documentation)
|
||||
[Click here for more details](HOWTO-contribute-to-documentation)
|
||||
|
||||
|
||||
We are also extremely short on software developers. [HOWTO_contribute_to_firmware](HOWTO_contribute_to_firmware)
|
||||
We are also extremely short on software developers. [HOWTO-contribute-to-firmware](HOWTO-contribute-to-firmware)
|
||||
|
||||
|
||||
## Please do good and do not do bad
|
||||
|
|
|
|||
|
|
@ -4,8 +4,8 @@
|
|||
|
||||
Slack in a group messenger that can be accessed through your browser or as an application on your PC.
|
||||
|
||||
Before joining slack please read the section on [asking questions.](HOWTO_ask_questions)
|
||||
Please also read the section [Here.](D_is_for_DISTRACTION)
|
||||
Before joining slack please read the section on [asking questions.](HOWTO-ask-questions)
|
||||
Please also read the section [Here.](D-is-for-DISTRACTION)
|
||||
|
||||
#### Joining the channel
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@
|
|||
|
||||
## rusEfi Console
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Manual:Software:Console
|
||||
[Console](Console)
|
||||
|
||||
We have rusEfi console which is a handy development and debugging tool. The dev console is written in java and it talks to the ECU firmware. The console allows firmware monitoring and configuration. Here are some pictures of what it looks like when it operating correctly.
|
||||
|
||||
|
|
@ -44,7 +44,7 @@ We have rusEfi console which is a handy development and debugging tool. The dev
|
|||
To get the console working follow the below procedure, which assumes you have loaded the rusEFI firmware.
|
||||
|
||||
* Either power externally, or connect the "programming" USB cable as shown below. This will provide power to the Discovery board.
|
||||
* Connect the micro USB cable, see "console" cable shown below. When you do this for the first time, on a Windows PC, you will be prompted for drivers. You should download & install the drivers from here http://www.st.com/web/en/catalog/tools/PF257938. #: http://rusefi.com/wiki/images/thumb/0/06/RusEFI_STM.jpg/800px-RusEFI_STM.jpg
|
||||
* Connect the micro USB cable, see "console" cable shown below. When you do this for the first time, on a Windows PC, you will be prompted for drivers. You should download & install the drivers from here http://www.st.com/web/en/catalog/tools/PF257938. #: 
|
||||
* When the driver is installed & the board is connected via the micro USB cable, you can verify serial connectivity by
|
||||
* '''Windows''' - opening your Device Manager - we are expecting to see a Virtual COM Port
|
||||
* http://rusefi.com/images/forum_posts/device_manager.png
|
||||
|
|
@ -81,9 +81,9 @@ At this point, the Dev Console should be up and running. Play around with it and
|
|||
|
||||
## Tuner Studio
|
||||
|
||||
[HOWTO create TunerStudio project](HOWTO_create_tunerstudio_project)
|
||||
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project)
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_connectivity
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
|
||||
|
||||
## Power via 12V supply
|
||||
|
||||
|
|
@ -104,11 +104,11 @@ See also http://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_conn
|
|||
|
||||
## Tuning the engine
|
||||
|
||||
[Get Running](HOWTO-Get-Running)
|
||||
|
||||
[Get Tuning](Get-tuning-with-TunerStudio-and-your-rusEFI)
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:First_engine_start
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Error_codes
|
||||
[Error Codes](Error-Codes)
|
||||
|
||||
## Prerequisites
|
||||
This section assumes
|
||||
|
|
@ -157,10 +157,10 @@ TBD
|
|||
Once it's working well and reacts well to quick changes in the long pedal, you'll want cold temperature enrichments such that it starts nice and easy.
|
||||
TBD
|
||||
|
||||
see also [http://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control Fuel Control]
|
||||
see also [http://rusefi.com/wiki/index.php?title=Manual:Software:Ignition_Control]
|
||||
see also [http://rusefi.com/wiki/index.php?title=Manual:Software:Idle_control]
|
||||
see also [http://rusefi.com/forum/viewtopic.php?f=2&t=1124&p=21278]
|
||||
see also [Fuel Overview](Fuel-Overview)
|
||||
see also [Ignition](Ignition)
|
||||
see also [Idle Control](Idle-Control)
|
||||
see also http://rusefi.com/forum/viewtopic.php?f=2&t=1124&p=21278
|
||||
|
||||
## Share your tune
|
||||
|
||||
|
|
@ -205,11 +205,11 @@ I'd like to try to connect to Tuner Studio and see what happens. I have a USB/TT
|
|||
|
||||
This UART/real serial is just another way to connect either TunerStudio or rusEfi console to the firmware. By combining both microUsb virtual serial and TTL real serial one can connect to rusEfi with both TunerStudio and rusEfi console simultaneously.
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_connectivity
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
|
||||
|
||||
## rusEfi firmware
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Manual:Software:Trigger
|
||||
[Trigger](Trigger)
|
||||
|
||||
## LEDs
|
||||
|
||||
|
|
@ -228,14 +228,14 @@ orange LED: warning: blinking in case of trigger input decoding warning or other
|
|||
### Communication mode
|
||||
microUSB channel is more sensitive to noise but it's faster
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_connectivity
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
|
||||
|
||||
### Configuration reset
|
||||
Grounding PD6 resets saved configuration to default state - see http://rusefi.com/forum/viewtopic.php?f=5&t=373&p=9571&hilit=PD6#p9571
|
||||
|
||||
### Board Testing mode
|
||||
|
||||
Grounding PB0 enables board testing mode. See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Test_Mode
|
||||
Grounding PB0 enables board testing mode. See [Hardware Test Mode](Hardware-Test-Mode)
|
||||
|
||||
## FAQ
|
||||
Q: How do I change settings? Would I need to compile source code?
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Proteus v0.2 Pinout & Wiring
|
||||
|
||||
## _NOTE: this pinout only applies to boards v0.2 and older (probably black). [If you have v0.3 or newer (green), then use the pinout found here!](Hardware_Proteus_Wiring_v03)_
|
||||
## _NOTE: this pinout only applies to boards v0.2 and older (probably black). [If you have v0.3 or newer (green), then use the pinout found here!](Hardware-Proteus-Wiring-v03)_
|
||||
|
||||
## Black 35 Pin 776231-1
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Proteus v0.3 Pinout & Wiring
|
||||
|
||||
## _NOTE: this pinout only applies to boards v0.3 and newer (green). [If you have v0.2 or older (probably black), then use the pinout found here!](Hardware_Proteus_Wiring_v02)_
|
||||
## _NOTE: this pinout only applies to boards v0.3 and newer (green). [If you have v0.2 or older (probably black), then use the pinout found here!](Hardware-Proteus-Wiring-v02)_
|
||||
|
||||
## Black 35 Pin 776231-1
|
||||
|
||||
|
|
|
|||
|
|
@ -3,12 +3,12 @@ This page is dedicated to my experience with Frankenso 0.5 board, especially man
|
|||
## Prerequisites
|
||||
|
||||
Mandatory links:
|
||||
[Frankenso Hardware](Hardware_Frankenso)
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Hardware_Test_Mode<br>
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_connectivity<br>
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#step_3:_Analog_Inputs<br>
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger<br>
|
||||
https://rusefi.com/wiki/index.php?title=Manual:Software_Temperature_Sensors<br>
|
||||
[Frankenso Hardware](Hardware-Frankenso)
|
||||
[Hardware Test Mode](Hardware-Test-Mode)
|
||||
[TunerStudio Connectivity](Tunerstudio-Connectivity)
|
||||
[Frankenstein Analog Inputs](Hardware-Frankenstein#step-3-analog-inputs)
|
||||
[Trigger Hardware](Trigger-Hardware)
|
||||
[Temperature Sensing](Temperature-Sensing)
|
||||
https://docs.google.com/spreadsheets/d/1LTvS7I-128Hft9uXHG1JrBxetVjGJDSBkySgVDQ6MGk/edit#gid=0
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Frankenso should be powered by ignition switch. Frankenso main relay output can
|
|||
|
||||
[For sale fully assembled!](https://www.tindie.com/products/russian/frankenso-full-bundle/)
|
||||
|
||||
See [HOWTO Quick Start](HOWTO_quick_start) for rusEfi Quick Start.
|
||||
See [HOWTO Quick Start](HOWTO-quick-start) for rusEfi Quick Start.
|
||||
|
||||
[Known Issues](https://raw.githubusercontent.com/rusefi/rusefi/master/hardware/frankenso/known_issues.txt)
|
||||
|
||||
|
|
@ -54,23 +54,23 @@ See also [online BOM](https://rusefi.com/docs/ibom/frankenso_latest.html)
|
|||
|
||||
## Default Pinout
|
||||
|
||||
Frankenso was designed with Mazda Miata NA pinout in mind. The most easily available ECU harness pig tail comes from OBD-I Honda vehicles, different Honda vehicles use slightly different harness colors so the values given are pretty approximate, please use common sense. See connector details @ http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#64_pin
|
||||
Frankenso was designed with Mazda Miata NA pinout in mind. The most easily available ECU harness pig tail comes from OBD-I Honda vehicles, different Honda vehicles use slightly different harness colors so the values given are pretty approximate, please use common sense. See connector details [here](OEM-connectors#64-pin)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1991
|
||||
See also [Mazda Miata 1991](Mazda-Miata-1991)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1994
|
||||
See also [Mazda Miata 1994](Mazda-Miata-1994)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1999
|
||||
See also [Mazda Miata 1999](Mazda-Miata-1999)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Honda_Accord_1995
|
||||
See also [Honda Accord 1995](Honda-Accord-1995)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2003
|
||||
See also [Mazda Miata 2003](Mazda-Miata-2003)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2003_alt
|
||||
See also [Mazda Miata 2003 alt](Mazda-Miata-2003-alt)
|
||||
|
||||
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger
|
||||
See also [Trigger Hardware](Trigger-Hardware)
|
||||
|
||||
Here is a video about how to chang these "Honda obd1 ecu" connector pins. It has also been found that the second stage release can be done with a flat hair clips can be used from the back side of the connector to release the pin.
|
||||
|
||||
|
|
@ -140,11 +140,11 @@ PE1 was replaced with PD3
|
|||
|
||||
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:Fuel_Control
|
||||
See also [Fuel Overview](Fuel-Overview)
|
||||
|
||||
## VR Input
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger
|
||||
See also [Trigger Hardware](Trigger-Hardware)
|
||||
|
||||
|
||||
|
||||
|
|
@ -187,9 +187,9 @@ These chips could be configured to run 5v, 12v or GND output:
|
|||
|
||||
## Analog Inputs
|
||||
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#step_3:_Analog_Inputs
|
||||
See [Frankenstein Analog Inputs](Hardware-Frankenstein#step-3-analog-inputs)
|
||||
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Software_Temperature_Sensors
|
||||
See [Temperature Sensing](Temperature-Sensing)
|
||||
|
||||
https://docs.google.com/spreadsheets/d/1LTvS7I-128Hft9uXHG1JrBxetVjGJDSBkySgVDQ6MGk
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ Our op-amp of choice is MCP6004-E/SL
|
|||
|
||||
## Knock Sensor Decoder
|
||||
|
||||
[Knock Sensing](knock_sensing)
|
||||
[Knock Sensing](knock-sensing)
|
||||
|
||||
|
||||
|
||||
|
|
@ -243,7 +243,7 @@ C354 & C358 are 4.7uF
|
|||
C355, C356 and C357 are 0.1uF (same thing as 100nF)
|
||||
|
||||
## SD card socket
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Software:logging
|
||||
See [Logging](Logging)
|
||||
|
||||
|
||||
## EGT
|
||||
|
|
|
|||
|
|
@ -7,10 +7,10 @@ As of March 2020 Frankenso board is sold as mostly as a DIY kit.
|
|||
|
||||
| Board | Features | Connectors/Misc. Info | Released in | Maximum recommended engine |
|
||||
| ----- | -------- | --------------------- | ----------- | ---------------------------|
|
||||
| [Frankenso](Hardware_Frankenso) | + Most customizable board<br/>+ larger 154x152mm 4-layer board requires a Medium Box shipping rate<br/>+ on-board power supply<br/>+ 20x4 LCD screen<br/>+ joystick<br/>+ works both with external brain boards and on-board stm32 chip<br/>+ knock sensor chip<br/>+ used Denso OEM cases available | on-board 64 pin connector<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended |
|
||||
| [Frankenso](Hardware-Frankenso) | + Most customizable board<br/>+ larger 154x152mm 4-layer board requires a Medium Box shipping rate<br/>+ on-board power supply<br/>+ 20x4 LCD screen<br/>+ joystick<br/>+ works both with external brain boards and on-board stm32 chip<br/>+ knock sensor chip<br/>+ used Denso OEM cases available | on-board 64 pin connector<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended |
|
||||
| [Prometheus](https://rusefi.com/forum/viewtopic.php?f=4&t=1215) | + The only rusEfi board with on-board wide band controller.<br/>+ compact 4-layer PCB smaller than 93 x 100 mm<br/>+ on-board power supply<br/>+ knock sensor chip<br/>+ stepper motor IAC controller chip<br/>+ stepper motor IAC controller chip<br/>+ onboard 4-channel "smart" protected ignition drivers<br/>+ bluetooth module<br/>+ supports two packages of on-board stm32 chips | no on-board connector (wired)<br/>SD card, USB/TTL, CAN | 2017 | 4 cylinder. No plans to offer assembled units. |
|
||||
| [Frankenstein](https://rusefi.com/forum/viewtopic.php?f=4&t=359) | + Simplest rusEfi board<br/>+ our smaller two-layer board<br/>+ Small Box shipping rate<br/>+ low price<br/>- external 5v power supply required<br/>- external brain board required | no on-board connector (wired)<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. |
|
||||
| [microRusEfi](Hardware_microRusEfi) | + Available fully assembled!<br/>+ about 10 analog inputs<br/>+ One VR/Hall input channel for crank sensor<br/>+ One Hall input channel for crank sensor<br/>+ 4 injector output channels<br/>+ 4 logic level coil control channels (external igniters could be needed for some coils) | 48-pin connector<br/>On-board DBW<br/>USB, CAN<br/>open source hardware | 2019 | 4 cylinder, single electronic throttle |
|
||||
| [microRusEfi](Hardware-microRusEfi) | + Available fully assembled!<br/>+ about 10 analog inputs<br/>+ One VR/Hall input channel for crank sensor<br/>+ One Hall input channel for crank sensor<br/>+ 4 injector output channels<br/>+ 4 logic level coil control channels (external igniters could be needed for some coils) | 48-pin connector<br/>On-board DBW<br/>USB, CAN<br/>open source hardware | 2019 | 4 cylinder, single electronic throttle |
|
||||
| [Hellen](https://rusefi.com/forum/viewtopic.php?f=4&t=1682) | Coming soon! | modular design| 2020 | TBD cylinder, single electronic throttle |
|
||||
| [Proteus](Proteus) | + rusEfi if you have lots of hardware or cylinders<br/>+ 4 layer PCB, 135mm x 82.5mm<br/>+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)<br/>+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)<br/>+ Dual electronic throttles<br/>+ 4x High-side 12v drivers, 1 amp each<br/>+ 4 thermistor analog inputs (2.7k pull up resistor)<br/>+ 12 General purpose analog inputs<br/>+ Dual VR sensors (crank position, wheel speed)<br/>+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin<br/>rusEfi's most fully-featured shield<br/>IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles |
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ Frankenso supports up to 2 VR or 2 Hall shaft position sensors. Prometheus suppo
|
|||
|
||||
### Q: why stm32?
|
||||
|
||||
A: [selecting_open_source_ecu_microcontroller](selecting_open_source_ecu_microcontroller)
|
||||
A: [selecting-open-source-ecu-microcontroller](selecting-open-source-ecu-microcontroller)
|
||||
|
||||
|
||||
### Q: This is all very cool but you guys do not have a Plug&Play for my Trabant. I think I will go and make a new rusEFI board just for my Trabant!
|
||||
|
|
@ -45,8 +45,6 @@ If you proceed then please consider making a P&P adapter board design based on H
|
|||
|
||||
A: rusEFI preference at the moment is KiCad 5. A few legacy pieces are still using KiCad 4. While many EDAs have many cool features KiCad gives rusEFI uniformity and consistency.
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Hardware:Boards_Comparison
|
||||
|
||||
See also https://github.com/rusefi/rusefi/tree/master/hardware
|
||||
|
||||
### Q: What pin do I use for tachometer output?
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Disclaimer: the following observations could be really wrong, please let me know if you have better information.
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#121_pin
|
||||
See also [OEM Connectors - 121 pin](OEM-connectors#121-pin)
|
||||
|
||||
|
||||
There are two kinds of 121 connectors which look pretty much the same but do not mate together unless you use a grinder to massage them a bit.
|
||||
|
|
@ -11,7 +11,7 @@ http://www.te.com/catalog/pn/en/368255-2
|
|||
|
||||
This one is used on Asian vehicles - Kia Hyundai etc.
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Vehicle:Kia_Spectra_2005
|
||||
See also [Kia Spectra 2005](Kia-Spectra-2005)
|
||||
|
||||
|
||||
|
||||
|
|
@ -58,8 +58,8 @@ There is also a 115 pin version - 6 pins are left out (14, 15, 16, 33, 34, 35)
|
|||
|
||||
## pinouts
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Kia_Spectra_2005
|
||||
[Kia Spectra 2005](Kia-Spectra-2005)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mini_Cooper_2003
|
||||
[Mini-Cooper-2003](Mini-Cooper-2003)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Nissan_Xterra_2011
|
||||
[Nissan Xterra 2011](Nissan-Xterra-2011)
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ See also https://www.te.com/commerce/DocumentDelivery/DDEController?Action=showd
|
|||
http://www.te.com/catalog/pn/en/174917-6
|
||||
Escort GT, Ford Festiva, Miata NA6 manual
|
||||
|
||||
The larger plugs are the same as on http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#64_pin
|
||||
The larger plugs are the same as on [the 64 pin](OEM-connectors#64-pin).
|
||||
|
||||
## 52 pin
|
||||
http://www.te.com/usa-en/product-172319-1.html
|
||||
|
|
@ -174,7 +174,7 @@ terminal 173681
|
|||
|
||||
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#48_pin
|
||||
See also [the 48 pin](OEM-connectors#48-pin).
|
||||
|
||||
For sale @ http://www.ebay.com/usr/rusefi
|
||||
|
||||
|
|
@ -211,8 +211,7 @@ http://www.te.com/catalog/pn/en/1123038-2
|
|||
|
||||
|
||||
|
||||
Oem ECU Miata 2001 - 2005
|
||||
http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2001
|
||||
Oem ECU [Miata 2001 - 2005](Mazda-Miata-2001)
|
||||
|
||||
pins 316836
|
||||
|
||||
|
|
@ -315,7 +314,7 @@ Currently used by Nissan, Hyundai and Kia. Also Audi, VW and Mini Cooper
|
|||
|
||||
2003 VW Passat
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_121_pin_connectors
|
||||
[121 pin main page](OEM-121-pin-connectors)
|
||||
|
||||
## 122 pin
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ All microRusEfi kits use [MRE F4 rusEfi firmware - DOWNLOAD LATEST BUNDLE HERE](
|
|||
|
||||
|
||||
|
||||
[Wiring Diagram](Hardware_microRusEfi_wiring)
|
||||
[Wiring Diagram](Hardware-microRusEfi-wiring)
|
||||
|
||||
[0.5.0 schematics PDF](https://github.com/rusefi/hw_microRusEfi/blob/master/micro_rusEFI_Schematic_0_5_0.pdf)
|
||||
|
||||
|
|
@ -49,7 +49,7 @@ All microRusEfi kits use [MRE F4 rusEfi firmware - DOWNLOAD LATEST BUNDLE HERE](
|
|||
|
||||
[rusEfi Slack channel](https://rusefi.com/forum/viewtopic.php?f=13&t=1198) is the primary support channel.
|
||||
|
||||
[HOWTO program rusEfi using DFU](HOWTO_DFU)
|
||||
[HOWTO program rusEfi using DFU](HOWTO-DFU)
|
||||
|
||||
# Crankshaft position sensor options: Hall or VR
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
microRusEFI is a highly integrated board version of the rusEFI ECU. The microRusEFI ECU is targeted at port-injected
|
||||
gasoline engines up to 4 cylinders.
|
||||
|
||||
[Connector Pinout](Hardware_microRusEfi_wiring)
|
||||
[Connector Pinout](Hardware-microRusEfi-wiring)
|
||||
|
||||
The latest schematics for the microRusEFI ECU are available at https://github.com/rusefi/hw_microRusEfi/blob/master/microRusEfi_Schematic.pdf
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ A complete set of board source files is available at https://github.com/rusefi/h
|
|||
* CAN connectivity on the plug
|
||||
* USB connectivity on the plug
|
||||
|
||||
[Connector Pinout](Hardware_microRusEfi_wiring)
|
||||
[Connector Pinout](Hardware-microRusEfi-wiring)
|
||||
|
||||
|
||||
|
||||
|
|
@ -39,4 +39,4 @@ Q: How about 6 cylinders sequential on microRusEFI?
|
|||
|
||||
A: The microRusEFI ECU is primarily a 4 cylinder ECU. At this time the testing for safety, reliable control, and consistency have not been completed for running the microRusEFI ECU on a 6 cylinder engine. This is something that we are working on and could be added at a future point.
|
||||
|
||||
[See also Kit Instructions](Hardware_microRusEfi_kit_instructions)
|
||||
[See also Kit Instructions](Hardware-microRusEfi-kit-instructions)
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
# microRusEfi User Documentation
|
||||
|
||||
[rusEfi Hardware](Hardware_microRusEfi)
|
||||
[rusEfi Hardware](Hardware-microRusEfi)
|
||||
|
||||
[rusEfi wiring](Hardware_microRusEfi_wiring)
|
||||
[rusEfi wiring](Hardware-microRusEfi_wiring)
|
||||
|
||||
[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
|
||||
|
|
|
|||
8
Home.md
8
Home.md
|
|
@ -19,15 +19,15 @@ Feature|Supported?
|
|||
-------|----------
|
||||
Batch Injection|✓
|
||||
Sequential Injection up to 12 cylinders|✓
|
||||
[Direct Injection](GDI_status)|✗
|
||||
[Direct Injection](GDI-status)|✗
|
||||
Wasted Ignition|✓
|
||||
Sequential Ignition up to 12 cylinders|✓
|
||||
Rotary Engines|✗
|
||||
Closed Loop Fueling|✓
|
||||
Electronic Throttle Body|✓
|
||||
[Knock Sensing](knock_sensing)|✗
|
||||
[Knock Sensing](knock-sensing)|✗
|
||||
Boost Control|✗
|
||||
[Launch Control](Launch_Control)|✗
|
||||
[Launch Control](Launch-Control)|✗
|
||||
Flat Shifting|✗
|
||||
Automatic Transmission Control|✗
|
||||
[Acceleration enrichment - wall wetting/fuel trip/tau factor](wall_wetting)|✓
|
||||
|
|
@ -48,7 +48,7 @@ So you are thinking of doing an engine control project. You have stopped by the
|
|||
|
||||
## rusEFI in action!
|
||||
|
||||
[Engines running rusEFI](List_of_engines_running_rusEfi)
|
||||
[Engines running rusEFI](List-of-engines-running-rusEfi)
|
||||
|
||||
### [](https://www.youtube.com/embed/3xz66oR95F8?start=8 "Miata rusEFI Racecar!")
|
||||
|
||||
|
|
|
|||
|
|
@ -3,6 +3,6 @@
|
|||
A: Let me answer this universal question with a universal answer, in two parts:
|
||||
|
||||
1) shortage of available resources (mostly software developers and testers)
|
||||
2) how can you help with this proposal or [in general](HOWTO_help_rusEfi)?
|
||||
2) how can you help with this proposal or [in general](HOWTO-help-rusEfi)?
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
rusEfi supports both solenoid-type IAC out of the box (well, with a fly-back diode - 1 or two wire) and http://rusefi.com/wiki/index.php?title=Hardware:Stepper_motor (4 to six wires, add-on board from eBay required)
|
||||
rusEfi supports both solenoid-type IAC out of the box (well, with a fly-back diode - 1 or two wire) and [stepper motors](Stepper-Motor) (4 to six wires, add-on board from eBay required)
|
||||
|
||||
|
||||
By default Idle control is in 'manual' mode, while in manual mode you can control the idle valve with
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 946 KiB |
|
|
@ -14,14 +14,13 @@ microRusEFI should be set for Hall
|
|||
[Schematics 0.1](https://github.com/rusefi/rusefi_documentation/raw/master/Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0.1.pdf)
|
||||
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1990
|
||||
[Mazda Miata 1990](Mazda-Miata-1990)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1991
|
||||
[Mazda Miata 1991](Mazda-Miata-1991)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1994
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1995
|
||||
[Mazda Miata 1994](Mazda-Miata-1994)
|
||||
|
||||
[Mazda Miata 1995](Mazda-Miata-1995)
|
||||
|
||||
[InteractiveBOM 0.2](https://rusefi.com/docs/ibom/hw48na_V0.2.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
|
||||
Mazda Miata MX5 NB2 2001-2005 Standalone
|
||||
|
||||
[microRusEFI](Hardware_microRusEfi) should be set for Hall
|
||||
[microRusEFI](Hardware-microRusEfi) should be set for Hall
|
||||
|
||||
High-side jumper should be set for +12v.
|
||||
|
||||
[Some versions of Miata may need a jumper set on the board, See detail here](PNP_72_Jumpers)
|
||||
[Some versions of Miata may need a jumper set on the board, See detail here](PNP-72-Jumpers)
|
||||
|
||||
https://rusefi.com/forum/viewtopic.php?t=1677
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2002
|
||||
[Mazda Miata 2002](Mazda-Miata-2002)
|
||||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2003
|
||||
[Mazda Miata 2003](Mazda-Miata-2003)
|
||||
|
||||
|
||||
|
||||
|
|
@ -72,7 +72,7 @@ The following I/O is available. A jumper wire will need to be routed between the
|
|||
| J1 | PB9 |
|
||||
| J2 | PC12 |
|
||||
|
||||
Extra pins for [353830-5 72 pin](https://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#72_pin):
|
||||
Extra pins for [353830-5 72 pin](OEM-connectors#72-pin):
|
||||
|
||||
TE 316836-1 for 20 AWG to 22 AWG
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2002
|
||||
https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2003
|
||||
[Mazda Miata 2002](Mazda-Miata-2002)
|
||||
[Mazda Miata 2003](Mazda-Miata-2003)
|
||||
|
||||
|
||||
For remote start button three wires are needed:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This is a PNP adapter board for NA Miatas (1990-1995). The board is true plug and play. Just replace the PCB in your ECU with this board and drive the car. The hardware capabilities are defined by the [microRuseEFI](Hardware_microRusEfi) module that drives the unit.
|
||||
This is a PNP adapter board for NA Miatas (1990-1995). The board is true plug and play. Just replace the PCB in your ECU with this board and drive the car. The hardware capabilities are defined by the [microRuseEFI](Hardware-microRusEfi) module that drives the unit.
|
||||
|
||||
Your board should look something like this: 
|
||||
|
||||
|
|
|
|||
12
Miata.md
12
Miata.md
|
|
@ -14,7 +14,7 @@ Listed for sale with early June deliveries.
|
|||
|
||||
[Frankenso](Frankenso) could be set for this pinout using a few dozen jumper wires in the wiring breakout area.
|
||||
|
||||
As of May 2020 [Proteus](Proteus) or [Hardware_microRusEfi](Hardware_microRusEfi) could be wired
|
||||
As of May 2020 [Proteus](Proteus) or [Hardware-microRusEfi](Hardware-microRusEfi) could be wired
|
||||
using [breakout board](https://www.ebay.com/itm/64-pin-ECU-connector-civic-mazda-mx-5-eunos-miata-toyota-with-breakout-PCB/332771650527)
|
||||
|
||||
One day we plan to have a microRusEFI adapter for these cars maybe in August 2020?
|
||||
|
|
@ -23,7 +23,7 @@ One day we plan to have a microRusEFI adapter for these cars maybe in August 202
|
|||
# Early NB
|
||||
NB1 1999-2000 while connector still looks similar that's another different pinout.
|
||||
|
||||
As of May 2020 [Proteus](Proteus) or [Hardware_microRusEfi](Hardware_microRusEfi) could be wired
|
||||
As of May 2020 [Proteus](Proteus) or [Hardware-microRusEfi](Hardware-microRusEfi) could be wired
|
||||
using [breakout board](https://www.ebay.com/itm/64-pin-ECU-connector-civic-mazda-mx-5-eunos-miata-toyota-with-breakout-PCB/332771650527)
|
||||
|
||||
One day we plan to have a microRusEFI adapter for these cars maybe in August 2020?
|
||||
|
|
@ -35,11 +35,7 @@ NB2 2001-2005
|
|||
|
||||
# Other links
|
||||
|
||||
See also [Frankenso NA6 PnP](Frankenso-MazdaMiataNA6-pnp)
|
||||
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Manual:Hardware:Mazda_PnP
|
||||
|
||||
See also https://github.com/rusefi/rusefi/wiki/Frankenso_MazdaMiataNA6_pnp
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
|
||||
See [HOWTO set rusEfi Online authentication token](HOWTO-set-rusEfi-Online-authentication-token)
|
||||
|
||||
See [HOWTO upload tune](HOWTO_upload_tune)
|
||||
See [HOWTO upload tune](HOWTO-upload-tune)
|
||||
|
||||
See [HOWTO Remote Tuning](https://github.com/rusefi/rusefi/wiki/HOWTO-Remote-Tuning)
|
||||
|
||||
|
|
|
|||
|
|
@ -2,22 +2,22 @@
|
|||
|
||||
<details><summary><u>FAQs</u></summary>
|
||||
|
||||
* [Ignition](FAQ_Ignition)
|
||||
* [Ignition](FAQ-Ignition)
|
||||
* [Basic Wiring and Connections](FAQ-Basic-Wiring-and-Connections)
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary><u>HOWTOs</u></summary>
|
||||
|
||||
* [Asking Questions](HOWTO_ask_questions)
|
||||
* [Contributing to Documentation](HOWTO_contribute_to_documentation)
|
||||
* [Create a TunerStudio Project](HOWTO_create_tunerstudio_project)
|
||||
* [Direct Firmware Update](HOWTO_DFU)
|
||||
* [Help rusEFI](HOWTO_help_rusEfi)
|
||||
* [Join Slack](HOWTO_join_slack_channel)
|
||||
* [Quick Start](HOWTO_quick_start)
|
||||
* [Update Firmware](HOWTO_Update_Firmware)
|
||||
* [Upload a Tune](HOWTO_upload_tune)
|
||||
* [Asking Questions](HOWTO-ask-questions)
|
||||
* [Contributing to Documentation](HOWTO-contribute-to-documentation)
|
||||
* [Create a TunerStudio Project](HOWTO-create-tunerstudio-project)
|
||||
* [Direct Firmware Update](HOWTO-DFU)
|
||||
* [Help rusEFI](HOWTO-help-rusEfi)
|
||||
* [Join Slack](HOWTO-join-slack-channel)
|
||||
* [Quick Start](HOWTO-quick-start)
|
||||
* [Update Firmware](HOWTO-Update-Firmware)
|
||||
* [Upload a Tune](HOWTO-upload-tune)
|
||||
* [Search the Wiki](HOWTO-Search-on-rusEFI-wiki)
|
||||
* [Online Authorisation Tokens](HOWTO-set-rusEfi-Online-authentication-token)
|
||||
|
||||
|
|
|
|||
|
|
@ -8,17 +8,17 @@
|
|||
|
||||
<details><summary><u>Fuel Algorithms</u></summary>
|
||||
|
||||
* [Fuel Overview](Fuel_Overview)
|
||||
* [Fuel Overview](Fuel-Overview)
|
||||
* [Cranking](Cranking)
|
||||
* [AlphaN](AlphaN)
|
||||
* [Speed Density](Speed_Density)
|
||||
* [Speed Density](Speed-Density)
|
||||
* [Mass Air Flow](MAF)
|
||||
|
||||
</details>
|
||||
|
||||
<details><summary><u>Acceleration</u></summary>
|
||||
|
||||
* [Overview](Acceleration_Compensation)
|
||||
* [Overview](Acceleration-Compensation)
|
||||
* [X-Tau Wall Wetting](X-tau_Wall_Wetting)
|
||||
* TPS. - Coming Soon
|
||||
|
||||
|
|
@ -26,15 +26,15 @@
|
|||
|
||||
<details><summary><u>AFR measurement</u></summary>
|
||||
|
||||
* [Wide Band Sensors](Wide_Band_Sensors)
|
||||
* [Do I need a wideband](do_i_need_wideband_oxygen_sensor)
|
||||
* [Wide Band Sensors](Wide-Band-Sensors)
|
||||
* [Do I need a wideband](do-i-need-wideband-oxygen-sensor)
|
||||
* [Old WBO2 page](WBO)
|
||||
|
||||
</details>
|
||||
|
||||
<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)
|
||||
* [Basic Injector wiring](FAQ-Basic-Wiring-and-Connections)
|
||||
* [Fuel injectors](Fuel-Injectors)
|
||||
|
|
|
|||
|
|
@ -2,16 +2,16 @@
|
|||
|
||||
<details><summary><u>HOW TO</u></summary>
|
||||
|
||||
* [Ask questions](HOWTO_ask_questions.md)
|
||||
* [Contribute to documentation](HOWTO_contribute_to_documentation.md)
|
||||
* [Create a tunerstudio project](HOWTO_create_tunerstudio_project.md)
|
||||
* [DFU](HOWTO_DFU.md)
|
||||
* [Get running](HOWTO_Get_Running.md)
|
||||
* [Help out](HOWTO_help_rusEfi.md)
|
||||
* [Join Slack](HOWTO_join_slack_channel.md)
|
||||
* [Quick Start](HOWTO_quick_start.md)
|
||||
* [Update firmware](HOWTO_Update_Firmware.md)
|
||||
* [Upload a tune](HOWTO_upload_tune.md)
|
||||
* [Ask questions](HOWTO-ask-questions.md)
|
||||
* [Contribute to documentation](HOWTO-contribute-to-documentation.md)
|
||||
* [Create a tunerstudio project](HOWTO-create-tunerstudio-project.md)
|
||||
* [DFU](HOWTO-DFU.md)
|
||||
* [Get running](HOWTO-Get-Running.md)
|
||||
* [Help out](HOWTO-help-rusEfi.md)
|
||||
* [Join Slack](HOWTO-join-slack-channel.md)
|
||||
* [Quick Start](HOWTO-quick-start.md)
|
||||
* [Update firmware](HOWTO-Update-Firmware.md)
|
||||
* [Upload a tune](HOWTO-upload-tune.md)
|
||||
* [Remote tune](HOWTO-Remote-Tuning.md)
|
||||
* [Search the wiki](HOWTO-Search-on-rusEFI-wiki.md)
|
||||
* [Set rusEfi Online authentication token](HOWTO-set-rusEfi-Online-authentication-token.md)
|
||||
|
|
|
|||
|
|
@ -5,23 +5,23 @@
|
|||
|
||||
<details><summary><u>Universal Info</u></summary>
|
||||
|
||||
* [Hardware completeness options](Completeness_Chart)
|
||||
* [Microcontroller selection](selecting_open_source_ecu_microcontroller)
|
||||
* [Hardware development guidelines](Dev_Hardware_Guidelines)
|
||||
* [Hardware completeness options](Completeness-Chart)
|
||||
* [Microcontroller selection](selecting-open-source-ecu-microcontroller)
|
||||
* [Hardware development guidelines](Dev-Hardware-Guidelines)
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details><summary><u>Deucalion</u></summary>
|
||||
|
||||
* [Deucalion UART](Deucalion_uart)
|
||||
* [Deucalion UART](Deucalion-uart)
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details><summary><u>Frankenso</u></summary>
|
||||
|
||||
* [Frankenso main page](Hardware_Frankenso)
|
||||
* [Frankenso main page](Hardware-Frankenso)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -34,7 +34,7 @@
|
|||
* [MRE Kit instructions](Hardware_microRusEFI_kit_instructions)
|
||||
* [MRE Hardware checks](Hardware_microRusEFI_hardware_checks)
|
||||
* [MRE DIY TLDR](microRusEFI_DIY_TLDR)
|
||||
* [MRE Connectors](Hardware_microRusEfi_connectors)
|
||||
* [MRE Connectors](Hardware-microRusEfi-connectors)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -49,7 +49,7 @@
|
|||
* [MRE Adapter 68](MREAdapter68)
|
||||
* [MRE Adapter 72](MREAdapter72)
|
||||
* MRE Adaptor 88 - Coming Soon
|
||||
* [PNP 72 Jumper configs](PNP_72_Jumpers)
|
||||
* [PNP 72 Jumper configs](PNP-72-Jumpers)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -64,7 +64,7 @@
|
|||
<details><summary><u>Proteus</u></summary>
|
||||
|
||||
* [Proteus Main Page](Proteus)
|
||||
* [Proteus v0.2 wiring](Hardware_Proteus_Wiring_v02)
|
||||
* [Proteus v0.3 wiring](Hardware_Proteus_Wiring_v03)
|
||||
* [Proteus v0.2 wiring](Hardware-Proteus-Wiring-v02)
|
||||
* [Proteus v0.3 wiring](Hardware-Proteus-Wiring-v03)
|
||||
|
||||
</details>
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
## Master list of Ignition pages
|
||||
|
||||
### [Ignition FAQ](FAQ_Ignition)
|
||||
### [Ignition FAQ](FAQ-Ignition)
|
||||
|
||||
<details><summary><u>rusEFI Project</u></summary>
|
||||
|
||||
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
<details><summary><u>Coils and ignition modules</u></summary>
|
||||
|
||||
* [List of tested coils](Vault_Of_Ignition_Parts)
|
||||
* [List of tested Ignition modules and IGBTs](Vault_Of_Ignition_Parts)
|
||||
* [List of tested coils](Vault-Of-Ignition-Parts)
|
||||
* [List of tested Ignition modules and IGBTs](Vault-Of-Ignition-Parts)
|
||||
|
||||
</details>
|
||||
|
|
@ -2,6 +2,6 @@
|
|||
## These are containers for all the lists and data dumps we have collected over the years.
|
||||
|
||||
[BMW info](Vault_BWM_Info.md)
|
||||
[Ignition Parts](Vault_Of_Ignition_Parts.md)
|
||||
[Sensors](Vault_Of_Sensors.md)
|
||||
[Terminology and abbreviations](Vault_Of_Terminology.md)
|
||||
[Ignition Parts](Vault-Of-Ignition-Parts.md)
|
||||
[Sensors](Vault-Of-Sensors.md)
|
||||
[Terminology and abbreviations](Vault-Of-Terminology.md)
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@
|
|||
* [MRE DIY TLDR](microRusEFI_DIY_TLDR)
|
||||
|
||||
|
||||
[All Hardware pages](Pages_Hardware)
|
||||
[All Hardware pages](Pages-Hardware)
|
||||
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
<details><summary><u>Throttle and ETB</u></summary>
|
||||
|
||||
* [How To - ETB ](HOWTO_electronic_throttle_body)
|
||||
* [How To - ETB configuration](HOWTO_electronic_throttle_body_configuration)
|
||||
* [How To - ETB ](HOWTO-electronic-throttle-body)
|
||||
* [How To - ETB configuration](HOWTO-electronic-throttle-body_configuration)
|
||||
* List of tested ETBs - Coming Soon
|
||||
* List of tested TPS sensors - Coming Soon
|
||||
* List of tested Throttle pedal sensors - Coming Soon
|
||||
|
|
@ -13,7 +13,7 @@
|
|||
|
||||
<details><summary><u>MAP Sensors</u></summary>
|
||||
|
||||
* [Fuel Overview](Fuel_Overview)
|
||||
* [Fuel Overview](Fuel-Overview)
|
||||
* List of tested MAP sensors - Coming Soon
|
||||
* [GM Map sensor](GM-map-Sensor)
|
||||
|
||||
|
|
@ -22,15 +22,15 @@
|
|||
|
||||
<details><summary><u>MAF Sensors</u></summary>
|
||||
|
||||
* [List of tested MAP sensors](Vault_Of_Sensors)
|
||||
* [List of tested MAP sensors](Vault-Of-Sensors)
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
<details><summary><u>AFR measurement (Wideband)</u></summary>
|
||||
|
||||
* [Wide Band Sensors](Wide_Band_Sensors)
|
||||
* [Do I need a wideband](do_i_need_wideband_oxygen_sensor)
|
||||
* [Wide Band Sensors](Wide-Band-Sensors)
|
||||
* [Do I need a wideband](do-i-need-wideband-oxygen-sensor)
|
||||
* [Old WBO2 page](WBO)
|
||||
* List of tested WBO2 sensors - Coming Soon
|
||||
|
||||
|
|
@ -53,7 +53,7 @@
|
|||
|
||||
<details><summary><u>Crank Sensors</u></summary>
|
||||
|
||||
* [List of tested trigger patterns](All_Supported_Triggers)
|
||||
* [List of tested trigger patterns](All-Supported-Triggers)
|
||||
* List of tested Crank Sensors - Coming Soon
|
||||
|
||||
[//]: # 'Trigger page seems broken'
|
||||
|
|
@ -63,7 +63,7 @@
|
|||
|
||||
<details><summary><u>Knock Sensors</u></summary>
|
||||
|
||||
* [Overview](knock_sensing)
|
||||
* [Overview](knock-sensing)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
|
|||
|
|
@ -10,15 +10,15 @@
|
|||
<details><summary><u>General Firmware info</u></summary>
|
||||
|
||||
* [Preferred Code Style](Code-Style)
|
||||
* [Debug Mode](Debug_Mode)
|
||||
* [Debug Mode](Debug-Mode)
|
||||
* [Performance Tracing](Developer-Performance-Tracing)
|
||||
* [Firmware Downloads](Downloads)
|
||||
* [Feature requests](Feature_Request_Feature_Bounty_Program)
|
||||
* [Feature ideas](I_have_an_idea)
|
||||
* [How To DFU](HOWTO_DFU)
|
||||
* [How To Update Firmware](HOWTO_Update_Firmware)
|
||||
* [How To Upload a Tune](HOWTO_upload_tune)
|
||||
* [rusEFI Bundle](rusefi_bundle)
|
||||
* [Feature ideas](I-have-an-idea)
|
||||
* [How To DFU](HOWTO-DFU)
|
||||
* [How To Update Firmware](HOWTO-Update-Firmware)
|
||||
* [How To Upload a Tune](HOWTO-upload-tune)
|
||||
* [rusEFI Bundle](rusefi-bundle)
|
||||
|
||||
</details>
|
||||
|
||||
|
|
@ -26,6 +26,6 @@
|
|||
|
||||
* See also -> [rusEFI Project Overview](rusEFI-project)
|
||||
* [FSIO](FSIO)
|
||||
* [Virtual Simulator](Virtual_simulator)
|
||||
* [Virtual Simulator](Virtual-simulator)
|
||||
|
||||
</details>
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ Source & production files at: https://github.com/mck1117/proteus/
|
|||
|
||||
## Wiring & Pinout
|
||||
|
||||
[Pinout for version 0.3 (green)](Hardware_Proteus_Wiring_v03)
|
||||
[Pinout for version 0.3 (green)](Hardware-Proteus-Wiring-v03)
|
||||
|
||||
[Pinout for version 0.2 (black)](Hardware_Proteus_Wiring_v02)
|
||||
[Pinout for version 0.2 (black)](Hardware-Proteus-Wiring-v02)
|
||||
|
||||
[Fabrication](Hardware-Proteus-Fabrication)
|
||||
|
||||
|
|
|
|||
|
|
@ -6,12 +6,12 @@ It is important for a new user to understand some things about rusEFI before jum
|
|||
|
||||
RusEFI is a community project, everyone here is giving there time for free and have normal day jobs, this limits the amount of direct support we can give.
|
||||
This means that the wiki and forum should be the first port of call for any questions. Most things are covered within these two resources.
|
||||
With this in mind it is important that new users take a quick look at the [D is for distration](D_is_for_DISTRACTION.md) page and the [What rusEFI cannot do](What_rusEFI_Cannot_Do.md)
|
||||
With this in mind it is important that new users take a quick look at the [D is for distration](D-is-for-DISTRACTION.md) page and the [What rusEFI cannot do](What-rusEFI-Cannot-Do.md)
|
||||
|
||||
RusEFI is an advance system, many of the features of rusEFI are things you will only find on high end or OEM ECUs. This means that users will need to take time to understand the systems they are working on and the principals behind them, a lot of the information provided is based on the concept of "helping you to help yourself".
|
||||
You will be expected to put in the time to find information on the sensors you are using and any vehicle specific requirements of your install. (Though the team will always help where they can).
|
||||
|
||||
RusEFI is also still very much in development, the dev team provide no guarantee that any of the current features are fully working. It is important that users take a good look at the [current development status](Dev_Status.md) page. This is what we consider the most comprehensive list of the status of all the features of the rusEFI system.
|
||||
RusEFI is also still very much in development, the dev team provide no guarantee that any of the current features are fully working. It is important that users take a good look at the [current development status](Dev-Status.md) page. This is what we consider the most comprehensive list of the status of all the features of the rusEFI system.
|
||||
|
||||
## Identifying your hardware requirements
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ Ignition coils
|
|||
|
||||
## Getting help
|
||||
|
||||
[xxx](HOWTO_ask_questions.md)
|
||||
[xxx](HOWTO-ask-questions.md)
|
||||
|
||||
## Where to search for information
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
See also http://rusefi.com/wiki/index.php?title=Hardware:Troubleshooting
|
||||
See also [Troubleshooting](Troubleshooting)
|
||||
|
||||
## Summary
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ Please Read https://opensource.com/life/16/10/how-ask-technical-questions
|
|||
Q: Matt and Andrey are on Facebook, shall I message Matt or Andrey directly?
|
||||
|
||||
A: Unfortunately we do not have resources for technical support via Facebook direct messages.
|
||||
Same about forum private messages. Please use public channels to have a higher chance of a response from the community. The more effort you make to ask a good question, the better response you would get. See also [HOWTO_ask_questions](HOWTO_ask_questions)
|
||||
Same about forum private messages. Please use public channels to have a higher chance of a response from the community. The more effort you make to ask a good question, the better response you would get. See also [HOWTO-ask-questions](HOWTO-ask-questions)
|
||||
|
||||
Q: how do I attach logs to my forum post? Looks like forum does not allow .msl files?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
See also http://rusefi.com/articles/measuring_temperature/
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#step_3:_Analog_Inputs
|
||||
See also [Frankenstein Analog Inputs](Hardware-Frankenstein#step-3-analog-inputs)
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Analog_Inputs
|
||||
See also [Frankenso Analog Inputs](Hardware-Frankenso#analog-inputs)
|
||||
|
||||
See also Hardware:Troubleshooting
|
||||
See also [Troubleshooting](Troubleshooting)
|
||||
|
||||
In order to configure coolant temperature sensor or intake air sensor you would need to know it's resistance at three temperatures - lowest, highest and somewhere in between. You would also need to know the value of pull-up 'bias' resistor, which together with your sensor would make a voltage divider.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
See [list of all supported triggers](All_Supported_Triggers)
|
||||
See [list of all supported triggers](All-Supported-Triggers)
|
||||
|
||||
## Troubleshooting trigger input
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ A: try _enable trigger_details_ command in console or "print sync details to con
|
|||
|
||||
*Q: I have a 60/2 crank wheel and I would like to use a cam sensor for fully sequential mode. Should I use "4-stroke with Cam sensor"?*
|
||||
|
||||
A: You can only use "4-stroke with Cam sensor" if your composite trigger shape is known to rusEfi. If you are adding a cam to 60/2, rusEfi probably does not know this combination with all the angles precisely. The way to add sequential to a skipped-tooth crank wheel is via cam input mode, same as used for VVT (see also http://rusefi.com/wiki/index.php?title=Manual:Software:VVT)
|
||||
A: You can only use "4-stroke with Cam sensor" if your composite trigger shape is known to rusEfi. If you are adding a cam to 60/2, rusEfi probably does not know this combination with all the angles precisely. The way to add sequential to a skipped-tooth crank wheel is via cam input mode, same as used for VVT (see also [VVT](VVT))
|
||||
This case your known crank shape is used for shaft position lookup and your cam is only used for phase lookup - exact cam sensor angular position is less important.
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Software:VVT
|
||||
See also [VVT](VVT)
|
||||
|
|
|
|||
12
Try-It.md
12
Try-It.md
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
### Does Frankenso work with your setup?
|
||||
|
||||
Frankenso is expected to work with mid 1990's Mazda Miata, Protégé, Aspire, ect. It is also compatible (but to a lesser extent) with some vehicles like Honda Civic, ... If you have one of these vehicles, move to the below step. If you don't have this kind of setup, it may still be what you want. See this page for details about what is on the board. http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board
|
||||
Frankenso is expected to work with mid 1990's Mazda Miata, Protégé, Aspire, ect. It is also compatible (but to a lesser extent) with some vehicles like Honda Civic, ... If you have one of these vehicles, move to the below step. If you don't have this kind of setup, it may still be what you want. See this page for details about what is on the board. See [Frankenso](Frankenso)
|
||||
|
||||
If it has the features you need, then proceed to the next step.
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ If you get good feedback from the forum, then move on to the step below.
|
|||
|
||||
At this point, it appears the Frankenso is good for your applications. So now you need to get it. If you have some $, you can simply purchase an assembled board.
|
||||
|
||||
While you wait for the board, you can start learning about what you'll need to do when you get the board. You can install tuning software and you can get several items ready for when the board arrives. Start following the steps listed on this page http://rusefi.com/wiki/index.php?title=Manual:Start-a-project/en
|
||||
While you wait for the board, you can start learning about what you'll need to do when you get the board. You can install tuning software and you can get several items ready for when the board arrives. Start following the steps listed on 0this page](HOWTO-Get-Running)
|
||||
|
||||
Once you get the board, you should plug it into your harness. Then follow the instructions in the above link, which will walk you through powering it up, configure the board with TunerStudio (TS) and making software adjustments. Once you have things configured and working correctly you can then try to start it and make adjustments to the tuning tables via TS.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ Once you get the board, you should plug it into your harness. Then follow the in
|
|||
|
||||
### Does Frankenstein work for you setup?
|
||||
|
||||
Frankenstein is a generic board with a high level of flexibility. This flexibility comes at the cost of being a bit harder to work with. You will need to make some kind of adapter harness, which can often be done with an OEM harness and a break out board. In other situations like a small engine, you may wire direct to the board. This adapter harness can be done either by soldering in jumper wires to change a pin out for your specific needs, or it can be done by putting wires under screw terminal connections. This board includes high impedance fuel injectors, hi/lo drive ignition, several analog inputs and many of the most common circuits needed for a control unit. You can find information about this board at this link. http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board
|
||||
Frankenstein is a generic board with a high level of flexibility. This flexibility comes at the cost of being a bit harder to work with. You will need to make some kind of adapter harness, which can often be done with an OEM harness and a break out board. In other situations like a small engine, you may wire direct to the board. This adapter harness can be done either by soldering in jumper wires to change a pin out for your specific needs, or it can be done by putting wires under screw terminal connections. This board includes high impedance fuel injectors, hi/lo drive ignition, several analog inputs and many of the most common circuits needed for a control unit. You can find information about this board at [this link](Hardware-Frankenstein).
|
||||
|
||||
If this board contains the basic features you are looking for, continue to the next step.
|
||||
|
||||
|
|
@ -42,7 +42,7 @@ If you have some $, you can simply purchase the board or you can purchase the so
|
|||
|
||||
Once you have the board, you will need to follow the instructions found here (insert link some time) These instructions should get you physically connected and operational.
|
||||
|
||||
Once you are physically operational, then you can follow instructions found here http://rusefi.com/wiki/index.php?title=Manual:Software:User/en This can also be found under the users area in the left pane. These instructions will show you how to connect with the tuning software known as TunerStudio (TS). TS is used for configuring items like TPS, IAT, number of cyl, ect, as well it is used for uploading tuning tables and tuning parameter and making a large variety of software adjustments.
|
||||
Once you are physically operational, then you can follow instructions found [here](HOWTO-quick-start) This can also be found under the users area in the left pane. These instructions will show you how to connect with the tuning software known as TunerStudio (TS). TS is used for configuring items like TPS, IAT, number of cyl, ect, as well it is used for uploading tuning tables and tuning parameter and making a large variety of software adjustments.
|
||||
|
||||
## Adventure 3: I need other features. How do I get other features?
|
||||
|
||||
|
|
@ -85,11 +85,11 @@ The stimulator board allows better simulation than what is noted above. It allow
|
|||
|
||||
### Virtual simulation
|
||||
|
||||
rusEFI has a virtual option. This basically simulates the ARM processors, and you can feed it registers and such which will simulate the system which is done purely in PC software. This can be really handy for build validations. You can play a log file to the registers then measure the output signals and verify they are within certain tolerances. You can also develop a variety of situations that can't easily or safely be validated with real hardware. For example, it would be really costly to physically see what happens when you have extremely fast changes in RPM caused by back fires, or broken components. See http://rusefi.com/wiki/index.php?title=Manual:Software:Simulator
|
||||
rusEFI has a virtual option. This basically simulates the ARM processors, and you can feed it registers and such which will simulate the system which is done purely in PC software. This can be really handy for build validations. You can play a log file to the registers then measure the output signals and verify they are within certain tolerances. You can also develop a variety of situations that can't easily or safely be validated with real hardware. For example, it would be really costly to physically see what happens when you have extremely fast changes in RPM caused by back fires, or broken components. See [Simulator](Simulator)
|
||||
|
||||
### Compile firmware
|
||||
|
||||
You can compile the firmware, making changes and submitting bug fixes. See http://rusefi.com/wiki/index.php?title=Development:Source_code_intro
|
||||
You can compile the firmware, making changes and submitting bug fixes. See [HOWTO Contribute to Firmware](HOWTO-contribute-to-firmware)
|
||||
|
||||
### Experiment with java based dev console, tuner studio, etc.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ By default Tuner Studio connectivity is using pin PC10 for TX and PC11 RX, **bau
|
|||
|
||||
|
||||
|
||||
See also: http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Tuner_Studio
|
||||
See also: [TunerStudio Console Commands](Dev-Console-Commands#tuner-studio)
|
||||
|
||||
Please be sure to use current firmware version with current rusefi.ini project from [http://rusefi.com/build_server/rusefi_firmware.zip build_server]
|
||||
|
||||
|
|
|
|||
|
|
@ -39,4 +39,4 @@ TODO
|
|||
## Step 4: located TDC
|
||||
|
||||
Trigger synchronization is often not happening right at TDC. One would need to find out the angle between synchronization point and Top Dead Cylinder #1.
|
||||
See http://rusefi.com/wiki/index.php?title=Manual:Software:Trigger#Q_.26_A
|
||||
See [Trigger Q&A](Trigger#q--a)
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Audi 2006 A4 B7 Quattro 2.0 TFSI
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#154_pin
|
||||
[154 pin Connector](OEM-connectors#154-pin)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,8 +9,6 @@ Bosch 0280-155-976 injectors
|
|||
|
||||
http://rusefi.com/forum/viewtopic.php?f=3&t=696
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Hardware:Chrysler_PCI_Bus
|
||||
|
||||
## Plug 1
|
||||
38 pin
|
||||
|
||||
|
|
|
|||
|
|
@ -196,4 +196,4 @@ Outputs:
|
|||
Ignition module:
|
||||
IC7#28 via R28 & Q22
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Vehicle:Honda_Prelude_1993
|
||||
See also [Honda Prelude 1993](Honda-Prelude-1993)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
See also http://rusefi.com/wiki/index.php?title=Vehicle:Honda_Accord_1995
|
||||
See also [Honda Accord 1995](Honda Accord 1995)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
See also http://rusefi.com/wiki/index.php?title=Hardware:OEM_121_pin_connectors#368255.2FAsian
|
||||
See also [Asian 121 pin Connector](OEM-121-pin-connectors#368255asian)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,4 @@
|
|||
Manual:Hardware:Mazda_PnP
|
||||
|
||||
Back to http://rusefi.com/wiki/index.php?title=Vehicle-specific_pages
|
||||
[Frankenso Mazda Miata NA6 PnP](Frankenso-MazdaMiataNA6-pnp)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1990
|
||||
[Mazda Miata 1990](Mazda-Miata-1990)
|
||||
|
||||
[https://svn.code.sf.net/p/rusefi/code/trunk/misc/www/images/Frankenso/frankenso_1991_miata_f.jpg frankenso front]
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
Manual:Hardware:Mazda_PnP
|
||||
[Frankenso Mazda Miata NA6 PnP](Frankenso-MazdaMiataNA6-pnp)
|
||||
|
||||
[Frankenso options](https://docs.google.com/spreadsheets/d/1LTvS7I-128Hft9uXHG1JrBxetVjGJDSBkySgVDQ6MGk)
|
||||
|
||||
ECU pin-out seems to be very similar to https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1990 with few exceptions:
|
||||
ECU pin-out seems to be very similar to [1990](Mazda-Miata-1990) with few exceptions:
|
||||
|
||||
1. dedicated MAF ground
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Manual:Hardware:Mazda_PnP
|
||||
[Frankenso Mazda Miata NA6 PnP](Frankenso-MazdaMiataNA6-pnp)
|
||||
|
||||
1996 US 1.8
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
See also http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1994
|
||||
See also [Mazda Miata 1994](Mazda-Miata-1994)
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1996
|
||||
See also [Mazda Miata 1996](Mazda-Miata-1996)
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#64_pin
|
||||
[64 pin Connector](OEM-connectors#64-pin)
|
||||
|
||||
http://rusefi.com/forum/viewtopic.php?f=3&t=467
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Manual:Software:Trigger#Mazda_Miata_NB
|
||||
[Mazda Miata NB1 Trigger](All-Supported-Triggers#mazda-miata-nb1)
|
||||
|
||||
set engine_type 9
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,8 @@
|
|||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#72_pin
|
||||
[72 pin Connector](OEM-connectors#72-pin)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2001_ABS
|
||||
|
||||
For engine wiring see https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2002
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2001
|
||||
See also [Mazda Miata 2001 ABS](Mazda-Miata-2001-ABS)
|
||||
|
||||
For engine wiring see [Mazda Miata 2002](Mazda-Miata-2002)
|
||||
|
||||
|
||||
## Automatic Transmission
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#72_pin
|
||||
[72 pin Connector](OEM-connectors#72-pin)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ In RusEFI console, set engine_type 47 loads base settings.
|
|||
|
||||
## Wiring
|
||||
|
||||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#72_pin
|
||||
[121 pin Connector](OEM-121-pin-connectors)
|
||||
|
||||
|
||||
|
||||
|
|
@ -116,7 +116,7 @@ Individual pages for printing:
|
|||
|
||||
### Automatic Transmission
|
||||
|
||||
see http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2001#Automatic_Transmission
|
||||
see [Mazda Miata 2001 - Automatic Transmission](Mazda-Miata-2001#Automatic-Transmission)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#72_pin
|
||||
[72 pin Connector](OEM-connectors#72-pin)
|
||||
|
||||
See also https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2003_alt
|
||||
See also [Mazda Miata 2003 alt](Mazda-Miata-2003-alt)
|
||||
|
||||
For power see https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2002#Starting_.26_power
|
||||
For power see [Mazda Miata 2002 - Starting & Power](Mazda-Miata-2002#starting--power)
|
||||
|
||||
|
||||
|
||||
|
|
@ -127,7 +127,7 @@ Individual pages for printing:
|
|||
|
||||
## Automatic Transmission
|
||||
|
||||
see http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2001#Automatic_Transmission
|
||||
see [Mazda Miata 2001 - Automatic Transmission](Mazda-Miata-2001#automatic-transmission)
|
||||
|
||||
|
||||
|
||||
|
|
@ -153,7 +153,7 @@ US immobilizer
|
|||
|
||||
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2002
|
||||
See also [Mazda Miata 2002](Mazda-Miata-2002)
|
||||
|
||||
## Starting & power
|
||||
|
||||
|
|
@ -169,7 +169,7 @@ Fly-back diode - stripe facing +12 - is needed between IAC 2P (power, stripe sid
|
|||
|
||||
See http://rusefi.com/forum/viewtopic.php?f=3&t=906&p=25018l#p25018
|
||||
|
||||
For ignition key see https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2002#Starting_.26_power
|
||||
For ignition key see [Mazda Miata 2002 - Starting & Power](Mazda-Miata-2002#starting--power)
|
||||
|
||||
## Misc
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#72_pin
|
||||
[72 pin Connector](OEM-connectors#72-pin)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -27,4 +27,4 @@ ID 420 is temp, oil pressure gauge, coolent level, battery (alternator), oil war
|
|||
ID 201 is Speed (Max 300.00 Km/h, 186mph [9C 40] and RPM (Max 16382 [FF FE], although scale goes non-linear after 10k), minimum 0.5 sec timing.
|
||||
```
|
||||
|
||||
See also http://rusefi.com/wiki/index.php?title=Manual:Hardware:CAN_sniffer
|
||||
See also [CAN Sniffer](CAN-Sniffer)
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@
|
|||
#3 YEL/BLK CAN high
|
||||
#7 BLU +12v power
|
||||
|
||||
See also See also http://rusefi.com/wiki/index.php?title=Manual:Hardware:CAN_sniffer
|
||||
See also [CAN Sniffer](CAN-Sniffer)
|
||||
|
||||
ECU header: 121p, compatible with IV Volkswagen Jetta VR6, part number http://www.te.com/catalog/pn/en/966971-2
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ There are two ways to connect rusEFI virtual simulator to Tunerstudio, it all de
|
|||
|
||||
To start off you'll need to open one of your existing projects or just create a new one.
|
||||
|
||||
If you don't know how to create a Tunerstudio project go [here](HOWTO_create_tunerstudio_project.md)
|
||||
If you don't know how to create a Tunerstudio project go [here](HOWTO-create-tunerstudio-project.md)
|
||||
|
||||
With the paid version all you need to do is to go into the communication settings inside a created project
|
||||
|
||||
|
|
|
|||
|
|
@ -26,4 +26,4 @@ We get a lot of questions along the lines of "Can rusEFI run on XYZ processor?"
|
|||
There are many possible STM32 chips and development boards available on Ebay and Aliexpress that might in theory work with rusEFI.
|
||||
In reality there is absolutely no guarantee that any one of these will work as there are so many small variations of pinout, ram spec, processor speed, IO configurations, etc that it is impossible to support them all.
|
||||
This is without considering the problems that come with fake/poor quality chips or the GD32 series.
|
||||
For these reasons rusEFI only officially supports the chips listed [here](stm32_readme) we cannot provide assistance to get rusEFI working on any other chip set.
|
||||
For these reasons rusEFI only officially supports the chips listed [here](stm32-readme) we cannot provide assistance to get rusEFI working on any other chip set.
|
||||
54
_Sidebar.md
54
_Sidebar.md
|
|
@ -4,53 +4,53 @@
|
|||
# Getting Started
|
||||
|
||||
- [How to search the Wiki](HOWTO-Search-on-rusEFI-wiki)
|
||||
- [Quick Start](HOWTO_quick_start)
|
||||
- [How to ask questions](HOWTO_ask_questions)
|
||||
- [Quick Start](HOWTO-quick-start)
|
||||
- [How to ask questions](HOWTO-ask-questions)
|
||||
- [Support](Support)
|
||||
- [How to create a TunerStudio project](HOWTO_create_tunerstudio_project)
|
||||
- [HOWTOs and FAQs](Pages_FAQ_and_HOWTO)
|
||||
- [How to create a TunerStudio project](HOWTO-create-tunerstudio-project)
|
||||
- [HOWTOs and FAQs](Pages-FAQ-and-HOWTO)
|
||||
|
||||
# Community
|
||||
|
||||
- [Forum](https://rusefi.com/forum/)
|
||||
- [Slack](HOWTO_join_slack_channel)
|
||||
- [Slack](HOWTO-join-slack-channel)
|
||||
- [Facebook Users Group](https://www.facebook.com/groups/rusEfi/)
|
||||
- [Engines running on rusEFI](List_of_engines_running_rusEfi)
|
||||
- [Engines running on rusEFI](List-of-engines-running-rusEfi)
|
||||
|
||||
# Pages
|
||||
- [Fuel](Pages_Fuel)
|
||||
- [Hardware](Pages_Hardware)
|
||||
- [Sensors and Actuators](Pages_Sensors_and_Actuators)
|
||||
- [Ignition](Pages_Ignition)
|
||||
- [Software](Pages_Software)
|
||||
- [Fuel](Pages-Fuel)
|
||||
- [Hardware](Pages-Hardware)
|
||||
- [Sensors and Actuators](Pages-Sensors-and-Actuators)
|
||||
- [Ignition](Pages-Ignition)
|
||||
- [Software](Pages-Software)
|
||||
- [rusEFI Project](rusEFI-project)
|
||||
- [How To](Pages_HOWTO)
|
||||
- [How To](Pages-HOWTO)
|
||||
|
||||
|
||||
# Features
|
||||
|
||||
- [rusEFI project overview](rusEFI-project)
|
||||
- [rusEFI Online](Online)
|
||||
- [rusEFI virtual simulator](Virtual_simulator)
|
||||
- [Fueling](Fuel_Overview)
|
||||
- [rusEFI virtual simulator](Virtual-simulator)
|
||||
- [Fueling](Fuel-Overview)
|
||||
- [Multispark](Multi-Spark)
|
||||
- [Cranking](cranking)
|
||||
- [Electronic Throttle](HOWTO_electronic_throttle_body)
|
||||
- [Knock Sensing](knock_sensing)
|
||||
- [Electronic Throttle](HOWTO-electronic-throttle-body)
|
||||
- [Knock Sensing](knock-sensing)
|
||||
- [Variable Valve Timing](VVT)
|
||||
- [FSIO - Flexible Sweet Input Output](FSIO)
|
||||
- [GDI](GDI_status)
|
||||
- [GDI](GDI-status)
|
||||
|
||||
# Hardware
|
||||
|
||||
- [rusEfi Hardware Overview](Hardware)
|
||||
- [Wiring & Connectivity Overview](FAQ-Basic-Wiring-and-Connections)
|
||||
- [rusEFI Assembly Completeness Chart](Completeness_Chart)
|
||||
- [Kit Instructions](Pages_Kit_Instructions)
|
||||
- [rusEFI Assembly Completeness Chart](Completeness-Chart)
|
||||
- [Kit Instructions](Pages-Kit-Instructions)
|
||||
|
||||
### Boards
|
||||
|
||||
- [microRusEfi](Hardware_microRusEfi)
|
||||
- [microRusEfi](Hardware-microRusEfi)
|
||||
- [Proteus](Proteus)
|
||||
- [Frankenso](https://rusefi.com/forum/viewtopic.php?f=4&t=569)
|
||||
- [Hellen](https://rusefi.com/forum/viewtopic.php?f=4&t=1682)
|
||||
|
|
@ -61,21 +61,21 @@
|
|||
- [MREAdapter48: Miata NA6 & early NA8](MREAdapter48)
|
||||
- [MREAdapter55: from Lada to e30](MREAdapter55)
|
||||
- [MREAdapter72: Miata NB2 Mark 2.5 72 pin](MREAdapter72)
|
||||
- [Frankenso MazdaMiataNA6 PnP](Frankenso_MazdaMiataNA6_pnp)
|
||||
- [Creating a PnP PCB](PnP_PCB_HowTo)
|
||||
- [Frankenso MazdaMiataNA6 PnP](Frankenso-MazdaMiataNA6-pnp)
|
||||
- [Creating a PnP PCB](PnP-PCB-HowTo)
|
||||
|
||||
# Contributors
|
||||
|
||||
- [Documentation Strategy](Documentation_Strategy)
|
||||
- [Documentation Workflow](Documentation_Workflow)
|
||||
- [Documentation Strategy](Documentation-Strategy)
|
||||
- [Documentation Workflow](Documentation-Workflow)
|
||||
- [Firmware Code Doxygen](https://rusefi.com/docs/html)
|
||||
- [Firmware Code Automated Test Coverage](https://rusefi.com/docs/unit_tests_coverage)
|
||||
- [HOWTO Contribute To Firmware](HOWTO_contribute_to_firmware)
|
||||
- [HOWTO Contribute To Firmware](HOWTO-contribute-to-firmware)
|
||||
- [Firmware performance tracing](Developer-Performance-Tracing)
|
||||
|
||||
# Misc
|
||||
|
||||
- [How to convert from carburetor to EFI](how_to_convert_from_carburetor_to_EFI)
|
||||
- [Do I need a wideband oxygen sensor?](do_i_need_wideband_oxygen_sensor)
|
||||
- [How to convert from carburetor to EFI](how-to-convert-from-carburetor-to-EFI)
|
||||
- [Do I need a wideband oxygen sensor?](do-i-need-wideband-oxygen-sensor)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
|
||||
|
||||
[Frankenso Board Technical Details](https://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Default_Pinout)
|
||||
[Frankenso Board Technical Details](Hardware-Frankenso#default-pinout)
|
||||
|
||||
# Board Jumper Wires
|
||||
|
||||
|
|
@ -26,9 +26,9 @@
|
|||
-----------------------------------
|
||||
|
||||
|
||||
[Frankenso analog](https://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Analog_Inputs)
|
||||
[Frankenso analog](Hardware-Frankenso#analog-inputs)
|
||||
|
||||
| Analog | ECU pin |MCU pin | pull-up | pull-down | |
|
||||
| Analog | ECU pin |MCU pin | pull-up | pull-down | |
|
||||
|------|------|----|-------|---|---|
|
||||
| Coolant (stock) | 3Q | PC2 | 2.7K | n/a | |
|
||||
| Intake Air (stock) | 3P | PC1 | 2.7K | n/a | |
|
||||
|
|
@ -47,7 +47,7 @@
|
|||
-----------------------------------
|
||||
|
||||
|
||||
[Frankenso_MazdaMiataNA6_pnp](Frankenso_MazdaMiataNA6_pnp)
|
||||
[Frankenso MazdaMiataNA6 pnp](Frankenso-MazdaMiataNA6-pnp)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
The [Frankenso](https://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board) board was designed to be used on Mazda Miata NA6 as a plug-and-play solution.
|
||||
The [Frankenso](Hardware-Frankenso) board was designed to be used on Mazda Miata NA6 as a plug-and-play solution.
|
||||
|
||||
## Stage 0
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Insert supplied extra pin wire (pin on this picture) and close the latches. Done
|
|||
|
||||
|
||||
-----------------------------------
|
||||
[Frankenso Miata NA6 PNP Technical Details](Frankenso_MazdaMiataNA6_pnp_board_wiring)
|
||||
[Frankenso Miata NA6 PNP Technical Details](Frankenso-MazdaMiataNA6-pnp-board-wiring)
|
||||
|
||||
|
||||
### TPS mod
|
||||
|
|
@ -69,14 +69,12 @@ NSR0530HT SOD-323 SMD Schottky Barrier Diodes 30V 500mA 0.5A
|
|||
|
||||
|
||||
|
||||
[old wiki Mazda PnP](https://rusefi.com/wiki/index.php?title=Manual:Hardware:Mazda_PnP)
|
||||
[Mazda_Miata_1990](Mazda-Miata-1990)
|
||||
|
||||
[old wiki Mazda_Miata_1990](https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1990)
|
||||
[Mazda_Miata_1994](Mazda-Miata-1994)
|
||||
|
||||
[old wiki Mazda_Miata_1994](https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1994)
|
||||
|
||||
[old wiki Frankenso board](https://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board)
|
||||
[Frankenso board](Hardware-Frankenso)
|
||||
|
||||
1996+ is too different unfortunately
|
||||
|
||||
[old wiki Mazda_Miata_1996](https://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_1996)
|
||||
[Mazda_Miata_1996](Mazda-Miata-1996)
|
||||
|
|
|
|||
Loading…
Reference in New Issue