change rusEfi to rusEFI
This commit is contained in:
David Holdeman
parent
f5a977a52d
commit
1afff1b975
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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<end of line>`
|
||||
|
||||
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
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
**A:** We can do collapsible sections & hints sections! See [cranking](Cranking) for an example.
|
||||
|
|
|
|||
|
|
@ -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/
|
||||
- https://www.facebook.com/rusEfiECU/
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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`
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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].
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
See also https://rusefi.com/forum/viewtopic.php?f=5&t=1642
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
|
||||
|
||||
|
||||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
||||
|
|
|
|||
|
|
@ -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"
|
||||
[//]: # "Matt Kennedy"
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
|
||||
|
|
@ -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
|
||||
|
||||
|
||||
## 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!
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
|
||||
|
||||
In rusEfi console `sdinfo` command could be used to query logging state.
|
||||
In rusEFI console `sdinfo` command could be used to query logging state.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
|||
|
||||
|
||||
|
||||
For development details see https://github.com/rusefi/web_backend
|
||||
For development details see https://github.com/rusefi/web_backend
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
||||
</details>
|
||||
</details>
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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?
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
See http://rusefi.com and https://github.com/rusefi/rusefi_documentation for more information about rusEFI
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
||||
|
|
|
|||
|
|
@ -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<br/>+ larger 154x152mm 4-layer board requires a Medium Box shipping rate<br/>+ on-board power supply<br/>+ 20x4 LCD screen<br/>+ joystick<br/>+ works both with external brain boards and on-board stm32 chip<br/>+ knock sensor chip<br/>+ used Denso OEM cases available | on-board 64 pin connector<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended |
|
||||
| [Prometheus](https://rusefi.com/forum/viewtopic.php?f=4&t=1215) | + The only rusEfi board with on-board wide band controller.<br/>+ compact 4-layer PCB smaller than 93 x 100 mm<br/>+ on-board power supply<br/>+ knock sensor chip<br/>+ stepper motor IAC controller chip<br/>+ stepper motor IAC controller chip<br/>+ onboard 4-channel "smart" protected ignition drivers<br/>+ bluetooth module<br/>+ supports two packages of on-board stm32 chips | no on-board connector (wired)<br/>SD card, USB/TTL, CAN | 2017 | 4 cylinder. No plans to offer assembled units. |
|
||||
| [Frankenstein](https://rusefi.com/forum/viewtopic.php?f=4&t=359) | + Simplest rusEfi board<br/>+ our smaller two-layer board<br/>+ Small Box shipping rate<br/>+ low price<br/>- external 5v power supply required<br/>- external brain board required | no on-board connector (wired)<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. |
|
||||
| [Prometheus](https://rusefi.com/forum/viewtopic.php?f=4&t=1215) | + The only rusEFI board with on-board wide band controller.<br/>+ compact 4-layer PCB smaller than 93 x 100 mm<br/>+ on-board power supply<br/>+ knock sensor chip<br/>+ stepper motor IAC controller chip<br/>+ stepper motor IAC controller chip<br/>+ onboard 4-channel "smart" protected ignition drivers<br/>+ bluetooth module<br/>+ supports two packages of on-board stm32 chips | no on-board connector (wired)<br/>SD card, USB/TTL, CAN | 2017 | 4 cylinder. No plans to offer assembled units. |
|
||||
| [Frankenstein](https://rusefi.com/forum/viewtopic.php?f=4&t=359) | + Simplest rusEFI board<br/>+ our smaller two-layer board<br/>+ Small Box shipping rate<br/>+ low price<br/>- external 5v power supply required<br/>- external brain board required | no on-board connector (wired)<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. |
|
||||
| [microRusEfi](Hardware-microRusEFI) | + Available fully assembled!<br/>+ about 10 analog inputs<br/>+ One VR/Hall input channel for crank sensor<br/>+ One Hall input channel for crank sensor<br/>+ 4 injector output channels<br/>+ 4 logic level coil control channels (external igniters could be needed for some coils) | 48-pin connector<br/>On-board DBW<br/>USB, CAN<br/>open source hardware | 2019 | 4 cylinder, single electronic throttle |
|
||||
| [Hellen](https://rusefi.com/forum/viewtopic.php?f=4&t=1682) | Coming soon! | modular design| 2020 | TBD cylinder, single electronic throttle |
|
||||
| [Proteus](Proteus) | + rusEfi if you have lots of hardware or cylinders<br/>+ 4 layer PCB, 135mm x 82.5mm<br/>+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)<br/>+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)<br/>+ Dual electronic throttles<br/>+ 4x High-side 12v drivers, 1 amp each<br/>+ 4 thermistor analog inputs (2.7k pull up resistor)<br/>+ 12 General purpose analog inputs<br/>+ Dual VR sensors (crank position, wheel speed)<br/>+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin<br/>rusEfi's most fully-featured shield<br/>IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles |
|
||||
| [Proteus](Proteus) | + rusEFI if you have lots of hardware or cylinders<br/>+ 4 layer PCB, 135mm x 82.5mm<br/>+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)<br/>+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)<br/>+ Dual electronic throttles<br/>+ 4x High-side 12v drivers, 1 amp each<br/>+ 4 thermistor analog inputs (2.7k pull up resistor)<br/>+ 12 General purpose analog inputs<br/>+ Dual VR sensors (crank position, wheel speed)<br/>+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin<br/>rusEFI's most fully-featured shield<br/>IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles |
|
||||
|
||||
|
||||
### Q: How to select a board?
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ For component placement please use interactive BOM
|
|||
[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
|
||||
|
||||
|
|
@ -130,4 +130,4 @@ Tag Connect In circuit Cable "NO Legs" Version
|
|||
|
||||
|
||||
### 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
|
||||
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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ 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
|
||||
|
||||
|
|
@ -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.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
[Spark Advance Modeling and Control](http://www.fs.isy.liu.se/Publications/PhD/99_PhD_580_LE.pdf)
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
In this folder we keep OEM documentation - so, no rusEfi content here
|
||||
In this folder we keep OEM documentation - so, no rusEFI content here
|
||||
|
|
|
|||
|
|
@ -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 | |
|
||||
|------|-----------|-----|-------|-------|---|---|
|
||||
|
|
|
|||
|
|
@ -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 RPM<target by adding extra percent to PID-error
|
||||
|
||||
|
|
|
|||
|
|
@ -216,11 +216,11 @@ Some older German vehicles
|
|||
TODO: implement a feature so that trigger could be defined via TunerStudio
|
||||
|
||||
|
||||
If your have an unknown or an unsupported trigger shape, once you've confirmed that trigger events are getting into the software (see "troubleshooting" sections) you need to crank your engine while rusEfi console is connected with Engine Sniffer tab active.
|
||||
If your have an unknown or an unsupported trigger shape, once you've confirmed that trigger events are getting into the software (see "troubleshooting" sections) you need to crank your engine while rusEFI console is connected with Engine Sniffer tab active.
|
||||
|
||||
With long enough cranking you should get a visual log of your trigger signal, that would give you some idea of what kind of trigger shape you have. Save an image and post it on a forum. It's recommended to remove spark plugs while investigating trigger shape to make your cranking more even.
|
||||
|
||||
Once preliminary shape of a new trigger is added into rusEfi firmware based on the Engine Sniffer image, second step is getting a more precise recording of the shape with exact angles. This is done with spark plugs removed and Sensor Sniffer mode set to TRIGGER. With long enough cranking a chart of trigger shape would appear on the Sensor Sniffer tab and the console log file (see out/ folder next to rusefi console binaries) would contain the angles. Please post this log file on the forum for the developers to encode the new trigger shape into the software.
|
||||
Once preliminary shape of a new trigger is added into rusEFI firmware based on the Engine Sniffer image, second step is getting a more precise recording of the shape with exact angles. This is done with spark plugs removed and Sensor Sniffer mode set to TRIGGER. With long enough cranking a chart of trigger shape would appear on the Sensor Sniffer tab and the console log file (see out/ folder next to rusefi console binaries) would contain the angles. Please post this log file on the forum for the developers to encode the new trigger shape into the software.
|
||||
|
||||
## How this works
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
## Intro
|
||||
|
||||
rusefi firmwave currently supports two protocols for ECU monitoring & control
|
||||
rusEFI firmware currently supports two protocols for ECU monitoring & control
|
||||
|
||||
1. human-readable native protocol - connect to the ECU using HyperTerminal. This used to be protocol rusEfi console was using but not any more, we are moving towards not having text protocol enabled by default.
|
||||
1. human-readable native protocol - connect to the ECU using HyperTerminal. This used to be protocol rusEFI console was using but not any more, we are moving towards not having text protocol enabled by default.
|
||||
|
||||
|
||||
[List of commands](Dev-Console-Commands)
|
||||
|
|
@ -11,7 +11,7 @@ rusefi firmwave currently supports two protocols for ECU monitoring & control
|
|||
[Java console code overview](Dev-Console-Implementation)
|
||||
|
||||
|
||||
2. binary protocol for integration with rusEfi console or http://www.tunerstudio.com/ tuning software
|
||||
2. binary protocol for integration with rusEFI console or http://www.tunerstudio.com/ tuning software
|
||||
See [tunerstudio.cpp](https://sourceforge.net/p/rusefi/code/HEAD/tree/trunk/firmware/console/binary/tunerstudio.cpp) for a brief description of this binary protocol
|
||||
|
||||
For physical level rs232 is used ("serial port") - either via a FL232 chip or by emulating a USB device right within stm32f4. A bluetooth option is also available.
|
||||
|
|
@ -27,4 +27,4 @@ A: Not really. Our text-based protocol has support for human-readable messages a
|
|||
The protocol has better support for engine tuning in terms of editing individual cells on fuel maps etc.
|
||||
|
||||
Q: Is the binary protocol compatible with MegaSquirt?
|
||||
A: Kind of, but not really. The general protocol is the same, but the packet format is rusEfi specific. All this works based on TunerStudio packet definition flexibility.
|
||||
A: Kind of, but not really. The general protocol is the same, but the packet format is rusEFI specific. All this works based on TunerStudio packet definition flexibility.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
## rusEfi power supply troubleshooting guide
|
||||
## rusEFI power supply troubleshooting guide
|
||||
|
||||
http://www.ti.com/product/lm2596
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ http://www.pololu.com/file/download/a4988_DMOS_microstepping_driver_with_transla
|
|||
|
||||
Use a jumper or wire to connect SLEEP with RESET
|
||||
|
||||
For first test, leave ENABLE disconnected. Once tested, connect stepper enable to rusEfi 'stepper enable' pin
|
||||
For first test, leave ENABLE disconnected. Once tested, connect stepper enable to rusEFI 'stepper enable' pin
|
||||
|
||||
We do not have our own add-on board for a4988, we use ones from eBay like "stepper motor driver A4988 with Heat sinks"
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ See also [Troubleshooting](Troubleshooting)
|
|||
|
||||
In order to configure coolant temperature sensor or intake air sensor you would need to know it's resistance at three temperatures - lowest, highest and somewhere in between. You would also need to know the value of pull-up 'bias' resistor, which together with your sensor would make a voltage divider.
|
||||
|
||||
While troubleshooting CLT and IAT, the two most useful commands are `analoginfo` and `tempinfo` - these show you the voltage registered by rusEfi alongside with input pins and resistance processing values.
|
||||
While troubleshooting CLT and IAT, the two most useful commands are `analoginfo` and `tempinfo` - these show you the voltage registered by rusEFI alongside with input pins and resistance processing values.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,9 +9,9 @@ to start supporting more trigger options.
|
|||
|
||||
At the moment rusEFI has only one channel of VVT position input.
|
||||
|
||||
rusEfi trigger configuration is the most confusing part of rusEfi configuration unfortunately.
|
||||
rusEFI trigger configuration is the most confusing part of rusEFI configuration unfortunately.
|
||||
|
||||
If rusEfi does not know your exact overall trigger shape and you use composite setup with crank sensor driving RPM and single tooth cam sensor providing phase information, that's considered "4 stroke without cam with VVT". Even if you do not have VVT :(
|
||||
If rusEFI does not know your exact overall trigger shape and you use composite setup with crank sensor driving RPM and single tooth cam sensor providing phase information, that's considered "4 stroke without cam with VVT". Even if you do not have VVT :(
|
||||
|
||||
|
||||
## VVT mode 'first half'
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ See [list of all supported triggers](All-Supported-Triggers)
|
|||
|
||||
## Troubleshooting trigger input
|
||||
|
||||
### Troubleshooting hardware with rusEfi console
|
||||
### Troubleshooting hardware with rusEFI console
|
||||
|
||||
Use `triggerinfo` command (go to Messages tab, your can either type or use a button from the panel on the right) to confirm input pin(s). Also use `triggerinfo` command to see how many trigger events were registered by the firmware ("trigger#1 event counters up=x/down=y").
|
||||
|
||||
|
|
@ -18,11 +18,11 @@ test #1: GND input channels 11 and 12, tell me what you read on W211 and W212
|
|||
|
||||
test #2: float input channels 11 and 12, tell me what you read on W211 and W212
|
||||
|
||||
### Troubleshooting synchronization rusEfi console
|
||||
### Troubleshooting synchronization rusEFI console
|
||||
|
||||
Type `enable trigger_details` in rusEfi console to enable verbose synchronization logging. Post from 'Messages" output on the forum.
|
||||
Type `enable trigger_details` in rusEFI console to enable verbose synchronization logging. Post from 'Messages" output on the forum.
|
||||
|
||||
"print sync details to console" in TS enables the same output but the output still goes only to rusEfi console.
|
||||
"print sync details to console" in TS enables the same output but the output still goes only to rusEFI console.
|
||||
|
||||
### Troubleshooting with TunenStudio
|
||||
|
||||
|
|
@ -30,21 +30,21 @@ Enable Trigger Counters
|
|||
|
||||
|
||||
|
||||
Channel #1 counter would be "debug i1" gauge and channel #2 is "debug i2". These values should go up if you are cranking and that confirms that the events are being registered by rusEfi firmware.
|
||||
Channel #1 counter would be "debug i1" gauge and channel #2 is "debug i2". These values should go up if you are cranking and that confirms that the events are being registered by rusEFI firmware.
|
||||
|
||||
|
||||
|
||||
## Trigger Simulation
|
||||
|
||||
rusEfi has a feature of trigger signal emulation on Trigger Simulator Pins. All channels of trigger input would be simulated on corresponding channels of Trigger Simlator.
|
||||
rusEFI has a feature of trigger signal emulation on Trigger Simulator Pins. All channels of trigger input would be simulated on corresponding channels of Trigger Simlator.
|
||||
|
||||
At the moment rusEfi has no means for VVT/camInput simulation.
|
||||
At the moment rusEFI has no means for VVT/camInput simulation.
|
||||
|
||||
## Q & A
|
||||
|
||||
**Q: what is _globalTriggerAngleOffset_ configuration parameter?**
|
||||
|
||||
A: On engine sniffer tab in rusEfi console, there is a signal front with "0" next to it. That's the trigger synchronization event on the primary trigger line. The trigger synchronization always happens at one of the rise of fall of the primary trigger. globalTriggerAngleOffset is the angle distance between synchronization point and cylinder #1 top dead center. TDC#1 is the green line by the way.
|
||||
A: On engine sniffer tab in rusEFI console, there is a signal front with "0" next to it. That's the trigger synchronization event on the primary trigger line. The trigger synchronization always happens at one of the rise of fall of the primary trigger. globalTriggerAngleOffset is the angle distance between synchronization point and cylinder #1 top dead center. TDC#1 is the green line by the way.
|
||||
|
||||
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ A: try _enable trigger_details_ command in console or "print sync details to con
|
|||
|
||||
*Q: I have a 60/2 crank wheel and I would like to use a cam sensor for fully sequential mode. Should I use "4-stroke with Cam sensor"?*
|
||||
|
||||
A: You can only use "4-stroke with Cam sensor" if your composite trigger shape is known to rusEfi. If you are adding a cam to 60/2, rusEfi probably does not know this combination with all the angles precisely. The way to add sequential to a skipped-tooth crank wheel is via cam input mode, same as used for VVT (see also [VVT](VVT))
|
||||
A: You can only use "4-stroke with Cam sensor" if your composite trigger shape is known to rusEFI. If you are adding a cam to 60/2, rusEFI probably does not know this combination with all the angles precisely. The way to add sequential to a skipped-tooth crank wheel is via cam input mode, same as used for VVT (see also [VVT](VVT))
|
||||
This case your known crank shape is used for shaft position lookup and your cam is only used for phase lookup - exact cam sensor angular position is less important.
|
||||
|
||||
See also [VVT](VVT)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
At the moment the only way to add a new trigger pattern is by having rusEfi developers add a little bit of code into the firmware along the lines of:
|
||||
At the moment the only way to add a new trigger pattern is by having rusEFI developers add a little bit of code into the firmware along the lines of:
|
||||
|
||||
s->addEvent(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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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) | | |
|
||||
||| | | | | |
|
||||
||| | | | | |
|
||||
||| | | | | |
|
||||
||| | | | | |
|
||||
||| | | | | |
|
||||
|
|
@ -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 |
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue