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

Update Java version dependency (#242) 

- fix some markdownlint warnings
This commit is contained in:
mi-hol 2022-11-07 19:08:45 +01:00 committed by GitHub
parent fc74d404e5
commit 639dda2eb0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
HOWTO/Console.md
View File

@ -1,13 +1,14 @@
rusEFI Console 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.
# rusEFI Dev Console - Overview
rusEFI Dev Console 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.
To get the console working follow the below procedure, which assumes you have loaded the rusEFI firmware.
To get the console working follow the below procedure, which assumes you have loaded the rusEFI firmware.
* Either power externally, or connect the "programming" USB cable as shown below. This will provide power to the Discovery board.
* Connect the micro USB cable, see "console" cable shown below. When you do this for the first time, on a Windows PC, you will be prompted for drivers. You should download & install the drivers from [here](http://www.st.com/web/en/catalog/tools/PF257938). #: ![Jumper Setup](Images/rusEFI_STM.jpg)
* When the driver is installed & the board is connected via the micro USB cable, you can verify serial connectivity by
* When the driver is installed & the board is connected via the micro USB cable, you can verify serial connectivity by
* '''Windows''' - opening your Device Manager - we are expecting to see a Virtual COM Port
![Device Manager screenshot](http://rusefi.com/images/forum_posts/device_manager.png)
* '''Linux'''
* '''Linux'''
* ''Ubuntu (11.10)'' - plug in the "console" USB cable, then check the message log with this command.
```
$ dmesg
@ -17,14 +18,15 @@ 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](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](http://rusefi.com/build_server/rusefi_bundle.zip) (part of the same bundle)
* Note: rusEFI Dev Console requires java 1.8 or later!
* 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`
* Linux (ubuntu 11.10)
`java -jar rusefi_console.jar /dev/ttyACM0`
* You got it to open, great! Now install gray jumper wire as noted above between pins PD1 and PC6.
* Select "digital sniffer" in the dev console and you should see the simulated signal.
* You got it to open, great! Now install gray jumper wire as noted above between pins PD1 and PC6.
* Select "digital sniffer" in the dev console and you should see the simulated signal.
* Install the blue jumper wire as noted between pins PD2 and PA5.
![Jumper Wire](Images/discovery_and_wires.jpg)
* You should see the crank signals as noted in the "sniffer" tab.