fix md syntax and hierarchy
This commit is contained in:
mi-hol
parent
18b4dcb9b3
commit
ffa9e410fa
|
|
@ -2,6 +2,7 @@
|
|||
"cSpell.words": [
|
||||
"Acura",
|
||||
"Altima",
|
||||
"Andrey",
|
||||
"Aristo",
|
||||
"autotune",
|
||||
"Avenir",
|
||||
|
|
|
|||
|
|
@ -1,10 +1,16 @@
|
|||
# Hellen 154 Hyundai
|
||||
|
||||
[Issue tracker & Repository](https://github.com/rusefi/hellen154hyundai)
|
||||
|
||||
[pinout](https://rusefi.com/docs/pinouts/hellen/hellen154hyundai/)
|
||||
|
||||
[[Schematics rev c]][Hardware/Hellen/hellen154hyundai-c-schematic.pdf]([ibom rev c)](https://rusefi.com/docs/ibom/hellen154hyundai-c-ibom.html)
|
||||
[Schematics rev c](Hardware/Hellen/hellen154hyundai-c-schematic.pdf)
|
||||
|
||||
[[Schematics rev b]][Hardware/Hellen/hellen154hyundai-b-schematic.pdf]([ibom rev b)](https://rusefi.com/docs/ibom/hellen154hyundai-b-ibom.html)
|
||||
[ibom rev c](https://rusefi.com/docs/ibom/hellen154hyundai-c-ibom.html)
|
||||
|
||||
[Schematics rev b](Hardware/Hellen/hellen154hyundai-b-schematic.pdf)
|
||||
|
||||
[ibom rev b](https://rusefi.com/docs/ibom/hellen154hyundai-b-ibom.html)
|
||||
|
||||
[fw snapshot](https://rusefi.com/build_server/rusefi_bundle_hellen154hyundai.zip)
|
||||
|
||||
|
|
@ -29,12 +35,12 @@ the thing is, the harness changes slightly between the years
|
|||
|
||||
## Changelog
|
||||
|
||||
# Rev C
|
||||
### Rev C
|
||||
|
||||
* Molex Aux connector
|
||||
* ETB issue fixed
|
||||
|
||||
# Rev B
|
||||
### Rev B
|
||||
|
||||
* It's alive
|
||||
* ETB requires a hardware mod
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
# Knowledge sharing and Channels
|
||||
|
||||
TL,DR: are you interested in any knowledge being indexed by google and are you interested in any knowledge outliving your rusEFI involvment? Are you interested in the social aspect of the rusEFI Slack lounge?
|
||||
|
||||
TL,DR: please post knowledge on forum and report issues at [https://github.com/rusefi/rusefi/issues](https://github.com/rusefi/rusefi/issues)
|
||||
|
|
|
|||
12
Support.md
12
Support.md
|
|
@ -1,21 +1,23 @@
|
|||
# Support
|
||||
|
||||
[TL,DR](Knowledge-best-practices-and-Channels#q-i-need-help)
|
||||
|
||||
rusEFI is a community-driven free open source project. It comes with zero warranty and zero promises including zero promises of technical support.
|
||||
|
||||
rusEFI has zero full time staff and most of rusEFI contributors all over the globe have day jobs and other obligations.
|
||||
|
||||
[[https://rusefi.com/forum/](https://rusefi.com/forum/)](<https://rusefi.com/forum/>) is the primary free support channel. Please post your tune & log files at [rusEFI Online](Online).
|
||||
[https://rusefi.com/forum/](https://rusefi.com/forum/) is the primary free support channel. Please post your tune & log files at [rusEFI Online](Online).
|
||||
|
||||
Please Read [How To Ask Technical Questions](https://opensource.com/life/16/10/how-ask-technical-questions)
|
||||
|
||||
## Q: What is Slack?
|
||||
|
||||
A: Slack is a group chat available via browser and phone app. After initial problem statement is defined on [[https://rusefi.com/forum/](https://rusefi.com/forum/)](<https://rusefi.com/forum/>) Slack often comes handy for follow-up discussion. Slack registration [http://rusefi.com/slack/](http://rusefi.com/slack/) and login [https://rusefi.slack.com/](https://rusefi.slack.com/)
|
||||
A: Slack is a group chat available via browser and phone app. After initial problem statement is defined on [https://rusefi.com/forum/](https://rusefi.com/forum/) Slack often comes handy for follow-up discussion. Slack registration [http://rusefi.com/slack/](http://rusefi.com/slack/) and login [https://rusefi.slack.com/](https://rusefi.slack.com/)
|
||||
|
||||
## Q: Do you guys prefer short text descriptions or long text descriptions?
|
||||
|
||||
A: We prefer longer problem descriptions with as much of supporting material as possible. Screen shots, videos etc.
|
||||
Just a reminder that to attach a screen shot to the forum post you LITERLLY need to hit under 6 keys.
|
||||
Just a reminder that to attach a screen shot to the forum post you LITERALLY need to hit under 6 keys.
|
||||
|
||||
"ctrl-print screen" or "alt-print screen" to take a screenshot into clipboard
|
||||
"ctrl-v" to attach image from clipboard into forum post.
|
||||
|
|
@ -30,7 +32,7 @@ A: rusEFI is not specific to a particular vehicle. The people involved own and
|
|||
|
||||
### Q: I have 2009 AXP with TAMTAM. Help me. ("AXP" and "TAMTAM" are made up to illustrate that the particulars really don't matter here.)
|
||||
|
||||
A: You are very unlikely to get much help asking for support like this. rusEFI helps those that are willing to help themselves. We do not have the have time or bandwidth to provide handholding for specific setups or features. Unless you want to become involved in the development process as a contributor, it is very unlikely that we will "just get around to it" in the next year.
|
||||
A: You are very unlikely to get much help asking for support like this. rusEFI helps those that are willing to help themselves. We do not have the have time or bandwidth to provide hand holding for specific setups or features. Unless you want to become involved in the development process as a contributor, it is very unlikely that we will "just get around to it" in the next year.
|
||||
|
||||
Please feel free to familiarize yourself with the available open source files and submit a PR to enable the functionality required to meet your needs.
|
||||
|
||||
|
|
@ -89,7 +91,7 @@ Tell us about your engine setup. Something like the below.
|
|||
|-|-|-|-|-|
|
||||
|1|port|distributor|gasoline/petrol|turbo|
|
||||
|2|batch|COP|diesel|supercharger|
|
||||
|4|direct|CNP|propane|Natrually Aspirated|
|
||||
|4|direct|CNP|propane|Naturally Aspirated|
|
||||
|6|no fuel control|no spark control|ethanol|
|
||||
|8||wasted spark|
|
||||
|12|other|other|other|other|
|
||||
|
|
|
|||
|
|
@ -1,16 +1,20 @@
|
|||
# microRusEFI DIY
|
||||
|
||||
Bare minimum microRusEFI instructions:
|
||||
|
||||
# Step 1 80% ready microRusEFI
|
||||
## Step 1 80% ready microRusEFI
|
||||
|
||||
Fabricate "pre-populated" 80% ready microRusEFI at [https://jlcpcb.com/](https://jlcpcb.com/)
|
||||
|
||||
You would need three files to do that - gerbers archive, BOM and placement files."
|
||||
|
||||
Current version as of April 7, 2020 is 0.4.8
|
||||
Check for latest version in repository.
|
||||
|
||||
[[https://github.com/rusefi/hw_microRusEfi](https://github.com/rusefi/hw_microRusEfi)/tree/master/gerbers/0.4.8](<https://github.com/rusefi/hw_microRusEfi/tree/master/gerbers/0.4.8>)
|
||||
[https://github.com/rusefi/hw_microRusEfi](https://github.com/rusefi/hw_microRusEfi)
|
||||
|
||||
# Step 2 Finish assembly
|
||||
[https://github.com/rusefi/hw_microRusEfi)/tree/master/gerbers](https://github.com/rusefi/hw_microRusEfi/tree/master/gerbers/)
|
||||
|
||||
## Step 2 Finish assembly
|
||||
|
||||
Order the following 8 parts:
|
||||
|
||||
|
|
@ -23,13 +27,13 @@ Order the following 8 parts:
|
|||
|
||||
[Saved Cart on Mouser](https://www.mouser.com/ProjectManager/ProjectDetail.aspx?AccessID=dacd727e05)
|
||||
|
||||
# Step 3 Upload firmware
|
||||
## Step 3 Upload firmware
|
||||
|
||||
Once you solder 8 parts to your 80% ready microRusEFI upload firmware into micro-controller
|
||||
|
||||
[https://rusefi.com/build_server/rusefi_bundle_mre_f4.zip](https://rusefi.com/build_server/rusefi_bundle_mre_f4.zip)
|
||||
|
||||
# More info
|
||||
## More info
|
||||
|
||||
More info like connector & case see [https://github.com/rusefi/hw_microRusEfi](https://github.com/rusefi/hw_microRusEfi)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue