Flat .md structure as a way to reduce migration pain/consistency #293

This commit is contained in:
rusefillc 2022-12-19 11:32:48 -05:00
parent 5bc10e9615
commit 3f8b13fa4f
131 changed files with 78 additions and 78 deletions

View File

@ -1,4 +1,4 @@
[Shock Dyno](Shock-Dyno)
[Shock Dyno](Shock-Dyno.md)
[ArsTechnica: DSC Sports 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)."

View File

@ -12,7 +12,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).
* Capture crank signals via [dev console](Console.md).
* 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.

View File

@ -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.md)
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)

View File

@ -7,4 +7,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)
See [Debug Fields](Debug-Fields.md)

View File

@ -51,7 +51,7 @@ Resistors should be listed like this 100R or 2k2
---
## PCB design rules
- See [PCB Design Rules](PCB-Design-Rules)
- See [PCB Design Rules](PCB-Design-Rules.md)
---
## Links to specific hardware projects

View File

@ -35,12 +35,12 @@ 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 [Tunerstudio Connectivity](Tunerstudio-Connectivity)
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity.md)
### Configuration reset
Grounding PD6 resets saved configuration to default state - see [this forum post](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 [Hardware Test Mode](Hardware-Test-Mode)
Grounding PB0 enables board testing mode. See [Hardware Test Mode](Hardware-Test-Mode.md)

1
First-Engine-Start.md Normal file
View File

@ -0,0 +1 @@
Please see here: [HOWTO Get Running](HOWTO-Get-Running.md)

View File

@ -47,7 +47,7 @@ TBD
see also [Fuel Overview](Fuel-Overview)
see also [Ignition](Ignition)
see also [Idle Control](Idle-Control)
see also [Idle Control](Idle-Control.md)
see also [this forum thread](http://rusefi.com/forum/viewtopic.php?f=2&t=1124&p=21278)
## Share your tune

View File

@ -1,4 +1,4 @@
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project)
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project.md)
# Summary
@ -73,7 +73,7 @@ Place some place that is away from hot items like the exhaust. Mount on a piece
* Wire rusEFI like Frankenstein as shown below
![Frankenstein wired with connector breakout](Images/Aspire_20140306_state.jpg)
![Frankenstein wired in enclosure](Images/P1050839_zpsfdbdbd97.jpg)
* 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)
* 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)
* 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
@ -153,7 +153,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)
See also [Debug Fields](Debug-Fields.md)
## External links

View File

@ -1,4 +1,4 @@
See also [HOWTO-Crimp-Ampseal](HOWTO-Crimp-Ampseal)
See also [HOWTO-Crimp-Ampseal](HOWTO-Crimp-Ampseal.md)
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".

View File

@ -3,7 +3,7 @@ Remote tuning is possible over Internet using rusEFI TunerStudio plugin if rusEF
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)
3) [rusEFI Android application](rusEFI-Android.md)
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.

View File

@ -81,7 +81,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)
See also [Debug Fields](Debug-Fields.md)
## External links

View File

@ -3,7 +3,7 @@
[Download the rusEFI bundle](Download) for your hardware.
## Windows:
Launch [rusEFI Console](Console). You can find it in the bundle you downloaded, in the "console" folder.
Launch [rusEFI Console](Console.md). 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.
@ -29,7 +29,7 @@ dfu-util -a 0 -D rusefi.dfu
## More Information
For more about DFU see [HOWTO-DFU](HOWTO-DFU)
For more about DFU see [HOWTO-DFU](HOWTO-DFU.md)
ST-LINK is an advanced mode of firmware update which requires ST-LINK device, either external, or built-in like on Discovery/Nucleo board.

View File

@ -1,4 +1,4 @@
## Please post your tune & log files at [rusEFI Online](Online). More on that in [Support](Support)
## Please post your tune & log files at [rusEFI Online](Online.md). More on that in [Support](Support)
---
@ -6,7 +6,7 @@
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) Take a look through the [forum]([https://rusefi.com/forum](https://rusefi.com/forum)/search.php) or read through the [FAQs.](Pages-FAQs)
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](https://rusefi.com/forum)/search.php) or read through the [FAQs.](Pages-FAQs)
If after that you still need direct help then please have a read of the information below and help us to help you.

View File

@ -1,6 +1,6 @@
* 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)
* Please upload your best rusEFI tune to rusEFI Online [HOWTO-upload-tune](HOWTO-upload-tune.md)
* Please upload a few interesting log files to rusEFI online - a starting/warm-up log, a wide open throttle driving log etc.

View File

@ -3,14 +3,14 @@
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)
[HOWTO contribute success stories](HOWTO-contribute-success-stories.md)
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)
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)
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.md)
## Please do good and do not do bad

View File

