speeduino
/
wiki.js
mirror of https://github.com/speeduino/wiki.js.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/speeduino/wiki.js

This commit is contained in:
Josh Stewart 2020-01-19 09:05:32 +11:00
parent 9dcb49e9a0 2901b656af
commit f406eef979
12 changed files with 142 additions and 112 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
boards/V03.md
View File

@ -2,17 +2,16 @@
title: V0.3 Board
description: Usage and details of the v0.3 series of boards
published: true
date: 2020-01-16T11:53:24.022Z
date: 2020-01-18T12:36:49.252Z
tags:
---
Overview
--------
# V0.3 Board
## Overview
The v0.3 board was the first widely available Speeduino shield and is suitable for many typical 1-4 cylinder injection and ignition applications (Excluding direct injected engines). It uses screw terminals for all connections in order to make test wiring simple and quick for prototyping.
Board Features
--------------
## Board Features
The v0.3 boards includes the following features:
@ -102,11 +101,11 @@ For users having difficulty obtaining the SP721 used in some versions, see info
Depending on the type of crank and cam sensors you have, there are a number of jumpers that will need to be set. The jumpers that need setting are:
- JP1 - This sets whether the Ignition outputs are 12v or 5v. Note that even if you set this to 12v you should \*\*NOT\*\* connect these directly to a high current coil. These outputs should only ever go to a logic level coil or an igniter
- JP2 - Whether or not the RPM1 (Crank) input should be routed via the (Optional) VR conditioner. This should be set to VR when using either a VR sensor or a hall sensor that switches between 0v-12v
- JP3 - Same as JP2, but for the RPM2 (Cam) input
- JP4 - 10k pullup resistor for RPM1 input. Should be jumpered ('On') when a sensor is used that switches between ground and floating (Which is most hall effect sensors)
- JP5 - Same as JP4, but for the RPM2 (Cam) input
- JP1 - This sets whether the Ignition outputs are 12v or 5v. Note that even if you set this to 12v you should \*\*NOT\*\* connect these directly to a high current coil. These outputs should only ever go to a logic level coil or an igniter
- JP2 - Whether or not the RPM1 (Crank) input should be routed via the (Optional) VR conditioner. This should be set to VR when using either a VR sensor or a hall sensor that switches between 0v-12v
- JP3 - Same as JP2, but for the RPM2 (Cam) input
- JP4 - 10k pullup resistor for RPM1 input. Should be jumpered ('On') when a sensor is used that switches between ground and floating (Which is most hall effect sensors)
- JP5 - Same as JP4, but for the RPM2 (Cam) input
To make this simpler, the most common sensor types and their required configurations are below:
@ -118,8 +117,7 @@ To make this simpler, the most common sensor types and their required configurat
| Hall sensor | Floating Hall sensor | Hall | Hall | On | On |
| VR Sensor | Floating Hall sensor | VR | Hall | Off | On |
Board revisions
---------------
## Board revisions
| Version | Changes | BOM |
|---------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|

59
boards/V04.md
View File

