diff --git a/Components/Shadow-Dash.md b/Components/Shadow-Dash.md index 8184a1d2..af669ba3 100644 --- a/Components/Shadow-Dash.md +++ b/Components/Shadow-Dash.md @@ -1,4 +1,4 @@ -In order to use Shadow Dash with rusEfi, you would need to copy rusefi.ini file into .efiAnalytics\config\ecuDef folder on your Android device and rename it to 'unknown.ini' +In order to use Shadow Dash with rusEFI, you would need to copy rusefi.ini file into .efiAnalytics\config\ecuDef folder on your Android device and rename it to 'unknown.ini' I've used ES File Explorer since Windows does not show hidden folders - and .efiAnalytics is a hidden folder. In ES File Explorer settings I have 'show hidden files' checkbox enabled. diff --git a/Dev/Dev-Console-Implementation.md b/Dev/Dev-Console-Implementation.md index 5b5a5448..3e8f6311 100644 --- a/Dev/Dev-Console-Implementation.md +++ b/Dev/Dev-Console-Implementation.md @@ -1,12 +1,12 @@ ## human readable protocol -A typical line in rusEfi human-readable protocol look like +A typical line in rusEFI human-readable protocol look like `line:16:rpm,100,maf,3.3,` Here `line` is a magic prefix, `16` is the length of the payload, and the payload `rpm,100,maf,3.3,` is a comma separated list of keys and pairs, let's call this "a line of known length" -As for sending commands to rusEfi, there are two options +As for sending commands to rusEFI, there are two options a) plain unwrapped command, for example @@ -16,7 +16,7 @@ b) a command with specified length (this case the firmware can validate the comm `sec!7!rpm 400` -Pretty much same was as with data coming from rusEfi, we have a prefix `sec` and `7` for the payload length. +Pretty much same was as with data coming from rusEFI, we have a prefix `sec` and `7` for the payload length. TODO: unify `line` and sec `one` day? ## java classes diff --git a/Dev/Dev-Status.md b/Dev/Dev-Status.md index 10c1d00e..d2507924 100644 --- a/Dev/Dev-Status.md +++ b/Dev/Dev-Status.md @@ -409,7 +409,7 @@ Engine chart size [SPI settings](rusEFI-project-Controller#spi-settings) (🔶): SPI communication configuration -[rusEfi Console Settings](rusEFI-project-Controller#rusefi-console-settings) +[rusEFI Console Settings](rusEFI-project-Controller#rusefi-console-settings) (💚): rusEFI console configuration [Connection](rusEFI-project-Controller#connection) diff --git a/Documentation-Workflow.md b/Documentation-Workflow.md index 97b85a29..d84cb1f2 100644 --- a/Documentation-Workflow.md +++ b/Documentation-Workflow.md @@ -9,7 +9,7 @@ For example, in order for user abelom to edit this page: 1) abelom would start editing at https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md which would automatically create a branch in https://github.com/abelom/rusefi_documentation fork 2) Once changed are made, abelom would create a Pull Request -3) Once that PR is merged into primary rusEfi modified content would appear as https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md +3) Once that PR is merged into primary rusEFI modified content would appear as https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md 4) Within the next 5 minutes automation would sync this page into wiki git and it would be available with nicer layout as https://github.com/rusefi/rusefi/wiki/Documentation_Workflow Same but in different terms: @@ -29,9 +29,9 @@ Long story short, for images to work correctly both in the technical git and the (More details: Please note that all .md files like https://github.com/rusefi/rusefi_documentation/blob/master/FAQ/HOWTO_quick_start.md are displayed without folder name like https://github.com/rusefi/rusefi/wiki/HOWTO_quick_start - which also means -that you need full image path like ``FAQ/images/rusEfi_console/rusEfi_console_start_screen.png`` for the image to be rendered properly. This is one of the github wiki features which are a bit counter-intuitive to me. +that you need full image path like ``FAQ/images/rusEFI_console/rusEFI_console_start_screen.png`` for the image to be rendered properly. This is one of the github wiki features which are a bit counter-intuitive to me. This also means that .md file names have to be unique for the whole.) **Q:** What sort of fancy options do we have? -**A:** We can do collapsible sections & hints sections! See [cranking](Cranking) for an example. \ No newline at end of file +**A:** We can do collapsible sections & hints sections! See [cranking](Cranking) for an example. diff --git a/FAQ/rusEFI-chat.md b/FAQ/rusEFI-chat.md index 31b40691..92ec5607 100644 --- a/FAQ/rusEFI-chat.md +++ b/FAQ/rusEFI-chat.md @@ -1,8 +1,8 @@ -[rusEfi forum](https://rusefi.com/forum/) is the central meeting point for everything rusEfi but there are also: +[rusEFI forum](https://rusefi.com/forum/) is the central meeting point for everything rusEFI but there are also: - Slack at https://rusefi.slack.com/ see https://rusefi.com/forum/viewtopic.php?t=1198 - Russian-speaking Skype group channel - стукнитесь в arro239 в Скайпе, чтобы добавиться. -- https://www.facebook.com/rusEfiECU/ \ No newline at end of file +- https://www.facebook.com/rusEfiECU/ diff --git a/Fuel/Wide-Band-Sensors.md b/Fuel/Wide-Band-Sensors.md index 78045360..4f7c33cf 100644 --- a/Fuel/Wide-Band-Sensors.md +++ b/Fuel/Wide-Band-Sensors.md @@ -3,7 +3,7 @@ A reliable measurement of the AFR is vital for the tuner to be able to tune the engine and be sure that his changes to the fueling are correct. For this purpose we recommend one of the readily available aftermarket wideband gauges or controllers. A wide-band oxygen sensor is pretty much a must for what we are doing here. Bosch is the only manufacturer of these sensors I am aware of. The wide-band precision of the sensor is achieved by a relatively sophisticated magic which happens inside the sensor, that's why 5 or 6 wises and that's why the sensor requires it's own controller (brain). Since there are at least two kinds of sensors it's safer to buy a kit. -As of April 2016 rusEfi does not have build-in WBO controller. +As of April 2016 rusEFI does not have build-in WBO controller. Wide-band controllers range from $35.00 for http://www.14point7.com/products/slc-free ($85 with sensor) all the way to high-200 for kits with a gauge. diff --git a/HOWTO/CAN-Sniffer.md b/HOWTO/CAN-Sniffer.md index 864c8d3e..e55f30f7 100644 --- a/HOWTO/CAN-Sniffer.md +++ b/HOWTO/CAN-Sniffer.md @@ -1,4 +1,4 @@ -## HOWTO use custom build of rusEfi for CAN bus sniffing +## HOWTO use custom build of rusEFI for CAN bus sniffing In this HOWTO I will explain how to see raw CAN message flow with less than $30 in hardware & some free software. diff --git a/HOWTO/Console.md b/HOWTO/Console.md index 0b9a4ca1..b793495c 100644 --- a/HOWTO/Console.md +++ b/HOWTO/Console.md @@ -6,7 +6,7 @@ You can sniff either trigger angles or MAP values. -Analog chart tab in java console is a very, very plain oscilloscope build into rusEfi firmware. +Analog chart tab in java console is a very, very plain oscilloscope build into rusEFI firmware. Analog chart always displays the signal for a duration of one complete engine cycle. diff --git a/HOWTO/Debug-Fields.md b/HOWTO/Debug-Fields.md index 38d058f4..14af8200 100644 --- a/HOWTO/Debug-Fields.md +++ b/HOWTO/Debug-Fields.md @@ -1,4 +1,4 @@ -Debug fields is an advanced troubleshooting feature allowing one to monitor internal state of some rusEfi subsystems. In an ideal world we would be always saving all these data points, in reality we need to only save those while troubleshooting something specific. +Debug fields is an advanced troubleshooting feature allowing one to monitor internal state of some rusEFI subsystems. In an ideal world we would be always saving all these data points, in reality we need to only save those while troubleshooting something specific. `set debug_mode CODE` diff --git a/HOWTO/Debug-Mode.md b/HOWTO/Debug-Mode.md index f9e1a088..de5f38f1 100644 --- a/HOWTO/Debug-Mode.md +++ b/HOWTO/Debug-Mode.md @@ -1,4 +1,4 @@ -Debug fields is an advanced troubleshooting feature allowing one to monitor the internal state of some rusEfi subsystems. +Debug fields is an advanced troubleshooting feature allowing one to monitor the internal state of some rusEFI subsystems. In TunerStudio, select "Base Engine Settings -> Debug Mode" and use the gauges from "Debug" category. diff --git a/HOWTO/Engine-Types.md b/HOWTO/Engine-Types.md index eb973e8a..63d363b4 100644 --- a/HOWTO/Engine-Types.md +++ b/HOWTO/Engine-Types.md @@ -1,8 +1,8 @@ Update 2017: things are much more settled these days, at least 6 months without an incompatible configuration format change. -The best way to configure rusEfi according to your engine setup is via Tuner Studio - there are not many settings there, it should be to some expend self-explanatory. In case of any questions your best chance at the moment is to ask questions on the forum - there are still not enough walk-troughs and articles. +The best way to configure rusEFI according to your engine setup is via Tuner Studio - there are not many settings there, it should be to some expend self-explanatory. In case of any questions your best chance at the moment is to ask questions on the forum - there are still not enough walk-troughs and articles. -But rusEfi is still in the phase of active development: some parts of the code are still far from final, and new configuration parameters are being added every month. Because of that, the TunerStudio project definition is still pretty volatile. Volatile TunerStudio project definition means your settings could be lost next time you upgrade the firmware, because of that we need a way to keep default configurations for each setup in a more persistent way. This is the reason why we have... +But rusEFI is still in the phase of active development: some parts of the code are still far from final, and new configuration parameters are being added every month. Because of that, the TunerStudio project definition is still pretty volatile. Volatile TunerStudio project definition means your settings could be lost next time you upgrade the firmware, because of that we need a way to keep default configurations for each setup in a more persistent way. This is the reason why we have... Engine Type concept: we have an array of default configurations for different engines defined [right in the source code](https://github.com/rusefi/rusefi/tree/master/firmware/config/engines). Which of the configurations is used is controlled by 'engine type' field which is persisted in the internal chip flash memory along with the rest of the configuration. So, in order to get your trigger decoding parameters and your fuel & injection control strategies activated, you need to invoke the 'set engine_type X' command as described [http://rusefi.com/forum/viewtopic.php?f=5&t=210#p4038 here]. diff --git a/HOWTO/FSIO.md b/HOWTO/FSIO.md index 40248a58..d030f4b2 100644 --- a/HOWTO/FSIO.md +++ b/HOWTO/FSIO.md @@ -2,11 +2,11 @@ ## The content below is mostly from 2018 and is in the process of being updated. This wiki article needs to be viewed as a work in progress at this time and may contain contradictory information. -Flexible Logic is the fanciest-schmanciest feature of rusEfi. Using the FSIO a user can quickly add a logical function directly into the program of the ECU. +Flexible Logic is the fanciest-schmanciest feature of rusEFI. Using the FSIO a user can quickly add a logical function directly into the program of the ECU. -Flexible Logic allows advanced users to get unprecedented level of configurability for custom outputs and engine control. rusEfi supports up to 16 flexible outputs, each of these could be either an on/off or PWM signal. In case of a PWM signal the frequency is defined in the configuration and the duty cycle is dynamically controlled by the evaluated expression. +Flexible Logic allows advanced users to get unprecedented level of configurability for custom outputs and engine control. rusEFI supports up to 16 flexible outputs, each of these could be either an on/off or PWM signal. In case of a PWM signal the frequency is defined in the configuration and the duty cycle is dynamically controlled by the evaluated expression. -For FSIO, rusEfi console provides a better user experience due to automated human to RPN conversion. +For FSIO, rusEFI console provides a better user experience due to automated human to RPN conversion. --- diff --git a/HOWTO/Feature-Requests-the-Feature-Bounty-Program.md b/HOWTO/Feature-Requests-the-Feature-Bounty-Program.md index 0e418f74..afb953a7 100644 --- a/HOWTO/Feature-Requests-the-Feature-Bounty-Program.md +++ b/HOWTO/Feature-Requests-the-Feature-Bounty-Program.md @@ -1,5 +1,5 @@ -The challenge of rusEfi as of 2020 is the fact that hardware is way ahead of software at this point. With just a few programmers and the complexity of the project, it would be a while until normal users would be benefiting from rusEfi because of the complexity and knowledge required. +The challenge of rusEFI as of 2020 is the fact that hardware is way ahead of software at this point. With just a few programmers and the complexity of the project, it would be a while until normal users would be benefiting from rusEFI because of the complexity and knowledge required. -But if for any reason you would prefer to use rusEfi and look for any specific feature, money can probably help you! +But if for any reason you would prefer to use rusEFI and look for any specific feature, money can probably help you! -See also https://rusefi.com/forum/viewtopic.php?f=5&t=1642 \ No newline at end of file +See also https://rusefi.com/forum/viewtopic.php?f=5&t=1642 diff --git a/HOWTO/HOWTO-Get-Running.md b/HOWTO/HOWTO-Get-Running.md index 9307079e..a11850fe 100644 --- a/HOWTO/HOWTO-Get-Running.md +++ b/HOWTO/HOWTO-Get-Running.md @@ -81,11 +81,11 @@ http://www.littelfuse.com/~/media/automotive/datasheets/fuses/passenger-car-and- Once connected you should test the wires. Especially the power wires like coil wires and injector wires. A poor connection with a slight resistance like .1 ohms can cause an electrical fire, which I'm sure you do not want. Once everything is connected measure both the voltage drop and current from the ECU connector, or where ever is applicably appropriate. Using your voltage and current readings, calculate the ohms, if it's above about .1 ohms fix the issue. Take note that .1 ohms at 1A is about .1watt that that connection will have to dissipate. If you have a 12 cyl, and 12 .1 ohm connections, the connector will have to dissipate 1.2 watts. -HOWTO start you engine with rusEfi for the first time +HOWTO start you engine with rusEFI for the first time ### test outputs -Both rusEfi console and TS allows you to test if rusEfi properly controls things like injectors (you would hear the clicks), cooling fan (you would hear it - if needed), fuel pump (you would usually hear it - if needed), ignition coil (that's challenging if you have a distributor) +Both rusEFI console and TS allows you to test if rusEFI properly controls things like injectors (you would hear the clicks), cooling fan (you would hear it - if needed), fuel pump (you would usually hear it - if needed), ignition coil (that's challenging if you have a distributor) ## get tachometer showing correct cranking rpm @@ -101,13 +101,13 @@ Assuming you have the hardware ready to spark we now need to find your TDC posit Set cranking advance angle to zero for now. Use a timing gun while cranking. We now need to try different values of Engine->Trigger->global trigger angle offset until we get spark at zero advance - that's because we might know the relation between TDC#1 and trigger signal. -On Engine Sniffer tab of rusEfi console TDC#1 is shown with the green vertical line. +On Engine Sniffer tab of rusEFI console TDC#1 is shown with the green vertical line. ![Initial Cranking Parameters](Images/Initial_cranking_parameters.png) ## cranking parameters -rusEfi has separate cranking control strategy for your first couple of engine revolutions - usually you want more fuel, different timing and simultaneous injection to start an engine. +rusEFI has separate cranking control strategy for your first couple of engine revolutions - usually you want more fuel, different timing and simultaneous injection to start an engine. ![Cranking Dialog](Images/Cranking_dialog_jan_2017.png) @@ -137,7 +137,7 @@ One plain MAF workk next step is running with proper MAP sensor calibration & fl There are three ways to produce similar logs - the intention is for these three to have same exact data. 1. SD card logging -2. rusEfi console logging +2. rusEFI console logging 3. TunerStudio logging See also https://svn.code.sf.net/p/rusefi/code/trunk/firmware/console/binary/tunerstudio_configuration.h diff --git a/HOWTO/HOWTO-Miata-NB2-on-Proteus.md b/HOWTO/HOWTO-Miata-NB2-on-Proteus.md index 7a4df9f8..16fcbc69 100644 --- a/HOWTO/HOWTO-Miata-NB2-on-Proteus.md +++ b/HOWTO/HOWTO-Miata-NB2-on-Proteus.md @@ -29,7 +29,7 @@ Two 23 pins Ampseal extension connectors allows you to wire more functions like The board pin mapping for OEM connector follows the tab given in the Pinning section below. -![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png) +![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png) For the extension connectors the pinnig is the following \: diff --git a/HOWTO/HOWTO-ask-questions.md b/HOWTO/HOWTO-ask-questions.md index b41dae1c..e440b32c 100644 --- a/HOWTO/HOWTO-ask-questions.md +++ b/HOWTO/HOWTO-ask-questions.md @@ -17,7 +17,7 @@ If after that you still need direct help then please have a read of the informat 1) In TunerStudio, Use "DataLogging">"Start Logging" menu item. Logs are written to Documents\TunerStudioProjects\NAMEOFYOURPROJECT\DataLogs folder. - 2) With rusEfi console, simply grab the latest .msl file from "out" folder + 2) With rusEFI console, simply grab the latest .msl file from "out" folder ## HOWTO Ask Technical Questions @@ -35,4 +35,4 @@ An example of a question asked with helpful background information: https://rusefi.com/forum/viewtopic.php?f=3&t=1282&start=101 -![video](FAQ/images/fantastic-story-video-or-it-never-happened.jpg) \ No newline at end of file +![video](FAQ/images/fantastic-story-video-or-it-never-happened.jpg) diff --git a/HOWTO/HOWTO-contribute-to-documentation.md b/HOWTO/HOWTO-contribute-to-documentation.md index a26d416e..8303dcd5 100644 --- a/HOWTO/HOWTO-contribute-to-documentation.md +++ b/HOWTO/HOWTO-contribute-to-documentation.md @@ -14,7 +14,7 @@ This would produce a [Pull request like this](https://github.com/rusefi/rusefi_d https://github.com/rusefi/rusefi/blob/master/firmware/tunerstudio/rusefi.input -#### How to contribute to rusEfi TunerStudio project +#### How to contribute to rusEFI TunerStudio project Same as above, fork https://github.com/rusefi/rusefi and edit your local copy of diff --git a/HOWTO/HOWTO-contribute-to-firmware.md b/HOWTO/HOWTO-contribute-to-firmware.md index 0f4e9e4d..33f7776f 100644 --- a/HOWTO/HOWTO-contribute-to-firmware.md +++ b/HOWTO/HOWTO-contribute-to-firmware.md @@ -1,4 +1,4 @@ -The majority of rusEfi code is written in very plain C++ ("C with classes"), with rusEfi console and some code generating +The majority of rusEFI code is written in very plain C++ ("C with classes"), with rusEFI console and some code generating tools written in java. Most of the needs are within the C/C++ firmware and automated testing. @@ -15,7 +15,7 @@ Testing coverage open tickets: https://github.com/rusefi/rusefi/labels/automated All open tickets: https://github.com/rusefi/rusefi/issues -See [Try It](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) diff --git a/HOWTO/HOWTO-electronic-throttle-body-configuration.md b/HOWTO/HOWTO-electronic-throttle-body-configuration.md index bc61e825..8dc2d67e 100644 --- a/HOWTO/HOWTO-electronic-throttle-body-configuration.md +++ b/HOWTO/HOWTO-electronic-throttle-body-configuration.md @@ -51,7 +51,7 @@ https://www.youtube.com/watch?v=USU0nnekokA ### Start with autotune -rusEfi has auto-tuning software that can help generate a starting point for your PID settings. +rusEFI has auto-tuning software that can help generate a starting point for your PID settings. ### _Ensure the engine is off! Do not attempt to start the engine during this process!_ @@ -67,4 +67,4 @@ The pedal map allows you to configure how the electronic throttle's position res This table is really one to tune to taste, since it has no bearing on actual engine performance, only on the relationship between driver input and resulting throttle position. -[//]: # "Matt Kennedy" \ No newline at end of file +[//]: # "Matt Kennedy" diff --git a/HOWTO/HOWTO-help-rusEFI.md b/HOWTO/HOWTO-help-rusEFI.md index d40ae6c3..d352f230 100644 --- a/HOWTO/HOWTO-help-rusEFI.md +++ b/HOWTO/HOWTO-help-rusEFI.md @@ -7,7 +7,7 @@ The weakest point of rusEFI is lack of samples and success stories. As of Aug 20 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) We are also extremely short on software developers. [HOWTO contribute to firmware](HOWTO-contribute-to-firmware) @@ -27,4 +27,4 @@ There are two ways to help financially: One-time or monthly https://tinyurl.com/paypal-rusefi -One-time or monthly [rusEfi Patreon](https://www.patreon.com/rusefi) +One-time or monthly [rusEFI Patreon](https://www.patreon.com/rusefi) diff --git a/HOWTO/HOWTO-quick-start.md b/HOWTO/HOWTO-quick-start.md index 78bb1c71..7343217f 100644 --- a/HOWTO/HOWTO-quick-start.md +++ b/HOWTO/HOWTO-quick-start.md @@ -33,11 +33,11 @@ * Another way to upload firmware is using a [DFU file](HOWTO-DFU) -## rusEfi Console +## rusEFI 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. +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. ![Java Console](Images/java_console_1.png) ![Java Console](Images/java_console_2.png) @@ -60,7 +60,7 @@ To get the console working follow the below procedure, which assumes you have lo [10572.797285] cdc_acm 5-1:1.0: ttyACM0: USB ACM device ``` * In this case, the newly plugged in USB is register to ttyACM0, which you can find on /dev/ttyACM0 -* If you don't already have the Dev Console, get it http://rusefi.com/build_server/rusefi_bundle.zip (part of the same bundle) Take note rusEfi dev console required java 1.7+ +* If you don't already have the Dev Console, get it http://rusefi.com/build_server/rusefi_bundle.zip (part of the same bundle) Take note rusEFI dev console required java 1.7+ * When you launch the Dev Console, it will ask you to select which serial address it should use. However you can specify that when you launch it by specifying a command line parameter as noted below. * Windows `java -jar rusefi_console.jar COM15` @@ -78,7 +78,7 @@ Update: there is also a lazier way to self-stimulate now, you would not need the At this point, the Dev Console should be up and running. Play around with it and see what you can learn. Also note, it as some functionality as noted below. * If used together with the build-in position sensor emulator, the console allows some level of testing on the bench, without a real engine or any additional hardware. The most useful feature is the plain signal sniffer - both real inputs and generated signals can go into it and this is actually quite handy. Another useful feature is the text log. -* You can use the console to invoke rusEfi commands and control the internal flow using the 'Messages Central' tab +* You can use the console to invoke rusEFI commands and control the internal flow using the 'Messages Central' tab ![Messages Central](Images/messages_central.png) ## Tuner Studio @@ -205,11 +205,11 @@ I'd like to try to connect to Tuner Studio and see what happens. I have a USB/TT `4073 Alive` -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. +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 [Tunerstudio Connectivity](Tunerstudio-Connectivity) -## rusEfi firmware +## rusEFI firmware [Trigger](Trigger) @@ -248,10 +248,10 @@ Q: Low side, high side... Too complicated! Where do I hook my coils?! A: There is some variation between vehicles and components. Please use [rusEFI forums](https://rusefi.com/forum) for custom installation help! -Q: I've made some changes in Tuner Studio & hit Burn. 'Need Burn' has appeared but the values are not there after rusEfi reset? +Q: I've made some changes in Tuner Studio & hit Burn. 'Need Burn' has appeared but the values are not there after rusEFI reset? -A: rusEfi does not write to internal flash memory while your engine is running. In order to really write the values into the permanent memory you would need to stop the engine (or disconnect your stimulator). Online tuning is not affected by this issue - you can still tune and the new values would be applied right away, they just would not be saved until you stop the engine. +A: rusEFI does not write to internal flash memory while your engine is running. In order to really write the values into the permanent memory you would need to stop the engine (or disconnect your stimulator). Online tuning is not affected by this issue - you can still tune and the new values would be applied right away, they just would not be saved until you stop the engine. Q: I've remapped some analog inputs and outputs but nothing has changed, looks like the old pins are still used for output? -A: For most of the pinout changes to be applied you need to reset rusEfi. Do not forget to stop the engine so that the new config is saved into internal memory! +A: For most of the pinout changes to be applied you need to reset rusEFI. Do not forget to stop the engine so that the new config is saved into internal memory! diff --git a/HOWTO/Hardware-Test-Mode.md b/HOWTO/Hardware-Test-Mode.md index 26d2d1e8..0b8d15e7 100644 --- a/HOWTO/Hardware-Test-Mode.md +++ b/HOWTO/Hardware-Test-Mode.md @@ -1,8 +1,8 @@ -rusEfi firmware has a **I/O hardware testing mode** feature - this comes handy if you've just soldered some I/O board like Frankenso. +rusEFI firmware has a **I/O hardware testing mode** feature - this comes handy if you've just soldered some I/O board like Frankenso. In order to activate I/O testing board you need to ground pin PB0. (You can confirm the current pin associated with this feature using `showconfig` command.) -Once PB0 is ground, you need to reset rusEfi. +Once PB0 is ground, you need to reset rusEFI. Currently dev console is not supported - in I/O testing mode you need to connect to the firmware using some terminal application like putty or hyperterminal. (TODO: add dev console support, for now you need to use putty) Same as with normal mode, console uses micro USB port for the data flow by default. diff --git a/HOWTO/Idle-Control.md b/HOWTO/Idle-Control.md index ae49171b..b58446cb 100644 --- a/HOWTO/Idle-Control.md +++ b/HOWTO/Idle-Control.md @@ -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 [stepper motors](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 @@ -9,7 +9,7 @@ command, where X should be between 1 and 100. In order to enable automatic idle control you would need `set_idle_enabled 1` command. Another command related to idle is `set idle_position X`, where X is desired idle speed -In case of stepper idle valve, the position is a percent of the total stepper steps. On startup, rusEfi would move stepper all the way in in order order to find zero position. +In case of stepper idle valve, the position is a percent of the total stepper steps. On startup, rusEFI would move stepper all the way in in order order to find zero position. In case of solenoid valve, the % is just the PWM of the control signal - it has nothing to do with the actual percentage of valve opening and you should not expect it to be linear. diff --git a/HOWTO/Logging.md b/HOWTO/Logging.md index 844a637d..efb26c49 100644 --- a/HOWTO/Logging.md +++ b/HOWTO/Logging.md @@ -1,6 +1,6 @@ ## SD card logging -rusEfi supports SD card logging. SD has to be formatted FAT16 or FAT32, up to 32Gb cards are known to work. +rusEFI supports SD card logging. SD has to be formatted FAT16 or FAT32, up to 32Gb cards are known to work. ![Fat Format](Images/Gat_format.png @@ -10,6 +10,6 @@ logs are being written at about 2 megabytes per hour, so the oldest 128Mb card w ![TunerStudio Logging](Images/Ts_logging.png) -In rusEfi console `sdinfo` command could be used to query logging state. +In rusEFI console `sdinfo` command could be used to query logging state. ![SD Info](Images/SD_info.png) diff --git a/HOWTO/MSDroid.md b/HOWTO/MSDroid.md index 77e017bd..963df25e 100644 --- a/HOWTO/MSDroid.md +++ b/HOWTO/MSDroid.md @@ -4,12 +4,12 @@ Then you need to save this file: https://svn.code.sf.net/p/rusefi/code/trunk/fir Move the rusefi.ini file you've just downloaded to MSDroid/ini folder (I've used https://play.google.com/store/apps/details?id=com.estrongs.android.pop for that) -In order to connect msDroid to rusEfi you would need to tap 'App settings' and select the paired Bluetooth device. As of today, msDroid does not turn Bluetooth on automatically. +In order to connect msDroid to rusEFI you would need to tap 'App settings' and select the paired Bluetooth device. As of today, msDroid does not turn Bluetooth on automatically. Current status: partial integration -* List of rusEfi gauges YES -* List of rusEfi menues YES +* List of rusEFI gauges YES +* List of rusEFI menues YES * Simple single-values parameters YES * Gauge values NO diff --git a/HOWTO/Online.md b/HOWTO/Online.md index d8b3cfe8..fb82c216 100644 --- a/HOWTO/Online.md +++ b/HOWTO/Online.md @@ -1,13 +1,13 @@ # rusEFI Online -[rusEFI online](https://rusefi.com/online/) is facilitating data flow within rusEfi open source engine management community. +[rusEFI online](https://rusefi.com/online/) is facilitating data flow within rusEFI open source engine management community. - share your tune - 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) See [HOWTO upload tune](HOWTO-upload-tune) @@ -19,4 +19,4 @@ See [HOWTO Remote Tuning](https://github.com/rusefi/rusefi/wiki/HOWTO-Remote-Tun ![x](https://github.com/rusefi/web_backend/blob/master/documentation/rusEFI%20remote.png) -For development details see https://github.com/rusefi/web_backend \ No newline at end of file +For development details see https://github.com/rusefi/web_backend diff --git a/HOWTO/Pages-HOWTO.md b/HOWTO/Pages-HOWTO.md index d64bddb4..22a2df84 100644 --- a/HOWTO/Pages-HOWTO.md +++ b/HOWTO/Pages-HOWTO.md @@ -14,6 +14,6 @@ * [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) +* [Set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token) - \ No newline at end of file + diff --git a/HOWTO/Pages-Software.md b/HOWTO/Pages-Software.md index 3ce4b0e2..e2cc650f 100644 --- a/HOWTO/Pages-Software.md +++ b/HOWTO/Pages-Software.md @@ -18,7 +18,7 @@ * [How To DFU](HOWTO-DFU) * [How To Update Firmware](HOWTO-Update-Firmware) * [How To Upload a Tune](HOWTO-upload-tune) -* [rusEFI Bundle](HOWTO/rusEFI-bundle.md) +* [rusEFI Bundle](rusEFI-bundle) diff --git a/HOWTO/Troubleshooting.md b/HOWTO/Troubleshooting.md index d57279aa..d27b0410 100644 --- a/HOWTO/Troubleshooting.md +++ b/HOWTO/Troubleshooting.md @@ -1,4 +1,4 @@ -Over the years of developing rusEfi at least 20 of these stm32f4discovery boards were destroyed by just the primary developers. Sometimes we know we've shorted VCC to GND, sometimes the reasons are unknown. TODO: one day we would know more about it +Over the years of developing rusEFI at least 20 of these stm32f4discovery boards were destroyed by just the primary developers. Sometimes we know we've shorted VCC to GND, sometimes the reasons are unknown. TODO: one day we would know more about it TODO: write down safest operation protocols. diff --git a/HOWTO/Tunerstudio-Connectivity.md b/HOWTO/Tunerstudio-Connectivity.md index 8e3e76ce..a74487b5 100644 --- a/HOWTO/Tunerstudio-Connectivity.md +++ b/HOWTO/Tunerstudio-Connectivity.md @@ -24,7 +24,7 @@ you are expected to see a response like this: Q: I try to connect with Tuner Studio and it says "line:532:rusEfiVersion,20140822@4388 Ford Aspire,outpin,c1@PC6,outpin,c2@PA5,ou"? -A: what you have is a piece of rusEfi own console text-based protocol, you need to connect TS to the other port. +A: what you have is a piece of rusEFI own console text-based protocol, you need to connect TS to the other port. Q: how should it look in Tuner Studio mini terminal? diff --git a/HOWTO/rusEFI-bundle.md b/HOWTO/rusEFI-bundle.md index 36495c6a..394280c6 100644 --- a/HOWTO/rusEFI-bundle.md +++ b/HOWTO/rusEFI-bundle.md @@ -1,11 +1,11 @@ -`rusefi.bin` file is compiled rusEfi firmware. Sometimes you would have `rusefi_no_asserts.bin` variation of this file with fewer safety checks. +`rusefi.bin` file is compiled rusEFI firmware. Sometimes you would have `rusefi_no_asserts.bin` variation of this file with fewer safety checks. - `rusefi.dfu` is also compiled rusEfi firmware, that file is used for DFU mode of flashing. + `rusefi.dfu` is also compiled rusEFI firmware, that file is used for DFU mode of flashing. - `rusefi.ini` is TunerStudio project template file, you would use it if you use TunerStudio software to tune your rusEfi unit. + `rusefi.ini` is TunerStudio project template file, you would use it if you use TunerStudio software to tune your rusEFI unit. See http://www.tunerstudio.com/index.php/downloads for TunerStudio download - See http://rusefi.com and https://github.com/rusefi/rusefi_documentation for more information about rusEfi \ No newline at end of file + See http://rusefi.com and https://github.com/rusefi/rusefi_documentation for more information about rusEFI diff --git a/Hardware/Frankenso/Hardware-Frankenso.md b/Hardware/Frankenso/Hardware-Frankenso.md index 4f37d89d..9e862934 100644 --- a/Hardware/Frankenso/Hardware-Frankenso.md +++ b/Hardware/Frankenso/Hardware-Frankenso.md @@ -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) diff --git a/Hardware/Hardware.md b/Hardware/Hardware.md index 510b9c9f..45dadd00 100644 --- a/Hardware/Hardware.md +++ b/Hardware/Hardware.md @@ -8,11 +8,11 @@ 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
+ larger 154x152mm 4-layer board requires a Medium Box shipping rate
+ on-board power supply
+ 20x4 LCD screen
+ joystick
+ works both with external brain boards and on-board stm32 chip
+ knock sensor chip
+ used Denso OEM cases available | on-board 64 pin connector
SD card, USB/TTL, CAN
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.
+ compact 4-layer PCB smaller than 93 x 100 mm
+ on-board power supply
+ knock sensor chip
+ stepper motor IAC controller chip
+ stepper motor IAC controller chip
+ onboard 4-channel "smart" protected ignition drivers
+ bluetooth module
+ supports two packages of on-board stm32 chips | no on-board connector (wired)
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
+ our smaller two-layer board
+ Small Box shipping rate
+ low price
- external 5v power supply required
- external brain board required | no on-board connector (wired)
SD card, USB/TTL, CAN
open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. | +| [Prometheus](https://rusefi.com/forum/viewtopic.php?f=4&t=1215) | + The only rusEFI board with on-board wide band controller.
+ compact 4-layer PCB smaller than 93 x 100 mm
+ on-board power supply
+ knock sensor chip
+ stepper motor IAC controller chip
+ stepper motor IAC controller chip
+ onboard 4-channel "smart" protected ignition drivers
+ bluetooth module
+ supports two packages of on-board stm32 chips | no on-board connector (wired)
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
+ our smaller two-layer board
+ Small Box shipping rate
+ low price
- external 5v power supply required
- external brain board required | no on-board connector (wired)
SD card, USB/TTL, CAN
open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. | | [microRusEfi](Hardware-microRusEFI) | + Available fully assembled!
+ about 10 analog inputs
+ One VR/Hall input channel for crank sensor
+ One Hall input channel for crank sensor
+ 4 injector output channels
+ 4 logic level coil control channels (external igniters could be needed for some coils) | 48-pin connector
On-board DBW
USB, CAN
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
+ 4 layer PCB, 135mm x 82.5mm
+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)
+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)
+ Dual electronic throttles
+ 4x High-side 12v drivers, 1 amp each
+ 4 thermistor analog inputs (2.7k pull up resistor)
+ 12 General purpose analog inputs
+ Dual VR sensors (crank position, wheel speed)
+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin
rusEfi's most fully-featured shield
IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles | +| [Proteus](Proteus) | + rusEFI if you have lots of hardware or cylinders
+ 4 layer PCB, 135mm x 82.5mm
+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)
+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)
+ Dual electronic throttles
+ 4x High-side 12v drivers, 1 amp each
+ 4 thermistor analog inputs (2.7k pull up resistor)
+ 12 General purpose analog inputs
+ Dual VR sensors (crank position, wheel speed)
+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin
rusEFI's most fully-featured shield
IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles | ### Q: How to select a board? diff --git a/Hardware/Pages-Hardware.md b/Hardware/Pages-Hardware.md index 466f0be4..18e7d9f7 100644 --- a/Hardware/Pages-Hardware.md +++ b/Hardware/Pages-Hardware.md @@ -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) @@ -42,7 +42,7 @@
PNP Boards * [PNP 48 - MRE based for Miata NA](microrusefi48adapter.pdf) -* [PNP 72 - MRE based for Miata NB2](Hardware/pnp_microRusEfi_nb2/hw72nb.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) * [MRE Adapter 55](MREAdapter55) diff --git a/Hardware/microrusefi/Hardware-microRusEFI-hardware-checks.md b/Hardware/microRusEFI/Hardware-microRusEFI-hardware-checks.md similarity index 84% rename from Hardware/microrusefi/Hardware-microRusEFI-hardware-checks.md rename to Hardware/microRusEFI/Hardware-microRusEFI-hardware-checks.md index 6d0881cd..d49520bd 100644 --- a/Hardware/microrusefi/Hardware-microRusEFI-hardware-checks.md +++ b/Hardware/microRusEFI/Hardware-microRusEFI-hardware-checks.md @@ -8,4 +8,4 @@ v0.1/v0.2 power supply check list 1. 5v test pad: expected 5.0v -![front lower](Hardware/microrusefi/Hardware_microRusEfi_0_2_top_checks.jpg) \ No newline at end of file +![front lower](Hardware/microRusEFI/Hardware_microRusEFI_0_2_top_checks.jpg) \ No newline at end of file diff --git a/Hardware/microrusefi/Hardware-microRusEFI-kit-instructions.md b/Hardware/microRusEFI/Hardware-microRusEFI-kit-instructions.md similarity index 77% rename from Hardware/microrusefi/Hardware-microRusEFI-kit-instructions.md rename to Hardware/microRusEFI/Hardware-microRusEFI-kit-instructions.md index 4ae8e993..19537d05 100644 --- a/Hardware/microrusefi/Hardware-microRusEFI-kit-instructions.md +++ b/Hardware/microRusEFI/Hardware-microRusEFI-kit-instructions.md @@ -32,10 +32,10 @@ For component placement please use interactive BOM [0.4.7](https://rusefi.com/docs/ibom/microRusEfi_R0.4.7.html) -[Some checkpoints](Hardware/microrusefi/Hardware_microRusEfi_0_4_7_front_checks.jpg) +[Some checkpoints](Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_front_checks.jpg) -All microRusEfi kits use [MRE F4 rusEfi firmware - DOWNLOAD LATEST BUNDLE HERE](https://rusefi.com/build_server/rusefi_bundle_mre_f4.zip) +All microRusEfi kits use [MRE F4 rusEFI firmware - DOWNLOAD LATEST BUNDLE HERE](https://rusefi.com/build_server/rusefi_bundle_mre_f4.zip) @@ -49,9 +49,9 @@ All microRusEfi kits use [MRE F4 rusEfi firmware - DOWNLOAD LATEST BUNDLE HERE]( [0.4.7 schematics PDF](https://github.com/rusefi/hw_microRusEfi/blob/master/microRusEfi_Schematic_0_4_7.pdf) -[rusEfi Slack channel](https://rusefi.com/forum/viewtopic.php?f=13&t=1198) is the primary support channel. +[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 @@ -62,10 +62,10 @@ Depending on your crankshaft position sensor type you would need to populate eit 0.4.8: Comes set for VR (R9 & C12 are now on the front since) VR mode front - comes pre-assembled -![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_front.png) +![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_front.png) VR mode back -![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_back.jpg) +![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_back.jpg) 0.4.5, 0.4.7: For Hall, you would need to REMOVE R15 & C35 on the front, and install R17=1.5K R18=R19=4.7K on the back. @@ -73,36 +73,36 @@ VR mode back 0.4.8: For Hall, you would need to REMOVE R15&R9, C12 & C35 on the front, and install R17=1.5K R18=R19=4.7K on the back. 0.5.0 Hall -![Front](Hardware/microrusefi/Hardware_microRusEfi_0.5.0_hall_mode.jpg) +![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_hall_mode.jpg) 0.4.7 Hall mode front -![Front](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_front.jpg) +![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_front.jpg) 0.4.7 Hall mode back -![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_back.png) +![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_back.png) # Board Photos -![F](Hardware/microrusefi/Hardware_microRusEfi_0.5.3_assembled_front.jpg) +![F](Hardware/microRusEFI/Hardware_microRusEFI_0.5.3_assembled_front.jpg) -![F](Hardware/microrusefi/Hardware_microRusEfi_0.5.0_module_assembled_front.jpg) +![F](Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_module_assembled_front.jpg) Kit front: -![Front](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_pre_assembled_front.jpg) +![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_pre_assembled_front.jpg) Kit parts on the front: -![Front](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_front.jpg) +![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_front.jpg) Kit parts on the back: -![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_assembled_back.jpg) +![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_assembled_back.jpg) Flyback diodes orientation -![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_diodes_orientation.jpg) +![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_diodes_orientation.jpg) # Important details @@ -127,7 +127,7 @@ J7 header in bottom-left corner of microRusEFI allows direct SWD programming usi Tag Connect In circuit Cable "NO Legs" Version -![x](Hardware/microrusefi/TC2030_SWD.jpg) +![x](Hardware/microRusEFI/TC2030_SWD.jpg) ### Note - Missing wire caps -In the even of a missing wire cap on the molex plug the correct part number is 64320-1301 and these can be easily sourced online \ No newline at end of file +In the even of a missing wire cap on the molex plug the correct part number is 64320-1301 and these can be easily sourced online diff --git a/Hardware/microrusefi/Hardware-microRusEFI-wiring.md b/Hardware/microRusEFI/Hardware-microRusEFI-wiring.md similarity index 91% rename from Hardware/microrusefi/Hardware-microRusEFI-wiring.md rename to Hardware/microRusEFI/Hardware-microRusEFI-wiring.md index d05addf0..b38443f7 100644 --- a/Hardware/microrusefi/Hardware-microRusEFI-wiring.md +++ b/Hardware/microRusEFI/Hardware-microRusEFI-wiring.md @@ -2,15 +2,15 @@ [Interactive Pinout](https://rusefi.com/docs/pinouts/microrusefi/) -![connector](Hardware/microrusefi/Hardware_microRusEfi_connector.png) +![connector](Hardware/microRusEFI/Hardware_microRusEFI_connector.png) -![microRusEfi photo](Hardware/microrusefi/Hardware_microRusEfi_connector.jpg) +![microRusEfi photo](Hardware/microRusEFI/Hardware_microRusEFI_connector.jpg) Rear side of PCB -![microRusEfi image](Hardware/microrusefi/Hardware_microRusEfi_0_3_PCB_pinout.png) +![microRusEfi image](Hardware/microRusEFI/Hardware_microRusEFI_0_3_PCB_pinout.png) -![x](Hardware/microrusefi/microRusEfi_connectors/MRE_reality.jpg) +![x](Hardware/microRusEFI/microRusEFI_connectors/MRE_reality.jpg) In some cases without "main relay output +12v" both pins #1 and #5 should be connected to the single source of +12v. @@ -18,7 +18,7 @@ Pin #1 feeds ETB H-bridge, battery voltage sense, gp5 & gp6 high-side +12v, TLE8 # Pin Types -These tables provide technical information about the different types of pin found on microrusEfi. +These tables provide technical information about the different types of pin found on microRusEFI. ## Power @@ -91,8 +91,8 @@ R12=10K R13=0R -![front hall](Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_hall_setup.jpg) -![front lower](Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_lower.jpg) +![front hall](Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_hall_setup.jpg) +![front lower](Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_lower.jpg) @@ -102,7 +102,7 @@ microRusEFI exposes the following pins in addition to the primary 48 pin connect J4: -![x](Hardware/microrusefi/J4.png) +![x](Hardware/microRusEFI/J4.png) | N | Name | Possible functions (not all listed!) | |----|-------------| ---- | | 9 | GNS | GND @@ -131,7 +131,7 @@ Three GPIOs are available on J2 (SWD) connector. If you are not going to use deb For HW version 0.5.0 and newer some additional GPIOs are available on testpoints around STM32. -![x](Hardware/microrusefi/J8_9_10.png) +![x](Hardware/microRusEFI/J8_9_10.png) [Testpoint Interactive Pinout](https://rusefi.com/docs/pinouts/microrusefi/pads.html) diff --git a/Hardware/microrusefi/Hardware-microRusEFI.md b/Hardware/microRusEFI/Hardware-microRusEFI.md similarity index 100% rename from Hardware/microrusefi/Hardware-microRusEFI.md rename to Hardware/microRusEFI/Hardware-microRusEFI.md diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.5_back.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_back.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.5_back.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_back.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.5_more_assembled_back.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_more_assembled_back.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.5_more_assembled_back.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_more_assembled_back.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.5_more_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_more_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.5_more_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_more_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.5_pre_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_pre_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.5_pre_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.5_pre_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_back.png b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_back.png similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_back.png rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_back.png diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_back.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_back.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_back.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_back.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_front.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_front.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_front.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_front.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_assembled_back.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_assembled_back.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_assembled_back.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_assembled_back.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_diodes_orientation.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_diodes_orientation.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_diodes_orientation.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_diodes_orientation.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_front.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_front.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_front.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_front.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_pre_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_pre_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_pre_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_pre_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_back.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_back.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_back.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_back.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_back.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_back.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_back.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_back.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_front.png b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_front.png similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_front.png rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_front.png diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_front.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_front.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_front.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_front.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.4.8_pre_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.4.8_pre_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.4.8_pre_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.4.8_pre_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.0_full_assembled_back.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_full_assembled_back.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.0_full_assembled_back.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_full_assembled_back.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.0_full_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_full_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.0_full_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_full_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.0_hall_mode.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_hall_mode.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.0_hall_mode.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_hall_mode.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.0_module_assembled_back.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_module_assembled_back.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.0_module_assembled_back.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_module_assembled_back.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.0_module_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_module_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.0_module_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_module_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.0_pre_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_pre_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.0_pre_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_pre_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0.5.3_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0.5.3_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0.5.3_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0.5.3_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_hall_setup.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_hall_setup.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_hall_setup.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_hall_setup.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_lower.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_lower.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_lower.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_lower.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_1_pcb.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_1_pcb.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_1_pcb.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_1_pcb.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_2_top_checks.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_2_top_checks.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_2_top_checks.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_2_top_checks.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_2_top_checks.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0_2_top_checks.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_2_top_checks.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0_2_top_checks.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_3_PCB_pinout.png b/Hardware/microRusEFI/Hardware_microRusEFI_0_3_PCB_pinout.png similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_3_PCB_pinout.png rename to Hardware/microRusEFI/Hardware_microRusEFI_0_3_PCB_pinout.png diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_3_PCB_pinout_vertical.png b/Hardware/microRusEFI/Hardware_microRusEFI_0_3_PCB_pinout_vertical.png similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_3_PCB_pinout_vertical.png rename to Hardware/microRusEFI/Hardware_microRusEFI_0_3_PCB_pinout_vertical.png diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_3_assembled_front_hall_setup.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_3_assembled_front_hall_setup.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_3_assembled_front_hall_setup.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_3_assembled_front_hall_setup.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_4_7_assembled_front.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_assembled_front.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_4_7_assembled_front.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_assembled_front.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_4_7_front_checks.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_front_checks.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_4_7_front_checks.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_front_checks.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_0_4_7_front_checks.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_front_checks.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_0_4_7_front_checks.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_front_checks.xcf diff --git a/Hardware/microrusefi/Hardware_microRusEfi_connector.jpg b/Hardware/microRusEFI/Hardware_microRusEFI_connector.jpg similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_connector.jpg rename to Hardware/microRusEFI/Hardware_microRusEFI_connector.jpg diff --git a/Hardware/microrusefi/Hardware_microRusEfi_connector.png b/Hardware/microRusEFI/Hardware_microRusEFI_connector.png similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_connector.png rename to Hardware/microRusEFI/Hardware_microRusEFI_connector.png diff --git a/Hardware/microrusefi/Hardware_microRusEfi_connector.xcf b/Hardware/microRusEFI/Hardware_microRusEFI_connector.xcf similarity index 100% rename from Hardware/microrusefi/Hardware_microRusEfi_connector.xcf rename to Hardware/microRusEFI/Hardware_microRusEFI_connector.xcf diff --git a/Hardware/microrusefi/J4.png b/Hardware/microRusEFI/J4.png similarity index 100% rename from Hardware/microrusefi/J4.png rename to Hardware/microRusEFI/J4.png diff --git a/Hardware/microrusefi/J8_9_10.png b/Hardware/microRusEFI/J8_9_10.png similarity index 100% rename from Hardware/microrusefi/J8_9_10.png rename to Hardware/microRusEFI/J8_9_10.png diff --git a/Hardware/microrusefi/TC2030_SWD.jpg b/Hardware/microRusEFI/TC2030_SWD.jpg similarity index 100% rename from Hardware/microrusefi/TC2030_SWD.jpg rename to Hardware/microRusEFI/TC2030_SWD.jpg diff --git a/Hardware/microrusefi/microRusEFI-DIY-TLDR.md b/Hardware/microRusEFI/microRusEFI-DIY-TLDR.md similarity index 100% rename from Hardware/microrusefi/microRusEFI-DIY-TLDR.md rename to Hardware/microRusEFI/microRusEFI-DIY-TLDR.md diff --git a/Hardware/microrusefi/microRusEFI-Manual.md b/Hardware/microRusEFI/microRusEFI-Manual.md similarity index 95% rename from Hardware/microrusefi/microRusEFI-Manual.md rename to Hardware/microRusEFI/microRusEFI-Manual.md index 5d1419d2..9ebe0fd3 100644 --- a/Hardware/microrusefi/microRusEFI-Manual.md +++ b/Hardware/microRusEFI/microRusEFI-Manual.md @@ -15,21 +15,21 @@ ## HOWTO update microRusEFI Firmware -The best way to update microRusEfi firmware is using rusEfi console "Auto DFU" mode. +The best way to update microRusEfi firmware is using rusEFI console "Auto DFU" mode. In AutoDFU a few things happen once you click the "Update Firmware" button. 0) AutoDFU procedure works if your Windows device manager shows "STMicroelectronics Virtual COM Port" in "Ports" category. ![img](Support/AutoDFU_precondition.png) -1) rusEfi console finds your microRusEFI device serial port and sends it a command to reboot into DFU mode. +1) rusEFI console finds your microRusEFI device serial port and sends it a command to reboot into DFU mode. It is expected that microRusEFI would stop blinking the blue light and reboot. It is expected that Virtual COM Port would disappear from Device Manager and "STM Device in DFU Mode" device would appear in "Universal Serial Bus controllers" category. ![img](Support/stm_device_in_dfu_mode.png) -2) rusEfi console gives Windows 3 seconds to re-enumerate USB device from Virtual COM Port to DFU Device. +2) rusEFI console gives Windows 3 seconds to re-enumerate USB device from Virtual COM Port to DFU Device. Now the programming begins and the expected output is along the following lines: ``` @@ -117,8 +117,8 @@ Done! Please power cycle device to exit DFU mode ``` -At this point you need to power rusEfi device off/on and new firmware version would be running! +At this point you need to power rusEFI device off/on and new firmware version would be running! -New firmware version could be confirmed in rusEfi window title - both console and firmware versions are displayed there. +New firmware version could be confirmed in rusEFI window title - both console and firmware versions are displayed there. ![img](Support/console_showing_firmware_version.png) diff --git a/Hardware/microrusefi/microRusEfi_connectors/Hardware-microRusEfi-connectors.md b/Hardware/microRusEFI/microRusEFI_connectors/Hardware-microRusEFI-connectors.md similarity index 81% rename from Hardware/microrusefi/microRusEfi_connectors/Hardware-microRusEfi-connectors.md rename to Hardware/microRusEFI/microRusEFI_connectors/Hardware-microRusEFI-connectors.md index 5d998039..183fe32b 100644 --- a/Hardware/microrusefi/microRusEfi_connectors/Hardware-microRusEfi-connectors.md +++ b/Hardware/microRusEFI/microRusEFI_connectors/Hardware-microRusEFI-connectors.md @@ -6,13 +6,13 @@ US: 2007+ Nissan Altima & 2007+ Nissan Sentra Harness side socket. "Removable front key" style. Left from China, Right removed from Nissan Sentra. -![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_removable_key_China_and_Nissan_harness_socket.jpg) +![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_removable_key_China_and_Nissan_harness_socket.jpg) Removed from Nissan Sentra - square terminals. Left large terminal. Right small pin terminal. -![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_Nissan_crimped_terminals.jpg) +![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_Nissan_crimped_terminals.jpg) PCB side: [Molex 48 pin PCB plug](https://www.mouser.com/datasheet/2/276/5007620481_PCB_HEADERS-179151.pdf) 5007620481 500762-0481 @@ -37,7 +37,7 @@ todo "Side clip" style harness socket, both from China. -![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_side_clip_China_harness_socket.jpg) +![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_side_clip_China_harness_socket.jpg) Terminals @@ -54,7 +54,7 @@ With a utility knife you need to cut 4 keys from inside the male part to mate de as is. -![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_helping_black_plug_with_brown.jpg) +![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_helping_black_plug_with_brown.jpg) -![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness.jpg) \ No newline at end of file +![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_lada_donor_harness.jpg) \ No newline at end of file diff --git a/Hardware/microrusefi/microRusEfi_connectors/MRE_reality.jpg b/Hardware/microRusEFI/microRusEFI_connectors/MRE_reality.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/MRE_reality.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/MRE_reality.jpg diff --git a/Hardware/microrusefi/microRusEfi_connectors/microRusEfi_Nissan_crimped_terminals.jpg b/Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_Nissan_crimped_terminals.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/microRusEfi_Nissan_crimped_terminals.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_Nissan_crimped_terminals.jpg diff --git a/Hardware/microrusefi/microRusEfi_connectors/microRusEfi_helping_black_plug_with_brown.jpg b/Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_helping_black_plug_with_brown.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/microRusEfi_helping_black_plug_with_brown.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_helping_black_plug_with_brown.jpg diff --git a/Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness.jpg b/Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_lada_donor_harness.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_lada_donor_harness.jpg diff --git a/Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness2.jpg b/Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_lada_donor_harness2.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness2.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_lada_donor_harness2.jpg diff --git a/Hardware/microrusefi/microRusEfi_connectors/microRusEfi_removable_key_China_and_Nissan_harness_socket.jpg b/Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_removable_key_China_and_Nissan_harness_socket.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/microRusEfi_removable_key_China_and_Nissan_harness_socket.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_removable_key_China_and_Nissan_harness_socket.jpg diff --git a/Hardware/microrusefi/microRusEfi_connectors/microRusEfi_side_clip_China_harness_socket.jpg b/Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_side_clip_China_harness_socket.jpg similarity index 100% rename from Hardware/microrusefi/microRusEfi_connectors/microRusEfi_side_clip_China_harness_socket.jpg rename to Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_side_clip_China_harness_socket.jpg diff --git a/Hardware/microrusefi/mre_test_board/mre_test_board1.jpg b/Hardware/microRusEFI/mre_test_board/mre_test_board1.jpg similarity index 100% rename from Hardware/microrusefi/mre_test_board/mre_test_board1.jpg rename to Hardware/microRusEFI/mre_test_board/mre_test_board1.jpg diff --git a/Hardware/microrusefi/mre_test_board/mre_test_board1.xcf b/Hardware/microRusEFI/mre_test_board/mre_test_board1.xcf similarity index 100% rename from Hardware/microrusefi/mre_test_board/mre_test_board1.xcf rename to Hardware/microRusEFI/mre_test_board/mre_test_board1.xcf diff --git a/Hardware/microrusefi/mre_test_board/normal_and_inverted_test_LED_accounting_for_diag_leakeage.png b/Hardware/microRusEFI/mre_test_board/normal_and_inverted_test_LED_accounting_for_diag_leakeage.png similarity index 100% rename from Hardware/microrusefi/mre_test_board/normal_and_inverted_test_LED_accounting_for_diag_leakeage.png rename to Hardware/microRusEFI/mre_test_board/normal_and_inverted_test_LED_accounting_for_diag_leakeage.png diff --git a/Hardware/microrusefi/store/mre_assembled.jpg b/Hardware/microRusEFI/store/mre_assembled.jpg similarity index 100% rename from Hardware/microrusefi/store/mre_assembled.jpg rename to Hardware/microRusEFI/store/mre_assembled.jpg diff --git a/Hardware/microrusefi/store/mre_assembled_connector_kit.jpg b/Hardware/microRusEFI/store/mre_assembled_connector_kit.jpg similarity index 100% rename from Hardware/microrusefi/store/mre_assembled_connector_kit.jpg rename to Hardware/microRusEFI/store/mre_assembled_connector_kit.jpg diff --git a/Hardware/microrusefi/store/mre_assembled_pigtail.jpg b/Hardware/microRusEFI/store/mre_assembled_pigtail.jpg similarity index 100% rename from Hardware/microrusefi/store/mre_assembled_pigtail.jpg rename to Hardware/microRusEFI/store/mre_assembled_pigtail.jpg diff --git a/Hardware/pnp_microRusEfi_48na/48_Pin_Connector.png b/Hardware/pnp_microRusEFI_48na/48_Pin_Connector.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/48_Pin_Connector.png rename to Hardware/pnp_microRusEFI_48na/48_Pin_Connector.png diff --git a/Hardware/pnp_microRusEfi_48na/M4_washers_mtg_hole.png b/Hardware/pnp_microRusEFI_48na/M4_washers_mtg_hole.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/M4_washers_mtg_hole.png rename to Hardware/pnp_microRusEFI_48na/M4_washers_mtg_hole.png diff --git a/Hardware/pnp_microRusEfi_48na/MREAdapter48.md b/Hardware/pnp_microRusEFI_48na/MREAdapter48.md similarity index 100% rename from Hardware/pnp_microRusEfi_48na/MREAdapter48.md rename to Hardware/pnp_microRusEFI_48na/MREAdapter48.md diff --git a/Hardware/pnp_microRusEfi_48na/MRE_Micro_USB.png b/Hardware/pnp_microRusEFI_48na/MRE_Micro_USB.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/MRE_Micro_USB.png rename to Hardware/pnp_microRusEFI_48na/MRE_Micro_USB.png diff --git a/Hardware/pnp_microRusEfi_48na/Miata-NA-48-pin-board-for-MRE-(version-0.2).md b/Hardware/pnp_microRusEFI_48na/Miata-NA-48-pin-board-for-MRE-(version-0.2).md similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Miata-NA-48-pin-board-for-MRE-(version-0.2).md rename to Hardware/pnp_microRusEFI_48na/Miata-NA-48-pin-board-for-MRE-(version-0.2).md diff --git a/Hardware/pnp_microRusEfi_48na/Miata-NA-48-pin-board-for-MRE.md b/Hardware/pnp_microRusEFI_48na/Miata-NA-48-pin-board-for-MRE.md similarity index 94% rename from Hardware/pnp_microRusEfi_48na/Miata-NA-48-pin-board-for-MRE.md rename to Hardware/pnp_microRusEFI_48na/Miata-NA-48-pin-board-for-MRE.md index 757608ef..aa35aa67 100644 --- a/Hardware/pnp_microRusEfi_48na/Miata-NA-48-pin-board-for-MRE.md +++ b/Hardware/pnp_microRusEFI_48na/Miata-NA-48-pin-board-for-MRE.md @@ -3,11 +3,11 @@ See also https://github.com/rusefi/rusefi/wiki/Installing-a-PnP-rusEFI-unit-star 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 [microRusEFI](Hardware-microRusEFI) module that drives the unit. -Your board should look something like this: ![Miata NA 48 pin board for MRE](Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view.png) +Your board should look something like this: ![Miata NA 48 pin board for MRE](Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view.png) -![x](Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view_0_4_NA6.jpg) +![x](Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view_0_4_NA6.jpg) -![x](Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view_0_4_NA94.jpg) +![x](Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view_0_4_NA94.jpg) Currently the only tested configuration is the NA6 Miata with a manual transmission. If you have a different car, we may need your help testing the configuration! Automatic transmission cars are not yet confirmed to work, although there's no reason to think they won't. @@ -18,14 +18,14 @@ The board can be configured for several different options simply by adding/remov # 1. Installation - Open the stock ECU case - Remove the stock PCB from the ECU case -- Install the rusEfi board in the ECU case (note: one of the mounting holes, labeled J27, requires a stack of 3 M4 washers- see image below) +- Install the rusEFI board in the ECU case (note: one of the mounting holes, labeled J27, requires a stack of 3 M4 washers- see image below) - Close the case* - Plug in connectors and drive *You may want to not put the lid on the case for now. That makes it easier to connect to the unit with a laptop using a micro USB cable. See below: USB connection. One of the mounting screws needs three M4 washers because the case has a recessed thread- the stock ECU has a heat sink at that location. The washers may be included with your kit. They go here: -![M4 washers mounting](Hardware/pnp_microRusEfi_48na/M4_washers_mtg_hole.png) +![M4 washers mounting](Hardware/pnp_microRusEFI_48na/M4_washers_mtg_hole.png) # 2. Standard upgrades over stock The board should be received set up as a stock replacement unit for your year car. Either a 1990-1993 NA6 or a 1994/1995 NA8. Even in standard configuration it can perform a few tricks the stock ECU just can't. @@ -34,20 +34,20 @@ The board should be received set up as a stock replacement unit for your year ca The unit can connect to [TunerStudio](http://www.tunerstudio.com/index.php/tuner-studio) via native USB communication. You can either plug a MiniUSB (or some boards have MicroUSB) cable into the top of the unit. This is a bit difficult to get to in the stock installation position on an NA6, so it may not be ideal for a permanent installation in the stock location. -![Micro USB connector](Hardware/pnp_microRusEfi_48na/MRE_Micro_USB.png) +![Micro USB connector](Hardware/pnp_microRusEFI_48na/MRE_Micro_USB.png) If you want to use this connector for communication with your tuning laptop, cutting a hole in the top for connector access is helpful. Here are some rough dimensions on where the hole should go. A 5/16" or 8mm drill and a small file or Dremel works well. -![Lid cutout](Hardware/pnp_microRusEfi_48na/Miata_NA_PnP_Lid_Cutout_Dimensions.png) -![USB plugged in](Hardware/pnp_microRusEfi_48na/Miata_NA_PnP_USB_plugged_in.png) +![Lid cutout](Hardware/pnp_microRusEFI_48na/Miata_NA_PnP_Lid_Cutout_Dimensions.png) +![USB plugged in](Hardware/pnp_microRusEFI_48na/Miata_NA_PnP_USB_plugged_in.png) Alternatively, you can wire a standard USB cable into the main connector for a more permanent solution. Your board may come with additional contacts / wires for the main connector that can be soldered to a standard USB cable. (Please note that the 5V connection is not needed for communication. It can, however be used to power the MRE unit with the ignition off. The 5V power suply feature is untested and may not work. Communication using GND, D+ and D- is confirmed to work.) -![USB main connector](Hardware/pnp_microRusEfi_48na/USB_connections.png) +![USB main connector](Hardware/pnp_microRusEFI_48na/USB_connections.png) ## 2.2. Micro SD card adapter The board comes with an adapter for a Micro SD card. Install a card in this slot and it will automatically keep a log of your engine when it's running. The log can be retrieved using the rusEFI plugin in Tunerstudio. Please note that Tunerstudio must be offline for the plugin to have access to the USB port. If Tunerstudio is still communicating with the ECU (online), the rusEFI plugin will be unable to access the USB port. Another way to retrieve logs from the SD card is to open the case, remove the SD card and read it directly from a computer or other device running MegaLogViewer. -![Micro SD adapter](Hardware/pnp_microRusEfi_48na/Micro_SD_adapter.png) +![Micro SD adapter](Hardware/pnp_microRusEFI_48na/Micro_SD_adapter.png) Warning: There are reports that some Micro SD cards will not work for this setup. So if you are having trouble with this, try a different card. @@ -56,19 +56,19 @@ Your board may, or may not, have an onboard MAP sensor. The onboard MAP sensor c The board can be equipped with a secondary MAP sensor for barometric correction as well ## 2.4. Tach Signal -Your stock engine (Miata NA6 and 94/95 NA8) uses external igniters that not only drive the ignition coils, they also provide the signal the tachometer uses to display rpm. The ECU provides only a pull-up to 5V. When equipping the vehicle with coils from a different generation Miata, or any other logic-level coil, like COPs or GM LS coils, they will not provide the tach signal and the rusEfi unit needs to take care of it. In the standard configuration the ECU only provides the pull-up resistor, but it can easily be changed to provide the tach signal. +Your stock engine (Miata NA6 and 94/95 NA8) uses external igniters that not only drive the ignition coils, they also provide the signal the tachometer uses to display rpm. The ECU provides only a pull-up to 5V. When equipping the vehicle with coils from a different generation Miata, or any other logic-level coil, like COPs or GM LS coils, they will not provide the tach signal and the rusEFI unit needs to take care of it. In the standard configuration the ECU only provides the pull-up resistor, but it can easily be changed to provide the tach signal. # 3. Upgrades / expansions / options ## 3.1. Wideband O2 sensor -This is so basic that you should probably do this at the same time as the installation of the ECU. Any aftermarket wideband sensors with an analog output will work. You will have to supply it with switched 12V from a decent source and connect to signal ground at the ECU. For the 12V you can splice into the wire going to pin 1B on the ECU (ignition power) and for ground rusEfi provides an additional signal ground pin on pin 2F that is not populated on the stock connector. Or you can splice into wires from pins 1C or 1D. The analog output should be connected to pin 2N on the ECU connector. This is the stock narrowband oxygen sensor input. +This is so basic that you should probably do this at the same time as the installation of the ECU. Any aftermarket wideband sensors with an analog output will work. You will have to supply it with switched 12V from a decent source and connect to signal ground at the ECU. For the 12V you can splice into the wire going to pin 1B on the ECU (ignition power) and for ground rusEFI provides an additional signal ground pin on pin 2F that is not populated on the stock connector. Or you can splice into wires from pins 1C or 1D. The analog output should be connected to pin 2N on the ECU connector. This is the stock narrowband oxygen sensor input. ## 3.2. MAP Sensor The first thing most users will likely want to do is use a MAP sensor for load sensing instead of the stock VAF (AFM). The easiest way to achieve this is to install an MPX4250 in the designated spot on the PCB (see image). Your board may already have this sensor installed. Warning: V 0.2 of the board has an unintended "feature" that requires you to Note that only 4 of the six legs of the sensor get soldered directly to the board. Pin 1 and pin 3 get bent up by 90 degrees and wired into pin 3 and pin 1 of the ADJACENT barometric sensor. Note that pin 1 on the sensor goes to pin 3 on the board and pin 3 on the sensor goes to pin 1 on the board. -![Onboard MAP sensor](Hardware/pnp_microRusEfi_48na/onboard_baro.png) +![Onboard MAP sensor](Hardware/pnp_microRusEFI_48na/onboard_baro.png) -Please make sure to upload the correct tune for this configuration or change your tune manually. Tunes can be found at [rusEfi Online](https://rusefi.com/online/?sorts[uploadedMsq]=-1&sorts[uploadedLog]=-1) +Please make sure to upload the correct tune for this configuration or change your tune manually. Tunes can be found at [rusEFI Online](https://rusefi.com/online/?sorts[uploadedMsq]=-1&sorts[uploadedLog]=-1) If you want to install an external MAP sensor, like a GM 3 bar sensor for example, you can wire it to your stock AFM connector instead of the AFM. Or you can run additional wires from the ECU. Instructions will follow separately. @@ -193,7 +193,7 @@ JP44 USB GND| Y| N| *| Press. Reg. vlv JP50 2X CAN_L| Y |N| Purg Sol. Vlv| Purg Sol. Vlv -[Schematics 0.4](Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0.4.pdf) +[Schematics 0.4](Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0.4.pdf) [Schematics 0.2](https://github.com/rusefi/rusefi_documentation/raw/master/Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0_2.pdf) diff --git a/Hardware/pnp_microRusEfi_48na/Miata_NA_PnP_Lid_Cutout_Dimensions.png b/Hardware/pnp_microRusEFI_48na/Miata_NA_PnP_Lid_Cutout_Dimensions.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Miata_NA_PnP_Lid_Cutout_Dimensions.png rename to Hardware/pnp_microRusEFI_48na/Miata_NA_PnP_Lid_Cutout_Dimensions.png diff --git a/Hardware/pnp_microRusEfi_48na/Miata_NA_PnP_USB_plugged_in.png b/Hardware/pnp_microRusEFI_48na/Miata_NA_PnP_USB_plugged_in.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Miata_NA_PnP_USB_plugged_in.png rename to Hardware/pnp_microRusEFI_48na/Miata_NA_PnP_USB_plugged_in.png diff --git a/Hardware/pnp_microRusEfi_48na/Micro_SD_adapter.png b/Hardware/pnp_microRusEFI_48na/Micro_SD_adapter.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Micro_SD_adapter.png rename to Hardware/pnp_microRusEFI_48na/Micro_SD_adapter.png diff --git a/Hardware/pnp_microRusEfi_48na/USB_connections.png b/Hardware/pnp_microRusEFI_48na/USB_connections.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/USB_connections.png rename to Hardware/pnp_microRusEFI_48na/USB_connections.png diff --git a/Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view.png b/Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view.png rename to Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view.png diff --git a/Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view_0_4_NA6.jpg b/Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view_0_4_NA6.jpg similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view_0_4_NA6.jpg rename to Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view_0_4_NA6.jpg diff --git a/Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view_0_4_NA94.jpg b/Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view_0_4_NA94.jpg similarity index 100% rename from Hardware/pnp_microRusEfi_48na/Whole_PCB_top_view_0_4_NA94.jpg rename to Hardware/pnp_microRusEFI_48na/Whole_PCB_top_view_0_4_NA94.jpg diff --git a/Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0.1.pdf b/Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0.1.pdf similarity index 100% rename from Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0.1.pdf rename to Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0.1.pdf diff --git a/Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0.4.pdf b/Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0.4.pdf similarity index 100% rename from Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0.4.pdf rename to Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0.4.pdf diff --git a/Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0_2.pdf b/Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0_2.pdf similarity index 100% rename from Hardware/pnp_microRusEfi_48na/microrusefi48adapter_0_2.pdf rename to Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_0_2.pdf diff --git a/Hardware/pnp_microRusEfi_48na/microrusefi48adapter_latest.pdf b/Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_latest.pdf similarity index 100% rename from Hardware/pnp_microRusEfi_48na/microrusefi48adapter_latest.pdf rename to Hardware/pnp_microRusEFI_48na/microRusEFI48adapter_latest.pdf diff --git a/Hardware/pnp_microRusEfi_48na/onboard_baro.png b/Hardware/pnp_microRusEFI_48na/onboard_baro.png similarity index 100% rename from Hardware/pnp_microRusEfi_48na/onboard_baro.png rename to Hardware/pnp_microRusEFI_48na/onboard_baro.png diff --git a/Hardware/pnp_microRusEfi_nb2/MREAdapter72.md b/Hardware/pnp_microRusEFI_nb2/MREAdapter72.md similarity index 100% rename from Hardware/pnp_microRusEfi_nb2/MREAdapter72.md rename to Hardware/pnp_microRusEFI_nb2/MREAdapter72.md diff --git a/Hardware/pnp_microRusEfi_nb2/MREAdapter72_0_2_back.jpg b/Hardware/pnp_microRusEFI_nb2/MREAdapter72_0_2_back.jpg similarity index 100% rename from Hardware/pnp_microRusEfi_nb2/MREAdapter72_0_2_back.jpg rename to Hardware/pnp_microRusEFI_nb2/MREAdapter72_0_2_back.jpg diff --git a/Hardware/pnp_microRusEfi_nb2/MREAdapter72_0_2_front.jpg b/Hardware/pnp_microRusEFI_nb2/MREAdapter72_0_2_front.jpg similarity index 100% rename from Hardware/pnp_microRusEfi_nb2/MREAdapter72_0_2_front.jpg rename to Hardware/pnp_microRusEFI_nb2/MREAdapter72_0_2_front.jpg diff --git a/Hardware/pnp_microRusEfi_nb2/PNP-72-Jumpers.md b/Hardware/pnp_microRusEFI_nb2/PNP-72-Jumpers.md similarity index 100% rename from Hardware/pnp_microRusEfi_nb2/PNP-72-Jumpers.md rename to Hardware/pnp_microRusEFI_nb2/PNP-72-Jumpers.md diff --git a/Hardware/pnp_microRusEfi_nb2/hw72nb.pdf b/Hardware/pnp_microRusEFI_nb2/hw72nb.pdf similarity index 100% rename from Hardware/pnp_microRusEfi_nb2/hw72nb.pdf rename to Hardware/pnp_microRusEFI_nb2/hw72nb.pdf diff --git a/Hardware/pnp_microRusEfi_nb2/hw72nb.png b/Hardware/pnp_microRusEFI_nb2/hw72nb.png similarity index 100% rename from Hardware/pnp_microRusEfi_nb2/hw72nb.png rename to Hardware/pnp_microRusEFI_nb2/hw72nb.png diff --git a/Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png b/Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png similarity index 100% rename from Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png rename to Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png diff --git a/Misc/Saab_Trionic_8_Combustion Detection Module_on_Mazda_Miata_running_rusEFI/Saab-Trionic-8-Combustion-Detection-Module-on-Mazda-Miata-running-rusEFI.md b/Misc/Saab_Trionic_8_Combustion Detection Module_on_Mazda_Miata_running_rusEFI/Saab-Trionic-8-Combustion-Detection-Module-on-Mazda-Miata-running-rusEFI.md index d575c6cb..b96a17bb 100644 --- a/Misc/Saab_Trionic_8_Combustion Detection Module_on_Mazda_Miata_running_rusEFI/Saab-Trionic-8-Combustion-Detection-Module-on-Mazda-Miata-running-rusEFI.md +++ b/Misc/Saab_Trionic_8_Combustion Detection Module_on_Mazda_Miata_running_rusEFI/Saab-Trionic-8-Combustion-Detection-Module-on-Mazda-Miata-running-rusEFI.md @@ -1,14 +1,14 @@ -## Reverse Engineering Saab Trionic 8 Combustion Detection Module (CDM) output signals using rusEfi ECU +## Reverse Engineering Saab Trionic 8 Combustion Detection Module (CDM) output signals using rusEFI ECU ###### by Andrey Belomutskiy, 2018 * Table of contents - * [Overview](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEfi#overview) - * [Hardware](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEfi#hardware) - * [Detonation test scenario](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEfi#detonation-test-scenario) - * [Detonation signals](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEfi#detonation-signals) -* [Next Steps](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEfi#next-steps) -* [External links](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEfi#external-links) + * [Overview](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEFI#overview) + * [Hardware](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEFI#hardware) + * [Detonation test scenario](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEFI#detonation-test-scenario) + * [Detonation signals](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEFI#detonation-signals) +* [Next Steps](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEFI#next-steps) +* [External links](https://github.com/rusefi/rusefi_documentation/tree/master/misc/Saab_Trionic_8_Combustion%20Detection%20Module_on_Mazda_Miata_running_rusEFI#external-links) This data would not be gathered without help from kb1gtt, stefanst, andreika, nighthunter, hankthefourth and many others. @@ -64,7 +64,7 @@ Knock detection wire has 0.8KOhm pull-up to 5v, combustion detection signal has ### Detonation test scenario -2003 Mazda Miata 1.8 VVT Automatic running on rusEfi open source ECU. +2003 Mazda Miata 1.8 VVT Automatic running on rusEFI open source ECU. Engine coolant temperature 100C, ambient temperature 4C, violent 40 degrees advance from 1500 RPM to 3500 RPM timing table. @@ -89,7 +89,7 @@ Detonation is also audible while parked, revving with brakes applied in "D" gear [youtube: No knocking while standing on brakes 25 degrees timing](https://youtu.be/jS3LXw_v9ls) -And that's it! We have seen enough to get some code for the rusEfi firmware to start consuming this knock singal data! +And that's it! We have seen enough to get some code for the rusEFI firmware to start consuming this knock singal data! ### Next Steps @@ -107,16 +107,16 @@ Inside of 55352173 Saab Ionization Detection Module ### External Links -[rusEfi Patreon](https://www.patreon.com/rusefi) +[rusEFI Patreon](https://www.patreon.com/rusefi) -[rusEfi ECU](https://www.rusefi.com/) +[rusEFI ECU](https://www.rusefi.com/) -[rusEfi forum](https://www.rusefi.com/forum/) +[rusEFI forum](https://www.rusefi.com/forum/) -[rusEfi store](https://www.tindie.com/stores/russian/) +[rusEFI store](https://www.tindie.com/stores/russian/) [Trionic 8](https://en.wikipedia.org/wiki/Trionic_8) [Saab 9-3 wikipedia](https://en.wikipedia.org/wiki/Saab_9-3#Second_generation_(2003%E2%80%932014)) -[Spark Advance Modeling and Control](http://www.fs.isy.liu.se/Publications/PhD/99_PhD_580_LE.pdf) \ No newline at end of file +[Spark Advance Modeling and Control](http://www.fs.isy.liu.se/Publications/PhD/99_PhD_580_LE.pdf) diff --git a/OEM-Docs/oem-docs-readme.md b/OEM-Docs/oem-docs-readme.md index 15d44a53..8ce9ed6a 100644 --- a/OEM-Docs/oem-docs-readme.md +++ b/OEM-Docs/oem-docs-readme.md @@ -1 +1 @@ -In this folder we keep OEM documentation - so, no rusEfi content here \ No newline at end of file +In this folder we keep OEM documentation - so, no rusEFI content here diff --git a/OEM-Docs/stm32/stm32-readme.md b/OEM-Docs/stm32/stm32-readme.md index 50b741d1..977f7ab0 100644 --- a/OEM-Docs/stm32/stm32-readme.md +++ b/OEM-Docs/stm32/stm32-readme.md @@ -1,16 +1,16 @@ -rusEfi is known to work on these stm32 chips: +rusEFI is known to work on these stm32 chips: | chip | Frequency | Ram | Flash | Notes | Package notes | | |------|-----------|-----|-------|-------|---|---| -| F407 | 168 MHz | 192 Kb | 1M | most popular rusEfi chip | | | +| F407 | 168 MHz | 192 Kb | 1M | most popular rusEFI chip | | | | F469 | 180 MHz | 384 KB | two banks of flash should allow storing settings without execution pauses. | Prometheus board. | | | | F767 | 216MHz | 512 KB | 1M | Used on MicroRusEFI | | | | F429 | 180MHz | 256 KB | 2MB | 144 pin used on Proteus | [pinout](https://os.mbed.com/platforms/ST-Nucleo-F767ZI/#board-pinout) | | | | | | | | | | -Trying to get rusEfi running on: +Trying to get rusEFI running on: | chip | Frequency | Ram | Flash | Notes | Package notes | | |------|-----------|-----|-------|-------|---|---| diff --git a/Overview/TS_generated/rusEFI-project-Idle.md b/Overview/TS_generated/rusEFI-project-Idle.md index 169d5fa2..f49bd69b 100644 --- a/Overview/TS_generated/rusEFI-project-Idle.md +++ b/Overview/TS_generated/rusEFI-project-Idle.md @@ -21,7 +21,7 @@ Use separate VE Table for idle: This activates a separate fuel table for Idle, t Use separate IAC Table For Coasting: This setting allows the ECU to open the IAC during overrun conditions to help reduce engine breaking, this can be helpful for large engines in light weight cars. -Detailed status in console: Print details into rusEfi console +Detailed status in console: Print details into rusEFI console PID Extra for low RPM(%): Increases PID reaction for RPMaddEvent(52.960405, T_SECONDARY, TV_RISE); @@ -20,7 +20,7 @@ For developers to add the code we need to know the angles of signal rises and fa ## Step 1: tooth count -Using rusEfi console get a picture of a long enough engine sniff. On this example you see that a cycle of events consists of 24 tooth. +Using rusEFI console get a picture of a long enough engine sniff. On this example you see that a cycle of events consists of 24 tooth. ![Engine Sniffer](Images/Engine_sniffer.png) diff --git a/Triggers/weird-file-work-in-progress.md b/Triggers/weird-file-work-in-progress.md index 1345c88d..18ab1bd7 100644 --- a/Triggers/weird-file-work-in-progress.md +++ b/Triggers/weird-file-work-in-progress.md @@ -1,12 +1,12 @@ |ID|# of strokes| # of cam | # of crank | shape | | | |---|---|---|---|---|---|---| -|0_1E(xact)|4 strokes | 0 | 1 | exact angles known to rusEfi since shape is so simple| | z | -|1E_0|4 strokes | 1 | 0 | exact angles known to rusEfi since shape is so simple - 1/0 pattern or well-known signal with gap ratio| |z | +|0_1E(xact)|4 strokes | 0 | 1 | exact angles known to rusEFI since shape is so simple| | z | +|1E_0|4 strokes | 1 | 0 | exact angles known to rusEFI since shape is so simple - 1/0 pattern or well-known signal with gap ratio| |z | |1U(known)_0|4 strokes | 1 | 0 | exact angles NOT known - distributor 4/0 pattern for example, works with one coil | |z | -|1U_1E|4 strokes | 1 | 1 | relative cam position is not exactly known to rusEfi, exact cam position does not really matter or could be even variable like VVT | | z | -|1E_1E|4 strokes | 1 | 1 | exact angles known to rusEfi (Neon 1995) | | z | -|2E_0|4 strokes| 2 | 0 | exact angles known to rusEfi (Miata NA) | | | +|1U_1E|4 strokes | 1 | 1 | relative cam position is not exactly known to rusEFI, exact cam position does not really matter or could be even variable like VVT | | z | +|1E_1E|4 strokes | 1 | 1 | exact angles known to rusEFI (Neon 1995) | | z | +|2E_0|4 strokes| 2 | 0 | exact angles known to rusEFI (Miata NA) | | | +||| | | | | | ||| | | | | | ||| | | | | | ||| | | | | | -||| | | | | | \ No newline at end of file diff --git a/Vehicles/Mazda-Miata-2003-alt.md b/Vehicles/Mazda-Miata-2003-alt.md index c270e5ac..ef4f927f 100644 --- a/Vehicles/Mazda-Miata-2003-alt.md +++ b/Vehicles/Mazda-Miata-2003-alt.md @@ -6,7 +6,7 @@ In RusEFI console, set engine_type 47 loads base settings. ![Connector Face](OEM-Docs/Mazda/Miata_NB2_ECU_Connectors_Drawing.png) -![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png) +![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png) | Pin STM32 | Type | Pin RusEFI | Pin 64 Conn | Pin 72 Conn (NB2) | Desc | | --------- | ---------------- | ---------- | ----------- | ----------------- | ------------------------- | diff --git a/Vehicles/Mazda-Miata-2003.md b/Vehicles/Mazda-Miata-2003.md index 854174c3..8245c048 100644 --- a/Vehicles/Mazda-Miata-2003.md +++ b/Vehicles/Mazda-Miata-2003.md @@ -6,7 +6,7 @@ For power see [Mazda Miata 2002 - Starting & Power](Mazda-Miata-2002#starting--p ![Connector Face](Images/NB2 Miata ECU Connectors Drawing.png) -![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png) +![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png) Coil three wire plug: @@ -18,7 +18,7 @@ pin further away from the engine signal [Hellen72 Interactive Pinout](https://rusefi.com/docs/pinouts/hellen/hellen72/) -| desc | type | rusEfi harness | +| desc | type | rusEFI harness | | ---------- | ------ | -------------- | | MAP signal | analog | blue | | AFR signal | analog | white | diff --git a/Vehicles/Vehicle-Page-Template.md b/Vehicles/Vehicle-Page-Template.md index 8164f188..f7370a13 100644 --- a/Vehicles/Vehicle-Page-Template.md +++ b/Vehicles/Vehicle-Page-Template.md @@ -3,7 +3,7 @@ Want to add new page like this? At the moment rusEFI wiki is wide open for anyon Connector image here -![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png) +![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png) Wiring diagrams here diff --git a/_Sidebar.md b/_Sidebar.md index 2e80895b..32919185 100644 --- a/_Sidebar.md +++ b/_Sidebar.md @@ -16,7 +16,7 @@ - [Slack](HOWTO-join-slack-channel) - [Facebook Users Group](https://www.facebook.com/groups/rusEfi/) - [Engines running on rusEFI](List-of-engines-running-rusEFI) -- [HOWTO-help-rusEfi](HOWTO-help-rusEFI) +- [HOWTO-help-rusEFI](HOWTO-help-rusEFI) # Pages - [Fuel](Pages-Fuel) diff --git a/installations/MazdaMiataNA6_Frankenso_pnp/Frankenso-MazdaMiataNA6-pnp.md b/installations/MazdaMiataNA6_Frankenso_pnp/Frankenso-MazdaMiataNA6-pnp.md index 35cf6953..58a4adbb 100644 --- a/installations/MazdaMiataNA6_Frankenso_pnp/Frankenso-MazdaMiataNA6-pnp.md +++ b/installations/MazdaMiataNA6_Frankenso_pnp/Frankenso-MazdaMiataNA6-pnp.md @@ -3,8 +3,8 @@ The [Frankenso](Hardware-Frankenso) board was designed to be used on Mazda Miata ## Stage 0 -### Everything stock running rusEfi ECU -All stock sensors, no extra wires, no extra hoses - just lift the carpet and plug rusEfi box instead of OEM ECU. +### Everything stock running rusEFI ECU +All stock sensors, no extra wires, no extra hoses - just lift the carpet and plug rusEFI box instead of OEM ECU. Timing, fuel control based on VAF/MAF, programmable check engine light, A/C compressor control. Online tuning using TunerStudio. @@ -29,7 +29,7 @@ produce three clicks a second after you press the button in the software. #### Wideband O2 sensor wire WBO -You would really need a wideband sensor. Here is the middle plug pinout to wire an external wideband controller - +12v would feed external controller and analog output signal would provide rusEfi ECU with air/fuel ratio information. +You would really need a wideband sensor. Here is the middle plug pinout to wire an external wideband controller - +12v would feed external controller and analog output signal would provide rusEFI ECU with air/fuel ratio information. ![middle plug](installations/MazdaMiataNA6_Frankenso_pnp/Frankenso_MazdaMiataNA6_pnp_middle_plug_0_2.png) diff --git a/installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusefi27_20190413_back.jpg b/installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_back.jpg similarity index 100% rename from installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusefi27_20190413_back.jpg rename to installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_back.jpg diff --git a/installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusefi27_20190413_front.jpg b/installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_front.jpg similarity index 100% rename from installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusefi27_20190413_front.jpg rename to installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_front.jpg diff --git a/installations/MazdaMiataNB2_Frankenso/Frankenso.md b/installations/MazdaMiataNB2_Frankenso/Frankenso.md index 758917fe..b8dfab22 100644 --- a/installations/MazdaMiataNB2_Frankenso/Frankenso.md +++ b/installations/MazdaMiataNB2_Frankenso/Frankenso.md @@ -2,7 +2,7 @@ https://rusefi.com/forum/viewtopic.php?f=3&t=1095 -[PCB front](installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusefi27_20190413_front.jpg) -[PCB back](installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusefi27_20190413_back.jpg) +[PCB front](installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_front.jpg) +[PCB back](installations/MazdaMiataNB2_Frankenso/2003_Miata_NB2_rusEFI27_20190413_back.jpg) [ECU Plug Latch](installations/MazdaMiataNB2_Frankenso/nb2_ecu_plugs_latch.jpg) [ECU pins](installations/MazdaMiataNB2_Frankenso/NB2_Miata_ECU_Connectors_Add-Ons.png) diff --git a/readme.md b/readme.md index 64fa3712..97222aed 100644 --- a/readme.md +++ b/readme.md @@ -1,13 +1,13 @@ -# rusEfi Documentation & Knowledge +# rusEFI Documentation & Knowledge Documentation and knowledge repo for about https://github.com/rusefi/rusefi -If you are rusEfi end user, you are looking at the wrong page - you are probably interested in +If you are rusEFI end user, you are looking at the wrong page - you are probably interested in https://github.com/rusefi/rusefi/wiki -If you are looking to change rusEfi documentation you are in the right place! +If you are looking to change rusEFI documentation you are in the right place! This readme.md file is the main file visible at https://github.com/rusefi/rusefi_documentation diff --git a/rusEFI-History/10k_driven_with_rusefi.png b/rusEFI-History/10k_driven_with_rusEFI.png similarity index 100% rename from rusEFI-History/10k_driven_with_rusefi.png rename to rusEFI-History/10k_driven_with_rusEFI.png diff --git a/rusEFI-History/hardware_rusefi_v2.jpg b/rusEFI-History/hardware_rusEFI_v2.jpg similarity index 100% rename from rusEFI-History/hardware_rusefi_v2.jpg rename to rusEFI-History/hardware_rusEFI_v2.jpg diff --git a/rusEFI-History/hardware_rusefi_v3.jpg b/rusEFI-History/hardware_rusEFI_v3.jpg similarity index 100% rename from rusEFI-History/hardware_rusefi_v3.jpg rename to rusEFI-History/hardware_rusEFI_v3.jpg diff --git a/rusEFI-History/rusEFI-history.md b/rusEFI-History/rusEFI-history.md index e3230d7b..f583f774 100644 --- a/rusEFI-History/rusEFI-history.md +++ b/rusEFI-History/rusEFI-history.md @@ -1,5 +1,5 @@ # 2012 -rusEfi has started out of the blue by Andrey. +rusEFI has started out of the blue by Andrey. # 2013 @@ -14,4 +14,4 @@ Honda Accord came with head gasket pre-blown! https://honda-tech.com/forums/engi That's when Nick has joined the party. -https://github.com/rusefi/rusefi_documentation/wiki/List_of_engines_running_rusEfi +https://github.com/rusefi/rusefi_documentation/wiki/List_of_engines_running_rusEFI