Wiki porting bedtime dump (#85)

* add Accelerometer, Connectivity, add stuff to Hardware Guidelines

* dev notes

* switch to hyphen

* Frankenso soldering

* add adaptive suspension

* add max232

* added details to Hardware table

* added details to Hardware table

* fix table

* added OEM 121 pin connectors

* port oem connectors, change names from drawing to render

* missing pic

* missing pic

* add some more pages

* add repair pages

* wrong dir

* add build server

* add debug fields

* fix table

* add Console

Accelerometer.md

@@ -0,0 +1 @@
+http://00xnor.blogspot.com/2014/03/stm32-f4-spi-accelerometer.html

Adaptive-Suspension.md

@@ -0,0 +1,61 @@
+https://rusefi.com//wiki/index.php?title=Hardware:Shock_Dyno
+
+https://arstechnica.com/cars/2015/07/the-future-of-car-suspension-is-here-dsc-sports-active-shocks-in-action/
+"Normally, a car's weight transfers from front to back as it brakes and accelerates, and from side to side as it corners. As the force on each corner changes, so does the grip available to that wheel; less weight equals less grip. Active shocks control this by varying the degree to which each spring's compresses and extends (as the springs are passive, these systems are sometimes known as semi-active)."
+
+
+http://en.wikipedia.org/wiki/Active_suspension
+
+https://en.wikipedia.org/wiki/Active_suspension pasm 
+
+http://www.f1fanatic.co.uk/2007/05/17/banned-active-suspension/
+
+http://en.wikipedia.org/wiki/Northstar_engine_series
+Road Sensing Suspension
+RSS
+CV-RSS continuously-variable CV-RSS
+
+https://en.wikipedia.org/wiki/MagneRide#Applications
+
+https://en.wikipedia.org/wiki/Toyota_Active_Control_Suspension
+
+"yaw velocity sensors, vertical G sensors, height sensors, wheel speed sensors, longitudinal and lateral G sensors) that detected cornering, acceleration and braking forces"
+
+Mercedes-Benz hydraulic fully active suspension: https://en.wikipedia.org/wiki/Active_Body_Control
+W220: "Prior to September 2002, only higher end models" S600 2003 "ABC system which combined an hydraulic system and springs"
+Furthermore, at highway speeds the suspension computer automatically engages sport mode (Airmatic - Sport mode 1 or 2 depending on the current speed), thus aiding safety by significantly reducing body roll in sharp turns.
+
+
+http://www.drifting.com/forums/tech-discussion-forum/6741-suspension-101-stiffer-is-better-text-by-tanabe-u-s-a.html
+
+http://www.cadillacforums.com/forums/suspension-brakes-tires/175670-article-tells-how-cvrss-works.html
+
+http://www.corvetteactioncenter.com/tech/c5/activehandling.html
+
+http://www.dscsport.com/wp-content/uploads/2017/01/DSC-Sport_Software-User-Manual.pdf
+
+https://www.corvetteforum.com/forums/c6-corvette-general-discussion/3778441-how-does-the-ebcm-communicate-with-the-yaw-sensor.html
+
+Used hardware:
+
+2005 Strut Cadillac STS ~$75
+
+http://www.cadillacforums.com/forums/cadillac-seville-cadillac-eldorado-forum/212531-fe1-suspension-system-soft-ride-soft.html
+"2000 Seville STS - 98 to 2004 F45 is CVRSS"
+
+gm 22784742 
+
+"it has rotory sensors on the frame that connect to each lower suspension a arm. these give the rate of bump and rebound, and Rate of travel"
+
+2011 Cts-v Rear Magnetic Ride Control Yaw Sensor Left Rear Driver
+
+buick regal 13319741
+
+yaw sensor
+
+http://jalopnik.com/5932764/how-magnets-make-the-camaro-zl1-dance-around-a-race-track
+
+
+https://www.youtube.com/watch?v=DS9LjHSTofw
+
+shock connector adapter GM 19180262 https://www.cadillacforums.com/forums/cadillac-escalade-ext-esv-forum-2007/1067118-how-delete-z95-front-rear-mrc.html

Build-Server.md

@@ -0,0 +1,99 @@
+Github Actions is currently in charge of:
+* Firmware Builds
+* Console Builds
+* Simulator Builds
+* Android App Builds
+* TS Plugin Builds
+* Generating configs
+* Running Unit Tests
+* Generating Coverity code coverage pages
+* Generating Doxygen documentation
+* Generating iBOMs for hardware
+* Generating Hardware PCB visual diffs
+* Updating date stamps for builds
+* Synchronizing between rusefi/rusefi/wiki to rusefi_documentation repo
+
+We have tried to keep Jenkins working in case we need to revert to it.
+
+## Jenkins setup
+
+### Jobs:
+1) unit_tests
+2) integration_and_primary_bundle
+3) documentation
+4) build_extra_bundles
+5) git2svn_sync
+
+### Install Cygwin
+https://cygwin.com/install.html
+
+Cygwin packages that need to be installed:
+- make
+- gcc-core
+- mingw64-i686-gcc-core
+- mingw64-i686-gcc-g++
+- mingw64-x86_64-gcc-core
+- mingw64-x86_64-gcc-g++
+- python3
+- git
+- subversion
+- doxygen
+- zip
+- ncftp
+- wget
+- ccache
+- graphviz
+
+### Install Java JDK 8
+https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html
+
+### Install Ant:
+https://ant.apache.org/
+
+### Install Jenkins
+https://jenkins.io/download/
+
+### Install Kicad
+http://www.kicad-pcb.org/download/
+for iBom automation
+
+### Install for Hardware Testing
+#### ST Link Utility  
+http://www.st.com/st-web-ui/static/active/en/st_prod_software_internet/resource/technical/software/utility/stsw-link004.zip
+#### ST Virtual Serial Driver
+http://www.st.com/web/en/catalog/tools/PF257938
+
+### System Environment Variables:
+|Variable|Example|
+|--|--|
+|CCACHE_DIR|C:\ccache  |
+|ANT_HOME|C:\Program Files\apache-ant-1.10.8|
+|JAVA_HOME|C:\Program Files\Java\jdk1.8.0_251|
+|RUSEFI_FTP_SERVER|ftp.yourdomain.com|
+|RUSEFI_BUILD_FTP_USER|rusefi_firmware|
+|RUSEFI_BUILD_FTP_PASS|secretpass|
+|RUSEFI_DOXYGEN_FTP_USER|rusefi_doxygen|
+|RUSEFI_DOXYGEN_FTP_PASS|secretpass|
+
+### Add to Path:
+|Tool|Example|
+|--|--|
+|Java|C:\Program Files (x86)\Common Files\Oracle\Java\javapath|
+|Java|%JAVA_HOME%\bin|
+|Ant|%ANT_HOME%\bin|
+|Cygwin|C:\cygwin64\bin|
+|GCC|C:\Program Files (x86)\GNU Arm Embedded Toolchain\9 2020-q2-update\bin|
+
+### Additional Jenkins set-up
+#### Additional plugins:
+- Pipeline GitHub Notify Step
+
+https://stackoverflow.com/questions/14274293/show-current-state-of-jenkins-build-on-github-repo
+
+https://github.com/settings/tokens
+
+Discard Old Build
+
+smtphost: smtp.gmail.com
+r***@gmail.com
+useSsl=yes

