David Holdeman
GitHub
parent
8d80ac8034
commit
08bf2ad059
|
|
@ -1,6 +1,6 @@
|
|||
# Adaptive Suspension
|
||||
|
||||
[Shock Dyno](Shock-Dyno.md)
|
||||
[Shock Dyno](Shock-Dyno)
|
||||
|
||||
[ArsTechnica: DSC Sport’s active shocks in action](https://arstechnica.com/cars/2015/07/the-future-of-car-suspension-is-here-dsc-sports-active-shocks-in-action/)
|
||||
"Normally, a car's weight transfers from front to back as it brakes and accelerates, and from side to side as it corners. As the force on each corner changes, so does the grip available to that wheel; less weight equals less grip. Active shocks control this by varying the degree to which each spring's compresses and extends (as the springs are passive, these systems are sometimes known as semi-active)."
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Uses breakout module noted [here](http://rusefi.com/forum/viewtopic.php?f=4&t=45
|
|||
* 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](Console.md).
|
||||
* 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.md)
|
||||
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)
|
||||
|
|
|
|||
|
|
@ -8,4 +8,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 [Debug Fields](Debug-Fields.md)
|
||||
See [Debug Fields](Debug-Fields)
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Resistors should be listed like this 100R or 2k2
|
|||
|
||||
## PCB design rules
|
||||
|
||||
- See [PCB Design Rules](PCB-Design-Rules.md)
|
||||
- See [PCB Design Rules](PCB-Design-Rules)
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ orange LED: warning: blinking in case of trigger input decoding warning or other
|
|||
|
||||
microUSB channel is more sensitive to noise but it's faster
|
||||
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity.md)
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
|
||||
|
||||
### Configuration reset
|
||||
|
||||
|
|
@ -45,4 +45,4 @@ Grounding PD6 resets saved configuration to default state - see [this forum post
|
|||
|
||||
### Board Testing mode
|
||||
|
||||
Grounding PB0 enables board testing mode. See [Hardware Test Mode](Hardware-Test-Mode.md)
|
||||
Grounding PB0 enables board testing mode. See [Hardware Test Mode](Hardware-Test-Mode)
|
||||
|
|
|
|||
|
|
@ -51,7 +51,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 [guide](Electronic-Throttle-Body-Configuration-Guide) you should read.
|
||||
|
||||
### Main Relay support
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ There is some information on known smart coils and how to work out if you have a
|
|||
|
||||
Great - same as the smart coils, please double check your coils are actually simple coils without built in ignition modules.
|
||||
You will need to source an external ignition module to go between the ECU and the coils.
|
||||
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)
|
||||
These are generally quite cheap and can be found on some cars in the junk yard. We also made our own simple module [here](https://rusefi.com/forum/viewtopic.php?t=286)
|
||||
|
||||
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)
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
# First Engine Start
|
||||
|
||||
Please see here: [HOWTO Get Running](HOWTO-Get-Running.md)
|
||||
Please see here: [HOWTO Get Running](HOWTO-Get-Running)
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ TBD
|
|||
|
||||
see also [Fuel Overview](Fuel-Overview)
|
||||
see also [Ignition](Ignition)
|
||||
see also [Idle Control](Idle-Control.md)
|
||||
see also [Idle Control](Idle-Control)
|
||||
see also [this forum thread](http://rusefi.com/forum/viewtopic.php?f=2&t=1124&p=21278)
|
||||
|
||||
## Share your tune
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# HOWTO Get Running
|
||||
|
||||
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project.md)
|
||||
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project)
|
||||
|
||||
## Summary
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ Place some place that is away from hot items like the exhaust. Mount on a piece
|
|||
* Wire rusEFI like Frankenstein as shown below
|
||||
|
||||
|
||||
* It will likely be helpful to get a partial harness from a junk yard, and switch to rusEFI circuit-by-circuit using a [breakout module.](Breakout-Module.md)
|
||||
* It will likely be helpful to get a partial harness from a junk yard, and switch to rusEFI circuit-by-circuit using a [breakout module.](Breakout-Module)
|
||||
* Use junk hard harness to make extension harness. Use the junk yard ECU connector to break out the wire harness to the breakout board. Then from the far side of the breakout board, install the junk yard harness connector. Then connect the original ECU. This should allow you to start and run then engine as normal.
|
||||
|
||||
#### Prepare engine wiring
|
||||
|
|
@ -152,7 +152,7 @@ See also [https://github.com/rusefi/rusefi/blob/master/firmware/console/binary/o
|
|||
|
||||
See also [Error Codes](Error-Codes)
|
||||
|
||||
See also [Debug Fields](Debug-Fields.md)
|
||||
See also [Debug Fields](Debug-Fields)
|
||||
|
||||
### External links
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# HOWTO M72 V12 on Proteus
|
||||
|
||||
See also [HOWTO-Crimp-Ampseal](HOWTO-Crimp-Ampseal.md)
|
||||
See also [HOWTO-Crimp-Ampseal](HOWTO-Crimp-Ampseal)
|
||||
|
||||
See also [Vault-Of-Electronic-Throttle-Bodies-ETB](Vault-Of-Electronic-Throttle-Bodies-ETB) Nissan Hitachi SERA576-01 60mm throttle body recommended. In order to mount SERA576-01 you just need to drill ETB bolt passages to 10mm / 3/8".
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ There are three ways to connect rusEFI to internet:
|
|||
|
||||
1) "Broadcast" tab of rusEFI TunerStudio plugin.
|
||||
2) rusEFI network_connector tool running for instance on Raspberry Pi or similar Single Board Computer
|
||||
3) [rusEFI Android application](rusEFI-Android.md)
|
||||
3) [rusEFI Android application](rusEFI-Android)
|
||||
|
||||
Connecting to remote ECU is a two step process:
|
||||
First you connect rusEFI TunerStudio plugin to remote controller via Internet, and then you connect TunerStudio to rusEFI TunerStudio plugin locally. IP Address "localhost" Port default value 29001.
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ See also [https://github.com/rusefi/rusefi/blob/master/firmware/console/binary/o
|
|||
|
||||
See also [Error Codes](Error-Codes)
|
||||
|
||||
See also [Debug Fields](Debug-Fields.md)
|
||||
See also [Debug Fields](Debug-Fields)
|
||||
|
||||
## External links
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
## Windows
|
||||
|
||||
Launch [rusEFI Console](Console.md). You can find it in the bundle you downloaded, in the "console" folder.
|
||||
Launch [rusEFI Console](Console). You can find it in the bundle you downloaded, in the "console" folder.
|
||||
|
||||
Click the "Update Firmware" button once you've picked desired update mode.
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ dfu-util -a 0 -D rusefi.dfu
|
|||
|
||||
## More Information
|
||||
|
||||
For more about DFU see [HOWTO-DFU](HOWTO-DFU.md)
|
||||
For more about DFU see [HOWTO-DFU](HOWTO-DFU)
|
||||
|
||||
ST-LINK is an advanced mode of firmware update which requires ST-LINK device, either external, or built-in like on Discovery/Nucleo board.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,11 +2,11 @@
|
|||
|
||||
Before getting in touch for some assistance there are a couple of things to know that will make it easy for us to help you.
|
||||
|
||||
First off before asking for help, please check the rest of the [wiki,](HOWTO-Search-on-rusEFI-wiki.md) Take a look through the [forum](https://rusefi.com/forum)/search.php) or read through the [FAQs.](Pages-FAQ-and-HOWTO)
|
||||
First off before asking for help, please check the rest of the [wiki,](HOWTO-Search-on-rusEFI-wiki) Take a look through the [forum](https://rusefi.com/forum)/search.php) or read through the [FAQs.](Pages-FAQ-and-HOWTO)
|
||||
|
||||
If after that you still need direct help then please have a read of the information below and help us to help you.
|
||||
|
||||
## Please post your tune & log files at [rusEFI Online](Online.md). More on that in [Support](Support)
|
||||
## Please post your tune & log files at [rusEFI Online](Online). More on that in [Support](Support)
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
* Please have a separate [forum](https://rusefi.com/forum) thread for each of your rusEFI vehicles. Please have at least one picture in the first forum post.
|
||||
|
||||
* Please upload your best rusEFI tune to rusEFI Online [HOWTO-upload-tune](HOWTO-upload-tune.md)
|
||||
* Please upload your best rusEFI tune to rusEFI Online [HOWTO-upload-tune](HOWTO-upload-tune)
|
||||
|
||||
* Please upload a few interesting log files to rusEFI online - a starting/warm-up log, a wide open throttle driving log etc.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,13 +2,13 @@
|
|||
|
||||
The weakest point of rusEFI is lack of samples and success stories. As of Aug 2020, we _really_ need vehicle threads on the forum.
|
||||
|
||||
[HOWTO contribute success stories](HOWTO-contribute-success-stories.md)
|
||||
[HOWTO contribute success stories](HOWTO-contribute-success-stories)
|
||||
|
||||
We also do not have much user feedback in general - we do not know how many rusEFI units are used regularly and what are users looking for (we know about launch control).
|
||||
|
||||
Another weak point of rusEFI is documentation. If you've played with rusEFI for any time chances are you have help [improve the documentation.](HOWTO-contribute-to-documentation.md)
|
||||
Another weak point of rusEFI is documentation. If you've played with rusEFI for any time chances are you have help [improve the documentation.](HOWTO-contribute-to-documentation)
|
||||
|
||||
We are also extremely short on software developers. [HOWTO contribute to firmware](HOWTO-contribute-to-firmware.md)
|
||||
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,7 +4,7 @@
|
|||
|
||||
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.md)
|
||||
Before joining slack please read the section on [asking questions.](HOWTO-ask-questions)
|
||||
Please also read the topic on [distraction.](D-is-for-DISTRACTION). And maybe even [Knowledge-best-practices-and-Channels](Knowledge-best-practices-and-Channels)
|
||||
|
||||
## Joining the channel
|
||||
|
|
|
|||
|
|
@ -24,9 +24,9 @@
|
|||
|
||||
Your board comes with rusEFI firmware installed on it, but it should be updated.
|
||||
|
||||
[How to update your firmware](HOWTO-Update-Firmware.md)
|
||||
[How to update your firmware](HOWTO-Update-Firmware)
|
||||
|
||||
If you have a Frankenso, Frankenstein, or are just messing with a Discovery, you will need to install firmware first. See [these instructions.](Discovery-Based-Board-Setup.md)
|
||||
If you have a Frankenso, Frankenstein, or are just messing with a Discovery, you will need to install firmware first. See [these instructions.](Discovery-Based-Board-Setup)
|
||||
|
||||
## Plug and Play (PNP) Initial Setup
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ And we're done with the initial startup. Congratulations- you have your car runn
|
|||
|
||||
Q: How do I change settings?
|
||||
|
||||
A: You can change settings and your engine tune using [TunerStudio](HOWTO-create-tunerstudio-project.md).
|
||||
A: You can change settings and your engine tune using [TunerStudio](HOWTO-create-tunerstudio-project).
|
||||
|
||||
Q: Is there anything special I need to do to wire USB from ECU harness?
|
||||
|
||||
|
|
@ -119,20 +119,20 @@ A: For most of the pinout changes to be applied you need to reset rusEFI. Do not
|
|||
|
||||
## rusEFI Console
|
||||
|
||||
[rusEFI Console](Console.md) is a handy development and debugging tool. Try it out and learn what it is capable of.
|
||||
[rusEFI Console](Console) is a handy development and debugging tool. Try it out and learn what it is capable of.
|
||||
|
||||
## Tuner Studio
|
||||
|
||||
rusEFI uses TunerStudio to allow you to configure and tune your ECU.
|
||||
|
||||
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project.md)
|
||||
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project)
|
||||
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity.md)
|
||||
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
|
||||
|
||||
## Tuning the engine
|
||||
|
||||
[Get Running](HOWTO-Get-Running.md)
|
||||
[Get Running](HOWTO-Get-Running)
|
||||
|
||||
[Get Tuning](Get-tuning-with-TunerStudio-and-your-rusEFI.md)
|
||||
[Get Tuning](Get-tuning-with-TunerStudio-and-your-rusEFI)
|
||||
|
||||
[Error Codes](Error-Codes)
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ node .\node_modules\markdown-link-validator\dist\src\bin\markdown-link-validator
|
|||
|
||||
VS Code Extensions "markdownlint" and "Code Spell Checker" have to be installed
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -69,4 +69,4 @@ A: USB choice dictated by price and availability. If it changes MRE page will no
|
|||
|
||||
## Q: Exiting, what soldering iron is best?
|
||||
|
||||
A: [FAQ Why No Self Assembly](FAQ-Why-No-Self-Assembly/)
|
||||
A: [FAQ Why No Self Assembly](FAQ-Why-No-Self-Assembly)
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@
|
|||
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.md)?
|
||||
2) how can you help with this proposal or [in general](HOWTO-help-rusEFI)?
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ There are two kinds of 121 connectors which look pretty much the same but do not
|
|||
|
||||
This one is used on Asian vehicles - Kia Hyundai etc.
|
||||
|
||||
See also [Kia Spectra 2005](Vehicles/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
|
||||
|
||||
[Kia Spectra 2005](Vehicles/Kia-Spectra-2005)
|
||||
[Kia Spectra 2005](Kia-Spectra-2005)
|
||||
|
||||
[Mini-Cooper-2003](Vehicles/Mini-Cooper-2003)
|
||||
[Mini-Cooper-2003](Mini-Cooper-2003)
|
||||
|
||||
[Nissan Xterra 2011](Vehicles/Nissan-Xterra-2011)
|
||||
[Nissan Xterra 2011](Nissan-Xterra-2011)
|
||||
|
|
|
|||
|
|
@ -600,7 +600,7 @@ Currently used by Nissan, Hyundai and Kia. Also Audi, VW and Mini Cooper
|
|||
|
||||
2003 VW Passat
|
||||
|
||||
[121 pin main page](OEM-121-pin-connectors.md)
|
||||
[121 pin main page](OEM-121-pin-connectors)
|
||||
|
||||
## 122 pin
|
||||
|
||||
|
|
|
|||
|
|
@ -6,13 +6,13 @@
|
|||
- share your tune
|
||||
- checkout other's tunes
|
||||
|
||||
See [HOWTO set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token.md)
|
||||
See [HOWTO set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
|
||||
|
||||
See [HOWTO upload tune](HOWTO-upload-tune.md)
|
||||
See [HOWTO upload tune](HOWTO-upload-tune)
|
||||
|
||||
See [HOWTO upload log](HOWTO-upload-log.md)
|
||||
See [HOWTO upload log](HOWTO-upload-log)
|
||||
|
||||
See [HOWTO Remote Tuning](HOWTO-Remote-Tuning.md)
|
||||
See [HOWTO Remote Tuning](HOWTO-Remote-Tuning)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
## FAQs
|
||||
|
||||
* [Ignition](FAQ-Ignition.md)
|
||||
* [Basic Wiring and Connections](FAQ-Basic-Wiring-and-Connections.md)
|
||||
* [Ignition](FAQ-Ignition)
|
||||
* [Basic Wiring and Connections](FAQ-Basic-Wiring-and-Connections)
|
||||
|
||||
## HOWTOs
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@
|
|||
|
||||
<details markdown="1"><summary><u>AFR measurement</u></summary>
|
||||
|
||||
* [Wide Band Sensors](Wide-Band-Sensors.md)
|
||||
* [Wide Band Sensors](Wide-Band-Sensors)
|
||||
* [Do I need a wideband](do-i-need-wideband-oxygen-sensor)
|
||||
* [Old WBO2 page](WBO)
|
||||
|
||||
|
|
@ -37,6 +37,6 @@
|
|||
* [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.md)
|
||||
* [Fuel injectors](Fuel-Injectors)
|
||||
|
||||
</details>
|
||||
|
|
|
|||
|
|
@ -1,15 +1,15 @@
|
|||
# Master list of HOW TO pages
|
||||
|
||||
* [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)
|
||||
* [Ask questions](HOWTO-ask-questions)
|
||||
* [Contribute to documentation](HOWTO-contribute-to-documentation)
|
||||
* [Create a tunerstudio project](HOWTO-create-tunerstudio-project)
|
||||
* [DFU](HOWTO-DFU)
|
||||
* [Get running](HOWTO-Get-Running)
|
||||
* [Help out](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)
|
||||
* [Remote tune](HOWTO-Remote-Tuning)
|
||||
* [Search the wiki](HOWTO-Search-on-rusEFI-wiki)
|
||||
* [Set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@
|
|||
|
||||
<details><summary><u>PNP Boards</u></summary>
|
||||
|
||||
* [PNP 48 - MRE based for Miata NA](microrusefi48adapter.pdf)
|
||||
* [PNP 48 - MRE based for Miata NA](/Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_latest.pdf)
|
||||
* [PNP 72 - MRE based for Miata NB2](Hardware/pnp_microRusEFI_nb2/hw72nb.pdf)
|
||||
* PNP 88 - Proteus based for 88pin Bosch - Coming Soon
|
||||
* [MRE Adapter 48](MREAdapter48)
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
## These are containers for all the lists and data dumps we have collected over the years
|
||||
|
||||
[BMW info](Vault-BMW-Info.md)
|
||||
[Ignition Parts](Vault-Of-Ignition-Parts.md)
|
||||
[Sensors](Vault-Of-Sensors.md)
|
||||
[Terminology and abbreviations](Vault-Of-Terminology.md)
|
||||
[BMW info](Vault-BMW-Info)
|
||||
[Ignition Parts](Vault-Of-Ignition-Parts)
|
||||
[Sensors](Vault-Of-Sensors)
|
||||
[Terminology and abbreviations](Vault-Of-Terminology)
|
||||
|
|
|
|||
|
|
@ -9,23 +9,23 @@
|
|||
<details markdown="1"><summary><u>General Firmware info</u></summary>
|
||||
|
||||
* [Preferred Code Style](Code-Style)
|
||||
* [Debug Mode](Debug-Mode.md)
|
||||
* [Debug Mode](Debug-Mode)
|
||||
* [Performance Tracing](Developer-Performance-Tracing)
|
||||
* [Firmware Downloads](Downloads)
|
||||
* [Feature requests](Feature-Requests-the-Feature-Bounty-Program.md)
|
||||
* [Feature ideas](I-have-an-idea.md)
|
||||
* [How To DFU](HOWTO-DFU.md)
|
||||
* [How To Update Firmware](HOWTO-Update-Firmware.md)
|
||||
* [How To Upload a Tune](HOWTO-upload-tune.md)
|
||||
* [Firmware Downloads](Download)
|
||||
* [Feature requests](Feature-Requests-the-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)
|
||||
* [Developing On Linux](Developing-On-Linux)
|
||||
* [rusEFI Bundle](rusEFI-bundle.md)
|
||||
* [rusEFI Bundle](rusEFI-bundle)
|
||||
|
||||
</details>
|
||||
|
||||
<details markdown="1"><summary><u>Firmware Features</u></summary>
|
||||
|
||||
* See also -> [rusEFI Project Overview](rusEFI-project)
|
||||
* [FSIO](FSIO.md)
|
||||
* [Virtual Simulator](Virtual-simulator.md)
|
||||
* [FSIO](FSIO)
|
||||
* [Virtual Simulator](Virtual-simulator)
|
||||
|
||||
</details>
|
||||
|
|
|
|||
|
|
@ -19,8 +19,8 @@ RusEFI is also still very much in development, the dev team provide no guarantee
|
|||
|
||||
You are going to need to know technical details about below referenced items.
|
||||
|
||||
To get an idea of [tested sensors and actuators](rusEFI-project-Sensors.md)
|
||||
and [available sensors and actuators](Pages-Sensors-and-Actuators.md)
|
||||
To get an idea of [tested sensors and actuators](rusEFI-project-Sensors)
|
||||
and [available sensors and actuators](Pages-Sensors-and-Actuators)
|
||||
|
||||
### Camshaft position sensor (optional)
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Is the trigger wheel of your engine contained in [All-Supported-triggers](All-Su
|
|||
- is a High or low impedance injector?
|
||||
- what is the flow rate?
|
||||
|
||||
To answer look at [Fuel-Injectors](Fuel-Injectors.md)
|
||||
To answer look at [Fuel-Injectors](Fuel-Injectors)
|
||||
|
||||
### Temperature sensors
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ To answer look at [Idle Control](Idle-Control)
|
|||
|
||||
- **wide band oxygen sensor required**
|
||||
|
||||
please see [Wide-Band-Sensors](Wide-Band-Sensors.md)
|
||||
please see [Wide-Band-Sensors](Wide-Band-Sensors)
|
||||
|
||||
### Speed sensor
|
||||
|
||||
|
|
@ -73,11 +73,11 @@ ToDo:
|
|||
|
||||
### Throttle control
|
||||
|
||||
[ETB](Electronic-Throttle-Body.md)
|
||||
[ETB](Electronic-Throttle-Body)
|
||||
|
||||
### Ignition coils
|
||||
|
||||
[Vault-Of-Ignition-Parts](Vault-Of-Ignition-Parts.md)
|
||||
[Vault-Of-Ignition-Parts](Vault-Of-Ignition-Parts)
|
||||
|
||||
### Engine characteristics
|
||||
|
||||
|
|
@ -90,11 +90,11 @@ ToDo:
|
|||
|
||||
- number of pins
|
||||
- shape of connector
|
||||
[OEM connectors](OEM-connectors.md)
|
||||
[OEM connectors](OEM-connectors)
|
||||
|
||||
## What rusEFI board is correct for your engine?
|
||||
|
||||
- Select from available Plug-and-Play ECUs [see](Vault-of-Pnp-Vehicle-Pages.md)
|
||||
- Select from available Plug-and-Play ECUs [see](Vault-of-Pnp-Vehicle-Pages)
|
||||
|
||||
OR
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# TunerStudio Plugin
|
||||
|
||||
rusEFI TunerStudio plugin is part of [rusEFI Online](Online.md) suite.
|
||||
rusEFI TunerStudio plugin is part of [rusEFI Online](Online) suite.
|
||||
|
||||
rusEFI TunerStudio plugin facilitates tune & logs upload.
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,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 [VVT](VVT.md))
|
||||
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 [VVT](VVT.md)
|
||||
See also [VVT](VVT)
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
||||
With the paid version all you need to do is to go into the communication settings inside a created project
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Good tuning of the X-tau system relies on taking logs and some trial and error t
|
|||
|
||||
## Old info
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# rusEFI Android App
|
||||
|
||||
rusEFI Android App is part of [rusEFI Online](Online.md) suite. The primary job of rusEFI Android app is to provide rusEFI ECU with remote tuning capability.
|
||||
rusEFI Android App is part of [rusEFI Online](Online) suite. The primary job of rusEFI Android app is to provide rusEFI ECU with remote tuning capability.
|
||||
|
||||
One day we will publish rusEFI Android at the google store but for now you would have to install it using [rusEFI-release.apk](https://rusefi.com/build_server/rusEFI-release.apk)
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Mary Shelley has a novel named "Frankenstein, or The Modern Prometheus" and that
|
|||
|
||||
That's when Nick has joined the party.
|
||||
|
||||
[List of Engines Running rusEFI](List-of-Engines-Running-rusEFI/)
|
||||
[List of Engines Running rusEFI](List-of-Engines-Running-rusEFI)
|
||||
|
||||
## 2013
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ searchfile() {
|
|||
# At some point in this scripts development, fixed links to files/images were given the './' prefix.
|
||||
# This didn't really hurt anything, but it's not idiomatic.
|
||||
# I added this to fix the problems I caused, and decided it was worth keeping around.
|
||||
if echo $link | grep -E '^\.\/' >/dev/null; then
|
||||
if echo $link | grep -E '^\./' >/dev/null; then
|
||||
# NEWLINK is the corrected link
|
||||
NEWLINK=$(echo $link | sed 's/^\.\///')
|
||||
# Print the file and the old link
|
||||
|
|
|
|||
Loading…
Reference in New Issue