mirror of https://github.com/speeduino/wiki.js.git
docs: add all untracked content
This commit is contained in:
Josh Stewart
parent
b6d05b1118
commit
78ed39c89c
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
|
|
@ -2,9 +2,9 @@
|
|||
title: 3rd_party
|
||||
description:
|
||||
published: true
|
||||
date: 2021-08-24T12:56:11.236Z
|
||||
date: 2021-08-24T12:56:17.357Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:36:57.774Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Bluetooth
|
||||
description:
|
||||
published: true
|
||||
date: 2020-06-25T01:49:38.083Z
|
||||
date: 2020-06-25T01:49:44.047Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:36:59.175Z
|
||||
---
|
||||
|
||||
## Bluetooth Wireless Option
|
||||
|
|
|
|||
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: Board_overview
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:05:37.646Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:00.375Z
|
||||
---
|
||||
|
||||
**THIS PAGE IS A WORK IN PROGRESS. FURTHER DETAILS TO COME!**
|
||||
|
||||
There are currently 2 families of Speeduino boards available, the v0.3 line and the v0.4 line. These boards were designed to fit 2 different use cases and serve different purposes. The v0.4 line of boards is not necessarily newer/better than the v0.3, the 2 share largely the same features and capabilities. The differences are in how these are intended to be used.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,28 @@
|
|||
<!--
|
||||
title: CanBus Support
|
||||
description: Configuring Speeduino to use Canbus
|
||||
published: true
|
||||
date: 2020-12-15T21:24:32.239Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-12-05T23:01:05.753Z
|
||||
-->
|
||||
|
||||
<p>CanBus Support </p>
|
||||
<p>Speeduino is able to support Canbus in two ways.</p>
|
||||
<ol>
|
||||
<li>Use a mega2560 MCU with a coprocessor board </li>
|
||||
<li>Use a Teensy or STM32 (with internal can module) MCU.</li>
|
||||
</ol>
|
||||
<p>Enable Canbus Support</p>
|
||||
<p> </p>
|
||||
<p> </p>
|
||||
<p>Can OBD2 data output </p>
|
||||
<p>When used with an MCU that has an Internal canbus interface Speeduino firmware is able to output data using the OBD2 std </p>
|
||||
<p>Speeduino does not offer “readiness monitoring” or emission testing support and should not be used for such.</p>
|
||||
<p>Any code reader /app /software following OBD2 standard protocol is able to access the data described below.</p>
|
||||
<p> </p>
|
||||
<p>Interface setup </p>
|
||||
<p>The Interface supports 11bit addressing @500kbps data rate.</p>
|
||||
<p> </p>
|
||||
<p>PID supported</p>
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: CanBus Support
|
||||
description:
|
||||
published: true
|
||||
date: 2021-08-10T13:29:19.688Z
|
||||
date: 2021-08-10T13:29:25.945Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-12-15T21:58:51.731Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Configuration Index
|
||||
description: Listing of all dialog configuration help pages
|
||||
published: true
|
||||
date: 2021-11-11T07:06:33.517Z
|
||||
date: 2021-11-11T07:25:37.866Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:02.999Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Configuring TunerStudio project options
|
||||
description:
|
||||
published: true
|
||||
date: 2020-01-16T15:21:09.539Z
|
||||
tags: TunerStudio
|
||||
date: 2020-04-08T02:05:40.982Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:04.245Z
|
||||
---
|
||||
|
||||
# Configuring TunerStudio Project Properties
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Setting up TunerStudio
|
||||
description: How to create and connect to your ECU within TunerStudio
|
||||
published: true
|
||||
date: 2021-01-20T11:22:30.482Z
|
||||
date: 2021-01-20T11:22:36.487Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:05.419Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,11 @@
|
|||
---
|
||||
title: Creating_a_TunerStudio_Project
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:05:47.326Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:06.617Z
|
||||
---
|
||||
|
||||
1. REDIRECT [Configuring_TunerStudio](Configuring_TunerStudio "wikilink")
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Firmware_History
|
||||
description:
|
||||
published: true
|
||||
date: 2020-06-19T05:31:03.807Z
|
||||
date: 2020-06-19T05:31:10.277Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:11.016Z
|
||||
---
|
||||
|
||||
# Firmware releases now posted on GitHub
|
||||
|
|
|
|||
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: GPIO_for_Speeduino
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:06:04.454Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:12.223Z
|
||||
---
|
||||
|
||||
GPIO for Speeduino
|
||||
==================
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: GearControl_for_Speeduino
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:06:07.657Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:13.632Z
|
||||
---
|
||||
|
||||
Dxcontrol-Gears , A Gearbox Controller for Speeduino
|
||||
====================================================
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Getting Started
|
||||
description: Starting pages for each area of the manual
|
||||
published: true
|
||||
date: 2021-11-26T21:13:01.136Z
|
||||
date: 2021-11-26T21:13:11.304Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:14.971Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Hardware Requirements
|
||||
description:
|
||||
published: true
|
||||
date: 2021-07-30T04:48:59.090Z
|
||||
tags: hardware, wiring
|
||||
editor: markdown
|
||||
date: 2021-07-30T04:49:05.622Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:16.331Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Hardware_testing_page
|
||||
description:
|
||||
published: true
|
||||
date: 2021-11-26T21:21:16.024Z
|
||||
date: 2021-11-26T21:21:21.954Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:17.626Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Speeduino Firmware setup
|
||||
description: Setting up the Speeduino firmware on your board
|
||||
published: true
|
||||
date: 2021-01-27T11:59:11.000Z
|
||||
date: 2021-01-27T11:59:19.461Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:01.522Z
|
||||
---
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 370 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 490 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 474 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 382 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 930 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 101 KiB |
10
Overview.md
10
Overview.md
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: Overview
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:06:25.866Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:18.780Z
|
||||
---
|
||||
|
||||
So what's the go?
|
||||
-----------------
|
||||
|
||||
|
|
|
|||
10
README.md
10
README.md
|
|
@ -1,2 +1,12 @@
|
|||
---
|
||||
title: README
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:06:28.981Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T22:12:03.224Z
|
||||
---
|
||||
|
||||
# wiki.js
|
||||
Github backend for the Speeduino wiki.js instance
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: SD Card logging
|
||||
description:
|
||||
published: true
|
||||
date: 2022-03-20T22:48:10.068Z
|
||||
tags: sd, logging, dropbear
|
||||
editor: markdown
|
||||
date: 2022-03-20T22:48:20.396Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2021-10-12T05:18:25.120Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Secondary_Serial_IO_interface
|
||||
description:
|
||||
published: true
|
||||
date: 2021-07-09T13:15:13.573Z
|
||||
date: 2021-07-09T13:15:20.454Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:19.933Z
|
||||
---
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 164 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
File diff suppressed because one or more lines are too long
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
|
|
@ -2,9 +2,9 @@
|
|||
title: Trigger Wheel Generator
|
||||
description:
|
||||
published: true
|
||||
date: 2021-03-02T01:41:01.825Z
|
||||
date: 2021-03-02T01:41:07.766Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:21.158Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: Tuning_Index
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:06:38.734Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:22.290Z
|
||||
---
|
||||
|
||||
Tuning
|
||||
======
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 234 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 115 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 475 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 110 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 4.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.8 KiB |
|
|
@ -0,0 +1,651 @@
|
|||
---
|
||||
title: DxControl-GPIO
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:32:14.673Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:08.537Z
|
||||
---
|
||||
|
||||
dxControl-GPIO, A GPIO Controller for Speeduino
|
||||
===============================================
|
||||
|
||||
By Darren Siepka
|
||||
|
||||
### What is it?
|
||||
|
||||
dxControl-GPIO are a family of multipurpose general programmable input and output modules that can be used both in conjunction with the Speeduino engine ECU or standalone. The modules are programmed via Tunerstudio either via the serial port or over the integrated CanBus network(certain variants only)
|
||||
|
||||
The modules can use several different processor board types, including different arduino, teensy and stm32.
|
||||
|
||||
Io operations are programmed with logic, < ,>,= and bitwise AND . some variants offer 2 or even 3 connecting logic conditions.
|
||||
|
||||
### Versions
|
||||
|
||||
### GPIO MINI V0.001
|
||||
|
||||
This firmware supports up to 16 output channels , 16 input channels and 16 analog channels from local sources subject to MCU capability. MCU supported are currently Arduino Pro-Mini , Arduino Uno and Arduino Mega2560. The Output channels can be activated via one condition with logical operations of < , > and = Only onboard(local) io are supported in this version.
|
||||
|
||||
### GPIO MINI V0.002
|
||||
|
||||
This firmware offers the same features as V0.001 but with the ability to also access the output channel data values from a Speeduino ECU connected directly using the Speeduino Serial3 support.This firmware is currently only supported by Arduino Mega2560
|
||||
|
||||
### GPIO MINI V0.003
|
||||
|
||||
This firmware allows Speeduino to access the GPIO device's inputs(both digital and analog) to be displayed within TunerStudio or logged.Again in this version the GPIO device is still connected directly to the Speeduino via Serial3.This firmware is currently only supported by Arduino Mega2560
|
||||
|
||||
### GPIO MINI V3.001
|
||||
|
||||
This firmware has substantial improvements to the speed and stability of the Serial3 link with Speeduino. It also introduced the Display code module, which gives support for two displays of either I2C or SPI type. There are a few dispaly types pre configured and the list is growing. Current support
|
||||
|
||||
1. SSD1306 , Hardware I2C
|
||||
2. SSH1106 , Hardware I2C
|
||||
3. SSH1106 , Hardware SPI
|
||||
4. SSH1106 , Hardware SPI
|
||||
|
||||
The display section offer users the ability to easily integrate a custom display solution without worrying about timing or the serial protocols itself. All GPIO system realtime variables are available to use withon the display routine.
|
||||
|
||||
### GPIO STD V1.000
|
||||
|
||||
This firmware offer the first of a range of BCU or "body control unit" features.
|
||||
|
||||
Max number of input pins supported is 32 (subject to mcu limitations)
|
||||
|
||||
Max number of output pins supported is 32 (subject to mcu limitations)
|
||||
|
||||
Max number of analog inputs supported is 16 (subject to mcu limitations)
|
||||
|
||||
The firmware supports up to 2 canbus modules via spi(mcp2515) specified as CAN0 and CAN1
|
||||
|
||||
CAN0 is used for broadcast and other general use
|
||||
|
||||
CAN1 is for OBD2 use. The port offers a wide range of data to any STD code reader. In this firmware only realtime data is available.If the Speeduino ECU is connected to GPIO then all the supported realtime from The Speeduino will be available to the OBD2 reader.
|
||||
|
||||
Inputs can be linked to canbus addresses and have their status periodically broadcast at a selectable rate on CAN0.
|
||||
|
||||
Outputs can be linked to a Canbus address and have their status changed upon reciept of a valid value on CAN0.They can also broadcast on a selectable can address, at a selectable rate the status of the output including and error or fault detection that the output stage may support.
|
||||
|
||||
This Firmware also offers Generic 11bit broadcasting of any outchannel data.
|
||||
|
||||
Software installation
|
||||
---------------------
|
||||
|
||||
You can download the latest versions of GPIO [here](https://github.com/Autohome2/Speeduino-GPIO)
|
||||
|
||||
If you are installing one of the versions with CANBUS you will need to install the libraries to your Arduino IDE if you dont have a current version installed.The libraries are included in the download.
|
||||
|
||||
The libraries used are:
|
||||
|
||||
Canbus .This is for the mcp2515 can modules if used. This library is included in the libraries folder in the GPIO git download.
|
||||
|
||||
U8g2. This is the display library used.This library is included in the libraries folder in the GPIO git download.
|
||||
|
||||
Flexcan from Pawelsky( for Teensy onboard Can)[1](https://github.com/pawelsky/FlexCAN_Library)
|
||||
|
||||
The flexcan library is included in the installation of Teensyduino into the Arduino IDE[2](https://www.pjrc.com/teensy/td_download.html)
|
||||
|
||||
The Tunerstudio INI file and base tune can be found in the reference folder for the specific variant you wish to install in the download . NOTE it is very important to install the correct ini and base msq for the selected firmware. A demo dash fie for tunerstudio may also be provided.
|
||||
|
||||
Realtime Data Organisation
|
||||
--------------------------
|
||||
|
||||
Some versions of GPIO support the ability to access the realtime data from the GPIO I/O ports remotely via Either the Serial3 port or Canbus (see model versions). The data is stuctured as an offset address to the GPIO device real canID.
|
||||
|
||||
- 1 - 32 The Digital Inputs 1 through 32. These Send a value of 1023 if ON and 0 when OFF.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- 33 - 64 The Digital Outputs 1 through 32. These have an ON value of 1023 and an Off value of 0.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- 65 - 81 The Analog Inputs 0 through 15. These Send a value ranging from 0 to 1024.
|
||||
|
||||
example:
|
||||
|
||||
`if the GPIO real canID == 0x105 (261dec)`
|
||||
`to request analog 0 you would request data from 261dec + 65dec == 326dec == 0x146`
|
||||
|
||||
The data is located in bytes 0 and 1 of the 8 transmitted , 0 being lsb 1 being msb.
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
NOTE! The following information covers many versions of the GPIO family some Configurations,Features or Options may not be available in certain firmware code versions.
|
||||
|
||||
### Device Configuration
|
||||
|
||||
Device configuration can be found in the Tunerstudio Tab "Settings" then select "device configuration"
|
||||
|
||||
|
||||
|
||||
- **Device Real CanID** - The HEX 11bit Can address of the GPIO device
|
||||
- **Board Pin Layout** - The Mcu and board layout the GPIO is using
|
||||
|
||||
<img src="Board_pin_layout_2.jpg" title="Board_pin_layout_2.jpg" alt="Board_pin_layout_2.jpg" width="400" />
|
||||
|
||||
Select the appropriate mcu and board type for your GPIO unit.The firmware download has several board configurations pre setup in the code. Depending on which MCU you compile the firmware with will depend if that configuration is available to use.
|
||||
|
||||
- **Speeduino Connection Type**
|
||||
- **Not used** - This setting if the GPIO is a standalone device
|
||||
- **Via Serial3** - This setting if the GPIO connects directly using its serial connection to the secondary serial port on the Speeduino(usually Serial3).
|
||||
- **Via CanBus** - This setting if the GPIO is connected using its CanBus .This is pre-set at 11bit 250kbps.
|
||||
|
||||
<img src="Speeduino_connection_2.jpg" title="Speeduino_connection_2.jpg" alt="Speeduino_connection_2.jpg" width="400" />
|
||||
|
||||
- **Speeduino Realtime Base CanBus Address** - The HEX 11bit Can address of the Speeduino ECU
|
||||
- **GPIO OBD Address** - The HEX 11bit CanBus address of the GPIO OBD port
|
||||
|
||||
### Project Properties
|
||||
|
||||
In project Properties you can enable the Hardware Testpage and CAN_COMMANDS. Select "File", "Vehicle Projects", "Project Properties".
|
||||
|
||||
<img src="Project_properties_select.jpg" title="Project_properties_select.jpg" alt="Project_properties_select.jpg" width="800" />
|
||||
|
||||
Yuo can now enable/disable the appropriate options. The project will reload after you confirm the changes.
|
||||
|
||||
<img src="Project_properties_gpio.jpg" title="Project_properties_gpio.jpg" alt="Project_properties_gpio.jpg" width="800" />
|
||||
|
||||
### Programmable I/O and Output config
|
||||
|
||||
From the Programmable Outputs Tab you can select to configure the Universal outputs or the External IO
|
||||
|
||||
<img src="Prog_outputs1.jpg" title="Prog_outputs1.jpg" alt="Prog_outputs1.jpg" width="400" />
|
||||
|
||||
### Configuring Universal Outputs
|
||||
|
||||
This page enables the configuration of the Universal Outputs.
|
||||
|
||||
<img src="Universal_outputs1_16.jpg" title="Universal_outputs1_16.jpg" alt="Universal_outputs1_16.jpg" width="500" />
|
||||
|
||||
- *' Output port*' - This is the output port on the GPIO device . To use first select a port from the output port list ,configure the setting for that port and then click "burn" to burn the changes to your GPIO device(if online)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- *' Port settings*'
|
||||
- - *' Enabled*' - Enables this output port
|
||||
- *' Power on value*' - The active state of the port when the GPIO device starts up
|
||||
- *' Active value*' - The active output state(Active High or Active Low)
|
||||
|
||||
<!-- -->
|
||||
|
||||
- *' Active conditions*'
|
||||
- - *' Controller*' - This is fixed as the name of the GPIO device in use
|
||||
- *' Output channel*' - This is either the realtime output data from the local GPIO device or data from External devices[(see external data configuration)]((see_external_data_configuration) "wikilink")).
|
||||
- *' Logic option*' - The logical operation on the source value compared to the threshold , select <,>, =, or &
|
||||
- *' Threshold*' - The Trigger threshold for the output vs the source data.
|
||||
- ''' Hysteresis ''' - The threshold used with the threshold value
|
||||
- ''' Linking Logical condition ''' This is the logical operation(if applicable/available) between the first and second data source.
|
||||
- *' Output channel(second data source)*' - This is either the realtime output data from the local GPIO device or data from External devices[(see external data configuration)]((see_external_data_configuration) "wikilink")).
|
||||
- *' Logic option(second data source)*' - The logical operation on the source value compared to the threshold , select <,>, =, or &
|
||||
- *' Threshold(second data source)*' - The Trigger threshold for the output vs the source data.
|
||||
- ''' Hysteresis(second data source) ''' - The threshold used with the threshold value
|
||||
|
||||
To use the universal outputs
|
||||
|
||||
1. select the appropriate output port, be sure that the port is in use and not used by other functions it may clash operstion with.
|
||||
2. select "enabled"
|
||||
3. choose the power on state of the port
|
||||
4. choose if the port is to be active high or low(on or off)
|
||||
5. select the output channel the data is to be sourced from
|
||||
6. select the logic operation the data equation is to use.If you choose "&" then the threshold and hysteresis have slightly different purposes see example in next section.
|
||||
7. input the threshold value the data formula is to use
|
||||
8. input the hysteresis value . This value will stop the output switching on/off repeatedly if the data only changes a small amount .
|
||||
|
||||
`If logical operation was "&" then the threshold value is the value the data is logically ANDed to. and the result of that is compared to the value input in hysteresis.If the comparison of the ANDed value == the value in hysteresis then the output is active . This is useful for bit operations eg the digital inputs.`
|
||||
|
||||
Some controller firmware offer support for a second set of input and comparison , with and additional lnking logical operation between the two. This linking operation can be OR , AND and NOT(!).
|
||||
|
||||
1. OR , the output is active if EITHER or BOTH statement is true.
|
||||
2. AND , the output is active only if BOTH statement are true.
|
||||
3. NOT , the output is active if ONLY ONE of the statement are true.
|
||||
|
||||
The second output channel,logic operation ,threshold and hysteresis must be chosen for the second comparison input in a similar manner to the first.
|
||||
|
||||
### External IO Configuration
|
||||
|
||||
### Configuring external data input sources
|
||||
|
||||
This page configures the external input data sources.
|
||||
|
||||
<img src="Externalio_config_2.jpg" title="Externalio_config_2.jpg" alt="Externalio_config_2.jpg" width="800" />
|
||||
|
||||
- **Input Alias** - This is a user defined Alias name (up to 20 characters) for the input channel.This will appear on the gauge for the channel.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **External Input Channel Selection** - Enable/disable the external input channel
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Source Base CanID** - The 11bit HEX CanID of the device the data is to be sourced from.
|
||||
|
||||
EG: In the picture this is set to 0x200 which was the Speeduino Base Can address set in "device configuration"
|
||||
|
||||
- **Data from outchannel** - The outchannel number (from realtime outchannels) the data BEGINS at.
|
||||
|
||||
If the device is being accessed via CANBUS then this is the offset added to the base address +1 EG: in the picture it is 7 this would give a Can address of 0x208 or if a direct connection with Speeduino collect data from outchannel 7 (tpsADC)
|
||||
|
||||
- **no: of bytes** - The number of bytes the data has , select 1 or 2 (a 1 byte value has a range 0-254 , a 2 byte from 0 - 1024).
|
||||
|
||||
EG: In the picture it shows 1. This is due to outchannel 7(tpsADC) being only 1 byte long with a value of 0 - 254.
|
||||
|
||||
### Hardware Test Page
|
||||
|
||||
To see this option you must enable it in [Project Properties](#project_properties "wikilink")
|
||||
|
||||
Then a new Tab will appear on the main dash
|
||||
|
||||
<img src="Hardware_test_tab_gpio.jpg" title="Hardware_test_tab_gpio.jpg" alt="Hardware_test_tab_gpio.jpg" width="800" />
|
||||
|
||||
- Test Output Hardware
|
||||
- Test Input Hardware
|
||||
|
||||
#### Test Output Hardware
|
||||
|
||||
This will allow you to individually turn on/off output ports that are available . The availability depends on the board you have selected and pin configuration.
|
||||
|
||||
To start testing click on "Enable test mode" . The output ports that can be tested will then be unGreyed and can be clicked on/off. After testing either click "Stop test mode" or just close the window. Any outputs still activated will be switched off.
|
||||
|
||||
<img src="Hardware_output_test.jpg" title="Hardware_output_test.jpg" alt="Hardware_output_test.jpg" width="800" />
|
||||
|
||||
#### Test Input Hardware
|
||||
|
||||
This will allow you to monitor operation of the digital inputs or force the input ,overriding what GPIO sees.
|
||||
|
||||
The availability depends on the board you have selected and pin configuration.
|
||||
|
||||
Whilst test mode is NOT enabled you can observe the current state of an input pin on the "STATE" button for the appropriate input.This will be black when active(high) and grey when not(low).When test mode is enabled this feature does not work.
|
||||
|
||||
To start overide testing click on "Enable test mode" . The Input ports that can be tested will then be unGreyed and can be clicked on/off. After testing either click "Stop test mode" or just close the window. Any Inputs overriden will be returned to their current true input state.
|
||||
|
||||
<img src="Test_input_hardware.jpg" title="Test_input_hardware.jpg" alt="Test_input_hardware.jpg" width="800" />
|
||||
|
||||
### Creating new board layouts/pin configurations
|
||||
|
||||
New board types can be easily added to GPIO. It requires changes to be made to two files , "Utils.ino" and the Tunerstudio ini file.
|
||||
|
||||
#### Utils.ino
|
||||
|
||||
In the utils.ino file is the indiivual configurations for each board option EG:
|
||||
|
||||
` #if defined(CORE_AVR)`
|
||||
` case 1: // mega2560 demo V0.001`
|
||||
` pinOut[1] = 2; //`
|
||||
` pinOut[2] = 3; //`
|
||||
` pinOut[3] = 4; //`
|
||||
` pinOut[4] = 5; //`
|
||||
` pinOut[5] = 255; //`
|
||||
` pinOut[6] = 255; //`
|
||||
` pinOut[7] = 255; //`
|
||||
` pinOut[8] = 255; //`
|
||||
` pinOut[9] = 255; //`
|
||||
` pinOut[10] = 255; //`
|
||||
` pinOut[11] = 255; //`
|
||||
` pinOut[12] = 255; //`
|
||||
` pinOut[13] = 13; //`
|
||||
` pinOut[14] = 255; //`
|
||||
` pinOut[15] = 255; //`
|
||||
` pinOut[16] = 255; //`
|
||||
|
||||
` pinIn[1] = 6;`
|
||||
` pinIn[2] = 7;`
|
||||
` pinIn[3] = 8;`
|
||||
` pinIn[4] = 9;`
|
||||
` pinIn[5] = 255;`
|
||||
` pinIn[6] = 255;`
|
||||
` pinIn[7] = 255;`
|
||||
` pinIn[8] = 255;`
|
||||
` pinIn[9] = 255;`
|
||||
` pinIn[10] = 255;`
|
||||
` pinIn[11] = 255;`
|
||||
` pinIn[12] = 255;`
|
||||
` pinIn[13] = 255;`
|
||||
` pinIn[14] = 255;`
|
||||
` pinIn[15] = 255;`
|
||||
` pinIn[16] = 255;`
|
||||
` `
|
||||
` pinAin[1] = A0;`
|
||||
` pinAin[2] = A1;`
|
||||
` pinAin[3] = A2;`
|
||||
` pinAin[4] = A3;`
|
||||
` pinAin[5] = A4;`
|
||||
` pinAin[6] = A5;`
|
||||
` pinAin[7] = A6;`
|
||||
` pinAin[8] = A7;`
|
||||
` pinAin[9] = A8;`
|
||||
` pinAin[10] = A9;`
|
||||
` pinAin[11] = A10;`
|
||||
` pinAin[12] = A11;`
|
||||
` pinAin[13] = A12;`
|
||||
` pinAin[14] = A13;`
|
||||
` pinAin[15] = A14;`
|
||||
` pinAin[16] = A15;`
|
||||
` `
|
||||
` break;`
|
||||
` #endif `
|
||||
|
||||
This is the entry for position 1 the STD mega2560 board.
|
||||
|
||||
To add a new board create a new case with all the above pins. Ensure you change the MCU define if it is not a mega2560 to that of the MCU you are compiling with(only mega2560 is currently supported in). Any pins that are not used must be set to 255. EG: adding a new entry called"mynewboard" in position 6.
|
||||
|
||||
` #if defined(CORE_AVR)`
|
||||
` case 6: // mynewboard`
|
||||
` pinOut[1] = 2; //`
|
||||
` pinOut[2] = 3; //`
|
||||
` pinOut[3] = 255; //`
|
||||
` pinOut[4] = 5; //`
|
||||
` pinOut[5] = 255; //`
|
||||
` pinOut[6] = 255; //`
|
||||
` pinOut[7] = 255; //`
|
||||
` pinOut[8] = 255; //`
|
||||
` pinOut[9] = 255; //`
|
||||
` pinOut[10] = 4; //`
|
||||
` pinOut[11] = 255; //`
|
||||
` pinOut[12] = 255; //`
|
||||
` pinOut[13] = 13; //`
|
||||
` pinOut[14] = 255; //`
|
||||
` pinOut[15] = 255; //`
|
||||
` pinOut[16] = 255; //`
|
||||
|
||||
` pinIn[1] = 6;`
|
||||
` pinIn[2] = 7;`
|
||||
` pinIn[3] = 8;`
|
||||
` pinIn[4] = 255;`
|
||||
` pinIn[5] = 255;`
|
||||
` pinIn[6] = 255;`
|
||||
` pinIn[7] = 255;`
|
||||
` pinIn[8] = 255;`
|
||||
` pinIn[9] = 255;`
|
||||
` pinIn[10] = 9;`
|
||||
` pinIn[11] = 255;`
|
||||
` pinIn[12] = 255;`
|
||||
` pinIn[13] = 255;`
|
||||
` pinIn[14] = 255;`
|
||||
` pinIn[15] = 255;`
|
||||
` pinIn[16] = 255;`
|
||||
` `
|
||||
` pinAin[1] = A0;`
|
||||
` pinAin[2] = A1;`
|
||||
` pinAin[3] = A2;`
|
||||
` pinAin[4] = A11;`
|
||||
` pinAin[5] = A4;`
|
||||
` pinAin[6] = A7;`
|
||||
` pinAin[7] = A6;`
|
||||
` pinAin[8] = 255;`
|
||||
` pinAin[9] = A8;`
|
||||
` pinAin[10] = 255;`
|
||||
` pinAin[11] = A10;`
|
||||
` pinAin[12] = 255;`
|
||||
` pinAin[13] = 255;`
|
||||
` pinAin[14] = 255;`
|
||||
` pinAin[15] = A14;`
|
||||
` pinAin[16] = A15;`
|
||||
` `
|
||||
` break;`
|
||||
` #endif `
|
||||
|
||||
`Add that in in the appropriate space ie between 5 and 7 (in they exist or at the end of the options if not).`
|
||||
|
||||
Saving and rcomplie the file and upload to your GPIO. Ensure the position used matches that in the ini file mods see next.
|
||||
|
||||
#### The Tunerstudio ini
|
||||
|
||||
This is located in the "reference" folder in the firmware download. Do not use MS notepad to edit this file!! A good editor is Notepad++ a few software download. The line rquiring editing is line 140
|
||||
|
||||
`#define PIN_LAYOUT = "ProMini GPIO v0.002", "Mega2560 GPIO v0.003", "STM32 BluePill GPIO V0.003", "Speeduino v0.3", "Speeduino v0.4", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID" `
|
||||
|
||||
To add a new entry simply remove one of the "INVALID" and replace with your board name EG: the changed file adding a new board called "mynewboard"
|
||||
|
||||
`#define PIN_LAYOUT = "ProMini GPIO v0.002", "Mega2560 GPIO v0.003", "STM32 BluePill GPIO V0.003", "Speeduino v0.3", "Speeduino v0.4", "INVALID", "mynewboard", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID" `
|
||||
|
||||
This shows the new entry being a position 6(promini is position 0). The board config must be at position 6 in the utils.ino too. When you save the changed file and reload it into Tunerstudio your new board will appear as an option.
|
||||
|
||||
### Display Configuration
|
||||
|
||||
GPIO(firmware versions may vary level of support) supports up to Two independant screens. They can be connected via I2C or SPI.Each display can be of either type.The display support is configured before uploading the firmware via settings in the display.h file. In the display.h file you will see the following(typical extract from file , may vary)
|
||||
|
||||
#### Step1 activate the display and its type
|
||||
|
||||
if a display is not in use then comment out the line DISP1_ACTIVE for display 1 or DISP2_ACTIVE for display 2 If display1 is I2C set DISP1_ROUTE to 0 if it is connected to the hardware I2C port or enter the mux address if a TCA9548A I2C mux is in use. The same applies to display2 Uncomment the appropriate USE option according to your display model
|
||||
|
||||
//display module options . only choose one of the following defines for display selection , comment out the unused ones //set display 1 type
|
||||
|
||||
1. define DISP1_ACTIVE 1 // 1 if in use or comment out
|
||||
2. define DISP1_ROUTE 0 // direct i2c == 0 , remote == mux address
|
||||
3. define DISP1_USE_SSD1106_I2C
|
||||
|
||||
//\#define DISP1_USE_SSD1306_I2C //\#define DISP1_USE_SSD1106_SPI //\#define DISP1_USE_SSH1106_SPI
|
||||
|
||||
//set display 2 type //\#define DISP2_ACTIVE 1
|
||||
|
||||
1. define DISP2_ROUTE 0 // direct i2c == 0 , remote == mux address
|
||||
2. define DISP2_USE_SSD1106_I2C
|
||||
|
||||
//\#define DISP2_USE_SSD1306_I2C //\#define DISP2_USE_SSD1106_SPI //\#define DISP2_USE_SSH1106_SPI
|
||||
|
||||
#### Step 2 , set display size
|
||||
|
||||
This feature is not currently in use as only displays of 128x64 are supported
|
||||
|
||||
//set display size
|
||||
|
||||
1. define USE_128x64
|
||||
|
||||
//\#define USE_128x128
|
||||
|
||||
#### Step 3, set the port used by the display
|
||||
|
||||
Set The correct pins for your display(1 and/or 2) depending on where they are connected to. DO NOT USE PINS FOR THE DISPLAY THAT ARE CONFIGURED AS PORTS IN UTILS.ino FOR IO PURPOSES!
|
||||
|
||||
SPI NOTES: hardware spi on mega2560 mosi == 51, clk(sck) == 52 I2C NOTES: hardware i2c on the mega2560 sda == 20, scl == 21
|
||||
|
||||
//set pins for screens in spi mode //display 1
|
||||
|
||||
1. define DISPLAY1_CS 7 //pin to use for CS
|
||||
2. define DISPLAY1_DC 6 //pin to use for DC
|
||||
3. define DISPLAY1_RESET 8
|
||||
|
||||
//display 2
|
||||
|
||||
1. define DISPLAY2_CS 7 //pin to use for CS
|
||||
2. define DISPLAY2_DC 6 //pin to use for DC
|
||||
3. define DISPLAY2_RESET 8
|
||||
|
||||
#### Step 4 , add your display code
|
||||
|
||||
now in display.ino add your display code in the "driveDisplay()" function For display1 add the cide after the \#if defined DISP1_ACTIVE For display2 add the cide after the \#if defined DISP2_ACTIVE
|
||||
|
||||
HINT!: keep your display code as short as possible to prevent timing hangups, and DO NOT use delay or other blocking functions!
|
||||
|
||||
### Canbus Configuration
|
||||
|
||||
<img src="Canbus_broadcast_config.jpg" title="fig:Canbus_broadcast_config.jpg" alt="Canbus_broadcast_config.jpg" width="800" /> The CanBus Configuration menu tab options are only visible when CAN_COMMANDS are enabled in [Project Properties](#project_properties "wikilink").
|
||||
|
||||
#### CanBus Module Configuration
|
||||
|
||||
<img src="Canbus_broadcast_config_B.jpg" title="fig:Canbus_broadcast_config_B.jpg" alt="Canbus_broadcast_config_B.jpg" width="800" /> Here you enable the CAN0 and CAN1 Canbus modules. These modules are MCP2515 SPI modules connected to the hardware spi ports on the mcu.
|
||||
|
||||
#### Generic 11bit CanBus Broadcast
|
||||
|
||||
The 11bit CanBus Broadast feature offers the ability to periodically broadcast on a specified can address the values from any Outchannel on GPIO. This could include external data read from Speeduino for instance using the [Configuring external data sources](#Configuring_external_data_sources "wikilink") method. <img src="Canbus_broadcast_config_C.jpg" title="fig:Canbus_broadcast_config_C.jpg" alt="Canbus_broadcast_config_C.jpg" width="800" />
|
||||
|
||||
- **Name Alias** - This is a user defined Alias name (up to 20 characters) for the broadcast channel .
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **CAN broadcast channel on/off** - Enable/disable the broadcast channel
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Source OutChannel** - The OutChannel data source on GPIO.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Can Broadcast Adddress** - The 11bit HEX Can Address the OutChannel data will be broadcast as being assigned to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Broadcast Freq** - This is the Frequency the OutChannel data is broadcast at.
|
||||
|
||||
### Remote CanBus Triggers
|
||||
|
||||
The Remote Trigger menu tab options are only visible when CAN_COMMANDS are enabled in [Project Properties](#project_properties "wikilink").
|
||||
|
||||
Remote CanBus triggers come in four varietys , Digtial Input, Analog Input, Digital Output, PWM Output.
|
||||
|
||||
They are part of the BCU or BODY CONTROL UNIT functions introduced in the GPIO STD firmwares.
|
||||
|
||||
The Remote inputs attach a input port on GPIO to a canbus address. The current status of the input pin is broadcast on the assigned canbus address at the frequency chosen.
|
||||
|
||||
The Remote Outputs attach an output port on GPIO to a canbus address. The current status of the output port can be changed by sending a valid value to GPIO on that canbus address.
|
||||
|
||||
<img src="Digital_remote_canbus_output_config.jpg" title="Digital_remote_canbus_output_config.jpg" alt="Digital_remote_canbus_output_config.jpg" width="800" />
|
||||
|
||||
#### Digital Remote Input Triggers
|
||||
|
||||
<img src="remote_digital_input.jpg" title="remote_digital_input.jpg" alt="remote_digital_input.jpg" width="800" />
|
||||
|
||||
There are two pages of these configs , channels 0 -15 and 16-31. They have both the same appearance and functions so we will just refer to 0-15 page here.
|
||||
|
||||
- **Name Alias** - This is a user defined Alias name (up to 20 characters) for the Remote Input Trigger .
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **External In** - Enable/disable the remote input channel
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Can Address** - The 11bit HEX Can Address the remote Input is linked to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Input Port** - This is the physical Input port on GPIO the channel is linked to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Broadcast Freq** - This is the Frequency the status of the input pin port is broadcast at.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Available Input Ports** - This is a list of all Input ports on GPIO. If the port is active(enabled and assigned a pin in utils.ino) then it will be black , else it will be grey.
|
||||
|
||||
It is important to NEVER choose a greyed out port as an Input Port selection!
|
||||
|
||||
##### Use of Remote Digital input port
|
||||
|
||||
To use this feature
|
||||
|
||||
1. Enable the channel you wish to configure
|
||||
2. (optional) set a "alias" name to make remembering the data source easier.
|
||||
3. choose the Can Address you wish the data to use.
|
||||
4. select the input port you wish to broadcast the value of.
|
||||
5. select the frequency the broadcast will be made at , 4,5,10,15, and 20Hz
|
||||
|
||||
The broadcast will be made to the specified address at the frequency set with bit0 of Byte 0 (of the 8 can bytes) reflecting the port state.
|
||||
|
||||
#### Digital Remote Output Triggers
|
||||
|
||||
<img src="Remote_out_triggers.jpg" title="Remote_out_triggers.jpg" alt="Remote_out_triggers.jpg" width="800" />
|
||||
|
||||
There are two pages of these configs , channels 0 -15 and 16-31. They have both the same appearance and functions so we will just refer to 0-15 page here.
|
||||
|
||||
- **Name Alias** - This is a user defined Alias name (up to 20 characters) for the Remote Output Trigger .
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **External Out** - Enable/disable the remote output channel
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Can Address** - The 11bit HEX Can Address the remote output is linked to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Output Port** - This is the physical output port on GPIO the channel is linked to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Send Status?** - Enable/Disable the output status broadcast.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Status Can Address** - The 11bit HEX Can Address the remote output status is broadcasted on.If this option is not available then the data is broadcast on the same can address.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Status Broadcast Frequency** - choose the frequency that the status data is broadcast 4, 5, 10 ,15 and 20Hz.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Available Output Ports** - This is a list of all output ports on GPIO. If the port is active(enabled and assigned a pin in utils.ino) then it will be black , else it will be grey.
|
||||
|
||||
It is important to NEVER choose a greyed out port as an Output Port selection!
|
||||
|
||||
##### Use of remote outputs
|
||||
|
||||
To trigger an output GPIO must receive the following
|
||||
|
||||
1. Can Address matching as configured.
|
||||
2. In byte 0 (of the 8 can bytes) the on/off bit set or reset(bit 0).
|
||||
|
||||
##### Status broadcast
|
||||
|
||||
If the status broadcast option is chosen then the following information is periodically broadcast(according to the frequency setting)
|
||||
|
||||
` Function Bit`
|
||||
`REMOTE_OUT_OFF 0`
|
||||
`REMOTE_OUT_ON 1`
|
||||
`REMOTE_OUT_OPENCIRCUIT 2`
|
||||
`REMOTE_OUT_SHORTCIRCUIT 3`
|
||||
`REMOTE_OUT_THERMALOVERLOAD 4`
|
||||
`REMOTE_OUT_CURRENTOVERLOAD 5`
|
||||
`REMOTE_OUT_unused6 6`
|
||||
`REMOTE_OUT_unused7 7`
|
||||
|
||||
These bit values are sent in byte 1 (of the 8 can bytes).
|
||||
|
||||
#### Analog Remote Input Triggers
|
||||
|
||||
<img src="Remote_analog_input.jpg" title="Remote_analog_input.jpg" alt="Remote_analog_input.jpg" width="800" />
|
||||
|
||||
- **Name Alias** - This is a user defined Alias name (up to 20 characters) for the Remote Analog Input .
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Enable Ain** - Enable/disable the remote analog input channel
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Can Address** - The 11bit HEX Can Address the remote analog Input is linked to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Input Port** - This is the physical analog Input port on GPIO the channel is linked to.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Broadcast Freq** - This is the Frequency the status of the analog input pin port is broadcast at.
|
||||
|
||||
<!-- -->
|
||||
|
||||
- **Available Analog Input Ports** - This is a list of all Analog Input ports on GPIO. If the port is active(enabled and assigned a pin in utils.ino) then it will be black , else it will be grey.
|
||||
|
||||
It is important to NEVER choose a "greyed out" port as an Analog Input Port selection!
|
||||
|
||||
##### Use of Remote Analog input port
|
||||
|
||||
To use this feature
|
||||
|
||||
1. Enable the channel you wish to configure
|
||||
2. (optional) set a "alias" name to make remembering the data source easier.
|
||||
3. choose the Can Address you wish the data to use.
|
||||
4. select the Analog input port you wish to broadcast the value of.
|
||||
5. select the frequency the broadcast will be made at , 4,5,10,15, and 20Hz
|
||||
|
||||
The broadcast will be made to the specified address at the frequency set with the lsb to Byte 0 and the msb to byte 1 (of the 8 can bytes) reflecting the port state(0-1024).
|
||||
|
||||
#### PWM Remote Output Triggers
|
||||
|
||||
under development!
|
||||
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
title: DxControl-Gears
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:32:03.793Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:37:09.869Z
|
||||
---
|
||||
|
||||
dxControl-Gears , A Gearbox Controller for Speeduino
|
||||
====================================================
|
||||
|
||||
By Darren Siepka
|
||||
|
||||
### What is it ?
|
||||
|
||||
dxControl-Gears is a controller for electronically controlled Automatic gearboxes , designed to accompany Speeduino. It is a custom development of the dxControl-GPIO code .
|
||||
|
||||
It supports up to 32 output channels to drive solenoids and valve , 16 digital input channels ,8 analog input channels.
|
||||
|
||||
Future releases will have pwm input and output capability along with direct or Canbus connectivity to the Speeduino ECU.
|
||||
|
||||
### Gearbox Configurations Available
|
||||
|
||||
1. A340E
|
||||
|
||||
2. AODE (coming soon)
|
||||
|
||||
3. 5R55s (coming soon)
|
||||
|
||||
4. TBA... Yours?
|
||||
|
||||
#### The A340E
|
||||
|
||||
The A340E made by Aisin Warner can be found in numerous vehicles including mitsubishi and Lexus.
|
||||
|
||||
It has Two shift solenoids and electric convertor lockup.
|
||||
|
||||
The solenoid to gearselection pattern is
|
||||
|
||||
` Solenoid 1 Solenoid 2`
|
||||
` Gear 1 on off`
|
||||
` Gear 2 on on`
|
||||
` Gear 3 off on`
|
||||
` Gear 4 off off`
|
||||
|
||||
#### The AODE
|
||||
|
||||
#### The 5R55s
|
||||
|
||||
### Input Hardware Testing
|
||||
|
||||
### Output Hardware Testing
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: NO2C_for_Speeduino
|
||||
description:
|
||||
published: true
|
||||
date: 2021-11-17T11:47:57.731Z
|
||||
date: 2021-11-17T11:48:03.837Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:35.241Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: UA4C Seafox/Sea Wolf
|
||||
description:
|
||||
published: true
|
||||
date: 2021-11-17T11:47:14.513Z
|
||||
date: 2021-11-17T11:47:20.049Z
|
||||
tags:
|
||||
editor: ckeditor
|
||||
editor: undefined
|
||||
dateCreated: 2021-01-20T11:01:47.993Z
|
||||
-->
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
title: V02x_Assembly_Tips
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:23:52.880Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:38.998Z
|
||||
---
|
||||
|
||||
**The most current version of the bill of materials is kept on my GitHub here: [GitHub](https://github.com/turboedge/SpeedyBoards)**
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
I normally insert and then solder all the passive components at one time, BUT I would suggest soldering down the resistor networks before you bend a whole bunch of through hole leads (especially from the input capacitors) in front of their solder pads. It's difficult to get the tip in there otherwise. Speaking of the resistor networks. The orientation on them does not matter except for RN3 where is does matter. The dot on RN3 should align with the square pad and the little square around the square pad.
|
||||
|
||||
When soldering the stepper module pin sockets bend the first four pins over. This will help the board sit flat even though the Arduino DC jack will be right under it (Optional, I always forget).
|
||||
|
||||
If you choose to have the connector soldered directly to the PCB the tab for the locking latch should aim toward IC2, and do NOT use a socket under IC2, solder it directly to the board. If you use an IC socket it will be difficult to unlatch the connector.
|
||||
|
||||
When inserting the LEDs be sure to put the squared off side with the short lead into the square solder pad. Or it won't work. Also, if you want the resistors to sit flush like the ones in the picture (though that third one crept up a bit) the legs need to be folded over as close to the resistor body as possible.
|
||||
|
||||
For version v.0.2.2 a header was added to the NO2C to allow easier connection of a Bluetooth module. This causes a bit of an issue with the Arduino header pins. The pins required for the BTMod to function (TX0/RX0) are marked for use with the daughter-board. The DB has connections for a BTMod also, so they were routed to that, and if you ever got a DB you may want to connect the BTMod there since it is easier. If you don't have any plans to use the mostly unreleased DB with your NO2C you may want to add standard header pins in the two serial0 locations.
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: Dropbear
|
||||
description:
|
||||
published: true
|
||||
date: 2022-03-13T01:03:40.769Z
|
||||
date: 2022-03-13T01:03:47.721Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-12-24T00:42:27.964Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Miata/MX5 89-95 NA6 PNP
|
||||
description: Plug and Play board for the NA Miata/MX5 model years '89 through to early '95
|
||||
published: true
|
||||
date: 2021-01-31T04:02:46.210Z
|
||||
tags: boards
|
||||
editor: markdown
|
||||
date: 2021-01-31T04:02:56.074Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:34.029Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: V0.3 Board
|
||||
description: Usage and details of the v0.3 series of boards
|
||||
published: true
|
||||
date: 2021-08-11T06:21:18.942Z
|
||||
date: 2021-08-11T06:21:25.444Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:42.683Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,92 @@
|
|||
---
|
||||
title: V031
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T11:54:26.633Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:40.166Z
|
||||
---
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
The v0.3 board is the first widely available Speeduino shield and is suitable for many typical 1-4 cylinder injection and ignition applications (Excluding direct injected engines).
|
||||
|
||||
Board Features
|
||||
==============
|
||||
|
||||
The v0.3 boards includes the following features:
|
||||
|
||||
- 4 injector channels
|
||||
- 4 Ignition outputs
|
||||
- Fully protected input channels for CLT, IAT, TPS and O2
|
||||
- Optional VR conditioner mount on crank and cam inputs
|
||||
- MAP sensor mount location
|
||||
- 4 medium current spare outputs (Eg Fuel pump, thermo fan etc)
|
||||
- All I/O through screw terminals on the board
|
||||
- Optional EEPROM mount (Not currently in use, but expected for future potential support of Arduino Due)
|
||||
- OLED breakout header
|
||||
|
||||
Physical Layout
|
||||
===============
|
||||
|
||||
<img src="https://raw.githubusercontent.com/speeduino/wiki/master/v0_3_board_annotated.jpg" width="60%" />
|
||||
|
||||
Board Assembly
|
||||
==============
|
||||
|
||||
Assembly of a complete board is relatively straightforward with all components being through hole and labelled on the board. Whilst it does not matter which order components are installed, the following is recommended for simplicity:
|
||||
|
||||
1. All resistors
|
||||
2. All diodes (Including LEDS)
|
||||
3. All capacitors
|
||||
1. 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.
|
||||
|
||||
4. All jumper headers (JP\*)
|
||||
5. 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.
|
||||
|
||||
6. IC sockets
|
||||
7. MAP sensor (If used)
|
||||
8. All screw terminals
|
||||
9. All MOSFETs
|
||||
10. Power regulator
|
||||
|
||||
Board Configuration
|
||||
===================
|
||||
|
||||
The board can be configured in multiple ways depending on the hardware you use and way your setup is configured.
|
||||
|
||||
Optional Components
|
||||
-------------------
|
||||
|
||||
If using a VR crank sensor, the board will require the addition of a VR conditioner. The board has been designed to work with the dual VR conditioner from JBPerf (http://www.jbperf.com/dual_VR/index.html) which will plug directly in. Other VR conditioners will also likely work, but have not been tested.
|
||||
|
||||
Jumper Configs
|
||||
--------------
|
||||
|
||||
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
|
||||
|
||||
To make this simpler, the most common sensor types and their required configurations are below:
|
||||
|
||||
| Crank Sensor | Cam Sensor | JP2 | JP3 | JP4 | JP5 |
|
||||
|---------------------------|-----------------------|------|------|-----|-----|
|
||||
| Floating Hall sensor
|
||||
(Ground and floating) | - | Hall | Off | On | Off |
|
||||
| VR Sensor | - | VR | Off | Off | Off |
|
||||
| 0v-12v Hall Sensor
|
||||
(Requires VR Conditioner) | - | VR | Off | Off | Off |
|
||||
| Floating Hall sensor
|
||||
(Ground and floating) | Floating Hall sensor
|
||||
(Ground and floating) | Hall | Hall | On | On |
|
||||
| VR Sensor | Floating Hall sensor
|
||||
(Ground and floating) | VR | Hall | Off | On |
|
||||
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: V04 Board
|
||||
description:
|
||||
published: true
|
||||
date: 2021-10-12T16:22:15.412Z
|
||||
tags: boards, hardware, v0.4
|
||||
editor: markdown
|
||||
date: 2021-10-12T16:22:22.221Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:44.099Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: VR_Conditioners
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:07:30.498Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:45.530Z
|
||||
---
|
||||
|
||||
The following Signal Conditioner Boards are known to work with Speeduino, and plug into the VR conditioner Socket:
|
||||
|
||||
The JBPerf dual VR conditioner (http://forum.jbperf.com/viewtopic.php?f=6&t=1089)
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: VR_conditioner
|
||||
description:
|
||||
published: true
|
||||
date: 2021-07-16T08:02:10.464Z
|
||||
date: 2021-07-16T08:02:16.412Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:46.712Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Turbine Bear
|
||||
description:
|
||||
published: true
|
||||
date: 2021-09-30T00:26:53.597Z
|
||||
date: 2021-09-30T00:27:00.547Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2021-08-25T01:57:06.706Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
title: V01
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:03:40.894Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:36.476Z
|
||||
---
|
||||
|
||||
<img src="IMG_20151010_123440490_zpsqw2dla5a-sideways.jpg" title="IMG_20151010_123440490_zpsqw2dla5a-sideways.jpg" alt="IMG_20151010_123440490_zpsqw2dla5a-sideways.jpg" width="500" />
|
||||
|
||||
Overview
|
||||
--------
|
||||
|
||||
The V0.1 board was the first hardware implementation and is not intended for general in car use. It does however drastically simplify testing on stationary engines.
|
||||
|
||||
Layout
|
||||
------
|
||||
|
||||
The board is a 2 sided 'shield' that is approximately the same width as an Arduino Mega, but extends out at both ends. It has I/O for all the main sensors as well as 4 channels each of ignition and fuel.
|
||||
<img src="https://raw.githubusercontent.com/noisymime/speeduino/master/reference/hardware/v0.1/kartduino%20v.1.png" style="width: 1000px;height: auto" />
|
||||
|
||||
Populating the board
|
||||
--------------------
|
||||
|
||||
The following components are needed to fully populate the board:
|
||||
|
||||
- R1, R2, R3, R5, R7, R7 = 10k Ohm resistors
|
||||
- R4, R6, R8, R9 = 1k Ohm resistors
|
||||
- D1-D4 = Schottky diode (Eg 1N5819)
|
||||
- C1-C4 = 100nF capacitors rated for at least 6V
|
||||
- Q1-Q4 = TO220 nChannel MOSFETs (Eg STP62NS04Z). Other appropriate MOSFETs will work and maybe substituted but these should have clamping >30V and some protection built in.
|
||||
- U1 = Opto-isolator (Eg CNY17-3). May or may not be needed depending on the type of crank sensor you are using. If your sensor outputs 0-5V directly, this can be left out and the sensor connected directly to digital pin 2 on the arduino
|
||||
|
||||
Dev Notes
|
||||
---------
|
||||
|
||||
The V0.1 board has several drawbacks and issues that are to be addressed for the next version. These include:
|
||||
|
||||
- Lack of ground screw terminals. The board only has a single ground screw connector which must be shared by all sensors. This is less than ideal both physically and electrically.
|
||||
- The use of an opto-isolator for the crank sensor is of debatable value. Most suitable hall sensors will output 0-5V signals and I'm not sure it's worth the extra cost/space to support 0-12V+ sensors as well. This leads to the next issue:
|
||||
- No support for VR crank sensors. The next version of the board will either use a built in VR conditioner or will allow something such as \[the jbperf VR conditioner board\](http://jbperf.com/dual_VR/v2_1.html) to be plugged in if required
|
||||
- No bias resistors onboard for the 2 temperature inputs (CLT and IAT). In order to standardise the voltage divider circuit, these should both have a 2490 Ohm resistor
|
||||
- There is no fly back diode on the MOSFETs. Assumption for this board was that protected drivers would always be used, but the provision for a diode should be added for flexiblity.
|
||||
|
|
@ -0,0 +1,82 @@
|
|||
---
|
||||
title: V02
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:03:50.195Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:37.636Z
|
||||
---
|
||||
|
||||
Overview
|
||||
--------
|
||||
|
||||
The second speeduino shield board is intended to be much more usable and feature complete than the original v0.1 prototype. To this end, I expect it to have the following features:
|
||||
|
||||
- 4 fully protected High impedance injector channels (Each with a LED indicator)
|
||||
- 4 ignition outputs (for driving igniters or logic level coils)
|
||||
- Inputs for CLT, IAT, O2 and TPS
|
||||
- Optional onboard MAP sensor
|
||||
- 2 medium current generic PWM output (3A - Eg Idle control)
|
||||
- 2 low current digital outputs (Max 40mA)
|
||||
- Battery voltage monitoring
|
||||
- 2 speed sensing inputs (RPM and cam)
|
||||
|
||||
` * Hall or optical input by default or;`
|
||||
` * Optional plug in board for VR sensors (Likely to be `[`http://jbperf.com/dual_VR/v2_1.html`](http://jbperf.com/dual_VR/v2_1.html)`)`
|
||||
|
||||
- All I/O to be through screw terminals. Will look at doing an alternative version of the board with a connector if there is interest
|
||||
|
||||
Status
|
||||
------
|
||||
|
||||
First batch of boards is currently in testing (Sep 2014)
|
||||
|
||||
Board layout
|
||||
------------
|
||||
|
||||
A snapshot of the current state of the board is below. Note that this is a working snapshot of the board, so it may look quite messy at times.
|
||||
[<img style="width: 500px;height: auto" src="https://raw.githubusercontent.com/noisymime/speeduino/master/reference/hardware/v0.2/speeduino-v0.2-board.png"/>](https://raw.githubusercontent.com/noisymime/speeduino/master/reference/hardware/v0.2/speeduino-v0.2-board.png)
|
||||
|
||||
Schematic
|
||||
---------
|
||||
|
||||
As above, this is a working, in-progress snapshot of the current schematic. It may look messy at times.
|
||||
[<img style="width: 1000px;height: auto" src="https://raw.githubusercontent.com/noisymime/speeduino/master/reference/hardware/v0.2/speeduino-v0.2-schematic.png" />](https://raw.githubusercontent.com/noisymime/speeduino/master/reference/hardware/v0.2/speeduino-v0.2-schematic.png)
|
||||
|
||||
Board Configuration
|
||||
===================
|
||||
|
||||
The board can be configured in multiple ways depending on the hardware you use and way your setup is configured.
|
||||
|
||||
Optional Components
|
||||
-------------------
|
||||
|
||||
If using a VR crank sensor, the board will require the addition of a VR conditioner. The board has been designed to work with the dual VR conditioner from JBPerf (http://www.jbperf.com/dual_VR/index.html) which will plug directly in. Other VR conditioners will also likely work, but have not been tested.
|
||||
|
||||
Jumper Configs
|
||||
--------------
|
||||
|
||||
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
|
||||
|
||||
To make this simpler, the most common sensor types and their required configurations are below:
|
||||
|
||||
| Crank Sensor | Cam Sensor | JP2 | JP3 | JP4 | JP5 |
|
||||
|---------------------------|-----------------------|------|------|-----|-----|
|
||||
| Floating Hall sensor
|
||||
(Ground and floating) | - | Hall | Off | On | Off |
|
||||
| VR Sensor | - | VR | Off | Off | Off |
|
||||
| 0v-12v Hall Sensor
|
||||
(Requires VR Conditioner) | - | VR | Off | Off | Off |
|
||||
| Floating Hall sensor
|
||||
(Ground and floating) | Floating Hall sensor
|
||||
(Ground and floating) | Hall | Hall | On | On |
|
||||
| VR Sensor | Floating Hall sensor
|
||||
(Ground and floating) | VR | Hall | Off | On |
|
||||
|
||||
|
|
@ -0,0 +1,11 @@
|
|||
---
|
||||
title: V032
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:02:37.928Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:41.549Z
|
||||
---
|
||||
|
||||
1. REDIRECT [V0.3](V0.3 "wikilink")
|
||||
|
|
@ -0,0 +1,104 @@
|
|||
---
|
||||
title: Dropbear
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-27T09:00:37.879Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2021-01-27T08:58:24.108Z
|
||||
---
|
||||
|
||||
# Dropbear ECU
|
||||
The Dropbear is an 8 fuel + 8 ignition ECU that is currently in testing prior to a full production release. It is powered by the high speed Teensy 3.5 board and is designed to be a complete unit out of the box.
|
||||
|
||||
## Features
|
||||
|
||||
- 8x high impedance injector drivers
|
||||
- 8x 5v/12v coil pre-drivers (For use with igniters/smart coils)
|
||||
- 6x medium current (2A) outputs
|
||||
- 7x analog inputs
|
||||
- 4x digital inputs
|
||||
- CAN transceiver
|
||||
- Onboard VR conditioner
|
||||
- Swappable internal MAP sensors
|
||||
- Onboard baro sensor
|
||||
- Optional stepper motor driver
|
||||
|
||||
## Board Configuration
|
||||
The Dropbear board contains 4 switches and 1 DIP switch pair that can be used to change the setup of the ECU.
|
||||
|
||||
### Crank/Cam inputs
|
||||
The ECU contains a dual onboard conditioner that can can be used with VR sensors. The selection between Hall/Optical sensors and VR sensors is made via a pair of switches, one each for the crank and cam. These can be selected independently for setups that use one of each sensor type.
|
||||
|
||||
When set for Hall sensors, this input will work with both the traditional ground switching sensor (the pullup resistor is on the board and does not need to be added) or a 0-12v signal as used on some GM vehicles.
|
||||
|
||||
### MAP Selector
|
||||
The Dropbear board uses a removable MAP card containing the sensor and a short hose running to the bulkhead connector on the enclosure. Currently only the default 0-250kpa sensor board is available, with higher range boards to be made available in the future. To use this MAP card, select the `Int.` (Internal) option on the MAP switch.
|
||||
|
||||
If you wish to use an external MAP sensor located in the engine bay, this switch should be to to `Ext.` and the sensors signal line should be connected to pin `C8` on the Black connector. The MAP card can be left in place or removed when the `Ext.` option is used.
|
||||
|
||||
|
||||
## Pin out
|
||||
|
||||
The Dropbear ECU uses 2x 24 pin Delphi Sicma connectors. The connectors are keyed and will only connect to the matching colour loom plug.
|
||||
|
||||
### Black Connector
|
||||
{.align-center width=400}
|
||||
|
||||
| Pin | Direction | Max Current | Purpose | Comment |
|
||||
|-----|-----------|-------------|---------|---------|
|
||||
| A1 | Input | 5A | Switched 12v | Main power input. Connect to switched 12v power via 5A fuse |
|
||||
| A2 | Input | 15A | Power Ground | Connect to battery negative. |
|
||||
| A3 | Output | 80mA | Sensor reference | Used for sensors requiring a 5v reference (Eg TPS). **Do not use for powering offboard systems.** |
|
||||
| A4 | N/A | N/A | Not used. | |
|
||||
| A5 | Input | N/A | Spare Digital In 2| 12v or Ground switching digital input. Can be used for VSS, Idle Up etc |
|
||||
| A6 | Both | N/A | CAN L | CAN L connection |
|
||||
| A7 | Both | N/A | CAN H | CAN H connection |
|
||||
| A8 | Input | 15A | Power Ground | Connect to battery negative. |
|
||||
| B1 | Output | 100mA | Tacho | 12v square wave output for use as input to a tachometer |
|
||||
| B2 | Input | N/A | Crank Primary | Primary crank sensor (CKP) input. Can be 12v, Ground switching or the positive wire of a VR sensor. See [Crank/Cam Inputs](#crankcam-inputs) section |
|
||||
| B3 | Input | N/A | Crank Negative | **Only used with a VR sensor.** Connect to negative side of VR crank sensor. See [Crank/Cam Inputs](#crankcam-inputs) section |
|
||||
| B4 | Input | N/A | Cam Primary | Cam sensor (CMP) primary input. Can be 12v, Ground switching or the positive wire of a VR sensor. See [Crank/Cam Inputs](#crankcam-inputs) section |
|
||||
| B5 | Input | N/A | Cam Negative | **Only used with a VR sensor.** Connect to negative side of VR cam sensor. See [Crank/Cam Inputs](#crankcam-inputs) section |
|
||||
| B6 | Input | N/A | Spare Digital 1| 12v or Ground switching digital input. Can be used for VSS, Idle Up etc |
|
||||
| B7 | Input | N/A | Clutch input. | Ground switching digital input that goes to ground when clutch is engaged. Do not feed 12v on this input |
|
||||
| B8 | Input | N/A | Flex sensor | Signal wire from GM/Continental Flex sensor. |
|
||||
| C1 | Output | N/A | Analog ground | Ground reference for use by sensors such as TPS, IAT, CLT. **Do not use for powering offboard controllers** |
|
||||
| C2 | Input | N/A | Spare Analog 1 | Spare analog input for use with sensors such as fuel pressure/temperature, oil pressure etc. Should be a 0-5v signal |
|
||||
| C3 | Input | N/A | Spare Analog 2 | Spare analog input for use with sensors such as fuel pressure/temperature, oil pressure etc. Should be a 0-5v signal |
|
||||
| C4 | Input | N/A | O2 Sensor | Connect to the 0-5v signal wire of external wideband controller. Can also be used with 0-1v output from narrowband sensor however wideband is **strongly** recommended |
|
||||
| C5 | Input | N/A | Coolant Sensor | Connect to one side of 2 wire coolant sensor (CLT). Other side of sensor connected to pin C1 |
|
||||
| C6 | Input | N/A | Inlet Air Sensor | Connect to one side of 2 wire inlet air temp sensor (IAT). Other side of sensor connected to pin C1 |
|
||||
| C7 | Input | N/A | Throttle Sensor | Connect to signal line of variable throttle position sensor (TPS). Other pins of sensor should connect to C1 and A3 |
|
||||
| C8 | Input | N/A |External MAP Sensor| Signal line if using external MAP sensor. Input should be 0-5v and MAP source switch should be set to 'Ext.'. See [MAP Selection](#map-selector) section for more details. If using internal sensor this pin should be left unconnected. |
|
||||
|
||||
### Grey Connector
|
||||
{.align-center width=400}
|
||||
|
||||
| Pin | Direction | Max Current | Purpose | Comment |
|
||||
|-----|-----------|-------------|---------|---------|
|
||||
| A1 | Output | 2A | Injector 1 | Injector 1 output |
|
||||
| A2 | Output | 2A | Injector 2 | Injector 2 output |
|
||||
| A3 | Output | 2A | Injector 3 | Injector 3 output |
|
||||
| A4 | Output | 2A | Injector 4 | Injector 4 output |
|
||||
| A5 | Output | 2A | Injector 5 | Injector 5 output |
|
||||
| A6 | Output | 2A | Injector 6 | Injector 6 output |
|
||||
| A7 | Output | 2A | Injector 7 | Injector 7 output |
|
||||
| A8 | Output | 2A | Injector 8 | Injector 8 output |
|
||||
| B1 | Output | 100mA | Ignition 1 | Ignition 1 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B2 | Output | 100mA | Ignition 2 | Ignition 2 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B3 | Output | 100mA | Ignition 3 | Ignition 3 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B4 | Output | 100mA | Ignition 4 | Ignition 4 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B5 | Output | 100mA | Ignition 5 | Ignition 5 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B6 | Output | 100mA | Ignition 6 | Ignition 6 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B7 | Output | 100mA | Ignition 7 | Ignition 7 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| B8 | Output | 100mA | Ignition 8 | Ignition 8 outout. 5v or 12v depending on switch selection. **Do not connect directly to high current coils**, only connect to igniter or 'smart' coil |
|
||||
| C1 | Output | 2A | Boost | Ground switching output for use with boost control solenoid |
|
||||
| C2 | Output | 2A | Fan. | Ground switching output for triggering a fan relay. **Do not drive fan directly from this pin, use only with relay** |
|
||||
| C3 | Output | 2A | Spare 2/Stepper-B2 | Can be used either as ground switching output for general purpose use or 12v output if using a stepper idle control (Requires stepper driver to be fitted, see below) |
|
||||
| C4 | Output | 2A | Idle/Stepper-B1 | Can be used either as ground switching idle output (For use with PWM valves) or 12v output if using a stepper idle control (Requires stepper driver to be fitted, see below) |
|
||||
| C5 | Output | 2A | VVT/Stepper-A1. | Can be used either as ground switching VVT output or 12v output if using a stepper idle control (Requires stepper driver to be fitted, see below) |
|
||||
| C6 | Output | 2A | Spare 1/Stepper-A2 | Can be used either as ground switching output for general purpose use or 12v output if using a stepper idle control (Requires stepper driver to be fitted, see below) |
|
||||
| C7 | Output | 1.5A | Fuel Pump | Ground switching output for triggering fuel pump relay. **Do not drive pump directly from this pin, use only with relay** |
|
||||
| C8 | Input | 15A | Power Ground | Connect to battery negative. |
|
||||
|
||||
|
|
@ -2,9 +2,9 @@
|
|||
title: ASE
|
||||
description: Afterstart Enrichment (ASE)
|
||||
published: true
|
||||
date: 2021-08-10T14:44:13.619Z
|
||||
date: 2021-08-10T14:44:19.360Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2021-08-10T09:26:15.758Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Acceleration Wizard
|
||||
description: Tuning the acceleration enrichment
|
||||
published: true
|
||||
date: 2020-09-16T00:13:54.075Z
|
||||
date: 2020-09-16T00:14:00.031Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:49.039Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Auxillary IO Configuration
|
||||
description:
|
||||
published: true
|
||||
date: 2020-01-19T11:55:21.136Z
|
||||
tags: tuning, aux, IO
|
||||
date: 2021-11-17T12:02:01.896Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:50.218Z
|
||||
---
|
||||
|
||||
# Auxillary IO Configuration
|
||||
|
|
@ -21,9 +23,13 @@ The configuration is mainly split into two categories,
|
|||
|
||||
### How to Configure to use a Local MCU pin
|
||||
|
||||
The configuration page is accessed from the Accessories drop down within TunerStudio ,select the "local Auxillary input channel configuration" option 
|
||||
The configuration page is accessed from the Accessories drop down within TunerStudio ,select the "local Auxillary input channel configuration" option
|
||||
|
||||
This window will be opened. 
|
||||
|
||||
|
||||
This window will be opened.
|
||||
|
||||
!
|
||||
|
||||
In the above image the first two channels have been configured as an local analog and a local digital input respectively.
|
||||
|
||||
|
|
@ -53,11 +59,16 @@ This setting is only available for local mcu pin selections. It is the actual mc
|
|||
|
||||
### How to Configure to use a External Data Source
|
||||
|
||||
To use the Auxillary input channels for external data the Secondary IO must be enabled. [See here for further information on how to do this.](Secondary_Serial_IO_interface#Enable_Secondary_IO_interface "wikilink")
|
||||
To use the Auxillary input channels for external data the Secondary IO must be enabled. [See here for further information on how to do this.](https://wiki.speeduino.com/en/Secondary_Serial_IO_interface)
|
||||
|
||||
The configuration page is accessed from the Accessories drop down within TunerStudio ,select the "External Auxillary input channel configuration" option 
|
||||
The configuration page is accessed from the Accessories drop down within TunerStudio ,select the "External Auxillary input channel configuration" option
|
||||
|
||||
This window will be opened. 
|
||||
|
||||
|
||||
This window will be opened.
|
||||
|
||||
|
||||
|
||||
|
||||
For External data inputs to be active the "Enable External Data Input" option must be enabled.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Barometric Correction
|
||||
description:
|
||||
published: true
|
||||
date: 2021-11-11T07:25:29.014Z
|
||||
tags: baro
|
||||
editor: markdown
|
||||
date: 2021-11-11T07:25:34.808Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2021-11-11T07:25:29.014Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Board Defaults
|
||||
description: Changing board defaults or reusing already in use inputs/outputs
|
||||
published: true
|
||||
date: 2021-04-03T16:54:13.262Z
|
||||
tags: board default
|
||||
editor: ckeditor
|
||||
date: 2021-04-03T16:54:18.611Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2021-02-28T05:54:07.954Z
|
||||
-->
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Boost Control
|
||||
description: Open and closed loop boost control settings
|
||||
published: true
|
||||
date: 2020-01-19T11:43:23.245Z
|
||||
date: 2020-04-08T02:07:36.974Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:51.415Z
|
||||
---
|
||||
|
||||
# Boost Control
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Cranking
|
||||
description:
|
||||
published: true
|
||||
date: 2021-08-10T13:17:40.276Z
|
||||
date: 2021-08-10T13:17:46.299Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:52.563Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Dwell
|
||||
description:
|
||||
published: true
|
||||
date: 2021-08-12T08:18:24.876Z
|
||||
date: 2021-08-12T08:18:30.759Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:53.703Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Engine Constants
|
||||
description:
|
||||
published: true
|
||||
date: 2021-08-24T12:54:34.436Z
|
||||
date: 2021-08-24T12:54:40.432Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:54.869Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,13 @@
|
|||
---
|
||||
title: Errors
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:07:46.754Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:56.025Z
|
||||
---
|
||||
|
||||
Overview
|
||||
--------
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Flex Fuel
|
||||
description: Setting up the flex fuel / ethanol content sensor
|
||||
published: true
|
||||
date: 2020-01-16T12:09:30.179Z
|
||||
date: 2020-04-08T02:07:49.978Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:57.218Z
|
||||
---
|
||||
|
||||
# Flex Fuel
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Fuel pump
|
||||
description: Setting the on/off conditions of the fuel pump
|
||||
published: true
|
||||
date: 2021-01-20T11:39:57.637Z
|
||||
tags: aux outputs, tuning
|
||||
editor: markdown
|
||||
date: 2021-01-20T11:40:03.348Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-14T06:24:04.641Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: GM Distributor Module
|
||||
description:
|
||||
published: true
|
||||
date: 2021-02-21T21:51:36.677Z
|
||||
date: 2021-02-28T05:51:30.664Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2021-02-21T21:51:36.677Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: IAT Density
|
||||
description:
|
||||
published: true
|
||||
date: 2020-01-16T16:05:09.541Z
|
||||
date: 2020-04-08T02:07:56.210Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:58.480Z
|
||||
---
|
||||
|
||||
# IAT Density
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Temperature based timing changes
|
||||
description:
|
||||
published: true
|
||||
date: 2020-01-16T11:40:27.486Z
|
||||
tags: tuning
|
||||
date: 2020-04-08T02:07:59.335Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-14T00:30:56.331Z
|
||||
---
|
||||
|
||||
# Temperature based timing changes
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Idle
|
||||
description:
|
||||
published: true
|
||||
date: 2020-04-08T02:02:30.883Z
|
||||
date: 2020-04-08T02:08:02.750Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:53:59.753Z
|
||||
---
|
||||
|
||||
# Idle Control
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Idle advance
|
||||
description: Controlling idle speed with changes to advance
|
||||
published: true
|
||||
date: 2020-01-14T02:02:16.409Z
|
||||
tags: idle, tuning
|
||||
date: 2020-04-08T02:08:05.954Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-14T00:45:09.872Z
|
||||
---
|
||||
|
||||
# Idle advance control
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Injector Characteristics
|
||||
description: Configuring the injector properties
|
||||
published: true
|
||||
date: 2020-02-29T21:36:42.779Z
|
||||
date: 2020-04-08T02:08:09.204Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:01.036Z
|
||||
---
|
||||
|
||||
# Injector Characteristics
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Launch & Flatshift
|
||||
description:
|
||||
published: true
|
||||
date: 2020-01-18T22:26:20.161Z
|
||||
tags: tuning, launch, flat shift, 2-step
|
||||
date: 2020-04-08T02:08:12.434Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:02.178Z
|
||||
---
|
||||
|
||||
# Launch Control & Flat Shift
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Nitrous Control
|
||||
description:
|
||||
published: true
|
||||
date: 2020-03-19T03:56:03.494Z
|
||||
tags: n2o, nitrous, tuning
|
||||
date: 2020-04-08T02:08:15.613Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-03-19T02:43:54.000Z
|
||||
---
|
||||
|
||||
# Nitrous Control
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: O2
|
||||
description:
|
||||
published: true
|
||||
date: 2020-01-16T16:03:52.330Z
|
||||
date: 2020-04-08T02:08:18.892Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:03.309Z
|
||||
---
|
||||
|
||||
# AFR/O2 (Closed loop fuel)
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Priming
|
||||
description: Priming Pulsewidth page
|
||||
published: true
|
||||
date: 2021-08-10T14:18:37.328Z
|
||||
date: 2021-08-10T14:18:43.034Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2021-08-10T07:29:47.817Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
title: Reset_Control
|
||||
description:
|
||||
published: true
|
||||
date: 2021-01-20T12:47:36.387Z
|
||||
date: 2021-01-20T12:47:42.614Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:04.493Z
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Limiters
|
||||
description: Configuring engine protection limiters
|
||||
published: true
|
||||
date: 2020-01-19T11:45:07.950Z
|
||||
date: 2020-04-08T02:08:25.395Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:05.687Z
|
||||
---
|
||||
|
||||
# Limiters
|
||||
|
|
|
|||
|
|
@ -2,8 +2,10 @@
|
|||
title: Sensor Calibration
|
||||
description: Steps for calibrating all analog sensor inputs
|
||||
published: true
|
||||
date: 2020-01-19T11:42:14.490Z
|
||||
date: 2020-04-08T02:08:28.650Z
|
||||
tags:
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:06.827Z
|
||||
---
|
||||
|
||||
# Sensor Calibration
|
||||
|
|
|
|||
|
|
@ -2,9 +2,10 @@
|
|||
title: Spark Settings
|
||||
description: Configuration options for the ignition outputs
|
||||
published: true
|
||||
date: 2020-06-18T01:40:50.711Z
|
||||
date: 2020-06-18T01:40:56.465Z
|
||||
tags:
|
||||
editor: markdown
|
||||
editor: undefined
|
||||
dateCreated: 2020-01-06T01:54:08.016Z
|
||||
---
|
||||
|
||||
# Spark Settings
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue