rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix typos and md syntax

This commit is contained in:
mi-hol 2022-12-30 18:33:08 +01:00
parent 217e149c0a
commit 963271e041
3 changed files with 10 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.vscode/settings.json vendored
View File

@ -14,6 +14,7 @@
"ELANTRA",
"Festiva",
"Frankenso",
"FTDI",
"Galant",
"GSXR",
"Haltech",
@ -43,6 +44,7 @@
"superseal",
"Terrano",
"triggerinfo",
"tunerstudio",
"tyco",
"Vitara",
"Vref",

6
Common-Issues.md
View File

@ -1,9 +1,9 @@
## Protoboard does not show the ON light
# Prototype board does not show the ON light
Isolate to only USB power by disconnecting from vehicle and plugging in to USB power. If that helps. There is probably a problem with the 12V power supply.
Check the 3.3V LED
Check the 3.3V LED.
## ON light is bright, but can not communiate over USB
## ON light is bright, but can not communicate over USB
Check that the FTDI driver is installed and that you find your COM port.

12
Connectivity.md
View File

@ -1,15 +1,12 @@
## Intro
# Intro
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.
[List of commands](Dev-Console-Commands)
[List of commands](Dev-Console-Commands)
[Java console code overview](Dev-Console-Implementation)
[Java console code overview](Dev-Console-Implementation)
2. binary protocol for integration with rusEFI console or [TunerStudio](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
@ -17,13 +14,12 @@ See [tunerstudio.cpp](https://sourceforge.net/p/rusefi/code/HEAD/tree/trunk/firm
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.
![FTDI IC pads](Images/ftdi.png)
[Forum thread](http://rusefi.com/forum/viewtopic.php?f=5&t=210)
## Q&A
Q: Why two protocols? can you achieve the same results using both protocols?
A: Not really. Our text-based protocol has support for human-readable messages and it handles our own build-in logic anayzer - it is better for troubleshooting.
A: Not really. Our text-based protocol has support for human-readable messages and it handles our own build-in logic analyzer - it is better for troubleshooting.
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?