@ -5,7 +5,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)
Before joining slack please read the section on [asking questions.](HOWTO-ask-questions.md)
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

View File

@ -22,9 +22,9 @@
Your board comes with rusEFI firmware installed on it, but it should be updated.
[How to update your firmware](HOWTO-Update-Firmware)
[How to update your firmware](HOWTO-Update-Firmware.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)
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)
## Plug and Play (PNP) Initial Setup
@ -88,7 +88,7 @@ And we're done with the initial startup. Congratulations- you have your car runn
## FAQ
Q: How do I change settings?
A: You can change settings and your engine tune using [TunerStudio](HOWTO-create-tunerstudio-project).
A: You can change settings and your engine tune using [TunerStudio](HOWTO-create-tunerstudio-project.md).
Q: Is there anything special I need to do to wire USB from ECU harness?
@ -112,20 +112,20 @@ A: For most of the pinout changes to be applied you need to reset rusEFI. Do not
## rusEFI Console
[rusEFI Console](Console) is a handy development and debugging tool. Try it out and learn what it is capable of.
[rusEFI Console](Console.md) 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)
[HOWTO create TunerStudio project](HOWTO-create-tunerstudio-project.md)
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
See also [Tunerstudio Connectivity](Tunerstudio-Connectivity.md)
## Tuning the engine
[Get Running](HOWTO-Get-Running)
[Get Running](HOWTO-Get-Running.md)
[Get Tuning](Get-tuning-with-TunerStudio-and-your-rusEFI)
[Get Tuning](Get-tuning-with-TunerStudio-and-your-rusEFI.md)
[Error Codes](Error-Codes)

View File

@ -1 +0,0 @@
Please see here: [HOWTO Get Running](HOWTO-Get-Running)

View File

@ -1,19 +0,0 @@
#Master list of HOW TO pages
<details><summary><u>HOW TO</u></summary>
* [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)
</details>

View File

@ -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.md)?

View File

@ -7,13 +7,13 @@
- checkout other's tunes
See [HOWTO set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
See [HOWTO set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token.md)
See [HOWTO upload tune](HOWTO-upload-tune)
See [HOWTO upload tune](HOWTO-upload-tune.md)
See [HOWTO upload log](HOWTO-upload-log)
See [HOWTO upload log](HOWTO-upload-log.md)
See [HOWTO Remote Tuning](HOWTO-Remote-Tuning)
See [HOWTO Remote Tuning](HOWTO-Remote-Tuning.md)
![x](https://github.com/rusefi/web_backend/blob/master/documentation/rusEFI%20remote.png)

View File

@ -2,8 +2,8 @@
<details><summary><u>FAQs</u></summary>
* [Ignition](FAQ-Ignition)
* [Basic Wiring and Connections](FAQ-Basic-Wiring-and-Connections)
* [Ignition](FAQ-Ignition.md)
* [Basic Wiring and Connections](FAQ-Basic-Wiring-and-Connections.md)
</details>

View File

@ -26,7 +26,7 @@
<details><summary><u>AFR measurement</u></summary>
* [Wide Band Sensors](Wide-Band-Sensors)
* [Wide Band Sensors](Wide-Band-Sensors.md)
* [Do I need a wideband](do-i-need-wideband-oxygen-sensor)
* [Old WBO2 page](WBO)
@ -37,7 +37,7 @@
* [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)
* [Fuel injectors](Fuel-Injectors.md)
</details>

19
Pages-HOWTO.md Normal file
View File

@ -0,0 +1,19 @@
#Master list of HOW TO pages
<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)
* [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)
</details>

View File

@ -2,6 +2,6 @@
## 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)
[Sensors](Vault-Of-Sensors)
[Terminology and abbreviations](Vault-Of-Terminology)
[Ignition Parts](Vault-Of-Ignition-Parts.md)
[Sensors](Vault-Of-Sensors.md)
[Terminology and abbreviations](Vault-Of-Terminology.md)

View File

@ -10,23 +10,23 @@
<details><summary><u>General Firmware info</u></summary>
* [Preferred Code Style](Code-Style)
* [Debug Mode](Debug-Mode)
* [Debug Mode](Debug-Mode.md)
* [Performance Tracing](Developer-Performance-Tracing)
* [Firmware Downloads](Downloads)
* [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)
* [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)
* [Developing On Linux](Developing-On-Linux)
* [rusEFI Bundle](rusEFI-bundle)
* [rusEFI Bundle](rusEFI-bundle.md)
</details>
<details><summary><u>Firmware Features</u></summary>
* See also -> [rusEFI Project Overview](rusEFI-project)
* [FSIO](FSIO)
* [Virtual Simulator](Virtual-simulator)
* [FSIO](FSIO.md)
* [Virtual Simulator](Virtual-simulator.md)
</details>

Some files were not shown because too many files have changed in this diff Show More