@ -1,27 +1,26 @@
---
title: V04
title: V04 Board
description:
published: true
date: 2020-01-16T11:52:16.617Z
tags:
date: 2020-01-18T12:35:34.427Z
tags: boards, hardware, v0.4
---
Overview
--------
# V0.4 Board
## Overview
The v0.4 board is a testing board that was developed with the goals of reproducing the existing v0.3 boards capabilities, but with the following improvements:
- Lower cost (Primarily due to reduced size, but also some component changes)
- More compatible with off the shelf cases/enclosures
- Stepper-style IAC driver option
- Has a single 40 pin connector for all IO (Excluding 12v power)
- Lower cost (Primarily due to reduced size, but also some component changes)
- More compatible with off the shelf cases/enclosures
- Stepper-style IAC driver option
- Has a single 40 pin connector for all IO (Excluding 12v power)
> **Note:** The v0.4 is **NOT** intended as a replacement for the v0.3 line of boards! The 2 are designed with different goals in mind. The v0.4 is intended to be integrated more closely into existing wiring, with the aim being that interface boards can be used to easily connect through the IDC40 connector. Unless you understand the interface on the v0.4 board and believe it is the best option for your install, the v0.3 may well be a better option for you.
{.is-warning}
Board Features
--------------
## Board Features
The v0.4 boards includes the following features:
@ -35,8 +34,7 @@ The v0.4 boards includes the following features:
- 5 unpopulated/configured optional low-current spare outputs in "proto" section, including tachometer-out
- A single 40-pin IDC connector includes all pins required for the board with the exception of the 12v input
Physical Layout
---------------
## Physical Layout
Note that there are some differences between the various versions of the board, however the pinouts on the main IDC40 connector remain the same.
@ -86,29 +84,28 @@ Note that there are some differences between the various versions of the board,
| 39 | Injector 2 - Pin 2/2 |
| 40 | Injector 1 - Pin 2/2 |
Board Assembly
--------------
## Board Assembly
Assembly of a complete board is virtually identical to the v0.3 and remains relatively straightforward with all components being through hole and labelled on the board. Whilst it does not technically matter which order components are installed, the following is recommended for simplicity:
1. All resistors
2. All diodes (Including LEDS)
3. All capacitors
1. All resistors
2. All diodes (Including LEDS)
3. All capacitors
> Take note that C14 and C16 are polarised capacitors, meaning that they must be put in the correct way around. The capacitors should be marked with a + sign on one side. On the PCB, the positive side is indicated by a line on the capacitor symbol.
{.is-warning}
![capacitor_orientation.png](/img/hardware/capacitor_orientation.png){.align-center width=180}
1. All jumper headers (JP\*)
2. Arduino pins:
1. Suggested method: Break header pins into required lengths and insert into an Arduino Mega. Place the board over the top of the pins and solder in place
2. Note that not all the pins on the end double row need to be populated (Though there's no harm in doing so). The odd numbered pins (Eg D23, D25 .. DD53) do not need pins on them.
3. IDC 40 connector
4. IC sockets
5. All screw terminals
6. All MOSFETs
7. Power regulator
8. MAP sensor (If used)
4. All jumper headers (JP\*)
5. Arduino pins:
* **Suggested method**: Break header pins into required lengths and insert into an Arduino Mega. Place the board over the top of the pins and solder in place
* Note that not all the pins on the end double row need to be populated (Though there's no harm in doing so). The odd numbered pins (Eg D23, D25 .. DD53) do not need pins on them.
6. IDC 40 connector
7. IC sockets
8. All screw terminals
9. All MOSFETs
10. Power regulator
11. MAP sensor (If used)
> **NOTE:** ALL self assembly boards have the MAP sensor with the hole at the top. All assembled boards will typically have the hole on the bottom
{.is-warning}
@ -121,8 +118,7 @@ This video is for the v0.3 board, but it largely applies to v0.4 designs as well
<iframe width="560" height="315" src="https://www.youtube.com/embed/IjKlmIi_Dug" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</center>
Board Configuration
-------------------
## Board Configuration
The board can be configured in multiple ways depending on the hardware you use and way your setup is configured.
@ -175,8 +171,7 @@ To make this simpler, the most common sensor types and their required configurat
You can solder wires directly to the board or use IDC (Insulation Displacement Contact) connectors. The 40-pin IDC is the connector that was used on computer drive ribbon cables for years and old computer cables can be used. A heavier cable, called DuPont cable is recommend for long term use though. Later in the IDE/ATA interfaces life the speed was increased and this required a new fine 80-wire cable. These cables are **NOT** compatible. Some of the pins are connected together causing the magic blue smoke to be released.
Board revisions
---------------
## Board revisions
| Version | Changes | BOM |
|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|

6
decoders.md
View File

@ -2,7 +2,7 @@
title: Trigger patterns and decoders
description: List of supported crank/cam patterns
published: true
date: 2020-01-06T03:04:16.730Z
date: 2020-01-18T12:19:32.241Z
tags:
---
@ -19,8 +19,8 @@ The list below includes all those that are currently supported. They each lead t
| [GM 7X](/decoders/GM_7X "wikilink") | Untested | Multi tooth pulse |
| [4G63](/decoders/4G63 "wikilink") | Complete | As used on many 4 cylinder Mitsubishis and NA/NB Miata / MX-5. Also supports the 6 cylinder variation of this pattern (Eg 6g72) |
| [GM 24X](/decoders/GM_24X "wikilink") | Untested | Commonly used on GM LS1 V8 |
| [Jeep 2000](/decoders/Jeep_2000 "wikilink") | Complete | 6 Cylinder Jeep engines from '91 to 2000 |
| [Audi 135](/decoders/Audi_135 "wikilink") | Complete | Audi engines with 135 pulses-per-revolution |
| [Jeep 2000](/decoders/Jeep_2000 "wikilink") | Complete | 6 Cylinder Jeep engines from '91 to 2000 |
| [Harley EVO](/decoders/Harley_EVO "wikilink") | Complete | Harley EVO V-Twin engines up to '99 |
| [Honda D17](/decoders/Honda_D17 "wikilink") | Complete | Honda 4 cylinder D17 engine |
| [Miata 99](/decoders/Miata_99 "wikilink") | Complete | 1.8L Miata/MX5 from '99 to '00 |
| [Non-360](/decoders/Non-360 "wikilink") | Complete | A variation of the dual wheel decoder that can be used with tooth counts that do not divide evenly into 360 |

13
decoders/Harley_EVO.md Normal file
View File

@ -0,0 +1,13 @@
---
title: Harley EVO
description:
published: true
date: 2020-01-18T12:32:13.812Z
tags: decoder, trigger, Harley
---
## Harley Evo
The Harley EVO pattern is used on V-Twin engines from '86 through to '99.
This pattern will work on all injected EVO engines.

29
decoders/Honda_D17.md
View File

@ -1,28 +1,27 @@
<h2>
Overview
---
title: Honda D17
description:
published: true
date: 2020-01-18T11:58:20.186Z
tags: decoder, trigger
---
## Overview
</h2>
The Honda D17 decoder applies to the Honda engine family using a 12+1 crankshaft wheel. The 4+1 camshaft signal is not currently used with Speeduino. Without the cam signal, all standard fuel and ignition modes up to semi-sequential and wasted-spark are supported.
Applications
------------
### Applications
- TBA
Tuner Studio Configuration
--------------------------
### Tuner Studio Configuration
Timing adjustment
-----------------
### Timing adjustment
In most cases altering the trigger angle should not be required, however there is some small variation between the OEM versions of thIs trigger so some minor adjustment may be needed. Once you have the engine started, set a fixed ignition angle and check the timing with a timing light. If this is a few degrees out (&lt;20°), adjust the trigger angle here. If this is more than 20° out, there may be a larger problem.
Trigger Pattern
---------------
### Trigger Pattern
The crank trigger wheel consists of 12 evenly spaced teeth plus 1 additional 13th tooth which provides position information. The first tooth after this 13th one is considered Tooth \#1
<center>
<img src="https://raw.githubusercontent.com/speeduino/wiki/master/decoders/honda_D17.png" width="75%" />
</center>
![honda_D17.png](/img/decoders/honda_D17.png){.align-center width=75%}

30
decoders/Miata_99.md
View File

@ -1,32 +1,36 @@
Overview
--------
---
title: Miata 99-05
description:
published: true
date: 2020-01-18T12:03:50.588Z
tags: decoder, miata, trigger
---
## Miata 99-05
From MY99 onwards, Miatas moved to a new trigger patter that, whilst similar to that used on the 4g63, is more tolerant to noise and does not rely on both edges of a tooth being tracked. Crucially it also permits movement of the cam signal relative to the crank signal which is required due to the addition of variable cam timing in these engines. Sync can be determined in the same way regardless of if the variable cam is at it's maximum or minimum movement.
The trigger consists of a 4 tooth wheel located on the crankshaft and a 3 tooth wheel on the cam. The teeth on both wheels are unevenly spaced.
Applications
------------
### Applications
NB Miatas from 1999 until 2005.
Tuner Studio Configuration
--------------------------
### Tuner Studio Configuration
The trigger angle should not need changing once this pattern has been selected.
For most installs, Trigger filtering set to Off or Weak is sufficient.
In the `Starting/Idle` `->` `Cranking` `Settings` dialog, the `Fix` `cranking` `timing` `with` `trigger` option should be set to On
In the `Starting/Idle -> Cranking Settings` dialog ensure the following options are turned on:
Trigger Pattern
---------------
* 'Fix cranking timing with trigger'
* 'Use new ignition mode'
### Trigger Pattern
The crank wheel contains 4 teeth, separated by an alternating 70 and 110 degrees.
Sync is determined by counting the number of secondary (cam) pulses that occur between the primary (crank) pulses and can be confirmed at 2 points in the cycle. The first crank pulse after 2 cam pulses is tooth \#6 and the first crank pulse after a single cam pulse is tooth \#2. Tooth \#1 is located at 10 degrees BTDC and cannot be identified directly, only relative to teeth \#2 and \#6. As the camshaft timing is moved as part of the VVT, the secondary pulses remain within the same 'window' relative to the primary pulses. Sync can therefore before confirmed at all loads and speeds, no matter what VVT value is being currently used.
<center>
<img src="https://raw.githubusercontent.com/speeduino/wiki/master/decoders/miata9905.png" width="90%" />
</center>
![miata9905.png](/img/decoders/miata9905.png){.align-center width=90%}

53
decoders/Nissan_360.md
View File

@ -1,5 +1,12 @@
Overview
--------
---
title: Nissan_360
description:
published: true
date: 2020-01-18T12:15:19.364Z
tags:
---
## Nissan 360
The Nissan 360 CAS trigger is used across a large number of both 4 and 6 cylinder Nissan engines. See below for applications.
@ -7,38 +14,34 @@ The trigger is comprised of a wheel, running at cam speed, that has 360 windows
**NOTE:** There are multiple versions of the 4 cylinder CAS and not all are currently supported. Each known version is described below
1. Pattern 1 - Has a single unique inner window with all others being identical. Not currently supported
2. Pattern 2 - The unique slot sizes are in opposing pairs. This is partially supported.
3. Pattern 3 - Each inner window has a unique size. Typically 4,8,12,16 on 4 cylinder engines and 4,8,12,16,20,24 on 6 cylinders. This is supported.
1. Pattern 1 - Has a single unique inner window with all others being identical. Not currently supported
2. Pattern 2 - The unique slot sizes are in opposing pairs. This is partially supported.
3. Pattern 3 - Each inner window has a unique size. Typically 4, 8, 12, 16 on 4 cylinder engines and 4, 8, 12, 16, 20, 24 on 6 cylinders. This is supported.
Applications
------------
### Applications
- CA18 - Believed to have pattern 3
- SRxx Redtop - Believed to be pattern 3
- SRxx Blacktop (early) - Believed to be pattern 1
- SRxx Blacktop (notch) - Believed to be pattern 1
- FJ20 - Believed to have pattern 1
- RB30 - Believed to have pattern 1
- RB25/26 - Believed to all have pattern 3
- CA18 - Believed to have pattern 3
- SRxx Redtop - Believed to be pattern 3
- SRxx Blacktop (early) - Believed to be pattern 1
- SRxx Blacktop (notch) - Believed to be pattern 1
- FJ20 - Believed to have pattern 1
- RB30 - Believed to have pattern 1
- RB25/26 - Believed to all have pattern 3
Tuner Studio Configuration
--------------------------
### Tuner Studio Configuration
- Set both Trigger edge to Trailing
- Trigger Filter: off
- Re-sync every cycle: yes
- Set both Trigger edge to Trailing
- Trigger Filter: off
- Re-sync every cycle: yes
**NOTE**: If you are still not seeing any RPM signal or Sync try reversing the CAM and CRANK signals on the IDC40. These settings are confirmed for the 4-8-12-16 wheel.
![<File:SR20> Trigger Setting.png](SR20_Trigger_Setting.png "File:SR20 Trigger Setting.png")
![nissan_360.gif](/img/decoders/nissan_360_settings.png){.align-center width=400}
Timing adjustment
-----------------
### Timing adjustment
In most cases altering the trigger angle should not be required, however there is some small variation between the OEM versions of thIs trigger so some minor adjustment may be needed. Once you have the engine started, set a fixed ignition angle and check the timing with a timing light. If this is a few degrees out (&lt;20°), adjust the trigger angle here. If this is more than 20° out, there may be a larger problem.
Trigger Pattern
---------------
### Trigger Pattern
TBA
![nissan_360.gif](/img/decoders/nissan_360.gif){.align-center width=80%}

11
decoders/Non-360.md
View File

@ -1,4 +1,11 @@
Non-360 Decoder
---------------
---
title: Non-360
description:
published: true
date: 2020-01-18T12:04:54.939Z
tags: decoder, trigger
---
## Non-360 Decoder
This is a variation of the dual-wheel decoder that can be used with tooth counts that do not divide evenly into 360° This decoder system is usually unique to a particular brand or engine series, and therefore has previously been assigned a name to identify the type, such as the Audi 135 decoder. While this "uneven divisor" decoder can be used with a variety of tooth counts, not all tooth counts can be used with this system.

6
decoders/Subaru_36-2-2-2.md
View File

@ -2,17 +2,17 @@
title: Subaru 36-2-2-2
description:
published: true
date: 2020-01-16T11:48:52.741Z
date: 2020-01-18T12:16:32.362Z
tags:
---
## Overview
## Subaru 36-2-2-2
The 36-2-2-2 wheel is common on many 4 cylinder Subaru engines from approx. 2000 onwards. It utilises a crank trigger wheel containing a nominal 36 teeth, spaced 10 crank degrees apart, and 3 groups of 2 missing teeth. These missing tooth groupings allow for sync to be determined within at most 1/2 a crank turn.
Early wheels were VR triggered however after the switch to variable valve timing, Subaru switched to Hall sensors. Most configurations are paired with one or two 4-1 cam sensors, however these are not required for sync on Speeduino.
## Trigger Pattern
### Trigger Pattern
The 3 sets of 2 missing teeth are located such that one group is on its own and the other two are located adjacent to one another, with a single tooth in between. Sync can be determined by detecting the missing 2 teeth, then seeing if there is another set of missing teeth immediately after it.
Cylinder 1 TDC compression happens on the fourth tooth after the single gap. Speeduino watches for any missing tooth period, then waits to confirm whether it is followed by another. Sync can therefore be determined in this manner at 2 points in a single crank revolution.

18
make_pdf.sh
View File

@ -1,6 +1,14 @@
#!/bin/bash
#PANDOC_PATH=/home/pi/pandoc_src/bin/
PANDOC_PATH=/usr/bin/
for arg in "$@"
do
if [ "$arg" == "--local" ]
then
PANDOC_PATH=/home/pi/pandoc_src/bin/
fi
done
MAKEFILE=Makefile
WORKING_DIR=`pwd`
OUTPUT_FILENAME=${WORKING_DIR}'/offline/Speeduino_manual.pdf'
@ -13,11 +21,11 @@ IMAGES=${IMAGES_FOLDER}/*
COVER_IMAGE=${IMAGES_FOLDER}/Speeduino\ logo.png
TEMPLATE=offline/eisvogel.tex
TEMPLATE_OPTIONS='--listings --toc --toc-depth=2'
METADATA_ARG=--metadata-file=${METADATA}
ARGS="${TEMPLATE_OPTIONS} --template=${TEMPLATE}"
#ARGS="${TEMPLATE_OPTIONS}"
#PDF_ARGS="--pdf-engine=xelatex"
PDF_ARGS="-f markdown-markdown_in_html_blocks --pdf-engine=xelatex --metadata date=`date +%D`"
PDF_ARGS="-f markdown-markdown_in_html_blocks --pdf-engine=xelatex --metadata-file=${WORKING_DIR}/offline/metadata.yml"
METADATA_ARGS="--metadata date=`date +%D`"
#This contains all the fonts that might be needed
#sudo apt-get install texlive-fonts-extra
@ -35,8 +43,8 @@ do
done
echo ${PANDOC_PATH}pandoc ${ARGS} ${PDF_ARGS} -o ${OUTPUT_FILENAME} ${CHAPTERS}
${PANDOC_PATH}pandoc ${ARGS} ${PDF_ARGS} -o ${OUTPUT_FILENAME} ${CHAPTERS}
echo ${PANDOC_PATH}pandoc ${ARGS} ${PDF_ARGS} ${METADATA_ARGS} -o ${OUTPUT_FILENAME} ${CHAPTERS}
${PANDOC_PATH}pandoc ${ARGS} ${PDF_ARGS} ${METADATA_ARGS} -o ${OUTPUT_FILENAME} ${CHAPTERS}
#Copy the produced PDF back to the main directory
#cp ${OUTPUT_FILENAME} ${CUR_PATH}/offline

3
offline/metadata.yml Normal file
View File

@ -0,0 +1,3 @@
'''
title: Speeduino Manual
'''

4
offline/std_manual.md
View File

@ -2,7 +2,7 @@
title: std_manual
description:
published: true
date: 2020-01-17T01:03:46.600Z
date: 2020-01-18T12:20:10.417Z
tags:
---
@ -44,7 +44,7 @@ tags:
./decoders/4G63.md
./decoders/GM_24X.md
./decoders/Jeep_2000.md
./decoders/Audi_135.md
./decoders/Harley_EVO.md
./decoders/Honda_D17.md
./decoders/Miata_99.md
./decoders/Non-360.md