Code-Style.md

@@ -4,4 +4,29 @@
 
 * Please do not push dead code
 
-See here: https://rusefi.com/wiki/index.php?title=Development:Code_Style
+We make with -std=c++11 see https://github.com/rusefi/rusefi/blob/master/firmware/Makefile
+
+
+## Brackets
+Only the simplest, two-line if/for/while should not have the curly brackets. Anything more than two lines should have {}.
+
+```
+if (plain_condition)
+   oneLineStatement();
+
+if (plain_condition) {
+   // comment
+   oneLineStatement();
+}
+
+if (plain_condition) {
+   oneLineStatement();
+} else {
+   oneLineStatement2();
+}
+```
+
+## Code Formatting
+Code formatting matters. The de-facto standard is Eclipse CDT (K&R) with one change: Maximum line width = 120
+
+This standard is far from perfect, but it's good enough for now.

Connectivity.md

@@ -0,0 +1,30 @@
+## Intro
+
+rusefi firmwave 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](http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands)
+
+
+[Java console code overview](http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_implementation)
+
+
+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.
+![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.
+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.

Console.md

@@ -0,0 +1,29 @@
+## Gauges
+
+## Analog Chart
+
+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 always displays the signal for a duration of one complete engine cycle.
+
+Currently analog chart can display one of these two things
+
+1. trigger signal shape. the value consists of the trigger signal index and fall/rise type of the event
+
+`set_analog_chart_mode 1`
+
+2. MAP sensor signal
+
+`set_analog_chart_mode 2`
+
+## Digital Chart
+
+![Log Viewer](Images/log_viewer.png)
+
+Greed line is a border of engine cycle. Please note that the angle within current engine cycle is displayed in the bottom left corner - the angle is from 0 to 720 in case of a four stroke engine.
+
+Red line is just absolute time scale. One line per second? Per 100ms? Something like that. TODO.
+
+## Log Viewer

Debug-Fields.md

@@ -0,0 +1,29 @@
+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`
+
+
+| code | name | debug f1 | debug f2 | debug f3 | debug f4 | debug f5 | debug f6 | debug f7 | debug i1 | debug i2 | debug i3 | debug i4 | debug i5
+|-|-|-|-|-|-|-|-|-|-|-|-|-|-|
+| 0 | Alternator_PID | controller output | integration term | previous error | I setting | D setting | dTerm | maxValue | P setting | offset | settings change counter
+| 1 | TPS acceleration | from TPS | to TPS | current TPS<>TPS value | extra fuel
+| 2 | Warmup PID | 3 | Idle | controller output | integration term | previous error | I setting | D setting | dTerm | maxValue | P setting | offset | settings change counter
+| 4 | Engine load acceleration
+| 5 | Trigger Counters | channel #1 rise counter | channel #2 rise counter | channel #3 rise counter | | | | | channel #1 fall counter | channel #2 fall counter | channel #3 fall counter
+| 6 | FSIO ADC
+| 7 | Aux PID #1 | controller output | integration term | previous error | I setting | D setting | dTerm
+| 8 | VVT position | | | | | | | | VVT event counter
+| 9 | Cranking | | | | | | | | cycles from start counter
+| 11 | short-term closed loop fuel PID | | integration term | previous error | I setting | D setting | dTerm | maxValue | P setting | offset | settings change counter
+| 12 | VSS | | | | | | | | vss event counter
+| 17 | ETB electronic throttle body PID | duty cycle | integration term | previous error | I setting | D setting | dTerm | maxValue | P setting | offset | settings change counter
+| 21 | ADC #1 / Analog Inputs | VBatt | TPS | MAF | MAP | CLT | IAT | EGO
+| 23 | FSIO_EXPRESSION | FSIO output #1 | FSIO output #2 | FSIO output #3 | FSIO output #4 | FSIO output #5 | FSIO output #6 
+| 24 | Status | Seconds since reboot | | | | | | | VCS_VERSION
+| 25 | CJ125 | Heater Duty | Heater PID I Term | Heater PID Err | UA | UR | Calibr.UA | Calibr.UR | State | Diag.reg
+| 26 | CAN | | | | | | | | read counter | write OK | write NOT ok
+| 31 | TLE8888 | | | | | | | | SPI counter | latest transmit | latest recieved | init count (should be 2) | i5
+
+![Base Engine Settings](Images/1-Base_Engine_Settings.png)
+
+![Debug Gauges](Images/debug_gauges.png)

Dev-Hardware-Guidelines.md

@@ -6,6 +6,23 @@ suggestions on how to design and work with things like a PCB layout.
 
 ---
 
+## Basic principles
+
+We are developing hardware using [KiCad EDA Suite](http://www.kicad-pcb.org/)
+Our file repository for hardware is https://github.com/rusefi/rusefi/tree/master/hardware
+For now we are developing hardware as individual functional modules. While all individual modules are in-depended from each over, the use the share the same component library which is located at https://github.com/rusefi/kicad-libraries
+
+## Collaboration process
+Since patch files do not work well for hardware projects, our collaboration process is pulling whole folders from the SVN where board author would develop them into the central SVN which is the unified repository. That's a poor man workaround over the lack of free SVN hosting with directory user permissions.
+
+
+## Naming convention
+Name capacitors with uF and pF only. So 100nF is a no go while 0.1uF is good.
+This works better with filter/sort operations in spread sheets.
+Also start the name with 0.1 instead of .1.
+
+Resistors should be listed like this 100R or 2k2
+
 ## General suggested environment
 - Allow an ambient temperature from -40C to +85C (-40F to 185F) AEC Q100 Grade 3  
 - Voltage regulators that are compatible with ISO 7637-2 and ISO16750-2 (100V repetitive pulses via 50ohm impedance, 18 V for 60 min, 24V for 60s to all relevant inputs, withstand a reversed voltage for 60s, 500V rms (50 Hz to 60 Hz) for 60s, ect).  
@@ -103,4 +120,4 @@ http://rusefi.com/wiki/index.php?title=Manual:Hardware:CAN_sniffer
 
 [2003 dodge Neon test mule](https://rusefi.com/forum/viewtopic.php?f=3&t=696)
 
-[Connector boards](https://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors)
+[Connector boards](https://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors)

Dev-Quality-Control.md

@@ -0,0 +1,7 @@
+We love our engines and we want them to live a long & happy life. That's why we have a three-tier quality assurance process:
+
+* Continuous Integration: Unit testing with [Github Actions](https://github.com/rusefi/rusefi/actions?query=workflow%3A%22Unit+Test+CI%22)
+* built-in trigger signal simulation
+* [Simulator](Virtual_simulator)
+
+For current coverage report see https://rusefi.com/docs/unit_tests_coverage/

FAQ/HOWTO-contribute-to-firmware.md

@@ -7,8 +7,14 @@ A good first contribution could be adding some automated testing into https://gi
 
 For current coverage report see https://rusefi.com/docs/unit_tests_coverage/
 
+Doxygen source code documentation is found [here.](https://rusefi.com/docs/html/)
+
+Our primary tool-chain is GCC+Eclipse but we also support IAR. 
+
 Testing coverage open tickets: https://github.com/rusefi/rusefi/labels/automated_testing
 
 All open tickets: https://github.com/rusefi/rusefi/issues
 
-See https://rusefi.com/wiki/index.php?title=Manual:Try_It for how to work on rusEfi code with zero or minimal hardware.
+See https://rusefi.com/wiki/index.php?title=Manual: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)

Hardware/Frankenso/Frankenso-Hand-Soldering-Step-By-Step.md

@@ -0,0 +1,52 @@
+This page is dedicated to my experience with Frankenso 0.5 board, especially manual soldering and bringing it to life.
+
+## Prerequisites
+
+Mandatory links:
+[Frankenso Hardware](Hardware_Frankenso)
+https://rusefi.com/wiki/index.php?title=Manual:Hardware_Test_Mode<br>
+https://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_connectivity<br>
+https://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#step_3:_Analog_Inputs<br>
+https://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger<br>
+https://rusefi.com/wiki/index.php?title=Manual:Software_Temperature_Sensors<br>
+https://docs.google.com/spreadsheets/d/1LTvS7I-128Hft9uXHG1JrBxetVjGJDSBkySgVDQ6MGk/edit#gid=0
+
+
+First you need the board. Then you need the components. I decided to select and buy the components step-by-step.
+
+![Frankenso 0.5 bare board](Hardware/Frankenso/Frankenso-0.5-naked.jpg)
+
+Before you begin it would be helpful if you have experience with KiCad. Sometimes it is more convenient to use it to explore the schematic and the PCB files.
+The latest Frankenso files can be found here: https://github.com/rusefi/rusefi/tree/master/hardware/frankenso
+
+## Helpful files
+
+* [frankenso.csv ](https://github.com/rusefi/rusefi/blob/master/hardware/frankenso/frankenso.csv)
+* [frankenso_PCB.pdf](https://github.com/rusefi/rusefi/blob/master/hardware/frankenso/frankenso_PCB.pdf)
+* [frankenso_schematic.pdf](https://github.com/rusefi/rusefi/blob/master/hardware/frankenso/frankenso_schematic.pdf)
+
+Make sure to look at the file frankenso.csv. This is a list of the components of the board. You can import it with program like MS Excel or other CSV (comma separated values) viewer.
+In MS Excel you can import it going to tab "Data", select "From Text" from "Get External Data" group, now you browse to the file and select it, "Import" , "Delimited" (next) , You chose "Comma", then Finish. Here is a pdf version of the file. I printed it in order to make  a quick reference.
+
+I made the table borders black, set the page margins to "Narrow" , orientation to "Landscape", forced "Wrap text" to the first column in order to fit all the components in one row, and all this in order to make everything on single page. You can see the file [[File:Frankenso-0.5-components.pdf]]. It is best to print this list.
+
+Next is to print all the pages from frankenso_schematic.pdf. Currently there are 15 pages. This is the most important think to do because you'll use it to note the soldered and the remaining components to be soldered.
+
+## Identifying the different sections
+
+I decided to start with the power supply / voltage converter. After the required output voltage is available (no chance to burn the components on the first run) I choose the MCU, because it is much more easier to solder in the absence of the other components. You can actually start with it if you feel more comfortable to solder LQFP-100 on bare board. The jumper W23 connects the 5V output from the buck converter to the power plane.
+
+**If you aren't experienced in soldering LQFP or similar packes better go with the development board! The price is not much higher and you'll save a lot of time.** My idea to solder the MCU directly to the board was to decrease the lengths of the tracks in order to decrease noise.
+
+The remaining parts I group by the engine components, see the following table:
+
+### Engine components
+* Crankshaft position sensor 
+* Camshaft position sensor
+* Mass Air Flow sensor
+* Throttle position sensor
+* Knock sensor
+
+## Step 1 - Voltage converter
+
+![Voltage converter](Frankenso-0.5-power.jpg)

Hardware/Hardware.md

@@ -5,14 +5,14 @@ As of March 2020 microRusEFI is sold as completely ready to run ECU or as a pre-
 
 As of March 2020 Frankenso board is sold as mostly as a DIY kit.
 
-| Board | Features | Released in | Maximum recommended engine |
-| ------------- | ------------- | ---- | ---- |
-| [Frankenso](Hardware_Frankenso) | Most customizable board | 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. | 2017 | 4 cylinder. No plans to offer assembled units. |
-| [Frankenstein](https://rusefi.com/forum/viewtopic.php?f=4&t=359)  | Simplest rusEfi board | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. |
-| [microRusEfi](Hardware_microRusEfi) | Available fully assembled! | 2019 | 4 cylinder, single electronic throttle |
-| [Hellen](https://rusefi.com/forum/viewtopic.php?f=4&t=1682) | Coming soon! | 2020 | TBD cylinder, single electronic throttle |
-| [Proteus](Proteus) | rusEfi if you have lots of hardware or cylinders | 2020 | 12 cylinder, dual electronic throttles |
+| 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. |
+| [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 |
 
 
 ### Q: How to select a board?

Hardware/connectors/OEM-121-pin-connectors.md

@@ -0,0 +1,65 @@
+Disclaimer: the following observations could be really wrong, please let me know if you have better information. 
+
+See also https://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#121_pin
+
+
+There are two kinds of 121 connectors which look pretty much the same but do not mate together unless you use a grinder to massage them a bit.
+
+
+## 368255/Asian
+http://www.te.com/catalog/pn/en/368255-2
+
+This one is used on Asian vehicles - Kia Hyundai etc.
+
+See also http://rusefi.com/wiki/index.php?title=Vehicle:Kia_Spectra_2005 
+
+![368255 Asian render](Hardware/connectors/368255_render.png)
+
+Note the horizontal line and the lack of double-lines
+
+![368255 Asian Top Photo](Hardware/connectors/368255_top.jpg)
+
+## 1241434/German
+
+http://www.te.com/catalog/pn/en/1241434-1
+
+This one is used on Audi, VW, Mini Cooper.
+
+![1241434 German render](Hardware/connectors/1241434_render.png)
+
+Note the double-lines:
+
+![1241434 German render Top](Hardware/connectors/1241434_render_top.png)
+
+![1241434 German Top Photo](Hardware/connectors1241434_top.jpg)
+
+## How to make a German plug work with an Asian header
+
+Use a grinder on the plug. This would probably void your warranty.
+
+Before grinding:
+
+![Before Shaving](Hardware/connectors/before_shaving.jpg)
+
+Take the orange rubber piece away while grinding. Grind a bit on the inside.
+
+![After Shaving](Hardware/connectors/after_shaving.jpg)
+
+Re-install the rubber ring.
+
+![After Shaving With Gasket](Hardware/connectors/after_shaving_2.jpg)
+
+This way you should be able to use a "German" style plug on a "Asian" style connector.
+
+![Final Result](Hardware/connectors/final_result.jpg)
+
+
+There is also a 115 pin version - 6 pins are left out (14, 15, 16, 33, 34, 35)
+
+## pinouts
+
+https://rusefi.com/wiki/index.php?title=Vehicle:Kia_Spectra_2005
+
+https://rusefi.com/wiki/index.php?title=Vehicle:Mini_Cooper_2003
+
+https://rusefi.com/wiki/index.php?title=Vehicle:Nissan_Xterra_2011

Hardware/connectors/OEM-connectors.md

@@ -0,0 +1,414 @@
+Do you know part numbers for any other OEM connectors? Please let us know!
+
+Here are some OEM connector part numbers. Bosch & Siemens, German and Japanese, Mazda Toyota BMW Volkswagen:
+
+
+## 30 pin
+
+https://www.te.com/global-en/product-172491-1.html
+
+18+12
+
+ADM 22RE
+
+## 34 pin
+Superseal 6437288-1 and 6437288-2
+
+https://www.te.com/usa-en/product-6437288-1.html
+https://www.te.com/usa-en/product-6437288-2.html
+
+
+Suzuki GSXR1300 Hayabusa ECU (99'-07')
+
+Yamaha YZF-R1 2009-2011 ECU
+
+Many aftermarket ECUs
+
+## 35 pin
+http://www.te.com/catalog/pn/en/825213-1
+
+![35 Pin connector](Hardware/connectors/35_pin.png)
+
+## 38 pin
+
+Chrysler Next Generation Controller NGC
+
+Female wire side
+
+INDEX A 9-1326726-8
+
+INDEX B 9-1326727-8
+
+INDEX C 9-1326728-8
+
+INDEX D 9-1326729-8
+
+PCB side unavailable Mates to 
+05087006AB
+05087007AB
+05087008AA
+05087009AA
+
+## 42 pin two piece
+
+26+16
+
+175446 https://www.te.com/usa-en/product-175446-1.html
+
+## 42 pin three piece
+172489-7
+
+http://www.te.com/usa-en/product-172489-7.html
+
+10+18+14
+
+Toyota Camry, early 22R(T)E and 4AGE
+
+See also https://www.te.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F108-5157%7FB%7Ftif%7FEnglish%7FENG_SS_108-5157_B.tif%7F172315-7
+
+## 48 pin
+http://www.te.com/catalog/pn/en/174917-6
+Escort GT, Ford Festiva, Miata NA6 manual
+
+The larger plugs are the same as on http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#64_pin
+
+## 52 pin
+http://www.te.com/usa-en/product-172319-1.html
+
+10+18+24
+18 pin housing 172316-7
+10 pin housing 172315-7
+contacts 170353-1 
+
+Toyota early 3SGE, 7MGTE and 4AGZE
+
+Galant VR4, Eclipse 1G
+
+## 54 pin
+
+175448-6
+
+26+16+12
+
+last 22RE, 4AGE, 4/7AFE
+
+## 55 pin
+https://www.te.com/usa-en/product-963063-1.html
+
+http://www.te.com/catalog/pn/en/963063-2
+
+http://rusefi.com/forum/viewtopic.php?f=4&t=616
+
+ECU connector for 1990-1995 Porsche 911
+
+ECU connector for 1987-1988 Porsche 944 S
+
+ECU connector for 1992-1995 Hyundai Scoupe
+
+ECU connector for 1987-1992 BMW
+
+harness side - 292096-1
+harness side - 963532
+terminals 144431-3 and 144431-1
+
+some Audi around 1990
+
+Citroen Berlingo m49, Citroen Xara
+
+Lada Samara
+
+![55 pin connector](Hardware/connectors/55_pin.png)
+
+For sale @ http://www.ebay.com/usr/rusefi
+
+## 2 row 55 pin
+sagem/renault
+
+https://www.te.com/usa-en/product-828763-1.html
+
+Female side 85193-2
+https://www.te.com/usa-en/product-85193-2.html
+
+## 60 pin
+
+Ford todo :)
+
+Terminals are E7EB-14488-GA (18 ga) and E7EB-14488-NA (14 ga)
+
+## 60 pin superseal
+
+https://www.te.com/usa-en/product-6437288-3.html
+
+Motec Haltech DTAfast
+
+## 64 pin
+http://www.te.com/catalog/pn/en/176122-6
+
+http://www.te.com/usa-en/product-4-174518-7.html
+
+-1, -6 and -7 are color options
+
+![64 pin connector](Hardware/connectors/64_pin.png)
+
+http://rusefi.com/forum/viewtopic.php?f=4&t=507
+
+Mating plugs:
+16p http://www.te.com/catalog/pn/en/175109-6 
+
+16p  http://www.te.com/usa-en/product-174514-6.html
+
+22p http://www.te.com/catalog/pn/en/175110-6
+
+22p  http://www.te.com/usa-en/product-174515-6.html
+
+26p http://www.te.com/catalog/pn/en/175111-6
+
+26p http://www.te.com/usa-en/product-174516-6.html
+
+http://www.te.com/usa-en/product-174515-6.html
+
+terminal http://www.te.com/usa-en/product-173634-1.html
+
+terminal 173681
+
+![Grey connectors](Hardware/connectors/64_pin_connectors_grey.png)
+![Green connectors](Hardware/connectors/64_pin_connectors_green.png)
+
+See also http://rusefi.com/wiki/index.php?title=Hardware:OEM_connectors#48_pin
+
+For sale @ http://www.ebay.com/usr/rusefi
+
+## 4 row 64 pin
+
+Used on 5SF, Bosch 7.3H4, 7.3.1
+
+Mating harness connector 1-284272-5
+
+284331-1 64+64 header
+
+## 68 pin
+https://rusefi.com/forum/viewtopic.php?f=4&t=1303
+
+http://www.te.com/catalog/pn/en/963356-1
+
+![68 pin connector](Hardware/connectors/68_pin.png)
+
+http://www.te.com/catalog/pn/en/966595-1
+
+VW Jetta, Passat
+
+See http://faculty.ccp.edu/faculty/dreed/Campingart/jettatech/techset/index.htm
+
+## 68 pin center lock
+
+https://www.te.com/usa-en/product-174836-5.html
+
+## 72 pin
+
+http://www.te.com/usa-en/product-353830-5.html
+
+http://www.te.com/catalog/pn/en/1123038-2
+
+![72 pin connector](Hardware/connectors/72_pin.png)
+
+Oem ECU Miata 2001 - 2005
+http://rusefi.com/wiki/index.php?title=Vehicle:Mazda_Miata_2001
+
+pins 316836
+
+## 76 pin
+
+http://www.te.com/usa-en/product-3-178780-6.html
+178780-6 AMP maybe also 174915-6
+
+Vehicle:Subaru SVX 1995
+
+Vehicle:Subaru Impreza 1991-1996
+
+26 pins (10 hi-current + 16 low-current) 174516-6
+
+16 pins (all low current) 174514-6
+
+12 pins (all low current) 174913-1
+
+22 pins (6 hi-current + 16 low-current) 174515-6
+
+And terminals 173716-1 or 173716-2 and 173630-1 or 173630-2 
+
+![76 Pin Connector](Hardware/connectors/76_render.png)
+
+## 76 pin center lock
+
+https://www.te.com/usa-en/product-5-174385-5.html
+
+Nissan
+
+## 80 pin
+
+http://www.te.com/catalog/pn/en/8-1393476-0
+
+![80 Pin Connector](Hardware/connectors/80_render.png)
+
+Audi
+VW Jetta Golf VR6 Turbo
+
+1997 1998 Audi 4D0 907 551 A
+
+## 81 pin
+
+unknown part number used by Chinese vehicles, google for DJ7811-1-3.5-10
+
+https://rusefi.com/forum/viewtopic.php?f=4&t=1501
+
+## 88 pin
+http://www.te.com/catalog/pn/en/185785-1
+
+![88 Pin Connector in ECU](Hardware/connectors/88_ecu.png)
+
+98-01 KIA SEPHIA
+
+## 100 pin
+
+34-22-16-28 pins
+
+Toyota 1MZ-FE 3RZ-FE 5VZ
+1-5178203-6
+
+1-178203-6
+
+## 104 pin
+
+https://www.te.com/usa-en/product-179686-6.html
+
+Honda Accord 96-2002
+
+
+## 120 pin
+
+http://www.te.com/usa-en/product-1-178405-6.html
+
+Toyota Supra ECU connector 120 pin
+
+JZ
+
+## 121 pin
+
+http://www.te.com/catalog/pn/en/1241434-1
+
+http://www.te.com/catalog/pn/en/368255-2
+
+
+https://github.com/rusefi/rusefi/tree/master/hardware/368255-2-connector
+
+
+https://www.te.com/global-en/product-1473244-1.html
+
+https://www.te.com/global-en/product-1473252-1.html
+
+![121 Pin Connector](Hardware/connectors/368255_render.png)
+
+http://rusefi.com/forum/viewtopic.php?t=208
+
+Currently used by Nissan, Hyundai and Kia. Also Audi, VW and Mini Cooper
+
+2005 Altima 2.5
+
+2003 VW Passat
+
+http://rusefi.com/wiki/index.php?title=Hardware:OEM_121_pin_connectors
+
+## 122 pin
+
+![122 Pin Connector](Hardware/connectors/122_render.png)
+
+http://www.te.com/catalog/pn/en/8-5353015-1
+
+
+maybe the most common Aristo 2JZ ECU connector?
+1999 TOYOTA CAMRY 3.0L V6
+
+## 134 pin
+
+https://www.te.com/usa-en/product-7-967288-1.html
+
+Also known as 965497-1
+
+9+24+52+40+9
+
+bmw e38 e46 e65 e66
+
+02-03 Hyundai Santa
+
+2002-2005 Land Rover
+
+## 135 pin
+http://www.te.com/catalog/pn/en/1-1376430-0
+
+![135 Pin Connector](Hardware/connectors/135_render.png)
+
+Honda
+2003-2008 corolla/matrix/vibe
+
+harness side connectors:
+
+E 3 Engine Control Module Toyota 90980-12144
+
+E 4 Engine Control Module Toyota 90980-12145
+
+E 5 Engine Control Module Toyota 90980-12529
+
+E 6 Engine Control Module Toyota 90980-12525
+
+
+## 145 pin
+
+Mercedes 145 pin
+
+M111
+
+8+4+40+24+48+21
+
+part number?
+
+individual plugs 1685450828 2205459428
+
+## 152 pin
+
+Chrysler NGC ECU connector
+
+38 pin plugs:
+
+http://www.te.com/catalog/pn/en/9-1326726-8
+
+http://www.te.com/catalog/pn/en/9-1326727-8
+
+http://www.te.com/catalog/pn/en/9-1326728-8
+
+http://www.te.com/catalog/pn/en/9-1326729-8
+
+## 154 pin
+http://www.te.com/catalog/pn/en/284617-1
+
+http://www.te.com/catalog/pn/en/936524-2
+
+http://www.te.com/catalog/pn/en/936762-2
+
+https://www.te.com/global-en/product-936762-2.html
+
+![154 Pin Connector](Hardware/connectors/154_render.png)
+
+https://github.com/rusefi/rusefi/tree/master/hardware/284617-1-connector
+
+http://rusefi.com/forum/viewtopic.php?f=4&t=582
+
+## 200 pin
+http://www.te.com/catalog/pn/en/6473649-1
+
+![200 Pin Connector](Hardware/connectors/200_render.png)
+
+Toyota
+
+## Random links
+http://www.autosoftsys.com/supra/ecuext/
+
+https://speeduino.com/wiki/index.php/ECU_Connectors

MAX232.md

@@ -0,0 +1,7 @@
+MAX232 chip - dual 232 driver - could be used to stimulate VR sensing circuits
+
+![MAX232 Pinout](Images/max232_pinout.png)
+
+![MAX232 Application Information](Images/max232_appinfo.png)
+
+![MAX232 on a Breadboard](Images/max232_breadboard.png)

Power-Supply-Repair.md

@@ -0,0 +1,13 @@
+## rusEfi power supply troubleshooting guide
+
+http://www.ti.com/product/lm2596
+
+![Regulator Pinout](Images/regulator_pinout.png)
+
+## Scenario: 12v on regulator output
+
+With +12 applied, I measure +12 on lm2596 pin #2. With everything disconnected, I can see that #2 is not shortened to #1 (input)
+
+I also measure zero on the feedback pin and zero on the +5 output.
+
+Solution: make sure that regulator output pin is soldered (should show continuity with one of the inductors), make sure that feedback pin is solder (should show continuity with one of the inductors)

STM32F4Discovery-Repair.md

@@ -0,0 +1,140 @@
+See also http://rusefi.com/wiki/index.php?title=Hardware:Troubleshooting
+
+## Summary
+
+So you think you broke your discovery, good news, we have some tips for diagnostics and some suggestions for solutions. Fear not there is likely some good news below. For this diagnostics, we will assume you have removed the discovery from what ever circuit it was connected to and it is only being connected via "CN1" USB jack on SWD side of the board. The board should be something like the below picture. 
+
+![Discovery with USB JP1 Installed](Images/Discovery_USB_JP1-installed.jpg)
+
+## Diagnostics steps
+
+### Step 1 Check the power supply and programming chip
+#### Setup the Discovery like this
+* With USB not connected, remove Idd jumper JP1.
+* Plug in to USB power,
+
+#### Description of what is being check
+This prevents the 3V from making it to the target ST chip. This will isolate the part of the board you may have damaged. It will likely remove stray loads and will allow you to test if the power supply and SWD programming chip is functional. 
+
+#### Check(s) to determine what solution to follow.
+* Does the red LD2 "PWR" go bright RED? -- If so your power supply is probably in good order. Go to solution **Step 2**. If the LED is dim, proceed to the next line.
+* Is LD1 "COM" solid red and LD2 "PWR" dim? -- If so this is good, it means you are getting 5V via USB and the programmer chip is probably functional. If it is red, proceed to **Solution 1 Broken D3** else proceed to the next line.
+* Is LD1 "COM" green? -- If so this means you have 3V and ??? (I don't know when it will be green). If it's green or blinks green when communicating with it, this means you have 3V and your LD2 "PWR" light is broken. Proceed to **Solution 3 Broken LD1** else proceed to the next line.
+* Is LD1 "COM" blinking red? -- If so this could be and could be indicating the processor is active and doing stuff. TBD inquire in the forums for help. 
+* Is LD1 dim -- TBD ask in the forums for help.
+* Are all LED's off? -- If so this likely means there was a 5V short to GND and D1 has broken. To really check, with a multi-meter measure ![DC Symbol](DC-symbol.gif) DC voltage referenced to GND like at JP2 or JP3. Measure the voltage at both sides of D1. If you measure 5V at one side and less than 100mV on the other side, proceed to **Solution 2 Broken D1** If you measure below 100mV on both sides, 5V is not making it to this board, check your USB is providing 5V. 
+
+
+### Step 2 Check the target ST chip
+#### Setup the Discovery like this
+TBD
+
+#### Description of what is being check
+TBD
+
+#### Check(s) to determine what solution to follow.
+TBD
+
+reference forum suggestion for repair found here http://rusefi.com/forum/viewtopic.php?f=4&t=653&start=16
+
+## Solutions
+### Solution 1 Broken D3
+#### Fix 1
+You may notice that D1, D2, D3 are the same. You probably don't use D2, as R2 is not populated by default. You can probably safely re-purpose that diode. If you have a second broken board, you can probably scavenge a diode from another dead board. If replace the diode, before you power it up, carefully check that the line on the diode looks like it does in the picture. If it's installed backwards, the board will not turn on. It will act like the diode is broken. Once this repair has been made, start the diagnostics process over. 
+
+![D3 Orientation](Images/D3_orientation.jpg)
+
+#### Fix 2
+Easiest solution is to get a new D3 which can be found [http://www.digikey.com/product-detail/en/BAT60JFILM/497-3707-6-ND/1848703?WT.z_cid=ref_octopart_dkc_buynow&site=us here at digikey] or [http://octopart.com/partsearch#!?q=BAT60JFILM%0D%0A here at octopart] If you replace the diode, before you power it up, carefully check that the line on the diode looks like it does in the picture. If it's installed backwards, the board will not turn on. It will act like the diode is broken. Once this repair has been made, start the diagnostics process over.  
+
+![D3 Orientation](Images/D3_orientation.jpg)
+
+#### Fix 3
+Replace with some other diode you have kicking around int the junk box. Once this repair has been made, start the diagnostics process over.
+
+#### Fix 4
+You can remove the diode and install a little jumper wire. However be careful as a short to GND now could damage your regulator, and it's much harder to replace the regulator. Once this repair has been made, start the diagnostics process over.
+
+### Solution 2 Broken D1
+#### Fix 1
+See "Solution 1 Broken D3" but change the D1 diode instead. Once this repair has been made, start the diagnostics process over.
+
+![D3 Orientation](Images/D3_orientation.jpg)
+
+### Solution 2 Broken D1
+#### Fix 1
+Replace the LED or ignore it. This is only an indicator that you have 3V. 
+
+## general information
+
+![STM42F4 Discovery](Images/2014-08-21T15-20-24.645Z-stm32f4_discovery.jpg)
+
+![STM42F4 Discovery Layout](Images/layout.png
+
+[stm32f4discovery home page](http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419)
+
+[BOM archive](http://www.st.com/st-web-ui/static/active/en/resource/technical/document/bill_of_materials/stm32f4discovery_bom.zip)
+
+https://rusefi.com/wiki/index.php?title=File:Stm32f4discovery_schematics.pdf
+
+## Normal measurements
+Here are several measurements to function as a point of reference. These were taken with a known good board.
+
+With the USB powering the board via CN1 and JP1 removed, 
+* Voltage referenced to GND is 
+Voltage measurements
+||Away from audio jack|closer to audio jack
+|D1|4.76V|5.08V
+|D3|3.298V|2.968V
+|JP1|2.968V|.3mV
+
+With no USB and no other connections to the discovery, 
+* the measured ohms (auto scale) to GND with JP1 removed, The SWD side of JP1 measured at 7.34k ohms, and the audio jack side of JP 1 measured at 4.98k ohms.
+
+## common parts
+
+D1, D2, D3: BAT60JFILM
+
+U1: LD3985M33R
+
+U3: LD3985M25R
+
+## Scenario: Normal operation
+
+![Normal](Images/normal.png)
+
+You plug discovery into a powered mini USB cable and both LD1 and LD2 are bright red.
+
+## Scenario: Full darkness
+
+You plug discovery into a powered mini USB cable and discovery is totally dark
+
+## Scenario: A drop of life
+
+![Weak](Images/weak.png)
+
+You plug discovery into a powered mini USB cable and there is bit of light on LD2 but nothing on LD1.
+
+
+## checks
+
+### Check #1: D1
+With mini USB supplying power both sides of D1 should show about +5v. If not D1 might be at fault.
+
+![D1 Diode schematic](Images/D1_schematic.png)
+
+### Check #2: U1
+
+With mini USB supplying power bottom-right pin on U1 should show ~3v. If it's below 2v, U1 might be faulty.
+
+![Regulator schematic](Images/regulator_schematic.png)
+
+
+LD3985M33R
+
+![Regulator pinout](Images/regulator_pinout.png)
+
+On the discovery board the chip is upside-down.
+
+## stats
+Repaired by D1 replacement: 1

Servo-Motor.md

@@ -0,0 +1,5 @@
+
+SpringRC SM-S4303R Continuous Rotation Servo https://www.pololu.com/product/1248
+
+
+See also https://rusefi.com/forum/viewtopic.php?f=4&t=775 

Shock-Dyno.md

@@ -0,0 +1,13 @@
+http://www.hotrod.com/articles/82884-buildling-shock-dyno/
+
+http://honda-tech.com/road-racing-autocross-time-attack-19/diy-shock-dyno-2325055/
+
+Linear Velocity Transducer
+
+"sensotec load cell that I got off ebay for somewhere around $40-50. Rated up to 500 lbs"
+
+https://www.youtube.com/watch?v=SV0FXGfSN38 "3 or 4hp"
+
+https://www.youtube.com/watch?v=2L_S78RpUcU
+
+https://www.eng-tips.com/viewthread.cfm?qid=357653 "scotch-yoke drive" 

Stepper-Motor.md

@@ -0,0 +1,17 @@
+http://www.pololu.com/product/1182
+
+http://www.pololu.com/file/download/a4988_DMOS_microstepping_driver_with_translator.pdf?file_id=0J450
+
+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
+
+We do not have our own add-on board for a4988, we use ones from eBay like "stepper motor driver A4988 with Heat sinks"
+
+![Stepper Motor Driver](Images/stepper_motor_driver.jpg)
+
+http://rusefi.com/forum/viewtopic.php?f=5&t=767
+
+pinout: http://rusefi.com/forum/viewtopic.php?f=5&t=767&start=30#p17671
+
+See http://rusefi.com/forum/viewtopic.php?f=4&t=1161

Temperature-Sensing.md

@@ -0,0 +1,10 @@
+MLX90621
+
+
+http://forum.arduino.cc/index.php?topic=126244.0
+
+http://www.melexis.com/Asset/Datasheet-IR-thermometer-16X4-sensor-array-MLX90620-DownloadLink-6099.aspx
+
+http://www.melexis.com/Assets/Transition-from-MLX90620-to-MLX90621-6446.aspx
+
+![MLX90621  Pinout](Images/MLX90621_pinout.png)

Troubleshooting.md

@@ -0,0 +1,49 @@
+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.
+
+## Does you brain board work?
+Remove the green brain board from the ECU and remove all cables. Power brain board with mini-USB - just the top mini-USB, no other cables. 
+
+![Only Mini USB](Images/Only_mini_usb.png)
+
+Download latest http://rusefi.com/build_server/rusefi_bundle.zip
+Run rusefi_console.exe hit Erase, then hit Program
+
+![Reflash](Images/Reflash.png)
+
+Expected result: blue LED is constantly flashing. Once your blue LED is constantly flashing, connect micro-USB cable while the green boards is still not connected to anything. The blue LED should start blinking slower. The change in blue LED blinking confirms that your brain board is relatively OK.
+
+## Does you 5v power supply work?
+
+With brain board still removed, apply 12 volts to the power input. Check the 5 volts test pad for 5 voltage with a multimeter.
+
+Expected result: expecting +5 volts on the 5 volt test pad.
+
+## 5 volt regulator tests
+
+1.0 there should be no continuity between pads #2 and #3, #2 and #5, #3 and #4, #4 and #5
+
+1.1 pads #3 and #5 should be both connected to GND
+
+1.2 pads #2 and #4 should have continuity between them. L1001 inductor on F0.4 is the one connecting those.
+
+1.3 with +12v applied pad #1 should read close to +12v
+
+## 5 volts possible problems
+
+2.1 sometimes 5v regulators leads are not aligned and some would be not touching the PCB
+
+2.2 we've seen shorted tantalum 220µF capactors
+
+## Sensor wiring
+
+Invalid sensor readings could be due to faulty wiring or broken configuration. `analoginfo` is the first step in troubleshooting these: with a multimeter, measure voltage on the sensor signal wire while everything is plugged, powered and on (please be careful - everything is on, poking your probe into the wrong spot is the easiest way to burn your board)
+
+What you see on the multimeter should match the 'input' value in the corresponding line of `analoginfo` output.
+
+![Analog Info](Images/Analoginfo.png)
+
+## CLT and IAT sensors
+
+See Software Temperature Sensors