Autosport Labs - User contributions [en]

CAN Bus Integration

2026-08-19T19:28:13Z

Brentp: /* Check the CAN activity LED */

=Introduction=
Mapping an existing CAN bus system can be easy with basic knowledge of CAN mapping, and most importantly - if CAN technical documentation is available for the device in question. Fortunately, ECU and sensor manufacturers are keen on providing documentation as they naturally want their devices as inter-operable as possible.

If documentation isn't available, the problem is just more interesting to someone with the time and skills, and it helps that the CAN bus system is open in terms of it's messaging format and provides simple 8 byte message packets with a numeric identifier, much like an internet IP address.

=Prerequisites=
To successfully perform a custom CAN integration, it's helpful to have the following knowledge before you get started.
* Basic knowledge of wiring and making wiring connections
* Basic knowledge of CAN bus technology. [https://www.google.com/webhp?&ion=1#q=can+bus+tutorial Here are some some helpful links.]

Also, if you need to make a custom mapping because no preset exists for your device:
* Basic understanding of math
* Basic understanding of data represented as [https://computer.howstuffworks.com/bytes.htm bits and bytes]

If this appears challenging, get a friend to help and / or [http://forum.autosportlabs.com jump onto the forums] and ask for assistance - another forum member might have mapped the same system as you're working with, or can help you with your particular project.

=Preset configurations=
Fortunately, we have a [[RCP_CAN|growing library of pre-set configurations for different ECUs and sensors]]. As time goes on, the chances grow that you'll be able to simply click a button and have a quickly working CAN integration.

[[image:racecapture_select_can_preset.gif]]
==Wiring CAN bus==

Integrating a CAN-enabled device to RaceCapture involves connecting the CAN bus connections to RaceCapture.

Each CAN device has two wires that provides data:
* CAN high (CANH)
* CAN low (CANL)

When you connect the device to the CAN bus, you would connect the CAN high and CAN low wires of the device to the CAN high and CAN low wires of RaceCapture.

===Choosing the CAN bus to connect===
RaceCapture has multiple CAN bus networks. There is a convention for choosing which CAN bus when connecting a device:

* CAN1 - typically used for ECUs (OBDII and after-market)
* CAN2 and higher - typically used for extended sensor networks, such as AnalogX, TireX, etc.
[[File:CAN Connection 1.png|700px]]

This approach isolates the extended sensors from the car's ECU, especially important when working with OEM ECU networks.

* '''Note''' - this is not a hard and fast rule, but a convention. Advanced users may choose any configuration that meets their needs.

===Plug and Play connector system===
* Applies to
** RaceCapture/Track MK3
** RaceCapture/Pro MK4
** PodiumConnect MK2
[[Harness_specifications|See the full plug and play harness specification]]

====Power + CAN Single interconnect====
* Connector: M8 4P, A coding
[[file:M8_4P_male_pinout.jpg|200px]]

''Male connector pictured''

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}

==Dual CAN + power interconnect==
* Connector: M8 6P, A coding
[[file:M8_6P_male_connector.png]]

''Male connector pictured''
{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN1 low ||
|-
| 2 || CAN2 low ||
|-
| 3 || CAN2 high ||
|-
| 4 || Ground ||
|-
| 5 || CAN1 high ||
|-
| 6 || Power || 9-24v / 1A (~12W)
|}

===Molex connector===
* Applies to
** RaceCapture/Pro MK3

Both CAN ports are available on the molex connector:

[[file:RaceCapture_Pro_MK3_Molex_CAN_pinout.png]]

===RJ45 connector===
* Applies to
** RaceCapture/Pro MK2, MK3
** RaceCapture/Track MK1, MK2

This port is typically used for the optional CAN-OBDII interface cable, but can also be used for custom integrations. Both CAN channels are available on the RJ45 connection.

====Cabling====
You can custom crimp an RJ45 cable, or you can use a standard CAT-5 ethernet cable with RJ45 connectors to integrate with RaceCapture/Pro.
{| class="wikitable" style="text-align:center; width:700px; height:200px;"
|+ RJ45 Power, ground and CAN bus connections to RaceCapture/Pro
|+ EIA-T568B RJ45 cable color codes (check printing on the cable to confirm)
|-
! Connection
! RaceCapture/Pro (RJ45 cable)
|-
| +12v
| Brown
|-
| Ground
| Orange/White
|-
| CAN 1 High
| Orange
|-
| CAN 1 Low
| Green/White
|-
| CAN 2 High
| Blue
|-
| CAN 2 Low
| Blue/White
|}

[[File:RaceCapturePro_MK3_RJ45_pinout.png]]
* '''Important note for MK2:''' The +12v connection on the RJ45 is connected internally to the +12v on the terminal block on RaceCapture/Pro MK2. It's recommended you only power via one source - RJ45 or terminal block - if you have both connected at the same time, you may cause back-feeding of power through RaceCapture/Pro, which may cause damage to the unit. '''Note: RaceCapture/Pro MK3 has internal protection diodes which avoids this issue.'''

==Researching CAN Bus protocol==
If you are working to integrate an ECU, first ask the manufacturer for their CAN bus specification. This documentation will provide a breakdown of channels - such as RPM, temperatures and pressures and describe how they appear in the CAN message stream. A good example is the [http://www.msextra.com/doc/pdf/Megasquirt_CAN_Broadcast.pdf Megasquirt CAN Broadcast Specification].

===CAN Bus documentation===
The manufacturer provided document will show for each channel the following information:
* '''Channel''': (RPM, Engine Temperature, Throttle Position, etc)
* '''CAN Identifier''': The CAN Identifier for each channel. This may appear in either 11 or the extended 29 bit format. Typically 11 bits are used.
* '''Offset''': where the data starts within the 8 byte CAN message. An offset of 0 means the data starts on the first byte.
* '''Length''': Typically 1 or two bytes
* '''Scaling''': The raw value from the message is often scaled to a real world value. Typically this is provided as a multiplier and adder value, but may also specify a divider.

===Big Endian or Little Endian mode===
Additionally, the manufacturer will specify if multi-byte (16, 24 or 32 bit) values are presented in '''Big Endian''' (MSB (Most Significant Bit)) or '''Little Endian''' (LSB (Least Significant Bit)) mode.

BigEndian mode data will have the high byte presented first in the data packet and is typically the most common format.

Big Endian / Little Endian Example:
* Decimal value: 1000
* Hex Value in Big Endian: 0x03E8
* Hex Value in Little Endian: 0xE803

If provided in a CAN message, it might show up as follows in this hypothetical message:

MSB format:
* Offset 1
* Length 2
* Data:
(Hex) [xx] [03] [E8] [xx] [xx] [xx] [xx] [xx]
(Decimal) [xx] [3] [232] [xx] [xx] [xx] [xx] [xx]

LSB format:
* Offset 1
* Length 2
* Data:
(Hex) [xx] [E8] [03] [xx] [xx] [xx] [xx] [xx]
(Decimal) [xx] [232] [3] [xx] [xx] [xx] [xx] [xx]

=Enabling CAN bus=
Once you have the CAN connections wired, you can enable CAN bus on your RaceCapture system. This provides the ability to turn on the CAN bus connectivity at the global level, and allows you to set the baud rate for the individual CAN bus channels.

[[file:RaceCapture_CAN_bus_settings.png|640px]]

After making changes, be sure to '''write''' your configuration back to your RaceCapture device.

=Mapping CAN data to channels=

==Direct CAN mapping==
The direct CAN mapping capabilities will allow easy mapping of 99% of existing CAN based ECUs and sensors. For the outliers, you can map CAN data using the [[CAN_Bus_Integration#Lua_scripting|on-board Lua Scripting]], allowing for any custom formula or logic.

===Adding a channel===
* To start, connect to your RaceCapture device and ensure the current configuration is read, or open a previously saved configuration.
* Navigate to the CAN Mapping page.
* Ensure '''CAN channels''' is set to '''on'''
* Press the (+) button to add your first channel.

[[file:RaceCapture_CAN_mapping.png|640px]]

====Defining the Channel====
The first tab will let you define the channel name and sample rate.

[[file:RaceCapture_CAN_mapping_channel_tab.png]]

* '''Channel Name''': selecting a channel name from the drop-down will pre-set the units, min, max and precision to typical values.

You can customize this by pressing the gear icon to customize:
** '''Channel Name''' - Specify the channel name. We recommend formatting the name with CamelCase with a leading capital letter, and no spaces or underscores.
** '''Units''' - The unit of measurement for the channel
** '''Min''' - The minimum value for the channel
** '''Max''' - The maximum value for the channel
** '''Precision''' - Sets the number of decimal places for logged and displayed numbers.

* '''Rate''': This sets the rate that RaceCapture will log or broadcast the data for this channel. This rate is independent of the actual rate the CAN data is received. Select a rate that mirrors the expected update rate of the sensor. Example: Engine temperature changes slowly, so select 1Hz. RPM changes quickly; 10-50Hz is ideal.

====Defining the CAN ID and bus====
The CAN ID match tab lets you define the CAN ID to match upon, and the CAN bus the data is expected to appear upon. The manufacturer will specify the CAN ID for the channel you are mapping.

[[file:RaceCapture_CAN_mapping_can_id_tab.png|486px]]

* '''CAN ID''': this is the ID of the CAN bus message, in decimal format.
* '''Mask''': This is an optional mask, in decimal format. If set to greater than zero, the Mask will be logically AND'd with the CAN ID for further matching and filtering.
** ''If uncertain, leave this unchanged''
* '''Sub ID''': If the CAN message specifies the first byte as an additional ID to differentiate messages, specify the value to match here.
* '''CAN Bus''': Select the CAN bus your data is appearing on - CAN 1 or 2, depending on the available CAN ports of your RaceCapture device.

====Defining the mapping====
The Raw Value Mapping tab lets you define how to extract the data from the 8 byte CAN message. The manufacturer's CAN documentation will identify this information for channel you are mapping.

[[file:RaceCapture_CAN_mapping_raw_value_mapping.png]]

* '''Offset''': this is the offset where the data appears in the CAN message. An offset of 0 would be used to start at the first byte of the CAN message.
* '''Length''': this represents the length of the value. A length of 1 would be one byte, 2 would represent a two byte or 16 bit word, and so on.
* '''Source Type''': this represents the native encoding of the data. Most typically this is represented as a plain unsigned value, but can appear in other formats. The manufacturer's CAN documentation will identify the data type. Supported native data types:
** Unsigned: the data is provided as an unsigned value.
** Signed: the data is provided as a [https://en.wikipedia.org/wiki/Two%27s_complement two's compliment] signed value.
** Float: the data is provided as a [https://en.wikipedia.org/wiki/IEEE_floating_point IEEE-754 encoded] floating point value
** Sign-Magnitude: the data is provided as a [https://en.wikipedia.org/wiki/Signed_number_representations#Signed_magnitude_representation sign-magnitude] encoded value.

* '''Endian''': This defines Big Endian (Most significant bit / MSB) or Little Endian (Least Significant Bit / LSB) mode, and applies to values where the data length is 2 or higher. The manufacturer's documentation will identify whether the data is encoded in big or little endian format.

* '''Bit Mode''': This allows mapping in cases where the data does not fall on even byte boundaries. For example, you may want to extract a single bit at the offset of 11; in which case you would enable bit mode, then set your offset to 11 with a length of 1.
** ''If uncertain, leave this unchecked, or check the manufacturer's documentation''

====Defining the Formula====
The Formula tab lets you define how to convert the extracted raw value into a meaningful real-world value.

[[file:RaceCapture_CAN_mapping_formula_tab.png]]

The formula is defined as:
Extracted Raw Value X '''multiplier''' ÷ '''divider''' + '''adder'''

Use these fields to specify the conversion formula you wish to apply to the raw value extracted from the CAN message. The manufacturer's documentation will specify the conversion formula.

====Units Conversion====
[[file:RaceCapture_CAN_mapping_units_conversion_tab.png]]

You can optionally apply a common units conversion to the value after it has been processed by the formula. Often the manufacturer will provide the mapping in one form of units - this allows you to retain the original mapping and then convert the units to the desired format.

===Testing your channel===
When complete with the mapping, press the (check) button and then '''Write''' your configuration back to RaceCapture. You can then go to the dashboard to monitor the current channels and verify you are receiving data as expected.

===Not getting the expected data?===
See the [[CAN_Bus_Integration#Troubleshooting|Troubleshooting Guide]] to help understand and identify problems in your CAN mapping and connectivity.

==Lua scripting==
* Applies to:
** RaceCapture/Pro MK2 and newer
** RaceCapture/Apex
** RaceCapture/Track MK2 and newer

For custom mapping that cannot be handled by the direct CAN mapping capabilities, you can map data using the on-board Lua scripting runtime. Here you will be able to apply any formula or custom logic to the data before mapping it to a channel in RaceCapture.

===Reading a CAN message===
You can use the Lua scripting to read and process data from a CAN message. See the [[RaceCapturePro_Lua_Scripting#CAN_Bus_functions|Lua Scripting reference]] for a list of CAN bus functions.

Example reading and printing the ID and first byte of a CAN message:

id, ext, data = rxCAN(0, 100)
print("ID: " ..id .."Data: " ..data[1])

===Mapping to a Virtual Channel===

You can create a virtual channel by using the ''[[RaceCapturePro_Lua_Scripting#Virtual_Channels|addChannel()]]'' lua function. The typical approach involves:

* Set up the channel. Example "EngineTemp"

* Read a CAN message
* Extract a value from the data fields
* Scale the extracted value to a real world value (Example: Degrees F)
* Set the virtual channel with the scaled value

* Example: Set '''MyChannel''' from CAN ID 1234. Data is in the first byte of the message.
<pre>
channelId = addChannel("MyChannel", 10)
setTickRate(10)

function onTick()
id, ext, data = rxCAN(0)
if id == 1234 then
setChannel(channelId, data[1])
end
end
</pre>

==CAN integration framework==
Below is a script framework to ease mapping of CAN bus data to virtual channels. You can copy the script and modify as you need. This example showcases mapping some of the BMW E46 CAN bus channels.

To create your own integration, edit the top portion of the file to match your system's CAN bus configuration and data mapping.

<pre>
--This example configured for E46 CAN

--how frequently we poll for CAN messages
tickRate = 30
--the CAN baud rate
CAN_baud = 500000
--CAN channel to listen on. 0=first CAN channel, 1=second
CAN_chan = 0
--1 for Big Endian (MSB) mode; 0 for Little Endian mode (LSB)
be_mode = 0

--add your virtual channels here
tpsId = addChannel("TPS", 10, 0, 0, 100, "%")
tempId = addChannel("EngineTemp", 1, 0, 0, 200, 'C')
oilTempId = addChannel("OilTemp", 1, 0, 0, 200, 'C')
rpmId = addChannel("RPM", 10, 0, 0, 10000)

--customize here for CAN channel mapping
--format is: [CAN Id] = function(data) map_chan(<channel id>, data, <CAN offset>, <CAN length>, <multiplier>, <adder>)
CAN_map = {
[809] = function(data) map_chan(tpsId, data, 6, 1 , 0.392156863, 0) map_chan_le(tempId, data, 2, 1 , 0.75, -48.373) end,
[1349] = function(data) map_chan(oilTempId, data, 5, 1, 1, -48.373) end,
[790] = function(data) map_chan(rpmId, data, 3, 2, 0.15625, 0) end
}

function onTick()
processCAN(CAN_chan)
end

--===========do not edit below===========
function processCAN(chan)
repeat
local id, e, data = rxCAN(chan)
if id ~= nil then
local map = CAN_map[id]
if map ~= nil then
map(data)
end
end
until id == nil
end

--Map CAN channel, little endian format
function map_chan_le(cid, data, offset, len, mult, add)
offset = offset + 1
local value = 0
local shift = 1
while len > 0 do
value = value + (data[offset] * shift)
shift = shift * 256
offset = offset + 1
len = len - 1
end
setChannel(cid, (value * mult) + add)
end

--Map CAN channel, big endian format
function map_chan_be(cid, data, offset, len, mult, add)
offset = offset + 1
local value = 0
while len > 0 do
value = (value * 256) + data[offset]
offset = offset + 1
len = len - 1
end
setChannel(cid, (value * mult) + add)
end

map_chan = (be_mode == 1) and map_chan_be or map_chan_le
initCAN(CAN_chan, CAN_baud)
setTickRate(tickRate)
</pre>

==Reverse Engineering==
Reverse engineering can be a rewarding experience, providing you can log the CAN data stream from the device and compare it against direct measurements on the system.

===Common Approach===
* Log all messages from the CAN bus
* Directly measure or observe a sensor channel and compare it against changes in the CAN bus data, watching for patterns.

===Example===
An example for decoding RPM: To detect which CAN message contains RPM, log all CAN messages while simultaneously directly logging RPM, synchronizing the messages and the direct RPM measurement in time. Watch for patterns in the CAN data: any data changing in sync with the direct RPM measurements will be a strong indicator of which CAN message contains RPM data.

Repeat with other sensors of interest, such as steering angle, tempertures, etc.

===Logging Data===
You can use a commercial CAN data logger, or simply use RaceCapture/Pro's [[CAN_Bus_logger|CAN bus logger script]] to output all messages to the logging window.

=Troubleshooting=
==Check the CAN bus settings==
* Ensure the global CAN enabled option is turned '''on'' on the CAN settings page
* Ensure the baud rate matches the network you're connecting to.
** If you're not certain, check the documentation of the device you're integrating with (ECU, sensor network, etc)
* Ensure the CAN termination is correct for the network you are on.
** Termination is required at both ends of the network; check your manufacturer if termination is enabled inside the device, or if an external jumper is needed.
** '''Note:'''
*** RaceCapture/Pro MK3, RaceCapture/Apex, PodiumConnect, RaceCapture/Track MK3: Termination is software controlled; enabled by default. It can be enabled/disabled in the CAN Bus settings page.
*** RaceCapture/Pro MK2 has termination enabled by default, it can be disabled by disabling the internal jumper
*** RaceCapture/Track (MK1, MK2) - Termination is disabled by default. Termination can be enabled by enabling an internal jumper.

==Check the CAN activity LED==
The CAN activity LED will indicate if CAN data is being received by your RaceCapture system. If it's illuminated, that means RaceCapture is receiving CAN data.
* Applies to:
** RaceCapture/Apex
** RaceCapture/Pro MK3
** RaceCapture/Track (MK3 and MK4)
** PodiumConnect MK2
** PodiumConnect/Micro

==Check the CAN bus you are using (CAN1 or CAN2)==
If you're using a preset, check if the CAN bus you wired matches the CAN bus selected for each channel in the preset.
* Most presets are configured to use CAN1. If you wired your CAN but to CAN2, you will need to switch each channel under presets to CAN2.

==Check the wiring==
* Ensure you have CAN High and CAN Low of the other CAN device wired to the equivalent CAN high and CAN low of RaceCapture.
** If the wires are reversed, try swapping them.
* Check that you have the wires connected correctly per the pinout of your system.

==Check termination on the bus==
Ideally, you should have termination at each end of the bus. Due to the robustness of CAN bus, often termination at one end of the bus is sufficient for correct data transmission.
** RaceCapture/Pro, RaceCapture/Apex and PodiumConnect: Software-controlled termination can be accessed under Setup/CAN bus.
** RaceCapture/Track MK1 and MK2 have no termination on board - termination can be added near the connector.

Ensure that the device at the opposite end of the CAN bus has termination enabled.

* To enable termination, connect a 120 ohm resistor (1/8 to 1/4 W) across the CAN high and CAN low wires.

==Check the other device==
Ensure the setup is correct on the device. Check their manual and software to ensure:
* CAN broadcasting is enabled
* CAN baud rate matches the CAN baud rate your system
** Typical baud rates are 250K, 500K and 1M
* CAN IDs match the IDs you have defined under the CAN channels.
** Some devices have the ability to set an alternate addressing scheme; their documentation will indicate if this is possible.
** Use the [[CAN_Bus_logger|simple logging script]] to display all CAN traffic in the logging window to see if what you are receiving is what you expect.

==CAN bus logger==
* Try using the [[CAN_Bus_logger|simple logging script]] to show any incoming data and that it matches what you expect vs the manufacturer's specifications.

File:Pin Configuration 1.png

2026-07-30T14:28:38Z

Brentp: Brentp uploaded a new version of File:Pin Configuration 1.png

Pin Configuration

File:PodiumConnect Micro Solid.zip

2026-07-24T14:24:47Z

Brentp:

PodiumConnect Micro

2026-07-24T14:24:29Z

Brentp: /* Technical Specifications */

=Quick Start Guide=
[[File:Podium Connect Micro.png|640px]]
==Connecting the Hardware==
===Mounting===
* Mount the Podium Connect Micro where the USB connection is easily accessible.
* The unit can be mounted in any orientation.
* Ensure the unit is kept away from direct heat sources.

===Pigtail Connection===
* If your system includes a pigtail connector, use the M8 4-pin connector for power and CAN communication.
* Red wire to +12V, Black to ground, Green to CAN High and White to CAN Low.
* Note: it is recommended to use same power of your data system.

[[file:M8_4P_male_pinout.jpg|200px]]

''Male connector pictured''

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}

Power is standard automotive 12-14v (nominal).

===Plug-and-Play Connection (AIM)===
* If your system includes the AIM integration cable, plug it directly to the AIM Data Hub.
'''Note:''' It is the same data hub where AIM SmartyCAM plug into.

[[File:AIM Connection node.jpg]]

==Create Your Podium Account==
===Create Device and Streaming Key===
* Create an account on [http://podium.live Podium]
* Setup the Device Name
* Make a note of the Streaming ID provided, so you can enter it into the wizard later.
[[File:Streaming ID.jpg|640px]]

==Downloading and Installing the Podium App==
The Podium App is available for Windows, macOS, Android, and iOS platforms. You can find the download links on the Podium Software Page.
[[File:Windows Download.png]]
===Windows===
* Get the latest version of the Podium App from the [https://podium.live/software DOWNLOADS PAGE].
* Download the .exe file for Windows.
[[File:Installing on Window.png]]
* Run the setup wizard and follow the on-screen instructions to complete the installation.
* Once installed, launch the app and log in using your Podium account.
===macOS===
Download the .dmg file for macOS.
Open it and drag the Podium App to your Applications folder.
After installation, open the app and sign in with your credentials.

===Android/iOS===
* Get the latest version of the Podium app from the following.
[[Image:google_play.jpg|link=https://play.google.com/store/apps/details?id=com.autosportlabs.podium]][[Image:itunes_app_store.jpg|link=https://apps.apple.com/us/app/podium-livestream-your-racing/id1499176249]]

==Creating an Event and Adding Devices==
* Create an Event
** In the app, go to My Events and click Create Event.
** Enter your Event Title, Start and End Dates, and Track details.
[[File:Creating Event.png]]

* Add Devices
** After creating an event, add one or more devices to it.
** This enables you to stream telemetry data and compare laps directly within the dashboard.
[[File:Adding Devices.png]] 

For more detailed guidance on analyzing driver data and using advanced tools, refer to the [Podium Driver Data Analysis Guide https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis]

==First-Time Setup Wizard==

The first time setup wizard will guide you through the essential setup of your PodiumConnect

[[File:First-Time Wizard 1.png|640px]]

Ensure the device is connected via USB before proceeding

[[File:First-Time Wizard 2.png|640px]]

* Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app.
* Note: To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.

===Configure System Presets===
Select the preset configuration matching the data system you have.
[[Image:RaceCapture_app_PodiumConnect_AIM_preset_selection.jpg|640px]]

===Select Favorite Race Tracks===
* Select the tracks you will typically race at so PodiumConnect can detect the track location and calculate lap times.
* '''This is an important step''' to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [[RaceTracks|please submit your track]]!

[[Image:RaceCapture_app_select_favorite_tracks.jpg|640px]]

===Configure Telemetry Streaming Key===
* Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium.
[[File:Streaming key.png|640px]]

===Configure WiFi Connection and WiFi Telemetry===
'''After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:'''

* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the '''client setup''' to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"

[[File:Configure wifi.jpg|640px]]

===Verify Telemetry===
[[File:VERIFYING TELEMETRY.png]]

====Verifying CAN Bus Connectivity====
* Ensure the connector is properly plugged into your data system. This will initiate data reception and also power up the unit when USB is not connected.
* Observe the orange LED on the unit, a steady blinking orange light indicates active CAN bus communication
====Verifying Wi-Fi====
* In the RaceCapture application go to System Status > Wifi
* Verify Client is connected
[[File:Podium Verifying Wifi.png|640px]]

====Verify Telemetry on Podium====
* Wait for the telemetry LED to begin flashing regularly, this indicates that telemetry is actively broadcasting.
* Log in to your Podium account at PODIUM and navigate to the event page.
* Refresh the page; if telemetry is active, an Ad Hoc event will appear.
[[File:Verify Telemetry on Podium.png|640px]]

* Click the Ad Hoc event link to view the connected device.
* Select your device to access the race dashboard and confirm that live data is streaming.
[[File:Verify Telemetry on Podium2.png|640px]]

====Verify Telemetry on Podium Mobile App====
* Download the [https://play.google.com/store/apps/details?id=com.autosportlabs.podium&hl=en Podium Mobile App]
* Log in to your Podium account using the Podium app.
* Navigate to the Events section and tap on the active streaming event.
* You will be directed to the dashboard displaying live telemetry data, lap timing, and other real-time metrics.

== Wi-Fi Operating Modes==
PodiumConnect Micro support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

=== Wi-Fi Operating Modes ===
[[File:Wifi Podium Updated.png]]

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

==== Wi-Fi Reliability Improvements in Firmware v2.23.3 ====
Firmware version 2.23.3 introduces multiple improvements to Wi-Fi reliability and connection stability for PodiumConnect/Micro. These updates are focused on improving real-world Wi-Fi behavior during configuration and telemetry use.

'''Summary of Improvements'''

* Improved Wi-Fi connection stability during normal operation
* More reliable reconnection behavior after temporary signal loss
* Improved handling of access point and network transitions
* Reduced likelihood of stalled or unresponsive Wi-Fi connections
* Improved behavior during STA hotspot scanning
* General robustness improvements when operating in environments with variable or congested wireless conditions

'''Note:''' These improvements apply automatically when running firmware version 2.23.3 or newer. No additional configuration is required.

= Real-time Telemetry Setup =
This section explains how to configure PodiumConnect Micro to stream live telemetry data to the Podium cloud service so it can be viewed remotely using the Podium app or the Podium website.

=== Overview ===
Three components are used when working with live telemetry:

* RaceCapture App : Used to connect directly to the device for configuration and local dashboard viewing.
* Podium App : Used to view live telemetry and previously recorded sessions in the cloud.
* Podium Website : Provides web access to the same telemetry data available in the Podium app.

=== Step 1 : Configure WiFi Connectivity ===
[[File:Inital setup.gif|750px]]
* Open the RaceCapture app and connect to your device.
* Navigate to Setup from the main screen.
* Click Read to load the current configuration.
* Select the Wireless tab.
** Configure the following settings:
*** Enable WiFi Support
*** Enable Client Mode
*** Enter the SSID and password for your hotspot or WiFi network
'''Note:''' The hotspot must support 2.4 GHz WiFi. Many hotspots default to 5 GHz, which is not supported. If necessary, configure your hotspot to allow 2.4 GHz operation.
For testing purposes, you may use your phone’s hotspot to confirm the connection is working correctly.
* Enable WiFi Telemetry at the bottom of the Wireless settings.
[[File:Enable wifi telemetry option.png|750px]]

=== Step 2 : Configure the Telemetry Streaming Key ===
[[File:Telemetry streaming key updated.gif|750px]]

To stream telemetry to Podium, you must enter a Telemetry Streaming Key.
* Open the Podium website.
* Navigate to Settings → Devices.
* Select your device from the list.
* Copy the Streaming Key shown for the device.
Return to the RaceCapture app:
* Navigate to the Telemetry tab.
* Paste the Streaming Key into the Telemetry Streaming Key field.

=== Step 3 : Configure Streaming Behavior ===
[[File:Background streaming key.png|750px]]

For testing or continuous streaming '''Enable Background Streaming'''.
This causes the device to begin telemetry streaming immediately after power-up. If Background Streaming is disabled, telemetry streaming will begin only when the system starts logging based on its configured trigger (typically vehicle speed, but other channels such as RPM may be used). This helps prevent unnecessary telemetry transmission when the vehicle is powered but not actively driving.

=== Step 4: Apply Configuration and Reboot===
Click Write to save the configuration to the device.

[[File:Configuration (write).png|750px]]

Reboot the device by either:
* Power cycling the unit, or
[[File:Rebot.png|750px]]
* Navigating to Setup > Firmware > Reboot.

=== Step 5 : Verify WiFi Connection ===
[[File:Verify WiFi Connection gif file.gif|750px]]

After rebooting:
* Navigate to System Status > WiFi.
* Confirm the WiFi Client is connected to the hotspot.

=== Step 6 : Confirm Telemetry Streaming ===
If telemetry streaming is active:
* The telemetry LED on the device will blink, indicating the system is transmitting telemetry to Podium.
* This indicates the system is transmitting telemetry to Podium.
=== Viewing Live Telemetry ===
==== Podium Website ====

[[File:Viewing Live Telemetry podium website.gif|750px]]

* Open the Podium website.
* Navigate to Events.
* Locate the automatically generated live event for your device.
* Open the event to view live telemetry data.
* You should see real-time channel updates such as:
** IMU motion
** G-forces
** Sensor values

==== Podium App ====

The Podium app provides a richer telemetry viewing experience.

# Open the Podium app.
# Navigate to Events > Live Events.
# Select your device.

From here you can:
* View live dashboards
* Switch dashboard views
* Monitor individual telemetry channels

Dashboards can be:
* Selected from built-in presets
* Custom created and saved
* Shared by the community

=== Track Detection and Lap Timing ===

For automatic lap timing, ensure your track is added in Podium.
# Navigate to Racetracks.
# Add the tracks where you typically race.
When the system detects a known track, Podium will automatically enable:
* Lap timing
* Lap-based telemetry analysis
This allows session data to be viewed and analyzed in the context of laps.

=Comprehensive Setup Guide=
==Data System Cable Connection==
Podium Connect Micro supports two types of cable connection systems for data integration:

===Pigtail for MoTeC, ECUmaster, VBox or Others===
The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input on the Podium Connect Micro.
[[file:M8_4P_male_pinout.jpg|200px]]

''Male connector pictured''

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}

'''Note:''' It is recommended to use the same power source as your data system

===AIM Standard Cable===
For AIM data systems, Podium Connect Micro includes a pre-made integration cable with a Binder 5-pin to M8 connector, enabling seamless CAN bus communication.

==Connecting to Your Data System==
===Required CAN Channels for Telemetry===
At a minimum, Podium Connect Micro requires the following data channels from your data system:
* '''Speed :''' Configured with 2 digits of precision in the CAN mapping (e.g., 33.24 kph)
* '''Latitude :''' Configured as decimal degrees of Latitude, with 6 digits of precision in the CAN mapping
* '''Longitude :''' Configured as decimal degrees of Longitude, with 6 digits of precision in the CAN mapping

'''Note:''' These channel names must be defined exactly as shown above in your CAN bus mapping. This minimum data enables
PodiumConnect to calculate lap timing, which forms the context for analyzing additional telemetry such as temperature, throttle position (TPS), RPM, oil pressure, and more.

'''Important:''' Without these channels, telemetry will not function correctly. Do not rename the default channels provided in the system presets.

==CAN Bus Configuration==
===Baud Rate, Termination===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that Termination is enabled if PodiumConnect is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

==CAN Channel Mapping Guide==
RaceCapture provides presetted channel mappings for supported data systems.
* During the First Time Setup Wizard, you can select your data system (e.g., AIM SmartyCam, MoTec etc), which automatically includes the required channels such as Speed, Latitude, Longitude, and additional default channels may also be included.
* You can verify or customize these mappings by going to the CAN Channel Mappings section under Setup in the RaceCapture app. From there, you can view active channels, edit channel parameters or remove unused channels.
'''Note :''' [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN bus integration guide]

[[File:CAN Channel Mapping2.gif]]
===Lua Scripting and Virtual Channels===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting LUA SCRIPTING GUIDE] for detailed instructions and examples.

===Driver ID and Heart Rate Sensor Setup===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your PodiumConnect/Micro system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
* After all devices are registered, press the Write button to save the configuration.

'''Note:''' Only power on one device during each registration to avoid incorrect pairing.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 

==Telemetry and Logging Setup==
===Enabling WiFi Telemetry===
* Navigate to Setup > Wireless in the RaceCapture app.
* Enable WiFi Telemetry to allow the device to stream live data over your wireless network.
[[File:Wi-Fi telemetry.png]]
[[File:Enabling WiFi Telemetry.png|640px]]

===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details

===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
PodiumConnect/Micro logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.

'''Note:''' This process only deletes log files and cache data; it does not affect system configuration or firmware.
[[File:Racecapture app format flash storage.jpg|720px]]

== Bluetooth Connectivity ==
PodiumConnect Micro support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the PodiumConnect Micro
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the PodiumConnect Micro is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== Tire Pressure Monitoring System (TPMS) ==
PodiumConnect Micro support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

=== System Overview ===

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

=== Supported Features ===
* PodiumConnect Micro support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

=== Registering TPMS Sensors ===
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=Real-Time Podium Features=

==Setting Up Podium App==
===Create Device and Streaming Key===
* Create an account on [https://podium.live/ Podium].
* Open the Settings section and Add the name for your device.
* Once your device is created, a Streaming ID will be generated. Make a note of this ID, so you can enter it into the RaceCapture wizard later.
[[File:Streaming ID.jpg|640px]]

==Downloading and Installing the Podium App==
The Podium App is available for Windows, macOS, Android, and iOS platforms. You can find the download links on the Podium Software Page.
===Windows/OSX===
* Get the latest version of the Podium app from the [https://podium.live/software DOWNLOADS PAGE].
[[File:Windows Download.png]]
* Download the .exe file for Windows.
* Run the setup wizard and follow the on-screen instructions to complete the installation.
[[File:Installing on Window.png]]
* Once installed, Connect your Podium Connect Micro to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.

===Android/iOS===
* Get the latest version of the RaceCapture app from the following.
[[Image:google_play.jpg|link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]][[Image:itunes_app_store.jpg|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]][[Image:amazon_app_store.jpg|link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

* Power up Podium Connect Micro with 12v or via USB power (computer or USB power source)
* Go to your device's WiFi settings, and connect to the Podium Connect Micro WiFi access point.
* Note that the WiFi Access Point is open, with no password - you can set a password and encryption later under Setup.
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.

==Live Data Streaming==
* Once the system setup is complete, live data is streamed in real time to Podium Live, the Podium app, and the RaceCapture dashboard.
* You can customize the streaming channels by navigating to the RaceCapture app > Setup > Channels, where you can enable or disable the data you wish to broadcast.
[[File:Live Data Streaming.gif]]

==Predictive Lap Timing==
* ● Podium Connect Micro offers a Predictive Lap Timing feature, which estimates your current lap time before it’s completed.
* To enable this, navigate to the Race Timing screen and turn on Predictive Timing Mode.
* More info: [https://wiki.autosportlabs.com/RaceCapturePro2_Enable_Predictive_Timing#Predictive_Lap_timing_mode Predictive Lap Timing]

==Driver Coaching Tools==
'''Need more information'''

==Monitoring Engine Vitals==
Podium Connect Micro allows real-time monitoring of critical engine parameters such as RPM, oil pressure, coolant temperature, TPS, and more. These values can be displayed live on dashboards and logged for post-session review. Custom alerts can also be configured for vital thresholds.
[[File:Monitoring Engine Vitals.gif]]

==Endurance Strategy Tools==
With Podium’s advanced endurance strategy tools (available with the Pro subscription), you can accurately monitor fuel consumption and optimize your lap timing to execute perfectly timed pit stops. Eliminate the risk of last-minute fuel stops and stay ahead with strategic precision that maximizes your chances of victory.

=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your Podium Connect Micro system to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to Podium Connect Micro using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest Podium Connect Micro firmware from http://podium.live/software
* Unzip the archive to a location on your computer
* Connect Podium Connect Micro via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the Podium Connect Micro firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Data System Integration Guides=
Use the provided integration cable and connect it to your data system. Follow the guide for your specific system:
* [https://wiki.autosportlabs.com/PodiumConnect_AIM AIM SMARTY CAM]
* [https://wiki.autosportlabs.com/PodiumConnect_MoTeC MOTEC]
* [https://www.autosportlabs.com/racelogic-vbox-support-for-podiumconnect/ RACELOGIC VBOX]
* [https://wiki.autosportlabs.com/PodiumConnect_AEM_CD7_VDM AEM CD-7 WITH VDM]
* [https://wiki.autosportlabs.com/PodiumConnect_RaceTechnology RACE TECHNOLOGY]

=Troubleshooting and Diagnostics=
==LED and Status Indicators==
[[File:LED & Status Indicator.jpg]]

The device features multiple LED indicators on the front panel, each representing a specific system status. These indicators provide quick visual feedback for monitoring device functionality and diagnostics.

* '''Power Icon :''' Indicates system power is on.
* '''Error Indicator – Triangle with Exclamation Mark :''' Signals an error, such as a Lua script failure or a local logging error.
* '''Telemetry Indicator – Cloud with Arrow :''' Shows that telemetry is actively broadcasting.
* '''CAN Bus Activity – Two Arrows (⇄) :''' Shows ongoing CAN bus communication, confirming data exchange with connected systems.

'''Note:''' The top-mounted button is also equipped with an integrated LED. This button will flash to indicate active data logging.
=Technical Specifications=
{| class="wikitable"
! colspan="2" | Analog Inputs
|-
| Channels || 1 (Battery Voltage, Internally connected 0–20V)
|-
! colspan="2" | CAN Bus
|-
| CAN Channels || 1
|-
| CAN Baud Rate || 125K, 250K, 500K, 1M Baud
|-
| Protocol Support || OBDII PID, custom CAN mapping
|-
| CAN Bus || CAN 2.0 compatible
|-
| CAN Termination || Software controlled
|-
| CAN Channels Supported || 100
|-
! colspan="2" | Telemetry Connection
|-
| WiFi || Connect to your provided hotspot (cellular or satellite)
|-
| Max Telemetry Sample Rate || 10Hz (1 / 5 / 10Hz supported)
|-
! colspan="2" | Wireless
|-
| WiFi Standard || 802.11b/g/n
|-
| WiFi Modes || Access Point, Infrastructure
|-
| Max Sample Rate (Dashboard) || 50Hz
|-
! colspan="2" | Storage
|-
| Onboard SD || Minimum 2GB
|-
| Max Sample Rate to SD || 100Hz
|-
| Predictive Lap Timing || Built-in
|-
| Track Mapping || Circuit and point-to-point
|-
| Track Maps || Built-in database for auto-detection
|-
| Sectors per Track || 20
|-
| Analysis || Local via RaceCapture app and online with Podium
|-
| Export Data Format || Plain CSV
|-
! colspan="2" | Scripting / Customization
|-
| Virtual/Math Channels || Real-time via onboard Lua scripting
|-
| Virtual Channels Supported || 100
|-
! colspan="2" | Physical
|-
| Dimensions || 94 x 61 x 16 mm (3.7 x 2.4 x 0.63 in)
|-
| Temperature Range || 0 to 65°C
|-
| Environmental Protection || IP65 rated
|-
| Weight || 100g (3.6 oz)
|-
| Connections || M8 Connector, 4 pins (CAN1 and power)
|-
| Power Consumption (Max) || 0.6W
|}

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:PodiumConnect_Micro_Solid.zip]]

==Dimensions==
Dimensions of main body, not including cable: 94 x 61 x 16 mm (3.7 x 2.4 x 0.63 in)

=Additional Tutorials and How-To Guides=
==Guides==

* [[RaceCaptureLoggingData|Logging Data]]
* [[AIM_Integration_CAN_Mapping|AIM Integration guide using CAN Mapping]]
* [[RaceCapture_real_time_telemetry|Real-time Telemetry guide]]
*[[RaceCapturePro_Lua_Scripting|Lua scripting guide]]
*[[RaceCapturePro_Lua_Scripting_Examples|Lua script examples]]
*[[RaceCapturePro2_GoProWiFi|GoPro control guide]]
*[[RaceCapture_troubleshooting|General troubleshooting guide]]
*[[RaceCapture_DashWare_Guide|Creating video with RCP data overlay using DashWare]]
*[[RaceCapture_RaceRender_Guide|Exporting to RaceRender guide]]
*[[Podium_Driver_Data_Analysis|Data Analysis in Podium to become a faster driver]]
*[[RaceCapture_Dashboard_Tablet_Automation|Automating Tablets/Phones for use as Dashboards Guide]]
*[[Add_TPMS_Data|Add TPMS data for $225]]

==How To==
*[[RaceCapturePro2_Enable_Predictive_Timing|How to: enable Predictive Timing]]
*[[Podium_Live_Gauges|How to control which gauges show up on Podium.live]]
*[[RaceCapture-Pro_MK3#RaceCapture_App_Tour|How to: Use Race Capture App]] (some features are specific to Race Capture Pro)
*[[RaceTracks|How to: Submit a new race track]]
*[[RaceCapturePro2_OBD2|How to: enable OBD2 channels]]
*[[RaceCapturePro_How_To_Update_Firmware|How to update firmware]]
*[[Add_Video_To_Podium|How to add video to Podium.live]]
*[[RaceCapturePro_FAQ|More FAQs and How-To's]]
*[https://www.youtube.com/watch?v=jAgFQ9k6VIw&list=PLZdfZf8eVujn2VSIXR5I-PPQSYS25xW5j How To Videos]

How To Update Firmware

2026-07-21T00:30:54Z

Brentp: /* Alternative method via config file */

=Firmware upgrade steps=
Applies to:
* RaceCapture/Pro MK4, MK3, and MK2
* RaceCapture/Apex
* PodiumConnect MK2 and MK1
* RaceCapture/Track MK4, MK3, MK2, and MK1
* PodiumConnect/Micro

* How to video: [https://www.youtube.com/watch?v=LAFb-EeiXy8 Video: How to update firmware for RaceCapture/Pro]

==Save your configuration==

WARNING: Updating firmware will reset the default config on a major and minor release. Bugfix releases do not reset configuration.
Version scheme: MAJOR.MINOR.BUGFIX

If in doubt, be sure to save your configuration using the RaceCapture app.

==Download the firmware==

Download the firmware matching your hardware version from the [http://podium.live/software downloads section]

* '''Note''' Ensure you download the correct firmware for your device (matching the product name), or the firmware process will fail to complete.

==Flash the firmware==
Connect your system to your computer using the USB cable and connect to it with the app.
* '''Note:''' Flashing is only possible via the USB interface, so you must use the desktop version of the RaceCapture app.

===Steps===

=Updating Firmware=
* Unzip the firmware your downloaded to a location on your computer.
* Connect your system to your Windows or OSX computer using the included USB cable.
* Run the RaceCapture app, and confirm that it is connected.
* Navigate to the '''Setup''' view
* Save your current configuration. '''The firmware upgrade may reset your RaceCapture device to a factory default'''.
** Press '''Read''' to read the current configuration and then press '''Save''' to save it to a file.
* Select the Firmware section in the left menu.
** '''Note:''' - If the RaceCapture app cannot read the configuration, you may need to first '''Open a previously saved configuration''' so you can access the firmware page.
* Press the '''Update Firmware''' Button
* Browse to the unzipped firmware from the first step. Select the file ending with ".ihex" or ".bin" - and press '''Open'''
* The firmware will begin updating - watch for the progress to go 0-100%.
* Restore your saved configuration by pressing the '''Open''' button, selecting your saved configuration, and then '''Write''' it to your system.
* Confirm your firmware is updated by viewing the firmware version in the upper right corner of the RaceCapture app, after connecting.

* If there is a problem detecting the system after firmware upgrade, unplug/replug your device and restart the app.

===Alternative method via config file===
* While holding down the button on the device, power it up by plugging in to USB.
* You should observe a rapidly flashing LED on the unit: this means it's in bootloader mode.
* Start the app. '''Note, it will not be able to connect - this is expected.'''
* Navigate to Setup.
* Load a previously saved configuration file '''for that device (Important)'''.
* Navigate to the firmware update view, then follow the process to update firmware.

===Forcing a factory reset via firmware===
Flashing a different minor version of the firmware will trigger the system to perform a factory reset. This will help address the case when the system 'stuck' and cannot normally connect.

Steps:
Follow the steps [[#Alternative method via config file]], but when choosing the firmware file to load, pick a firmware version that is older by the minor version.

Example minor version:

Current firmware version: 1.2.3
Flash this firmware: 1.1.3

After the firmware has completed flashing, you can flash the latest firmware again, using the regular procedure.

===Issues===
* If the firmware fails part way through, you can retry the firmware upgrade.
** Start the app
** Connect your device via USB
** Load a previously saved config file (file ending in .rcp)
** Navigate to Setup / Firmware
** Attempt the firmware upgrade process again.

=RaceCapture/Pro MK1=

Unzip the Firmware download into a folder and follow the directions in HOW_TO_FLASH.txt

Note: if you have problems getting the firmware to flash (it cannot find RaceCapture/Pro while in bootloader mode), try the following:

* Hold down the front panel button on RCP right at the beginning of the process, before running flashRCP.bat
* When asked 'is this your first time flashing' say 'No' so it will re-install the bootloader drivers
* Then proceed with the firmware flash update.

Alternatively:

Try installing the bootloader drivers while the hardware is plugged in to USB in bootloader mode (hold down logging button on RaceCapture/Pro, plug in to USB, then release button) outside of running flashRCP.bat. Then, check Windows Device Manager for the Presence of Autosport Labs bootloader while plugged in. Once you you see it show up, you can proceed with the firmware update process.

==Mac Users==
For Mac users with RaceCapture/Pro MK1 you will need to use a Windows VM to connect to RCP. Free virtual machine images are available here: http://dev.modern.ie/tools/vms/ You will need to add a network adapter to the VM. After that follow the Windows instructions.

Video plus data streaming with racecapture

2026-06-06T18:40:03Z

Brentp: /* Experimental */

=Introduction=
This guide shows you how to add video+data livestreaming to your existing RaceCapture system.

After following this guide, you will have:
* 2-camera video with picture-in-picture
* Rich, realtime graphics overlay
* Broadcast to youtube or your preferred streaming provider via an in-vehicle cellular hotspot
* Local video recording

=System Overview=
Video+data streaming is enabled by using a separate streaming/encoding device. As RaceCapture supports multiple simultaneous connections, an existing dashboard can be retained.
[[image:RaceCapture video+data livestreaming system diagram.png]]

==Cost==
The cost for adding video+data livestreaming to your RaceCapture system can range '''between 0 and 800 USD''', depending on the parts you may already have on hand.

==How hard is it to setup?==
'''This project requires following instructions and knowledge of Linux''', including:
* Installing an operating system
* Typing computer commands
* Plugging in cables
* Editing configuration files
* Selecting options in an application

This ability is within the realm of someone with '''good computer and Linux skills'''. If the instructions seem daunting, find someone to help you along.

* For those who crave convenience, we will also be offering a pre-packaged setup that take care of most of the setup steps.

==Production State==
Since it is based on existing RaceCapture technology (RaceCapture hardware and RaceCapture app), the core of the system is very stable.

New components that add video rendering, encoding, and streaming will be improved through your testing feedback and rounds of updates.

As of this writing, several existing RaceCapture users have put the system through it's paces with great results.

So far we were very pleased with the stability and performance, and we will continue to improve the system through software updates.

===A demonstration===
Here's the Session from the inaugural test (with sub optimal camera exposure settings and low quality microphone)

<youtube>zVUJwnGoCnI&t=2990s</youtube>

===Experimental===
While we consider this '''experimental''' - it is also a free software upgrade for a system that was never originally designed for this purpose.

The system requires Linux expertise and a great deal of configuration at the command line - it is polished and it is not plug and play. Expect problems and periodic troubleshooting.

However with effort and patience you can create a a high performance system that rivals solutions costing upwards of $5000 USD.

=Parts you will need=
==Your existing RaceCapture system==
The RaceCapture system will provide access to your car's sensor data (CAN bus or analog sensors), high performance GPS, Accelerometer / Gyro sensors, lap timing and other motorsport related statistics.
===Compatible Systems===
* Any current or previous RaceCapture or PodiumConnect system will work.
[[image:racecapture_pro_mk4_connectors_1024.jpg|520px]]
[[Image:PodiumConnect_MK2_3quarter_1024.jpg|270px]]
[[Image:rct_mk3_3quarter.jpg|300px]]

==Rendering/Streaming computer==
A tiny form-factor computer is used to receive data from RaceCapture and is responsible for video+data overlay, encoding, and broadcasting the video to youtube or similar streaming platform.
===Recommended===
* [https://www.amazon.com/gp/product/B0BCVCZDH3 Beelink SER5]
The Beelink SER5 is our recommended choice as it is powerful, cost effective, and provided in a compact and lightweight form factor.

[[image:beelink_ser5_micro_pc.jpg|500px]]

===Alternatives===
A micro system with an Intel I5-6500 through I5-7600 + SSD + 8GB RAM is an acceptable option as well. This may be a system you already have or a surplus system you can get at minimum cost.
* Look for these options:
** SSD (required for ruggedness - smallest size is fine).
** Smallest RAM option is fine (typically 8GB)
** Included WiFi - for connection versatility
====Candidates====
* Dell Optiplex 7050 micro desktop: [https://www.ebay.com/sch/i.html?_nkw=Dell+Optiplex+7050+Micro+Desktop+Computer&_sacat=0 Ebay search] (nice because most have wifi)
[[image:dell-optiplex-7050.jpg|510px]]
* HP EliteDesk 800 G3 Mini: [https://www.ebay.com/sch/i.html?_nkw=HP+EliteDesk+800+G3+Desktop+Mini&_sacat=0 Ebay search]
[[image:HP-elitedesk-800.jpg|550px]]

==12v DC to DC converter==
A 12v-19v DC to DC converter is needed to power the rendering/broadcasting computer in the vehicle. This converter avoids needing an AC inverter in the car, making for a clean installation.
* '''Tips''':
** Choose a device that has sufficient power capacity (100W minimum)
===Recommended===
These have been tested to work:
* [https://www.amazon.com/gp/product/B07TT2F95L KFD 100W universal car charger]
[[image:KFD-100W-DC-to-DC-converter-12v-to-19v.jpg|500px]]
* '''Tips''':
** We recommend cutting the cigar lighter connection and hard-wiring the power to a 15A circuit. (center conductor is positive).

==Cameras==
You will need 1 or 2 cameras for capturing and rendering video.
===Recommended Camera Kit===
Autosport Labs will soon provide a camera kit that provides high quality imaging, a compact and ruggedized IP65 form-factor, and the perfect 110 degree field of view.

[[image:RaceCapture_video+data_livestreaming_windshield_mount.jpg|600px]]

[[image:RaceCapture_video+data_livestreaming_gopro_camera_mount.jpg|600px]]

===Assembling the Camera Kit===
Using the supplied hardware, insert the nut into the camera clamp using a pair of small pliers. Then, use the included screw to clamp the camera to the mount.

[[image:RaceCapture_video+data_livestreaming_gopro_camera_mount_clamp_insert_nut.jpg|600px]]

[[image:RaceCapture_video+data_livestreaming_gopro_camera_mount_clamp_screw_attached.jpg|600px]]

Then, assemble the camera clamp into ball and socket windshield mount, or the GoPro mount. (1 of each style is included in the kit)

====Ball and Socket windshield mount====
[[image:RaceCapture_video+data_livestreaming_gopro_camera_mount_clamp_ball_and_socket_mount.jpg|600px]]

[[image:RaceCapture_video+data_livestreaming_gopro_camera_mount_clamp_ball_and_socket_mount_assembled.jpg|600px]]

====GoPro style mount====
[[image:RaceCapture_video+data_livestreaming_gopro_camera_mount.jpg|600px]]

===Alternatives===
Most any USB camera (such as a webcam) can be used. These are commonly found on [https://www.amazon.com/s?k=usb+webcam Amazon] or [https://www.ebay.com/sch/i.html?_nkw=usb+webcam&_sacat=0 Ebay].
* '''Tips''':
** Logitech is a good, high quality option
** Find a camera that offers a 1/4-20 threaded camera mount for a secure rollbar attachment to minimize vibration.

==Microphone==
A microphone is needed for capturing audio.
* Candidates:
** USB microphone - you can use a separate USB microphone, especially if you get one that offers higher quality.
** Analog microphone - you can use an analog microphone that attaches to the front headset input of the micro PC. Make sure you get a microphone that has the 4-ring connector for proper operation.
** Microphone embedded in one of the cameras - if one of your your cameras has its own microphone, you can use that as an audio source.

===Using the Microphone included with the kit===
The kit provides a USB microphone with good audio quality.
[[image:RaceCapture_video+data_livestreaming_microphone.jpg|600px]]

==Display Emulator==
You'll need a display emulator to plug into the streamer while running on track. This tricks the computer into thinking a monitor is attached, allowing the streamer to run.

[[image:hdmi_display_emulator.jpg|300px]]

The following have been tested:
* [https://www.amazon.com/gp/product/B06XSY9THQ HDMI emulator] - use this for the Beelink Micro PC
* [https://www.amazon.com/gp/product/B075PTQ4NH DisplayPort emulator] - use this for the HP or Dell Micro PCs

==Hotspot/Router==
Most any hostspot should work, but for the best performance and reliability, these options should be considered:
* Hard-wired ethernet connection, for direct connection to the micro computer.
* External antenna connection - a hotspot that offers external antenna will boost performance by allowing you to use a high-gain roof-mount antenna.

Suggested units that offer direct hardwired connection:
* [https://www.amazon.com/NETGEAR-Broadband-Modem-LM1300-Always/dp/B0BKTSMQFF Netgear LM1300]
* [https://www.amazon.com/Teltonika-RUT950-LTE-4G-Router/dp/B00TKFKLCI Teltonika RUT950]
* [https://www.amazon.com/Peplink-Pepwave-Cellular-Router-MAX-BR1-MINI-LTE-US-T/dp/B01MR5YKF9 Pepwave BR1]

=Setup=
Connect a keyboard, mouse, and monitor to the rendering/streaming computer and prepare to install Ubuntu:
==Install ubuntu 22 LTS==
[https://ubuntu.com/download/desktop/thank-you?version=22.04.2&architecture=amd64 Download Ubuntu Desktop] and follow the instructions to install to a USB flash drive.
* '''Notes''' To install, you will need to configure the system's BIOS to boot first from the USB flash drive.
** Beelink: Repeatedly press 'delete' on the keyboard right after power up.
** HP: Repeatedly press F10 after power up
** Dell: Repeatedly press F2 after power up

===OS configuration options===
* '''Important -''' Install Ubuntu with the following options
** During installation, choose the option to download / install updates, including "third-party software for graphics, WiFi, and additional media formats"
** Choose the option to erase the hard drive and perform a complete install.
** Select Login Automatically
** When prompted for your account's username, make sure you specify a password. This will allow you to easily switch between streaming mode and maintenance mode.

[[image:ubunut_setup_options.jpg]]

After the installation is complete, the computer will reboot into the standard desktop.

==Disable keyring popup==
From the desktop: log out, and log back in using with the password you created during the installation step.

Then, [https://linuxconfig.org/how-to-disable-keyring-popup-on-ubuntu Disable the keyring popup] using these instructions. Observe the security notes in this guide.
* '''Notes'''
** The log-out/log-in step is important - don't skip it!
** Disabling the keyring is important; it prevents a popup dialog when the RaceCapture app automatically starts.

==Run the installer==
From the Ubuntu desktop, open a terminal and enter the following commands, pressing <enter> after each line:
<pre>
sudo apt install curl
curl -sL bit.ly/3RL9Yoj | bash
</pre>

This will automatically install the RaceCapture app and video streamer, related software dependencies, and set up configuration file templates.

==Reboot==
Reboot the computer once it is complete with the installation. It should automatically launch the RaceCapture app.

==Edit RaceCapture settings==
Edit these RaceCapture settings for proper operation when streaming
===App Preferences===
Navigate to Setup / App Preferences:
* set Fullscreen -> ON
* Set Startup Screen -> Dashboard
* Turn off Session Recording
[[image:racecapture-video-data-livestreaming-app-settings.jpg]]

===Dashboard Preferences===
Navigate to the Dashboard, then press the gear icon in the upper right of the dashboard, select "More Settings" and set the following:
* Turn off Pit stop timer
* Turn off pit-to-car alerts
* Turn off remote dashboard navigation (scroll to bottom)
[[image:racecapture-video-data-livestreaming-dashboard-settings.jpg]]

[[image:racecapture-video-data-livestreaming-disable-remote-dashboard-navigation.jpg]]

==Plug in camera(s)==
Plug in 1 or 2 cameras into the USB port

* '''Note:''' Remember the ports the cameras are plugged into, and keep this consistent during use.

==Plug in USB microphone==
* Plug USB microphone into a USB port.

Note: if using the Beelink, plug into one of the USB ports on the rear of the system.

==Connect RaceCapture==
Your current RaceCapture system already supports multiple connections, so you can continue using your dashboard (e.g. Android tablet via Bluetooth) when adding this video+data streaming capability.
===Via USB (overall best option)===
This is the best option for connecting RaceCapture to the streaming computer. Just connect a USB cable between the rendering/streaming system and RaceCapture. RaceCapture will automatically connect.
===Via WiFi===
If you're already using the USB connection for a Raspberry Pi dash, you can configure the rendering/streaming system to connect to RaceCapture via WiFi.
====Configure as Client====
If you are already using WiFi to connect the rendering/streaming system to your hotspot, you will need to configure RaceCapture to connect to the same hotspot via the WiFi client settings. In this configuration, everything shares the same network created by the hotspot.
* '''Note''': Due to system limitations, your hotspot must be up and running before RaceCapture attempts to connect to it via WiFi.
====Access Point connection (best WiFi option)====
If you are connecting the rendering/streaming system to the hotspot via ethernet, then you can connect the rendering/streaming system directly to RaceCapture's WiFi Access Point. The system will receive data from RaceCapture via WiFi, and broadcast the video+data stream to the hotspot via ethernet.

==Configure dashboard video options==
* Press Settings Gear Icon, go to More Settings / Camera Preferences

Select /dev/video0 for Camera #1, and /dev/video2 for Camera #2

[[image:racecapture-video-data-livestreaming-camera-settings.jpg]]

==Create a test dashboard==
* Press the Settings gear icon, select Add Gauge
* create a video gauge, and select Camera 1 as the source.
* Resize to fit the dashboard.
* create another video gauge, and select Camera 2 as the source.
* Resize to be the picture-in-picture video window.
* Add additional gauges as you see fit, such as an analog speed gauge, track map, etc.

* '''Note''' If the cameras are reversed, you can swap the camera mappings in the main dashboard settings under More Settings / Camera Preferences

Editing the dashboard is very easy - see this demo for an example:

<youtube>r4mxA-fhJn0</youtube>

==Exiting the RaceCapture app==
To get back to the regular Ubuntu desktop, press ctrl-t, type :quit and press <enter>.

At the login screen, select your username and press the small gear icon in the lower right to select the Ubuntu desktop.

To switch back to streaming mode, log out, press the small gear icon in the lower right and select the RaceCapture streaming option. Log in, and you will be streaming again.
* '''Note''': The system will persist the last option you pick - so if you reboot or power cycle, it will automatically enter streaming mode.

=Video Streaming / recording=
To configure your streaming settings, switch back to the regular Ubuntu Desktop.

Then, edit the video-config.ini - you'll find the file on the desktop. Edit this with the standard text editor by double-clicking it.

==Example default video-config.ini file==
<pre>
[capture]
# specify the id number of the audio device, or the name of the audio
# device as reported by arecord -l
audio_device=USB Audio Device

[local_recording]
video_dir=$HOME/Videos
segment_length_sec=60

[streaming]
# replace <your-streaming-key> with the actual key provided by youtube
streaming_url=rtmp://a.rtmp.youtube.com/live2/<your-streaming-key>

# bitrate in kbps
bitrate=4500
</pre>

==Video Streaming==
===Streaming Key / URL===
If using Youtube: Set the streaming key as provided by youtube. Or, you can specify a custom URL.

===Bitrate===
Specified in kbps. Specify a lower number to conserve bandwidth, at the cost of quality.

<pre>
[streaming]
# replace <your-streaming-key> with the actual key provided by youtube
streaming_url=rtmp://a.rtmp.youtube.com/live2/<your-streaming-key>
bitrate=4500
</pre>

* '''Note''': Typical numbers are 2000 - 6000

==Local recording==
If video_dir is set and points to a valid directory, local video recording will also be enabled.

Videos for the current session are stored in a timestamped directory name under the configured video directory. Videos are saved as fixed-length segments to protect against file corruption due to sudden power loss, similar to how dashcams operate.

If the system experiences sudden power loss, the video currently being written to will be corrupt and unreadable. Therefore, it is important to keep the video segment length reasonably short.

After the session is complete, a full video can be made by using commonly available software to assemble all of the files.

<pre>
[local_recording]
video_dir=$HOME/Videos
segment_length_sec=60
</pre>

===Notes===
* Configure video_dir to the location where you want to save your video files.
* Configure segment_length_sec for the desired segment length size. If not specified, the default is 60 seconds '''Note, keep this value reasonably short''' - sudden power loss will result in corruption in the last written file.

==Microphone==
We recommend using a USB microphone.
Edit the video-config.ini to specify the microphone device you are using.

===Specifying microphone by device name (recommended)===

To configure your USB microphone by device name, open a terminal window on the streamer and issue this command:

<pre>
arecord -l
</pre>

Example output (yours may be different)

<pre>
streamer@streamer:~/logs$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: Generic_1 [HD-Audio Generic], device 0: ALC897 Analog [ALC897 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 2: ALC897 Alt Analog [ALC897 Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: acp [acp], device 0: DMIC capture dmic-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
</pre>

In this case, the USB microphone is named '''USB PnP Sound Device''' - so the video-config.ini can be updated as follows:

<pre>
[capture]
audio_device=USB PnP Sound Device
</pre>

* '''Note''': the default video-config.ini is pre-configured as '''USB PnP Sound Device''', which matches the USB microphone we provide in our pre-made kits.

===Specifying microphone by device ID (alternative, not recommended)===

You can also specify the numeric ID of the audio device. In the above example, the ID is 3

<pre>
[capture]
audio_device=3
</pre>

* '''Note''': This is not normally recommended because the order of the USB IDs may change every time the streamer boots up.

=First Test=
Once your streaming key has been set and saved, log out and log back into the streamer by selecting the RaceCapture streaming mode on the login page using the gear icon in the lower right.

Check your youtube livestream to see if you are receiving video. If not, try restarting the system and let the streamer launch cleanly after a fresh reboot.

=Maintenance/Troubleshooting=
==Open a terminal window==
(advanced mode) You can open a terminal window while RaceCapture is streaming by entering the following command.
* Press ctrl+t, then type c, then press <enter>

The screen will split into two equal windows; the new window will be a terminal where you can perform debugging steps, such as viewing log files, etc.

* '''Note''': The more user-friendly alternative is to just log out and log back in to the Ubuntu desktop.

==Log out==
You can log out of the current session to access the original Ubuntu desktop to perform additional maintenance.
* Press ctrl-t, then type :quit, then press <enter>

Once you've logged out, you can log back into the Ubuntu desktop by pressing the gear icon in the lower right, and select Ubuntu.

To get back to the RaceCapture full-screen app mode, select "RaceCapture livestreaming" from this menu; this is the window manager that is configured to run RaceCapture in full-screen mode.

==Inspecting Logfiles==
Log files are located in the logs directory under the user's home directory. Log files are named with the date they were created.
===Video streamer log file===
The log files for the video streamer agent have information about the video streamer's connection and activity. You can open it to see any helpful error messages regarding streaming.
===RaceCapture log file===
The RaceCapture log file will have potentially useful information for debugging the operation of the RaceCapture app.

=Extras=
==Mount for Beelink micro PC==

We have designed a cage-style mount for the Beelink Micro PC. This allows convenient surface mounting of the PC.
* Download STL file for 3D printing: [[file:Beelink_SER5_mount.zip]]

[[image:beelink_cage_mount.jpg]]

BMW E36 Guide

2026-06-02T17:44:45Z

Brentp: /* Connecting to the first Pulse/RPM input of the system */

=BMW E36 (1990 - 1999)=
[[Image:e36_race_car.jpg|500px]]

==RPM==
Use the wire connected to the instrument cluster #20, black wire. Also available on the round diagnostic connector at the back of the engine compartment (black wire, Pin #1)
===RaceCapture/Pro Timer RPM Configuration===
* Timer Mode: RPM
* Timer Speed: Medium
* Pulse Per Revolution: 3

===Connecting to the first Pulse/RPM input of the system===
* Connect the sensor pigtail to Port P2 of the 4 way splitter, then connect the splitter to the "A" branch of the 8-4 splitter
* Configure the first channel at the top of the list for Pulse/RPM Sensors in the RaceCapture app

[[image:BMW_E36_RPM_timer_configuration.jpg|800px]]

==TPS==

Pin 2 (Black/Brown wire) of the Throttle Position Sensor is the voltage reference. Connect this wire to an analog input on your RaceCapture system.

Typical voltage values. You may need to measure this on your engine:
* 0.62 volts at 0% throttle
* 4.64 volts at 100%

Configure a linear mapping in the analog input where the first bin is 0.62 volts / 0 scaled value; 2nd bin is 4.64 volts / 100 scaled value. Repeat the 2nd bin values for bins 3, 4 and 5.

==Engine Temperature==
''In research''

Should be similar to [[BMW_E30_Guide#Engine_Temperature|E30]]

==Fuel Level==
* [http://www.bimmerforums.com/forum/showthread.php?1718687-Stock-fuel-level-sender-output-V-wiring-Integration-to-AIM-MXL Forum discussion]
*[https://www.facebook.com/groups/1041375552601984/permalink/1041384422601097/ Facebook Discussion]

Tap the brown/yellow wire that is in the small connector on the back of the dash closest to
the driver's door.

'''Note''': This assumes the factory gauge is still connected.

Mapping in the analog channel
*0.2v = 0 (empty)
*1.33v = 25 (1/4)
*2.2v = 50 (half)
*2.95v = 75 (3/4)
*3.53v = 100 (full)

[[file:BMW_E36_fuel_level_curve.png]]

==Brakes==
*Tap the Blue/Red wire coming out of the brake light switch on the back of the brake pedal. Wire this to a digital GPIO input of RaceCapture. Note: Must use a 10k Ohm resistor between the GPIO input and brake light wire.

*Can be helpful to know when the driver actually applies the brakes for data analysis of the driver. This gives you a simple yes/no of whether the driver is on the brakes. Lets you know exactly when they applied the brakes. Use this in conjunction with TPS to see how much time they are 'coasting', or how long it takes them to transition from throttle to brakes and vice versa.

==Oil Pressure==
Recommend a dedicated 10 bar / 145 PSI 0.5-4.5v pressure sensor. [https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/ Pressure Sensor]

==OBDII==
You can get a few channels from the OBDII port of the E36 using the [https://www.autosportlabs.com/product/obdii-legacy-adapter/ ASL Legacy OBDII Cable], but it is fairly slow to update. Useful channels are RPM, EngineTemp, and TPS. See the [[RaceCapturePro2_OBD2|Enabling OBD-II Guide]]. It is also possible to [[RaceCapturePro_Lua_Scripting_Examples#Display_OBDII_Codes_as_a_channel_and_allow_driver_to_reset_the_OBDII_Codes_with_a_button|read and clear OBDII trouble/diagnostic codes via Lua Script]].

Available Sensors:
*RPM
*EngineTemp
*TPS
*IAT (needs to be converted to F)
*WheelSpeed (needs to be converted to MPH)
*MAF
*EngineLoad
*FuelFlowRate
*Timing

==Road speed (differential speed sensor based)==

This calculates gear and speed based on the differential speed sensor.

Assumes:
* Engine RPM is connected to the first timer input.
* Differential speed pulse is connected to the 2nd timer input

The differential speed signal is on a black w/ white stripe wire and can be found in the following location:
* Pin 2 on connector X17 to the back of the gauge cluster
* Pin 10 on connector X22 on the cruise control module behind the glove box
* Pin 10 on radio connector

<pre>
setTickRate(10) --10Hz

--virtual channels
--addChannel("name",SR,prec,min,max,"unit")
speeddiff_id = addChannel("Speed_",10,0,0,160,"MPH")
gear_id = addChannel("Gear_",5,0,0,5,"gear")

--global constants
--edit these to match your car
first = 4.20
second = 2.49
third = 1.66
fourth = 1.24
fifth = 1.00
final = 3.46
tirediameter = 24.7

--global variables
rpm = 0
rpm_diff = 0
speed = 0

function updateSpeedDiff()
rpm_diff = getTimerRpm(1)
speed = rpm_diff*tirediameter*0.002975
speed = speed + 0.5 -- round because 0 prec. truncates
setChannel(speeddiff_id, speed)
end

function updateGear()
rpm = getTimerRpm(0)
local gearErr = 0.15
local gear = 0

if speed > 2 then
ratio = rpm/(rpm_diff*final)
if ((first - ratio)^2) < (gearErr^2) then gear = 1 end
if ((second - ratio)^2) < (gearErr^2) then gear = 2 end
if ((third - ratio)^2) < (gearErr^2) then gear = 3 end
if ((fourth - ratio)^2) < (gearErr^2) then gear = 4 end
if ((fifth - ratio)^2) < (gearErr^2) then gear = 5 end
end
setChannel(gear_id, gear)
end

function onTick()
updateSpeedDiff()
updateGear()
end
</pre>

=External Reference=
* [http://www.scribd.com/doc/247124381/1998-BMW-E36-Electrical-Wiring-Diagram#scribd BMW E36 Wiring Diagram]
* [http://wedophones.com/Manuals/BMW/1996%20BMW%20318is-c%20-%20320i%20-%20325i-c%20-%20328i-c%20%20Electrical%20Troubleshooting%20Manual.pdf Wiring Troubleshooting Manual]

BMW E36 Guide

2026-06-02T17:43:38Z

Brentp: /* RaceCapture/Pro Timer RPM Configuration */

=BMW E36 (1990 - 1999)=
[[Image:e36_race_car.jpg|500px]]

==RPM==
Use the wire connected to the instrument cluster #20, black wire. Also available on the round diagnostic connector at the back of the engine compartment (black wire, Pin #1)
===RaceCapture/Pro Timer RPM Configuration===
* Timer Mode: RPM
* Timer Speed: Medium
* Pulse Per Revolution: 3

===Connecting to the first Pulse/RPM input of the system===
* Connect the sensor pigtail to Port P2 of the 4 way splitter, and then the "A" branch of the 8-4 splitter
* Configure the first channel at the top of the list for Pulse/RPM Sensors in the RaceCapture app

[[image:BMW_E36_RPM_timer_configuration.jpg|800px]]

==TPS==

Pin 2 (Black/Brown wire) of the Throttle Position Sensor is the voltage reference. Connect this wire to an analog input on your RaceCapture system.

Typical voltage values. You may need to measure this on your engine:
* 0.62 volts at 0% throttle
* 4.64 volts at 100%

Configure a linear mapping in the analog input where the first bin is 0.62 volts / 0 scaled value; 2nd bin is 4.64 volts / 100 scaled value. Repeat the 2nd bin values for bins 3, 4 and 5.

==Engine Temperature==
''In research''

Should be similar to [[BMW_E30_Guide#Engine_Temperature|E30]]

==Fuel Level==
* [http://www.bimmerforums.com/forum/showthread.php?1718687-Stock-fuel-level-sender-output-V-wiring-Integration-to-AIM-MXL Forum discussion]
*[https://www.facebook.com/groups/1041375552601984/permalink/1041384422601097/ Facebook Discussion]

Tap the brown/yellow wire that is in the small connector on the back of the dash closest to
the driver's door.

'''Note''': This assumes the factory gauge is still connected.

Mapping in the analog channel
*0.2v = 0 (empty)
*1.33v = 25 (1/4)
*2.2v = 50 (half)
*2.95v = 75 (3/4)
*3.53v = 100 (full)

[[file:BMW_E36_fuel_level_curve.png]]

==Brakes==
*Tap the Blue/Red wire coming out of the brake light switch on the back of the brake pedal. Wire this to a digital GPIO input of RaceCapture. Note: Must use a 10k Ohm resistor between the GPIO input and brake light wire.

*Can be helpful to know when the driver actually applies the brakes for data analysis of the driver. This gives you a simple yes/no of whether the driver is on the brakes. Lets you know exactly when they applied the brakes. Use this in conjunction with TPS to see how much time they are 'coasting', or how long it takes them to transition from throttle to brakes and vice versa.

==Oil Pressure==
Recommend a dedicated 10 bar / 145 PSI 0.5-4.5v pressure sensor. [https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/ Pressure Sensor]

==OBDII==
You can get a few channels from the OBDII port of the E36 using the [https://www.autosportlabs.com/product/obdii-legacy-adapter/ ASL Legacy OBDII Cable], but it is fairly slow to update. Useful channels are RPM, EngineTemp, and TPS. See the [[RaceCapturePro2_OBD2|Enabling OBD-II Guide]]. It is also possible to [[RaceCapturePro_Lua_Scripting_Examples#Display_OBDII_Codes_as_a_channel_and_allow_driver_to_reset_the_OBDII_Codes_with_a_button|read and clear OBDII trouble/diagnostic codes via Lua Script]].

Available Sensors:
*RPM
*EngineTemp
*TPS
*IAT (needs to be converted to F)
*WheelSpeed (needs to be converted to MPH)
*MAF
*EngineLoad
*FuelFlowRate
*Timing

==Road speed (differential speed sensor based)==

This calculates gear and speed based on the differential speed sensor.

Assumes:
* Engine RPM is connected to the first timer input.
* Differential speed pulse is connected to the 2nd timer input

The differential speed signal is on a black w/ white stripe wire and can be found in the following location:
* Pin 2 on connector X17 to the back of the gauge cluster
* Pin 10 on connector X22 on the cruise control module behind the glove box
* Pin 10 on radio connector

<pre>
setTickRate(10) --10Hz

--virtual channels
--addChannel("name",SR,prec,min,max,"unit")
speeddiff_id = addChannel("Speed_",10,0,0,160,"MPH")
gear_id = addChannel("Gear_",5,0,0,5,"gear")

--global constants
--edit these to match your car
first = 4.20
second = 2.49
third = 1.66
fourth = 1.24
fifth = 1.00
final = 3.46
tirediameter = 24.7

--global variables
rpm = 0
rpm_diff = 0
speed = 0

function updateSpeedDiff()
rpm_diff = getTimerRpm(1)
speed = rpm_diff*tirediameter*0.002975
speed = speed + 0.5 -- round because 0 prec. truncates
setChannel(speeddiff_id, speed)
end

function updateGear()
rpm = getTimerRpm(0)
local gearErr = 0.15
local gear = 0

if speed > 2 then
ratio = rpm/(rpm_diff*final)
if ((first - ratio)^2) < (gearErr^2) then gear = 1 end
if ((second - ratio)^2) < (gearErr^2) then gear = 2 end
if ((third - ratio)^2) < (gearErr^2) then gear = 3 end
if ((fourth - ratio)^2) < (gearErr^2) then gear = 4 end
if ((fifth - ratio)^2) < (gearErr^2) then gear = 5 end
end
setChannel(gear_id, gear)
end

function onTick()
updateSpeedDiff()
updateGear()
end
</pre>

=External Reference=
* [http://www.scribd.com/doc/247124381/1998-BMW-E36-Electrical-Wiring-Diagram#scribd BMW E36 Wiring Diagram]
* [http://wedophones.com/Manuals/BMW/1996%20BMW%20318is-c%20-%20320i%20-%20325i-c%20-%20328i-c%20%20Electrical%20Troubleshooting%20Manual.pdf Wiring Troubleshooting Manual]

File:BMW E36 RPM timer configuration.jpg

2026-06-02T17:40:55Z

Brentp:

How To Update Firmware

2026-06-02T13:24:36Z

Brentp: /* Alternative method via config file */

=Firmware upgrade steps=
Applies to:
* RaceCapture/Pro MK4, MK3, and MK2
* RaceCapture/Apex
* PodiumConnect MK2 and MK1
* RaceCapture/Track MK4, MK3, MK2, and MK1
* PodiumConnect/Micro

* How to video: [https://www.youtube.com/watch?v=LAFb-EeiXy8 Video: How to update firmware for RaceCapture/Pro]

==Save your configuration==

WARNING: Updating firmware will reset the default config on a major and minor release. Bugfix releases do not reset configuration.
Version scheme: MAJOR.MINOR.BUGFIX

If in doubt, be sure to save your configuration using the RaceCapture app.

==Download the firmware==

Download the firmware matching your hardware version from the [http://podium.live/software downloads section]

* '''Note''' Ensure you download the correct firmware for your device (matching the product name), or the firmware process will fail to complete.

==Flash the firmware==
Connect your system to your computer using the USB cable and connect to it with the app.
* '''Note:''' Flashing is only possible via the USB interface, so you must use the desktop version of the RaceCapture app.

===Steps===

=Updating Firmware=
* Unzip the firmware your downloaded to a location on your computer.
* Connect your system to your Windows or OSX computer using the included USB cable.
* Run the RaceCapture app, and confirm that it is connected.
* Navigate to the '''Setup''' view
* Save your current configuration. '''The firmware upgrade may reset your RaceCapture device to a factory default'''.
** Press '''Read''' to read the current configuration and then press '''Save''' to save it to a file.
* Select the Firmware section in the left menu.
** '''Note:''' - If the RaceCapture app cannot read the configuration, you may need to first '''Open a previously saved configuration''' so you can access the firmware page.
* Press the '''Update Firmware''' Button
* Browse to the unzipped firmware from the first step. Select the file ending with ".ihex" or ".bin" - and press '''Open'''
* The firmware will begin updating - watch for the progress to go 0-100%.
* Restore your saved configuration by pressing the '''Open''' button, selecting your saved configuration, and then '''Write''' it to your system.
* Confirm your firmware is updated by viewing the firmware version in the upper right corner of the RaceCapture app, after connecting.

* If there is a problem detecting the system after firmware upgrade, unplug/replug your device and restart the app.

===Alternative method via config file===
* While holding down the button on the device, power it up by plugging in to USB.
* You should observe a rapidly flashing LED on the unit: this means it's in bootloader mode.
* Start the app. Note, it will not be able to connect - this is expected.
* Navigate to Setup.
* Load a previously saved configuration file '''for that device (Important)'''.
* Navigate to the firmware update view, then follow the process to update firmware.

===Forcing a factory reset via firmware===
Flashing a different minor version of the firmware will trigger the system to perform a factory reset. This will help address the case when the system 'stuck' and cannot normally connect.

Steps:
Follow the steps [[#Alternative method via config file]], but when choosing the firmware file to load, pick a firmware version that is older by the minor version.

Example minor version:

Current firmware version: 1.2.3
Flash this firmware: 1.1.3

After the firmware has completed flashing, you can flash the latest firmware again, using the regular procedure.

===Issues===
* If the firmware fails part way through, you can retry the firmware upgrade.
** Start the app
** Connect your device via USB
** Load a previously saved config file (file ending in .rcp)
** Navigate to Setup / Firmware
** Attempt the firmware upgrade process again.

=RaceCapture/Pro MK1=

Unzip the Firmware download into a folder and follow the directions in HOW_TO_FLASH.txt

Note: if you have problems getting the firmware to flash (it cannot find RaceCapture/Pro while in bootloader mode), try the following:

* Hold down the front panel button on RCP right at the beginning of the process, before running flashRCP.bat
* When asked 'is this your first time flashing' say 'No' so it will re-install the bootloader drivers
* Then proceed with the firmware flash update.

Alternatively:

Try installing the bootloader drivers while the hardware is plugged in to USB in bootloader mode (hold down logging button on RaceCapture/Pro, plug in to USB, then release button) outside of running flashRCP.bat. Then, check Windows Device Manager for the Presence of Autosport Labs bootloader while plugged in. Once you you see it show up, you can proceed with the firmware update process.

==Mac Users==
For Mac users with RaceCapture/Pro MK1 you will need to use a Windows VM to connect to RCP. Free virtual machine images are available here: http://dev.modern.ie/tools/vms/ You will need to add a network adapter to the VM. After that follow the Windows instructions.

TireX

2026-05-29T00:40:27Z

Brentp: /* Mounting Orientation */

=Introduction=
TireX is a powerful and versatile multi-zone tire temperature sensor designed for motorsports applications.
 
[[file:tirex_3quarter.jpg|600px]]

==Features==
===High Performance===
TireX can be configured to report up to 16 temperature zones, supporting sample rates up to 64Hz via CAN bus with the powerful embedded 32 bit processor.
===Rugged and Compact===
TireX features a rugged, low profile design with a wide field of view for space constrained environments.
===Flexible Setup===
* Temperature zones and sensor calibration is customizable by the end user
* Sensor position can be assigned to provide consistent data reporting between left and right sides of vehicle.
* CAN bus can be set for 1MB or 500K (default is 1MB)

=Quick Setup Guide=
The following setup assumes you have the following:
* RaceCapture system
* Plug and play wiring harness
* Powered CAN hub kit
* RaceCapture to hub integration cable

==Hardware Setup==
===TireX 4-corner plug and play harness===
We recommend using the TireX 4-corner plug and play harness for the easiest installation. 
https://www.autosportlabs.com/product/tirex-4-corner-plug-and-play-harness/

[[image:TireX_plug_and_play_harness_assembled_with_sensors_cropped.jpg|1024px]]
 
[[image:TireX_plug_and_play_harness_closeup_2_sensors_connected_top_view.jpg|400px]]
[[image:TireX_plug_and_play_harness_closeup_2_sensors_connected_end_view.jpg|400px]]

===By System===
===For newer plug and play RaceCapture and PodiumConnect systems===
You have two plug and play options for connecting the TireX harness:
====Use the Dual CAN splitter====
For a minimal installation, use the Dual CAN splitter 
https://www.autosportlabs.com/product/can1-can2-dual-can-splitter/ 
This splitter connects to the dual CAN port of your system, and TireX connects to the CAN2 ("B" connection) branch on the splitter.

[[image:ASL_DUAL_CAN_SPLITTER.jpg]]

===For older generation RaceCapture systems with RJ45 connector===
====Plug and Play option====
Get the 8 port hub and dual CAN link cable -> RJ45 
https://www.autosportlabs.com/product/powered-8-port-dual-can-bus-hub-kit/ 
https://www.autosportlabs.com/product/racecapture-rj45-to-dual-can-bus-link-cable/ 
The cable plugs into the RJ45 port of your RaceCapture/Pro, and then plugs into the hub. Then, the TireX harness plugs into the hub.
====Minimal installation (requires some custom wiring)====
Get the Device CAN pigtail 
https://www.autosportlabs.com/product/can-power-pigtail-for-device/ 
This will plug into the TireX harness, and then on the pigtail side you will connect it to CAN2 on your system (molex or RJ45 port) and then connect it to the same 12v power used for your system.

===For other data systems===
Get the Device CAN pigtail.
https://www.autosportlabs.com/product/can-power-pigtail-for-device/ 
This will plug into the TireX harness, and then on the pigtail side you will connect it to your system's CAN bus and 12v, on the same circuit powering your data system.
==TireX Connection==
=== Connect Each TireX Sensor to the Wiring Harness ===

To maintain proper CAN bus signal integrity, connect the sensors in a daisy-chain configuration. Install the inline CAN terminator at the final sensor in the chain.

⚠️ Do not create star or branch connections. The CAN network must remain a single continuous chain.

==== Routing ====

Begin at the male connector end of the plug-and-play harness (data system connection) and route the harness in sequence around the vehicle.

Recommended cable segments:

* Data system → Sensor 1 (first corner, front or rear): 3 m cable
* Sensor 1 → Sensor 2 (opposite side of same axle): 3 m cable
* Sensor 2 → Sensor 3 (same side, opposite axle): 4 m cable
* Sensor 3 → Sensor 4 (final corner): 3 m cable — install inline terminator here

==== Example Layout (Data System Mounted Near Center of Vehicle) ====
* Route a 3 m segment to the left-front corner and connect the sensor using the Y-splitter.
* Route a 3 m segment across to the right-front corner and connect the sensor.
* Route a 4 m segment to the right-rear corner and connect the sensor.
* Route a 3 m segment to the left-rear corner and connect the final sensor.
* Install the inline CAN terminator at this last sensor.

[[image:TireX_plug_and_play_harness_assembled_with_sensors_cropped.jpg|500px]]

==Software Setup==
https://i.imgur.com/rDiKXpC.gif

===Enable CAN bus and set CAN2 to 1MB===
Connect the RaceCapture app to your RaceCapture system.

* Go to Setup/CAN bus and ensure the CAN bus is turned '''ON'''
* Ensure CAN2 is set to 1M Baud

===Enable the TireX CAN mapping===
* Go to '''Setup/CAN mapping'''

* Ensure CAN Channels are set to '''ON'''

* Press the Presets button, then select the TireX 4 zone preset.
** '''Note''' - you may need to press the cloud update button to fetch the newest presets.

===Write the settings back to your RaceCapture System===
* Press the '''Write''' button to write your new settings to the system.

===Ensure RaceCapture / TireX is powered by 12v===
* Ensure the TireX sensor(s) are receiving 12v power. If powered via RaceCapture via the plug and play harness, ensure RaceCapture is powered with 12v.

* '''Note''': USB power is insufficient for powering the CAN bus network.

===Verify the TireX data on the dashboard===
====Using the overview gauge====
* Switch to the RaceCapture dashboard mode.
* Create a new Dashboard screen by pressing the gear icon in the upper right of the screen.
* Select the TireX test dashboard preset
** '''Note''' - you may need to press the cloud update button to fetch the newest presets.

====Using the raw channels view====
* Navigate to the Raw Channels view of the dashboard by pressing the left or right arrows on the dashboard screen.

* You can observe all of the available telemetry channels, including the individual channels for the TireX sensors.

=Specifications=
''Specifications are preliminary and subject to change''
{| class="wikitable" | width="600px"
|-
! Feature
! Description
|-
| Sensor type
| Thermal array
|-
| Sensor Resolution
| 16 x 12 (196 pixels)
|-
| Object temperature range
| 0 - 127.5C (tire temperature mode (factory default)) / 0 - 255C (full frame mode)
|-
| Field of view
| 110 x 75 degrees
|-
| Accuracy
| 1C
|-
| Temperature zones (tire)
| 1 / 2 / 4 (factory default) / 8 / 16
|-
| Sample rate
| 0.5 - 64Hz (Tire temperature mode, 16Hz factory default) 0.5 - 10Hz (Full frame mode)
|-
| Processing Engine
| 32 bit
|-
| Configurable positions
| 4 (Left-Front (factory default), Right-Front, Left-Rear, Right-Rear); Reversible orientation
|-
| Emissivity
| Configurable (0.95 default)
|-
| Ambient temperature compensation
| Automatic (adjustable offset)
|-
! Electrical
!
|-
| Interface
| CAN 2.0
|-
| Supply voltage
| 6 - 14v (automotive power)
|-
| Power
| 200mW
|-
| Harness
| M8 4P Male, 250mm length
|-
! CAN bus
!
|-
| CAN baud rate
| 500K and 1M, jumper configurable (1M default)
|-
| Address space
| 4 separate address spaces (configurable via jumper)
|-
| Termination
| No Termination (configurable via jumper)
|-
|-
! Physical / Environmental
!
|-
| Construction
| CNC aluminum
|-
| Dimensions
| 64 x 46 x 12.5mm
|-
| Weight
| 10 grams
|-
| Operating temperature
| -40 - 85C
|-
| IP rating
| IP65
|}

=Dimensions / Mounting=
[[image:TireX_dimensions.png]]

==Mounting Orientation==
We recommend mounting TireX above the tire, with the cable pointing towards the rear of the vehicle.

* '''Note:''' Mounting above the tire is especially ideal for the front tires, as this will minimize errors during turning. However, you can clock the mounting point so the sensor is mounted at the front or rear of the wheel well; just ensure the orientation remains the same.
[[Image:tirex_mounting_orientation.jpg]]

==Mounting Distance==
TireX has a wide aspect ratio of 110 degrees, so you can use some trigonometry to calculate the distance. Here are some examples:

* 205 width = 71mm
* 225 width = 79mm
* 235 width = 82mm
* 245 width = 85mm
* 255 width = 89mm
* 275 width = 96mm
* 315 width = 110mm

[https://www.triangle-calculator.com/?what=iso&a=C%3D110%2C+c%3D245&submit=Solve Here's a convenient online calculator]

Tip: you can mount TireX at a further distance if you use the middle channels. Example:

* if only using 8 channel, you can mount 2x the distance
* If only using 16 channels, you can mount 4x the distance

* '''Note:''' 4 channels is often the resolution of choice to reduce the bulk of data generated, and gives perfectly adequate results for determining tire performance.

=Electrical / CAN connection=
* Connection is provided by a standard industrial M8 4P male plug. [[Harness_specifications#Power_.2B_CAN_Single_interconnect|Pigtails and connectors are available from Autosport Labs, or 3rd parties]]
* TireX is designed to connect to regular automotive 12-14v per our [[Harness_specifications#Power_.2B_CAN_Single_interconnect|Standard Power interconnect]]

 
[[image:M8_4P_male.png]]
{| class="wikitable" | width="600px"
|-
! Pin
! Connecton
! Wire Color
|-
| Pin 1
| CAN Low
| Brown
|-
| Pin 2
| Voltage supply (6-14v)
| White
|-
| Pin 3
| CAN High
| Blue
|-
| Pin 4
| Ground
| Black
|}

== CAN termination ==
By default, TireX is not terminated. We recommend using the external termination adapter, connected inline on the last sensor of the chain.

[[image:autosport_labs_inline_can_terminator.jpg]]

This terminator is [https://www.autosportlabs.com/product/inline-can-terminator/ available separately] or [https://www.autosportlabs.com/product/tirex-4-corner-plug-and-play-harness/ included with the TireX plug and play harness].

=== Customizing Termination ===
CAN termination can be enabled on TireX by disassembling the sensor and closing the jumper on the TireX circuit board.

[[image:tirex_jumpers_can_termination.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

=Zone Configuration=
===Up to 16 configurable temperature zones===
TireX can be configured to report up to 16 temperature zones across the sensor's entire field of vision.

When configured for 2 or more zones, temperature for zones are reported in the order of inside through outside edge.

{| class="wikitable" | width="600px"
|-
! Zones
! Coverage
|-
| 1
| Averaged across the entire field of vision
|-
| 2
| Each zone averaged across 1/2 the field of vision
|-
| 4
| Each zone averaged across 1/4 the field of vision
|-
| 8
| Each zone averaged across 1/8 the field of vision
|}
===Reversible orientation based on sensor position===
TireX zones are reversed based on the configured sensor position (left vs right side) to allow identical physical sensor mounting orientation between sides.
[[file:TireX_zones.jpg|800px]]

=CAN bus protocol=

==CAN protocol files==
DBC File for standard 4 corner, 4 zone configuration: [[file:TireX_standard.dbc.zip]]

==Overview==
The CAN bus API provides the configuration, control and sensor broadcast interface for TireX

==Conventions==
===Formula===
* Conversion formulas are expressed as converting the CAN encoded value to real-world value.

* Example:
** Encoded value in CAN message: 95
** Formula: A / 100
** Real-world value: 0.95

===Data encoding===
====Endian====
16 and 32 bit values are encoded as little endian.

====Single and mulit-byte values====
{| class="wikitable" | width="600px"
|-
! Value
! Symbol Reference
|-
| 8 Bit values
| A
|-
| 16 bit values
| A (low byte) / B (high byte)
|-
| 32 Bit values
| A (low byte) / B / C / D (high byte)
|}

==CAN Baud rate==

1M and 500K rates are supported.

1M is enabled by default; cut the jumper labeled '''BAUD''' on the bottom of TireX to enable 500K rate.

[[image:tirex_jumpers_can_term.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

==CAN base ID==

A configured TireX sensor will have a CAN base address that is a combination of the '''Main Base ID''' + '''Position Offset''' based on the installed position of the sensor on the vehicle. This combination creates a final '''Sensor Base ID'''.

All broadcast and configuration CAN messages is offset from the final calculated '''Sensor Base ID'''.

===Default Main Base ID===
Default Main CAN base ID is '''0xA100 (41216)'''

====Adjusting Main Base ID====
The base address is determined by the state of the '''ADR1''' and '''ADR2''' jumpers. By default, the jumpers are closed (bridged); the jumper can be opened by cutting the trace between the pads. To re-close the jumper, add a small amount of solder to bridge the gap between the pads you want to close.
* '''Note:''' In the vast majority of the cases you can use the default Main Base ID of 0xA100.

[[image:tirex_jumpers_base_id.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

{| class="wikitable" | width="600px"
|-
! ADR2 Jumper
! ADR1 Jumper
! Address
|-
| Closed
| Closed
| 0xA100 (41216)
|-
| Closed
| Open
| 0xB100 (45312)
|-
| Open
| Closed
| 0xC100 (49408)
|-
| Open
| Open
| 0xD100 (53504)
|}
* Opening the jumper ADR1 will add (0x1000) 4096 to the base ID
* Opening the jumper ADR2 will add (0x2000) 8192 to the base ID
* Opening both jumpers ADR1 and ADR2 will add (0x3000) 12288 to the base ID.

==Sensor Position Offset==
The sensor position will offset the '''Main Base ID''' by the position of the sensor as defined in the table, to set the final '''Sensor Base ID'''.

{| class="wikitable" | width="600px"
|-
! Position ID
! Sensor Position
! Offset
|-
| 0
| Left-Front
| 0x0 (0)
|-
| 1
| Right-Front
| 0x100 (256)
|-
| 2
| Left-Rear
| 0x200 (512)
|-
| 3
| Right-Rear
| 0x300 (768)
|}

===Example: default base address (0xA100)===
{| class="wikitable" | width="600px"
|-
! Sensor Position
! Final Sensor Base ID
|-
| Left-Front
| 0xA100
|-
| Right-Front
| 0xA200
|-
| Left-Rear
| 0xA300
|-
| Right-Rear
| 0xA400
|}

* '''Note:''' Single sensor kits are configured as left-front tire position. This can be changed by sending the appropriate configuration message.

==CAN Messages==
The announcement message is broadcast by TireX once per second for 10 seconds upon power up.

===Announcement===
'''CAN ID:''' Sensor Base ID + 0

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sample Rate
| unsigned
| A * 1
| 0.5 - 64Hz (0 = 0.5Hz)
|-
| 1
| Temperature Zones
| unsigned
| A * 1
| Number of configured temperature zones (1 / 2 / 4 / 8 / 16) (factory default is 4)
|-
| 2
| Sensor Position
| Unsigned
| A * 1
| Configured sensor position (0=Left-Front / 1=Right-Front / 2=Left-Rear / 3=Right-Rear)
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Major Version
| unsigned
| A * 1
| Firmware Major Version Number
|-
| 6
| Minor Version
| unsigned
| A * 1
| Firmware Minor Version Number
|-
| 7
| Patch Version
| unsigned
| A * 1
| Firmware Patch version number
|}

===Statistics===

Broadcast by TireX every 10 seconds.

'''CAN ID:''' Sensor Base ID + 2

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sensor Ambient Temperature
| unsigned
| A * 1
| 0 - 255C
|-
| 1
| Reserved
|
|
|
|-
| 2
| Reserved
|
|
|
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Major Version
| unsigned
| A * 1
| Firmware Major Version Number
|-
| 6
| Minor Version
| unsigned
| A * 1
| Firmware Minor Version Number
|-
| 7
| Patch Version
| unsigned
| A * 1
| Firmware Patch version number
|}

===Configuration Preferences===

This message is broadcasted to TireX to configure the sensor's preferences. The settings are persisted in TireX's flash memory.

'''CAN ID:''' Sensor Base ID + 3

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - TireX will reply with the current configuration.

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sample Rate
| unsigned
| A * 1
| Rate to report sensor values ( 0.5 - 64Hz) Valid sample rates: 0 (0.5Hz) / 1 (1Hz) / 2 (2Hz) / 4 (4Hz) / 8 (8Hz) / 16 (16Hz) / 32 (32Hz) / 64 (64Hz). Specifying an invalid value will select the default value of 16
|-
| 1
| Temperature zones
| unsigned
| A * 1
| Number of temperature zones. Valid zones: 1 / 2 / 4 / 8 / 16. Specifying an invalid value will select the default value of 4.
|-
| 2
| Sensor Position
| unsigned
| A * 1
| Location of the sensor on the vehicle. This position adjusts the '''Sensor Base ID'''. Valid Positions 0 (Left-Front) / 1 (Right-Front) / 2 (Left-Rear) / 3 (Right-Rear). Specifying an invalid value will select the default value of 0 (Left-Front). '''Note:''' The sensor position affects the orientation of the sensor zones. Sensor Position 1 and 3 will report temperature zones left - right; Position 0 and 2 will report temperature zones right - left. 
'''Note''': When in full frame mode, this setting is ignored.
|-
| 3
| Frame mode
| unsigned
| A * 1
| 0 = Standard (Tire Temperature) mode; 1 = Full Frame mode
|-
| 4
| Reserved
|
|
|
|-
| 5
| Reserved
|
|
|
|-
| 6
| Reserved
|
|
|
|-
| 7
| Reserved
|
|
|
|}

===Calibration Preferences===

This message is broadcasted to TireX to configure the sensor's calibration. The settings are persisted in TireX's flash memory.

'''TireX is calibrated at the factory and normally these values will not need to be changed.'''

'''CAN ID:''' Sensor Base ID + 4

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - TireX will reply with the current configuration.

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Emissivity
| unsigned
| A / 100
| Emissivity of the target. Default is 0.95
|-
| 1
| Ambient temperature compensation
| unsigned
| A * 1
| Value in C. Default is 2
|-
| 2
| Sensor Resolution
| unsigned
| 16-19
| Sensor ADC resolution, in bits. Default is 18
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Reserved
|
|
|
|-
| 6
| Reserved
|
|
|
|-
| 7
| Reserved
|
|
|
|}

===Sensor Temperature Value Broadcast===
The following messages will contain the temperature values based on the number of temperature zones configured, broadcast at the currently configured sample rate.

* '''Note:''' The sensor position affects the orientation of the sensor zones:
** Position 1 and 3 will report temperature zones left - right;
** Position 0 and 2 will report temperature zones right - left.
====1 Zone====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====2 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====4 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====8 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 5 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 6 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 7 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 8 value
| unsigned
| A / 2
| 0 - 127.5C
|}
====16 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 5 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 6 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 7 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 8 value
| unsigned
| A / 2
| 0 - 127.5C
|}

'''CAN ID:''' Sensor Base ID + 0x21 (33)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 9 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 10 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 11 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 12 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 13 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 14 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 15 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 16 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====Full Frame Mode====
'''CAN ID:''' Sensor Base ID + 0x40 (64)

* '''Note:''' Pixels increment linearly by row x column

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Pixel 0 value
| unsigned
| A
| 0 - 255C
|-
| ...
| ...
| ...
| ...
| ...
|-
| 191
| Pixel 191 value
| unsigned
| A
| 0 - 255C
|}
= Hardware configuration =
Hardware defaults can be altered by disassembling TireX and adjusting jumpers on the bottom of the circuit board.

* To break a jumper: scrape the space between the jumper pads using a sharp tool, such as a razor blade or very small screwdriver.
* To re-close a jumper: use a fine tip soldering iron and add solder between the jumper pads.

[[image:tirex_jumper_settings.png|500px]]

When re-assembling the sensor, ensure the sensor and enclosure seals are correctly seated, and torque the enclosure screws evenly.

= Disassembly and replacing harness =
In the event the TireX pigtail is damaged, it can be replaced by the end user relatively easily.

Disassembly steps:
* Use a small screwdriver to remove the 4 outer screws.
* Remove the black gasket, and set aside
* Gently pry away the old harness from the notch of the enclosure
* Remove the circuit board by pressing the sensor from the outside of the enclosure.
* Remove the red seal around the sensor, and set aside.
* Using a small flat bladed screwdriver, '''carefully''' unplug the the harness from the circuit board. Gently pry away the harness connection from each side until it pops out of the connector.

Re-assembly steps:
* Re-insert the red sensor seal into the back of the main enclosure, so that it is installed and flush with the outside of the enclosure
* Plug the new harness into the circuit board. The connector mounts only one direction, and it should press in with just finger pressure. Ensure it is fully seated.
* Locate the cable notch on the enclosure. Press the harness into this notch, centered on the thick section near the end of the harness, close to the PCB connector. You may use finger / thumb pressure, or gently with a pair of cushioned pliers to prevent marring the enclosure. (you can wrap tape around the jaws of the pliers). Press it in until it is fully inserted into the notch.
* Press the PCB into the enclosure, focusing on pressing the sensor into the red seal.
* Inspect the opposite side of the enclosure, ensuring the sensor is properly seated into the seal, and no edges are caught.
* On the PCB, ensure the silicone pad is still mounted opposite of the sensor.
* Re-attach the black gasket onto the back lid of the enclosure, making sure the notch in the gasket matches the relief made in the lid to allow cable exit.
* Mount the back lid of onto the main body of the enclosure, ensuring the black gasket is properly inserted into the enclosure, with no pinching or caught edges. The stepped design of the gasket is designed to sure the back lid is perfectly centered. '''Ensure the cable relief of the bottom lid is installed in the direction where the cable exits'''
* Re-attach the 4 screws, torquing evenly until there is slight compression of the gasket.
* Test for proper operation before re-attaching it to the vehicle.
*

ESP32-CAN-X2

2026-04-29T00:52:42Z

Brentp: /* 3D printed enclosure */

=Introduction=

ESP32-CAN-X2 is an automotive-grade ESP32-based development board specifically designed for CAN communication. This board has all the features of a modern ESP32 development board, integrated Wi-Fi and Bluetooth, along with the extended CAN controller. Autosport Labs has specifically designed it for CAN communication in harsh automotive and industrial environment, while offering fast processing and computation options.

This is a complete how-to-use guide and this user guide will describe each and every step to use the board and harness the maximum potential of the board.

[[File:ESP32_CAN_X2_revD_3quarter.jpg|700px]]

=Purchasing=
You can order the ESP32-CAN-X2 from our online store:
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Features=

Features of ESP32-CAN-X2 development board:

* Flexible power supply options up to 40V, suitable for automotive and industrial applications
* Based on ESP32-S3-WROOM-1-N8R8 microcontroller powerful dual-core Xtensa LX6 CPU running at up to 240 MHz.
* 384 KB ROM, 512 KB SRAM, 16 KB SRAM in RTC, 8 MB PSRAM
* Two LED’s: Power LED and user-defined LED1
* Integrated Wi-Fi (802.11b/g/n) and Bluetooth capabilities
* Reset and Boot push button
* USB-C type socket for flashing, and power supply
* Integrated antenna for long-range communication
* Additional CAN communication controller CAN using MCP2515
* Two 4-pin headers are strategically positioned at the top for CAN communication.
* Easy-to-interface programming. Required no external debugger for flashing
* Integrated CAN transceivers
* Configurable CAN termination resistors, which can be disabled via breakable jumpers
* Support of a wide choice of commonly used Integrated Development Environments (IDEs)
* [https://github.com/autosportlabs/ESP32-CAN-X2/ Comprehensive free software libraries] and examples for CAN communication for Arduino and Circuit Python
* Supports a range of stackable [[#Bolt-ons|add-on boards]] offering additional features such as GPS, RGB LEDs, switches, and more.

=Bolt-ons=
Bolt-ons are stackable add-on boards that offer easy extensibility

Make your own bolt on with a blank design template https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/bolt-on-template
===GPS bolt-on===
Adds a high performance GPS receiver 
[[File:GPS Bolt-on image main.png|300px|link=Gps-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/gps-bolt-on/]]
===Button bolt-on===
Adds 4 tactile switches + RGB LEDs 
[[File:Button Bolt-on white background.jpg|300px|link=Button-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/button-bolt-on/]]
===RGB LED bolt-on===
Adds 10 RGB LEDs across two groups for alert indicators 
[[File:RGB LED Bolt-on.jpg|300px|link=RGB-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/rgb-led-bolt-on/]]

=Getting started=

This section will provide you with comprehensive information about the ESP32-CAN-X2 development board's key components, mechanical layout, power rating, & requirements. This detailed information helps you to use the board effectively and efficiently in your projects.

== Key Components of ESP32-CAN-X2 Development Board ==

Figure 1 given below indicates the important key components of the ESP32-CAN-X2 Development Board and their location on the board.

[[File:REV D Images updated.png|Figure 1]]

=== Microcontroller ===

The ESP32-CAN-X2 Development Board is designed around the ESP32-S3-WROOM-1-N8R8 microcontroller in a 40-pin package. The connections between the development board and the microcontroller is straightforward, where the majority of GPIO pins are directly connected with the external headers, SV1 & SV2, and some pins are reserved internal connections between the board and CAN controllers. The internal connections between the microcontroller and CAN controllers are shown in the CAN controller heading given below. The microcontroller pin layout is shown in Figure 2 given below.

[[File:Microcontroller pin layout.png|Figure 2]]

=== External Connection Header ===

External headers, SV1 & SV2, are the two other important components of this development board. SV1 is the left side dual row header and the SV2 is the right side dual row header. Both of these headers have 20 pins available for connection. These headers provide connections for GPIOs, power output, ground (GND), power input, and CAN communication pins. Both of these header pinouts have standard size, allowing users to connect them using jumper wires, a breadboard, or even solder wires permanently onto the development board. However, while doing the wire connection the customer must make sure that none of them get short circuit. The details regarding the pin's names, numbers, outputs, and functions are given in the Board Pinout section below.

=== CAN bus transceivers===

The following are the specifications of the CAN transceivers for CAN1 and CAN2:

'''Detection of Ground Fault'''
* Permanent Dominant Detection on TXD
* Permanent Dominant Detection on Bus
* Power-on Reset and Voltage Brown-Out

'''Protection on V DD Pin'''
* Protection Against Damage Due to Short-Circuit
Conditions (Positive or Negative Battery Voltage)
* Protection Against High-Voltage Transients in

'''Automotive Environments'''
* Automatic Thermal Shutdown Protection
* Suitable for 12V and 24V Systems
* Meets or exceeds stringent automotive design requirements including “Hardware Requirementsfor LIN, CAN and FlexRay Interfaces in Automotive Applications”, Version 1.3, May 2012
• High-Noise Immunity Due to Differential Bus Implementation
• High Electrostatic Discharge (ESD) Protection on CANH and CANL, meeting the IEC61000-4-2 up to ±14 kV

=== CAN Controllers ===

The MCP2515 external connected CAN communication controller, and ESP-32 built-in CAN communication controller are two other main components of this development board.

The MCP2515, operating as the second external CAN controller in this development board, is a specialized component designed for Controller Area Network (CAN) applications. Its features include:

* Implements CAN V2.0B at up to 1 Mb/s.
* High-Speed SPI Interface (10 MHz)
* Interrupt Output Pin with selectable enables
* Multiple receive and transmit buffers
* Low-Power CMOS Technology: - 5 mA active current (typical), 1 μA standby current
 
The internal CAN controller also works at CAN V2.0. The internal CAN supports two message formats:

* Base frame format (11-bit ID)
* Extended frame format (29-bit ID)
 
'''Internal pinout connection between the CAN controllers and ESP32'''

==== CAN 1 ====
This is a built-in CAN controller and its RX is connected to IO6 of the microcontroller and TX is connected to IO7 of the microcontroller. The connections are shown in Figure 3 given below

==== CAN 2 ====
This is the externally connected MCP2515 controller with the following connections:
{| class="wikitable" style="text-align:center; width:60%"
|+ '''MCP2515 ESP32-CAN-X2 GPIO connections'''
! Signal !! ESP32 GPIO
|-
| CS || 10
|-
| CLK || 12
|-
| MISO || 13
|-
| MOSI || 11
|-
| IRQ || 3
|}

Crystal: 16MHz
[[File:CAN Controller Connections ESP32.jpg|Figure 3]]

=== Two 4-Pin header Connector ===

The ESP32-CAN-X2 development board provides two additional 4-pin connector headers at the top of the board to support CAN communication. This header makes wiring the device more convenient and robust. The CAN communication connection pinout details are given in the pinout section below.

=== Built-in LED ===
The built-in blue LED is connected to GPIO2 of the ESP32. For a demo that exercises this LED, see the [https://github.com/autosportlabs/ESP32-CAN-X2/blob/main/arduino/ping_pong/ping_pong.ino#L23 ping-pong example].

=== USB-C Socket ===
The ESP32-CAN-X2 development board has one USB-C port. This port is used for multiple functions: it powers the board, allows programming, and facilitates serial communication both ways.
However, it is important to note that when powering the board through the USB-C port, please ensure the nominal voltage range is 6-20V and Vmax is 40V.

=== Debug Connector ===
The following 6-pin connector marked as X4 is used for serial communication and debugging purposes with ESP32 CAN X2. The 6-pin configurations on the ESP32 CAN X2 is arranged as follows:

[[File:Debug connectors 6 pins.png|Figure 4]]

== Board Layout ==

Mechanical board outline physical dimensions:

* Width : 42.10 mm
* Length : 72 mm
 
The board top view is shown in the Figure 4 given below.

[[File:Board Layout.png|700px]]

== Power Ratings & Environmental Requirements ==

'''Power Options'''

The ESP32-CAN-X2 development board is flexible in its power input, and it provides multiple power input options. Power can either be supplied via the VIN pin, or via USB-C connector. Any voltage input either via USB or VIN is stepped down to 3.3 V via a voltage regulator.

'''Power available to your circuit'''

The onboard regulator can provide power to your devices:
* 1.5A is available on the 5V header pins
* 100mA is available on the 3.3v header pins

'''Pin Voltage'''

All digital & analog pins on the ESP32-CAN-X2 development board are 3.3 V. Do not connect any higher voltage devices to any of the pins as it will risk damaging the board.

'''VIN Rating'''

The nominal input voltage rating for the development board is 6-20v, with a 40v max input. Please do not attempt to power the board with a voltage outside the recommended range.

'''Operating Current'''

The typical operating current of ESP32-CAN-X2 development board is 105mA and maximum operating current is 500mA ( peak, during transmission )

'''Power Consumption'''

The normal power consumption of the board is 330mW and peak power consumption is 1.65W

'''Operating Temperature'''

Temperate rating is -40°C to +85°C

=CAN bus information=

CAN, also known as Control area networking, is a serial communication protocol that is widely used in Automotive applications. CAN bus communication protocol utilizes differential signaling methods in which data is transferred as a voltage difference between High and low voltage. Can Bus communication provides various advantages over other communication methods which makes it the most important communication protocol in automotive. A few features are follows

'''Multimaster system'''

In CAN Bus communication, multiple controllers can act as a master, and multiple devices can act as a node. Each node can share data with other nodes via the CAN bus. In modern cars, there are more than 70 ECUs, and using CAN communication each ECU acts as a node and can transfer the data to the CAN bus, this data is then available to all the ECUs, and ECU can then check the data and decide whether to receive or ignore it.

For details, visit: https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial

'''Lossless communication'''

CAN communication uses a bitwise arbitration method that avoids the contentions of data on the bus. When two nodes simultaneously try to send the data, then the node with the high priority ( lower identifier ) gets priority and continues transmitting. The identifier message can be 11-bit ( standard CAN ) or 29-bit ( extended CAN) in length.

For details, visit: https://dewesoft.com/blog/what-is-can-bus

'''Simple and cheap'''

The CAN communication between the ECUs is done through a single CAN system instead of direct complex analog signal lines which makes it extremely simple and reduces errors.

For details, visit: https://www.autopi.io/blog/can-bus-explained/

'''Errorless communication'''

CAN incorporates different built-in error detection mechanisms including cyclic redundancy checks (CRC), and frame check sequences (FCS) to detect errors during data transmission.

'''CAN network types'''
 
Prominent CAN network types are as follows.

* High-speed CAN bus ( Supports bit rates between 40 kbit/s and 1 Mbit/s )
* Low-Speed CAN bus ( Supports bit rates between 40 kbit/s and 125 kbit/s )
* CAN FD ( Supports bit rates between 1 Mbps to 8 Mbps )
 
For details, visit:https://dewesoft.com/blog/what-is-can-bus

'''Data transmission'''

In CAN, data is transferred between two nodes in messages known as CAN frames. There are four types of CAN frames.
* Data frame ( Used to transfer data between two node )
* Remote frame ( request data from other node )
* Error frame ( report errors )
* Overload frame ( report overload )
 
For details, visit:https://www.autopi.io/blog/can-bus-explained/

== CAN Termination ==

CAN termination is a process of terminating the CAN bus to prevent the signal reflection at the end of the bus and to ensure the correct DC level of the bus. The CAN BUS is bidirectional, and both ends of the bus must be properly terminated to prevent errors in communication. CAN termination is achieved by placing the termination resistance, which is normally 120 ohm, that matches the nominal resistance of the cable. ISO 11898 requires normally required CAN BUS cable of impedance 120 ohm; therefore, the CAN 120 ohm resistance is used for CAN termination. However, while doing the CAN termination, it must be kept in mind that the nodes from the far two ends of the cable only require termination resistors.

Figure 5 given below explain the CAN termination.

[[File:CAN BUS TERMINATION.png]]

Note : The low-speed CAN, single wire CAN, may not require the CAN bus termination.

'''How to enable & disable CAN termination in ESP-32-X2 ?'''

The ESP-32-X2 development board has given two separate CAN termination pads at the back side of the development board. The CAN termination jumpers are shown in figure 6 given below.

[[File:CAN termination.png]]

* Enable termination : In ESP-32-X2 development board, CAN termination is enabled by default.
* Disable termination : Scratch the copper trace between the pads, TERM1 & TERM2.
* Re-enable termination : Re-solder the traces between the pads

Note : Proper termination is necessary for ensuring errorless communication and signal integrity. Please follow the above given instruction carefully.

=Board Pinout=

The ESP32-CAN-X2 board has 40 pins across its two headers, SV1 & SV2 headers, and two 4-pin headers at the top. This guide explains the pin functionalities of the board. The pin configuration of the development board is shown in Figure 7 given below.

[[File:Pin Configuration 1.png|Figure 7]]

'''Left Header (SV1) Pinout (Top to Bottom)'''

The pin count start from the top of the left header, and the pin details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || CAN1H/2.7D || high-level signal for the first CAN channel.
|-
| 2 || CAN1L/2.7D || low-level signal for the first CAN channel
|-
| 3 || CAN2H/2.7C || high-level signal for the second CAN channel
|-
| 4 || CAN2L/2.7C || low-level signal for the second CAN channel
|-
| 5 || RX Pin || USART RX
|-
| 6 || TX Pin || USART TX
|-
| 7-20|| GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
|}

'''Right Header (SV2) Pinout (Bottom to Top )'''

The pin count start from bottom to top and details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1-11 || GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
| 12-13 || 3.3V || 3.3v Voltage Output (can be used to power your custom circuits)
|-
| 14-15 || 5V || 5v Voltage Output (can be used to power your custom circuits)
|-
| 16-18 || GND || Ground
|-
| 19-20 || 12 Vin || 12v voltage Input
|}

==12v note==
Only connect 12v to the 12v voltage input (19-20). To avoid electrical damage, do not connect 12v to any other pin on the board.

==Top Headers Pinout==

The X1 and X2 header supports CAN communication. Pin count starts at the right viewing the board from the top. The pinout configuration of the X1 and X2 header is shown in the figure 8 below:

[[File:Two 4-Pin CAN Connectors.png|Figure 8]]
* '''Note:''' Color codes on the provided pigtail may not match documentation.

The pin description of the X1 header is given in the table below:
{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the first CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the first CAN channel
|-
| 4 || GND || Ground
|}

The pin description of the X2 header is given in the table below:

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the second CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the second CAN channel
|-
| 4 || GND || Ground
|}

=Pigtail for Plug and Play Harness=
A [https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/ pigtail] is available for connector X1 and X2 that can integrate with the [[Harness_specifications|Autosport Labs plug and play harness system]]. This pigtail can provide power + CAN data to the board.

[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/]]

[[file:ESP32_CAN_X2_with_plug_and_play_harness_closeup.jpg|400px]] [[file:ESP32_CAN_X2_with_plug_and_play_harness-scaled.jpg|400px]]

=3D printed enclosure=
You can 3D print your own enclosure: files [https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/enclosures available on Github].

The enclosure is a snap together design with ports for USB and grommets holes for the plug and play harness.

[[file:esp32-can-x2-pigtail-3d-printed-enclosure-cover-off.jpg|400px]]
[[file:esp32-can-x2-pigtail-3d-printed-enclosure-cover-on.jpg|400px]]

=Flashing Firmware=

Firmware flashing in this development board is straightforward. The following components are required for firmware flashings.

'''Hardware Components'''

* USB-C cable
* Computer running Windows, Linux, or macOS
 

'''Software Components'''

* Updated Arduino IDE to compile code for ESP-32-X2.
* Update Mu Editor from codewith.mu
 
Note : Link to download Arduino IDE : https://www.arduino.cc/en/software || Link to download Mu Editor : codewith.mu

== Step by step instruction for Arduino IDE==

===Sample Arduino Project===
https://github.com/autosportlabs/ESP32-CAN-X2

Step-by-step instructions for flashing ESP-32-X2 are as follows.

'''Install ESP-32-X2 Board Support:'''

Adding ESP-32-X2 in Arduino Ide is a single-time process and its steps are as follows.

* Open Arduino Ide
* Go to File > Preferences
 

[[File:Flashing1.png| Figure 7|800px]]

* Add the below given Json URL in the Additional board manager URL

Json URL : https://espressif.github.io/arduino-esp32/package_esp32_index.json
 
[[File:ESPBSP1.png|Figure 8|800px]]

* Go to Tools > Board > Boards Manager
 

[[File:Flashing3.png|Figure 9|800px]]

* In the Board Manager search bar, type ESP-32, search for esp32 by Espressif and click on install to install the board
 
[[File:ESPBSP2.png|Figure 10|800px]]

* After installing, click on Tool > Boards and select AutosportLabs ESP32-CAN-X2
 
'''Flashing'''

* Connect the ESP-32-X2 board to your computer using a USB-C cable with your Arduino IDE open

* Select AutosportLabs ESP32-CAN-X2 in Tools > Board menu

* Go to Tools > Port and select the COM port to which ESP-32-X2 is connected.

[[File:ArduinoFlashing3.png|Figure 11|800px]]
 
Note : If you don’t see the COM Port in your Arduino IDE, you need to install the CP210x USB to UART Bridge VCP Drivers: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
 

* Write your firmware code or add an existing sketch that you want to upload to your custom board.

* Go to Sketch > Click upload to compile and upload the code

* After successful uploading, you should see a “Done uploading.” message at the bottom console. This console will also show error messages if there is any error.

[[File:ArduinoFlashing4...png|Figure 12|800px]]

If any issues occur during upload, double-check the board selection, COM port, and your code for errors.
<be>

===Importing Libraries in Arduino IDE===

* To Install Libraries for ESP32-CAN-X2 like mcp_canbus or mcp2515
* Go to Sketch > Include Library > Manage LibrarieSs

[[File:Arduino IDE Library 1.png]]

* Type and find the desired library like mcp_canbus by Longan Labs
* Search and Install the library

[[File:Arduino IDE Library 2...png]]

== Step-by-step instruction for CircuitPython==
===Sample CircuitPython code===
https://github.com/autosportlabs/ESP32-CAN-X2

'''Downloading ESP-32-X2 Board Support:''' 

Installing ESP-32-X2 is simple, please follow the steps given below :

* Go to circuitpython.org/board/autosportlabs_esp32_can_x2
Click on the browse S3 

[[File:CircuitpythonFlashing1.png|800px]] 

* Select the desired language 
 

[[File:CircuitpythonFlashing2.png|800px]]
* Download the latest .bin file
 

[[File:CircuitpythonFlashing4.png|800px]]

'''Prepare the ESP32 CAN X2 for Installation:''' 

* Connect the ESP-32-X2 board to your computer using a USB-C cable
* Press and hold the boot button on the development board.
* While holding the boot button, press and release the reset button once.
* Release the boot button to put the board into bootloader mode.
[[File:REV D Flashing Image.png|800px]]

'''Connect to the Web Serial ESP Tool'''

* Go to : https://adafruit.github.io/Adafruit_WebSerial_ESPTool/
* Press the Connect button in the top right corner of the page.
* A pop-up will appear asking you to select the COM or Serial port.
* Look for an option with ESP32, JTAG Loader, SLAB, or FTDI in the name
 

[[File:CircuitpythonFlashing6.png|800px]]

'''Flash the Firmware'''

* Click on Choose the .bin file you downloaded.
* Ensure that the Offset box next to the file location is set to 0x0.
* After selecting the file, the button text will change to match your filename.
* Click the Program button to start flashing. A progress bar will appear, and after a minute or two, the firmware will be
written.

[[File:Circuytpython7.gif|800px]]

'''Exit Bootloader Mode'''
* Press the reset button to exit bootloader mode. Shortly, the CIRCUITPY drive will pop up.

'''Downloading and Installing Mu Editor'''
* Download and install the recommended Mu Editor from codewith.mu.
* When you first start Mu, you will be prompted to select your mode. Select CircuitPython.
 
[[File:Mudownload.png|800px]]

* In Mu editor, click the Load button in the button bar, navigate to the CIRCUITPY drive, and choose code.py.
 
[[File:MU2.png|800px]]

'''Note :''' The CIRCUITPY drive is where your code and necessary libraries will reside. With a fresh CircuitPython install, the CIRCUITPY drive will contain a code.py file with print("Hello World!") and an empty lib folder. If your CIRCUITPY drive does not have a code.py file, create one and save it to the drive. CircuitPython automatically executes the code in code.py when the board starts up or resets. Do not press reset immediately after saving your code it will corrupt the drive and you may lose your code.

* Enter your code into the editor and save the code.py file on the CIRCUITPY drive.
 

[[File:MU3.png|800px]]

'''Congratulations!''' You have just run your first CircuitPython program.

=== Importing Libraries in Circuitpython ===

Importing libraries in Circuitpython is straightforward. For installing Libraries in Circuitpython, please follow the steps given below :
* Go to https://circuitpython.org/libraries and download the bundle for version 9.xx.
'''Note:''' The version of the bundle should be the same that you are using.
 

[[File:Mu4.png|800px]]

* Extract the zip file.
* Find the lib file where you can find your desired library.
* Copy that library folder or .mpy file and paste it to the lib folder in CIRCUITPY drive
 

[[File:Mueditor Library.gif|800px]]

=ESP32-CAN-X2 Rev-C=
[https://wiki.autosportlabs.com/ESP32-CAN-X2/RevC#6_pin_JST-PH_Connector ESP32-CAN-X2 Rev-C]

ESP32-CAN-X2

2026-04-29T00:51:36Z

Brentp: /* Board Pinout */

=Introduction=

ESP32-CAN-X2 is an automotive-grade ESP32-based development board specifically designed for CAN communication. This board has all the features of a modern ESP32 development board, integrated Wi-Fi and Bluetooth, along with the extended CAN controller. Autosport Labs has specifically designed it for CAN communication in harsh automotive and industrial environment, while offering fast processing and computation options.

This is a complete how-to-use guide and this user guide will describe each and every step to use the board and harness the maximum potential of the board.

[[File:ESP32_CAN_X2_revD_3quarter.jpg|700px]]

=Purchasing=
You can order the ESP32-CAN-X2 from our online store:
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Features=

Features of ESP32-CAN-X2 development board:

* Flexible power supply options up to 40V, suitable for automotive and industrial applications
* Based on ESP32-S3-WROOM-1-N8R8 microcontroller powerful dual-core Xtensa LX6 CPU running at up to 240 MHz.
* 384 KB ROM, 512 KB SRAM, 16 KB SRAM in RTC, 8 MB PSRAM
* Two LED’s: Power LED and user-defined LED1
* Integrated Wi-Fi (802.11b/g/n) and Bluetooth capabilities
* Reset and Boot push button
* USB-C type socket for flashing, and power supply
* Integrated antenna for long-range communication
* Additional CAN communication controller CAN using MCP2515
* Two 4-pin headers are strategically positioned at the top for CAN communication.
* Easy-to-interface programming. Required no external debugger for flashing
* Integrated CAN transceivers
* Configurable CAN termination resistors, which can be disabled via breakable jumpers
* Support of a wide choice of commonly used Integrated Development Environments (IDEs)
* [https://github.com/autosportlabs/ESP32-CAN-X2/ Comprehensive free software libraries] and examples for CAN communication for Arduino and Circuit Python
* Supports a range of stackable [[#Bolt-ons|add-on boards]] offering additional features such as GPS, RGB LEDs, switches, and more.

=Bolt-ons=
Bolt-ons are stackable add-on boards that offer easy extensibility

Make your own bolt on with a blank design template https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/bolt-on-template
===GPS bolt-on===
Adds a high performance GPS receiver 
[[File:GPS Bolt-on image main.png|300px|link=Gps-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/gps-bolt-on/]]
===Button bolt-on===
Adds 4 tactile switches + RGB LEDs 
[[File:Button Bolt-on white background.jpg|300px|link=Button-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/button-bolt-on/]]
===RGB LED bolt-on===
Adds 10 RGB LEDs across two groups for alert indicators 
[[File:RGB LED Bolt-on.jpg|300px|link=RGB-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/rgb-led-bolt-on/]]

=Getting started=

This section will provide you with comprehensive information about the ESP32-CAN-X2 development board's key components, mechanical layout, power rating, & requirements. This detailed information helps you to use the board effectively and efficiently in your projects.

== Key Components of ESP32-CAN-X2 Development Board ==

Figure 1 given below indicates the important key components of the ESP32-CAN-X2 Development Board and their location on the board.

[[File:REV D Images updated.png|Figure 1]]

=== Microcontroller ===

The ESP32-CAN-X2 Development Board is designed around the ESP32-S3-WROOM-1-N8R8 microcontroller in a 40-pin package. The connections between the development board and the microcontroller is straightforward, where the majority of GPIO pins are directly connected with the external headers, SV1 & SV2, and some pins are reserved internal connections between the board and CAN controllers. The internal connections between the microcontroller and CAN controllers are shown in the CAN controller heading given below. The microcontroller pin layout is shown in Figure 2 given below.

[[File:Microcontroller pin layout.png|Figure 2]]

=== External Connection Header ===

External headers, SV1 & SV2, are the two other important components of this development board. SV1 is the left side dual row header and the SV2 is the right side dual row header. Both of these headers have 20 pins available for connection. These headers provide connections for GPIOs, power output, ground (GND), power input, and CAN communication pins. Both of these header pinouts have standard size, allowing users to connect them using jumper wires, a breadboard, or even solder wires permanently onto the development board. However, while doing the wire connection the customer must make sure that none of them get short circuit. The details regarding the pin's names, numbers, outputs, and functions are given in the Board Pinout section below.

=== CAN bus transceivers===

The following are the specifications of the CAN transceivers for CAN1 and CAN2:

'''Detection of Ground Fault'''
* Permanent Dominant Detection on TXD
* Permanent Dominant Detection on Bus
* Power-on Reset and Voltage Brown-Out

'''Protection on V DD Pin'''
* Protection Against Damage Due to Short-Circuit
Conditions (Positive or Negative Battery Voltage)
* Protection Against High-Voltage Transients in

'''Automotive Environments'''
* Automatic Thermal Shutdown Protection
* Suitable for 12V and 24V Systems
* Meets or exceeds stringent automotive design requirements including “Hardware Requirementsfor LIN, CAN and FlexRay Interfaces in Automotive Applications”, Version 1.3, May 2012
• High-Noise Immunity Due to Differential Bus Implementation
• High Electrostatic Discharge (ESD) Protection on CANH and CANL, meeting the IEC61000-4-2 up to ±14 kV

=== CAN Controllers ===

The MCP2515 external connected CAN communication controller, and ESP-32 built-in CAN communication controller are two other main components of this development board.

The MCP2515, operating as the second external CAN controller in this development board, is a specialized component designed for Controller Area Network (CAN) applications. Its features include:

* Implements CAN V2.0B at up to 1 Mb/s.
* High-Speed SPI Interface (10 MHz)
* Interrupt Output Pin with selectable enables
* Multiple receive and transmit buffers
* Low-Power CMOS Technology: - 5 mA active current (typical), 1 μA standby current
 
The internal CAN controller also works at CAN V2.0. The internal CAN supports two message formats:

* Base frame format (11-bit ID)
* Extended frame format (29-bit ID)
 
'''Internal pinout connection between the CAN controllers and ESP32'''

==== CAN 1 ====
This is a built-in CAN controller and its RX is connected to IO6 of the microcontroller and TX is connected to IO7 of the microcontroller. The connections are shown in Figure 3 given below

==== CAN 2 ====
This is the externally connected MCP2515 controller with the following connections:
{| class="wikitable" style="text-align:center; width:60%"
|+ '''MCP2515 ESP32-CAN-X2 GPIO connections'''
! Signal !! ESP32 GPIO
|-
| CS || 10
|-
| CLK || 12
|-
| MISO || 13
|-
| MOSI || 11
|-
| IRQ || 3
|}

Crystal: 16MHz
[[File:CAN Controller Connections ESP32.jpg|Figure 3]]

=== Two 4-Pin header Connector ===

The ESP32-CAN-X2 development board provides two additional 4-pin connector headers at the top of the board to support CAN communication. This header makes wiring the device more convenient and robust. The CAN communication connection pinout details are given in the pinout section below.

=== Built-in LED ===
The built-in blue LED is connected to GPIO2 of the ESP32. For a demo that exercises this LED, see the [https://github.com/autosportlabs/ESP32-CAN-X2/blob/main/arduino/ping_pong/ping_pong.ino#L23 ping-pong example].

=== USB-C Socket ===
The ESP32-CAN-X2 development board has one USB-C port. This port is used for multiple functions: it powers the board, allows programming, and facilitates serial communication both ways.
However, it is important to note that when powering the board through the USB-C port, please ensure the nominal voltage range is 6-20V and Vmax is 40V.

=== Debug Connector ===
The following 6-pin connector marked as X4 is used for serial communication and debugging purposes with ESP32 CAN X2. The 6-pin configurations on the ESP32 CAN X2 is arranged as follows:

[[File:Debug connectors 6 pins.png|Figure 4]]

== Board Layout ==

Mechanical board outline physical dimensions:

* Width : 42.10 mm
* Length : 72 mm
 
The board top view is shown in the Figure 4 given below.

[[File:Board Layout.png|700px]]

== Power Ratings & Environmental Requirements ==

'''Power Options'''

The ESP32-CAN-X2 development board is flexible in its power input, and it provides multiple power input options. Power can either be supplied via the VIN pin, or via USB-C connector. Any voltage input either via USB or VIN is stepped down to 3.3 V via a voltage regulator.

'''Power available to your circuit'''

The onboard regulator can provide power to your devices:
* 1.5A is available on the 5V header pins
* 100mA is available on the 3.3v header pins

'''Pin Voltage'''

All digital & analog pins on the ESP32-CAN-X2 development board are 3.3 V. Do not connect any higher voltage devices to any of the pins as it will risk damaging the board.

'''VIN Rating'''

The nominal input voltage rating for the development board is 6-20v, with a 40v max input. Please do not attempt to power the board with a voltage outside the recommended range.

'''Operating Current'''

The typical operating current of ESP32-CAN-X2 development board is 105mA and maximum operating current is 500mA ( peak, during transmission )

'''Power Consumption'''

The normal power consumption of the board is 330mW and peak power consumption is 1.65W

'''Operating Temperature'''

Temperate rating is -40°C to +85°C

=CAN bus information=

CAN, also known as Control area networking, is a serial communication protocol that is widely used in Automotive applications. CAN bus communication protocol utilizes differential signaling methods in which data is transferred as a voltage difference between High and low voltage. Can Bus communication provides various advantages over other communication methods which makes it the most important communication protocol in automotive. A few features are follows

'''Multimaster system'''

In CAN Bus communication, multiple controllers can act as a master, and multiple devices can act as a node. Each node can share data with other nodes via the CAN bus. In modern cars, there are more than 70 ECUs, and using CAN communication each ECU acts as a node and can transfer the data to the CAN bus, this data is then available to all the ECUs, and ECU can then check the data and decide whether to receive or ignore it.

For details, visit: https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial

'''Lossless communication'''

CAN communication uses a bitwise arbitration method that avoids the contentions of data on the bus. When two nodes simultaneously try to send the data, then the node with the high priority ( lower identifier ) gets priority and continues transmitting. The identifier message can be 11-bit ( standard CAN ) or 29-bit ( extended CAN) in length.

For details, visit: https://dewesoft.com/blog/what-is-can-bus

'''Simple and cheap'''

The CAN communication between the ECUs is done through a single CAN system instead of direct complex analog signal lines which makes it extremely simple and reduces errors.

For details, visit: https://www.autopi.io/blog/can-bus-explained/

'''Errorless communication'''

CAN incorporates different built-in error detection mechanisms including cyclic redundancy checks (CRC), and frame check sequences (FCS) to detect errors during data transmission.

'''CAN network types'''
 
Prominent CAN network types are as follows.

* High-speed CAN bus ( Supports bit rates between 40 kbit/s and 1 Mbit/s )
* Low-Speed CAN bus ( Supports bit rates between 40 kbit/s and 125 kbit/s )
* CAN FD ( Supports bit rates between 1 Mbps to 8 Mbps )
 
For details, visit:https://dewesoft.com/blog/what-is-can-bus

'''Data transmission'''

In CAN, data is transferred between two nodes in messages known as CAN frames. There are four types of CAN frames.
* Data frame ( Used to transfer data between two node )
* Remote frame ( request data from other node )
* Error frame ( report errors )
* Overload frame ( report overload )
 
For details, visit:https://www.autopi.io/blog/can-bus-explained/

== CAN Termination ==

CAN termination is a process of terminating the CAN bus to prevent the signal reflection at the end of the bus and to ensure the correct DC level of the bus. The CAN BUS is bidirectional, and both ends of the bus must be properly terminated to prevent errors in communication. CAN termination is achieved by placing the termination resistance, which is normally 120 ohm, that matches the nominal resistance of the cable. ISO 11898 requires normally required CAN BUS cable of impedance 120 ohm; therefore, the CAN 120 ohm resistance is used for CAN termination. However, while doing the CAN termination, it must be kept in mind that the nodes from the far two ends of the cable only require termination resistors.

Figure 5 given below explain the CAN termination.

[[File:CAN BUS TERMINATION.png]]

Note : The low-speed CAN, single wire CAN, may not require the CAN bus termination.

'''How to enable & disable CAN termination in ESP-32-X2 ?'''

The ESP-32-X2 development board has given two separate CAN termination pads at the back side of the development board. The CAN termination jumpers are shown in figure 6 given below.

[[File:CAN termination.png]]

* Enable termination : In ESP-32-X2 development board, CAN termination is enabled by default.
* Disable termination : Scratch the copper trace between the pads, TERM1 & TERM2.
* Re-enable termination : Re-solder the traces between the pads

Note : Proper termination is necessary for ensuring errorless communication and signal integrity. Please follow the above given instruction carefully.

=Board Pinout=

The ESP32-CAN-X2 board has 40 pins across its two headers, SV1 & SV2 headers, and two 4-pin headers at the top. This guide explains the pin functionalities of the board. The pin configuration of the development board is shown in Figure 7 given below.

[[File:Pin Configuration 1.png|Figure 7]]

'''Left Header (SV1) Pinout (Top to Bottom)'''

The pin count start from the top of the left header, and the pin details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || CAN1H/2.7D || high-level signal for the first CAN channel.
|-
| 2 || CAN1L/2.7D || low-level signal for the first CAN channel
|-
| 3 || CAN2H/2.7C || high-level signal for the second CAN channel
|-
| 4 || CAN2L/2.7C || low-level signal for the second CAN channel
|-
| 5 || RX Pin || USART RX
|-
| 6 || TX Pin || USART TX
|-
| 7-20|| GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
|}

'''Right Header (SV2) Pinout (Bottom to Top )'''

The pin count start from bottom to top and details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1-11 || GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
| 12-13 || 3.3V || 3.3v Voltage Output (can be used to power your custom circuits)
|-
| 14-15 || 5V || 5v Voltage Output (can be used to power your custom circuits)
|-
| 16-18 || GND || Ground
|-
| 19-20 || 12 Vin || 12v voltage Input
|}

==12v note==
Only connect 12v to the 12v voltage input (19-20). To avoid electrical damage, do not connect 12v to any other pin on the board.

==Top Headers Pinout==

The X1 and X2 header supports CAN communication. Pin count starts at the right viewing the board from the top. The pinout configuration of the X1 and X2 header is shown in the figure 8 below:

[[File:Two 4-Pin CAN Connectors.png|Figure 8]]
* '''Note:''' Color codes on the provided pigtail may not match documentation.

The pin description of the X1 header is given in the table below:
{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the first CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the first CAN channel
|-
| 4 || GND || Ground
|}

The pin description of the X2 header is given in the table below:

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the second CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the second CAN channel
|-
| 4 || GND || Ground
|}

=Pigtail for Plug and Play Harness=
A [https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/ pigtail] is available for connector X1 and X2 that can integrate with the [[Harness_specifications|Autosport Labs plug and play harness system]]. This pigtail can provide power + CAN data to the board.

[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/]]

[[file:ESP32_CAN_X2_with_plug_and_play_harness_closeup.jpg|400px]] [[file:ESP32_CAN_X2_with_plug_and_play_harness-scaled.jpg|400px]]

=3D printed enclosure=
You can 3D print your own enclosure - files [https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/enclosures available on Github]:

[[file:esp32-can-x2-pigtail-3d-printed-enclosure-cover-off.jpg|400px]]
[[file:esp32-can-x2-pigtail-3d-printed-enclosure-cover-on.jpg|400px]]

=Flashing Firmware=

Firmware flashing in this development board is straightforward. The following components are required for firmware flashings.

'''Hardware Components'''

* USB-C cable
* Computer running Windows, Linux, or macOS
 

'''Software Components'''

* Updated Arduino IDE to compile code for ESP-32-X2.
* Update Mu Editor from codewith.mu
 
Note : Link to download Arduino IDE : https://www.arduino.cc/en/software || Link to download Mu Editor : codewith.mu

== Step by step instruction for Arduino IDE==

===Sample Arduino Project===
https://github.com/autosportlabs/ESP32-CAN-X2

Step-by-step instructions for flashing ESP-32-X2 are as follows.

'''Install ESP-32-X2 Board Support:'''

Adding ESP-32-X2 in Arduino Ide is a single-time process and its steps are as follows.

* Open Arduino Ide
* Go to File > Preferences
 

[[File:Flashing1.png| Figure 7|800px]]

* Add the below given Json URL in the Additional board manager URL

Json URL : https://espressif.github.io/arduino-esp32/package_esp32_index.json
 
[[File:ESPBSP1.png|Figure 8|800px]]

* Go to Tools > Board > Boards Manager
 

[[File:Flashing3.png|Figure 9|800px]]

* In the Board Manager search bar, type ESP-32, search for esp32 by Espressif and click on install to install the board
 
[[File:ESPBSP2.png|Figure 10|800px]]

* After installing, click on Tool > Boards and select AutosportLabs ESP32-CAN-X2
 
'''Flashing'''

* Connect the ESP-32-X2 board to your computer using a USB-C cable with your Arduino IDE open

* Select AutosportLabs ESP32-CAN-X2 in Tools > Board menu

* Go to Tools > Port and select the COM port to which ESP-32-X2 is connected.

[[File:ArduinoFlashing3.png|Figure 11|800px]]
 
Note : If you don’t see the COM Port in your Arduino IDE, you need to install the CP210x USB to UART Bridge VCP Drivers: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
 

* Write your firmware code or add an existing sketch that you want to upload to your custom board.

* Go to Sketch > Click upload to compile and upload the code

* After successful uploading, you should see a “Done uploading.” message at the bottom console. This console will also show error messages if there is any error.

[[File:ArduinoFlashing4...png|Figure 12|800px]]

If any issues occur during upload, double-check the board selection, COM port, and your code for errors.
<be>

===Importing Libraries in Arduino IDE===

* To Install Libraries for ESP32-CAN-X2 like mcp_canbus or mcp2515
* Go to Sketch > Include Library > Manage LibrarieSs

[[File:Arduino IDE Library 1.png]]

* Type and find the desired library like mcp_canbus by Longan Labs
* Search and Install the library

[[File:Arduino IDE Library 2...png]]

== Step-by-step instruction for CircuitPython==
===Sample CircuitPython code===
https://github.com/autosportlabs/ESP32-CAN-X2

'''Downloading ESP-32-X2 Board Support:''' 

Installing ESP-32-X2 is simple, please follow the steps given below :

* Go to circuitpython.org/board/autosportlabs_esp32_can_x2
Click on the browse S3 

[[File:CircuitpythonFlashing1.png|800px]] 

* Select the desired language 
 

[[File:CircuitpythonFlashing2.png|800px]]
* Download the latest .bin file
 

[[File:CircuitpythonFlashing4.png|800px]]

'''Prepare the ESP32 CAN X2 for Installation:''' 

* Connect the ESP-32-X2 board to your computer using a USB-C cable
* Press and hold the boot button on the development board.
* While holding the boot button, press and release the reset button once.
* Release the boot button to put the board into bootloader mode.
[[File:REV D Flashing Image.png|800px]]

'''Connect to the Web Serial ESP Tool'''

* Go to : https://adafruit.github.io/Adafruit_WebSerial_ESPTool/
* Press the Connect button in the top right corner of the page.
* A pop-up will appear asking you to select the COM or Serial port.
* Look for an option with ESP32, JTAG Loader, SLAB, or FTDI in the name
 

[[File:CircuitpythonFlashing6.png|800px]]

'''Flash the Firmware'''

* Click on Choose the .bin file you downloaded.
* Ensure that the Offset box next to the file location is set to 0x0.
* After selecting the file, the button text will change to match your filename.
* Click the Program button to start flashing. A progress bar will appear, and after a minute or two, the firmware will be
written.

[[File:Circuytpython7.gif|800px]]

'''Exit Bootloader Mode'''
* Press the reset button to exit bootloader mode. Shortly, the CIRCUITPY drive will pop up.

'''Downloading and Installing Mu Editor'''
* Download and install the recommended Mu Editor from codewith.mu.
* When you first start Mu, you will be prompted to select your mode. Select CircuitPython.
 
[[File:Mudownload.png|800px]]

* In Mu editor, click the Load button in the button bar, navigate to the CIRCUITPY drive, and choose code.py.
 
[[File:MU2.png|800px]]

'''Note :''' The CIRCUITPY drive is where your code and necessary libraries will reside. With a fresh CircuitPython install, the CIRCUITPY drive will contain a code.py file with print("Hello World!") and an empty lib folder. If your CIRCUITPY drive does not have a code.py file, create one and save it to the drive. CircuitPython automatically executes the code in code.py when the board starts up or resets. Do not press reset immediately after saving your code it will corrupt the drive and you may lose your code.

* Enter your code into the editor and save the code.py file on the CIRCUITPY drive.
 

[[File:MU3.png|800px]]

'''Congratulations!''' You have just run your first CircuitPython program.

=== Importing Libraries in Circuitpython ===

Importing libraries in Circuitpython is straightforward. For installing Libraries in Circuitpython, please follow the steps given below :
* Go to https://circuitpython.org/libraries and download the bundle for version 9.xx.
'''Note:''' The version of the bundle should be the same that you are using.
 

[[File:Mu4.png|800px]]

* Extract the zip file.
* Find the lib file where you can find your desired library.
* Copy that library folder or .mpy file and paste it to the lib folder in CIRCUITPY drive
 

[[File:Mueditor Library.gif|800px]]

=ESP32-CAN-X2 Rev-C=
[https://wiki.autosportlabs.com/ESP32-CAN-X2/RevC#6_pin_JST-PH_Connector ESP32-CAN-X2 Rev-C]

File:Esp32-can-x2-pigtail-3d-printed-enclosure-cover-on.jpg

2026-04-29T00:51:15Z

Brentp:

File:Esp32-can-x2-pigtail-3d-printed-enclosure-cover-off.jpg

2026-04-29T00:50:15Z

Brentp:

ESP32-CAN-X2

2026-04-28T23:56:47Z

Brentp: /* Pigtail for Plug and Play Harness */

=Introduction=

ESP32-CAN-X2 is an automotive-grade ESP32-based development board specifically designed for CAN communication. This board has all the features of a modern ESP32 development board, integrated Wi-Fi and Bluetooth, along with the extended CAN controller. Autosport Labs has specifically designed it for CAN communication in harsh automotive and industrial environment, while offering fast processing and computation options.

This is a complete how-to-use guide and this user guide will describe each and every step to use the board and harness the maximum potential of the board.

[[File:ESP32_CAN_X2_revD_3quarter.jpg|700px]]

=Purchasing=
You can order the ESP32-CAN-X2 from our online store:
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Features=

Features of ESP32-CAN-X2 development board:

* Flexible power supply options up to 40V, suitable for automotive and industrial applications
* Based on ESP32-S3-WROOM-1-N8R8 microcontroller powerful dual-core Xtensa LX6 CPU running at up to 240 MHz.
* 384 KB ROM, 512 KB SRAM, 16 KB SRAM in RTC, 8 MB PSRAM
* Two LED’s: Power LED and user-defined LED1
* Integrated Wi-Fi (802.11b/g/n) and Bluetooth capabilities
* Reset and Boot push button
* USB-C type socket for flashing, and power supply
* Integrated antenna for long-range communication
* Additional CAN communication controller CAN using MCP2515
* Two 4-pin headers are strategically positioned at the top for CAN communication.
* Easy-to-interface programming. Required no external debugger for flashing
* Integrated CAN transceivers
* Configurable CAN termination resistors, which can be disabled via breakable jumpers
* Support of a wide choice of commonly used Integrated Development Environments (IDEs)
* [https://github.com/autosportlabs/ESP32-CAN-X2/ Comprehensive free software libraries] and examples for CAN communication for Arduino and Circuit Python
* Supports a range of stackable [[#Bolt-ons|add-on boards]] offering additional features such as GPS, RGB LEDs, switches, and more.

=Bolt-ons=
Bolt-ons are stackable add-on boards that offer easy extensibility

Make your own bolt on with a blank design template https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/bolt-on-template
===GPS bolt-on===
Adds a high performance GPS receiver 
[[File:GPS Bolt-on image main.png|300px|link=Gps-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/gps-bolt-on/]]
===Button bolt-on===
Adds 4 tactile switches + RGB LEDs 
[[File:Button Bolt-on white background.jpg|300px|link=Button-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/button-bolt-on/]]
===RGB LED bolt-on===
Adds 10 RGB LEDs across two groups for alert indicators 
[[File:RGB LED Bolt-on.jpg|300px|link=RGB-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/rgb-led-bolt-on/]]

=Getting started=

This section will provide you with comprehensive information about the ESP32-CAN-X2 development board's key components, mechanical layout, power rating, & requirements. This detailed information helps you to use the board effectively and efficiently in your projects.

== Key Components of ESP32-CAN-X2 Development Board ==

Figure 1 given below indicates the important key components of the ESP32-CAN-X2 Development Board and their location on the board.

[[File:REV D Images updated.png|Figure 1]]

=== Microcontroller ===

The ESP32-CAN-X2 Development Board is designed around the ESP32-S3-WROOM-1-N8R8 microcontroller in a 40-pin package. The connections between the development board and the microcontroller is straightforward, where the majority of GPIO pins are directly connected with the external headers, SV1 & SV2, and some pins are reserved internal connections between the board and CAN controllers. The internal connections between the microcontroller and CAN controllers are shown in the CAN controller heading given below. The microcontroller pin layout is shown in Figure 2 given below.

[[File:Microcontroller pin layout.png|Figure 2]]

=== External Connection Header ===

External headers, SV1 & SV2, are the two other important components of this development board. SV1 is the left side dual row header and the SV2 is the right side dual row header. Both of these headers have 20 pins available for connection. These headers provide connections for GPIOs, power output, ground (GND), power input, and CAN communication pins. Both of these header pinouts have standard size, allowing users to connect them using jumper wires, a breadboard, or even solder wires permanently onto the development board. However, while doing the wire connection the customer must make sure that none of them get short circuit. The details regarding the pin's names, numbers, outputs, and functions are given in the Board Pinout section below.

=== CAN bus transceivers===

The following are the specifications of the CAN transceivers for CAN1 and CAN2:

'''Detection of Ground Fault'''
* Permanent Dominant Detection on TXD
* Permanent Dominant Detection on Bus
* Power-on Reset and Voltage Brown-Out

'''Protection on V DD Pin'''
* Protection Against Damage Due to Short-Circuit
Conditions (Positive or Negative Battery Voltage)
* Protection Against High-Voltage Transients in

'''Automotive Environments'''
* Automatic Thermal Shutdown Protection
* Suitable for 12V and 24V Systems
* Meets or exceeds stringent automotive design requirements including “Hardware Requirementsfor LIN, CAN and FlexRay Interfaces in Automotive Applications”, Version 1.3, May 2012
• High-Noise Immunity Due to Differential Bus Implementation
• High Electrostatic Discharge (ESD) Protection on CANH and CANL, meeting the IEC61000-4-2 up to ±14 kV

=== CAN Controllers ===

The MCP2515 external connected CAN communication controller, and ESP-32 built-in CAN communication controller are two other main components of this development board.

The MCP2515, operating as the second external CAN controller in this development board, is a specialized component designed for Controller Area Network (CAN) applications. Its features include:

* Implements CAN V2.0B at up to 1 Mb/s.
* High-Speed SPI Interface (10 MHz)
* Interrupt Output Pin with selectable enables
* Multiple receive and transmit buffers
* Low-Power CMOS Technology: - 5 mA active current (typical), 1 μA standby current
 
The internal CAN controller also works at CAN V2.0. The internal CAN supports two message formats:

* Base frame format (11-bit ID)
* Extended frame format (29-bit ID)
 
'''Internal pinout connection between the CAN controllers and ESP32'''

==== CAN 1 ====
This is a built-in CAN controller and its RX is connected to IO6 of the microcontroller and TX is connected to IO7 of the microcontroller. The connections are shown in Figure 3 given below

==== CAN 2 ====
This is the externally connected MCP2515 controller with the following connections:
{| class="wikitable" style="text-align:center; width:60%"
|+ '''MCP2515 ESP32-CAN-X2 GPIO connections'''
! Signal !! ESP32 GPIO
|-
| CS || 10
|-
| CLK || 12
|-
| MISO || 13
|-
| MOSI || 11
|-
| IRQ || 3
|}

Crystal: 16MHz
[[File:CAN Controller Connections ESP32.jpg|Figure 3]]

=== Two 4-Pin header Connector ===

The ESP32-CAN-X2 development board provides two additional 4-pin connector headers at the top of the board to support CAN communication. This header makes wiring the device more convenient and robust. The CAN communication connection pinout details are given in the pinout section below.

=== Built-in LED ===
The built-in blue LED is connected to GPIO2 of the ESP32. For a demo that exercises this LED, see the [https://github.com/autosportlabs/ESP32-CAN-X2/blob/main/arduino/ping_pong/ping_pong.ino#L23 ping-pong example].

=== USB-C Socket ===
The ESP32-CAN-X2 development board has one USB-C port. This port is used for multiple functions: it powers the board, allows programming, and facilitates serial communication both ways.
However, it is important to note that when powering the board through the USB-C port, please ensure the nominal voltage range is 6-20V and Vmax is 40V.

=== Debug Connector ===
The following 6-pin connector marked as X4 is used for serial communication and debugging purposes with ESP32 CAN X2. The 6-pin configurations on the ESP32 CAN X2 is arranged as follows:

[[File:Debug connectors 6 pins.png|Figure 4]]

== Board Layout ==

Mechanical board outline physical dimensions:

* Width : 42.10 mm
* Length : 72 mm
 
The board top view is shown in the Figure 4 given below.

[[File:Board Layout.png|700px]]

== Power Ratings & Environmental Requirements ==

'''Power Options'''

The ESP32-CAN-X2 development board is flexible in its power input, and it provides multiple power input options. Power can either be supplied via the VIN pin, or via USB-C connector. Any voltage input either via USB or VIN is stepped down to 3.3 V via a voltage regulator.

'''Power available to your circuit'''

The onboard regulator can provide power to your devices:
* 1.5A is available on the 5V header pins
* 100mA is available on the 3.3v header pins

'''Pin Voltage'''

All digital & analog pins on the ESP32-CAN-X2 development board are 3.3 V. Do not connect any higher voltage devices to any of the pins as it will risk damaging the board.

'''VIN Rating'''

The nominal input voltage rating for the development board is 6-20v, with a 40v max input. Please do not attempt to power the board with a voltage outside the recommended range.

'''Operating Current'''

The typical operating current of ESP32-CAN-X2 development board is 105mA and maximum operating current is 500mA ( peak, during transmission )

'''Power Consumption'''

The normal power consumption of the board is 330mW and peak power consumption is 1.65W

'''Operating Temperature'''

Temperate rating is -40°C to +85°C

=CAN bus information=

CAN, also known as Control area networking, is a serial communication protocol that is widely used in Automotive applications. CAN bus communication protocol utilizes differential signaling methods in which data is transferred as a voltage difference between High and low voltage. Can Bus communication provides various advantages over other communication methods which makes it the most important communication protocol in automotive. A few features are follows

'''Multimaster system'''

In CAN Bus communication, multiple controllers can act as a master, and multiple devices can act as a node. Each node can share data with other nodes via the CAN bus. In modern cars, there are more than 70 ECUs, and using CAN communication each ECU acts as a node and can transfer the data to the CAN bus, this data is then available to all the ECUs, and ECU can then check the data and decide whether to receive or ignore it.

For details, visit: https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial

'''Lossless communication'''

CAN communication uses a bitwise arbitration method that avoids the contentions of data on the bus. When two nodes simultaneously try to send the data, then the node with the high priority ( lower identifier ) gets priority and continues transmitting. The identifier message can be 11-bit ( standard CAN ) or 29-bit ( extended CAN) in length.

For details, visit: https://dewesoft.com/blog/what-is-can-bus

'''Simple and cheap'''

The CAN communication between the ECUs is done through a single CAN system instead of direct complex analog signal lines which makes it extremely simple and reduces errors.

For details, visit: https://www.autopi.io/blog/can-bus-explained/

'''Errorless communication'''

CAN incorporates different built-in error detection mechanisms including cyclic redundancy checks (CRC), and frame check sequences (FCS) to detect errors during data transmission.

'''CAN network types'''
 
Prominent CAN network types are as follows.

* High-speed CAN bus ( Supports bit rates between 40 kbit/s and 1 Mbit/s )
* Low-Speed CAN bus ( Supports bit rates between 40 kbit/s and 125 kbit/s )
* CAN FD ( Supports bit rates between 1 Mbps to 8 Mbps )
 
For details, visit:https://dewesoft.com/blog/what-is-can-bus

'''Data transmission'''

In CAN, data is transferred between two nodes in messages known as CAN frames. There are four types of CAN frames.
* Data frame ( Used to transfer data between two node )
* Remote frame ( request data from other node )
* Error frame ( report errors )
* Overload frame ( report overload )
 
For details, visit:https://www.autopi.io/blog/can-bus-explained/

== CAN Termination ==

CAN termination is a process of terminating the CAN bus to prevent the signal reflection at the end of the bus and to ensure the correct DC level of the bus. The CAN BUS is bidirectional, and both ends of the bus must be properly terminated to prevent errors in communication. CAN termination is achieved by placing the termination resistance, which is normally 120 ohm, that matches the nominal resistance of the cable. ISO 11898 requires normally required CAN BUS cable of impedance 120 ohm; therefore, the CAN 120 ohm resistance is used for CAN termination. However, while doing the CAN termination, it must be kept in mind that the nodes from the far two ends of the cable only require termination resistors.

Figure 5 given below explain the CAN termination.

[[File:CAN BUS TERMINATION.png]]

Note : The low-speed CAN, single wire CAN, may not require the CAN bus termination.

'''How to enable & disable CAN termination in ESP-32-X2 ?'''

The ESP-32-X2 development board has given two separate CAN termination pads at the back side of the development board. The CAN termination jumpers are shown in figure 6 given below.

[[File:CAN termination.png]]

* Enable termination : In ESP-32-X2 development board, CAN termination is enabled by default.
* Disable termination : Scratch the copper trace between the pads, TERM1 & TERM2.
* Re-enable termination : Re-solder the traces between the pads

Note : Proper termination is necessary for ensuring errorless communication and signal integrity. Please follow the above given instruction carefully.

=Board Pinout=

The ESP32-CAN-X2 board has 40 pins across its two headers, SV1 & SV2 headers, and two 4-pin headers at the top. This guide explains the pin functionalities of the board. The pin configuration of the development board is shown in Figure 7 given below.

[[File:Pin Configuration 1.png|Figure 7]]

'''Left Header (SV1) Pinout (Top to Bottom)'''

The pin count start from the top of the left header, and the pin details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || CAN1H/2.7D || high-level signal for the first CAN channel.
|-
| 2 || CAN1L/2.7D || low-level signal for the first CAN channel
|-
| 3 || CAN2H/2.7C || high-level signal for the second CAN channel
|-
| 4 || CAN2L/2.7C || low-level signal for the second CAN channel
|-
| 5 || RX Pin || USART RX
|-
| 6 || TX Pin || USART TX
|-
| 7-20|| GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
|}

'''Right Header (SV2) Pinout (Bottom to Top )'''

The pin count start from bottom to top and details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1-11 || GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
| 12-13 || 3.3V || 3.3v Voltage Output (can be used to power your custom circuits)
|-
| 14-15 || 5V || 5v Voltage Output (can be used to power your custom circuits)
|-
| 16-18 || GND || Ground
|-
| 19-20 || 12 Vin || 12v voltage Input
|}

==12v note==
Only connect 12v to the 12v voltage input (19-20). To avoid electrical damage, do not connect 12v to any other pin on the board.

==Top Headers Pinout==

The X1 and X2 header supports CAN communication. Pin count starts at the right viewing the board from the top. The pinout configuration of the X1 and X2 header is shown in the figure 8 below:

[[File:Two 4-Pin CAN Connectors.png|Figure 8]]
* '''Note:''' Color codes on the provided pigtail may not match documentation.

The pin description of the X1 header is given in the table below:
{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the first CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the first CAN channel
|-
| 4 || GND || Ground
|}

The pin description of the X2 header is given in the table below:

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the second CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the second CAN channel
|-
| 4 || GND || Ground
|}

==Pigtail for Plug and Play Harness==
A [https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/ pigtail] is available for connector X1 and X2 that can integrate with the [[Harness_specifications|Autosport Labs plug and play harness system]]. This pigtail can provide power + CAN data to the board.

[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/]]

[[file:ESP32_CAN_X2_with_plug_and_play_harness_closeup.jpg|400px]] [[file:ESP32_CAN_X2_with_plug_and_play_harness-scaled.jpg|400px]]

=Flashing Firmware=

Firmware flashing in this development board is straightforward. The following components are required for firmware flashings.

'''Hardware Components'''

* USB-C cable
* Computer running Windows, Linux, or macOS
 

'''Software Components'''

* Updated Arduino IDE to compile code for ESP-32-X2.
* Update Mu Editor from codewith.mu
 
Note : Link to download Arduino IDE : https://www.arduino.cc/en/software || Link to download Mu Editor : codewith.mu

== Step by step instruction for Arduino IDE==

===Sample Arduino Project===
https://github.com/autosportlabs/ESP32-CAN-X2

Step-by-step instructions for flashing ESP-32-X2 are as follows.

'''Install ESP-32-X2 Board Support:'''

Adding ESP-32-X2 in Arduino Ide is a single-time process and its steps are as follows.

* Open Arduino Ide
* Go to File > Preferences
 

[[File:Flashing1.png| Figure 7|800px]]

* Add the below given Json URL in the Additional board manager URL

Json URL : https://espressif.github.io/arduino-esp32/package_esp32_index.json
 
[[File:ESPBSP1.png|Figure 8|800px]]

* Go to Tools > Board > Boards Manager
 

[[File:Flashing3.png|Figure 9|800px]]

* In the Board Manager search bar, type ESP-32, search for esp32 by Espressif and click on install to install the board
 
[[File:ESPBSP2.png|Figure 10|800px]]

* After installing, click on Tool > Boards and select AutosportLabs ESP32-CAN-X2
 
'''Flashing'''

* Connect the ESP-32-X2 board to your computer using a USB-C cable with your Arduino IDE open

* Select AutosportLabs ESP32-CAN-X2 in Tools > Board menu

* Go to Tools > Port and select the COM port to which ESP-32-X2 is connected.

[[File:ArduinoFlashing3.png|Figure 11|800px]]
 
Note : If you don’t see the COM Port in your Arduino IDE, you need to install the CP210x USB to UART Bridge VCP Drivers: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
 

* Write your firmware code or add an existing sketch that you want to upload to your custom board.

* Go to Sketch > Click upload to compile and upload the code

* After successful uploading, you should see a “Done uploading.” message at the bottom console. This console will also show error messages if there is any error.

[[File:ArduinoFlashing4...png|Figure 12|800px]]

If any issues occur during upload, double-check the board selection, COM port, and your code for errors.
<be>

===Importing Libraries in Arduino IDE===

* To Install Libraries for ESP32-CAN-X2 like mcp_canbus or mcp2515
* Go to Sketch > Include Library > Manage LibrarieSs

[[File:Arduino IDE Library 1.png]]

* Type and find the desired library like mcp_canbus by Longan Labs
* Search and Install the library

[[File:Arduino IDE Library 2...png]]

== Step-by-step instruction for CircuitPython==
===Sample CircuitPython code===
https://github.com/autosportlabs/ESP32-CAN-X2

'''Downloading ESP-32-X2 Board Support:''' 

Installing ESP-32-X2 is simple, please follow the steps given below :

* Go to circuitpython.org/board/autosportlabs_esp32_can_x2
Click on the browse S3 

[[File:CircuitpythonFlashing1.png|800px]] 

* Select the desired language 
 

[[File:CircuitpythonFlashing2.png|800px]]
* Download the latest .bin file
 

[[File:CircuitpythonFlashing4.png|800px]]

'''Prepare the ESP32 CAN X2 for Installation:''' 

* Connect the ESP-32-X2 board to your computer using a USB-C cable
* Press and hold the boot button on the development board.
* While holding the boot button, press and release the reset button once.
* Release the boot button to put the board into bootloader mode.
[[File:REV D Flashing Image.png|800px]]

'''Connect to the Web Serial ESP Tool'''

* Go to : https://adafruit.github.io/Adafruit_WebSerial_ESPTool/
* Press the Connect button in the top right corner of the page.
* A pop-up will appear asking you to select the COM or Serial port.
* Look for an option with ESP32, JTAG Loader, SLAB, or FTDI in the name
 

[[File:CircuitpythonFlashing6.png|800px]]

'''Flash the Firmware'''

* Click on Choose the .bin file you downloaded.
* Ensure that the Offset box next to the file location is set to 0x0.
* After selecting the file, the button text will change to match your filename.
* Click the Program button to start flashing. A progress bar will appear, and after a minute or two, the firmware will be
written.

[[File:Circuytpython7.gif|800px]]

'''Exit Bootloader Mode'''
* Press the reset button to exit bootloader mode. Shortly, the CIRCUITPY drive will pop up.

'''Downloading and Installing Mu Editor'''
* Download and install the recommended Mu Editor from codewith.mu.
* When you first start Mu, you will be prompted to select your mode. Select CircuitPython.
 
[[File:Mudownload.png|800px]]

* In Mu editor, click the Load button in the button bar, navigate to the CIRCUITPY drive, and choose code.py.
 
[[File:MU2.png|800px]]

'''Note :''' The CIRCUITPY drive is where your code and necessary libraries will reside. With a fresh CircuitPython install, the CIRCUITPY drive will contain a code.py file with print("Hello World!") and an empty lib folder. If your CIRCUITPY drive does not have a code.py file, create one and save it to the drive. CircuitPython automatically executes the code in code.py when the board starts up or resets. Do not press reset immediately after saving your code it will corrupt the drive and you may lose your code.

* Enter your code into the editor and save the code.py file on the CIRCUITPY drive.
 

[[File:MU3.png|800px]]

'''Congratulations!''' You have just run your first CircuitPython program.

=== Importing Libraries in Circuitpython ===

Importing libraries in Circuitpython is straightforward. For installing Libraries in Circuitpython, please follow the steps given below :
* Go to https://circuitpython.org/libraries and download the bundle for version 9.xx.
'''Note:''' The version of the bundle should be the same that you are using.
 

[[File:Mu4.png|800px]]

* Extract the zip file.
* Find the lib file where you can find your desired library.
* Copy that library folder or .mpy file and paste it to the lib folder in CIRCUITPY drive
 

[[File:Mueditor Library.gif|800px]]

=ESP32-CAN-X2 Rev-C=
[https://wiki.autosportlabs.com/ESP32-CAN-X2/RevC#6_pin_JST-PH_Connector ESP32-CAN-X2 Rev-C]

ESP32-CAN-X2

2026-04-28T23:55:49Z

Brentp: /* Top Headers Pinout */

=Introduction=

ESP32-CAN-X2 is an automotive-grade ESP32-based development board specifically designed for CAN communication. This board has all the features of a modern ESP32 development board, integrated Wi-Fi and Bluetooth, along with the extended CAN controller. Autosport Labs has specifically designed it for CAN communication in harsh automotive and industrial environment, while offering fast processing and computation options.

This is a complete how-to-use guide and this user guide will describe each and every step to use the board and harness the maximum potential of the board.

[[File:ESP32_CAN_X2_revD_3quarter.jpg|700px]]

=Purchasing=
You can order the ESP32-CAN-X2 from our online store:
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Features=

Features of ESP32-CAN-X2 development board:

* Flexible power supply options up to 40V, suitable for automotive and industrial applications
* Based on ESP32-S3-WROOM-1-N8R8 microcontroller powerful dual-core Xtensa LX6 CPU running at up to 240 MHz.
* 384 KB ROM, 512 KB SRAM, 16 KB SRAM in RTC, 8 MB PSRAM
* Two LED’s: Power LED and user-defined LED1
* Integrated Wi-Fi (802.11b/g/n) and Bluetooth capabilities
* Reset and Boot push button
* USB-C type socket for flashing, and power supply
* Integrated antenna for long-range communication
* Additional CAN communication controller CAN using MCP2515
* Two 4-pin headers are strategically positioned at the top for CAN communication.
* Easy-to-interface programming. Required no external debugger for flashing
* Integrated CAN transceivers
* Configurable CAN termination resistors, which can be disabled via breakable jumpers
* Support of a wide choice of commonly used Integrated Development Environments (IDEs)
* [https://github.com/autosportlabs/ESP32-CAN-X2/ Comprehensive free software libraries] and examples for CAN communication for Arduino and Circuit Python
* Supports a range of stackable [[#Bolt-ons|add-on boards]] offering additional features such as GPS, RGB LEDs, switches, and more.

=Bolt-ons=
Bolt-ons are stackable add-on boards that offer easy extensibility

Make your own bolt on with a blank design template https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/bolt-on-template
===GPS bolt-on===
Adds a high performance GPS receiver 
[[File:GPS Bolt-on image main.png|300px|link=Gps-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/gps-bolt-on/]]
===Button bolt-on===
Adds 4 tactile switches + RGB LEDs 
[[File:Button Bolt-on white background.jpg|300px|link=Button-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/button-bolt-on/]]
===RGB LED bolt-on===
Adds 10 RGB LEDs across two groups for alert indicators 
[[File:RGB LED Bolt-on.jpg|300px|link=RGB-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/rgb-led-bolt-on/]]

=Getting started=

This section will provide you with comprehensive information about the ESP32-CAN-X2 development board's key components, mechanical layout, power rating, & requirements. This detailed information helps you to use the board effectively and efficiently in your projects.

== Key Components of ESP32-CAN-X2 Development Board ==

Figure 1 given below indicates the important key components of the ESP32-CAN-X2 Development Board and their location on the board.

[[File:REV D Images updated.png|Figure 1]]

=== Microcontroller ===

The ESP32-CAN-X2 Development Board is designed around the ESP32-S3-WROOM-1-N8R8 microcontroller in a 40-pin package. The connections between the development board and the microcontroller is straightforward, where the majority of GPIO pins are directly connected with the external headers, SV1 & SV2, and some pins are reserved internal connections between the board and CAN controllers. The internal connections between the microcontroller and CAN controllers are shown in the CAN controller heading given below. The microcontroller pin layout is shown in Figure 2 given below.

[[File:Microcontroller pin layout.png|Figure 2]]

=== External Connection Header ===

External headers, SV1 & SV2, are the two other important components of this development board. SV1 is the left side dual row header and the SV2 is the right side dual row header. Both of these headers have 20 pins available for connection. These headers provide connections for GPIOs, power output, ground (GND), power input, and CAN communication pins. Both of these header pinouts have standard size, allowing users to connect them using jumper wires, a breadboard, or even solder wires permanently onto the development board. However, while doing the wire connection the customer must make sure that none of them get short circuit. The details regarding the pin's names, numbers, outputs, and functions are given in the Board Pinout section below.

=== CAN bus transceivers===

The following are the specifications of the CAN transceivers for CAN1 and CAN2:

'''Detection of Ground Fault'''
* Permanent Dominant Detection on TXD
* Permanent Dominant Detection on Bus
* Power-on Reset and Voltage Brown-Out

'''Protection on V DD Pin'''
* Protection Against Damage Due to Short-Circuit
Conditions (Positive or Negative Battery Voltage)
* Protection Against High-Voltage Transients in

'''Automotive Environments'''
* Automatic Thermal Shutdown Protection
* Suitable for 12V and 24V Systems
* Meets or exceeds stringent automotive design requirements including “Hardware Requirementsfor LIN, CAN and FlexRay Interfaces in Automotive Applications”, Version 1.3, May 2012
• High-Noise Immunity Due to Differential Bus Implementation
• High Electrostatic Discharge (ESD) Protection on CANH and CANL, meeting the IEC61000-4-2 up to ±14 kV

=== CAN Controllers ===

The MCP2515 external connected CAN communication controller, and ESP-32 built-in CAN communication controller are two other main components of this development board.

The MCP2515, operating as the second external CAN controller in this development board, is a specialized component designed for Controller Area Network (CAN) applications. Its features include:

* Implements CAN V2.0B at up to 1 Mb/s.
* High-Speed SPI Interface (10 MHz)
* Interrupt Output Pin with selectable enables
* Multiple receive and transmit buffers
* Low-Power CMOS Technology: - 5 mA active current (typical), 1 μA standby current
 
The internal CAN controller also works at CAN V2.0. The internal CAN supports two message formats:

* Base frame format (11-bit ID)
* Extended frame format (29-bit ID)
 
'''Internal pinout connection between the CAN controllers and ESP32'''

==== CAN 1 ====
This is a built-in CAN controller and its RX is connected to IO6 of the microcontroller and TX is connected to IO7 of the microcontroller. The connections are shown in Figure 3 given below

==== CAN 2 ====
This is the externally connected MCP2515 controller with the following connections:
{| class="wikitable" style="text-align:center; width:60%"
|+ '''MCP2515 ESP32-CAN-X2 GPIO connections'''
! Signal !! ESP32 GPIO
|-
| CS || 10
|-
| CLK || 12
|-
| MISO || 13
|-
| MOSI || 11
|-
| IRQ || 3
|}

Crystal: 16MHz
[[File:CAN Controller Connections ESP32.jpg|Figure 3]]

=== Two 4-Pin header Connector ===

The ESP32-CAN-X2 development board provides two additional 4-pin connector headers at the top of the board to support CAN communication. This header makes wiring the device more convenient and robust. The CAN communication connection pinout details are given in the pinout section below.

=== Built-in LED ===
The built-in blue LED is connected to GPIO2 of the ESP32. For a demo that exercises this LED, see the [https://github.com/autosportlabs/ESP32-CAN-X2/blob/main/arduino/ping_pong/ping_pong.ino#L23 ping-pong example].

=== USB-C Socket ===
The ESP32-CAN-X2 development board has one USB-C port. This port is used for multiple functions: it powers the board, allows programming, and facilitates serial communication both ways.
However, it is important to note that when powering the board through the USB-C port, please ensure the nominal voltage range is 6-20V and Vmax is 40V.

=== Debug Connector ===
The following 6-pin connector marked as X4 is used for serial communication and debugging purposes with ESP32 CAN X2. The 6-pin configurations on the ESP32 CAN X2 is arranged as follows:

[[File:Debug connectors 6 pins.png|Figure 4]]

== Board Layout ==

Mechanical board outline physical dimensions:

* Width : 42.10 mm
* Length : 72 mm
 
The board top view is shown in the Figure 4 given below.

[[File:Board Layout.png|700px]]

== Power Ratings & Environmental Requirements ==

'''Power Options'''

The ESP32-CAN-X2 development board is flexible in its power input, and it provides multiple power input options. Power can either be supplied via the VIN pin, or via USB-C connector. Any voltage input either via USB or VIN is stepped down to 3.3 V via a voltage regulator.

'''Power available to your circuit'''

The onboard regulator can provide power to your devices:
* 1.5A is available on the 5V header pins
* 100mA is available on the 3.3v header pins

'''Pin Voltage'''

All digital & analog pins on the ESP32-CAN-X2 development board are 3.3 V. Do not connect any higher voltage devices to any of the pins as it will risk damaging the board.

'''VIN Rating'''

The nominal input voltage rating for the development board is 6-20v, with a 40v max input. Please do not attempt to power the board with a voltage outside the recommended range.

'''Operating Current'''

The typical operating current of ESP32-CAN-X2 development board is 105mA and maximum operating current is 500mA ( peak, during transmission )

'''Power Consumption'''

The normal power consumption of the board is 330mW and peak power consumption is 1.65W

'''Operating Temperature'''

Temperate rating is -40°C to +85°C

=CAN bus information=

CAN, also known as Control area networking, is a serial communication protocol that is widely used in Automotive applications. CAN bus communication protocol utilizes differential signaling methods in which data is transferred as a voltage difference between High and low voltage. Can Bus communication provides various advantages over other communication methods which makes it the most important communication protocol in automotive. A few features are follows

'''Multimaster system'''

In CAN Bus communication, multiple controllers can act as a master, and multiple devices can act as a node. Each node can share data with other nodes via the CAN bus. In modern cars, there are more than 70 ECUs, and using CAN communication each ECU acts as a node and can transfer the data to the CAN bus, this data is then available to all the ECUs, and ECU can then check the data and decide whether to receive or ignore it.

For details, visit: https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial

'''Lossless communication'''

CAN communication uses a bitwise arbitration method that avoids the contentions of data on the bus. When two nodes simultaneously try to send the data, then the node with the high priority ( lower identifier ) gets priority and continues transmitting. The identifier message can be 11-bit ( standard CAN ) or 29-bit ( extended CAN) in length.

For details, visit: https://dewesoft.com/blog/what-is-can-bus

'''Simple and cheap'''

The CAN communication between the ECUs is done through a single CAN system instead of direct complex analog signal lines which makes it extremely simple and reduces errors.

For details, visit: https://www.autopi.io/blog/can-bus-explained/

'''Errorless communication'''

CAN incorporates different built-in error detection mechanisms including cyclic redundancy checks (CRC), and frame check sequences (FCS) to detect errors during data transmission.

'''CAN network types'''
 
Prominent CAN network types are as follows.

* High-speed CAN bus ( Supports bit rates between 40 kbit/s and 1 Mbit/s )
* Low-Speed CAN bus ( Supports bit rates between 40 kbit/s and 125 kbit/s )
* CAN FD ( Supports bit rates between 1 Mbps to 8 Mbps )
 
For details, visit:https://dewesoft.com/blog/what-is-can-bus

'''Data transmission'''

In CAN, data is transferred between two nodes in messages known as CAN frames. There are four types of CAN frames.
* Data frame ( Used to transfer data between two node )
* Remote frame ( request data from other node )
* Error frame ( report errors )
* Overload frame ( report overload )
 
For details, visit:https://www.autopi.io/blog/can-bus-explained/

== CAN Termination ==

CAN termination is a process of terminating the CAN bus to prevent the signal reflection at the end of the bus and to ensure the correct DC level of the bus. The CAN BUS is bidirectional, and both ends of the bus must be properly terminated to prevent errors in communication. CAN termination is achieved by placing the termination resistance, which is normally 120 ohm, that matches the nominal resistance of the cable. ISO 11898 requires normally required CAN BUS cable of impedance 120 ohm; therefore, the CAN 120 ohm resistance is used for CAN termination. However, while doing the CAN termination, it must be kept in mind that the nodes from the far two ends of the cable only require termination resistors.

Figure 5 given below explain the CAN termination.

[[File:CAN BUS TERMINATION.png]]

Note : The low-speed CAN, single wire CAN, may not require the CAN bus termination.

'''How to enable & disable CAN termination in ESP-32-X2 ?'''

The ESP-32-X2 development board has given two separate CAN termination pads at the back side of the development board. The CAN termination jumpers are shown in figure 6 given below.

[[File:CAN termination.png]]

* Enable termination : In ESP-32-X2 development board, CAN termination is enabled by default.
* Disable termination : Scratch the copper trace between the pads, TERM1 & TERM2.
* Re-enable termination : Re-solder the traces between the pads

Note : Proper termination is necessary for ensuring errorless communication and signal integrity. Please follow the above given instruction carefully.

=Board Pinout=

The ESP32-CAN-X2 board has 40 pins across its two headers, SV1 & SV2 headers, and two 4-pin headers at the top. This guide explains the pin functionalities of the board. The pin configuration of the development board is shown in Figure 7 given below.

[[File:Pin Configuration 1.png|Figure 7]]

'''Left Header (SV1) Pinout (Top to Bottom)'''

The pin count start from the top of the left header, and the pin details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || CAN1H/2.7D || high-level signal for the first CAN channel.
|-
| 2 || CAN1L/2.7D || low-level signal for the first CAN channel
|-
| 3 || CAN2H/2.7C || high-level signal for the second CAN channel
|-
| 4 || CAN2L/2.7C || low-level signal for the second CAN channel
|-
| 5 || RX Pin || USART RX
|-
| 6 || TX Pin || USART TX
|-
| 7-20|| GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
|}

'''Right Header (SV2) Pinout (Bottom to Top )'''

The pin count start from bottom to top and details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1-11 || GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
| 12-13 || 3.3V || 3.3v Voltage Output (can be used to power your custom circuits)
|-
| 14-15 || 5V || 5v Voltage Output (can be used to power your custom circuits)
|-
| 16-18 || GND || Ground
|-
| 19-20 || 12 Vin || 12v voltage Input
|}

==12v note==
Only connect 12v to the 12v voltage input (19-20). To avoid electrical damage, do not connect 12v to any other pin on the board.

==Top Headers Pinout==

The X1 and X2 header supports CAN communication. Pin count starts at the right viewing the board from the top. The pinout configuration of the X1 and X2 header is shown in the figure 8 below:

[[File:Two 4-Pin CAN Connectors.png|Figure 8]]
* '''Note:''' Color codes on the provided pigtail may not match documentation.

The pin description of the X1 header is given in the table below:
{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the first CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the first CAN channel
|-
| 4 || GND || Ground
|}

The pin description of the X2 header is given in the table below:

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the second CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the second CAN channel
|-
| 4 || GND || Ground
|}

==Pigtail for Plug and Play Harness==
A [https://www.autosportlabs.com/product/plug-and-play-harness-connection-for-esp32-can-x2/ pigtail] is available for connector X1 and X2 that can integrate with the [[Harness_specifications|Autosport Labs plug and play harness system]]. This pigtail can provide power + CAN data to the board.

[[file:ESP32_CAN_X2_with_plug_and_play_harness_closeup.jpg|400px]] [[file:ESP32_CAN_X2_with_plug_and_play_harness-scaled.jpg|400px]]

=Flashing Firmware=

Firmware flashing in this development board is straightforward. The following components are required for firmware flashings.

'''Hardware Components'''

* USB-C cable
* Computer running Windows, Linux, or macOS
 

'''Software Components'''

* Updated Arduino IDE to compile code for ESP-32-X2.
* Update Mu Editor from codewith.mu
 
Note : Link to download Arduino IDE : https://www.arduino.cc/en/software || Link to download Mu Editor : codewith.mu

== Step by step instruction for Arduino IDE==

===Sample Arduino Project===
https://github.com/autosportlabs/ESP32-CAN-X2

Step-by-step instructions for flashing ESP-32-X2 are as follows.

'''Install ESP-32-X2 Board Support:'''

Adding ESP-32-X2 in Arduino Ide is a single-time process and its steps are as follows.

* Open Arduino Ide
* Go to File > Preferences
 

[[File:Flashing1.png| Figure 7|800px]]

* Add the below given Json URL in the Additional board manager URL

Json URL : https://espressif.github.io/arduino-esp32/package_esp32_index.json
 
[[File:ESPBSP1.png|Figure 8|800px]]

* Go to Tools > Board > Boards Manager
 

[[File:Flashing3.png|Figure 9|800px]]

* In the Board Manager search bar, type ESP-32, search for esp32 by Espressif and click on install to install the board
 
[[File:ESPBSP2.png|Figure 10|800px]]

* After installing, click on Tool > Boards and select AutosportLabs ESP32-CAN-X2
 
'''Flashing'''

* Connect the ESP-32-X2 board to your computer using a USB-C cable with your Arduino IDE open

* Select AutosportLabs ESP32-CAN-X2 in Tools > Board menu

* Go to Tools > Port and select the COM port to which ESP-32-X2 is connected.

[[File:ArduinoFlashing3.png|Figure 11|800px]]
 
Note : If you don’t see the COM Port in your Arduino IDE, you need to install the CP210x USB to UART Bridge VCP Drivers: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
 

* Write your firmware code or add an existing sketch that you want to upload to your custom board.

* Go to Sketch > Click upload to compile and upload the code

* After successful uploading, you should see a “Done uploading.” message at the bottom console. This console will also show error messages if there is any error.

[[File:ArduinoFlashing4...png|Figure 12|800px]]

If any issues occur during upload, double-check the board selection, COM port, and your code for errors.
<be>

===Importing Libraries in Arduino IDE===

* To Install Libraries for ESP32-CAN-X2 like mcp_canbus or mcp2515
* Go to Sketch > Include Library > Manage LibrarieSs

[[File:Arduino IDE Library 1.png]]

* Type and find the desired library like mcp_canbus by Longan Labs
* Search and Install the library

[[File:Arduino IDE Library 2...png]]

== Step-by-step instruction for CircuitPython==
===Sample CircuitPython code===
https://github.com/autosportlabs/ESP32-CAN-X2

'''Downloading ESP-32-X2 Board Support:''' 

Installing ESP-32-X2 is simple, please follow the steps given below :

* Go to circuitpython.org/board/autosportlabs_esp32_can_x2
Click on the browse S3 

[[File:CircuitpythonFlashing1.png|800px]] 

* Select the desired language 
 

[[File:CircuitpythonFlashing2.png|800px]]
* Download the latest .bin file
 

[[File:CircuitpythonFlashing4.png|800px]]

'''Prepare the ESP32 CAN X2 for Installation:''' 

* Connect the ESP-32-X2 board to your computer using a USB-C cable
* Press and hold the boot button on the development board.
* While holding the boot button, press and release the reset button once.
* Release the boot button to put the board into bootloader mode.
[[File:REV D Flashing Image.png|800px]]

'''Connect to the Web Serial ESP Tool'''

* Go to : https://adafruit.github.io/Adafruit_WebSerial_ESPTool/
* Press the Connect button in the top right corner of the page.
* A pop-up will appear asking you to select the COM or Serial port.
* Look for an option with ESP32, JTAG Loader, SLAB, or FTDI in the name
 

[[File:CircuitpythonFlashing6.png|800px]]

'''Flash the Firmware'''

* Click on Choose the .bin file you downloaded.
* Ensure that the Offset box next to the file location is set to 0x0.
* After selecting the file, the button text will change to match your filename.
* Click the Program button to start flashing. A progress bar will appear, and after a minute or two, the firmware will be
written.

[[File:Circuytpython7.gif|800px]]

'''Exit Bootloader Mode'''
* Press the reset button to exit bootloader mode. Shortly, the CIRCUITPY drive will pop up.

'''Downloading and Installing Mu Editor'''
* Download and install the recommended Mu Editor from codewith.mu.
* When you first start Mu, you will be prompted to select your mode. Select CircuitPython.
 
[[File:Mudownload.png|800px]]

* In Mu editor, click the Load button in the button bar, navigate to the CIRCUITPY drive, and choose code.py.
 
[[File:MU2.png|800px]]

'''Note :''' The CIRCUITPY drive is where your code and necessary libraries will reside. With a fresh CircuitPython install, the CIRCUITPY drive will contain a code.py file with print("Hello World!") and an empty lib folder. If your CIRCUITPY drive does not have a code.py file, create one and save it to the drive. CircuitPython automatically executes the code in code.py when the board starts up or resets. Do not press reset immediately after saving your code it will corrupt the drive and you may lose your code.

* Enter your code into the editor and save the code.py file on the CIRCUITPY drive.
 

[[File:MU3.png|800px]]

'''Congratulations!''' You have just run your first CircuitPython program.

=== Importing Libraries in Circuitpython ===

Importing libraries in Circuitpython is straightforward. For installing Libraries in Circuitpython, please follow the steps given below :
* Go to https://circuitpython.org/libraries and download the bundle for version 9.xx.
'''Note:''' The version of the bundle should be the same that you are using.
 

[[File:Mu4.png|800px]]

* Extract the zip file.
* Find the lib file where you can find your desired library.
* Copy that library folder or .mpy file and paste it to the lib folder in CIRCUITPY drive
 

[[File:Mueditor Library.gif|800px]]

=ESP32-CAN-X2 Rev-C=
[https://wiki.autosportlabs.com/ESP32-CAN-X2/RevC#6_pin_JST-PH_Connector ESP32-CAN-X2 Rev-C]

File:ESP32 CAN X2 with plug and play harness-scaled.jpg

2026-04-28T23:54:27Z

Brentp:

File:ESP32 CAN X2 with plug and play harness closeup.jpg

2026-04-28T23:53:26Z

Brentp:

File:ASL M8 4P MALE CAN PH.jpg

2026-04-28T23:53:10Z

Brentp:

RaceCaptureTrack MK4

2026-04-14T04:28:07Z

Brentp: /* Connecting to RaceCapture System Dashboard */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

See the guide for [[RaceCapturePro_Sensors#IMU_(Accelerometer_/_Gyro)|remapping the IMU channels for alternate mounting orientations]].

'''Additional Notes:'''
* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your RaceCapture to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 123456. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.

=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Real-time Telemetry Setup ==
This section explains how to configure your device to stream live telemetry data to the Podium cloud service so it can be viewed remotely using the Podium app or the Podium website.

=== Overview ===
Three components are used when working with live telemetry:

* RaceCapture App : Used to connect directly to the device for configuration and local dashboard viewing.
* Podium App : Used to view live telemetry and previously recorded sessions in the cloud.
* Podium Website : Provides web access to the same telemetry data available in the Podium app.

=== Step 1 : Configure WiFi Connectivity ===
[[File:Inital setup.gif|750px]]
* Open the RaceCapture app and connect to your device.
* Navigate to Setup from the main screen.
* Click Read to load the current configuration.
* Select the Wireless tab.
** Configure the following settings:
*** Enable WiFi Support
*** Enable Client Mode
*** Enter the SSID and password for your hotspot or WiFi network
'''Note:''' The hotspot must support 2.4 GHz WiFi. Many hotspots default to 5 GHz, which is not supported. If necessary, configure your hotspot to allow 2.4 GHz operation.
For testing purposes, you may use your phone’s hotspot to confirm the connection is working correctly.
* Enable WiFi Telemetry at the bottom of the Wireless settings.
[[File:Enable wifi telemetry option.png|750px]]

=== Step 2 : Configure the Telemetry Streaming Key ===
[[File:Telemetry streaming key updated.gif|750px]]

To stream telemetry to Podium, you must enter a Telemetry Streaming Key.
* Open the Podium website.
* Navigate to Settings → Devices.
* Select your device from the list.
* Copy the Streaming Key shown for the device.
Return to the RaceCapture app:
* Navigate to the Telemetry tab.
* Paste the Streaming Key into the Telemetry Streaming Key field.

=== Step 3 : Configure Streaming Behavior ===
[[File:Background streaming key.png|750px]]

For testing or continuous streaming '''Enable Background Streaming'''.
This causes the device to begin telemetry streaming immediately after power-up. If Background Streaming is disabled, telemetry streaming will begin only when the system starts logging based on its configured trigger (typically vehicle speed, but other channels such as RPM may be used). This helps prevent unnecessary telemetry transmission when the vehicle is powered but not actively driving.

=== Step 4: Apply Configuration and Reboot===
Click Write to save the configuration to the device.

[[File:Configuration (write).png|750px]]

Reboot the device by either:
* Power cycling the unit, or
[[File:Rebot.png|750px]]
* Navigating to Setup > Firmware > Reboot.

=== Step 5 : Verify WiFi Connection ===
[[File:Verify WiFi Connection gif file.gif|750px]]

After rebooting:
* Navigate to System Status > WiFi.
* Confirm the WiFi Client is connected to the hotspot.

=== Step 6 : Confirm Telemetry Streaming ===
If telemetry streaming is active:
* The blue telemetry LED on the device will blink.
* This indicates the system is transmitting telemetry to Podium.
=== Viewing Live Telemetry ===
==== Podium Website ====

[[File:Viewing Live Telemetry podium website.gif|750px]]

* Open the Podium website.
* Navigate to Events.
* Locate the automatically generated live event for your device.
* Open the event to view live telemetry data.
* You should see real-time channel updates such as:
** IMU motion
** G-forces
** Sensor values

==== Podium App ====

The Podium app provides a richer telemetry viewing experience.

# Open the Podium app.
# Navigate to Events > Live Events.
# Select your device.

From here you can:
* View live dashboards
* Switch dashboard views
* Monitor individual telemetry channels

Dashboards can be:
* Selected from built-in presets
* Custom created and saved
* Shared by the community

=== Track Detection and Lap Timing ===

For automatic lap timing, ensure your track is added in Podium.
# Navigate to Racetracks.
# Add the tracks where you typically race.
When the system detects a known track, Podium will automatically enable:
* Lap timing
* Lap-based telemetry analysis
This allows session data to be viewed and analyzed in the context of laps.

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
Your system logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.

=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from your system.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

BMW E36 Guide

2026-04-13T16:31:20Z

Brentp: /* Fuel Level */

=BMW E36 (1990 - 1999)=
[[Image:e36_race_car.jpg|500px]]

==RPM==
Use the wire connected to the instrument cluster #20, black wire. Also available on the round diagnostic connector at the back of the engine compartment (black wire, Pin #1)
===RaceCapture/Pro Timer RPM Configuration===
* Timer Mode: RPM
* Timer Speed: Medium
* Pulse Per Revolution: 3

==TPS==

Pin 2 (Black/Brown wire) of the Throttle Position Sensor is the voltage reference. Connect this wire to an analog input on your RaceCapture system.

Typical voltage values. You may need to measure this on your engine:
* 0.62 volts at 0% throttle
* 4.64 volts at 100%

Configure a linear mapping in the analog input where the first bin is 0.62 volts / 0 scaled value; 2nd bin is 4.64 volts / 100 scaled value. Repeat the 2nd bin values for bins 3, 4 and 5.

==Engine Temperature==
''In research''

Should be similar to [[BMW_E30_Guide#Engine_Temperature|E30]]

==Fuel Level==
* [http://www.bimmerforums.com/forum/showthread.php?1718687-Stock-fuel-level-sender-output-V-wiring-Integration-to-AIM-MXL Forum discussion]
*[https://www.facebook.com/groups/1041375552601984/permalink/1041384422601097/ Facebook Discussion]

Tap the brown/yellow wire that is in the small connector on the back of the dash closest to
the driver's door.

'''Note''': This assumes the factory gauge is still connected.

Mapping in the analog channel
*0.2v = 0 (empty)
*1.33v = 25 (1/4)
*2.2v = 50 (half)
*2.95v = 75 (3/4)
*3.53v = 100 (full)

[[file:BMW_E36_fuel_level_curve.png]]

==Brakes==
*Tap the Blue/Red wire coming out of the brake light switch on the back of the brake pedal. Wire this to a digital GPIO input of RaceCapture. Note: Must use a 10k Ohm resistor between the GPIO input and brake light wire.

*Can be helpful to know when the driver actually applies the brakes for data analysis of the driver. This gives you a simple yes/no of whether the driver is on the brakes. Lets you know exactly when they applied the brakes. Use this in conjunction with TPS to see how much time they are 'coasting', or how long it takes them to transition from throttle to brakes and vice versa.

==Oil Pressure==
Recommend a dedicated 10 bar / 145 PSI 0.5-4.5v pressure sensor. [https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/ Pressure Sensor]

==OBDII==
You can get a few channels from the OBDII port of the E36 using the [https://www.autosportlabs.com/product/obdii-legacy-adapter/ ASL Legacy OBDII Cable], but it is fairly slow to update. Useful channels are RPM, EngineTemp, and TPS. See the [[RaceCapturePro2_OBD2|Enabling OBD-II Guide]]. It is also possible to [[RaceCapturePro_Lua_Scripting_Examples#Display_OBDII_Codes_as_a_channel_and_allow_driver_to_reset_the_OBDII_Codes_with_a_button|read and clear OBDII trouble/diagnostic codes via Lua Script]].

Available Sensors:
*RPM
*EngineTemp
*TPS
*IAT (needs to be converted to F)
*WheelSpeed (needs to be converted to MPH)
*MAF
*EngineLoad
*FuelFlowRate
*Timing

==Road speed (differential speed sensor based)==

This calculates gear and speed based on the differential speed sensor.

Assumes:
* Engine RPM is connected to the first timer input.
* Differential speed pulse is connected to the 2nd timer input

The differential speed signal is on a black w/ white stripe wire and can be found in the following location:
* Pin 2 on connector X17 to the back of the gauge cluster
* Pin 10 on connector X22 on the cruise control module behind the glove box
* Pin 10 on radio connector

<pre>
setTickRate(10) --10Hz

--virtual channels
--addChannel("name",SR,prec,min,max,"unit")
speeddiff_id = addChannel("Speed_",10,0,0,160,"MPH")
gear_id = addChannel("Gear_",5,0,0,5,"gear")

--global constants
--edit these to match your car
first = 4.20
second = 2.49
third = 1.66
fourth = 1.24
fifth = 1.00
final = 3.46
tirediameter = 24.7

--global variables
rpm = 0
rpm_diff = 0
speed = 0

function updateSpeedDiff()
rpm_diff = getTimerRpm(1)
speed = rpm_diff*tirediameter*0.002975
speed = speed + 0.5 -- round because 0 prec. truncates
setChannel(speeddiff_id, speed)
end

function updateGear()
rpm = getTimerRpm(0)
local gearErr = 0.15
local gear = 0

if speed > 2 then
ratio = rpm/(rpm_diff*final)
if ((first - ratio)^2) < (gearErr^2) then gear = 1 end
if ((second - ratio)^2) < (gearErr^2) then gear = 2 end
if ((third - ratio)^2) < (gearErr^2) then gear = 3 end
if ((fourth - ratio)^2) < (gearErr^2) then gear = 4 end
if ((fifth - ratio)^2) < (gearErr^2) then gear = 5 end
end
setChannel(gear_id, gear)
end

function onTick()
updateSpeedDiff()
updateGear()
end
</pre>

=External Reference=
* [http://www.scribd.com/doc/247124381/1998-BMW-E36-Electrical-Wiring-Diagram#scribd BMW E36 Wiring Diagram]
* [http://wedophones.com/Manuals/BMW/1996%20BMW%20318is-c%20-%20320i%20-%20325i-c%20-%20328i-c%20%20Electrical%20Troubleshooting%20Manual.pdf Wiring Troubleshooting Manual]

BMW E36 Guide

2026-04-07T15:38:07Z

Brentp: /* Oil Pressure */

=BMW E36 (1990 - 1999)=
[[Image:e36_race_car.jpg|500px]]

==RPM==
Use the wire connected to the instrument cluster #20, black wire. Also available on the round diagnostic connector at the back of the engine compartment (black wire, Pin #1)
===RaceCapture/Pro Timer RPM Configuration===
* Timer Mode: RPM
* Timer Speed: Medium
* Pulse Per Revolution: 3

==TPS==

Pin 2 (Black/Brown wire) of the Throttle Position Sensor is the voltage reference. Connect this wire to an analog input on your RaceCapture system.

Typical voltage values. You may need to measure this on your engine:
* 0.62 volts at 0% throttle
* 4.64 volts at 100%

Configure a linear mapping in the analog input where the first bin is 0.62 volts / 0 scaled value; 2nd bin is 4.64 volts / 100 scaled value. Repeat the 2nd bin values for bins 3, 4 and 5.

==Engine Temperature==
''In research''

Should be similar to [[BMW_E30_Guide#Engine_Temperature|E30]]

==Fuel Level==
* [http://www.bimmerforums.com/forum/showthread.php?1718687-Stock-fuel-level-sender-output-V-wiring-Integration-to-AIM-MXL Forum discussion]
*[https://www.facebook.com/groups/1041375552601984/permalink/1041384422601097/ Facebook Discussion]

Tap the brown/yellow wire that is in the small connector on the back of the dash closest to the driver's door.

Mapping in RCP
*0.2v = 0 (empty)
*1.33v = 25 (1/4)
*2.2v = 50 (half)
*2.95v = 75 (3/4)
*3.53v = 100 (full)

[[file:BMW_E36_fuel_level_curve.png]]

==Brakes==
*Tap the Blue/Red wire coming out of the brake light switch on the back of the brake pedal. Wire this to a digital GPIO input of RaceCapture. Note: Must use a 10k Ohm resistor between the GPIO input and brake light wire.

*Can be helpful to know when the driver actually applies the brakes for data analysis of the driver. This gives you a simple yes/no of whether the driver is on the brakes. Lets you know exactly when they applied the brakes. Use this in conjunction with TPS to see how much time they are 'coasting', or how long it takes them to transition from throttle to brakes and vice versa.

==Oil Pressure==
Recommend a dedicated 10 bar / 145 PSI 0.5-4.5v pressure sensor. [https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/ Pressure Sensor]

==OBDII==
You can get a few channels from the OBDII port of the E36 using the [https://www.autosportlabs.com/product/obdii-legacy-adapter/ ASL Legacy OBDII Cable], but it is fairly slow to update. Useful channels are RPM, EngineTemp, and TPS. See the [[RaceCapturePro2_OBD2|Enabling OBD-II Guide]]. It is also possible to [[RaceCapturePro_Lua_Scripting_Examples#Display_OBDII_Codes_as_a_channel_and_allow_driver_to_reset_the_OBDII_Codes_with_a_button|read and clear OBDII trouble/diagnostic codes via Lua Script]].

Available Sensors:
*RPM
*EngineTemp
*TPS
*IAT (needs to be converted to F)
*WheelSpeed (needs to be converted to MPH)
*MAF
*EngineLoad
*FuelFlowRate
*Timing

==Road speed (differential speed sensor based)==

This calculates gear and speed based on the differential speed sensor.

Assumes:
* Engine RPM is connected to the first timer input.
* Differential speed pulse is connected to the 2nd timer input

The differential speed signal is on a black w/ white stripe wire and can be found in the following location:
* Pin 2 on connector X17 to the back of the gauge cluster
* Pin 10 on connector X22 on the cruise control module behind the glove box
* Pin 10 on radio connector

<pre>
setTickRate(10) --10Hz

--virtual channels
--addChannel("name",SR,prec,min,max,"unit")
speeddiff_id = addChannel("Speed_",10,0,0,160,"MPH")
gear_id = addChannel("Gear_",5,0,0,5,"gear")

--global constants
--edit these to match your car
first = 4.20
second = 2.49
third = 1.66
fourth = 1.24
fifth = 1.00
final = 3.46
tirediameter = 24.7

--global variables
rpm = 0
rpm_diff = 0
speed = 0

function updateSpeedDiff()
rpm_diff = getTimerRpm(1)
speed = rpm_diff*tirediameter*0.002975
speed = speed + 0.5 -- round because 0 prec. truncates
setChannel(speeddiff_id, speed)
end

function updateGear()
rpm = getTimerRpm(0)
local gearErr = 0.15
local gear = 0

if speed > 2 then
ratio = rpm/(rpm_diff*final)
if ((first - ratio)^2) < (gearErr^2) then gear = 1 end
if ((second - ratio)^2) < (gearErr^2) then gear = 2 end
if ((third - ratio)^2) < (gearErr^2) then gear = 3 end
if ((fourth - ratio)^2) < (gearErr^2) then gear = 4 end
if ((fifth - ratio)^2) < (gearErr^2) then gear = 5 end
end
setChannel(gear_id, gear)
end

function onTick()
updateSpeedDiff()
updateGear()
end
</pre>

=External Reference=
* [http://www.scribd.com/doc/247124381/1998-BMW-E36-Electrical-Wiring-Diagram#scribd BMW E36 Wiring Diagram]
* [http://wedophones.com/Manuals/BMW/1996%20BMW%20318is-c%20-%20320i%20-%20325i-c%20-%20328i-c%20%20Electrical%20Troubleshooting%20Manual.pdf Wiring Troubleshooting Manual]

RacecapturePro MK4 hardware install

2026-04-03T20:50:47Z

Brentp: /* Mounting Orientation */

=Installation=

==Mounting Orientation==

The system can be mounted in various orientations to suit your needs. However, for optimal performance of the accelerometer and gyroscope, it is recommended to mount the system horizontally flat with the indicators facing the driver. After mounting, you can zero out the channels by performing calibration in the Setup section under Accel/Gyro.

''' Recommended Orientation''' 

Horizontally Flat Indicators facing toward the driver

[[File:Mounting Orientation.png]]

===Alternate mounting orientations===
See the guide for [[RaceCapturePro_Sensors#IMU_(Accelerometer_/_Gyro)|remapping the IMU channels for alternate mounting orientations]].

==Mounting Dimensions==

The mounting dimensions of Racecapture Pro Mk4 are given in the image below.

[[File:Mounting Dimensions.png]]

=Connections=

[[File:Connections.png]]

The RaceCapturePro MK4 has 5 connectors, detailed as follows from left to right:

# 12-pin female M12 connector for digital input and RPM sensors.
# SMA connector for GPS antenna connection.
# 12-pin female M12 connector for analog input devices.
# 6-pin female M8 connector for CAN1, CAN2, and power connections.
# 4-pin female M8 connector for CAN1 and power connections.
 
The detailed explanations of connector pinouts are given below.

==Full harness specifications==
See the full plug and play [[Harness_specifications|Wiring harness specifications]] detailing all cables, adapters, and interconnects available for your system.

==M12 Analog / Digital Connectors==
[[File:M12 Pin.png]]

{| class="wikitable"
|+ M12 Analog / Digital ConnectorsCaption text
|-
! Pin !! Connection !! Analog Mapping !! Digital Mapping
|-
| 1 || Analog/Digital B1 || Analog 5 || GPIO 1
|-
| 2 || Analog/Digital B2 || Analog 6 || GPIO 2
|-
| 3 || Analog/Digital B4 || Analog 8 || GPIO 4
|-
| 4 || Analog/Digital A1 || Analog 1 || Timer/RPM 1
|-
| 5 || Analog/Digital A2 || Analog 2 || Timer/RPM 2
|-
| 6 || Vref || 5v @ 0.5A || 5v @ 0.5A
|-
| 7 || Analog/Digital A3 || Analog 3 || Timer/RPM 3
|-
| 8 || Analog/Digital A4 || Analog 4 || Timer/RPM 4
|-
| 9 || Analog/Digital B || Analog 7 || GPIO 3
|-
| 10 || Ground || ||
|-
| 11 || Ground || ||
|-
| 12 || Ground || ||
|}

==M8 Connector 4-Pin CAN1+Power==

[[File:M8 4-Pin.png]]

{| class="wikitable"
|+ M8 Connectors 4-Pin CAN1+Power
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN 1 low ||
|-
| 2 || Power || 9-24v / 1A (~12W)
|-
| 3 || CAN 1 high ||
|-
| 4 || Ground ||
|}

==M8 Connector 6-Pin CAN1 + CAN2 + Power==

[[File:M8 6-Pin.png]]

{| class="wikitable"
|+ M8 Connectors 4-Pin CAN1+Power
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN 1 low ||
|-
| 2 || CAN 2 low ||
|-
| 3 || CAN 2 high ||
|-
| 4 || Ground ||
|-
| 5 || CAN 1 high ||
|-
| 6 || Power || 9-24v / 1A (~12W)
|}

==OBDII CAN cable==

Connecting the Racecapture MK4 to your vehicle's OBDII port is straightforward. The provided M8 connector allows you to easily plug in the OBDII cable using an M8 male to OBDII adapter. This makes for a convenient plug-and-play setup, with no additional connections needed.

[[File:M8 male to OBDII.png]]

==SMA Connector==

Connect the included GPS antenna to this port.
'''Note:''' Tighten this connection to 5-6 inches/lbs (just beyond finger tight). Do not over-torque

[[File:SMA Connector.png]]

===Antenna Placement Guide===

For optimal GPS reception, install a GPS antenna with a clear 360-degree view of the sky, such as on the roof of the vehicle.

=Powering=
Connect RaceCapture/Pro to a 12V power source, ideally using a switched OBD-II cable.

==Power Requirements==

{| class="wikitable" style="text-align:center; width:700px; height:100px;"
|+ Power requirements
|-
| Voltage
| 9-24v
|-
| Current
| 1A (~12W)
|}

=Sensor Connectivity=
==Analog Inputs pins==

{| class="wikitable"
|+ Analog Channel Speccifications
|-
| Channels || 9 analog input channels, with 8 external and 1 internal for monitoring battery or supply voltage
|-
| Voltage Range || 0-5V
|-
| Input Impedance || Greater than 1M ohm
|-
| Voltage Protection || Up to 400V (intermittent)
|-
| ADC Precision || 12-bit
|-
| Maximum Sample Rate || 1000Hz
|-
| Mapping || Can be configured as Raw, using a linear formula, or an interpolated map
|}

'''Note:''' You can use an analog port to monitor the states of 12V switches, lights, or other 5V-12V On/Off devices. It is recommended to use an inline 10K 1/4 watt resistor to ensure proper functioning and protection of the system. The input should be mapped such that a voltage range of 0-3.0V corresponds to a state of 0, and a voltage range of 3.01V and above corresponds to a state of 1. Even when 12V is applied, the system will display a maximum of approximately 5V, ensuring safe monitoring and accurate state detection of the connected devices.

[[File:Analog Pins.png]]

===Guides===
* See our comprehensive [https://wiki.autosportlabs.com/RaceCapturePro_Sensors Sensor Guide] for information on connecting various types of analog sensors.
* Also see our guide on [https://wiki.autosportlabs.com/RaceCapturePro_Calibrate_Sensor Calibrating an Analog Sensor]

==Frequency / RPM Input==
You can connect RPM, wheel speed, and other pulse-type sensors to the RaceCapture/Pro frequency input pins. These inputs are designed to handle various types of frequency-based signals, providing accurate and reliable data for performance monitoring and analysis.

{| class="wikitable"
|+ Frequency / RPM Input Specifications
|-
| Input Impedance || Greater than 1M ohm
|-
| Voltage Protection || Up to 400V (intermittent)
|-
| ADC Precision|| 12-bit
|-
| Maximum Sample Rate || 1000Hz (logging to SD card)
|-
| Mapping Supported|| The input signals can be mapped to RPM, frequency, or period measurements.
|}

===Signal input quality===
To ensure accurate measurements, verify that the source provides a relatively clean pulse signal transitioning between 0 and 5-12 volts. Clean signals are essential for precise and reliable data acquisition.

====Special note about RPM inputs====
For the best performance and reliability, it is preferred to obtain a clean RPM signal directly from the engine's ECU (Engine Control Unit). This approach minimizes the risk of noise and ensures a more stable signal.
* Verify if the signal you're tapping is driving the ignition coil directly, or if it's feeding into an igniter. If it's powering the coil directly, use the [https://wiki.autosportlabs.com/CoilX CoilX] module to buffer/filter the high-voltage signal.
* If uncertain, visualize the RPM signal using an oscilloscope - you should see a relatively clean square wave as the source.
* If your only source for RPM is the trigger wire driving the ignition coil primary winding, then you will need the [https://wiki.autosportlabs.com/CoilX CoilX] module to buffer/filter the noisy, high-voltage component.
[[File:RPM_input.png]]

==GPIO==
RaceCapture/Pro provides 4 General Purpose Input Output (GPIO) ports that can be used to control devices in output mode or read switches and high/low states of electrical signals in input mode.

{| class="wikitable"
|+ GPIO Specifications
|-
| Output Mode Type || Open Drain
|-
| Output Current Capacity || 1A, inductively clamped
|-
| Input Mode Voltage Range || 0-12V
|-
| Input Voltage Protection || 0-40V
|-
| Maximum Sample Rate || 1000Hz
|}

===Input Mode===
When configured for input mode, the RaceCapture/Pro sensor input will register a '1' when the input passes a voltage threshold of approximately 3V, and '0' when the input is low (close to 0 volts).

'''Important Note:''' When sensing large inductive loads, such as the state of brake lights or the on/off state of a motor, it is recommended to connect a '''10K 1/4 watt resistor''' in line with the GPIO input. This resistor helps protect RaceCapture/Pro from large inductive spikes, ensuring the longevity and reliability of the system.

===Output Mode===
When configured for output mode, RaceCapture connects that port to the ground and can sink a 1A load per port, which suitable for driving indicators, relays, sending signals to other systems, and driving small devices. [https://wiki.autosportlabs.com/GPIO_Output Click here for more info]

'''Output Behavior:'''
* When the port is active, the port will connect to the ground
* When the port is inactive, the port will be an open circuit.

[[File:GPIO Output Behavior.png]]

===Controlling GPIO Ports===
GPIO channels in output mode are controlled by the logic you create with the on-board Lua scripting capability.
See the [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting#General_Input_.2F_Output_.28GPIO.29_Functions GPIO section of the Lua Scripting reference] and collection of [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting_Examples Examples].

=Communications=
RaceCapture/Pro is equipped with multiple CAN bus networks to facilitate communication with various devices. There is a standard convention for selecting which CAN bus to use when connecting devices:
* '''CAN1:''' Typically used for connecting Engine Control Units (ECUs), including OBD-II interfaces and after-market ECUs. This CAN bus network is often utilized for critical vehicle data and diagnostics.
* '''CAN2:''' Typically used for extended sensor networks, such as AnalogX for analog sensors, TireX for tire pressure monitoring, and other peripheral sensors. These networks provide additional communication channels for expanded data acquisition and monitoring.

==CAN Bus Splitter==
The M8-6P male connector splits the CAN bus networks into individual CAN1 and CAN2 connections using dual M8-4P female connectors. This splitter allows you to connect devices to the specific CAN buses as needed:
* '''A Connection:''' Connects to CAN1
* '''B Connection:''' Connects to CAN2

'''Note:''' The CAN bus connections provide limited power (1A @ 12V) to devices connected to CAN1 and CAN2. For devices requiring higher power, it is recommended to use the Powered Dual CAN Hub. The Powered Dual CAN Hub provides additional power and helps ensure stable operation for connected devices.

[[File:CAN Connection 1.png|700px]]

See the [https://wiki.autosportlabs.com/RCP_CAN CAN bus / ECU integration guide] for information on integrating CAN bus communications and CAN channel mapping.

==CAN channel specifications==

{| class="wikitable"
|+ CAN channel specifications
|-
| Can Channel || 2
|-
| CAN Baud Rate || 125K, 250K, 500K, 1M Baud
|-
| CAN Filter || 14 per channel
|-
| Protocol Support || OBDII PID, custom CAN mapping
|-
| CAN bus compatibility || CAN 2.0 compatible, 1M baud
|-
| CAN termination || Software controlled
|}

RacecapturePro MK4 hardware install

2026-04-03T20:50:11Z

Brentp: /* Mounting Orientation */

=Installation=

==Mounting Orientation==

The system can be mounted in various orientations to suit your needs. However, for optimal performance of the accelerometer and gyroscope, it is recommended to mount the system horizontally flat with the indicators facing the driver. After mounting, you can zero out the channels by performing calibration in the Setup section under Accel/Gyro.

===Alternate mounting orientations===
See the guide for [[RaceCapturePro_Sensors#IMU_(Accelerometer_/_Gyro)|remapping the IMU channels for alternate mounting orientations]].

''' Recommended Orientation''' 

Horizontally Flat Indicators facing toward the driver

[[File:Mounting Orientation.png]]

'''Alternate Orientations''' 

If needed, the system can also be mounted in alternate orientations. Ensure that any alternate mounting is square to the orientation of the car. Some examples include:
* Upside Down
* Vertical / On Edge

'''Calibration and Remapping''' 

When an alternate mounting orientation is chosen, it is crucial to remap the accelerometer and gyroscope channels to accurately reflect this change. This can be done in the Setup section under Accel/Gyro.

==Mounting Dimensions==

The mounting dimensions of Racecapture Pro Mk4 are given in the image below.

[[File:Mounting Dimensions.png]]

=Connections=

[[File:Connections.png]]

The RaceCapturePro MK4 has 5 connectors, detailed as follows from left to right:

# 12-pin female M12 connector for digital input and RPM sensors.
# SMA connector for GPS antenna connection.
# 12-pin female M12 connector for analog input devices.
# 6-pin female M8 connector for CAN1, CAN2, and power connections.
# 4-pin female M8 connector for CAN1 and power connections.
 
The detailed explanations of connector pinouts are given below.

==Full harness specifications==
See the full plug and play [[Harness_specifications|Wiring harness specifications]] detailing all cables, adapters, and interconnects available for your system.

==M12 Analog / Digital Connectors==
[[File:M12 Pin.png]]

{| class="wikitable"
|+ M12 Analog / Digital ConnectorsCaption text
|-
! Pin !! Connection !! Analog Mapping !! Digital Mapping
|-
| 1 || Analog/Digital B1 || Analog 5 || GPIO 1
|-
| 2 || Analog/Digital B2 || Analog 6 || GPIO 2
|-
| 3 || Analog/Digital B4 || Analog 8 || GPIO 4
|-
| 4 || Analog/Digital A1 || Analog 1 || Timer/RPM 1
|-
| 5 || Analog/Digital A2 || Analog 2 || Timer/RPM 2
|-
| 6 || Vref || 5v @ 0.5A || 5v @ 0.5A
|-
| 7 || Analog/Digital A3 || Analog 3 || Timer/RPM 3
|-
| 8 || Analog/Digital A4 || Analog 4 || Timer/RPM 4
|-
| 9 || Analog/Digital B || Analog 7 || GPIO 3
|-
| 10 || Ground || ||
|-
| 11 || Ground || ||
|-
| 12 || Ground || ||
|}

==M8 Connector 4-Pin CAN1+Power==

[[File:M8 4-Pin.png]]

{| class="wikitable"
|+ M8 Connectors 4-Pin CAN1+Power
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN 1 low ||
|-
| 2 || Power || 9-24v / 1A (~12W)
|-
| 3 || CAN 1 high ||
|-
| 4 || Ground ||
|}

==M8 Connector 6-Pin CAN1 + CAN2 + Power==

[[File:M8 6-Pin.png]]

{| class="wikitable"
|+ M8 Connectors 4-Pin CAN1+Power
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN 1 low ||
|-
| 2 || CAN 2 low ||
|-
| 3 || CAN 2 high ||
|-
| 4 || Ground ||
|-
| 5 || CAN 1 high ||
|-
| 6 || Power || 9-24v / 1A (~12W)
|}

==OBDII CAN cable==

Connecting the Racecapture MK4 to your vehicle's OBDII port is straightforward. The provided M8 connector allows you to easily plug in the OBDII cable using an M8 male to OBDII adapter. This makes for a convenient plug-and-play setup, with no additional connections needed.

[[File:M8 male to OBDII.png]]

==SMA Connector==

Connect the included GPS antenna to this port.
'''Note:''' Tighten this connection to 5-6 inches/lbs (just beyond finger tight). Do not over-torque

[[File:SMA Connector.png]]

===Antenna Placement Guide===

For optimal GPS reception, install a GPS antenna with a clear 360-degree view of the sky, such as on the roof of the vehicle.

=Powering=
Connect RaceCapture/Pro to a 12V power source, ideally using a switched OBD-II cable.

==Power Requirements==

{| class="wikitable" style="text-align:center; width:700px; height:100px;"
|+ Power requirements
|-
| Voltage
| 9-24v
|-
| Current
| 1A (~12W)
|}

=Sensor Connectivity=
==Analog Inputs pins==

{| class="wikitable"
|+ Analog Channel Speccifications
|-
| Channels || 9 analog input channels, with 8 external and 1 internal for monitoring battery or supply voltage
|-
| Voltage Range || 0-5V
|-
| Input Impedance || Greater than 1M ohm
|-
| Voltage Protection || Up to 400V (intermittent)
|-
| ADC Precision || 12-bit
|-
| Maximum Sample Rate || 1000Hz
|-
| Mapping || Can be configured as Raw, using a linear formula, or an interpolated map
|}

'''Note:''' You can use an analog port to monitor the states of 12V switches, lights, or other 5V-12V On/Off devices. It is recommended to use an inline 10K 1/4 watt resistor to ensure proper functioning and protection of the system. The input should be mapped such that a voltage range of 0-3.0V corresponds to a state of 0, and a voltage range of 3.01V and above corresponds to a state of 1. Even when 12V is applied, the system will display a maximum of approximately 5V, ensuring safe monitoring and accurate state detection of the connected devices.

[[File:Analog Pins.png]]

===Guides===
* See our comprehensive [https://wiki.autosportlabs.com/RaceCapturePro_Sensors Sensor Guide] for information on connecting various types of analog sensors.
* Also see our guide on [https://wiki.autosportlabs.com/RaceCapturePro_Calibrate_Sensor Calibrating an Analog Sensor]

==Frequency / RPM Input==
You can connect RPM, wheel speed, and other pulse-type sensors to the RaceCapture/Pro frequency input pins. These inputs are designed to handle various types of frequency-based signals, providing accurate and reliable data for performance monitoring and analysis.

{| class="wikitable"
|+ Frequency / RPM Input Specifications
|-
| Input Impedance || Greater than 1M ohm
|-
| Voltage Protection || Up to 400V (intermittent)
|-
| ADC Precision|| 12-bit
|-
| Maximum Sample Rate || 1000Hz (logging to SD card)
|-
| Mapping Supported|| The input signals can be mapped to RPM, frequency, or period measurements.
|}

===Signal input quality===
To ensure accurate measurements, verify that the source provides a relatively clean pulse signal transitioning between 0 and 5-12 volts. Clean signals are essential for precise and reliable data acquisition.

====Special note about RPM inputs====
For the best performance and reliability, it is preferred to obtain a clean RPM signal directly from the engine's ECU (Engine Control Unit). This approach minimizes the risk of noise and ensures a more stable signal.
* Verify if the signal you're tapping is driving the ignition coil directly, or if it's feeding into an igniter. If it's powering the coil directly, use the [https://wiki.autosportlabs.com/CoilX CoilX] module to buffer/filter the high-voltage signal.
* If uncertain, visualize the RPM signal using an oscilloscope - you should see a relatively clean square wave as the source.
* If your only source for RPM is the trigger wire driving the ignition coil primary winding, then you will need the [https://wiki.autosportlabs.com/CoilX CoilX] module to buffer/filter the noisy, high-voltage component.
[[File:RPM_input.png]]

==GPIO==
RaceCapture/Pro provides 4 General Purpose Input Output (GPIO) ports that can be used to control devices in output mode or read switches and high/low states of electrical signals in input mode.

{| class="wikitable"
|+ GPIO Specifications
|-
| Output Mode Type || Open Drain
|-
| Output Current Capacity || 1A, inductively clamped
|-
| Input Mode Voltage Range || 0-12V
|-
| Input Voltage Protection || 0-40V
|-
| Maximum Sample Rate || 1000Hz
|}

===Input Mode===
When configured for input mode, the RaceCapture/Pro sensor input will register a '1' when the input passes a voltage threshold of approximately 3V, and '0' when the input is low (close to 0 volts).

'''Important Note:''' When sensing large inductive loads, such as the state of brake lights or the on/off state of a motor, it is recommended to connect a '''10K 1/4 watt resistor''' in line with the GPIO input. This resistor helps protect RaceCapture/Pro from large inductive spikes, ensuring the longevity and reliability of the system.

===Output Mode===
When configured for output mode, RaceCapture connects that port to the ground and can sink a 1A load per port, which suitable for driving indicators, relays, sending signals to other systems, and driving small devices. [https://wiki.autosportlabs.com/GPIO_Output Click here for more info]

'''Output Behavior:'''
* When the port is active, the port will connect to the ground
* When the port is inactive, the port will be an open circuit.

[[File:GPIO Output Behavior.png]]

===Controlling GPIO Ports===
GPIO channels in output mode are controlled by the logic you create with the on-board Lua scripting capability.
See the [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting#General_Input_.2F_Output_.28GPIO.29_Functions GPIO section of the Lua Scripting reference] and collection of [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting_Examples Examples].

=Communications=
RaceCapture/Pro is equipped with multiple CAN bus networks to facilitate communication with various devices. There is a standard convention for selecting which CAN bus to use when connecting devices:
* '''CAN1:''' Typically used for connecting Engine Control Units (ECUs), including OBD-II interfaces and after-market ECUs. This CAN bus network is often utilized for critical vehicle data and diagnostics.
* '''CAN2:''' Typically used for extended sensor networks, such as AnalogX for analog sensors, TireX for tire pressure monitoring, and other peripheral sensors. These networks provide additional communication channels for expanded data acquisition and monitoring.

==CAN Bus Splitter==
The M8-6P male connector splits the CAN bus networks into individual CAN1 and CAN2 connections using dual M8-4P female connectors. This splitter allows you to connect devices to the specific CAN buses as needed:
* '''A Connection:''' Connects to CAN1
* '''B Connection:''' Connects to CAN2

'''Note:''' The CAN bus connections provide limited power (1A @ 12V) to devices connected to CAN1 and CAN2. For devices requiring higher power, it is recommended to use the Powered Dual CAN Hub. The Powered Dual CAN Hub provides additional power and helps ensure stable operation for connected devices.

[[File:CAN Connection 1.png|700px]]

See the [https://wiki.autosportlabs.com/RCP_CAN CAN bus / ECU integration guide] for information on integrating CAN bus communications and CAN channel mapping.

==CAN channel specifications==

{| class="wikitable"
|+ CAN channel specifications
|-
| Can Channel || 2
|-
| CAN Baud Rate || 125K, 250K, 500K, 1M Baud
|-
| CAN Filter || 14 per channel
|-
| Protocol Support || OBDII PID, custom CAN mapping
|-
| CAN bus compatibility || CAN 2.0 compatible, 1M baud
|-
| CAN termination || Software controlled
|}

RaceCapturePro Sensors

2026-04-03T20:47:34Z

Brentp: /* Remapping channels */

=IMU (Accelerometer / Gyro)=
Systems with an on-board IMU should be mounted in the default orientation, typically with the device connectors oriented towards the front of the vehicle.
* '''Note''' Check the model's documentation for the specific mounting guide.

==Mounting in an alternate orientation==
The system can be mounted in an alternate orientation, ideally in square 90 degree increments. For example:
* Inverted mounting
* Flat / upright, but rotated 90 degrees
* On-edge, but aligned with the front-rear axis of the vehicle

Re-orientation requires re-mapping of the accelerometer channels using the RaceCapture app.

[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Re-orientation procedure==
===Preparation===
Prior to remapping, create a temporary RaceCapture dashboard with the 6 channels (AccelX, AccelY, AccelZ, Yaw, Pitch, Roll).

Detach the system from the vehicle and visually note the behavior of each channel by moving the system about in free air. See the diagram for reference:

[[image:yaw_pitch_roll_x_y_z_race_car_diagram.jpg|500px]]

===Remapping channels===
Hold the device in free air at the '''new orientation''', then swap or invert IMU channels using the RaceCapture app to match the behavior seen with the default orientation and default channel mappings.

'''Note:''' Ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

==Smoothing==
The Accel/Gyro configuration screen includes a '''Smoothing''' slider that controls the amount of filtering applied to the IMU output.

* '''Less''' (slider to the left): Minimal filtering, producing raw and highly responsive data. This is useful for capturing sharp, short-duration events such as curb strikes or sudden inputs, but may introduce more noise into the signal.
* '''More''' (slider to the right): Increased filtering, producing a smoother signal by averaging out rapid fluctuations. This is better suited for general handling analysis where a cleaner trace is preferred.

Adjust the smoothing level to suit your logging and analysis goals. For most track driving applications, a moderate smoothing setting is a good starting point.

[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Zero Calibration==
After orientation is updated (as needed) and the system is mounted to the vehicle, ensure the vehicle is on a level surface. Then, perform a final zero calibration by pressing the '''Calibrate''' button in the RaceCapture app. This will zero out all 6 axes. At this point you can perform a final write and save of your configuration.

=Temperature Sensors=

Temperature sensors are passive devices that measure temperature through the use of a thermistor, a resistor that varies resistance with temperature. We recommend using dedicated, two wire ECU-style sensor similar to the types specified in our recommended sensor list for best results.
<center>[[Image:temp_sensor_connection.png|500px]]</center>

'''Pullup Resistor'''

A pullup resistor is needed to create the necessary voltage divider circuit so RaceCapture/Pro's analog input can measure temperature as a varying voltage. This pullup resistor is connected to the 5v reference on the RaceCapture/Pro terminal block.

'''High Resistance ECU style sensors''' Use a 2.2K ohm pull-up resistor for high resistance ECU style sensors, such as the temperature sensors in [[#Sensors|supported list]]

'''Low Resistance Gauge type sensors''' Low resistance gauge type sensors are not recommended. If you must use one of these types of sensors, a 1/4 watt 220 ohm pull-up resistor can be used for sensors such as VDO 323-095, 325-002 and similar.

'''Sensor Ground'''

Two wire ECU style temperature sensors have one sense lead and one ground lead. For best accuracy, connect the ground lead to the same ground point as RaceCapture/Pro. One wire gauge type sensors have the ground as the body of the sensor. Ensure the engine is properly grounded to the chassis via multiple ground straps.

==Recommended GM-Style Temperature Sensor==

[[File:-40 to 150C.jpg|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/40-to-150c-linear-temperature-sensor-with-plug-and-play-harness/]]

'''[ASL_LINEAR_TEMP_M8 : -40 to 150C Linear temperature sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_LINEAR_TEMP_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 1 Meter
* '''Pigtail / Harness connector :''' M8
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 3-5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Uses :''' The sensor is suitable for fluids such as oil, coolant and water
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 

[[Image:SU109_C.jpg|200px |thumb|right]]
'''[ Wells SU109 || SMP TX3 : Engine Coolant Temperature Sensor ]'''

The specification of the sensor are as follows. 

* '''Mfg / Prt :''' Wells SU109 || SMP TX3
* '''Thread Size :''' 3/8" NPT
* '''Cable length :''' N/A
* '''Pigtail :''' Pico 5615pt ( 2 pin terminal )
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Copper
* '''Uses :''' Used for air inlet temperature for normally aspirated engine
 

'''[ Wells SU107 || SMP TX3 : Air Intake / Charge Temperature Sensor]'''
[[Image:SU107_C.jpg|200px |thumb|right]]
The specification of the sensor are as follows
* '''Mfg / Prt :''' Wells SU107 || SMP AX1
* '''Thread Size :''' 3/8" NPT
* '''Pigtail :'''Pico 5616pt
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Brass
* '''Uses :''' Use for measuring air inlet / charge temperature measurement
* '''Caution :''' Due to the fragility of the sensing bulb, it is necessary to pot the base of the sensor leads with sensor-safe silicone when used in high vibration environments.

 

==Recommended Delphi-Style Temperature Sensor==

'''[ Delphi 12160855 || AEM-30-2012 : Extended temperature range sensor ]'''

[[Image:AEM-30-2012.jpg|200px |thumb|right]]
The specifications are as follows.
* '''Mfg / Prt :''' Delphi 12160855 equivalent || AEM-30-2012 Equivalent
* '''Thread Size :''' 1/8" - 27 NPTF
* '''Matting Connector :''' 12047662 connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resisto
* '''Voltage supply :''' 5V
* '''Body Material :''' Brass (PA66)
* '''Uses :''' Extended temperature range suitable for coolant and oil
* '''Datasheet :'''[https://eu.mouser.com/datasheet/2/105/dcs_drawing_12160855-1162047.pdf Click here]

=Pressure Sensors=

Pressure sensors are powered devices and are a type of active sensors. They provide a variable voltage output. Pressure sensors are particularly easy to wire. Nearly all Pressure Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting pressure sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Fluid Pressure Sensors==

'''Note :''' These sensors are appropriate for measuring fluid pressures in an engine. Not appropriate for measuring manifold boost or vacuum as these are relative pressure sensors. Use an absolute pressure sensor instead.
 

[[Image:10 Bar 150 psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/]]

'''[ASL_10_BAR_DELPHI3_M8 : 10 bar / 150 PSI pressure sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_10_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[ASL_150_BAR_DELPHI3_M8 : 150 bar / 2175 PSI pressure sensor ]'''
[[Image:150 BAR 2175 Psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/150-bar-2175-psi-pressure-sensor-with-plug-and-play-harness/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_150_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Use :'''Typically used for high pressure sensing, such as brake or clutch pressure
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[AEM 30-2131-150 : 150 PSI pressure sensor ]'''
[[Image:AEM-30-2131-150.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' AEM 30-2131-150
* '''Thread Size :''' 1/8″ NPT
* '''Pigtail :''' 3 pin GM connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Body Material :''' Brass
* '''Output :''' Linear response with an output between 0.5v and 4.5v
* '''Use :'''Appropriate for oil and fuel pressure measurement
* '''Data Sheet :''' [https://documents.holley.com/30-2131-xxx.pdf Click here]

 

==Recommended Manifold Pressure (MAP) Sensors==

'''[12223861 (GM) : Manifold Absolute Pressure MAP Sensor ]'''
[[Image:GM_3bar_map_sensor.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' 12223861 (GM)
* '''Pigtail :''' 15305891 (GM) or PT1035 (AC Delco)
* '''Operating Pressure :''' 40 TO 304 kPa
* '''Voltage supply :''' 5.1 +/- 0.36 V
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.619V to 4.818 VDC 
* '''Datasheet :'''[https://www.omnitekcorp.com/images/MAP3barspec.pdf Click here]
 
 
'''[Freescale MXP4250AP : 2.5 bar Manifold Absolute Pressure Sensor ]''' 
[[Image:Freescale-Semiconductor-MPX4250AP.jpg|200px|thumb|right]]
The specification of the sensor are as follows.
* '''Mfg / Prt :''' Freescale MXP4250AP
* '''Operating Pressure :''' 20 to 250 kPa
* '''Voltage supply :''' 4.85 to 5.35 VDC
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.2 to 4.9 V
* '''Use :''' An extremely popular MAP sensor used in the Megajolt ignition and Megasquirt fuel injection systems
* '''Datasheet :'''[https://www.nxp.com/docs/en/data-sheet/MPX4250A.pdf Click here]

=Pulse/Speed/RPM Sensors=

Wheel speed sensors generate a series of pulses as a toothed wheel passes by the face of the sensor. We recommend hall-effect style sensors, and these are provided with 3 connections:

* Power
* Ground
* Signal Output
 

Note: - We do not recommend using 2 wire Variable Reluctance (VR) type sensors. VR Sensors will require a conditioning circuit before being provided to the inputs of RaceCapture/Pro.
[[Image:speed_sensor_connection.png]]

'''Wiring the Speed Sensor'''

* '''Power :''' Connect the sensor's power to the 5v Vref on RaceCapture/Pro
* '''Ground :''' Connect the sensor's ground connection to the ground shared by RaceCapture/Pro
* '''Sensor Output :''' Connect the Sensor Output to one of RaceCapture/Pro's timer input channels
 

'''Optional pull up resistor'''
RaceCapture/Pro requires both a voltage and ground pulse provided in the waveform provided by the sensor. Most sensors provide an internal pull-up resistor so an active square wave can be observed on the output. However, some sensors only switch ground and leave the output line in a high impedance state when not active, like opening and closing a mechanical switch. If the sensor does not provide a pull-up resistor the wheel speed signal may have noise and glitches which may be observed as high value glitches in the dashboard and log file data.

If it's determined a pull-up resistor is needed:

* Use 2.2 to 10K pull-up resistor can be added close to RaceCapture/Pro to ensure a clear signal
* You can use the SensorX breakout board to conveniently wire this pull-up resistor

==Recommended RPM Sensor==
'''[Autosport Labs CoilX RPM Input adapter ]'''
[[Image:CoilX.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/coilx-rpm-input-adapter/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_COILX
* '''Input Connection :''' Red: Coil Signal || Black: Ground (External)
* '''Output/ To Realitycapture :''' Yellow: 5v power || Black: Output || Red: Ground (data system)
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Caution :''' Do not exceed 5 volts or damage to module will occur
* '''Use :''' The CoilX sensor module is designed to safely interface the noisy, high voltage RPM signal at the ignition coil pack primary into a clean signal that RaceCapture/Pro can process.
* '''Installation Instruction :''' [https://wiki.autosportlabs.com/CoilX Click here]

 

==Recommended Wheel Speed / Gear speed Sensors==

[[Image:Hamlin_55505_gear_wheel_speed_sensor.jpg|200px|thumb|right]]
'''[Hamlin 55505 : Hall Effect Flange Mount Geartooth Sensor ]''' 
The specification of the sensor are as follows.

* '''Mfg / Prt :''' Hamlin 55505
* '''Pullup resistor :''' Simple 3 wire hookup - No external pullup resistor required
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 4.75 to 24 V
* '''Supply Current :''' 1 to 10.5 mA
* '''Operating Temperature :''' -40 to 125c
* '''Use :''' Rugged Hall effect sensor suitable for harsh automotive environments (fuels, solvents, lubricants)
* '''Datasheet : ''' [https://eu.mouser.com/datasheet/2/240/Littelfuse_Hall_Effect_Sensors_55505_Datasheet.pdf-938889.pdf Click here]
 
 
'''[Cherry GS100701 : GS100701 Gear Speed Sensor ]''' 

The specification of the sensor are as follows.
[[Image:Cherry_GS100701_gear_speed_sensor.jpg|200px|thumb|right]]
* '''Mfg / Prt :''' Cherry GS100701
* '''Thread Size :''' 15/32-32
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 5 to 24 V
* '''Supply Current :''' 3 to 6 mA
* '''Operating Temperature :''' -40 to 125c
* '''Body Material :''' Aluminum
* '''Output current :''' 25mA max
* '''Datasheet :''' [https://www.jameco.com/Jameco/Products/ProdDS/512401.pdf Click here]

=Distance Sensors=

Distance sensors are also a type of active sensors, except string potentiometer sensor, which is a passive device. Distance sensors also provide variable voltage output. These sensors are particularly easy to wire. Nearly all distance Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting distance sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Ride Height Sensors==
[[File:500mm String Potentiometer.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/500mm-string-potentiometer-sensor/]] 

'''[ASL_STRING_POT_M8 : 500mm string potentiometer sensor]'''

The specification are as follows.

* '''Mfg / Prt :''' ASL_STRING_POT_M8
* '''Measurement Range :''' Up to 2 meters,
* '''Draw Cable :''' 500mm stainless steel draw cable
* '''Connector :''' M8 3P connector, works with our plug and play harness system
* '''Cable :''' 2 meter cable
* '''Range :''' 10K ohm range
* '''Pinout :''' Pin 1 : Ground || Pin 2 : Ground || Pin 3 : Signal
* '''Mount Type :''' Three mounting holes available for mounting
* '''Uses :''' Used to measure steering angle or linear travel
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]

'''[ Sharp GP2D12 : IR Range Sensor]''' 

[[Image:Sensor_GP2D12.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' Sharp GP2D12
* '''Detecting Range :''' 10-80cm
* '''Connection :''' 3 Pin JST cable
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage supply :''' -0.3 to 7.0 V
* '''Average current consumption:''' 33 mA
* '''Output Terminal Voltage :''' -0.3 to (VCC + 0.3)
* '''Uses :''' Used for ride height position (pointed at ground) and pedal position measurement
* '''Datasheet :''' [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1/GP2D12.pdf Click here]
 
 
'''[ BMW 37140141444 : Height Level Sensor]'''
 
[[Image:BMW_37140141444_ride_height_sensor.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Pigtail :''' 61138383300
* '''Measurement Range :''' Measures distance over 90 degrees of the arm travel.
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage Supply :''' 5V
* '''Output Terminal Voltage :''' 0-5v
* '''Uses :''' Used as a ride-height sensor for BMW and Mini applications for auto-leveling headlights
 
 

[[Image:KA_Sensors_RHL3_Laser_Ride_Height_Sensor.jpg|200px |thumb|right]]
'''[ KA Sensors RHL3 : Laser Ride Height Sensor]'''
 
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Electrical Connection :''' Cable: 26AWG, 55spec wire+DR25 sleeve or ASL Conn.
* '''Measurement Range :''' 200mm (60-260) or 500mm (200-700)
* '''Pinout :''' Red (Pin1) : +Ve Supply || Black (Pin 2) : Ground || White (Pin 3) : Signal || Pin 4 & 5 : Not Connected
* '''Voltage Supply :''' 11-30v (50mA) ( Separate power supply required )
* '''Output Terminal Voltage :''' 1-5v
* '''Body Material :''' Aluminum
* '''Datasheet :''' [https://www.kasensors.com/sites/default/files/downloads/RHL3_Laser_Ride_Height_Sensor_Datasheet_RHL3_1115.pdf Click here]
 

=== Analog Channel Configuration of Ride Height Sensors ===

'''Note :''' Please follow the below instruction for all the ride height sensors analog channel configuration.
 

'''Step To Calibrate :'''

# After installation place the vehicle on a level surface
# Set the Analog calibration to 0-5v simple linear scaling
# At rest, note the voltage of the sensor. This is the zero level.
# Raise and safely support the corner of the vehicle and remove the spring.
# Move the suspension arm to full droop. Note actual inches / mm traveled and also note the voltage logged by RaceCapture/Pro
# Move the suspension arm to full compression. Note actual inches / mm and also note the voltage logged by RaceCapture/Pro 

 
'''Create Calibration Table:''' 

# Place the droop voltage / distance combination into the 1st column of the calibration table. Make the distance negative
# Place the 'at rest' voltage into the 2nd column of the calibration table. Make the distance zero
# Place the compression voltage / distance into the 3rd column of the calibration table. Make the distance positive
# Repeat the compression voltage / distance values for the 4th and 5th columns

=Angle/Rotation Sensors=
These type of sensors are passive devices comprising some form of a variable resistor.

'''Steps for connecting Angle/Rotation Sensors'''
* Consult the sensor's technical documentation for sensor connections.
* Connect one of the outside legs of the variable resistor to the ground point for RaceCapture/Pro
* Connect the opposite leg of the variable resistor to the 5v Vref of RaceCapture/Pro
* Connect the variable resistor wiper (typically the center lead) to the the desired analog input port of RaceCapture/Pro
* During calibration, if the sensor reads backwards, flip the 5v and ground connections.
 

'''Note :''' Users can follow the same instruction for connecting string Potentiometer
[[Image:Potentiometer Sensor Connection.png]]
==Recommended Throttle Position (TPS) Sensor==
[[Image:TPS-45.jpg|200px|thumb|right]]
'''[Ford / SMP TH45 : Throttle Position Sensor]'''

The specifications are as follows.
* '''Mfg/Prt :''' Ford / SMP TH45
* '''Pigtail :''' Pico 5752PT
* '''Supply Voltage :''' 5V
* '''Analog Channel Configuration :'''To calibrate, note the voltage at 0% throttle and then at 100% throttle. Use these two numbers to create a 2 point analog scaling map
* '''Use :''' Common Ford style Throttle Position sensor

=Fuel Level Sensor=

Fuel Level Sensors are also variable resistor, these provide variable resistance based on the level of the float.

'''Wiring''' 

Determine if you need a pullup resistor, or if you are tapping into an existing circuit with a gauge.

'''If you already have a gauge connected''', you will not need a pullup resistor - the gauge's internal circuitry already provides one. You will only need to tap into the existing signal feeding the fuel gauge sender. Jump to the calibration process below. 

'''Note :''' You will need to ensure the sender does not exceed 5v during calibration. if it does, you will need an additional voltage divider to scale the voltage down to 0-5v required by the RaceCapture input. 

[[Image:Fuel_level_sender_with_existing_gauge.png]]

If you have no gauge / you want to only use RaceCapture for your dashboard gauge, want to directly integrate with RaceCapture's analog input, follow this procedure.
* Choose a pull-up resistor value based on the the sender's ohm range. If it is less than 1000 ohms, then choose a 1000 (1K) ohm resistor as your pull-up. If the sender range is higher than 1000 ohms, choose a 2.2K resistor
**Rule of thumb - choose a resistor that is about 2X to 4X the maximum resistance of the sender
**A 1/2 watt, 1% accuracy resistor is recommended

* Wire up the sender per the diagram:
**Connect the ground of the fuel level sender to ground (ideally the same ground point used by RaceCapture)
**Connect the output of the sender to one of RaceCapture's analog inputs
**Connect the pullup resistor between +5v reference and the sender's output. This creates the voltage divider circuit which will present RaceCapture with a variable voltage depending on fuel level.
[[file:Fuel_level_sender_direct_connection.png]]

==Fuel level sensor calibration==
Once you have your sensor connected, you will need to calibrate it.

In the RaceCapture analog configuration screen, set the reading to Raw voltage (0-5v) so RaceCapture acts as a volt meter, showing the raw value on the dashboard. Alternatively, you can use a separate volt-meter, directly measuring the signal.

Empty the tank, and then take measurements with the tank at different fill levels:
* 0%
* 25%
* 50%
* 75%
* 100%

Configure your analog channel with the channel set to Interpolated mapping mode and then entering the following into the table.

[[file:RaceCapture_app_fuel_level_calibration_smoothing.jpg|800px]]

==Smoothing the channel to deal with slosh==
To have the smoothest readings, we suggest setting the channel sample rate to 1Hz and set the smoothing level to "max"

Enter 0,25,50,75,100 as the scaled value, and your measured voltages into the voltage row.

==Alternative Fuel level senders==
You may consider fuel level senders that output a convenient and clean 0-5v signal, avoiding the need to use pullup resistors.

[https://www.google.com/search?q=fuel+level+sender+for+racing+that+outputs+a+clean+0-5v+signal Fuel level senders with 0-5v signal output]

Regardless of the sensor you use, the calibration procedure still applies.

=Air/Fuel Ratio Sensor=
[[Image:Texense LSU 4.9 Sensor.png|200px|thumb|right]]
'''[Texense LSU 4.9 : Air / Fuel Ratio Sensors]'''

The specifications are as follows.

* '''Mfg/Prt :''' Texense LSU 4.9
* '''Pigtail''' : Built-in wiring
* '''Fitting :''' Screws into O2 sensor port
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Use :''' Use to measure the oxygen ratio in the exhaust gas of automobile engines (petrol or diesel)
* '''Datasheet :''' [https://www.sens4speed.com/images/produit/pdf/5cb9bc3f25e16669665015.pdf Click here]

=Thermal Sensor=
Thermal imaging sensors visualize how your tires are working, in real time, and use it to tune your suspension for maximum grip and balance. Thermal imaging sensors have superior accuracy and thermal compensation than other sensors, it’s thermal array design allows it measuring beyond tire temperatures.
==Recommended Thermal Sensors==
[[Image:tirex_3quarter.jpg|200px|right|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/tirex-advanced-thermal-sensor/]]
'''[ASL_TIREX_4PACK / ASL_TIREX_SINGLE : TireX advanced thermal sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_TIREX_4PACK / ASL_TIREX_SINGLE
* '''Sensor Resolution :''' 16 x 12 (192 pixels)
* '''Field of view :''' 110 x 75 degrees
* '''Accuracy :''' 1C
* '''Sample rate :''' 0.5 – 64Hz (Tire temperature mode) 0.5 – 10Hz (Full frame mode)
* '''Supply voltage :''' 6 – 12v
* '''Power :''' 200mW
* '''Harness :''' M8 4P Male, 250mm length
* '''Interface :''' CAN 2.0
* ''' Specifications and Installation guide :''' [https://wiki.autosportlabs.com/TireX Click here]

=SensorX sensor breakout board=
[[File:Seensorx sensor breakout.png|180px|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/sensorx-sensor-breakout-board/]] 

SensorX is a breakout / distribution board that will make it easier to use sensors that require pullup resistors as well as making available multiple ground and 5V Vref connections.

The built-in pullup resistors are easily disabled by breaking a designated trace on the board. This board is compact; enough to be bundled inline with your wiring harness and covered in heat shrink tubing when complete.

The features of boards are as follows.
* Breakout board is use to combine up to 7 analog sensor inputs and their matching ground connections and 5v power connections.
* Dimensions: 0.4″ x 4″
* Five 2.2K resistors
* For more details : [https://wiki.autosportlabs.com/SensorX Click here]

=Wiring Analog Sensors=
==RaceCapture/Pro Analog Input Specifications==

* '''Total Analog Inputs :''' 8 ( the 8th input is wired internally to measuring battery voltage.)
* '''Analog Input Voltage Range :''' 0 to 5V
* '''Input Impedance :''' Over 1 mega ohm

==Calibrating Analog Sensors==
===Linear Sensors===
A linear sensor specify two voltages/value pairs representing a low and high range for the sensor. A straight line is drawn between the points on the sensor.

'''Example : 150 PSI pressure sensor'''
* 0.5 v = 0 PSI
* 4.5 v = 150 PSI

In the Analog Channel configuration, select the "'Mapped"' sensor mode, and then enter the values into the interpolated mapping grid.

* For column 1, enter the low voltage range in the Volts cell, and the low scaled value in the Scaled cell.
* For columns 2-5 enter the high voltage range in the Volts cell, and the high scaled value in the Scaled cell 
 

[[file:linear_sensor_mapping.png]]

 
===Curved Sensors===
Curved sensors are usually thermistor based sensors, where the response is not a straight line, but a curve. Multiple points can be used to sufficiently approximate the curve.

'''Note :''' RaceCapture linearly interpolates the scaled values between the sensor points, so value transitions will be smooth.

'''Example : Extended range temperature sensor with 5v reference and 2.2K pullup resistor'''
* 0.4 v = 302 F
* 0.87 v = 239 F
* 1.88 v = 176 F
* 3.2 v = 122 F
* 4.72 v = 32 F

In the Analog Channel configuration, select the Mapped sensor mode, and then enter the values into the interpolated mapping grid. 

[[file:curved_sensor_mapping.png]] 

'''Note :''' If you have more than 5 points for the curve, spread the selection of points evenly between your low and high range.

===Fuel Level Sensors===
Fuel Level Sensors are usually variable resistance based sensors, and provide a variable resistance based on the level of the float.

'''Calibration''' 

With the fuel at different levels, measure and note the voltage present at the RaceCapture analog input for different fuel levels:

* Empty (0%)
* 1/4 (25%)
* 1/2 (50%)
* 3/4 (75%)
* Full (100%)
 

'''Set up the Analog Channel'''
# Choose an available analog input for your Fuel Level channel, then select the basic fuel level preset by selecting Fuel Level in the dropdown list. (This pre-sets the units (%), logging precision and min / max values. You can edit this by pressing the gear button next to the channel name
# Set the sample rate to 1Hz.
# Set the mode to Mapped. This will let you create a curved mapping for the sensor voltage.
# Set the smoothing to Maximum - this will help account for variances due to fuel slosh.
# Enter the mapped values noted in the calibration process into the Analog Channel mapping editor under RaceCapture setup. This will provide the calibration curve for your fuel tank.
# Write these settings back to RaceCapture and observe your fuel level readings in units of percentage.
 

'''Example BMW E36 fuel level mapping'''

Example BMW E36 Fuel curve mapping (your sender's calibration will be different)

[[file:BMW_E36_fuel_level_curve.png]]

RaceCaptureTrack MK4

2026-04-03T20:46:57Z

Brentp: /* Mounting */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

See the guide for [[RaceCapturePro_Sensors#IMU_(Accelerometer_/_Gyro)|remapping the IMU channels for alternate mounting orientations]].

'''Additional Notes:'''
* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your RaceCapture to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Real-time Telemetry Setup ==
This section explains how to configure your device to stream live telemetry data to the Podium cloud service so it can be viewed remotely using the Podium app or the Podium website.

=== Overview ===
Three components are used when working with live telemetry:

* RaceCapture App : Used to connect directly to the device for configuration and local dashboard viewing.
* Podium App : Used to view live telemetry and previously recorded sessions in the cloud.
* Podium Website : Provides web access to the same telemetry data available in the Podium app.

=== Step 1 : Configure WiFi Connectivity ===
[[File:Inital setup.gif|750px]]
* Open the RaceCapture app and connect to your device.
* Navigate to Setup from the main screen.
* Click Read to load the current configuration.
* Select the Wireless tab.
** Configure the following settings:
*** Enable WiFi Support
*** Enable Client Mode
*** Enter the SSID and password for your hotspot or WiFi network
'''Note:''' The hotspot must support 2.4 GHz WiFi. Many hotspots default to 5 GHz, which is not supported. If necessary, configure your hotspot to allow 2.4 GHz operation.
For testing purposes, you may use your phone’s hotspot to confirm the connection is working correctly.
* Enable WiFi Telemetry at the bottom of the Wireless settings.
[[File:Enable wifi telemetry option.png|750px]]

=== Step 2 : Configure the Telemetry Streaming Key ===
[[File:Telemetry streaming key updated.gif|750px]]

To stream telemetry to Podium, you must enter a Telemetry Streaming Key.
* Open the Podium website.
* Navigate to Settings → Devices.
* Select your device from the list.
* Copy the Streaming Key shown for the device.
Return to the RaceCapture app:
* Navigate to the Telemetry tab.
* Paste the Streaming Key into the Telemetry Streaming Key field.

=== Step 3 : Configure Streaming Behavior ===
[[File:Background streaming key.png|750px]]

For testing or continuous streaming '''Enable Background Streaming'''.
This causes the device to begin telemetry streaming immediately after power-up. If Background Streaming is disabled, telemetry streaming will begin only when the system starts logging based on its configured trigger (typically vehicle speed, but other channels such as RPM may be used). This helps prevent unnecessary telemetry transmission when the vehicle is powered but not actively driving.

=== Step 4: Apply Configuration and Reboot===
Click Write to save the configuration to the device.

[[File:Configuration (write).png|750px]]

Reboot the device by either:
* Power cycling the unit, or
[[File:Rebot.png|750px]]
* Navigating to Setup > Firmware > Reboot.

=== Step 5 : Verify WiFi Connection ===
[[File:Verify WiFi Connection gif file.gif|750px]]

After rebooting:
* Navigate to System Status > WiFi.
* Confirm the WiFi Client is connected to the hotspot.

=== Step 6 : Confirm Telemetry Streaming ===
If telemetry streaming is active:
* The blue telemetry LED on the device will blink.
* This indicates the system is transmitting telemetry to Podium.
=== Viewing Live Telemetry ===
==== Podium Website ====

[[File:Viewing Live Telemetry podium website.gif|750px]]

* Open the Podium website.
* Navigate to Events.
* Locate the automatically generated live event for your device.
* Open the event to view live telemetry data.
* You should see real-time channel updates such as:
** IMU motion
** G-forces
** Sensor values

==== Podium App ====

The Podium app provides a richer telemetry viewing experience.

# Open the Podium app.
# Navigate to Events > Live Events.
# Select your device.

From here you can:
* View live dashboards
* Switch dashboard views
* Monitor individual telemetry channels

Dashboards can be:
* Selected from built-in presets
* Custom created and saved
* Shared by the community

=== Track Detection and Lap Timing ===

For automatic lap timing, ensure your track is added in Podium.
# Navigate to Racetracks.
# Add the tracks where you typically race.
When the system detects a known track, Podium will automatically enable:
* Lap timing
* Lap-based telemetry analysis
This allows session data to be viewed and analyzed in the context of laps.

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
Your system logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.

=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from your system.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

File:Yaw pitch roll x y z race car diagram.jpg

2026-04-03T18:26:41Z

Brentp: Brentp uploaded a new version of File:Yaw pitch roll x y z race car diagram.jpg

RaceCapturePro Sensors

2026-04-03T15:56:59Z

Brentp: /* IMU (Accelerometer / Gyro) */

=IMU (Accelerometer / Gyro)=
Systems with an on-board IMU should be mounted in the default orientation, typically with the device connectors oriented towards the front of the vehicle.
* '''Note''' Check the model's documentation for the specific mounting guide.

==Mounting in an alternate orientation==
The system can be mounted in an alternate orientation, ideally in square 90 degree increments. For example:
* Inverted mounting
* Flat / upright, but rotated 90 degrees
* On-edge, but aligned with the front-rear axis of the vehicle

Re-orientation requires re-mapping of the accelerometer channels using the RaceCapture app.

[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Re-orientation procedure==
===Preparation===
Prior to remapping, create a temporary RaceCapture dashboard with the 6 channels (AccelX, AccelY, AccelZ, Yaw, Pitch, Roll).

Detach the system from the vehicle and visually note the behavior of each channel by moving the system about in free air. See the diagram for reference:

[[image:yaw_pitch_roll_x_y_z_race_car_diagram.jpg|500px]]

===Remapping channels===
Hold the device in free air at the '''new orientation''', then swap or invert IMU channels using the RaceCapture app to match the behavior seen with the default orientation and default channel mappings.

==Smoothing==
The Accel/Gyro configuration screen includes a '''Smoothing''' slider that controls the amount of filtering applied to the IMU output.

* '''Less''' (slider to the left): Minimal filtering, producing raw and highly responsive data. This is useful for capturing sharp, short-duration events such as curb strikes or sudden inputs, but may introduce more noise into the signal.
* '''More''' (slider to the right): Increased filtering, producing a smoother signal by averaging out rapid fluctuations. This is better suited for general handling analysis where a cleaner trace is preferred.

Adjust the smoothing level to suit your logging and analysis goals. For most track driving applications, a moderate smoothing setting is a good starting point.

[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Zero Calibration==
After orientation is updated (as needed) and the system is mounted to the vehicle, ensure the vehicle is on a level surface. Then, perform a final zero calibration by pressing the '''Calibrate''' button in the RaceCapture app. This will zero out all 6 axes. At this point you can perform a final write and save of your configuration.

=Temperature Sensors=

Temperature sensors are passive devices that measure temperature through the use of a thermistor, a resistor that varies resistance with temperature. We recommend using dedicated, two wire ECU-style sensor similar to the types specified in our recommended sensor list for best results.
<center>[[Image:temp_sensor_connection.png|500px]]</center>

'''Pullup Resistor'''

A pullup resistor is needed to create the necessary voltage divider circuit so RaceCapture/Pro's analog input can measure temperature as a varying voltage. This pullup resistor is connected to the 5v reference on the RaceCapture/Pro terminal block.

'''High Resistance ECU style sensors''' Use a 2.2K ohm pull-up resistor for high resistance ECU style sensors, such as the temperature sensors in [[#Sensors|supported list]]

'''Low Resistance Gauge type sensors''' Low resistance gauge type sensors are not recommended. If you must use one of these types of sensors, a 1/4 watt 220 ohm pull-up resistor can be used for sensors such as VDO 323-095, 325-002 and similar.

'''Sensor Ground'''

Two wire ECU style temperature sensors have one sense lead and one ground lead. For best accuracy, connect the ground lead to the same ground point as RaceCapture/Pro. One wire gauge type sensors have the ground as the body of the sensor. Ensure the engine is properly grounded to the chassis via multiple ground straps.

==Recommended GM-Style Temperature Sensor==

[[File:-40 to 150C.jpg|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/40-to-150c-linear-temperature-sensor-with-plug-and-play-harness/]]

'''[ASL_LINEAR_TEMP_M8 : -40 to 150C Linear temperature sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_LINEAR_TEMP_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 1 Meter
* '''Pigtail / Harness connector :''' M8
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 3-5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Uses :''' The sensor is suitable for fluids such as oil, coolant and water
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 

[[Image:SU109_C.jpg|200px |thumb|right]]
'''[ Wells SU109 || SMP TX3 : Engine Coolant Temperature Sensor ]'''

The specification of the sensor are as follows. 

* '''Mfg / Prt :''' Wells SU109 || SMP TX3
* '''Thread Size :''' 3/8" NPT
* '''Cable length :''' N/A
* '''Pigtail :''' Pico 5615pt ( 2 pin terminal )
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Copper
* '''Uses :''' Used for air inlet temperature for normally aspirated engine
 

'''[ Wells SU107 || SMP TX3 : Air Intake / Charge Temperature Sensor]'''
[[Image:SU107_C.jpg|200px |thumb|right]]
The specification of the sensor are as follows
* '''Mfg / Prt :''' Wells SU107 || SMP AX1
* '''Thread Size :''' 3/8" NPT
* '''Pigtail :'''Pico 5616pt
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Brass
* '''Uses :''' Use for measuring air inlet / charge temperature measurement
* '''Caution :''' Due to the fragility of the sensing bulb, it is necessary to pot the base of the sensor leads with sensor-safe silicone when used in high vibration environments.

 

==Recommended Delphi-Style Temperature Sensor==

'''[ Delphi 12160855 || AEM-30-2012 : Extended temperature range sensor ]'''

[[Image:AEM-30-2012.jpg|200px |thumb|right]]
The specifications are as follows.
* '''Mfg / Prt :''' Delphi 12160855 equivalent || AEM-30-2012 Equivalent
* '''Thread Size :''' 1/8" - 27 NPTF
* '''Matting Connector :''' 12047662 connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resisto
* '''Voltage supply :''' 5V
* '''Body Material :''' Brass (PA66)
* '''Uses :''' Extended temperature range suitable for coolant and oil
* '''Datasheet :'''[https://eu.mouser.com/datasheet/2/105/dcs_drawing_12160855-1162047.pdf Click here]

=Pressure Sensors=

Pressure sensors are powered devices and are a type of active sensors. They provide a variable voltage output. Pressure sensors are particularly easy to wire. Nearly all Pressure Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting pressure sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Fluid Pressure Sensors==

'''Note :''' These sensors are appropriate for measuring fluid pressures in an engine. Not appropriate for measuring manifold boost or vacuum as these are relative pressure sensors. Use an absolute pressure sensor instead.
 

[[Image:10 Bar 150 psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/]]

'''[ASL_10_BAR_DELPHI3_M8 : 10 bar / 150 PSI pressure sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_10_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[ASL_150_BAR_DELPHI3_M8 : 150 bar / 2175 PSI pressure sensor ]'''
[[Image:150 BAR 2175 Psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/150-bar-2175-psi-pressure-sensor-with-plug-and-play-harness/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_150_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Use :'''Typically used for high pressure sensing, such as brake or clutch pressure
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[AEM 30-2131-150 : 150 PSI pressure sensor ]'''
[[Image:AEM-30-2131-150.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' AEM 30-2131-150
* '''Thread Size :''' 1/8″ NPT
* '''Pigtail :''' 3 pin GM connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Body Material :''' Brass
* '''Output :''' Linear response with an output between 0.5v and 4.5v
* '''Use :'''Appropriate for oil and fuel pressure measurement
* '''Data Sheet :''' [https://documents.holley.com/30-2131-xxx.pdf Click here]

 

==Recommended Manifold Pressure (MAP) Sensors==

'''[12223861 (GM) : Manifold Absolute Pressure MAP Sensor ]'''
[[Image:GM_3bar_map_sensor.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' 12223861 (GM)
* '''Pigtail :''' 15305891 (GM) or PT1035 (AC Delco)
* '''Operating Pressure :''' 40 TO 304 kPa
* '''Voltage supply :''' 5.1 +/- 0.36 V
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.619V to 4.818 VDC 
* '''Datasheet :'''[https://www.omnitekcorp.com/images/MAP3barspec.pdf Click here]
 
 
'''[Freescale MXP4250AP : 2.5 bar Manifold Absolute Pressure Sensor ]''' 
[[Image:Freescale-Semiconductor-MPX4250AP.jpg|200px|thumb|right]]
The specification of the sensor are as follows.
* '''Mfg / Prt :''' Freescale MXP4250AP
* '''Operating Pressure :''' 20 to 250 kPa
* '''Voltage supply :''' 4.85 to 5.35 VDC
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.2 to 4.9 V
* '''Use :''' An extremely popular MAP sensor used in the Megajolt ignition and Megasquirt fuel injection systems
* '''Datasheet :'''[https://www.nxp.com/docs/en/data-sheet/MPX4250A.pdf Click here]

=Pulse/Speed/RPM Sensors=

Wheel speed sensors generate a series of pulses as a toothed wheel passes by the face of the sensor. We recommend hall-effect style sensors, and these are provided with 3 connections:

* Power
* Ground
* Signal Output
 

Note: - We do not recommend using 2 wire Variable Reluctance (VR) type sensors. VR Sensors will require a conditioning circuit before being provided to the inputs of RaceCapture/Pro.
[[Image:speed_sensor_connection.png]]

'''Wiring the Speed Sensor'''

* '''Power :''' Connect the sensor's power to the 5v Vref on RaceCapture/Pro
* '''Ground :''' Connect the sensor's ground connection to the ground shared by RaceCapture/Pro
* '''Sensor Output :''' Connect the Sensor Output to one of RaceCapture/Pro's timer input channels
 

'''Optional pull up resistor'''
RaceCapture/Pro requires both a voltage and ground pulse provided in the waveform provided by the sensor. Most sensors provide an internal pull-up resistor so an active square wave can be observed on the output. However, some sensors only switch ground and leave the output line in a high impedance state when not active, like opening and closing a mechanical switch. If the sensor does not provide a pull-up resistor the wheel speed signal may have noise and glitches which may be observed as high value glitches in the dashboard and log file data.

If it's determined a pull-up resistor is needed:

* Use 2.2 to 10K pull-up resistor can be added close to RaceCapture/Pro to ensure a clear signal
* You can use the SensorX breakout board to conveniently wire this pull-up resistor

==Recommended RPM Sensor==
'''[Autosport Labs CoilX RPM Input adapter ]'''
[[Image:CoilX.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/coilx-rpm-input-adapter/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_COILX
* '''Input Connection :''' Red: Coil Signal || Black: Ground (External)
* '''Output/ To Realitycapture :''' Yellow: 5v power || Black: Output || Red: Ground (data system)
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Caution :''' Do not exceed 5 volts or damage to module will occur
* '''Use :''' The CoilX sensor module is designed to safely interface the noisy, high voltage RPM signal at the ignition coil pack primary into a clean signal that RaceCapture/Pro can process.
* '''Installation Instruction :''' [https://wiki.autosportlabs.com/CoilX Click here]

 

==Recommended Wheel Speed / Gear speed Sensors==

[[Image:Hamlin_55505_gear_wheel_speed_sensor.jpg|200px|thumb|right]]
'''[Hamlin 55505 : Hall Effect Flange Mount Geartooth Sensor ]''' 
The specification of the sensor are as follows.

* '''Mfg / Prt :''' Hamlin 55505
* '''Pullup resistor :''' Simple 3 wire hookup - No external pullup resistor required
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 4.75 to 24 V
* '''Supply Current :''' 1 to 10.5 mA
* '''Operating Temperature :''' -40 to 125c
* '''Use :''' Rugged Hall effect sensor suitable for harsh automotive environments (fuels, solvents, lubricants)
* '''Datasheet : ''' [https://eu.mouser.com/datasheet/2/240/Littelfuse_Hall_Effect_Sensors_55505_Datasheet.pdf-938889.pdf Click here]
 
 
'''[Cherry GS100701 : GS100701 Gear Speed Sensor ]''' 

The specification of the sensor are as follows.
[[Image:Cherry_GS100701_gear_speed_sensor.jpg|200px|thumb|right]]
* '''Mfg / Prt :''' Cherry GS100701
* '''Thread Size :''' 15/32-32
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 5 to 24 V
* '''Supply Current :''' 3 to 6 mA
* '''Operating Temperature :''' -40 to 125c
* '''Body Material :''' Aluminum
* '''Output current :''' 25mA max
* '''Datasheet :''' [https://www.jameco.com/Jameco/Products/ProdDS/512401.pdf Click here]

=Distance Sensors=

Distance sensors are also a type of active sensors, except string potentiometer sensor, which is a passive device. Distance sensors also provide variable voltage output. These sensors are particularly easy to wire. Nearly all distance Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting distance sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Ride Height Sensors==
[[File:500mm String Potentiometer.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/500mm-string-potentiometer-sensor/]] 

'''[ASL_STRING_POT_M8 : 500mm string potentiometer sensor]'''

The specification are as follows.

* '''Mfg / Prt :''' ASL_STRING_POT_M8
* '''Measurement Range :''' Up to 2 meters,
* '''Draw Cable :''' 500mm stainless steel draw cable
* '''Connector :''' M8 3P connector, works with our plug and play harness system
* '''Cable :''' 2 meter cable
* '''Range :''' 10K ohm range
* '''Pinout :''' Pin 1 : Ground || Pin 2 : Ground || Pin 3 : Signal
* '''Mount Type :''' Three mounting holes available for mounting
* '''Uses :''' Used to measure steering angle or linear travel
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]

'''[ Sharp GP2D12 : IR Range Sensor]''' 

[[Image:Sensor_GP2D12.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' Sharp GP2D12
* '''Detecting Range :''' 10-80cm
* '''Connection :''' 3 Pin JST cable
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage supply :''' -0.3 to 7.0 V
* '''Average current consumption:''' 33 mA
* '''Output Terminal Voltage :''' -0.3 to (VCC + 0.3)
* '''Uses :''' Used for ride height position (pointed at ground) and pedal position measurement
* '''Datasheet :''' [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1/GP2D12.pdf Click here]
 
 
'''[ BMW 37140141444 : Height Level Sensor]'''
 
[[Image:BMW_37140141444_ride_height_sensor.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Pigtail :''' 61138383300
* '''Measurement Range :''' Measures distance over 90 degrees of the arm travel.
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage Supply :''' 5V
* '''Output Terminal Voltage :''' 0-5v
* '''Uses :''' Used as a ride-height sensor for BMW and Mini applications for auto-leveling headlights
 
 

[[Image:KA_Sensors_RHL3_Laser_Ride_Height_Sensor.jpg|200px |thumb|right]]
'''[ KA Sensors RHL3 : Laser Ride Height Sensor]'''
 
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Electrical Connection :''' Cable: 26AWG, 55spec wire+DR25 sleeve or ASL Conn.
* '''Measurement Range :''' 200mm (60-260) or 500mm (200-700)
* '''Pinout :''' Red (Pin1) : +Ve Supply || Black (Pin 2) : Ground || White (Pin 3) : Signal || Pin 4 & 5 : Not Connected
* '''Voltage Supply :''' 11-30v (50mA) ( Separate power supply required )
* '''Output Terminal Voltage :''' 1-5v
* '''Body Material :''' Aluminum
* '''Datasheet :''' [https://www.kasensors.com/sites/default/files/downloads/RHL3_Laser_Ride_Height_Sensor_Datasheet_RHL3_1115.pdf Click here]
 

=== Analog Channel Configuration of Ride Height Sensors ===

'''Note :''' Please follow the below instruction for all the ride height sensors analog channel configuration.
 

'''Step To Calibrate :'''

# After installation place the vehicle on a level surface
# Set the Analog calibration to 0-5v simple linear scaling
# At rest, note the voltage of the sensor. This is the zero level.
# Raise and safely support the corner of the vehicle and remove the spring.
# Move the suspension arm to full droop. Note actual inches / mm traveled and also note the voltage logged by RaceCapture/Pro
# Move the suspension arm to full compression. Note actual inches / mm and also note the voltage logged by RaceCapture/Pro 

 
'''Create Calibration Table:''' 

# Place the droop voltage / distance combination into the 1st column of the calibration table. Make the distance negative
# Place the 'at rest' voltage into the 2nd column of the calibration table. Make the distance zero
# Place the compression voltage / distance into the 3rd column of the calibration table. Make the distance positive
# Repeat the compression voltage / distance values for the 4th and 5th columns

=Angle/Rotation Sensors=
These type of sensors are passive devices comprising some form of a variable resistor.

'''Steps for connecting Angle/Rotation Sensors'''
* Consult the sensor's technical documentation for sensor connections.
* Connect one of the outside legs of the variable resistor to the ground point for RaceCapture/Pro
* Connect the opposite leg of the variable resistor to the 5v Vref of RaceCapture/Pro
* Connect the variable resistor wiper (typically the center lead) to the the desired analog input port of RaceCapture/Pro
* During calibration, if the sensor reads backwards, flip the 5v and ground connections.
 

'''Note :''' Users can follow the same instruction for connecting string Potentiometer
[[Image:Potentiometer Sensor Connection.png]]
==Recommended Throttle Position (TPS) Sensor==
[[Image:TPS-45.jpg|200px|thumb|right]]
'''[Ford / SMP TH45 : Throttle Position Sensor]'''

The specifications are as follows.
* '''Mfg/Prt :''' Ford / SMP TH45
* '''Pigtail :''' Pico 5752PT
* '''Supply Voltage :''' 5V
* '''Analog Channel Configuration :'''To calibrate, note the voltage at 0% throttle and then at 100% throttle. Use these two numbers to create a 2 point analog scaling map
* '''Use :''' Common Ford style Throttle Position sensor

=Fuel Level Sensor=

Fuel Level Sensors are also variable resistor, these provide variable resistance based on the level of the float.

'''Wiring''' 

Determine if you need a pullup resistor, or if you are tapping into an existing circuit with a gauge.

'''If you already have a gauge connected''', you will not need a pullup resistor - the gauge's internal circuitry already provides one. You will only need to tap into the existing signal feeding the fuel gauge sender. Jump to the calibration process below. 

'''Note :''' You will need to ensure the sender does not exceed 5v during calibration. if it does, you will need an additional voltage divider to scale the voltage down to 0-5v required by the RaceCapture input. 

[[Image:Fuel_level_sender_with_existing_gauge.png]]

If you have no gauge / you want to only use RaceCapture for your dashboard gauge, want to directly integrate with RaceCapture's analog input, follow this procedure.
* Choose a pull-up resistor value based on the the sender's ohm range. If it is less than 1000 ohms, then choose a 1000 (1K) ohm resistor as your pull-up. If the sender range is higher than 1000 ohms, choose a 2.2K resistor
**Rule of thumb - choose a resistor that is about 2X to 4X the maximum resistance of the sender
**A 1/2 watt, 1% accuracy resistor is recommended

* Wire up the sender per the diagram:
**Connect the ground of the fuel level sender to ground (ideally the same ground point used by RaceCapture)
**Connect the output of the sender to one of RaceCapture's analog inputs
**Connect the pullup resistor between +5v reference and the sender's output. This creates the voltage divider circuit which will present RaceCapture with a variable voltage depending on fuel level.
[[file:Fuel_level_sender_direct_connection.png]]

==Fuel level sensor calibration==
Once you have your sensor connected, you will need to calibrate it.

In the RaceCapture analog configuration screen, set the reading to Raw voltage (0-5v) so RaceCapture acts as a volt meter, showing the raw value on the dashboard. Alternatively, you can use a separate volt-meter, directly measuring the signal.

Empty the tank, and then take measurements with the tank at different fill levels:
* 0%
* 25%
* 50%
* 75%
* 100%

Configure your analog channel with the channel set to Interpolated mapping mode and then entering the following into the table.

[[file:RaceCapture_app_fuel_level_calibration_smoothing.jpg|800px]]

==Smoothing the channel to deal with slosh==
To have the smoothest readings, we suggest setting the channel sample rate to 1Hz and set the smoothing level to "max"

Enter 0,25,50,75,100 as the scaled value, and your measured voltages into the voltage row.

==Alternative Fuel level senders==
You may consider fuel level senders that output a convenient and clean 0-5v signal, avoiding the need to use pullup resistors.

[https://www.google.com/search?q=fuel+level+sender+for+racing+that+outputs+a+clean+0-5v+signal Fuel level senders with 0-5v signal output]

Regardless of the sensor you use, the calibration procedure still applies.

=Air/Fuel Ratio Sensor=
[[Image:Texense LSU 4.9 Sensor.png|200px|thumb|right]]
'''[Texense LSU 4.9 : Air / Fuel Ratio Sensors]'''

The specifications are as follows.

* '''Mfg/Prt :''' Texense LSU 4.9
* '''Pigtail''' : Built-in wiring
* '''Fitting :''' Screws into O2 sensor port
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Use :''' Use to measure the oxygen ratio in the exhaust gas of automobile engines (petrol or diesel)
* '''Datasheet :''' [https://www.sens4speed.com/images/produit/pdf/5cb9bc3f25e16669665015.pdf Click here]

=Thermal Sensor=
Thermal imaging sensors visualize how your tires are working, in real time, and use it to tune your suspension for maximum grip and balance. Thermal imaging sensors have superior accuracy and thermal compensation than other sensors, it’s thermal array design allows it measuring beyond tire temperatures.
==Recommended Thermal Sensors==
[[Image:tirex_3quarter.jpg|200px|right|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/tirex-advanced-thermal-sensor/]]
'''[ASL_TIREX_4PACK / ASL_TIREX_SINGLE : TireX advanced thermal sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_TIREX_4PACK / ASL_TIREX_SINGLE
* '''Sensor Resolution :''' 16 x 12 (192 pixels)
* '''Field of view :''' 110 x 75 degrees
* '''Accuracy :''' 1C
* '''Sample rate :''' 0.5 – 64Hz (Tire temperature mode) 0.5 – 10Hz (Full frame mode)
* '''Supply voltage :''' 6 – 12v
* '''Power :''' 200mW
* '''Harness :''' M8 4P Male, 250mm length
* '''Interface :''' CAN 2.0
* ''' Specifications and Installation guide :''' [https://wiki.autosportlabs.com/TireX Click here]

=SensorX sensor breakout board=
[[File:Seensorx sensor breakout.png|180px|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/sensorx-sensor-breakout-board/]] 

SensorX is a breakout / distribution board that will make it easier to use sensors that require pullup resistors as well as making available multiple ground and 5V Vref connections.

The built-in pullup resistors are easily disabled by breaking a designated trace on the board. This board is compact; enough to be bundled inline with your wiring harness and covered in heat shrink tubing when complete.

The features of boards are as follows.
* Breakout board is use to combine up to 7 analog sensor inputs and their matching ground connections and 5v power connections.
* Dimensions: 0.4″ x 4″
* Five 2.2K resistors
* For more details : [https://wiki.autosportlabs.com/SensorX Click here]

=Wiring Analog Sensors=
==RaceCapture/Pro Analog Input Specifications==

* '''Total Analog Inputs :''' 8 ( the 8th input is wired internally to measuring battery voltage.)
* '''Analog Input Voltage Range :''' 0 to 5V
* '''Input Impedance :''' Over 1 mega ohm

==Calibrating Analog Sensors==
===Linear Sensors===
A linear sensor specify two voltages/value pairs representing a low and high range for the sensor. A straight line is drawn between the points on the sensor.

'''Example : 150 PSI pressure sensor'''
* 0.5 v = 0 PSI
* 4.5 v = 150 PSI

In the Analog Channel configuration, select the "'Mapped"' sensor mode, and then enter the values into the interpolated mapping grid.

* For column 1, enter the low voltage range in the Volts cell, and the low scaled value in the Scaled cell.
* For columns 2-5 enter the high voltage range in the Volts cell, and the high scaled value in the Scaled cell 
 

[[file:linear_sensor_mapping.png]]

 
===Curved Sensors===
Curved sensors are usually thermistor based sensors, where the response is not a straight line, but a curve. Multiple points can be used to sufficiently approximate the curve.

'''Note :''' RaceCapture linearly interpolates the scaled values between the sensor points, so value transitions will be smooth.

'''Example : Extended range temperature sensor with 5v reference and 2.2K pullup resistor'''
* 0.4 v = 302 F
* 0.87 v = 239 F
* 1.88 v = 176 F
* 3.2 v = 122 F
* 4.72 v = 32 F

In the Analog Channel configuration, select the Mapped sensor mode, and then enter the values into the interpolated mapping grid. 

[[file:curved_sensor_mapping.png]] 

'''Note :''' If you have more than 5 points for the curve, spread the selection of points evenly between your low and high range.

===Fuel Level Sensors===
Fuel Level Sensors are usually variable resistance based sensors, and provide a variable resistance based on the level of the float.

'''Calibration''' 

With the fuel at different levels, measure and note the voltage present at the RaceCapture analog input for different fuel levels:

* Empty (0%)
* 1/4 (25%)
* 1/2 (50%)
* 3/4 (75%)
* Full (100%)
 

'''Set up the Analog Channel'''
# Choose an available analog input for your Fuel Level channel, then select the basic fuel level preset by selecting Fuel Level in the dropdown list. (This pre-sets the units (%), logging precision and min / max values. You can edit this by pressing the gear button next to the channel name
# Set the sample rate to 1Hz.
# Set the mode to Mapped. This will let you create a curved mapping for the sensor voltage.
# Set the smoothing to Maximum - this will help account for variances due to fuel slosh.
# Enter the mapped values noted in the calibration process into the Analog Channel mapping editor under RaceCapture setup. This will provide the calibration curve for your fuel tank.
# Write these settings back to RaceCapture and observe your fuel level readings in units of percentage.
 

'''Example BMW E36 fuel level mapping'''

Example BMW E36 Fuel curve mapping (your sender's calibration will be different)

[[file:BMW_E36_fuel_level_curve.png]]

RaceCapturePro Sensors

2026-04-03T15:52:03Z

Brentp: /* Remapping channels */

=IMU (Accelerometer / Gyro)=

Systems with an on-board IMU should be mounted in the default orientation, typically with the device connectors oriented towards the front of the vehicle.
* '''Note''' Check the model's documentation for the specific mounting guide.

==Mounting in an alternate orientation==
The system can be mounted in an alternate orientation, ideally in square 90 degree increments. For example:
* Inverted mounting
* Flat / upright, but rotated 90 degrees
* On-edge, but aligned with the front-rear axis of the vehicle

Re-orientation requires re-mapping of the accelerometer channels, using the RaceCapture app
[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Re-orientation procedure==

===Preparation===
Prior remapping, creata a temporary racecapture dashboard with the 6 channels (AccelX, AccelY, AccelZ, Yaw, Pitch, Roll)

Detach the system from the vehicle, and visually note the behavior of each channel by moving the system about in free air. See the diagram for reference:

[[image:yaw_pitch_roll_x_y_z_race_car_diagram.jpg|500px]]

===Remapping channels===
Now, hold the device in free air at the '''new orientation''', and then swap / invert IMU channels using the RaceCapture app to attain the behavior seen with the default orientation and default channel mappings.

==Zero Calibration==
After orientation is updated (as needed) and the system is mounted to the vehicle, ensure the vehicle is on a level surface. Then, perform a final zero calibration by pressing the Calibrate button in the RaceCapture app. This will zero out all 6 axis. At this point you can perform a final write / save of your configuration

=Temperature Sensors=

Temperature sensors are passive devices that measure temperature through the use of a thermistor, a resistor that varies resistance with temperature. We recommend using dedicated, two wire ECU-style sensor similar to the types specified in our recommended sensor list for best results.
<center>[[Image:temp_sensor_connection.png|500px]]</center>

'''Pullup Resistor'''

A pullup resistor is needed to create the necessary voltage divider circuit so RaceCapture/Pro's analog input can measure temperature as a varying voltage. This pullup resistor is connected to the 5v reference on the RaceCapture/Pro terminal block.

'''High Resistance ECU style sensors''' Use a 2.2K ohm pull-up resistor for high resistance ECU style sensors, such as the temperature sensors in [[#Sensors|supported list]]

'''Low Resistance Gauge type sensors''' Low resistance gauge type sensors are not recommended. If you must use one of these types of sensors, a 1/4 watt 220 ohm pull-up resistor can be used for sensors such as VDO 323-095, 325-002 and similar.

'''Sensor Ground'''

Two wire ECU style temperature sensors have one sense lead and one ground lead. For best accuracy, connect the ground lead to the same ground point as RaceCapture/Pro. One wire gauge type sensors have the ground as the body of the sensor. Ensure the engine is properly grounded to the chassis via multiple ground straps.

==Recommended GM-Style Temperature Sensor==

[[File:-40 to 150C.jpg|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/40-to-150c-linear-temperature-sensor-with-plug-and-play-harness/]]

'''[ASL_LINEAR_TEMP_M8 : -40 to 150C Linear temperature sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_LINEAR_TEMP_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 1 Meter
* '''Pigtail / Harness connector :''' M8
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 3-5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Uses :''' The sensor is suitable for fluids such as oil, coolant and water
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 

[[Image:SU109_C.jpg|200px |thumb|right]]
'''[ Wells SU109 || SMP TX3 : Engine Coolant Temperature Sensor ]'''

The specification of the sensor are as follows. 

* '''Mfg / Prt :''' Wells SU109 || SMP TX3
* '''Thread Size :''' 3/8" NPT
* '''Cable length :''' N/A
* '''Pigtail :''' Pico 5615pt ( 2 pin terminal )
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Copper
* '''Uses :''' Used for air inlet temperature for normally aspirated engine
 

'''[ Wells SU107 || SMP TX3 : Air Intake / Charge Temperature Sensor]'''
[[Image:SU107_C.jpg|200px |thumb|right]]
The specification of the sensor are as follows
* '''Mfg / Prt :''' Wells SU107 || SMP AX1
* '''Thread Size :''' 3/8" NPT
* '''Pigtail :'''Pico 5616pt
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Brass
* '''Uses :''' Use for measuring air inlet / charge temperature measurement
* '''Caution :''' Due to the fragility of the sensing bulb, it is necessary to pot the base of the sensor leads with sensor-safe silicone when used in high vibration environments.

 

==Recommended Delphi-Style Temperature Sensor==

'''[ Delphi 12160855 || AEM-30-2012 : Extended temperature range sensor ]'''

[[Image:AEM-30-2012.jpg|200px |thumb|right]]
The specifications are as follows.
* '''Mfg / Prt :''' Delphi 12160855 equivalent || AEM-30-2012 Equivalent
* '''Thread Size :''' 1/8" - 27 NPTF
* '''Matting Connector :''' 12047662 connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resisto
* '''Voltage supply :''' 5V
* '''Body Material :''' Brass (PA66)
* '''Uses :''' Extended temperature range suitable for coolant and oil
* '''Datasheet :'''[https://eu.mouser.com/datasheet/2/105/dcs_drawing_12160855-1162047.pdf Click here]

=Pressure Sensors=

Pressure sensors are powered devices and are a type of active sensors. They provide a variable voltage output. Pressure sensors are particularly easy to wire. Nearly all Pressure Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting pressure sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Fluid Pressure Sensors==

'''Note :''' These sensors are appropriate for measuring fluid pressures in an engine. Not appropriate for measuring manifold boost or vacuum as these are relative pressure sensors. Use an absolute pressure sensor instead.
 

[[Image:10 Bar 150 psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/]]

'''[ASL_10_BAR_DELPHI3_M8 : 10 bar / 150 PSI pressure sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_10_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[ASL_150_BAR_DELPHI3_M8 : 150 bar / 2175 PSI pressure sensor ]'''
[[Image:150 BAR 2175 Psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/150-bar-2175-psi-pressure-sensor-with-plug-and-play-harness/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_150_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Use :'''Typically used for high pressure sensing, such as brake or clutch pressure
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[AEM 30-2131-150 : 150 PSI pressure sensor ]'''
[[Image:AEM-30-2131-150.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' AEM 30-2131-150
* '''Thread Size :''' 1/8″ NPT
* '''Pigtail :''' 3 pin GM connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Body Material :''' Brass
* '''Output :''' Linear response with an output between 0.5v and 4.5v
* '''Use :'''Appropriate for oil and fuel pressure measurement
* '''Data Sheet :''' [https://documents.holley.com/30-2131-xxx.pdf Click here]

 

==Recommended Manifold Pressure (MAP) Sensors==

'''[12223861 (GM) : Manifold Absolute Pressure MAP Sensor ]'''
[[Image:GM_3bar_map_sensor.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' 12223861 (GM)
* '''Pigtail :''' 15305891 (GM) or PT1035 (AC Delco)
* '''Operating Pressure :''' 40 TO 304 kPa
* '''Voltage supply :''' 5.1 +/- 0.36 V
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.619V to 4.818 VDC 
* '''Datasheet :'''[https://www.omnitekcorp.com/images/MAP3barspec.pdf Click here]
 
 
'''[Freescale MXP4250AP : 2.5 bar Manifold Absolute Pressure Sensor ]''' 
[[Image:Freescale-Semiconductor-MPX4250AP.jpg|200px|thumb|right]]
The specification of the sensor are as follows.
* '''Mfg / Prt :''' Freescale MXP4250AP
* '''Operating Pressure :''' 20 to 250 kPa
* '''Voltage supply :''' 4.85 to 5.35 VDC
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.2 to 4.9 V
* '''Use :''' An extremely popular MAP sensor used in the Megajolt ignition and Megasquirt fuel injection systems
* '''Datasheet :'''[https://www.nxp.com/docs/en/data-sheet/MPX4250A.pdf Click here]

=Pulse/Speed/RPM Sensors=

Wheel speed sensors generate a series of pulses as a toothed wheel passes by the face of the sensor. We recommend hall-effect style sensors, and these are provided with 3 connections:

* Power
* Ground
* Signal Output
 

Note: - We do not recommend using 2 wire Variable Reluctance (VR) type sensors. VR Sensors will require a conditioning circuit before being provided to the inputs of RaceCapture/Pro.
[[Image:speed_sensor_connection.png]]

'''Wiring the Speed Sensor'''

* '''Power :''' Connect the sensor's power to the 5v Vref on RaceCapture/Pro
* '''Ground :''' Connect the sensor's ground connection to the ground shared by RaceCapture/Pro
* '''Sensor Output :''' Connect the Sensor Output to one of RaceCapture/Pro's timer input channels
 

'''Optional pull up resistor'''
RaceCapture/Pro requires both a voltage and ground pulse provided in the waveform provided by the sensor. Most sensors provide an internal pull-up resistor so an active square wave can be observed on the output. However, some sensors only switch ground and leave the output line in a high impedance state when not active, like opening and closing a mechanical switch. If the sensor does not provide a pull-up resistor the wheel speed signal may have noise and glitches which may be observed as high value glitches in the dashboard and log file data.

If it's determined a pull-up resistor is needed:

* Use 2.2 to 10K pull-up resistor can be added close to RaceCapture/Pro to ensure a clear signal
* You can use the SensorX breakout board to conveniently wire this pull-up resistor

==Recommended RPM Sensor==
'''[Autosport Labs CoilX RPM Input adapter ]'''
[[Image:CoilX.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/coilx-rpm-input-adapter/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_COILX
* '''Input Connection :''' Red: Coil Signal || Black: Ground (External)
* '''Output/ To Realitycapture :''' Yellow: 5v power || Black: Output || Red: Ground (data system)
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Caution :''' Do not exceed 5 volts or damage to module will occur
* '''Use :''' The CoilX sensor module is designed to safely interface the noisy, high voltage RPM signal at the ignition coil pack primary into a clean signal that RaceCapture/Pro can process.
* '''Installation Instruction :''' [https://wiki.autosportlabs.com/CoilX Click here]

 

==Recommended Wheel Speed / Gear speed Sensors==

[[Image:Hamlin_55505_gear_wheel_speed_sensor.jpg|200px|thumb|right]]
'''[Hamlin 55505 : Hall Effect Flange Mount Geartooth Sensor ]''' 
The specification of the sensor are as follows.

* '''Mfg / Prt :''' Hamlin 55505
* '''Pullup resistor :''' Simple 3 wire hookup - No external pullup resistor required
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 4.75 to 24 V
* '''Supply Current :''' 1 to 10.5 mA
* '''Operating Temperature :''' -40 to 125c
* '''Use :''' Rugged Hall effect sensor suitable for harsh automotive environments (fuels, solvents, lubricants)
* '''Datasheet : ''' [https://eu.mouser.com/datasheet/2/240/Littelfuse_Hall_Effect_Sensors_55505_Datasheet.pdf-938889.pdf Click here]
 
 
'''[Cherry GS100701 : GS100701 Gear Speed Sensor ]''' 

The specification of the sensor are as follows.
[[Image:Cherry_GS100701_gear_speed_sensor.jpg|200px|thumb|right]]
* '''Mfg / Prt :''' Cherry GS100701
* '''Thread Size :''' 15/32-32
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 5 to 24 V
* '''Supply Current :''' 3 to 6 mA
* '''Operating Temperature :''' -40 to 125c
* '''Body Material :''' Aluminum
* '''Output current :''' 25mA max
* '''Datasheet :''' [https://www.jameco.com/Jameco/Products/ProdDS/512401.pdf Click here]

=Distance Sensors=

Distance sensors are also a type of active sensors, except string potentiometer sensor, which is a passive device. Distance sensors also provide variable voltage output. These sensors are particularly easy to wire. Nearly all distance Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting distance sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Ride Height Sensors==
[[File:500mm String Potentiometer.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/500mm-string-potentiometer-sensor/]] 

'''[ASL_STRING_POT_M8 : 500mm string potentiometer sensor]'''

The specification are as follows.

* '''Mfg / Prt :''' ASL_STRING_POT_M8
* '''Measurement Range :''' Up to 2 meters,
* '''Draw Cable :''' 500mm stainless steel draw cable
* '''Connector :''' M8 3P connector, works with our plug and play harness system
* '''Cable :''' 2 meter cable
* '''Range :''' 10K ohm range
* '''Pinout :''' Pin 1 : Ground || Pin 2 : Ground || Pin 3 : Signal
* '''Mount Type :''' Three mounting holes available for mounting
* '''Uses :''' Used to measure steering angle or linear travel
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]

'''[ Sharp GP2D12 : IR Range Sensor]''' 

[[Image:Sensor_GP2D12.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' Sharp GP2D12
* '''Detecting Range :''' 10-80cm
* '''Connection :''' 3 Pin JST cable
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage supply :''' -0.3 to 7.0 V
* '''Average current consumption:''' 33 mA
* '''Output Terminal Voltage :''' -0.3 to (VCC + 0.3)
* '''Uses :''' Used for ride height position (pointed at ground) and pedal position measurement
* '''Datasheet :''' [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1/GP2D12.pdf Click here]
 
 
'''[ BMW 37140141444 : Height Level Sensor]'''
 
[[Image:BMW_37140141444_ride_height_sensor.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Pigtail :''' 61138383300
* '''Measurement Range :''' Measures distance over 90 degrees of the arm travel.
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage Supply :''' 5V
* '''Output Terminal Voltage :''' 0-5v
* '''Uses :''' Used as a ride-height sensor for BMW and Mini applications for auto-leveling headlights
 
 

[[Image:KA_Sensors_RHL3_Laser_Ride_Height_Sensor.jpg|200px |thumb|right]]
'''[ KA Sensors RHL3 : Laser Ride Height Sensor]'''
 
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Electrical Connection :''' Cable: 26AWG, 55spec wire+DR25 sleeve or ASL Conn.
* '''Measurement Range :''' 200mm (60-260) or 500mm (200-700)
* '''Pinout :''' Red (Pin1) : +Ve Supply || Black (Pin 2) : Ground || White (Pin 3) : Signal || Pin 4 & 5 : Not Connected
* '''Voltage Supply :''' 11-30v (50mA) ( Separate power supply required )
* '''Output Terminal Voltage :''' 1-5v
* '''Body Material :''' Aluminum
* '''Datasheet :''' [https://www.kasensors.com/sites/default/files/downloads/RHL3_Laser_Ride_Height_Sensor_Datasheet_RHL3_1115.pdf Click here]
 

=== Analog Channel Configuration of Ride Height Sensors ===

'''Note :''' Please follow the below instruction for all the ride height sensors analog channel configuration.
 

'''Step To Calibrate :'''

# After installation place the vehicle on a level surface
# Set the Analog calibration to 0-5v simple linear scaling
# At rest, note the voltage of the sensor. This is the zero level.
# Raise and safely support the corner of the vehicle and remove the spring.
# Move the suspension arm to full droop. Note actual inches / mm traveled and also note the voltage logged by RaceCapture/Pro
# Move the suspension arm to full compression. Note actual inches / mm and also note the voltage logged by RaceCapture/Pro 

 
'''Create Calibration Table:''' 

# Place the droop voltage / distance combination into the 1st column of the calibration table. Make the distance negative
# Place the 'at rest' voltage into the 2nd column of the calibration table. Make the distance zero
# Place the compression voltage / distance into the 3rd column of the calibration table. Make the distance positive
# Repeat the compression voltage / distance values for the 4th and 5th columns

=Angle/Rotation Sensors=
These type of sensors are passive devices comprising some form of a variable resistor.

'''Steps for connecting Angle/Rotation Sensors'''
* Consult the sensor's technical documentation for sensor connections.
* Connect one of the outside legs of the variable resistor to the ground point for RaceCapture/Pro
* Connect the opposite leg of the variable resistor to the 5v Vref of RaceCapture/Pro
* Connect the variable resistor wiper (typically the center lead) to the the desired analog input port of RaceCapture/Pro
* During calibration, if the sensor reads backwards, flip the 5v and ground connections.
 

'''Note :''' Users can follow the same instruction for connecting string Potentiometer
[[Image:Potentiometer Sensor Connection.png]]
==Recommended Throttle Position (TPS) Sensor==
[[Image:TPS-45.jpg|200px|thumb|right]]
'''[Ford / SMP TH45 : Throttle Position Sensor]'''

The specifications are as follows.
* '''Mfg/Prt :''' Ford / SMP TH45
* '''Pigtail :''' Pico 5752PT
* '''Supply Voltage :''' 5V
* '''Analog Channel Configuration :'''To calibrate, note the voltage at 0% throttle and then at 100% throttle. Use these two numbers to create a 2 point analog scaling map
* '''Use :''' Common Ford style Throttle Position sensor

=Fuel Level Sensor=

Fuel Level Sensors are also variable resistor, these provide variable resistance based on the level of the float.

'''Wiring''' 

Determine if you need a pullup resistor, or if you are tapping into an existing circuit with a gauge.

'''If you already have a gauge connected''', you will not need a pullup resistor - the gauge's internal circuitry already provides one. You will only need to tap into the existing signal feeding the fuel gauge sender. Jump to the calibration process below. 

'''Note :''' You will need to ensure the sender does not exceed 5v during calibration. if it does, you will need an additional voltage divider to scale the voltage down to 0-5v required by the RaceCapture input. 

[[Image:Fuel_level_sender_with_existing_gauge.png]]

If you have no gauge / you want to only use RaceCapture for your dashboard gauge, want to directly integrate with RaceCapture's analog input, follow this procedure.
* Choose a pull-up resistor value based on the the sender's ohm range. If it is less than 1000 ohms, then choose a 1000 (1K) ohm resistor as your pull-up. If the sender range is higher than 1000 ohms, choose a 2.2K resistor
**Rule of thumb - choose a resistor that is about 2X to 4X the maximum resistance of the sender
**A 1/2 watt, 1% accuracy resistor is recommended

* Wire up the sender per the diagram:
**Connect the ground of the fuel level sender to ground (ideally the same ground point used by RaceCapture)
**Connect the output of the sender to one of RaceCapture's analog inputs
**Connect the pullup resistor between +5v reference and the sender's output. This creates the voltage divider circuit which will present RaceCapture with a variable voltage depending on fuel level.
[[file:Fuel_level_sender_direct_connection.png]]

==Fuel level sensor calibration==
Once you have your sensor connected, you will need to calibrate it.

In the RaceCapture analog configuration screen, set the reading to Raw voltage (0-5v) so RaceCapture acts as a volt meter, showing the raw value on the dashboard. Alternatively, you can use a separate volt-meter, directly measuring the signal.

Empty the tank, and then take measurements with the tank at different fill levels:
* 0%
* 25%
* 50%
* 75%
* 100%

Configure your analog channel with the channel set to Interpolated mapping mode and then entering the following into the table.

[[file:RaceCapture_app_fuel_level_calibration_smoothing.jpg|800px]]

==Smoothing the channel to deal with slosh==
To have the smoothest readings, we suggest setting the channel sample rate to 1Hz and set the smoothing level to "max"

Enter 0,25,50,75,100 as the scaled value, and your measured voltages into the voltage row.

==Alternative Fuel level senders==
You may consider fuel level senders that output a convenient and clean 0-5v signal, avoiding the need to use pullup resistors.

[https://www.google.com/search?q=fuel+level+sender+for+racing+that+outputs+a+clean+0-5v+signal Fuel level senders with 0-5v signal output]

Regardless of the sensor you use, the calibration procedure still applies.

=Air/Fuel Ratio Sensor=
[[Image:Texense LSU 4.9 Sensor.png|200px|thumb|right]]
'''[Texense LSU 4.9 : Air / Fuel Ratio Sensors]'''

The specifications are as follows.

* '''Mfg/Prt :''' Texense LSU 4.9
* '''Pigtail''' : Built-in wiring
* '''Fitting :''' Screws into O2 sensor port
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Use :''' Use to measure the oxygen ratio in the exhaust gas of automobile engines (petrol or diesel)
* '''Datasheet :''' [https://www.sens4speed.com/images/produit/pdf/5cb9bc3f25e16669665015.pdf Click here]

=Thermal Sensor=
Thermal imaging sensors visualize how your tires are working, in real time, and use it to tune your suspension for maximum grip and balance. Thermal imaging sensors have superior accuracy and thermal compensation than other sensors, it’s thermal array design allows it measuring beyond tire temperatures.
==Recommended Thermal Sensors==
[[Image:tirex_3quarter.jpg|200px|right|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/tirex-advanced-thermal-sensor/]]
'''[ASL_TIREX_4PACK / ASL_TIREX_SINGLE : TireX advanced thermal sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_TIREX_4PACK / ASL_TIREX_SINGLE
* '''Sensor Resolution :''' 16 x 12 (192 pixels)
* '''Field of view :''' 110 x 75 degrees
* '''Accuracy :''' 1C
* '''Sample rate :''' 0.5 – 64Hz (Tire temperature mode) 0.5 – 10Hz (Full frame mode)
* '''Supply voltage :''' 6 – 12v
* '''Power :''' 200mW
* '''Harness :''' M8 4P Male, 250mm length
* '''Interface :''' CAN 2.0
* ''' Specifications and Installation guide :''' [https://wiki.autosportlabs.com/TireX Click here]

=SensorX sensor breakout board=
[[File:Seensorx sensor breakout.png|180px|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/sensorx-sensor-breakout-board/]] 

SensorX is a breakout / distribution board that will make it easier to use sensors that require pullup resistors as well as making available multiple ground and 5V Vref connections.

The built-in pullup resistors are easily disabled by breaking a designated trace on the board. This board is compact; enough to be bundled inline with your wiring harness and covered in heat shrink tubing when complete.

The features of boards are as follows.
* Breakout board is use to combine up to 7 analog sensor inputs and their matching ground connections and 5v power connections.
* Dimensions: 0.4″ x 4″
* Five 2.2K resistors
* For more details : [https://wiki.autosportlabs.com/SensorX Click here]

=Wiring Analog Sensors=
==RaceCapture/Pro Analog Input Specifications==

* '''Total Analog Inputs :''' 8 ( the 8th input is wired internally to measuring battery voltage.)
* '''Analog Input Voltage Range :''' 0 to 5V
* '''Input Impedance :''' Over 1 mega ohm

==Calibrating Analog Sensors==
===Linear Sensors===
A linear sensor specify two voltages/value pairs representing a low and high range for the sensor. A straight line is drawn between the points on the sensor.

'''Example : 150 PSI pressure sensor'''
* 0.5 v = 0 PSI
* 4.5 v = 150 PSI

In the Analog Channel configuration, select the "'Mapped"' sensor mode, and then enter the values into the interpolated mapping grid.

* For column 1, enter the low voltage range in the Volts cell, and the low scaled value in the Scaled cell.
* For columns 2-5 enter the high voltage range in the Volts cell, and the high scaled value in the Scaled cell 
 

[[file:linear_sensor_mapping.png]]

 
===Curved Sensors===
Curved sensors are usually thermistor based sensors, where the response is not a straight line, but a curve. Multiple points can be used to sufficiently approximate the curve.

'''Note :''' RaceCapture linearly interpolates the scaled values between the sensor points, so value transitions will be smooth.

'''Example : Extended range temperature sensor with 5v reference and 2.2K pullup resistor'''
* 0.4 v = 302 F
* 0.87 v = 239 F
* 1.88 v = 176 F
* 3.2 v = 122 F
* 4.72 v = 32 F

In the Analog Channel configuration, select the Mapped sensor mode, and then enter the values into the interpolated mapping grid. 

[[file:curved_sensor_mapping.png]] 

'''Note :''' If you have more than 5 points for the curve, spread the selection of points evenly between your low and high range.

===Fuel Level Sensors===
Fuel Level Sensors are usually variable resistance based sensors, and provide a variable resistance based on the level of the float.

'''Calibration''' 

With the fuel at different levels, measure and note the voltage present at the RaceCapture analog input for different fuel levels:

* Empty (0%)
* 1/4 (25%)
* 1/2 (50%)
* 3/4 (75%)
* Full (100%)
 

'''Set up the Analog Channel'''
# Choose an available analog input for your Fuel Level channel, then select the basic fuel level preset by selecting Fuel Level in the dropdown list. (This pre-sets the units (%), logging precision and min / max values. You can edit this by pressing the gear button next to the channel name
# Set the sample rate to 1Hz.
# Set the mode to Mapped. This will let you create a curved mapping for the sensor voltage.
# Set the smoothing to Maximum - this will help account for variances due to fuel slosh.
# Enter the mapped values noted in the calibration process into the Analog Channel mapping editor under RaceCapture setup. This will provide the calibration curve for your fuel tank.
# Write these settings back to RaceCapture and observe your fuel level readings in units of percentage.
 

'''Example BMW E36 fuel level mapping'''

Example BMW E36 Fuel curve mapping (your sender's calibration will be different)

[[file:BMW_E36_fuel_level_curve.png]]

RaceCapturePro Sensors

2026-04-03T15:51:37Z

Brentp: /* Preparation */

=IMU (Accelerometer / Gyro)=

Systems with an on-board IMU should be mounted in the default orientation, typically with the device connectors oriented towards the front of the vehicle.
* '''Note''' Check the model's documentation for the specific mounting guide.

==Mounting in an alternate orientation==
The system can be mounted in an alternate orientation, ideally in square 90 degree increments. For example:
* Inverted mounting
* Flat / upright, but rotated 90 degrees
* On-edge, but aligned with the front-rear axis of the vehicle

Re-orientation requires re-mapping of the accelerometer channels, using the RaceCapture app
[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Re-orientation procedure==

===Preparation===
Prior remapping, creata a temporary racecapture dashboard with the 6 channels (AccelX, AccelY, AccelZ, Yaw, Pitch, Roll)

Detach the system from the vehicle, and visually note the behavior of each channel by moving the system about in free air. See the diagram for reference:

[[image:yaw_pitch_roll_x_y_z_race_car_diagram.jpg|500px]]

===Remapping channels===
Now, hold the device in free air at the '''new orientation''', and then swap / invert IMU channels using the RaceCapture app to attain the behavior seen with the default orientation and default channel mapping settings.

==Zero Calibration==
After orientation is updated (as needed) and the system is mounted to the vehicle, ensure the vehicle is on a level surface. Then, perform a final zero calibration by pressing the Calibrate button in the RaceCapture app. This will zero out all 6 axis. At this point you can perform a final write / save of your configuration

=Temperature Sensors=

Temperature sensors are passive devices that measure temperature through the use of a thermistor, a resistor that varies resistance with temperature. We recommend using dedicated, two wire ECU-style sensor similar to the types specified in our recommended sensor list for best results.
<center>[[Image:temp_sensor_connection.png|500px]]</center>

'''Pullup Resistor'''

A pullup resistor is needed to create the necessary voltage divider circuit so RaceCapture/Pro's analog input can measure temperature as a varying voltage. This pullup resistor is connected to the 5v reference on the RaceCapture/Pro terminal block.

'''High Resistance ECU style sensors''' Use a 2.2K ohm pull-up resistor for high resistance ECU style sensors, such as the temperature sensors in [[#Sensors|supported list]]

'''Low Resistance Gauge type sensors''' Low resistance gauge type sensors are not recommended. If you must use one of these types of sensors, a 1/4 watt 220 ohm pull-up resistor can be used for sensors such as VDO 323-095, 325-002 and similar.

'''Sensor Ground'''

Two wire ECU style temperature sensors have one sense lead and one ground lead. For best accuracy, connect the ground lead to the same ground point as RaceCapture/Pro. One wire gauge type sensors have the ground as the body of the sensor. Ensure the engine is properly grounded to the chassis via multiple ground straps.

==Recommended GM-Style Temperature Sensor==

[[File:-40 to 150C.jpg|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/40-to-150c-linear-temperature-sensor-with-plug-and-play-harness/]]

'''[ASL_LINEAR_TEMP_M8 : -40 to 150C Linear temperature sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_LINEAR_TEMP_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 1 Meter
* '''Pigtail / Harness connector :''' M8
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 3-5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Uses :''' The sensor is suitable for fluids such as oil, coolant and water
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 

[[Image:SU109_C.jpg|200px |thumb|right]]
'''[ Wells SU109 || SMP TX3 : Engine Coolant Temperature Sensor ]'''

The specification of the sensor are as follows. 

* '''Mfg / Prt :''' Wells SU109 || SMP TX3
* '''Thread Size :''' 3/8" NPT
* '''Cable length :''' N/A
* '''Pigtail :''' Pico 5615pt ( 2 pin terminal )
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Copper
* '''Uses :''' Used for air inlet temperature for normally aspirated engine
 

'''[ Wells SU107 || SMP TX3 : Air Intake / Charge Temperature Sensor]'''
[[Image:SU107_C.jpg|200px |thumb|right]]
The specification of the sensor are as follows
* '''Mfg / Prt :''' Wells SU107 || SMP AX1
* '''Thread Size :''' 3/8" NPT
* '''Pigtail :'''Pico 5616pt
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Brass
* '''Uses :''' Use for measuring air inlet / charge temperature measurement
* '''Caution :''' Due to the fragility of the sensing bulb, it is necessary to pot the base of the sensor leads with sensor-safe silicone when used in high vibration environments.

 

==Recommended Delphi-Style Temperature Sensor==

'''[ Delphi 12160855 || AEM-30-2012 : Extended temperature range sensor ]'''

[[Image:AEM-30-2012.jpg|200px |thumb|right]]
The specifications are as follows.
* '''Mfg / Prt :''' Delphi 12160855 equivalent || AEM-30-2012 Equivalent
* '''Thread Size :''' 1/8" - 27 NPTF
* '''Matting Connector :''' 12047662 connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resisto
* '''Voltage supply :''' 5V
* '''Body Material :''' Brass (PA66)
* '''Uses :''' Extended temperature range suitable for coolant and oil
* '''Datasheet :'''[https://eu.mouser.com/datasheet/2/105/dcs_drawing_12160855-1162047.pdf Click here]

=Pressure Sensors=

Pressure sensors are powered devices and are a type of active sensors. They provide a variable voltage output. Pressure sensors are particularly easy to wire. Nearly all Pressure Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting pressure sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Fluid Pressure Sensors==

'''Note :''' These sensors are appropriate for measuring fluid pressures in an engine. Not appropriate for measuring manifold boost or vacuum as these are relative pressure sensors. Use an absolute pressure sensor instead.
 

[[Image:10 Bar 150 psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/]]

'''[ASL_10_BAR_DELPHI3_M8 : 10 bar / 150 PSI pressure sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_10_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[ASL_150_BAR_DELPHI3_M8 : 150 bar / 2175 PSI pressure sensor ]'''
[[Image:150 BAR 2175 Psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/150-bar-2175-psi-pressure-sensor-with-plug-and-play-harness/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_150_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Use :'''Typically used for high pressure sensing, such as brake or clutch pressure
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[AEM 30-2131-150 : 150 PSI pressure sensor ]'''
[[Image:AEM-30-2131-150.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' AEM 30-2131-150
* '''Thread Size :''' 1/8″ NPT
* '''Pigtail :''' 3 pin GM connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Body Material :''' Brass
* '''Output :''' Linear response with an output between 0.5v and 4.5v
* '''Use :'''Appropriate for oil and fuel pressure measurement
* '''Data Sheet :''' [https://documents.holley.com/30-2131-xxx.pdf Click here]

 

==Recommended Manifold Pressure (MAP) Sensors==

'''[12223861 (GM) : Manifold Absolute Pressure MAP Sensor ]'''
[[Image:GM_3bar_map_sensor.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' 12223861 (GM)
* '''Pigtail :''' 15305891 (GM) or PT1035 (AC Delco)
* '''Operating Pressure :''' 40 TO 304 kPa
* '''Voltage supply :''' 5.1 +/- 0.36 V
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.619V to 4.818 VDC 
* '''Datasheet :'''[https://www.omnitekcorp.com/images/MAP3barspec.pdf Click here]
 
 
'''[Freescale MXP4250AP : 2.5 bar Manifold Absolute Pressure Sensor ]''' 
[[Image:Freescale-Semiconductor-MPX4250AP.jpg|200px|thumb|right]]
The specification of the sensor are as follows.
* '''Mfg / Prt :''' Freescale MXP4250AP
* '''Operating Pressure :''' 20 to 250 kPa
* '''Voltage supply :''' 4.85 to 5.35 VDC
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.2 to 4.9 V
* '''Use :''' An extremely popular MAP sensor used in the Megajolt ignition and Megasquirt fuel injection systems
* '''Datasheet :'''[https://www.nxp.com/docs/en/data-sheet/MPX4250A.pdf Click here]

=Pulse/Speed/RPM Sensors=

Wheel speed sensors generate a series of pulses as a toothed wheel passes by the face of the sensor. We recommend hall-effect style sensors, and these are provided with 3 connections:

* Power
* Ground
* Signal Output
 

Note: - We do not recommend using 2 wire Variable Reluctance (VR) type sensors. VR Sensors will require a conditioning circuit before being provided to the inputs of RaceCapture/Pro.
[[Image:speed_sensor_connection.png]]

'''Wiring the Speed Sensor'''

* '''Power :''' Connect the sensor's power to the 5v Vref on RaceCapture/Pro
* '''Ground :''' Connect the sensor's ground connection to the ground shared by RaceCapture/Pro
* '''Sensor Output :''' Connect the Sensor Output to one of RaceCapture/Pro's timer input channels
 

'''Optional pull up resistor'''
RaceCapture/Pro requires both a voltage and ground pulse provided in the waveform provided by the sensor. Most sensors provide an internal pull-up resistor so an active square wave can be observed on the output. However, some sensors only switch ground and leave the output line in a high impedance state when not active, like opening and closing a mechanical switch. If the sensor does not provide a pull-up resistor the wheel speed signal may have noise and glitches which may be observed as high value glitches in the dashboard and log file data.

If it's determined a pull-up resistor is needed:

* Use 2.2 to 10K pull-up resistor can be added close to RaceCapture/Pro to ensure a clear signal
* You can use the SensorX breakout board to conveniently wire this pull-up resistor

==Recommended RPM Sensor==
'''[Autosport Labs CoilX RPM Input adapter ]'''
[[Image:CoilX.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/coilx-rpm-input-adapter/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_COILX
* '''Input Connection :''' Red: Coil Signal || Black: Ground (External)
* '''Output/ To Realitycapture :''' Yellow: 5v power || Black: Output || Red: Ground (data system)
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Caution :''' Do not exceed 5 volts or damage to module will occur
* '''Use :''' The CoilX sensor module is designed to safely interface the noisy, high voltage RPM signal at the ignition coil pack primary into a clean signal that RaceCapture/Pro can process.
* '''Installation Instruction :''' [https://wiki.autosportlabs.com/CoilX Click here]

 

==Recommended Wheel Speed / Gear speed Sensors==

[[Image:Hamlin_55505_gear_wheel_speed_sensor.jpg|200px|thumb|right]]
'''[Hamlin 55505 : Hall Effect Flange Mount Geartooth Sensor ]''' 
The specification of the sensor are as follows.

* '''Mfg / Prt :''' Hamlin 55505
* '''Pullup resistor :''' Simple 3 wire hookup - No external pullup resistor required
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 4.75 to 24 V
* '''Supply Current :''' 1 to 10.5 mA
* '''Operating Temperature :''' -40 to 125c
* '''Use :''' Rugged Hall effect sensor suitable for harsh automotive environments (fuels, solvents, lubricants)
* '''Datasheet : ''' [https://eu.mouser.com/datasheet/2/240/Littelfuse_Hall_Effect_Sensors_55505_Datasheet.pdf-938889.pdf Click here]
 
 
'''[Cherry GS100701 : GS100701 Gear Speed Sensor ]''' 

The specification of the sensor are as follows.
[[Image:Cherry_GS100701_gear_speed_sensor.jpg|200px|thumb|right]]
* '''Mfg / Prt :''' Cherry GS100701
* '''Thread Size :''' 15/32-32
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 5 to 24 V
* '''Supply Current :''' 3 to 6 mA
* '''Operating Temperature :''' -40 to 125c
* '''Body Material :''' Aluminum
* '''Output current :''' 25mA max
* '''Datasheet :''' [https://www.jameco.com/Jameco/Products/ProdDS/512401.pdf Click here]

=Distance Sensors=

Distance sensors are also a type of active sensors, except string potentiometer sensor, which is a passive device. Distance sensors also provide variable voltage output. These sensors are particularly easy to wire. Nearly all distance Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting distance sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Ride Height Sensors==
[[File:500mm String Potentiometer.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/500mm-string-potentiometer-sensor/]] 

'''[ASL_STRING_POT_M8 : 500mm string potentiometer sensor]'''

The specification are as follows.

* '''Mfg / Prt :''' ASL_STRING_POT_M8
* '''Measurement Range :''' Up to 2 meters,
* '''Draw Cable :''' 500mm stainless steel draw cable
* '''Connector :''' M8 3P connector, works with our plug and play harness system
* '''Cable :''' 2 meter cable
* '''Range :''' 10K ohm range
* '''Pinout :''' Pin 1 : Ground || Pin 2 : Ground || Pin 3 : Signal
* '''Mount Type :''' Three mounting holes available for mounting
* '''Uses :''' Used to measure steering angle or linear travel
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]

'''[ Sharp GP2D12 : IR Range Sensor]''' 

[[Image:Sensor_GP2D12.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' Sharp GP2D12
* '''Detecting Range :''' 10-80cm
* '''Connection :''' 3 Pin JST cable
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage supply :''' -0.3 to 7.0 V
* '''Average current consumption:''' 33 mA
* '''Output Terminal Voltage :''' -0.3 to (VCC + 0.3)
* '''Uses :''' Used for ride height position (pointed at ground) and pedal position measurement
* '''Datasheet :''' [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1/GP2D12.pdf Click here]
 
 
'''[ BMW 37140141444 : Height Level Sensor]'''
 
[[Image:BMW_37140141444_ride_height_sensor.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Pigtail :''' 61138383300
* '''Measurement Range :''' Measures distance over 90 degrees of the arm travel.
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage Supply :''' 5V
* '''Output Terminal Voltage :''' 0-5v
* '''Uses :''' Used as a ride-height sensor for BMW and Mini applications for auto-leveling headlights
 
 

[[Image:KA_Sensors_RHL3_Laser_Ride_Height_Sensor.jpg|200px |thumb|right]]
'''[ KA Sensors RHL3 : Laser Ride Height Sensor]'''
 
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Electrical Connection :''' Cable: 26AWG, 55spec wire+DR25 sleeve or ASL Conn.
* '''Measurement Range :''' 200mm (60-260) or 500mm (200-700)
* '''Pinout :''' Red (Pin1) : +Ve Supply || Black (Pin 2) : Ground || White (Pin 3) : Signal || Pin 4 & 5 : Not Connected
* '''Voltage Supply :''' 11-30v (50mA) ( Separate power supply required )
* '''Output Terminal Voltage :''' 1-5v
* '''Body Material :''' Aluminum
* '''Datasheet :''' [https://www.kasensors.com/sites/default/files/downloads/RHL3_Laser_Ride_Height_Sensor_Datasheet_RHL3_1115.pdf Click here]
 

=== Analog Channel Configuration of Ride Height Sensors ===

'''Note :''' Please follow the below instruction for all the ride height sensors analog channel configuration.
 

'''Step To Calibrate :'''

# After installation place the vehicle on a level surface
# Set the Analog calibration to 0-5v simple linear scaling
# At rest, note the voltage of the sensor. This is the zero level.
# Raise and safely support the corner of the vehicle and remove the spring.
# Move the suspension arm to full droop. Note actual inches / mm traveled and also note the voltage logged by RaceCapture/Pro
# Move the suspension arm to full compression. Note actual inches / mm and also note the voltage logged by RaceCapture/Pro 

 
'''Create Calibration Table:''' 

# Place the droop voltage / distance combination into the 1st column of the calibration table. Make the distance negative
# Place the 'at rest' voltage into the 2nd column of the calibration table. Make the distance zero
# Place the compression voltage / distance into the 3rd column of the calibration table. Make the distance positive
# Repeat the compression voltage / distance values for the 4th and 5th columns

=Angle/Rotation Sensors=
These type of sensors are passive devices comprising some form of a variable resistor.

'''Steps for connecting Angle/Rotation Sensors'''
* Consult the sensor's technical documentation for sensor connections.
* Connect one of the outside legs of the variable resistor to the ground point for RaceCapture/Pro
* Connect the opposite leg of the variable resistor to the 5v Vref of RaceCapture/Pro
* Connect the variable resistor wiper (typically the center lead) to the the desired analog input port of RaceCapture/Pro
* During calibration, if the sensor reads backwards, flip the 5v and ground connections.
 

'''Note :''' Users can follow the same instruction for connecting string Potentiometer
[[Image:Potentiometer Sensor Connection.png]]
==Recommended Throttle Position (TPS) Sensor==
[[Image:TPS-45.jpg|200px|thumb|right]]
'''[Ford / SMP TH45 : Throttle Position Sensor]'''

The specifications are as follows.
* '''Mfg/Prt :''' Ford / SMP TH45
* '''Pigtail :''' Pico 5752PT
* '''Supply Voltage :''' 5V
* '''Analog Channel Configuration :'''To calibrate, note the voltage at 0% throttle and then at 100% throttle. Use these two numbers to create a 2 point analog scaling map
* '''Use :''' Common Ford style Throttle Position sensor

=Fuel Level Sensor=

Fuel Level Sensors are also variable resistor, these provide variable resistance based on the level of the float.

'''Wiring''' 

Determine if you need a pullup resistor, or if you are tapping into an existing circuit with a gauge.

'''If you already have a gauge connected''', you will not need a pullup resistor - the gauge's internal circuitry already provides one. You will only need to tap into the existing signal feeding the fuel gauge sender. Jump to the calibration process below. 

'''Note :''' You will need to ensure the sender does not exceed 5v during calibration. if it does, you will need an additional voltage divider to scale the voltage down to 0-5v required by the RaceCapture input. 

[[Image:Fuel_level_sender_with_existing_gauge.png]]

If you have no gauge / you want to only use RaceCapture for your dashboard gauge, want to directly integrate with RaceCapture's analog input, follow this procedure.
* Choose a pull-up resistor value based on the the sender's ohm range. If it is less than 1000 ohms, then choose a 1000 (1K) ohm resistor as your pull-up. If the sender range is higher than 1000 ohms, choose a 2.2K resistor
**Rule of thumb - choose a resistor that is about 2X to 4X the maximum resistance of the sender
**A 1/2 watt, 1% accuracy resistor is recommended

* Wire up the sender per the diagram:
**Connect the ground of the fuel level sender to ground (ideally the same ground point used by RaceCapture)
**Connect the output of the sender to one of RaceCapture's analog inputs
**Connect the pullup resistor between +5v reference and the sender's output. This creates the voltage divider circuit which will present RaceCapture with a variable voltage depending on fuel level.
[[file:Fuel_level_sender_direct_connection.png]]

==Fuel level sensor calibration==
Once you have your sensor connected, you will need to calibrate it.

In the RaceCapture analog configuration screen, set the reading to Raw voltage (0-5v) so RaceCapture acts as a volt meter, showing the raw value on the dashboard. Alternatively, you can use a separate volt-meter, directly measuring the signal.

Empty the tank, and then take measurements with the tank at different fill levels:
* 0%
* 25%
* 50%
* 75%
* 100%

Configure your analog channel with the channel set to Interpolated mapping mode and then entering the following into the table.

[[file:RaceCapture_app_fuel_level_calibration_smoothing.jpg|800px]]

==Smoothing the channel to deal with slosh==
To have the smoothest readings, we suggest setting the channel sample rate to 1Hz and set the smoothing level to "max"

Enter 0,25,50,75,100 as the scaled value, and your measured voltages into the voltage row.

==Alternative Fuel level senders==
You may consider fuel level senders that output a convenient and clean 0-5v signal, avoiding the need to use pullup resistors.

[https://www.google.com/search?q=fuel+level+sender+for+racing+that+outputs+a+clean+0-5v+signal Fuel level senders with 0-5v signal output]

Regardless of the sensor you use, the calibration procedure still applies.

=Air/Fuel Ratio Sensor=
[[Image:Texense LSU 4.9 Sensor.png|200px|thumb|right]]
'''[Texense LSU 4.9 : Air / Fuel Ratio Sensors]'''

The specifications are as follows.

* '''Mfg/Prt :''' Texense LSU 4.9
* '''Pigtail''' : Built-in wiring
* '''Fitting :''' Screws into O2 sensor port
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Use :''' Use to measure the oxygen ratio in the exhaust gas of automobile engines (petrol or diesel)
* '''Datasheet :''' [https://www.sens4speed.com/images/produit/pdf/5cb9bc3f25e16669665015.pdf Click here]

=Thermal Sensor=
Thermal imaging sensors visualize how your tires are working, in real time, and use it to tune your suspension for maximum grip and balance. Thermal imaging sensors have superior accuracy and thermal compensation than other sensors, it’s thermal array design allows it measuring beyond tire temperatures.
==Recommended Thermal Sensors==
[[Image:tirex_3quarter.jpg|200px|right|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/tirex-advanced-thermal-sensor/]]
'''[ASL_TIREX_4PACK / ASL_TIREX_SINGLE : TireX advanced thermal sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_TIREX_4PACK / ASL_TIREX_SINGLE
* '''Sensor Resolution :''' 16 x 12 (192 pixels)
* '''Field of view :''' 110 x 75 degrees
* '''Accuracy :''' 1C
* '''Sample rate :''' 0.5 – 64Hz (Tire temperature mode) 0.5 – 10Hz (Full frame mode)
* '''Supply voltage :''' 6 – 12v
* '''Power :''' 200mW
* '''Harness :''' M8 4P Male, 250mm length
* '''Interface :''' CAN 2.0
* ''' Specifications and Installation guide :''' [https://wiki.autosportlabs.com/TireX Click here]

=SensorX sensor breakout board=
[[File:Seensorx sensor breakout.png|180px|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/sensorx-sensor-breakout-board/]] 

SensorX is a breakout / distribution board that will make it easier to use sensors that require pullup resistors as well as making available multiple ground and 5V Vref connections.

The built-in pullup resistors are easily disabled by breaking a designated trace on the board. This board is compact; enough to be bundled inline with your wiring harness and covered in heat shrink tubing when complete.

The features of boards are as follows.
* Breakout board is use to combine up to 7 analog sensor inputs and their matching ground connections and 5v power connections.
* Dimensions: 0.4″ x 4″
* Five 2.2K resistors
* For more details : [https://wiki.autosportlabs.com/SensorX Click here]

=Wiring Analog Sensors=
==RaceCapture/Pro Analog Input Specifications==

* '''Total Analog Inputs :''' 8 ( the 8th input is wired internally to measuring battery voltage.)
* '''Analog Input Voltage Range :''' 0 to 5V
* '''Input Impedance :''' Over 1 mega ohm

==Calibrating Analog Sensors==
===Linear Sensors===
A linear sensor specify two voltages/value pairs representing a low and high range for the sensor. A straight line is drawn between the points on the sensor.

'''Example : 150 PSI pressure sensor'''
* 0.5 v = 0 PSI
* 4.5 v = 150 PSI

In the Analog Channel configuration, select the "'Mapped"' sensor mode, and then enter the values into the interpolated mapping grid.

* For column 1, enter the low voltage range in the Volts cell, and the low scaled value in the Scaled cell.
* For columns 2-5 enter the high voltage range in the Volts cell, and the high scaled value in the Scaled cell 
 

[[file:linear_sensor_mapping.png]]

 
===Curved Sensors===
Curved sensors are usually thermistor based sensors, where the response is not a straight line, but a curve. Multiple points can be used to sufficiently approximate the curve.

'''Note :''' RaceCapture linearly interpolates the scaled values between the sensor points, so value transitions will be smooth.

'''Example : Extended range temperature sensor with 5v reference and 2.2K pullup resistor'''
* 0.4 v = 302 F
* 0.87 v = 239 F
* 1.88 v = 176 F
* 3.2 v = 122 F
* 4.72 v = 32 F

In the Analog Channel configuration, select the Mapped sensor mode, and then enter the values into the interpolated mapping grid. 

[[file:curved_sensor_mapping.png]] 

'''Note :''' If you have more than 5 points for the curve, spread the selection of points evenly between your low and high range.

===Fuel Level Sensors===
Fuel Level Sensors are usually variable resistance based sensors, and provide a variable resistance based on the level of the float.

'''Calibration''' 

With the fuel at different levels, measure and note the voltage present at the RaceCapture analog input for different fuel levels:

* Empty (0%)
* 1/4 (25%)
* 1/2 (50%)
* 3/4 (75%)
* Full (100%)
 

'''Set up the Analog Channel'''
# Choose an available analog input for your Fuel Level channel, then select the basic fuel level preset by selecting Fuel Level in the dropdown list. (This pre-sets the units (%), logging precision and min / max values. You can edit this by pressing the gear button next to the channel name
# Set the sample rate to 1Hz.
# Set the mode to Mapped. This will let you create a curved mapping for the sensor voltage.
# Set the smoothing to Maximum - this will help account for variances due to fuel slosh.
# Enter the mapped values noted in the calibration process into the Analog Channel mapping editor under RaceCapture setup. This will provide the calibration curve for your fuel tank.
# Write these settings back to RaceCapture and observe your fuel level readings in units of percentage.
 

'''Example BMW E36 fuel level mapping'''

Example BMW E36 Fuel curve mapping (your sender's calibration will be different)

[[file:BMW_E36_fuel_level_curve.png]]

RaceCapturePro Sensors

2026-04-03T15:47:16Z

Brentp:

=IMU (Accelerometer / Gyro)=

Systems with an on-board IMU should be mounted in the default orientation, typically with the device connectors oriented towards the front of the vehicle.
* '''Note''' Check the model's documentation for the specific mounting guide.

==Mounting in an alternate orientation==
The system can be mounted in an alternate orientation, ideally in square 90 degree increments. For example:
* Inverted mounting
* Flat / upright, but rotated 90 degrees
* On-edge, but aligned with the front-rear axis of the vehicle

Re-orientation requires re-mapping of the accelerometer channels, using the RaceCapture app
[[image:racecapture_app_setup_accel_gyro_sensors.jpg|800px]]

==Re-orientation procedure==

===Preparation===
Prior remapping, configure a racecapture dashboard with the 6 channels (AccelX, AccelY, AccelZ, Yaw, Pitch, Roll)

Detach the system from the vehicle, and visually note the behavior of each channel by moving the system about in free air. See the diagram for reference:

[[image:yaw_pitch_roll_x_y_z_race_car_diagram.jpg|500px]]

===Remapping channels===
Now, hold the device in free air at the '''new orientation''', and then swap / invert IMU channels using the RaceCapture app to attain the behavior seen with the default orientation and default channel mapping settings.

==Zero Calibration==
After orientation is updated (as needed) and the system is mounted to the vehicle, ensure the vehicle is on a level surface. Then, perform a final zero calibration by pressing the Calibrate button in the RaceCapture app. This will zero out all 6 axis. At this point you can perform a final write / save of your configuration

=Temperature Sensors=

Temperature sensors are passive devices that measure temperature through the use of a thermistor, a resistor that varies resistance with temperature. We recommend using dedicated, two wire ECU-style sensor similar to the types specified in our recommended sensor list for best results.
<center>[[Image:temp_sensor_connection.png|500px]]</center>

'''Pullup Resistor'''

A pullup resistor is needed to create the necessary voltage divider circuit so RaceCapture/Pro's analog input can measure temperature as a varying voltage. This pullup resistor is connected to the 5v reference on the RaceCapture/Pro terminal block.

'''High Resistance ECU style sensors''' Use a 2.2K ohm pull-up resistor for high resistance ECU style sensors, such as the temperature sensors in [[#Sensors|supported list]]

'''Low Resistance Gauge type sensors''' Low resistance gauge type sensors are not recommended. If you must use one of these types of sensors, a 1/4 watt 220 ohm pull-up resistor can be used for sensors such as VDO 323-095, 325-002 and similar.

'''Sensor Ground'''

Two wire ECU style temperature sensors have one sense lead and one ground lead. For best accuracy, connect the ground lead to the same ground point as RaceCapture/Pro. One wire gauge type sensors have the ground as the body of the sensor. Ensure the engine is properly grounded to the chassis via multiple ground straps.

==Recommended GM-Style Temperature Sensor==

[[File:-40 to 150C.jpg|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/40-to-150c-linear-temperature-sensor-with-plug-and-play-harness/]]

'''[ASL_LINEAR_TEMP_M8 : -40 to 150C Linear temperature sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_LINEAR_TEMP_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 1 Meter
* '''Pigtail / Harness connector :''' M8
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 3-5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Uses :''' The sensor is suitable for fluids such as oil, coolant and water
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 

[[Image:SU109_C.jpg|200px |thumb|right]]
'''[ Wells SU109 || SMP TX3 : Engine Coolant Temperature Sensor ]'''

The specification of the sensor are as follows. 

* '''Mfg / Prt :''' Wells SU109 || SMP TX3
* '''Thread Size :''' 3/8" NPT
* '''Cable length :''' N/A
* '''Pigtail :''' Pico 5615pt ( 2 pin terminal )
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Copper
* '''Uses :''' Used for air inlet temperature for normally aspirated engine
 

'''[ Wells SU107 || SMP TX3 : Air Intake / Charge Temperature Sensor]'''
[[Image:SU107_C.jpg|200px |thumb|right]]
The specification of the sensor are as follows
* '''Mfg / Prt :''' Wells SU107 || SMP AX1
* '''Thread Size :''' 3/8" NPT
* '''Pigtail :'''Pico 5616pt
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resistor
* '''Body Material :''' Brass
* '''Uses :''' Use for measuring air inlet / charge temperature measurement
* '''Caution :''' Due to the fragility of the sensing bulb, it is necessary to pot the base of the sensor leads with sensor-safe silicone when used in high vibration environments.

 

==Recommended Delphi-Style Temperature Sensor==

'''[ Delphi 12160855 || AEM-30-2012 : Extended temperature range sensor ]'''

[[Image:AEM-30-2012.jpg|200px |thumb|right]]
The specifications are as follows.
* '''Mfg / Prt :''' Delphi 12160855 equivalent || AEM-30-2012 Equivalent
* '''Thread Size :''' 1/8" - 27 NPTF
* '''Matting Connector :''' 12047662 connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' 2.2K pullup resisto
* '''Voltage supply :''' 5V
* '''Body Material :''' Brass (PA66)
* '''Uses :''' Extended temperature range suitable for coolant and oil
* '''Datasheet :'''[https://eu.mouser.com/datasheet/2/105/dcs_drawing_12160855-1162047.pdf Click here]

=Pressure Sensors=

Pressure sensors are powered devices and are a type of active sensors. They provide a variable voltage output. Pressure sensors are particularly easy to wire. Nearly all Pressure Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting pressure sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Fluid Pressure Sensors==

'''Note :''' These sensors are appropriate for measuring fluid pressures in an engine. Not appropriate for measuring manifold boost or vacuum as these are relative pressure sensors. Use an absolute pressure sensor instead.
 

[[Image:10 Bar 150 psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/10-bar-150-psi-pressure-sensor-with-plug-and-play-harness/]]

'''[ASL_10_BAR_DELPHI3_M8 : 10 bar / 150 PSI pressure sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_10_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[ASL_150_BAR_DELPHI3_M8 : 150 bar / 2175 PSI pressure sensor ]'''
[[Image:150 BAR 2175 Psi.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/150-bar-2175-psi-pressure-sensor-with-plug-and-play-harness/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_150_BAR_DELPHI3_M8
* '''Thread Size :''' 1/8″ NPT
* '''Cable length :''' 2 Meter
* '''Harness connector :''' M8 plug and play harness connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pull up resistor :''' Not required
* '''Voltage supply :''' 5V
* '''Pinout :''' Pin 1 : Ground || Pin 2 : 5V || Pin 3 : Signal Output
* '''Body Material :''' Stainless Steel
* '''Output :''' Linear response output between 0.5v and 4.5v
* '''Use :'''Typically used for high pressure sensing, such as brake or clutch pressure
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]
 
 

'''[AEM 30-2131-150 : 150 PSI pressure sensor ]'''
[[Image:AEM-30-2131-150.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' AEM 30-2131-150
* '''Thread Size :''' 1/8″ NPT
* '''Pigtail :''' 3 pin GM connector
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Body Material :''' Brass
* '''Output :''' Linear response with an output between 0.5v and 4.5v
* '''Use :'''Appropriate for oil and fuel pressure measurement
* '''Data Sheet :''' [https://documents.holley.com/30-2131-xxx.pdf Click here]

 

==Recommended Manifold Pressure (MAP) Sensors==

'''[12223861 (GM) : Manifold Absolute Pressure MAP Sensor ]'''
[[Image:GM_3bar_map_sensor.jpg|200px|thumb|right]]
The specification of the sensor are as follows.

* '''Mfg / Prt :''' 12223861 (GM)
* '''Pigtail :''' 15305891 (GM) or PT1035 (AC Delco)
* '''Operating Pressure :''' 40 TO 304 kPa
* '''Voltage supply :''' 5.1 +/- 0.36 V
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.619V to 4.818 VDC 
* '''Datasheet :'''[https://www.omnitekcorp.com/images/MAP3barspec.pdf Click here]
 
 
'''[Freescale MXP4250AP : 2.5 bar Manifold Absolute Pressure Sensor ]''' 
[[Image:Freescale-Semiconductor-MPX4250AP.jpg|200px|thumb|right]]
The specification of the sensor are as follows.
* '''Mfg / Prt :''' Freescale MXP4250AP
* '''Operating Pressure :''' 20 to 250 kPa
* '''Voltage supply :''' 4.85 to 5.35 VDC
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Pinout :''' Pin A : Ground || Pin B : Signal || Pin C : Power
* '''Output :''' 0.2 to 4.9 V
* '''Use :''' An extremely popular MAP sensor used in the Megajolt ignition and Megasquirt fuel injection systems
* '''Datasheet :'''[https://www.nxp.com/docs/en/data-sheet/MPX4250A.pdf Click here]

=Pulse/Speed/RPM Sensors=

Wheel speed sensors generate a series of pulses as a toothed wheel passes by the face of the sensor. We recommend hall-effect style sensors, and these are provided with 3 connections:

* Power
* Ground
* Signal Output
 

Note: - We do not recommend using 2 wire Variable Reluctance (VR) type sensors. VR Sensors will require a conditioning circuit before being provided to the inputs of RaceCapture/Pro.
[[Image:speed_sensor_connection.png]]

'''Wiring the Speed Sensor'''

* '''Power :''' Connect the sensor's power to the 5v Vref on RaceCapture/Pro
* '''Ground :''' Connect the sensor's ground connection to the ground shared by RaceCapture/Pro
* '''Sensor Output :''' Connect the Sensor Output to one of RaceCapture/Pro's timer input channels
 

'''Optional pull up resistor'''
RaceCapture/Pro requires both a voltage and ground pulse provided in the waveform provided by the sensor. Most sensors provide an internal pull-up resistor so an active square wave can be observed on the output. However, some sensors only switch ground and leave the output line in a high impedance state when not active, like opening and closing a mechanical switch. If the sensor does not provide a pull-up resistor the wheel speed signal may have noise and glitches which may be observed as high value glitches in the dashboard and log file data.

If it's determined a pull-up resistor is needed:

* Use 2.2 to 10K pull-up resistor can be added close to RaceCapture/Pro to ensure a clear signal
* You can use the SensorX breakout board to conveniently wire this pull-up resistor

==Recommended RPM Sensor==
'''[Autosport Labs CoilX RPM Input adapter ]'''
[[Image:CoilX.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/coilx-rpm-input-adapter/]]

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_COILX
* '''Input Connection :''' Red: Coil Signal || Black: Ground (External)
* '''Output/ To Realitycapture :''' Yellow: 5v power || Black: Output || Red: Ground (data system)
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Caution :''' Do not exceed 5 volts or damage to module will occur
* '''Use :''' The CoilX sensor module is designed to safely interface the noisy, high voltage RPM signal at the ignition coil pack primary into a clean signal that RaceCapture/Pro can process.
* '''Installation Instruction :''' [https://wiki.autosportlabs.com/CoilX Click here]

 

==Recommended Wheel Speed / Gear speed Sensors==

[[Image:Hamlin_55505_gear_wheel_speed_sensor.jpg|200px|thumb|right]]
'''[Hamlin 55505 : Hall Effect Flange Mount Geartooth Sensor ]''' 
The specification of the sensor are as follows.

* '''Mfg / Prt :''' Hamlin 55505
* '''Pullup resistor :''' Simple 3 wire hookup - No external pullup resistor required
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 4.75 to 24 V
* '''Supply Current :''' 1 to 10.5 mA
* '''Operating Temperature :''' -40 to 125c
* '''Use :''' Rugged Hall effect sensor suitable for harsh automotive environments (fuels, solvents, lubricants)
* '''Datasheet : ''' [https://eu.mouser.com/datasheet/2/240/Littelfuse_Hall_Effect_Sensors_55505_Datasheet.pdf-938889.pdf Click here]
 
 
'''[Cherry GS100701 : GS100701 Gear Speed Sensor ]''' 

The specification of the sensor are as follows.
[[Image:Cherry_GS100701_gear_speed_sensor.jpg|200px|thumb|right]]
* '''Mfg / Prt :''' Cherry GS100701
* '''Thread Size :''' 15/32-32
* '''Pulse Channel Configuration :''' Configure the pulse channel with the number of pulses per revolution, which maps to the number of teeth on the gear / wheel.
* '''Supply Voltage :''' 5 to 24 V
* '''Supply Current :''' 3 to 6 mA
* '''Operating Temperature :''' -40 to 125c
* '''Body Material :''' Aluminum
* '''Output current :''' 25mA max
* '''Datasheet :''' [https://www.jameco.com/Jameco/Products/ProdDS/512401.pdf Click here]

=Distance Sensors=

Distance sensors are also a type of active sensors, except string potentiometer sensor, which is a passive device. Distance sensors also provide variable voltage output. These sensors are particularly easy to wire. Nearly all distance Sensors, active sensors, for automotive applications specify 5v power and produce an output within 0 to 5v, making them directly compatible with RaceCapture/Pro. Most pressure sensors have a linear output and therefore are very easy to calibrate.

'''Steps for connecting distance sensors'''
# Identify the power, ground and output signal wires. The sensor technical documentation will provide this information
# Connect the sensor ground to the same location as the ground point for RaceCapture/Pro
# If the sensor is 5v powered, connect it to the 5v voltage reference on RaceCapture/Pro
# Connect the sensor output signal to the desired analog input port of RaceCapture/Pro

</center>[[Image:Pressure Sensors Connections.png]]</center>

==Recommended Ride Height Sensors==
[[File:500mm String Potentiometer.png|200px|thumb|right]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/500mm-string-potentiometer-sensor/]] 

'''[ASL_STRING_POT_M8 : 500mm string potentiometer sensor]'''

The specification are as follows.

* '''Mfg / Prt :''' ASL_STRING_POT_M8
* '''Measurement Range :''' Up to 2 meters,
* '''Draw Cable :''' 500mm stainless steel draw cable
* '''Connector :''' M8 3P connector, works with our plug and play harness system
* '''Cable :''' 2 meter cable
* '''Range :''' 10K ohm range
* '''Pinout :''' Pin 1 : Ground || Pin 2 : Ground || Pin 3 : Signal
* '''Mount Type :''' Three mounting holes available for mounting
* '''Uses :''' Used to measure steering angle or linear travel
* '''Full Harness Specifications :''' [https://wiki.autosportlabs.com/Harness_specifications#Single_analog/digital_channel| Click here]

'''[ Sharp GP2D12 : IR Range Sensor]''' 

[[Image:Sensor_GP2D12.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' Sharp GP2D12
* '''Detecting Range :''' 10-80cm
* '''Connection :''' 3 Pin JST cable
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage supply :''' -0.3 to 7.0 V
* '''Average current consumption:''' 33 mA
* '''Output Terminal Voltage :''' -0.3 to (VCC + 0.3)
* '''Uses :''' Used for ride height position (pointed at ground) and pedal position measurement
* '''Datasheet :''' [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/1/GP2D12.pdf Click here]
 
 
'''[ BMW 37140141444 : Height Level Sensor]'''
 
[[Image:BMW_37140141444_ride_height_sensor.jpg|200px |thumb|right]]
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Pigtail :''' 61138383300
* '''Measurement Range :''' Measures distance over 90 degrees of the arm travel.
* '''Pinout :''' Pin 1 : Signal || Pin 2 : Ground || Pin3 : Power
* '''Voltage Supply :''' 5V
* '''Output Terminal Voltage :''' 0-5v
* '''Uses :''' Used as a ride-height sensor for BMW and Mini applications for auto-leveling headlights
 
 

[[Image:KA_Sensors_RHL3_Laser_Ride_Height_Sensor.jpg|200px |thumb|right]]
'''[ KA Sensors RHL3 : Laser Ride Height Sensor]'''
 
The specification are as follows.

* '''Mfg / Prt :''' BMW 37140141444
* '''Electrical Connection :''' Cable: 26AWG, 55spec wire+DR25 sleeve or ASL Conn.
* '''Measurement Range :''' 200mm (60-260) or 500mm (200-700)
* '''Pinout :''' Red (Pin1) : +Ve Supply || Black (Pin 2) : Ground || White (Pin 3) : Signal || Pin 4 & 5 : Not Connected
* '''Voltage Supply :''' 11-30v (50mA) ( Separate power supply required )
* '''Output Terminal Voltage :''' 1-5v
* '''Body Material :''' Aluminum
* '''Datasheet :''' [https://www.kasensors.com/sites/default/files/downloads/RHL3_Laser_Ride_Height_Sensor_Datasheet_RHL3_1115.pdf Click here]
 

=== Analog Channel Configuration of Ride Height Sensors ===

'''Note :''' Please follow the below instruction for all the ride height sensors analog channel configuration.
 

'''Step To Calibrate :'''

# After installation place the vehicle on a level surface
# Set the Analog calibration to 0-5v simple linear scaling
# At rest, note the voltage of the sensor. This is the zero level.
# Raise and safely support the corner of the vehicle and remove the spring.
# Move the suspension arm to full droop. Note actual inches / mm traveled and also note the voltage logged by RaceCapture/Pro
# Move the suspension arm to full compression. Note actual inches / mm and also note the voltage logged by RaceCapture/Pro 

 
'''Create Calibration Table:''' 

# Place the droop voltage / distance combination into the 1st column of the calibration table. Make the distance negative
# Place the 'at rest' voltage into the 2nd column of the calibration table. Make the distance zero
# Place the compression voltage / distance into the 3rd column of the calibration table. Make the distance positive
# Repeat the compression voltage / distance values for the 4th and 5th columns

=Angle/Rotation Sensors=
These type of sensors are passive devices comprising some form of a variable resistor.

'''Steps for connecting Angle/Rotation Sensors'''
* Consult the sensor's technical documentation for sensor connections.
* Connect one of the outside legs of the variable resistor to the ground point for RaceCapture/Pro
* Connect the opposite leg of the variable resistor to the 5v Vref of RaceCapture/Pro
* Connect the variable resistor wiper (typically the center lead) to the the desired analog input port of RaceCapture/Pro
* During calibration, if the sensor reads backwards, flip the 5v and ground connections.
 

'''Note :''' Users can follow the same instruction for connecting string Potentiometer
[[Image:Potentiometer Sensor Connection.png]]
==Recommended Throttle Position (TPS) Sensor==
[[Image:TPS-45.jpg|200px|thumb|right]]
'''[Ford / SMP TH45 : Throttle Position Sensor]'''

The specifications are as follows.
* '''Mfg/Prt :''' Ford / SMP TH45
* '''Pigtail :''' Pico 5752PT
* '''Supply Voltage :''' 5V
* '''Analog Channel Configuration :'''To calibrate, note the voltage at 0% throttle and then at 100% throttle. Use these two numbers to create a 2 point analog scaling map
* '''Use :''' Common Ford style Throttle Position sensor

=Fuel Level Sensor=

Fuel Level Sensors are also variable resistor, these provide variable resistance based on the level of the float.

'''Wiring''' 

Determine if you need a pullup resistor, or if you are tapping into an existing circuit with a gauge.

'''If you already have a gauge connected''', you will not need a pullup resistor - the gauge's internal circuitry already provides one. You will only need to tap into the existing signal feeding the fuel gauge sender. Jump to the calibration process below. 

'''Note :''' You will need to ensure the sender does not exceed 5v during calibration. if it does, you will need an additional voltage divider to scale the voltage down to 0-5v required by the RaceCapture input. 

[[Image:Fuel_level_sender_with_existing_gauge.png]]

If you have no gauge / you want to only use RaceCapture for your dashboard gauge, want to directly integrate with RaceCapture's analog input, follow this procedure.
* Choose a pull-up resistor value based on the the sender's ohm range. If it is less than 1000 ohms, then choose a 1000 (1K) ohm resistor as your pull-up. If the sender range is higher than 1000 ohms, choose a 2.2K resistor
**Rule of thumb - choose a resistor that is about 2X to 4X the maximum resistance of the sender
**A 1/2 watt, 1% accuracy resistor is recommended

* Wire up the sender per the diagram:
**Connect the ground of the fuel level sender to ground (ideally the same ground point used by RaceCapture)
**Connect the output of the sender to one of RaceCapture's analog inputs
**Connect the pullup resistor between +5v reference and the sender's output. This creates the voltage divider circuit which will present RaceCapture with a variable voltage depending on fuel level.
[[file:Fuel_level_sender_direct_connection.png]]

==Fuel level sensor calibration==
Once you have your sensor connected, you will need to calibrate it.

In the RaceCapture analog configuration screen, set the reading to Raw voltage (0-5v) so RaceCapture acts as a volt meter, showing the raw value on the dashboard. Alternatively, you can use a separate volt-meter, directly measuring the signal.

Empty the tank, and then take measurements with the tank at different fill levels:
* 0%
* 25%
* 50%
* 75%
* 100%

Configure your analog channel with the channel set to Interpolated mapping mode and then entering the following into the table.

[[file:RaceCapture_app_fuel_level_calibration_smoothing.jpg|800px]]

==Smoothing the channel to deal with slosh==
To have the smoothest readings, we suggest setting the channel sample rate to 1Hz and set the smoothing level to "max"

Enter 0,25,50,75,100 as the scaled value, and your measured voltages into the voltage row.

==Alternative Fuel level senders==
You may consider fuel level senders that output a convenient and clean 0-5v signal, avoiding the need to use pullup resistors.

[https://www.google.com/search?q=fuel+level+sender+for+racing+that+outputs+a+clean+0-5v+signal Fuel level senders with 0-5v signal output]

Regardless of the sensor you use, the calibration procedure still applies.

=Air/Fuel Ratio Sensor=
[[Image:Texense LSU 4.9 Sensor.png|200px|thumb|right]]
'''[Texense LSU 4.9 : Air / Fuel Ratio Sensors]'''

The specifications are as follows.

* '''Mfg/Prt :''' Texense LSU 4.9
* '''Pigtail''' : Built-in wiring
* '''Fitting :''' Screws into O2 sensor port
* '''Analog Channel Configuration :''' Preset available in the RaceCapture app
* '''Use :''' Use to measure the oxygen ratio in the exhaust gas of automobile engines (petrol or diesel)
* '''Datasheet :''' [https://www.sens4speed.com/images/produit/pdf/5cb9bc3f25e16669665015.pdf Click here]

=Thermal Sensor=
Thermal imaging sensors visualize how your tires are working, in real time, and use it to tune your suspension for maximum grip and balance. Thermal imaging sensors have superior accuracy and thermal compensation than other sensors, it’s thermal array design allows it measuring beyond tire temperatures.
==Recommended Thermal Sensors==
[[Image:tirex_3quarter.jpg|200px|right|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/tirex-advanced-thermal-sensor/]]
'''[ASL_TIREX_4PACK / ASL_TIREX_SINGLE : TireX advanced thermal sensor ]'''

The specification of the sensor are as follows.

* '''Mfg / Prt :''' ASL_TIREX_4PACK / ASL_TIREX_SINGLE
* '''Sensor Resolution :''' 16 x 12 (192 pixels)
* '''Field of view :''' 110 x 75 degrees
* '''Accuracy :''' 1C
* '''Sample rate :''' 0.5 – 64Hz (Tire temperature mode) 0.5 – 10Hz (Full frame mode)
* '''Supply voltage :''' 6 – 12v
* '''Power :''' 200mW
* '''Harness :''' M8 4P Male, 250mm length
* '''Interface :''' CAN 2.0
* ''' Specifications and Installation guide :''' [https://wiki.autosportlabs.com/TireX Click here]

=SensorX sensor breakout board=
[[File:Seensorx sensor breakout.png|180px|thumb]]
[[Image:add_to_cart.png|70px|thumb|right|link=https://www.autosportlabs.com/product/sensorx-sensor-breakout-board/]] 

SensorX is a breakout / distribution board that will make it easier to use sensors that require pullup resistors as well as making available multiple ground and 5V Vref connections.

The built-in pullup resistors are easily disabled by breaking a designated trace on the board. This board is compact; enough to be bundled inline with your wiring harness and covered in heat shrink tubing when complete.

The features of boards are as follows.
* Breakout board is use to combine up to 7 analog sensor inputs and their matching ground connections and 5v power connections.
* Dimensions: 0.4″ x 4″
* Five 2.2K resistors
* For more details : [https://wiki.autosportlabs.com/SensorX Click here]

=Wiring Analog Sensors=
==RaceCapture/Pro Analog Input Specifications==

* '''Total Analog Inputs :''' 8 ( the 8th input is wired internally to measuring battery voltage.)
* '''Analog Input Voltage Range :''' 0 to 5V
* '''Input Impedance :''' Over 1 mega ohm

==Calibrating Analog Sensors==
===Linear Sensors===
A linear sensor specify two voltages/value pairs representing a low and high range for the sensor. A straight line is drawn between the points on the sensor.

'''Example : 150 PSI pressure sensor'''
* 0.5 v = 0 PSI
* 4.5 v = 150 PSI

In the Analog Channel configuration, select the "'Mapped"' sensor mode, and then enter the values into the interpolated mapping grid.

* For column 1, enter the low voltage range in the Volts cell, and the low scaled value in the Scaled cell.
* For columns 2-5 enter the high voltage range in the Volts cell, and the high scaled value in the Scaled cell 
 

[[file:linear_sensor_mapping.png]]

 
===Curved Sensors===
Curved sensors are usually thermistor based sensors, where the response is not a straight line, but a curve. Multiple points can be used to sufficiently approximate the curve.

'''Note :''' RaceCapture linearly interpolates the scaled values between the sensor points, so value transitions will be smooth.

'''Example : Extended range temperature sensor with 5v reference and 2.2K pullup resistor'''
* 0.4 v = 302 F
* 0.87 v = 239 F
* 1.88 v = 176 F
* 3.2 v = 122 F
* 4.72 v = 32 F

In the Analog Channel configuration, select the Mapped sensor mode, and then enter the values into the interpolated mapping grid. 

[[file:curved_sensor_mapping.png]] 

'''Note :''' If you have more than 5 points for the curve, spread the selection of points evenly between your low and high range.

===Fuel Level Sensors===
Fuel Level Sensors are usually variable resistance based sensors, and provide a variable resistance based on the level of the float.

'''Calibration''' 

With the fuel at different levels, measure and note the voltage present at the RaceCapture analog input for different fuel levels:

* Empty (0%)
* 1/4 (25%)
* 1/2 (50%)
* 3/4 (75%)
* Full (100%)
 

'''Set up the Analog Channel'''
# Choose an available analog input for your Fuel Level channel, then select the basic fuel level preset by selecting Fuel Level in the dropdown list. (This pre-sets the units (%), logging precision and min / max values. You can edit this by pressing the gear button next to the channel name
# Set the sample rate to 1Hz.
# Set the mode to Mapped. This will let you create a curved mapping for the sensor voltage.
# Set the smoothing to Maximum - this will help account for variances due to fuel slosh.
# Enter the mapped values noted in the calibration process into the Analog Channel mapping editor under RaceCapture setup. This will provide the calibration curve for your fuel tank.
# Write these settings back to RaceCapture and observe your fuel level readings in units of percentage.
 

'''Example BMW E36 fuel level mapping'''

Example BMW E36 Fuel curve mapping (your sender's calibration will be different)

[[file:BMW_E36_fuel_level_curve.png]]

File:Yaw pitch roll x y z race car diagram.jpg

2026-04-03T15:46:44Z

Brentp:

ESP32-CAN-X2

2026-03-25T14:20:02Z

Brentp: /* Power Ratings & Environmental Requirements */

=Introduction=

ESP32-CAN-X2 is an automotive-grade ESP32-based development board specifically designed for CAN communication. This board has all the features of a modern ESP32 development board, integrated Wi-Fi and Bluetooth, along with the extended CAN controller. Autosport Labs has specifically designed it for CAN communication in harsh automotive and industrial environment, while offering fast processing and computation options.

This is a complete how-to-use guide and this user guide will describe each and every step to use the board and harness the maximum potential of the board.

[[File:ESP32_CAN_X2_revD_3quarter.jpg|700px]]

=Purchasing=
You can order the ESP32-CAN-X2 from our online store:
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Features=

Features of ESP32-CAN-X2 development board:

* Flexible power supply options up to 40V, suitable for automotive and industrial applications
* Based on ESP32-S3-WROOM-1-N8R8 microcontroller powerful dual-core Xtensa LX6 CPU running at up to 240 MHz.
* 384 KB ROM, 512 KB SRAM, 16 KB SRAM in RTC, 8 MB PSRAM
* Two LED’s: Power LED and user-defined LED1
* Integrated Wi-Fi (802.11b/g/n) and Bluetooth capabilities
* Reset and Boot push button
* USB-C type socket for flashing, and power supply
* Integrated antenna for long-range communication
* Additional CAN communication controller CAN using MCP2515
* Two 4-pin headers are strategically positioned at the top for CAN communication.
* Easy-to-interface programming. Required no external debugger for flashing
* Integrated CAN transceivers
* Configurable CAN termination resistors, which can be disabled via breakable jumpers
* Support of a wide choice of commonly used Integrated Development Environments (IDEs)
* [https://github.com/autosportlabs/ESP32-CAN-X2/ Comprehensive free software libraries] and examples for CAN communication for Arduino and Circuit Python
* Supports a range of stackable [[#Bolt-ons|add-on boards]] offering additional features such as GPS, RGB LEDs, switches, and more.

=Bolt-ons=
Bolt-ons are stackable add-on boards that offer easy extensibility

Make your own bolt on with a blank design template https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/bolt-on-template
===GPS bolt-on===
Adds a high performance GPS receiver 
[[File:GPS Bolt-on image main.png|300px|link=Gps-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/gps-bolt-on/]]
===Button bolt-on===
Adds 4 tactile switches + RGB LEDs 
[[File:Button Bolt-on white background.jpg|300px|link=Button-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/button-bolt-on/]]
===RGB LED bolt-on===
Adds 10 RGB LEDs across two groups for alert indicators 
[[File:RGB LED Bolt-on.jpg|300px|link=RGB-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/rgb-led-bolt-on/]]

=Getting started=

This section will provide you with comprehensive information about the ESP32-CAN-X2 development board's key components, mechanical layout, power rating, & requirements. This detailed information helps you to use the board effectively and efficiently in your projects.

== Key Components of ESP32-CAN-X2 Development Board ==

Figure 1 given below indicates the important key components of the ESP32-CAN-X2 Development Board and their location on the board.

[[File:REV D Images updated.png|Figure 1]]

=== Microcontroller ===

The ESP32-CAN-X2 Development Board is designed around the ESP32-S3-WROOM-1-N8R8 microcontroller in a 40-pin package. The connections between the development board and the microcontroller is straightforward, where the majority of GPIO pins are directly connected with the external headers, SV1 & SV2, and some pins are reserved internal connections between the board and CAN controllers. The internal connections between the microcontroller and CAN controllers are shown in the CAN controller heading given below. The microcontroller pin layout is shown in Figure 2 given below.

[[File:Microcontroller pin layout.png|Figure 2]]

=== External Connection Header ===

External headers, SV1 & SV2, are the two other important components of this development board. SV1 is the left side dual row header and the SV2 is the right side dual row header. Both of these headers have 20 pins available for connection. These headers provide connections for GPIOs, power output, ground (GND), power input, and CAN communication pins. Both of these header pinouts have standard size, allowing users to connect them using jumper wires, a breadboard, or even solder wires permanently onto the development board. However, while doing the wire connection the customer must make sure that none of them get short circuit. The details regarding the pin's names, numbers, outputs, and functions are given in the Board Pinout section below.

=== CAN bus transceivers===

The following are the specifications of the CAN transceivers for CAN1 and CAN2:

'''Detection of Ground Fault'''
* Permanent Dominant Detection on TXD
* Permanent Dominant Detection on Bus
* Power-on Reset and Voltage Brown-Out

'''Protection on V DD Pin'''
* Protection Against Damage Due to Short-Circuit
Conditions (Positive or Negative Battery Voltage)
* Protection Against High-Voltage Transients in

'''Automotive Environments'''
* Automatic Thermal Shutdown Protection
* Suitable for 12V and 24V Systems
* Meets or exceeds stringent automotive design requirements including “Hardware Requirementsfor LIN, CAN and FlexRay Interfaces in Automotive Applications”, Version 1.3, May 2012
• High-Noise Immunity Due to Differential Bus Implementation
• High Electrostatic Discharge (ESD) Protection on CANH and CANL, meeting the IEC61000-4-2 up to ±14 kV

=== CAN Controllers ===

The MCP2515 external connected CAN communication controller, and ESP-32 built-in CAN communication controller are two other main components of this development board.

The MCP2515, operating as the second external CAN controller in this development board, is a specialized component designed for Controller Area Network (CAN) applications. Its features include:

* Implements CAN V2.0B at up to 1 Mb/s.
* High-Speed SPI Interface (10 MHz)
* Interrupt Output Pin with selectable enables
* Multiple receive and transmit buffers
* Low-Power CMOS Technology: - 5 mA active current (typical), 1 μA standby current
 
The internal CAN controller also works at CAN V2.0. The internal CAN supports two message formats:

* Base frame format (11-bit ID)
* Extended frame format (29-bit ID)
 
'''Internal pinout connection between the CAN controllers and ESP32'''

==== CAN 1 ====
This is a built-in CAN controller and its RX is connected to IO6 of the microcontroller and TX is connected to IO7 of the microcontroller. The connections are shown in Figure 3 given below

==== CAN 2 ====
This is the externally connected MCP2515 controller with the following connections:
{| class="wikitable" style="text-align:center; width:60%"
|+ '''MCP2515 ESP32-CAN-X2 GPIO connections'''
! Signal !! ESP32 GPIO
|-
| CS || 10
|-
| CLK || 12
|-
| MISO || 13
|-
| MOSI || 11
|-
| IRQ || 3
|}

Crystal: 16MHz
[[File:CAN Controller Connections ESP32.jpg|Figure 3]]

=== Two 4-Pin header Connector ===

The ESP32-CAN-X2 development board provides two additional 4-pin connector headers at the top of the board to support CAN communication. This header makes wiring the device more convenient and robust. The CAN communication connection pinout details are given in the pinout section below.

=== Built-in LED ===
The built-in blue LED is connected to GPIO2 of the ESP32. For a demo that exercises this LED, see the [https://github.com/autosportlabs/ESP32-CAN-X2/blob/main/arduino/ping_pong/ping_pong.ino#L23 ping-pong example].

=== USB-C Socket ===
The ESP32-CAN-X2 development board has one USB-C port. This port is used for multiple functions: it powers the board, allows programming, and facilitates serial communication both ways.
However, it is important to note that when powering the board through the USB-C port, please ensure the nominal voltage range is 6-20V and Vmax is 40V.

=== Debug Connector ===
The following 6-pin connector marked as X4 is used for serial communication and debugging purposes with ESP32 CAN X2. The 6-pin configurations on the ESP32 CAN X2 is arranged as follows:

[[File:Debug connectors 6 pins.png|Figure 4]]

== Board Layout ==

Mechanical board outline physical dimensions:

* Width : 42.10 mm
* Length : 72 mm
 
The board top view is shown in the Figure 4 given below.

[[File:Board Layout.png|700px]]

== Power Ratings & Environmental Requirements ==

'''Power Options'''

The ESP32-CAN-X2 development board is flexible in its power input, and it provides multiple power input options. Power can either be supplied via the VIN pin, or via USB-C connector. Any voltage input either via USB or VIN is stepped down to 3.3 V via a voltage regulator.

'''Power available to your circuit'''

The onboard regulator can provide power to your devices:
* 1.5A is available on the 5V header pins
* 100mA is available on the 3.3v header pins

'''Pin Voltage'''

All digital & analog pins on the ESP32-CAN-X2 development board are 3.3 V. Do not connect any higher voltage devices to any of the pins as it will risk damaging the board.

'''VIN Rating'''

The nominal input voltage rating for the development board is 6-20v, with a 40v max input. Please do not attempt to power the board with a voltage outside the recommended range.

'''Operating Current'''

The typical operating current of ESP32-CAN-X2 development board is 105mA and maximum operating current is 500mA ( peak, during transmission )

'''Power Consumption'''

The normal power consumption of the board is 330mW and peak power consumption is 1.65W

'''Operating Temperature'''

Temperate rating is -40°C to +85°C

=CAN bus information=

CAN, also known as Control area networking, is a serial communication protocol that is widely used in Automotive applications. CAN bus communication protocol utilizes differential signaling methods in which data is transferred as a voltage difference between High and low voltage. Can Bus communication provides various advantages over other communication methods which makes it the most important communication protocol in automotive. A few features are follows

'''Multimaster system'''

In CAN Bus communication, multiple controllers can act as a master, and multiple devices can act as a node. Each node can share data with other nodes via the CAN bus. In modern cars, there are more than 70 ECUs, and using CAN communication each ECU acts as a node and can transfer the data to the CAN bus, this data is then available to all the ECUs, and ECU can then check the data and decide whether to receive or ignore it.

For details, visit: https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial

'''Lossless communication'''

CAN communication uses a bitwise arbitration method that avoids the contentions of data on the bus. When two nodes simultaneously try to send the data, then the node with the high priority ( lower identifier ) gets priority and continues transmitting. The identifier message can be 11-bit ( standard CAN ) or 29-bit ( extended CAN) in length.

For details, visit: https://dewesoft.com/blog/what-is-can-bus

'''Simple and cheap'''

The CAN communication between the ECUs is done through a single CAN system instead of direct complex analog signal lines which makes it extremely simple and reduces errors.

For details, visit: https://www.autopi.io/blog/can-bus-explained/

'''Errorless communication'''

CAN incorporates different built-in error detection mechanisms including cyclic redundancy checks (CRC), and frame check sequences (FCS) to detect errors during data transmission.

'''CAN network types'''
 
Prominent CAN network types are as follows.

* High-speed CAN bus ( Supports bit rates between 40 kbit/s and 1 Mbit/s )
* Low-Speed CAN bus ( Supports bit rates between 40 kbit/s and 125 kbit/s )
* CAN FD ( Supports bit rates between 1 Mbps to 8 Mbps )
 
For details, visit:https://dewesoft.com/blog/what-is-can-bus

'''Data transmission'''

In CAN, data is transferred between two nodes in messages known as CAN frames. There are four types of CAN frames.
* Data frame ( Used to transfer data between two node )
* Remote frame ( request data from other node )
* Error frame ( report errors )
* Overload frame ( report overload )
 
For details, visit:https://www.autopi.io/blog/can-bus-explained/

== CAN Termination ==

CAN termination is a process of terminating the CAN bus to prevent the signal reflection at the end of the bus and to ensure the correct DC level of the bus. The CAN BUS is bidirectional, and both ends of the bus must be properly terminated to prevent errors in communication. CAN termination is achieved by placing the termination resistance, which is normally 120 ohm, that matches the nominal resistance of the cable. ISO 11898 requires normally required CAN BUS cable of impedance 120 ohm; therefore, the CAN 120 ohm resistance is used for CAN termination. However, while doing the CAN termination, it must be kept in mind that the nodes from the far two ends of the cable only require termination resistors.

Figure 5 given below explain the CAN termination.

[[File:CAN BUS TERMINATION.png]]

Note : The low-speed CAN, single wire CAN, may not require the CAN bus termination.

'''How to enable & disable CAN termination in ESP-32-X2 ?'''

The ESP-32-X2 development board has given two separate CAN termination pads at the back side of the development board. The CAN termination jumpers are shown in figure 6 given below.

[[File:CAN termination.png]]

* Enable termination : In ESP-32-X2 development board, CAN termination is enabled by default.
* Disable termination : Scratch the copper trace between the pads, TERM1 & TERM2.
* Re-enable termination : Re-solder the traces between the pads

Note : Proper termination is necessary for ensuring errorless communication and signal integrity. Please follow the above given instruction carefully.

=Board Pinout=

The ESP32-CAN-X2 board has 40 pins across its two headers, SV1 & SV2 headers, and two 4-pin headers at the top. This guide explains the pin functionalities of the board. The pin configuration of the development board is shown in Figure 7 given below.

[[File:Pin Configuration 1.png|Figure 7]]

'''Left Header (SV1) Pinout (Top to Bottom)'''

The pin count start from the top of the left header, and the pin details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || CAN1H/2.7D || high-level signal for the first CAN channel.
|-
| 2 || CAN1L/2.7D || low-level signal for the first CAN channel
|-
| 3 || CAN2H/2.7C || high-level signal for the second CAN channel
|-
| 4 || CAN2L/2.7C || low-level signal for the second CAN channel
|-
| 5 || RX Pin || USART RX
|-
| 6 || TX Pin || USART TX
|-
| 7-20|| GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
|}

'''Right Header (SV2) Pinout (Bottom to Top )'''

The pin count start from bottom to top and details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1-11 || GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
| 12-13 || 3.3V || 3.3v Voltage Output (can be used to power your custom circuits)
|-
| 14-15 || 5V || 5v Voltage Output (can be used to power your custom circuits)
|-
| 16-18 || GND || Ground
|-
| 19-20 || 12 Vin || 12v voltage Input
|}

==12v note==
Only connect 12v to the 12v voltage input (19-20). To avoid electrical damage, do not connect 12v to any other pin on the board.

==Top Headers Pinout==

The X1 and X2 header supports CAN communication. Pin count starts at the right viewing the board from the top. The pinout configuration of the X1 and X2 header is shown in the figure 8 below:

[[File:Two 4-Pin CAN Connectors.png|Figure 8]]
* '''Note:''' Color codes on the provided pigtail may not match documentation.

The pin description of the X1 header is given in the table below:
{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the first CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the first CAN channel
|-
| 4 || GND || Ground
|}

The pin description of the X2 header is given in the table below:

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the second CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the second CAN channel
|-
| 4 || GND || Ground
|}

=Flashing Firmware=

Firmware flashing in this development board is straightforward. The following components are required for firmware flashings.

'''Hardware Components'''

* USB-C cable
* Computer running Windows, Linux, or macOS
 

'''Software Components'''

* Updated Arduino IDE to compile code for ESP-32-X2.
* Update Mu Editor from codewith.mu
 
Note : Link to download Arduino IDE : https://www.arduino.cc/en/software || Link to download Mu Editor : codewith.mu

== Step by step instruction for Arduino IDE==

===Sample Arduino Project===
https://github.com/autosportlabs/ESP32-CAN-X2

Step-by-step instructions for flashing ESP-32-X2 are as follows.

'''Install ESP-32-X2 Board Support:'''

Adding ESP-32-X2 in Arduino Ide is a single-time process and its steps are as follows.

* Open Arduino Ide
* Go to File > Preferences
 

[[File:Flashing1.png| Figure 7|800px]]

* Add the below given Json URL in the Additional board manager URL

Json URL : https://espressif.github.io/arduino-esp32/package_esp32_index.json
 
[[File:ESPBSP1.png|Figure 8|800px]]

* Go to Tools > Board > Boards Manager
 

[[File:Flashing3.png|Figure 9|800px]]

* In the Board Manager search bar, type ESP-32, search for esp32 by Espressif and click on install to install the board
 
[[File:ESPBSP2.png|Figure 10|800px]]

* After installing, click on Tool > Boards and select AutosportLabs ESP32-CAN-X2
 
'''Flashing'''

* Connect the ESP-32-X2 board to your computer using a USB-C cable with your Arduino IDE open

* Select AutosportLabs ESP32-CAN-X2 in Tools > Board menu

* Go to Tools > Port and select the COM port to which ESP-32-X2 is connected.

[[File:ArduinoFlashing3.png|Figure 11|800px]]
 
Note : If you don’t see the COM Port in your Arduino IDE, you need to install the CP210x USB to UART Bridge VCP Drivers: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
 

* Write your firmware code or add an existing sketch that you want to upload to your custom board.

* Go to Sketch > Click upload to compile and upload the code

* After successful uploading, you should see a “Done uploading.” message at the bottom console. This console will also show error messages if there is any error.

[[File:ArduinoFlashing4...png|Figure 12|800px]]

If any issues occur during upload, double-check the board selection, COM port, and your code for errors.
<be>

===Importing Libraries in Arduino IDE===

* To Install Libraries for ESP32-CAN-X2 like mcp_canbus or mcp2515
* Go to Sketch > Include Library > Manage LibrarieSs

[[File:Arduino IDE Library 1.png]]

* Type and find the desired library like mcp_canbus by Longan Labs
* Search and Install the library

[[File:Arduino IDE Library 2...png]]

== Step-by-step instruction for CircuitPython==
===Sample CircuitPython code===
https://github.com/autosportlabs/ESP32-CAN-X2

'''Downloading ESP-32-X2 Board Support:''' 

Installing ESP-32-X2 is simple, please follow the steps given below :

* Go to circuitpython.org/board/autosportlabs_esp32_can_x2
Click on the browse S3 

[[File:CircuitpythonFlashing1.png|800px]] 

* Select the desired language 
 

[[File:CircuitpythonFlashing2.png|800px]]
* Download the latest .bin file
 

[[File:CircuitpythonFlashing4.png|800px]]

'''Prepare the ESP32 CAN X2 for Installation:''' 

* Connect the ESP-32-X2 board to your computer using a USB-C cable
* Press and hold the boot button on the development board.
* While holding the boot button, press and release the reset button once.
* Release the boot button to put the board into bootloader mode.
[[File:REV D Flashing Image.png|800px]]

'''Connect to the Web Serial ESP Tool'''

* Go to : https://adafruit.github.io/Adafruit_WebSerial_ESPTool/
* Press the Connect button in the top right corner of the page.
* A pop-up will appear asking you to select the COM or Serial port.
* Look for an option with ESP32, JTAG Loader, SLAB, or FTDI in the name
 

[[File:CircuitpythonFlashing6.png|800px]]

'''Flash the Firmware'''

* Click on Choose the .bin file you downloaded.
* Ensure that the Offset box next to the file location is set to 0x0.
* After selecting the file, the button text will change to match your filename.
* Click the Program button to start flashing. A progress bar will appear, and after a minute or two, the firmware will be
written.

[[File:Circuytpython7.gif|800px]]

'''Exit Bootloader Mode'''
* Press the reset button to exit bootloader mode. Shortly, the CIRCUITPY drive will pop up.

'''Downloading and Installing Mu Editor'''
* Download and install the recommended Mu Editor from codewith.mu.
* When you first start Mu, you will be prompted to select your mode. Select CircuitPython.
 
[[File:Mudownload.png|800px]]

* In Mu editor, click the Load button in the button bar, navigate to the CIRCUITPY drive, and choose code.py.
 
[[File:MU2.png|800px]]

'''Note :''' The CIRCUITPY drive is where your code and necessary libraries will reside. With a fresh CircuitPython install, the CIRCUITPY drive will contain a code.py file with print("Hello World!") and an empty lib folder. If your CIRCUITPY drive does not have a code.py file, create one and save it to the drive. CircuitPython automatically executes the code in code.py when the board starts up or resets. Do not press reset immediately after saving your code it will corrupt the drive and you may lose your code.

* Enter your code into the editor and save the code.py file on the CIRCUITPY drive.
 

[[File:MU3.png|800px]]

'''Congratulations!''' You have just run your first CircuitPython program.

=== Importing Libraries in Circuitpython ===

Importing libraries in Circuitpython is straightforward. For installing Libraries in Circuitpython, please follow the steps given below :
* Go to https://circuitpython.org/libraries and download the bundle for version 9.xx.
'''Note:''' The version of the bundle should be the same that you are using.
 

[[File:Mu4.png|800px]]

* Extract the zip file.
* Find the lib file where you can find your desired library.
* Copy that library folder or .mpy file and paste it to the lib folder in CIRCUITPY drive
 

[[File:Mueditor Library.gif|800px]]

=ESP32-CAN-X2 Rev-C=
[https://wiki.autosportlabs.com/ESP32-CAN-X2/RevC#6_pin_JST-PH_Connector ESP32-CAN-X2 Rev-C]

ESP32-CAN-X2

2026-03-25T14:19:50Z

Brentp: /* Power Ratings & Environmental Requirements */

=Introduction=

ESP32-CAN-X2 is an automotive-grade ESP32-based development board specifically designed for CAN communication. This board has all the features of a modern ESP32 development board, integrated Wi-Fi and Bluetooth, along with the extended CAN controller. Autosport Labs has specifically designed it for CAN communication in harsh automotive and industrial environment, while offering fast processing and computation options.

This is a complete how-to-use guide and this user guide will describe each and every step to use the board and harness the maximum potential of the board.

[[File:ESP32_CAN_X2_revD_3quarter.jpg|700px]]

=Purchasing=
You can order the ESP32-CAN-X2 from our online store:
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Features=

Features of ESP32-CAN-X2 development board:

* Flexible power supply options up to 40V, suitable for automotive and industrial applications
* Based on ESP32-S3-WROOM-1-N8R8 microcontroller powerful dual-core Xtensa LX6 CPU running at up to 240 MHz.
* 384 KB ROM, 512 KB SRAM, 16 KB SRAM in RTC, 8 MB PSRAM
* Two LED’s: Power LED and user-defined LED1
* Integrated Wi-Fi (802.11b/g/n) and Bluetooth capabilities
* Reset and Boot push button
* USB-C type socket for flashing, and power supply
* Integrated antenna for long-range communication
* Additional CAN communication controller CAN using MCP2515
* Two 4-pin headers are strategically positioned at the top for CAN communication.
* Easy-to-interface programming. Required no external debugger for flashing
* Integrated CAN transceivers
* Configurable CAN termination resistors, which can be disabled via breakable jumpers
* Support of a wide choice of commonly used Integrated Development Environments (IDEs)
* [https://github.com/autosportlabs/ESP32-CAN-X2/ Comprehensive free software libraries] and examples for CAN communication for Arduino and Circuit Python
* Supports a range of stackable [[#Bolt-ons|add-on boards]] offering additional features such as GPS, RGB LEDs, switches, and more.

=Bolt-ons=
Bolt-ons are stackable add-on boards that offer easy extensibility

Make your own bolt on with a blank design template https://github.com/autosportlabs/ESP32-CAN-X2/tree/main/bolt-on-template
===GPS bolt-on===
Adds a high performance GPS receiver 
[[File:GPS Bolt-on image main.png|300px|link=Gps-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/gps-bolt-on/]]
===Button bolt-on===
Adds 4 tactile switches + RGB LEDs 
[[File:Button Bolt-on white background.jpg|300px|link=Button-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/button-bolt-on/]]
===RGB LED bolt-on===
Adds 10 RGB LEDs across two groups for alert indicators 
[[File:RGB LED Bolt-on.jpg|300px|link=RGB-bolt-on]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/rgb-led-bolt-on/]]

=Getting started=

This section will provide you with comprehensive information about the ESP32-CAN-X2 development board's key components, mechanical layout, power rating, & requirements. This detailed information helps you to use the board effectively and efficiently in your projects.

== Key Components of ESP32-CAN-X2 Development Board ==

Figure 1 given below indicates the important key components of the ESP32-CAN-X2 Development Board and their location on the board.

[[File:REV D Images updated.png|Figure 1]]

=== Microcontroller ===

The ESP32-CAN-X2 Development Board is designed around the ESP32-S3-WROOM-1-N8R8 microcontroller in a 40-pin package. The connections between the development board and the microcontroller is straightforward, where the majority of GPIO pins are directly connected with the external headers, SV1 & SV2, and some pins are reserved internal connections between the board and CAN controllers. The internal connections between the microcontroller and CAN controllers are shown in the CAN controller heading given below. The microcontroller pin layout is shown in Figure 2 given below.

[[File:Microcontroller pin layout.png|Figure 2]]

=== External Connection Header ===

External headers, SV1 & SV2, are the two other important components of this development board. SV1 is the left side dual row header and the SV2 is the right side dual row header. Both of these headers have 20 pins available for connection. These headers provide connections for GPIOs, power output, ground (GND), power input, and CAN communication pins. Both of these header pinouts have standard size, allowing users to connect them using jumper wires, a breadboard, or even solder wires permanently onto the development board. However, while doing the wire connection the customer must make sure that none of them get short circuit. The details regarding the pin's names, numbers, outputs, and functions are given in the Board Pinout section below.

=== CAN bus transceivers===

The following are the specifications of the CAN transceivers for CAN1 and CAN2:

'''Detection of Ground Fault'''
* Permanent Dominant Detection on TXD
* Permanent Dominant Detection on Bus
* Power-on Reset and Voltage Brown-Out

'''Protection on V DD Pin'''
* Protection Against Damage Due to Short-Circuit
Conditions (Positive or Negative Battery Voltage)
* Protection Against High-Voltage Transients in

'''Automotive Environments'''
* Automatic Thermal Shutdown Protection
* Suitable for 12V and 24V Systems
* Meets or exceeds stringent automotive design requirements including “Hardware Requirementsfor LIN, CAN and FlexRay Interfaces in Automotive Applications”, Version 1.3, May 2012
• High-Noise Immunity Due to Differential Bus Implementation
• High Electrostatic Discharge (ESD) Protection on CANH and CANL, meeting the IEC61000-4-2 up to ±14 kV

=== CAN Controllers ===

The MCP2515 external connected CAN communication controller, and ESP-32 built-in CAN communication controller are two other main components of this development board.

The MCP2515, operating as the second external CAN controller in this development board, is a specialized component designed for Controller Area Network (CAN) applications. Its features include:

* Implements CAN V2.0B at up to 1 Mb/s.
* High-Speed SPI Interface (10 MHz)
* Interrupt Output Pin with selectable enables
* Multiple receive and transmit buffers
* Low-Power CMOS Technology: - 5 mA active current (typical), 1 μA standby current
 
The internal CAN controller also works at CAN V2.0. The internal CAN supports two message formats:

* Base frame format (11-bit ID)
* Extended frame format (29-bit ID)
 
'''Internal pinout connection between the CAN controllers and ESP32'''

==== CAN 1 ====
This is a built-in CAN controller and its RX is connected to IO6 of the microcontroller and TX is connected to IO7 of the microcontroller. The connections are shown in Figure 3 given below

==== CAN 2 ====
This is the externally connected MCP2515 controller with the following connections:
{| class="wikitable" style="text-align:center; width:60%"
|+ '''MCP2515 ESP32-CAN-X2 GPIO connections'''
! Signal !! ESP32 GPIO
|-
| CS || 10
|-
| CLK || 12
|-
| MISO || 13
|-
| MOSI || 11
|-
| IRQ || 3
|}

Crystal: 16MHz
[[File:CAN Controller Connections ESP32.jpg|Figure 3]]

=== Two 4-Pin header Connector ===

The ESP32-CAN-X2 development board provides two additional 4-pin connector headers at the top of the board to support CAN communication. This header makes wiring the device more convenient and robust. The CAN communication connection pinout details are given in the pinout section below.

=== Built-in LED ===
The built-in blue LED is connected to GPIO2 of the ESP32. For a demo that exercises this LED, see the [https://github.com/autosportlabs/ESP32-CAN-X2/blob/main/arduino/ping_pong/ping_pong.ino#L23 ping-pong example].

=== USB-C Socket ===
The ESP32-CAN-X2 development board has one USB-C port. This port is used for multiple functions: it powers the board, allows programming, and facilitates serial communication both ways.
However, it is important to note that when powering the board through the USB-C port, please ensure the nominal voltage range is 6-20V and Vmax is 40V.

=== Debug Connector ===
The following 6-pin connector marked as X4 is used for serial communication and debugging purposes with ESP32 CAN X2. The 6-pin configurations on the ESP32 CAN X2 is arranged as follows:

[[File:Debug connectors 6 pins.png|Figure 4]]

== Board Layout ==

Mechanical board outline physical dimensions:

* Width : 42.10 mm
* Length : 72 mm
 
The board top view is shown in the Figure 4 given below.

[[File:Board Layout.png|700px]]

== Power Ratings & Environmental Requirements ==

'''Power Options'''

The ESP32-CAN-X2 development board is flexible in its power input, and it provides multiple power input options. Power can either be supplied via the VIN pin, or via USB-C connector. Any voltage input either via USB or VIN is stepped down to 3.3 V via a voltage regulator.

'''Power available to your circuit'''
The onboard regulator can provide power to your devices:
* 1.5A is available on the 5V header pins
* 100mA is available on the 3.3v header pins

'''Pin Voltage'''

All digital & analog pins on the ESP32-CAN-X2 development board are 3.3 V. Do not connect any higher voltage devices to any of the pins as it will risk damaging the board.

'''VIN Rating'''

The nominal input voltage rating for the development board is 6-20v, with a 40v max input. Please do not attempt to power the board with a voltage outside the recommended range.

'''Operating Current'''

The typical operating current of ESP32-CAN-X2 development board is 105mA and maximum operating current is 500mA ( peak, during transmission )

'''Power Consumption'''

The normal power consumption of the board is 330mW and peak power consumption is 1.65W

'''Operating Temperature'''

Temperate rating is -40°C to +85°C

=CAN bus information=

CAN, also known as Control area networking, is a serial communication protocol that is widely used in Automotive applications. CAN bus communication protocol utilizes differential signaling methods in which data is transferred as a voltage difference between High and low voltage. Can Bus communication provides various advantages over other communication methods which makes it the most important communication protocol in automotive. A few features are follows

'''Multimaster system'''

In CAN Bus communication, multiple controllers can act as a master, and multiple devices can act as a node. Each node can share data with other nodes via the CAN bus. In modern cars, there are more than 70 ECUs, and using CAN communication each ECU acts as a node and can transfer the data to the CAN bus, this data is then available to all the ECUs, and ECU can then check the data and decide whether to receive or ignore it.

For details, visit: https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial

'''Lossless communication'''

CAN communication uses a bitwise arbitration method that avoids the contentions of data on the bus. When two nodes simultaneously try to send the data, then the node with the high priority ( lower identifier ) gets priority and continues transmitting. The identifier message can be 11-bit ( standard CAN ) or 29-bit ( extended CAN) in length.

For details, visit: https://dewesoft.com/blog/what-is-can-bus

'''Simple and cheap'''

The CAN communication between the ECUs is done through a single CAN system instead of direct complex analog signal lines which makes it extremely simple and reduces errors.

For details, visit: https://www.autopi.io/blog/can-bus-explained/

'''Errorless communication'''

CAN incorporates different built-in error detection mechanisms including cyclic redundancy checks (CRC), and frame check sequences (FCS) to detect errors during data transmission.

'''CAN network types'''
 
Prominent CAN network types are as follows.

* High-speed CAN bus ( Supports bit rates between 40 kbit/s and 1 Mbit/s )
* Low-Speed CAN bus ( Supports bit rates between 40 kbit/s and 125 kbit/s )
* CAN FD ( Supports bit rates between 1 Mbps to 8 Mbps )
 
For details, visit:https://dewesoft.com/blog/what-is-can-bus

'''Data transmission'''

In CAN, data is transferred between two nodes in messages known as CAN frames. There are four types of CAN frames.
* Data frame ( Used to transfer data between two node )
* Remote frame ( request data from other node )
* Error frame ( report errors )
* Overload frame ( report overload )
 
For details, visit:https://www.autopi.io/blog/can-bus-explained/

== CAN Termination ==

CAN termination is a process of terminating the CAN bus to prevent the signal reflection at the end of the bus and to ensure the correct DC level of the bus. The CAN BUS is bidirectional, and both ends of the bus must be properly terminated to prevent errors in communication. CAN termination is achieved by placing the termination resistance, which is normally 120 ohm, that matches the nominal resistance of the cable. ISO 11898 requires normally required CAN BUS cable of impedance 120 ohm; therefore, the CAN 120 ohm resistance is used for CAN termination. However, while doing the CAN termination, it must be kept in mind that the nodes from the far two ends of the cable only require termination resistors.

Figure 5 given below explain the CAN termination.

[[File:CAN BUS TERMINATION.png]]

Note : The low-speed CAN, single wire CAN, may not require the CAN bus termination.

'''How to enable & disable CAN termination in ESP-32-X2 ?'''

The ESP-32-X2 development board has given two separate CAN termination pads at the back side of the development board. The CAN termination jumpers are shown in figure 6 given below.

[[File:CAN termination.png]]

* Enable termination : In ESP-32-X2 development board, CAN termination is enabled by default.
* Disable termination : Scratch the copper trace between the pads, TERM1 & TERM2.
* Re-enable termination : Re-solder the traces between the pads

Note : Proper termination is necessary for ensuring errorless communication and signal integrity. Please follow the above given instruction carefully.

=Board Pinout=

The ESP32-CAN-X2 board has 40 pins across its two headers, SV1 & SV2 headers, and two 4-pin headers at the top. This guide explains the pin functionalities of the board. The pin configuration of the development board is shown in Figure 7 given below.

[[File:Pin Configuration 1.png|Figure 7]]

'''Left Header (SV1) Pinout (Top to Bottom)'''

The pin count start from the top of the left header, and the pin details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || CAN1H/2.7D || high-level signal for the first CAN channel.
|-
| 2 || CAN1L/2.7D || low-level signal for the first CAN channel
|-
| 3 || CAN2H/2.7C || high-level signal for the second CAN channel
|-
| 4 || CAN2L/2.7C || low-level signal for the second CAN channel
|-
| 5 || RX Pin || USART RX
|-
| 6 || TX Pin || USART TX
|-
| 7-20|| GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
|}

'''Right Header (SV2) Pinout (Bottom to Top )'''

The pin count start from bottom to top and details are as following :

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1-11 || GPIO Pins || GPIO's (3.3v tolerant; to avoid damage do not apply any higher voltages to these pins)
|-
| 12-13 || 3.3V || 3.3v Voltage Output (can be used to power your custom circuits)
|-
| 14-15 || 5V || 5v Voltage Output (can be used to power your custom circuits)
|-
| 16-18 || GND || Ground
|-
| 19-20 || 12 Vin || 12v voltage Input
|}

==12v note==
Only connect 12v to the 12v voltage input (19-20). To avoid electrical damage, do not connect 12v to any other pin on the board.

==Top Headers Pinout==

The X1 and X2 header supports CAN communication. Pin count starts at the right viewing the board from the top. The pinout configuration of the X1 and X2 header is shown in the figure 8 below:

[[File:Two 4-Pin CAN Connectors.png|Figure 8]]
* '''Note:''' Color codes on the provided pigtail may not match documentation.

The pin description of the X1 header is given in the table below:
{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the first CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the first CAN channel
|-
| 4 || GND || Ground
|}

The pin description of the X2 header is given in the table below:

{| class="wikitable"
|+
|-
! Pin !! Function !! Description
|-
| 1 || +12V_AUX || 6-12V Power Supply
|-
| 2 || CAN1H/2.7A || high-level signal for the second CAN channel
|-
| 3 || CAN1L/2.7A || low-level signal for the second CAN channel
|-
| 4 || GND || Ground
|}

=Flashing Firmware=

Firmware flashing in this development board is straightforward. The following components are required for firmware flashings.

'''Hardware Components'''

* USB-C cable
* Computer running Windows, Linux, or macOS
 

'''Software Components'''

* Updated Arduino IDE to compile code for ESP-32-X2.
* Update Mu Editor from codewith.mu
 
Note : Link to download Arduino IDE : https://www.arduino.cc/en/software || Link to download Mu Editor : codewith.mu

== Step by step instruction for Arduino IDE==

===Sample Arduino Project===
https://github.com/autosportlabs/ESP32-CAN-X2

Step-by-step instructions for flashing ESP-32-X2 are as follows.

'''Install ESP-32-X2 Board Support:'''

Adding ESP-32-X2 in Arduino Ide is a single-time process and its steps are as follows.

* Open Arduino Ide
* Go to File > Preferences
 

[[File:Flashing1.png| Figure 7|800px]]

* Add the below given Json URL in the Additional board manager URL

Json URL : https://espressif.github.io/arduino-esp32/package_esp32_index.json
 
[[File:ESPBSP1.png|Figure 8|800px]]

* Go to Tools > Board > Boards Manager
 

[[File:Flashing3.png|Figure 9|800px]]

* In the Board Manager search bar, type ESP-32, search for esp32 by Espressif and click on install to install the board
 
[[File:ESPBSP2.png|Figure 10|800px]]

* After installing, click on Tool > Boards and select AutosportLabs ESP32-CAN-X2
 
'''Flashing'''

* Connect the ESP-32-X2 board to your computer using a USB-C cable with your Arduino IDE open

* Select AutosportLabs ESP32-CAN-X2 in Tools > Board menu

* Go to Tools > Port and select the COM port to which ESP-32-X2 is connected.

[[File:ArduinoFlashing3.png|Figure 11|800px]]
 
Note : If you don’t see the COM Port in your Arduino IDE, you need to install the CP210x USB to UART Bridge VCP Drivers: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
 

* Write your firmware code or add an existing sketch that you want to upload to your custom board.

* Go to Sketch > Click upload to compile and upload the code

* After successful uploading, you should see a “Done uploading.” message at the bottom console. This console will also show error messages if there is any error.

[[File:ArduinoFlashing4...png|Figure 12|800px]]

If any issues occur during upload, double-check the board selection, COM port, and your code for errors.
<be>

===Importing Libraries in Arduino IDE===

* To Install Libraries for ESP32-CAN-X2 like mcp_canbus or mcp2515
* Go to Sketch > Include Library > Manage LibrarieSs

[[File:Arduino IDE Library 1.png]]

* Type and find the desired library like mcp_canbus by Longan Labs
* Search and Install the library

[[File:Arduino IDE Library 2...png]]

== Step-by-step instruction for CircuitPython==
===Sample CircuitPython code===
https://github.com/autosportlabs/ESP32-CAN-X2

'''Downloading ESP-32-X2 Board Support:''' 

Installing ESP-32-X2 is simple, please follow the steps given below :

* Go to circuitpython.org/board/autosportlabs_esp32_can_x2
Click on the browse S3 

[[File:CircuitpythonFlashing1.png|800px]] 

* Select the desired language 
 

[[File:CircuitpythonFlashing2.png|800px]]
* Download the latest .bin file
 

[[File:CircuitpythonFlashing4.png|800px]]

'''Prepare the ESP32 CAN X2 for Installation:''' 

* Connect the ESP-32-X2 board to your computer using a USB-C cable
* Press and hold the boot button on the development board.
* While holding the boot button, press and release the reset button once.
* Release the boot button to put the board into bootloader mode.
[[File:REV D Flashing Image.png|800px]]

'''Connect to the Web Serial ESP Tool'''

* Go to : https://adafruit.github.io/Adafruit_WebSerial_ESPTool/
* Press the Connect button in the top right corner of the page.
* A pop-up will appear asking you to select the COM or Serial port.
* Look for an option with ESP32, JTAG Loader, SLAB, or FTDI in the name
 

[[File:CircuitpythonFlashing6.png|800px]]

'''Flash the Firmware'''

* Click on Choose the .bin file you downloaded.
* Ensure that the Offset box next to the file location is set to 0x0.
* After selecting the file, the button text will change to match your filename.
* Click the Program button to start flashing. A progress bar will appear, and after a minute or two, the firmware will be
written.

[[File:Circuytpython7.gif|800px]]

'''Exit Bootloader Mode'''
* Press the reset button to exit bootloader mode. Shortly, the CIRCUITPY drive will pop up.

'''Downloading and Installing Mu Editor'''
* Download and install the recommended Mu Editor from codewith.mu.
* When you first start Mu, you will be prompted to select your mode. Select CircuitPython.
 
[[File:Mudownload.png|800px]]

* In Mu editor, click the Load button in the button bar, navigate to the CIRCUITPY drive, and choose code.py.
 
[[File:MU2.png|800px]]

'''Note :''' The CIRCUITPY drive is where your code and necessary libraries will reside. With a fresh CircuitPython install, the CIRCUITPY drive will contain a code.py file with print("Hello World!") and an empty lib folder. If your CIRCUITPY drive does not have a code.py file, create one and save it to the drive. CircuitPython automatically executes the code in code.py when the board starts up or resets. Do not press reset immediately after saving your code it will corrupt the drive and you may lose your code.

* Enter your code into the editor and save the code.py file on the CIRCUITPY drive.
 

[[File:MU3.png|800px]]

'''Congratulations!''' You have just run your first CircuitPython program.

=== Importing Libraries in Circuitpython ===

Importing libraries in Circuitpython is straightforward. For installing Libraries in Circuitpython, please follow the steps given below :
* Go to https://circuitpython.org/libraries and download the bundle for version 9.xx.
'''Note:''' The version of the bundle should be the same that you are using.
 

[[File:Mu4.png|800px]]

* Extract the zip file.
* Find the lib file where you can find your desired library.
* Copy that library folder or .mpy file and paste it to the lib folder in CIRCUITPY drive
 

[[File:Mueditor Library.gif|800px]]

=ESP32-CAN-X2 Rev-C=
[https://wiki.autosportlabs.com/ESP32-CAN-X2/RevC#6_pin_JST-PH_Connector ESP32-CAN-X2 Rev-C]

How To Update Firmware

2026-03-22T18:09:28Z

Brentp:

=Firmware upgrade steps=
Applies to:
* RaceCapture/Pro MK4, MK3, and MK2
* RaceCapture/Apex
* PodiumConnect MK2 and MK1
* RaceCapture/Track MK4, MK3, MK2, and MK1
* PodiumConnect/Micro

* How to video: [https://www.youtube.com/watch?v=LAFb-EeiXy8 Video: How to update firmware for RaceCapture/Pro]

==Save your configuration==

WARNING: Updating firmware will reset the default config on a major and minor release. Bugfix releases do not reset configuration.
Version scheme: MAJOR.MINOR.BUGFIX

If in doubt, be sure to save your configuration using the RaceCapture app.

==Download the firmware==

Download the firmware matching your hardware version from the [http://podium.live/software downloads section]

* '''Note''' Ensure you download the correct firmware for your device (matching the product name), or the firmware process will fail to complete.

==Flash the firmware==
Connect your system to your computer using the USB cable and connect to it with the app.
* '''Note:''' Flashing is only possible via the USB interface, so you must use the desktop version of the RaceCapture app.

===Steps===

=Updating Firmware=
* Unzip the firmware your downloaded to a location on your computer.
* Connect your system to your Windows or OSX computer using the included USB cable.
* Run the RaceCapture app, and confirm that it is connected.
* Navigate to the '''Setup''' view
* Save your current configuration. '''The firmware upgrade may reset your RaceCapture device to a factory default'''.
** Press '''Read''' to read the current configuration and then press '''Save''' to save it to a file.
* Select the Firmware section in the left menu.
** '''Note:''' - If the RaceCapture app cannot read the configuration, you may need to first '''Open a previously saved configuration''' so you can access the firmware page.
* Press the '''Update Firmware''' Button
* Browse to the unzipped firmware from the first step. Select the file ending with ".ihex" or ".bin" - and press '''Open'''
* The firmware will begin updating - watch for the progress to go 0-100%.
* Restore your saved configuration by pressing the '''Open''' button, selecting your saved configuration, and then '''Write''' it to your system.
* Confirm your firmware is updated by viewing the firmware version in the upper right corner of the RaceCapture app, after connecting.

* If there is a problem detecting the system after firmware upgrade, unplug/replug your device and restart the app.

===Alternative method via config file===
* While holding down the button on RaceCapture/Pro, power it up by plugging in to USB.
* You should observe a rapidly flashing LED on the unit: this means it's in bootloader mode.
* Start the app. Note, it will not be able to connect - this is expected.
* Navigate to Setup.
* Load a previously saved configuration file.
* Navigate to the firmware update view, then follow the process to update firmware.

===Forcing a factory reset via firmware===
Flashing a different minor version of the firmware will trigger the system to perform a factory reset. This will help address the case when the system 'stuck' and cannot normally connect.

Steps:
Follow the steps [[#Alternative method via config file]], but when choosing the firmware file to load, pick a firmware version that is older by the minor version.

Example minor version:

Current firmware version: 1.2.3
Flash this firmware: 1.1.3

After the firmware has completed flashing, you can flash the latest firmware again, using the regular procedure.

===Issues===
* If the firmware fails part way through, you can retry the firmware upgrade.
** Start the app
** Connect your device via USB
** Load a previously saved config file (file ending in .rcp)
** Navigate to Setup / Firmware
** Attempt the firmware upgrade process again.

=RaceCapture/Pro MK1=

Unzip the Firmware download into a folder and follow the directions in HOW_TO_FLASH.txt

Note: if you have problems getting the firmware to flash (it cannot find RaceCapture/Pro while in bootloader mode), try the following:

* Hold down the front panel button on RCP right at the beginning of the process, before running flashRCP.bat
* When asked 'is this your first time flashing' say 'No' so it will re-install the bootloader drivers
* Then proceed with the firmware flash update.

Alternatively:

Try installing the bootloader drivers while the hardware is plugged in to USB in bootloader mode (hold down logging button on RaceCapture/Pro, plug in to USB, then release button) outside of running flashRCP.bat. Then, check Windows Device Manager for the Presence of Autosport Labs bootloader while plugged in. Once you you see it show up, you can proceed with the firmware update process.

==Mac Users==
For Mac users with RaceCapture/Pro MK1 you will need to use a Windows VM to connect to RCP. Free virtual machine images are available here: http://dev.modern.ie/tools/vms/ You will need to add a network adapter to the VM. After that follow the Windows instructions.

AnalogX2

2026-03-03T16:24:44Z

Brentp: /* Harness / Cabling */

=Introduction=
AnalogX is a compact 4 channel Analog to CAN I/O expander, specially designed for the harsh automotive electrical environment.

[[image:analogx2_top.jpg|600px]]

AnalogX provides 4 buffered and protected 0-5v sensor inputs and can broadcast the sensor values between 1 and 255Hz. It also provides a 0.5A 5v reference for powering sensors.

==Parts in the Kit==
In the kit you will receive:
* AnalogX2 module

* '''Note''' Cabling is available separately, depending on how you design your sensor layout.

==Harness / Cabling==
AnalogX is designed for plug and play connection into Autosport Labs CAN bus networks and sensors. Parts and cables shown are available individually. Refer to the part numbers below to create your own sensor configuration.

===CAN bus connection to RaceCapture===
[[image:analogX_CAN_connection.jpg]]

{| class="wikitable"
|-
! SKU !! Description
|-
| ASL_DUAL_CAN_HUB || Powered, 8 port dual CAN bus hub kit
|-
| ASL_M8_CAN_EXT_0.5M ASL_M8_CAN_EXT_1M ASL_M8_CAN_EXT_2M ASL_M8_CAN_EXT_3M ASL_M8_CAN_EXT_4M || CAN extension cable, M8 4P female to M8 4P male, 0.5 - 4 Meter lengths
|}

===Sensor Connections===
[[image:analogX_plug_and_play_sensors.jpg]]

{| class="wikitable"
|-
! SKU !! Description
|-
| ASL_4X_SENSOR_SPLITTER || 4X sensor expander
|-
| ASL_M8_SENSOR_EXTENSION_1M ASL_M8_SENSOR_EXTENSION_2M ASL_M8_SENSOR_EXTENSION_3M ASL_M8_SENSOR_EXTENSION_4M || Single channel sensor extension cable
|-
| ASL_LINEAR_TEMP_M8 || Linear temperature sensor
|-
| ASL_10_BAR_DELPHI3_M8 || 10 bar (150 PSI) pressure sensor
|-
| ASL_150_BAR_DELPHI3_M8 || 150 bar (2175 PSI) pressure sensor
|-
| ASL_M8_SENSOR_PIGTAIL_2M || Single sensor pigtail for custom sensor connection, 2 Meters
|}

===Bare pigtails===
For a custom or non-plug and play installation, these bare pigtail cables are available for connecting AnalogX:
{| class="wikitable"
|-
! SKU !! Description
|-
| ASL_DEVICE_CAN_PIGTAIL_1M || CAN + power pigtail for connecting device, M8 4P male to bare wires, 1 meter
|-
| ASL_M8_QUAD_SENSOR_PIGTAIL_2M || M8 8P male to bare wire quad sensor pigtail, 1M, 24AWG
|}
See the [[AnalogX2#Wiring|Wiring]] guide for pinout information.

==Compatible Sensors==
AnalogX is compatible with any 0-5v voltage input; the voltage is broadcast over CAN bus with the value range of 0 - 5000mV.

Use the capabilities provided by the receiving data system to translate the raw voltage to a meaningful real-world value, such as pressure, temperature, distance, and so on.

===RaceCapture / PodiumConnect systems===
Setting up AnalogX in RaceCapture is easy: Go to Setup / CAN Channels and select the preset for AnalogX.

This will bring in the basic mapping with the default 0-5v scaling. From here, you can edit each channel to customize the formula to match your sensor's voltage scaling.

* '''Note''' - RaceCapture's CAN mapping features currently only supports sensors with a linear (straight-line) response. Sensors with a curved response, such as the Extended Range Temperature sensor is based on a thermistor design, and will not work with the built-in direct CAN mapping. We recommend using a temperature sensor with a linear response, such as the Autosport Labs Linear Temperature Sensor, Texense Liquid Temperature Sensor or similar.

===Setting CAN baud rate===
The default baud rate for AnalogX is 1M. Ensure this matches the setting under Setup / CAN bus settings.

===Selecting the AnalogX preset===
Select the starter CAN preset for AnalogX. This will bring in the basic 0-5v mapping, which you can then calibrate further using the CAN mapping conversion formula.

[[file:analogx2_preset_app.jpg|640px]]

===Calibrating Sensors attached to AnalogX===
Navigate to Setup / CAN mapping, and edit the channel you wish to customize.

===Select the channel===
Touch the channel selection drop down and select the channel that matches your sensor.
* '''Note, it's recommended you use the preset name for your channels; if no channel exists that matches your sensor, you can customize the channel name, units, and min/max values directly

==Sensor Conversion Formulas==
AnalogX reports it's raw value from 0-5000mV. You can use the formula to scale and offset the raw value to a real-world value.

===Linear Fluid Temperature Sensor===
The Autosport Labs Linear Fluid Temperature (ASL_LINEAR_TEMP_M8) sensor has a 10mV/C scaling, with a 0.5V offset at 0C.

[[file:linear_temp_sensor_analogx_scaling.png|480px]]

===10 bar / 150 PSI pressure sensor===
The Autosport Labs 10 bar pressure sensor (ASL_10_BAR_DELPHI3_M8) has the following calibration / range:

'''(0 - 10 bar / 150 PSI range)'''
* 0.5v 0 bar / = 0 PSI
* 4.5v = 10 bar / 150 PSI

The sensor has a 4000mV range between min and max values, with a 500mV offset.

Therefore,

The offset is calculated based on the 500mV offset of the sensor (500mv * 0.375 = 18.75)

for 0-150 PSI use the formula: '''RAW * 0.0375 - 18.75'''

* '''Note:''': The 0.0375 value was derived from the formua: 150 PSI / 4000mV = 0.0375 PSI/mV

[[file:AnalogX_150PSI_oil_pressure_example_formula.png|480px]]

===150 Bar / 2175 PSI pressure sensor===
The Autosport Labs 150 bar pressure sensor (ASL_150_BAR_DELPHI3_M8) has the following calibration / range:

'''(0 - 150 bar / 2175 PSI range)'''
* 0.5v = 0 bar / 0 PSI
* 4.5v = 150 bar / 2175 PSI

for 0-2175 PSI, use the formula: '''RAW * 0.5437 - 271.85'''

===Texense Liquid Temperature Sensor===
This sensor has a range of -50 to 150C and has a 22.5mV/C calibration.

0.25v = -50C
4.75v = 150C
(200C sweep)

The sensor has a 4500mV range between -50C and 150C, with a 250mV offset.

Therefore, 200C / 4500mV = 0.04444 C/mV

The offset is calculated based on the 250mV offset of the sensor (250mV * 0.0444444 = 11.1111)

The offset is further adjusted by the starting range of the sensor (-50C)

Resulting formula: '''RAW * 0.04444 - 61.1111'''

[[image:Texense_Liquid_temperature_sensor_CAN_channel_mapping.png|480px]]

* '''Note''' you can convert the resulting value to Fahrenheit by selecting the '''C -> F''' option in the Formula Conversions Tab.

===Other sensors===
Please refer to these manufacturer's user guide on how to map data using the provided AnalogX CAN protocol.

==Wiring==
===Power and CAN===
* Connector: M8 4P Male, A coding
[[file:M8_4P_male_pinout.jpg|200px]]
{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low ||
|-
| 2 || Power || Red, 12-14v / 50mA
|-
| 3 || CAN high ||
|-
| 4 || Ground || Black
|}

Power is standard automotive 12-14v (nominal).

===Sensor connections===
* Connector: M8 8P Female, A coding
[[file:M8_8P_female_pinout.jpg|200px]]
{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || Analog/Digital 1 ||
|-
| 2 || Analog/Digital 2 ||
|-
| 3 || Analog/Digital 4 ||
|-
| 4 || Vref || 5v @ 1A max current, combined with pin 6
|-
| 5 || Ground ||
|-
| 6 || Vref || 5v @ 1A max current, combined with pin 4
|-
| 7 || Analog/Digital 3 ||
|-
| 8 || Ground ||
|}

* '''Note''': The AnalogX inputs are very high impedance, allowing connection to existing circuits / sensors without affecting the reading of that circuit. As such, no pull-up or pull-down resistors are provided and must be added externally if needed.

==DIP switch settings==
You can access the DIP switches by removing the end plate on the CAN + power side. These switches enable an number of options:

{| class="wikitable"
|-
! Switch !! Function || Description
|-
| 1 || Termination || Set to ON to enable CAN termination
|-
| 2 || Address offset 1 || [[AnalogX2#Adjusting_Base_ID|Used to select the base CAN address]]
|-
| 3 || Address offset 2 || [[AnalogX2#Adjusting_Base_ID|Used to select the base CAN address]]
|-
| 4 || CAN Baud Rate || OFF to enable 1M (default), ON to enable 500K
|}

[[image: analogx2_dip_switch.jpg|600px]]

===CAN termination===

AnalogX is not terminated by default. You can enable termination by switching the [[AnalogX2#DIP_switch_settings|termination DIP switch]] to ON.

==Installation==
You can mount AnalogX2 to any flat mounting service. For best performance and reliability, keep away from sources of heat.

==Troubleshooting==

===No CAN data===
* Ensure AnalogX is receiving 12v via it's connection.
** '''Note''': Ensure your data system is also receiving 12v if it is powering AnalogX
* Double check the CAN bus connections
* Verify the CAN baud rate is compatible with the AnalogX configuration (1M by default, 500K enabled with DIP switch)
* Verify your CAN bus termination is correct. (Not terminated by default, enabled with DIP switch)
* Simplify your CAN bus network: Try making AnalogX the only other CAN device on the network, just as a test.
* Check for short circuits / over-current on the 5v reference. If too much current is drawn from the 5v reference, AnalogX may shut down in self-protection mode.

===Data is being received, but it is incorrect===

====Basic mapping test====
Try simplifying the mapping to verify the correct data is transmitted.

* Go into the software for the receiving system, and set the CAN formula to '''multiply by 1''' and '''add 0''' and '''divide by 1''' , and '''unsigned integer'''. and update the software settings.
** This will cause the receiving system to display the raw millivolt (mV) value from AnalogX.
* Disconnect the sensors from AnalogX.
* For each AnalogX input perform the following test:
** Connect the input to AnalogX's ground. Your receiving system should show very close to 0, which is 0 volts.
** Connect the input to AnalogX's 5v reference. Your receiving system should show very close to 5000, which represents 5000mV.

* '''Note''': The AnalogX inputs are very sensitive and high impedance to prevent affecting the readings of existing circuits. Therefore, if the inputs are disconnected, it will 'float' and may show random readings.

If you can confirm these readings, then perform the additional steps:
* For each AnalogX input, re-connect your sensor.
** Measure the voltage right where it enters AnalogX.
** Compare that with the reading on the receiving system. The value should be the voltage X 1000, translated to mV. Example: 2.5v measured should show 2500 on the receiving system.

If you can verify received millivolt value equals the measured voltage at the AnalogX input, then you know the correct value is being transmitted to the system, and you can focus on mapping the raw millivolt value to the real world temperature, pressure, or etc. Consult the sensor manufacturer and the system to determine the proper mapping of the sensor you are using.

==Specifications==
{| class="wikitable" | width="600px"
|-
! Feature
! Description
|-
| Analog sensor input voltage range
| 0 - 5v
|-
| DAC resolution
| 12 bit SAR
|-
| Sample output format
| 0 - 5000mV
|-
| Input impedance
| Greater than 10 Meg Ohm
|-
| Input voltage protection
| 100v
|-
| CAN baud rate
| 1M and 500K, jumper configurable
|-
| Address Space
| 4 separate address spaces allows up to 4 AnalogX modules to operate on the same CAN network. (DIP switch configurable)
|-
| Power input and connections
| 9 - 15volts, protected to 40v (intermittent)
|-
| Harness
| M8 4P Male for power + ground, M8 8P for sensor connection
|-
| Weight
| 100gm (approximately)
|-
| Dimensions
| 60 x 60 (approximately)
|-
| Environmental
| IP65, 0-85C
|}

=AnalogX CAN bus API=
==Overview==
The CAN bus API provides the configuration and control interface for AnalogX

==CAN base ID==

CAN base ID is '''0xE4600 (935424)'''

====Adjusting Base ID====
The base address is determined by the state of the '''ADR1''' and '''ADR2''' [[AnalogX2#DIP_switch_settings|DIP switches]], accessible behind the power + CAN end plate. By default, the DIP switches are off.

* Switching on ADR1 will add 256 to the base ID
* Switching on ADR2 will add 512 to the base ID.

The combination of jumper settings will allow up to 4 AnalogX units to coexist on the same CAN bus.

{| class="wikitable" | width="600px"
|-
! ADR2 switch
! ADR1 switch
! Address
|-
| Off
| Off
| 0xE4600 (935424)
|-
| Off
| On
| 0xE4700 (935680)
|-
| On
| Off
| 0xE4800 (935936)
|-
| On
| On
| 0xE4900 (936192)
|}

===CAN Baud rate===

1M and 500K rates are supported

1M is enabled by default; switch on the '''Baud''' [[AnalogX2#DIP_switch_settings|DIP switch]] to enable 500K data rate.

==CAN Messages==

===Announcement===

The announcement message is broadcast by the AnalogX upon power up.

====Address====
'''CAN ID:''' Base + 0x0 (0)

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Value
|-
| 0
| Channel Count
| Total number of channels on device
|-
| 1
| Current sample rate, in Hz
|
|-
| 2
| Reserved
|
|-
| 3
| Reserved
|
|-
| 4
| Reserved
|
|-
| 5
| Major Version
| Firmware Major Version Number
|-
| 6
| Minor Version
| Firmware Minor Version Number
|-
| 7
| Patch Version
| Firmware Patch version number
|}

===Configuration Group 1===

Configures options for AnalogX.

Send this message to AnalogX to configure runtime settings. Settings are saved in flash memory and will be preserved across power cycles.

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - AnalogX will reply with the current configuration.

====Address====
'''CAN ID:''' Base + 0x3 (3)

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Value
|-
| 0
| Sample Rate
| Rate to report sensor values ( 1 - 255Hz). Default sample rate is 50Hz.
|-
| 1
| Reserved
|
|-
| 2
| Reserved
|
|-
| 3
| Reserved
|
|-
| 4
| Reserved
|
|-
| 5
| Reserved
|
|-
| 6
| Reserved
|
|-
| 7
| Reserved
|
|}

===Statistics===

Broadcast by AnalogX every 1 second.

====Address====
'''CAN ID:''' Base + 0x2 (2)

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Value
|-
| 0
| Current Sample Rate
| 1 - 255Hz
|-
| 1
| Reserved
|
|-
| 2
| Reserved
|
|-
| 3
| Reserved
|
|-
| 4
| Reserved
|
|-
| 5
| Major Version
| Firmware Major Version Number
|-
| 6
| Minor Version
| Firmware Minor Version Number
|-
| 7
| Patch Version
| Firmware Patch version number
|}

===Sample Broadcast===

Sample Broadcast for Analog inputs. The samples are broadcast based on the configured sample rate (default is 50Hz)

===Scaling and Data format===
* '''Scaling:''' 0-5000mV
* '''Data format:''' Little Endian

===Address===
* '''CAN ID:''' Base + 0x14 (20)

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Value
|-
| 0
| Channel 1, low byte
|
|-
| 1
| Channel 1, high byte
|
|-
| 2
| Channel 2, low byte
|
|-
| 3
| Channel 2, high byte
|
|-
| 4
| Channel 3, low byte
|
|-
| 5
| Channel 3, high byte
|
|-
| 6
| Channel 4, low byte
|
|-
| 7
| Channel 4, high byte
|
|}

RaceCaptureTrack MK4

2026-02-15T19:32:02Z

Brentp: /* Backing Up Configurations */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your RaceCapture to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
Your system logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.

=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from your system.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

RaceCaptureTrack MK4

2026-02-15T19:31:48Z

Brentp: /* Accessing Flash Memory for Log File Transfer */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your RaceCapture to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
Your system logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.

=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

RaceCaptureTrack MK4

2026-02-15T19:31:32Z

Brentp: /* Wi-Fi Reliability Improvements in Firmware v2.23.3 */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your RaceCapture to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
PodiumConnect/Micro logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.
=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

RaceCaptureTrack MK4

2026-02-15T19:31:12Z

Brentp: /* Installing the RaceCapture App */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your RaceCapture to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

==== Wi-Fi Reliability Improvements in Firmware v2.23.3 ====
Firmware version 2.23.3 introduces multiple improvements to Wi-Fi reliability and connection stability for RaceCapture/Track MK4 and PodiumConnect/Micro. These updates are focused on improving real-world Wi-Fi behavior during configuration and telemetry use.

'''Summary of Improvements'''

* Improved Wi-Fi connection stability during normal operation
* More reliable reconnection behavior after temporary signal loss
* Improved handling of access point and network transitions
* Reduced likelihood of stalled or unresponsive Wi-Fi connections
* Improved behavior during STA hotspot scanning
* General robustness improvements when operating in environments with variable or congested wireless conditions

'''Note:''' These improvements apply automatically when running firmware version 2.23.3 or newer. No additional configuration is required.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
PodiumConnect/Micro logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.
=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

RaceCaptureTrack MK4

2026-02-13T21:50:44Z

Brentp: /* Mounting and dimensions */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your Podium Connect Micro to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

==== Wi-Fi Reliability Improvements in Firmware v2.23.3 ====
Firmware version 2.23.3 introduces multiple improvements to Wi-Fi reliability and connection stability for RaceCapture/Track MK4 and PodiumConnect/Micro. These updates are focused on improving real-world Wi-Fi behavior during configuration and telemetry use.

'''Summary of Improvements'''

* Improved Wi-Fi connection stability during normal operation
* More reliable reconnection behavior after temporary signal loss
* Improved handling of access point and network transitions
* Reduced likelihood of stalled or unresponsive Wi-Fi connections
* Improved behavior during STA hotspot scanning
* General robustness improvements when operating in environments with variable or congested wireless conditions

'''Note:''' These improvements apply automatically when running firmware version 2.23.3 or newer. No additional configuration is required.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
PodiumConnect/Micro logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.
=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
==STEP file for mounting pattern==
Download : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

==Dimensions==
Dimensions of main body (not including connectors): 94 x 61 x 16mm (3.7 x 2.4 x 0.63in)

RaceCaptureTrack MK4

2026-02-13T21:47:59Z

Brentp: /* Restoring Settings */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your Podium Connect Micro to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

==== Wi-Fi Reliability Improvements in Firmware v2.23.3 ====
Firmware version 2.23.3 introduces multiple improvements to Wi-Fi reliability and connection stability for RaceCapture/Track MK4 and PodiumConnect/Micro. These updates are focused on improving real-world Wi-Fi behavior during configuration and telemetry use.

'''Summary of Improvements'''

* Improved Wi-Fi connection stability during normal operation
* More reliable reconnection behavior after temporary signal loss
* Improved handling of access point and network transitions
* Reduced likelihood of stalled or unresponsive Wi-Fi connections
* Improved behavior during STA hotspot scanning
* General robustness improvements when operating in environments with variable or congested wireless conditions

'''Note:''' These improvements apply automatically when running firmware version 2.23.3 or newer. No additional configuration is required.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
PodiumConnect/Micro logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.
=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

=Mounting and dimensions=
STEP file for mounting pattern : [[File:RCT-Mk4_enclosure_solid_for_mounting_pattern.zip]]

File:RCT-Mk4 enclosure solid for mounting pattern.zip

2026-02-13T21:47:37Z

Brentp:

TireX

2026-02-13T15:58:24Z

Brentp: /* Connect Each TireX Sensor to the Wiring Harness */

=Introduction=
TireX is a powerful and versatile multi-zone tire temperature sensor designed for motorsports applications.
 
[[file:tirex_3quarter.jpg|600px]]

==Features==
===High Performance===
TireX can be configured to report up to 16 temperature zones, supporting sample rates up to 64Hz via CAN bus with the powerful embedded 32 bit processor.
===Rugged and Compact===
TireX features a rugged, low profile design with a wide field of view for space constrained environments.
===Flexible Setup===
* Temperature zones and sensor calibration is customizable by the end user
* Sensor position can be assigned to provide consistent data reporting between left and right sides of vehicle.
* CAN bus can be set for 1MB or 500K (default is 1MB)

=Quick Setup Guide=
The following setup assumes you have the following:
* RaceCapture system
* Plug and play wiring harness
* Powered CAN hub kit
* RaceCapture to hub integration cable

==Hardware Setup==
===TireX 4-corner plug and play harness===
We recommend using the TireX 4-corner plug and play harness for the easiest installation. 
https://www.autosportlabs.com/product/tirex-4-corner-plug-and-play-harness/

[[image:TireX_plug_and_play_harness_assembled_with_sensors_cropped.jpg|1024px]]
 
[[image:TireX_plug_and_play_harness_closeup_2_sensors_connected_top_view.jpg|400px]]
[[image:TireX_plug_and_play_harness_closeup_2_sensors_connected_end_view.jpg|400px]]

===By System===
===For newer plug and play RaceCapture and PodiumConnect systems===
You have two plug and play options for connecting the TireX harness:
====Use the Dual CAN splitter====
For a minimal installation, use the Dual CAN splitter 
https://www.autosportlabs.com/product/can1-can2-dual-can-splitter/ 
This splitter connects to the dual CAN port of your system, and TireX connects to the CAN2 ("B" connection) branch on the splitter.

[[image:ASL_DUAL_CAN_SPLITTER.jpg]]

===For older generation RaceCapture systems with RJ45 connector===
====Plug and Play option====
Get the 8 port hub and dual CAN link cable -> RJ45 
https://www.autosportlabs.com/product/powered-8-port-dual-can-bus-hub-kit/ 
https://www.autosportlabs.com/product/racecapture-rj45-to-dual-can-bus-link-cable/ 
The cable plugs into the RJ45 port of your RaceCapture/Pro, and then plugs into the hub. Then, the TireX harness plugs into the hub.
====Minimal installation (requires some custom wiring)====
Get the Device CAN pigtail 
https://www.autosportlabs.com/product/can-power-pigtail-for-device/ 
This will plug into the TireX harness, and then on the pigtail side you will connect it to CAN2 on your system (molex or RJ45 port) and then connect it to the same 12v power used for your system.

===For other data systems===
Get the Device CAN pigtail.
https://www.autosportlabs.com/product/can-power-pigtail-for-device/ 
This will plug into the TireX harness, and then on the pigtail side you will connect it to your system's CAN bus and 12v, on the same circuit powering your data system.
==TireX Connection==
=== Connect Each TireX Sensor to the Wiring Harness ===

To maintain proper CAN bus signal integrity, connect the sensors in a daisy-chain configuration. Install the inline CAN terminator at the final sensor in the chain.

⚠️ Do not create star or branch connections. The CAN network must remain a single continuous chain.

==== Routing ====

Begin at the male connector end of the plug-and-play harness (data system connection) and route the harness in sequence around the vehicle.

Recommended cable segments:

* Data system → Sensor 1 (first corner, front or rear): 3 m cable
* Sensor 1 → Sensor 2 (opposite side of same axle): 3 m cable
* Sensor 2 → Sensor 3 (same side, opposite axle): 4 m cable
* Sensor 3 → Sensor 4 (final corner): 3 m cable — install inline terminator here

==== Example Layout (Data System Mounted Near Center of Vehicle) ====
* Route a 3 m segment to the left-front corner and connect the sensor using the Y-splitter.
* Route a 3 m segment across to the right-front corner and connect the sensor.
* Route a 4 m segment to the right-rear corner and connect the sensor.
* Route a 3 m segment to the left-rear corner and connect the final sensor.
* Install the inline CAN terminator at this last sensor.

[[image:TireX_plug_and_play_harness_assembled_with_sensors_cropped.jpg|500px]]

==Software Setup==
https://i.imgur.com/rDiKXpC.gif

===Enable CAN bus and set CAN2 to 1MB===
Connect the RaceCapture app to your RaceCapture system.

* Go to Setup/CAN bus and ensure the CAN bus is turned '''ON'''
* Ensure CAN2 is set to 1M Baud

===Enable the TireX CAN mapping===
* Go to '''Setup/CAN mapping'''

* Ensure CAN Channels are set to '''ON'''

* Press the Presets button, then select the TireX 4 zone preset.
** '''Note''' - you may need to press the cloud update button to fetch the newest presets.

===Write the settings back to your RaceCapture System===
* Press the '''Write''' button to write your new settings to the system.

===Ensure RaceCapture / TireX is powered by 12v===
* Ensure the TireX sensor(s) are receiving 12v power. If powered via RaceCapture via the plug and play harness, ensure RaceCapture is powered with 12v.

* '''Note''': USB power is insufficient for powering the CAN bus network.

===Verify the TireX data on the dashboard===
====Using the overview gauge====
* Switch to the RaceCapture dashboard mode.
* Create a new Dashboard screen by pressing the gear icon in the upper right of the screen.
* Select the TireX test dashboard preset
** '''Note''' - you may need to press the cloud update button to fetch the newest presets.

====Using the raw channels view====
* Navigate to the Raw Channels view of the dashboard by pressing the left or right arrows on the dashboard screen.

* You can observe all of the available telemetry channels, including the individual channels for the TireX sensors.

=Specifications=
''Specifications are preliminary and subject to change''
{| class="wikitable" | width="600px"
|-
! Feature
! Description
|-
| Sensor type
| Thermal array
|-
| Sensor Resolution
| 16 x 12 (196 pixels)
|-
| Object temperature range
| 0 - 127.5C (tire temperature mode (factory default)) / 0 - 255C (full frame mode)
|-
| Field of view
| 110 x 75 degrees
|-
| Accuracy
| 1C
|-
| Temperature zones (tire)
| 1 / 2 / 4 (factory default) / 8 / 16
|-
| Sample rate
| 0.5 - 64Hz (Tire temperature mode, 16Hz factory default) 0.5 - 10Hz (Full frame mode)
|-
| Processing Engine
| 32 bit
|-
| Configurable positions
| 4 (Left-Front (factory default), Right-Front, Left-Rear, Right-Rear); Reversible orientation
|-
| Emissivity
| Configurable (0.95 default)
|-
| Ambient temperature compensation
| Automatic (adjustable offset)
|-
! Electrical
!
|-
| Interface
| CAN 2.0
|-
| Supply voltage
| 6 - 14v (automotive power)
|-
| Power
| 200mW
|-
| Harness
| M8 4P Male, 250mm length
|-
! CAN bus
!
|-
| CAN baud rate
| 500K and 1M, jumper configurable (1M default)
|-
| Address space
| 4 separate address spaces (configurable via jumper)
|-
| Termination
| No Termination (configurable via jumper)
|-
|-
! Physical / Environmental
!
|-
| Construction
| CNC aluminum
|-
| Dimensions
| 64 x 46 x 12.5mm
|-
| Weight
| 10 grams
|-
| Operating temperature
| -40 - 85C
|-
| IP rating
| IP65
|}

=Dimensions / Mounting=
[[image:TireX_dimensions.png]]

==Mounting Orientation==
We recommend mounting TireX above the tire, with the cable pointing towards the rear of the vehicle.
* '''Note:''' you can clock the mounting point so the sensor is mounted at the front or rear of the wheel well; just ensure the orientation remains the same.
[[Image:tirex_mounting_orientation.jpg]]
==Mounting Distance==
TireX has a wide aspect ratio of 110 degrees, so you can use some trigonometry to calculate the distance. Here are some examples:

* 205 width = 71mm
* 225 width = 79mm
* 235 width = 82mm
* 245 width = 85mm
* 255 width = 89mm
* 275 width = 96mm
* 315 width = 110mm

[https://www.triangle-calculator.com/?what=iso&a=C%3D110%2C+c%3D245&submit=Solve Here's a convenient online calculator]

Tip: you can mount TireX at a further distance if you use the middle channels. Example:

* if only using 8 channel, you can mount 2x the distance
* If only using 16 channels, you can mount 4x the distance

* '''Note:''' 4 channels is often the resolution of choice to reduce the bulk of data generated, and gives perfectly adequate results for determining tire performance.

=Electrical / CAN connection=
* Connection is provided by a standard industrial M8 4P male plug. [[Harness_specifications#Power_.2B_CAN_Single_interconnect|Pigtails and connectors are available from Autosport Labs, or 3rd parties]]
* TireX is designed to connect to regular automotive 12-14v per our [[Harness_specifications#Power_.2B_CAN_Single_interconnect|Standard Power interconnect]]

 
[[image:M8_4P_male.png]]
{| class="wikitable" | width="600px"
|-
! Pin
! Connecton
! Wire Color
|-
| Pin 1
| CAN Low
| Brown
|-
| Pin 2
| Voltage supply (6-14v)
| White
|-
| Pin 3
| CAN High
| Blue
|-
| Pin 4
| Ground
| Black
|}

== CAN termination ==
By default, TireX is not terminated. We recommend using the external termination adapter, connected inline on the last sensor of the chain.

[[image:autosport_labs_inline_can_terminator.jpg]]

This terminator is [https://www.autosportlabs.com/product/inline-can-terminator/ available separately] or [https://www.autosportlabs.com/product/tirex-4-corner-plug-and-play-harness/ included with the TireX plug and play harness].

=== Customizing Termination ===
CAN termination can be enabled on TireX by disassembling the sensor and closing the jumper on the TireX circuit board.

[[image:tirex_jumpers_can_termination.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

=Zone Configuration=
===Up to 16 configurable temperature zones===
TireX can be configured to report up to 16 temperature zones across the sensor's entire field of vision.

When configured for 2 or more zones, temperature for zones are reported in the order of inside through outside edge.

{| class="wikitable" | width="600px"
|-
! Zones
! Coverage
|-
| 1
| Averaged across the entire field of vision
|-
| 2
| Each zone averaged across 1/2 the field of vision
|-
| 4
| Each zone averaged across 1/4 the field of vision
|-
| 8
| Each zone averaged across 1/8 the field of vision
|}
===Reversible orientation based on sensor position===
TireX zones are reversed based on the configured sensor position (left vs right side) to allow identical physical sensor mounting orientation between sides.
[[file:TireX_zones.jpg|800px]]

=CAN bus protocol=

==CAN protocol files==
DBC File for standard 4 corner, 4 zone configuration: [[file:TireX_standard.dbc.zip]]

==Overview==
The CAN bus API provides the configuration, control and sensor broadcast interface for TireX

==Conventions==
===Formula===
* Conversion formulas are expressed as converting the CAN encoded value to real-world value.

* Example:
** Encoded value in CAN message: 95
** Formula: A / 100
** Real-world value: 0.95

===Data encoding===
====Endian====
16 and 32 bit values are encoded as little endian.

====Single and mulit-byte values====
{| class="wikitable" | width="600px"
|-
! Value
! Symbol Reference
|-
| 8 Bit values
| A
|-
| 16 bit values
| A (low byte) / B (high byte)
|-
| 32 Bit values
| A (low byte) / B / C / D (high byte)
|}

==CAN Baud rate==

1M and 500K rates are supported.

1M is enabled by default; cut the jumper labeled '''BAUD''' on the bottom of TireX to enable 500K rate.

[[image:tirex_jumpers_can_term.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

==CAN base ID==

A configured TireX sensor will have a CAN base address that is a combination of the '''Main Base ID''' + '''Position Offset''' based on the installed position of the sensor on the vehicle. This combination creates a final '''Sensor Base ID'''.

All broadcast and configuration CAN messages is offset from the final calculated '''Sensor Base ID'''.

===Default Main Base ID===
Default Main CAN base ID is '''0xA100 (41216)'''

====Adjusting Main Base ID====
The base address is determined by the state of the '''ADR1''' and '''ADR2''' jumpers. By default, the jumpers are closed (bridged); the jumper can be opened by cutting the trace between the pads. To re-close the jumper, add a small amount of solder to bridge the gap between the pads you want to close.
* '''Note:''' In the vast majority of the cases you can use the default Main Base ID of 0xA100.

[[image:tirex_jumpers_base_id.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

{| class="wikitable" | width="600px"
|-
! ADR2 Jumper
! ADR1 Jumper
! Address
|-
| Closed
| Closed
| 0xA100 (41216)
|-
| Closed
| Open
| 0xB100 (45312)
|-
| Open
| Closed
| 0xC100 (49408)
|-
| Open
| Open
| 0xD100 (53504)
|}
* Opening the jumper ADR1 will add (0x1000) 4096 to the base ID
* Opening the jumper ADR2 will add (0x2000) 8192 to the base ID
* Opening both jumpers ADR1 and ADR2 will add (0x3000) 12288 to the base ID.

==Sensor Position Offset==
The sensor position will offset the '''Main Base ID''' by the position of the sensor as defined in the table, to set the final '''Sensor Base ID'''.

{| class="wikitable" | width="600px"
|-
! Position ID
! Sensor Position
! Offset
|-
| 0
| Left-Front
| 0x0 (0)
|-
| 1
| Right-Front
| 0x100 (256)
|-
| 2
| Left-Rear
| 0x200 (512)
|-
| 3
| Right-Rear
| 0x300 (768)
|}

===Example: default base address (0xA100)===
{| class="wikitable" | width="600px"
|-
! Sensor Position
! Final Sensor Base ID
|-
| Left-Front
| 0xA100
|-
| Right-Front
| 0xA200
|-
| Left-Rear
| 0xA300
|-
| Right-Rear
| 0xA400
|}

* '''Note:''' Single sensor kits are configured as left-front tire position. This can be changed by sending the appropriate configuration message.

==CAN Messages==
The announcement message is broadcast by TireX once per second for 10 seconds upon power up.

===Announcement===
'''CAN ID:''' Sensor Base ID + 0

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sample Rate
| unsigned
| A * 1
| 0.5 - 64Hz (0 = 0.5Hz)
|-
| 1
| Temperature Zones
| unsigned
| A * 1
| Number of configured temperature zones (1 / 2 / 4 / 8 / 16) (factory default is 4)
|-
| 2
| Sensor Position
| Unsigned
| A * 1
| Configured sensor position (0=Left-Front / 1=Right-Front / 2=Left-Rear / 3=Right-Rear)
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Major Version
| unsigned
| A * 1
| Firmware Major Version Number
|-
| 6
| Minor Version
| unsigned
| A * 1
| Firmware Minor Version Number
|-
| 7
| Patch Version
| unsigned
| A * 1
| Firmware Patch version number
|}

===Statistics===

Broadcast by TireX every 10 seconds.

'''CAN ID:''' Sensor Base ID + 2

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sensor Ambient Temperature
| unsigned
| A * 1
| 0 - 255C
|-
| 1
| Reserved
|
|
|
|-
| 2
| Reserved
|
|
|
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Major Version
| unsigned
| A * 1
| Firmware Major Version Number
|-
| 6
| Minor Version
| unsigned
| A * 1
| Firmware Minor Version Number
|-
| 7
| Patch Version
| unsigned
| A * 1
| Firmware Patch version number
|}

===Configuration Preferences===

This message is broadcasted to TireX to configure the sensor's preferences. The settings are persisted in TireX's flash memory.

'''CAN ID:''' Sensor Base ID + 3

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - TireX will reply with the current configuration.

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sample Rate
| unsigned
| A * 1
| Rate to report sensor values ( 0.5 - 64Hz) Valid sample rates: 0 (0.5Hz) / 1 (1Hz) / 2 (2Hz) / 4 (4Hz) / 8 (8Hz) / 16 (16Hz) / 32 (32Hz) / 64 (64Hz). Specifying an invalid value will select the default value of 16
|-
| 1
| Temperature zones
| unsigned
| A * 1
| Number of temperature zones. Valid zones: 1 / 2 / 4 / 8 / 16. Specifying an invalid value will select the default value of 4.
|-
| 2
| Sensor Position
| unsigned
| A * 1
| Location of the sensor on the vehicle. This position adjusts the '''Sensor Base ID'''. Valid Positions 0 (Left-Front) / 1 (Right-Front) / 2 (Left-Rear) / 3 (Right-Rear). Specifying an invalid value will select the default value of 0 (Left-Front). '''Note:''' The sensor position affects the orientation of the sensor zones. Sensor Position 1 and 3 will report temperature zones left - right; Position 0 and 2 will report temperature zones right - left. 
'''Note''': When in full frame mode, this setting is ignored.
|-
| 3
| Frame mode
| unsigned
| A * 1
| 0 = Standard (Tire Temperature) mode; 1 = Full Frame mode
|-
| 4
| Reserved
|
|
|
|-
| 5
| Reserved
|
|
|
|-
| 6
| Reserved
|
|
|
|-
| 7
| Reserved
|
|
|
|}

===Calibration Preferences===

This message is broadcasted to TireX to configure the sensor's calibration. The settings are persisted in TireX's flash memory.

'''TireX is calibrated at the factory and normally these values will not need to be changed.'''

'''CAN ID:''' Sensor Base ID + 4

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - TireX will reply with the current configuration.

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Emissivity
| unsigned
| A / 100
| Emissivity of the target. Default is 0.95
|-
| 1
| Ambient temperature compensation
| unsigned
| A * 1
| Value in C. Default is 2
|-
| 2
| Sensor Resolution
| unsigned
| 16-19
| Sensor ADC resolution, in bits. Default is 18
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Reserved
|
|
|
|-
| 6
| Reserved
|
|
|
|-
| 7
| Reserved
|
|
|
|}

===Sensor Temperature Value Broadcast===
The following messages will contain the temperature values based on the number of temperature zones configured, broadcast at the currently configured sample rate.

* '''Note:''' The sensor position affects the orientation of the sensor zones:
** Position 1 and 3 will report temperature zones left - right;
** Position 0 and 2 will report temperature zones right - left.
====1 Zone====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====2 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====4 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====8 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 5 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 6 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 7 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 8 value
| unsigned
| A / 2
| 0 - 127.5C
|}
====16 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 5 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 6 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 7 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 8 value
| unsigned
| A / 2
| 0 - 127.5C
|}

'''CAN ID:''' Sensor Base ID + 0x21 (33)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 9 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 10 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 11 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 12 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 13 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 14 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 15 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 16 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====Full Frame Mode====
'''CAN ID:''' Sensor Base ID + 0x40 (64)

* '''Note:''' Pixels increment linearly by row x column

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Pixel 0 value
| unsigned
| A
| 0 - 255C
|-
| ...
| ...
| ...
| ...
| ...
|-
| 191
| Pixel 191 value
| unsigned
| A
| 0 - 255C
|}
= Hardware configuration =
Hardware defaults can be altered by disassembling TireX and adjusting jumpers on the bottom of the circuit board.

* To break a jumper: scrape the space between the jumper pads using a sharp tool, such as a razor blade or very small screwdriver.
* To re-close a jumper: use a fine tip soldering iron and add solder between the jumper pads.

[[image:tirex_jumper_settings.png|500px]]

When re-assembling the sensor, ensure the sensor and enclosure seals are correctly seated, and torque the enclosure screws evenly.

= Disassembly and replacing harness =
In the event the TireX pigtail is damaged, it can be replaced by the end user relatively easily.

Disassembly steps:
* Use a small screwdriver to remove the 4 outer screws.
* Remove the black gasket, and set aside
* Gently pry away the old harness from the notch of the enclosure
* Remove the circuit board by pressing the sensor from the outside of the enclosure.
* Remove the red seal around the sensor, and set aside.
* Using a small flat bladed screwdriver, '''carefully''' unplug the the harness from the circuit board. Gently pry away the harness connection from each side until it pops out of the connector.

Re-assembly steps:
* Re-insert the red sensor seal into the back of the main enclosure, so that it is installed and flush with the outside of the enclosure
* Plug the new harness into the circuit board. The connector mounts only one direction, and it should press in with just finger pressure. Ensure it is fully seated.
* Locate the cable notch on the enclosure. Press the harness into this notch, centered on the thick section near the end of the harness, close to the PCB connector. You may use finger / thumb pressure, or gently with a pair of cushioned pliers to prevent marring the enclosure. (you can wrap tape around the jaws of the pliers). Press it in until it is fully inserted into the notch.
* Press the PCB into the enclosure, focusing on pressing the sensor into the red seal.
* Inspect the opposite side of the enclosure, ensuring the sensor is properly seated into the seal, and no edges are caught.
* On the PCB, ensure the silicone pad is still mounted opposite of the sensor.
* Re-attach the black gasket onto the back lid of the enclosure, making sure the notch in the gasket matches the relief made in the lid to allow cable exit.
* Mount the back lid of onto the main body of the enclosure, ensuring the black gasket is properly inserted into the enclosure, with no pinching or caught edges. The stepped design of the gasket is designed to sure the back lid is perfectly centered. '''Ensure the cable relief of the bottom lid is installed in the direction where the cable exits'''
* Re-attach the 4 screws, torquing evenly until there is slight compression of the gasket.
* Test for proper operation before re-attaching it to the vehicle.
*

TireX

2026-02-13T15:56:17Z

Brentp: /* Connect Each TireX sensor to the Wiring harness */

=Introduction=
TireX is a powerful and versatile multi-zone tire temperature sensor designed for motorsports applications.
 
[[file:tirex_3quarter.jpg|600px]]

==Features==
===High Performance===
TireX can be configured to report up to 16 temperature zones, supporting sample rates up to 64Hz via CAN bus with the powerful embedded 32 bit processor.
===Rugged and Compact===
TireX features a rugged, low profile design with a wide field of view for space constrained environments.
===Flexible Setup===
* Temperature zones and sensor calibration is customizable by the end user
* Sensor position can be assigned to provide consistent data reporting between left and right sides of vehicle.
* CAN bus can be set for 1MB or 500K (default is 1MB)

=Quick Setup Guide=
The following setup assumes you have the following:
* RaceCapture system
* Plug and play wiring harness
* Powered CAN hub kit
* RaceCapture to hub integration cable

==Hardware Setup==
===TireX 4-corner plug and play harness===
We recommend using the TireX 4-corner plug and play harness for the easiest installation. 
https://www.autosportlabs.com/product/tirex-4-corner-plug-and-play-harness/

[[image:TireX_plug_and_play_harness_assembled_with_sensors_cropped.jpg|1024px]]
 
[[image:TireX_plug_and_play_harness_closeup_2_sensors_connected_top_view.jpg|400px]]
[[image:TireX_plug_and_play_harness_closeup_2_sensors_connected_end_view.jpg|400px]]

===By System===
===For newer plug and play RaceCapture and PodiumConnect systems===
You have two plug and play options for connecting the TireX harness:
====Use the Dual CAN splitter====
For a minimal installation, use the Dual CAN splitter 
https://www.autosportlabs.com/product/can1-can2-dual-can-splitter/ 
This splitter connects to the dual CAN port of your system, and TireX connects to the CAN2 ("B" connection) branch on the splitter.

[[image:ASL_DUAL_CAN_SPLITTER.jpg]]

===For older generation RaceCapture systems with RJ45 connector===
====Plug and Play option====
Get the 8 port hub and dual CAN link cable -> RJ45 
https://www.autosportlabs.com/product/powered-8-port-dual-can-bus-hub-kit/ 
https://www.autosportlabs.com/product/racecapture-rj45-to-dual-can-bus-link-cable/ 
The cable plugs into the RJ45 port of your RaceCapture/Pro, and then plugs into the hub. Then, the TireX harness plugs into the hub.
====Minimal installation (requires some custom wiring)====
Get the Device CAN pigtail 
https://www.autosportlabs.com/product/can-power-pigtail-for-device/ 
This will plug into the TireX harness, and then on the pigtail side you will connect it to CAN2 on your system (molex or RJ45 port) and then connect it to the same 12v power used for your system.

===For other data systems===
Get the Device CAN pigtail.
https://www.autosportlabs.com/product/can-power-pigtail-for-device/ 
This will plug into the TireX harness, and then on the pigtail side you will connect it to your system's CAN bus and 12v, on the same circuit powering your data system.
==TireX Connection==
=== Connect Each TireX Sensor to the Wiring Harness ===

To maintain proper CAN bus signal integrity, connect the sensors in a daisy-chain configuration. Install the inline CAN terminator at the final sensor in the chain.

⚠️ Do not create star or branch connections. The CAN network must remain a single continuous chain.

==== Routing ====

Begin at the male connector end of the plug-and-play harness (data system connection) and route the harness in sequence around the vehicle.

Recommended cable segments:

* Data system → Sensor 1 (first corner, front or rear): 3 m cable
* Sensor 1 → Sensor 2 (opposite side of same axle): 3 m cable
* Sensor 2 → Sensor 3 (same side, opposite axle): 4 m cable
* Sensor 3 → Sensor 4 (final corner): 3 m cable — install inline terminator here

==== Example Layout (Data System Mounted Near Center of Vehicle) ====
* Route a 3 m segment to the left-front corner and connect the sensor using the Y-splitter.
* Route a 3 m segment across to the right-front corner and connect the sensor.
* Route a 4 m segment to the right-rear corner and connect the sensor.
* Route a 3 m segment to the left-rear corner and connect the final sensor.
* Install the inline CAN terminator at this last sensor.

==Software Setup==
https://i.imgur.com/rDiKXpC.gif

===Enable CAN bus and set CAN2 to 1MB===
Connect the RaceCapture app to your RaceCapture system.

* Go to Setup/CAN bus and ensure the CAN bus is turned '''ON'''
* Ensure CAN2 is set to 1M Baud

===Enable the TireX CAN mapping===
* Go to '''Setup/CAN mapping'''

* Ensure CAN Channels are set to '''ON'''

* Press the Presets button, then select the TireX 4 zone preset.
** '''Note''' - you may need to press the cloud update button to fetch the newest presets.

===Write the settings back to your RaceCapture System===
* Press the '''Write''' button to write your new settings to the system.

===Ensure RaceCapture / TireX is powered by 12v===
* Ensure the TireX sensor(s) are receiving 12v power. If powered via RaceCapture via the plug and play harness, ensure RaceCapture is powered with 12v.

* '''Note''': USB power is insufficient for powering the CAN bus network.

===Verify the TireX data on the dashboard===
====Using the overview gauge====
* Switch to the RaceCapture dashboard mode.
* Create a new Dashboard screen by pressing the gear icon in the upper right of the screen.
* Select the TireX test dashboard preset
** '''Note''' - you may need to press the cloud update button to fetch the newest presets.

====Using the raw channels view====
* Navigate to the Raw Channels view of the dashboard by pressing the left or right arrows on the dashboard screen.

* You can observe all of the available telemetry channels, including the individual channels for the TireX sensors.

=Specifications=
''Specifications are preliminary and subject to change''
{| class="wikitable" | width="600px"
|-
! Feature
! Description
|-
| Sensor type
| Thermal array
|-
| Sensor Resolution
| 16 x 12 (196 pixels)
|-
| Object temperature range
| 0 - 127.5C (tire temperature mode (factory default)) / 0 - 255C (full frame mode)
|-
| Field of view
| 110 x 75 degrees
|-
| Accuracy
| 1C
|-
| Temperature zones (tire)
| 1 / 2 / 4 (factory default) / 8 / 16
|-
| Sample rate
| 0.5 - 64Hz (Tire temperature mode, 16Hz factory default) 0.5 - 10Hz (Full frame mode)
|-
| Processing Engine
| 32 bit
|-
| Configurable positions
| 4 (Left-Front (factory default), Right-Front, Left-Rear, Right-Rear); Reversible orientation
|-
| Emissivity
| Configurable (0.95 default)
|-
| Ambient temperature compensation
| Automatic (adjustable offset)
|-
! Electrical
!
|-
| Interface
| CAN 2.0
|-
| Supply voltage
| 6 - 14v (automotive power)
|-
| Power
| 200mW
|-
| Harness
| M8 4P Male, 250mm length
|-
! CAN bus
!
|-
| CAN baud rate
| 500K and 1M, jumper configurable (1M default)
|-
| Address space
| 4 separate address spaces (configurable via jumper)
|-
| Termination
| No Termination (configurable via jumper)
|-
|-
! Physical / Environmental
!
|-
| Construction
| CNC aluminum
|-
| Dimensions
| 64 x 46 x 12.5mm
|-
| Weight
| 10 grams
|-
| Operating temperature
| -40 - 85C
|-
| IP rating
| IP65
|}

=Dimensions / Mounting=
[[image:TireX_dimensions.png]]

==Mounting Orientation==
We recommend mounting TireX above the tire, with the cable pointing towards the rear of the vehicle.
* '''Note:''' you can clock the mounting point so the sensor is mounted at the front or rear of the wheel well; just ensure the orientation remains the same.
[[Image:tirex_mounting_orientation.jpg]]
==Mounting Distance==
TireX has a wide aspect ratio of 110 degrees, so you can use some trigonometry to calculate the distance. Here are some examples:

* 205 width = 71mm
* 225 width = 79mm
* 235 width = 82mm
* 245 width = 85mm
* 255 width = 89mm
* 275 width = 96mm
* 315 width = 110mm

[https://www.triangle-calculator.com/?what=iso&a=C%3D110%2C+c%3D245&submit=Solve Here's a convenient online calculator]

Tip: you can mount TireX at a further distance if you use the middle channels. Example:

* if only using 8 channel, you can mount 2x the distance
* If only using 16 channels, you can mount 4x the distance

* '''Note:''' 4 channels is often the resolution of choice to reduce the bulk of data generated, and gives perfectly adequate results for determining tire performance.

=Electrical / CAN connection=
* Connection is provided by a standard industrial M8 4P male plug. [[Harness_specifications#Power_.2B_CAN_Single_interconnect|Pigtails and connectors are available from Autosport Labs, or 3rd parties]]
* TireX is designed to connect to regular automotive 12-14v per our [[Harness_specifications#Power_.2B_CAN_Single_interconnect|Standard Power interconnect]]

 
[[image:M8_4P_male.png]]
{| class="wikitable" | width="600px"
|-
! Pin
! Connecton
! Wire Color
|-
| Pin 1
| CAN Low
| Brown
|-
| Pin 2
| Voltage supply (6-14v)
| White
|-
| Pin 3
| CAN High
| Blue
|-
| Pin 4
| Ground
| Black
|}

== CAN termination ==
By default, TireX is not terminated. We recommend using the external termination adapter, connected inline on the last sensor of the chain.

[[image:autosport_labs_inline_can_terminator.jpg]]

This terminator is [https://www.autosportlabs.com/product/inline-can-terminator/ available separately] or [https://www.autosportlabs.com/product/tirex-4-corner-plug-and-play-harness/ included with the TireX plug and play harness].

=== Customizing Termination ===
CAN termination can be enabled on TireX by disassembling the sensor and closing the jumper on the TireX circuit board.

[[image:tirex_jumpers_can_termination.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

=Zone Configuration=
===Up to 16 configurable temperature zones===
TireX can be configured to report up to 16 temperature zones across the sensor's entire field of vision.

When configured for 2 or more zones, temperature for zones are reported in the order of inside through outside edge.

{| class="wikitable" | width="600px"
|-
! Zones
! Coverage
|-
| 1
| Averaged across the entire field of vision
|-
| 2
| Each zone averaged across 1/2 the field of vision
|-
| 4
| Each zone averaged across 1/4 the field of vision
|-
| 8
| Each zone averaged across 1/8 the field of vision
|}
===Reversible orientation based on sensor position===
TireX zones are reversed based on the configured sensor position (left vs right side) to allow identical physical sensor mounting orientation between sides.
[[file:TireX_zones.jpg|800px]]

=CAN bus protocol=

==CAN protocol files==
DBC File for standard 4 corner, 4 zone configuration: [[file:TireX_standard.dbc.zip]]

==Overview==
The CAN bus API provides the configuration, control and sensor broadcast interface for TireX

==Conventions==
===Formula===
* Conversion formulas are expressed as converting the CAN encoded value to real-world value.

* Example:
** Encoded value in CAN message: 95
** Formula: A / 100
** Real-world value: 0.95

===Data encoding===
====Endian====
16 and 32 bit values are encoded as little endian.

====Single and mulit-byte values====
{| class="wikitable" | width="600px"
|-
! Value
! Symbol Reference
|-
| 8 Bit values
| A
|-
| 16 bit values
| A (low byte) / B (high byte)
|-
| 32 Bit values
| A (low byte) / B / C / D (high byte)
|}

==CAN Baud rate==

1M and 500K rates are supported.

1M is enabled by default; cut the jumper labeled '''BAUD''' on the bottom of TireX to enable 500K rate.

[[image:tirex_jumpers_can_term.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

==CAN base ID==

A configured TireX sensor will have a CAN base address that is a combination of the '''Main Base ID''' + '''Position Offset''' based on the installed position of the sensor on the vehicle. This combination creates a final '''Sensor Base ID'''.

All broadcast and configuration CAN messages is offset from the final calculated '''Sensor Base ID'''.

===Default Main Base ID===
Default Main CAN base ID is '''0xA100 (41216)'''

====Adjusting Main Base ID====
The base address is determined by the state of the '''ADR1''' and '''ADR2''' jumpers. By default, the jumpers are closed (bridged); the jumper can be opened by cutting the trace between the pads. To re-close the jumper, add a small amount of solder to bridge the gap between the pads you want to close.
* '''Note:''' In the vast majority of the cases you can use the default Main Base ID of 0xA100.

[[image:tirex_jumpers_base_id.png|500px]]
* '''Note''': See the [[TireX#Hardware_configuration|Hardware configuration section]] for details on making this modification.

{| class="wikitable" | width="600px"
|-
! ADR2 Jumper
! ADR1 Jumper
! Address
|-
| Closed
| Closed
| 0xA100 (41216)
|-
| Closed
| Open
| 0xB100 (45312)
|-
| Open
| Closed
| 0xC100 (49408)
|-
| Open
| Open
| 0xD100 (53504)
|}
* Opening the jumper ADR1 will add (0x1000) 4096 to the base ID
* Opening the jumper ADR2 will add (0x2000) 8192 to the base ID
* Opening both jumpers ADR1 and ADR2 will add (0x3000) 12288 to the base ID.

==Sensor Position Offset==
The sensor position will offset the '''Main Base ID''' by the position of the sensor as defined in the table, to set the final '''Sensor Base ID'''.

{| class="wikitable" | width="600px"
|-
! Position ID
! Sensor Position
! Offset
|-
| 0
| Left-Front
| 0x0 (0)
|-
| 1
| Right-Front
| 0x100 (256)
|-
| 2
| Left-Rear
| 0x200 (512)
|-
| 3
| Right-Rear
| 0x300 (768)
|}

===Example: default base address (0xA100)===
{| class="wikitable" | width="600px"
|-
! Sensor Position
! Final Sensor Base ID
|-
| Left-Front
| 0xA100
|-
| Right-Front
| 0xA200
|-
| Left-Rear
| 0xA300
|-
| Right-Rear
| 0xA400
|}

* '''Note:''' Single sensor kits are configured as left-front tire position. This can be changed by sending the appropriate configuration message.

==CAN Messages==
The announcement message is broadcast by TireX once per second for 10 seconds upon power up.

===Announcement===
'''CAN ID:''' Sensor Base ID + 0

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sample Rate
| unsigned
| A * 1
| 0.5 - 64Hz (0 = 0.5Hz)
|-
| 1
| Temperature Zones
| unsigned
| A * 1
| Number of configured temperature zones (1 / 2 / 4 / 8 / 16) (factory default is 4)
|-
| 2
| Sensor Position
| Unsigned
| A * 1
| Configured sensor position (0=Left-Front / 1=Right-Front / 2=Left-Rear / 3=Right-Rear)
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Major Version
| unsigned
| A * 1
| Firmware Major Version Number
|-
| 6
| Minor Version
| unsigned
| A * 1
| Firmware Minor Version Number
|-
| 7
| Patch Version
| unsigned
| A * 1
| Firmware Patch version number
|}

===Statistics===

Broadcast by TireX every 10 seconds.

'''CAN ID:''' Sensor Base ID + 2

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sensor Ambient Temperature
| unsigned
| A * 1
| 0 - 255C
|-
| 1
| Reserved
|
|
|
|-
| 2
| Reserved
|
|
|
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Major Version
| unsigned
| A * 1
| Firmware Major Version Number
|-
| 6
| Minor Version
| unsigned
| A * 1
| Firmware Minor Version Number
|-
| 7
| Patch Version
| unsigned
| A * 1
| Firmware Patch version number
|}

===Configuration Preferences===

This message is broadcasted to TireX to configure the sensor's preferences. The settings are persisted in TireX's flash memory.

'''CAN ID:''' Sensor Base ID + 3

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - TireX will reply with the current configuration.

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Sample Rate
| unsigned
| A * 1
| Rate to report sensor values ( 0.5 - 64Hz) Valid sample rates: 0 (0.5Hz) / 1 (1Hz) / 2 (2Hz) / 4 (4Hz) / 8 (8Hz) / 16 (16Hz) / 32 (32Hz) / 64 (64Hz). Specifying an invalid value will select the default value of 16
|-
| 1
| Temperature zones
| unsigned
| A * 1
| Number of temperature zones. Valid zones: 1 / 2 / 4 / 8 / 16. Specifying an invalid value will select the default value of 4.
|-
| 2
| Sensor Position
| unsigned
| A * 1
| Location of the sensor on the vehicle. This position adjusts the '''Sensor Base ID'''. Valid Positions 0 (Left-Front) / 1 (Right-Front) / 2 (Left-Rear) / 3 (Right-Rear). Specifying an invalid value will select the default value of 0 (Left-Front). '''Note:''' The sensor position affects the orientation of the sensor zones. Sensor Position 1 and 3 will report temperature zones left - right; Position 0 and 2 will report temperature zones right - left. 
'''Note''': When in full frame mode, this setting is ignored.
|-
| 3
| Frame mode
| unsigned
| A * 1
| 0 = Standard (Tire Temperature) mode; 1 = Full Frame mode
|-
| 4
| Reserved
|
|
|
|-
| 5
| Reserved
|
|
|
|-
| 6
| Reserved
|
|
|
|-
| 7
| Reserved
|
|
|
|}

===Calibration Preferences===

This message is broadcasted to TireX to configure the sensor's calibration. The settings are persisted in TireX's flash memory.

'''TireX is calibrated at the factory and normally these values will not need to be changed.'''

'''CAN ID:''' Sensor Base ID + 4

* '''Note:''' To read the current settings, broadcast a message with this CAN ID with no data (data length of 0) - TireX will reply with the current configuration.

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Emissivity
| unsigned
| A / 100
| Emissivity of the target. Default is 0.95
|-
| 1
| Ambient temperature compensation
| unsigned
| A * 1
| Value in C. Default is 2
|-
| 2
| Sensor Resolution
| unsigned
| 16-19
| Sensor ADC resolution, in bits. Default is 18
|-
| 3
| Reserved
|
|
|
|-
| 4
| Reserved
|
|
|
|-
| 5
| Reserved
|
|
|
|-
| 6
| Reserved
|
|
|
|-
| 7
| Reserved
|
|
|
|}

===Sensor Temperature Value Broadcast===
The following messages will contain the temperature values based on the number of temperature zones configured, broadcast at the currently configured sample rate.

* '''Note:''' The sensor position affects the orientation of the sensor zones:
** Position 1 and 3 will report temperature zones left - right;
** Position 0 and 2 will report temperature zones right - left.
====1 Zone====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====2 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====4 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====8 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 5 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 6 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 7 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 8 value
| unsigned
| A / 2
| 0 - 127.5C
|}
====16 Zones====
'''CAN ID:''' Sensor Base ID + 0x20 (32)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 1 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 2 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 3 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 4 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 5 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 6 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 7 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 8 value
| unsigned
| A / 2
| 0 - 127.5C
|}

'''CAN ID:''' Sensor Base ID + 0x21 (33)
{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Zone 9 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 1
| Zone 10 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 2
| Zone 11 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 3
| Zone 12 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 4
| Zone 13 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 5
| Zone 14 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 6
| Zone 15 value
| unsigned
| A / 2
| 0 - 127.5C
|-
| 7
| Zone 16 value
| unsigned
| A / 2
| 0 - 127.5C
|}

====Full Frame Mode====
'''CAN ID:''' Sensor Base ID + 0x40 (64)

* '''Note:''' Pixels increment linearly by row x column

{| class="wikitable" | width="600px"
|-
! Offset
! What
! Data Type
! Formula
! Value
|-
| 0
| Pixel 0 value
| unsigned
| A
| 0 - 255C
|-
| ...
| ...
| ...
| ...
| ...
|-
| 191
| Pixel 191 value
| unsigned
| A
| 0 - 255C
|}
= Hardware configuration =
Hardware defaults can be altered by disassembling TireX and adjusting jumpers on the bottom of the circuit board.

* To break a jumper: scrape the space between the jumper pads using a sharp tool, such as a razor blade or very small screwdriver.
* To re-close a jumper: use a fine tip soldering iron and add solder between the jumper pads.

[[image:tirex_jumper_settings.png|500px]]

When re-assembling the sensor, ensure the sensor and enclosure seals are correctly seated, and torque the enclosure screws evenly.

= Disassembly and replacing harness =
In the event the TireX pigtail is damaged, it can be replaced by the end user relatively easily.

Disassembly steps:
* Use a small screwdriver to remove the 4 outer screws.
* Remove the black gasket, and set aside
* Gently pry away the old harness from the notch of the enclosure
* Remove the circuit board by pressing the sensor from the outside of the enclosure.
* Remove the red seal around the sensor, and set aside.
* Using a small flat bladed screwdriver, '''carefully''' unplug the the harness from the circuit board. Gently pry away the harness connection from each side until it pops out of the connector.

Re-assembly steps:
* Re-insert the red sensor seal into the back of the main enclosure, so that it is installed and flush with the outside of the enclosure
* Plug the new harness into the circuit board. The connector mounts only one direction, and it should press in with just finger pressure. Ensure it is fully seated.
* Locate the cable notch on the enclosure. Press the harness into this notch, centered on the thick section near the end of the harness, close to the PCB connector. You may use finger / thumb pressure, or gently with a pair of cushioned pliers to prevent marring the enclosure. (you can wrap tape around the jaws of the pliers). Press it in until it is fully inserted into the notch.
* Press the PCB into the enclosure, focusing on pressing the sensor into the red seal.
* Inspect the opposite side of the enclosure, ensuring the sensor is properly seated into the seal, and no edges are caught.
* On the PCB, ensure the silicone pad is still mounted opposite of the sensor.
* Re-attach the black gasket onto the back lid of the enclosure, making sure the notch in the gasket matches the relief made in the lid to allow cable exit.
* Mount the back lid of onto the main body of the enclosure, ensuring the black gasket is properly inserted into the enclosure, with no pinching or caught edges. The stepped design of the gasket is designed to sure the back lid is perfectly centered. '''Ensure the cable relief of the bottom lid is installed in the direction where the cable exits'''
* Re-attach the 4 screws, torquing evenly until there is slight compression of the gasket.
* Test for proper operation before re-attaching it to the vehicle.
*

RaceCaptureTrack MK4

2026-02-04T21:37:28Z

Brentp: /* Mounting */

== Quick Start Guide ==
=== Overview ===
RaceCapture/Track MK4 is our latest generation motorsports telemetry system
[[File:RaceCaptureTrackMK4ac.jpg]]
=== Connecting the Hardware ===
==== Mounting ====
To ensure optimal performance, mount the RaceCapture system on a flat, level surface within the vehicle, with the round M8 connectors oriented toward the front of the vehicle, and USB connector / rubber antenna cover pointing towards the rear of the vehicle.

This orientation aligns with the factory calibration of the internal accelerometer and gyroscope.

Also:

* Mount the unit in a concealed, protected area of the vehicle, away from direct heat sources and moisture.
* Use hook-and-loop (Velcro) fasteners or other suitable mounting methods to secure the unit in place while allowing for easy removal if needed.

'''Note:''' If it is necessary to install the unit in an alternative orientation (e.g., vertical, on-edge, or upside down), ensure it is rotated in clean 90-degree increments relative to the vehicle’s primary axes. Avoid mounting the device at an arbitrary angle, as this can affect sensor accuracy.

Expert mode: For non-standard orientations, remap the accelerometer and gyroscope axes in the Setup menu to reflect the installed position.

==== Connectors ====
The RaceCapture/Track MK4 is equipped with the following connectors located on the rear panel of the module:
* M8 6-Pin Female Connector (CAN1 / CAN2 / Power)
* M8 4-Pin Female Connector (CAN1 / Power)
* SMA Antenna Connector (L5_GNSS, LTE)

==== Positioning the Antenna ====
Secure the antenna to the RP-SMA connector on the RaceCapture/Track MK4 module. Tighten the connector to 5 - 6 in-lbs, slightly beyond finger-tight, to prevent it from vibrating loose during vehicle operation. 

'''Caution:''' Do not overtighten the connector, as this may damage the SMA threads or the internal connection.
* Mount the antenna on the roof of the vehicle using the supplied magnetic base.
* Maintain a minimum separation of 3 feet (1 meter) from other transmitting antennas (e.g., cellular, FM/AM radio) to reduce signal interference.
* You can also place it on the dashboard, with an unobstructed view of the sky or on the rear parcel shelf, under the back window.
'''Note:''' Non-roof mounting may reduce GPS signal strength and tracking accuracy compared to optimal placement.

==== Powering up the Module ====
The RaceCapture/Track MK4 can be powered using the following methods: 

'''USB Power (USB Type-C)''' 

You may power the device via the USB Type-C port using any of the following sources:
* A computer USB port
* A USB car charger
* A USB battery pack
This method is ideal for quick setup, bench testing, or configuration. 

'''Vehicle Power via OBD-II (CAN1 / Power)''' 

Alternatively, you can power the module using the vehicle’s OBD-II port by connecting through an OBD-II to M8 4-Pin Female Connector. 

'''Note:''' Ensure that the chosen power source provides a stable 12V supply as required by the device for accurate sensor feedback.

=== Installing the RaceCapture App ===
'''Windows / MacOS / Linux'''
* Get the latest version of the RaceCapture app from the [https://podium.live/software| Downloads Page].
* Connect your Podium Connect Micro to your computer with the USB cable,
* Start the RaceCapture app.
* The RaceCapture app will launch the first time setup wizard.
'''Android / iOS''' 

For downloading Racecapture app, please click on the images below.
[[File:Get_it_on_google_play.png||left||205px||link=https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en]]
[[File:Apple apple store.png||Right||180px|link=https://itunes.apple.com/us/app/racecapture/id1162797255?mt=8]]
[[File:Available at Amazon App store.png||Right||200px||link=https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE]]

===On Raspberry Pi===

More advanced users can run the RaceCapture App on a Raspberry pi for a more dedicated dashboard experience.
* Learn more in the [[RaceCapture_on_Raspberry_Pi|Raspberry Pi Guide]]

=== Connecting to RaceCapture System Dashboard ===
* After powering up RaceCapture/Track MK4 with 12v or via USB power (computer or USB power source) and Installing the Race Capture App.
* Go to your device’s WiFi settings and connect to the RaceCapture/Track MK4 WiFi access point.
* '''Note:''' The default WiFi access point is open (no password). You can configure a password and enable encryption later under Setup > Wireless in the RaceCapture app.
* On Android devices, you can also pair via Bluetooth using the default PIN 1234. This can also be changed later in Setup > Wireless.
* Once you've linked the Bluetooth or WiFi (Mobile), or USB (Windows or OSX) launch the RaceCapture app.
* Launch the RaceCapture app to begin configuration. The app will automatically start the First-Time Setup Wizard to guide you through the initial setup process.
=== First Time Wizard Setup ===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture/Track MK4 will be verified. 

[[File:First time Setup.gif|800px]] 

Settings configured during the first-time setup can also be accessed later via the Setup section of the RaceCapture app. 

'''Note:''' To re-run the first-time setup, launch the RaceCapture app without connecting to the device. Then navigate to the setup screen and press the First-Time Setup button.
==== Configure System Presets ====
Select the preset configuration matching the data system you have 

[[File:Preset.png]]

==== Select Favorite Race Tracks ====
* Select the tracks you will typically race at so RaceCapture can auto detect the track location and calculate lap times.
* This is an important step to ensure you get valid data and lap times for your telemetry session.
* Note: Only select the one-track configuration per race track, to ensure the correct track is auto-selected.
* If you don't see your track listed, [http://wiki.autosportlabs.com/RaceTracks Please Submit Your Track!]
[[File:Selectracetrack.png]]
==== Configure Telemetry Streaming Key ====
Enter your unique Streaming Key in the Device ID section to enable live telemetry on Podium. 

'''Note:''' If you do not have a Streaming Key, you can obtain one by logging into [https://podium.live/ podium.live.] After setting up your Device ID, the platform will generate a Streaming Key specific to your device. 

[[File:Telemetry Streaming Key.png]]

=== Configure WiFi Connection and WiFi Telemetry ===
After exiting the setup wizard, go to Setup / Wireless. Scroll down and perform the following steps:
* Enable both WiFi Support and Client Mode.
* Enter your Hotspot's SSID and password into the client setup to connect the device to your wireless network for telemetry streaming
* Then, at the bottom, turn on "Enable WiFi telemetry"
[[File:Enable Telemetry.png|800px]]

=== Wi-Fi Operating Modes ===

RaceCapture/Track MK4 support multiple Wi-Fi operating modes to accommodate different configuration, connectivity, and telemetry use cases. Firmware version 2.23.3 introduces significant improvements to Wi-Fi reliability and connection behavior across all supported modes.

==== Wi-Fi Operating Modes ====
[[File:Wifi Modes.jpg|800px]] 

'''Access Point (AP) Mode'''

In Access Point (AP) mode, the device creates its own Wi-Fi network. The RaceCapture app connects directly to the device’s access point.

* Simple, direct connection between the app and the device
* Does not require an external hotspot or router
* Provides stable app connectivity
* Internet access is not available unless bridged through another device

This mode is useful when operating without external network infrastructure or when a direct connection is preferred.

'''AP + STA Mode (Access Point + Station)'''

In AP + STA mode, the device operates simultaneously as:
* A Wi-Fi access point for the RaceCapture app
* A Wi-Fi station (STA) connected to an external hotspot for internet access or telemetry uplink.

When operating in this mode:
* If the station is connected to a hotspot, telemetry and internet services can be routed through the hotspot.
* If the station is actively searching for a hotspot, brief pauses in access point traffic may occur while Wi-Fi scanning is in progress.

'''Note:''' During hotspot scanning, short interruptions in app communication are expected behavior.

'''Recommended Setup (App Connected to Hotspot)'''

For the smoothest real-time telemetry performance, the recommended configuration is:

* The RaceCapture app connects to the same hotspot as the device
* The device operates primarily as a Wi-Fi station
* The internal access point is not used for app communication

This configuration minimizes Wi-Fi scanning activity and provides the most stable telemetry operation, especially in dynamic or congested wireless environments.

For instructions on updating firmware, see the Updating Firmware section below.

==== Wi-Fi Reliability Improvements in Firmware v2.23.3 ====
Firmware version 2.23.3 introduces multiple improvements to Wi-Fi reliability and connection stability for RaceCapture/Track MK4 and PodiumConnect/Micro. These updates are focused on improving real-world Wi-Fi behavior during configuration and telemetry use.

'''Summary of Improvements'''

* Improved Wi-Fi connection stability during normal operation
* More reliable reconnection behavior after temporary signal loss
* Improved handling of access point and network transitions
* Reduced likelihood of stalled or unresponsive Wi-Fi connections
* Improved behavior during STA hotspot scanning
* General robustness improvements when operating in environments with variable or congested wireless conditions

'''Note:''' These improvements apply automatically when running firmware version 2.23.3 or newer. No additional configuration is required.

=== LED Status Indicators ===
The RaceCapture/Track MK4 features status LEDs that provide a visual indication of the system’s current state:
{| class="wikitable"
! LED !! Function
|-
| CAN
| Indicates activity on the OBD-II / CAN bus network. Blinks when data is being received from the ECU or sensors.
|-
| GPS
| Indicates GPS status: 
'''Slow flash:''' Searching for satellite lock 
'''Rapid flash:''' GPS lock acquired
|-
| Error
| Illuminates when the system encounters an error. Check the RaceCapture app logs for details.
|-
| Power
| Illuminates when the unit is powered via 12V or USB.
|-
| Telemetry indicator
| Indicates when real-time telemetry is actively broadcasting
|}

== Comprehensive Setup Guide ==
=== Data System Cable Connection ===
'''M8 4-Pin Female Connector (CAN1 / Power)''' 

The M8 4-pin pigtail connector is a standard interface used for CAN bus communication and power input.
[[File:M8 4-pin Female.png|200px|right]]

{| class="wikitable"
|-
! Pin !! Connection !! Notes
|-
| 1 || CAN low || White
|-
| 2 || Power || Red, 9-24v / 1A (~12W)
|-
| 3 || CAN high || Green
|-
| 4 || Ground || Black
|}
'''M8 6-Pin Female Connector (CAN1 / CAN2 / Power)''' 

[[File:M8 6-pin.png|250px|right]]
{| class="wikitable"
! Pin !! Connection !! Notes
|-
| 1
| CAN 1 Low
|
|-
| 2
| CAN 2 Low
|
|-
| 3
| CAN 2 High
|
|-
| 4
| Ground
|
|-
| 5
| CAN 1 High
|
|-
| 6
| Power
| 9–24V / 1A (~12W)
|} 

'''Note:''' The raw CAN pigtail wiring is intended for advanced or custom CAN integrations and is not required for standard OBD-II vehicle connections.
[[File:M8 TO OBD-11.jpg|300px|right]]
'''M8 CAN Bus to OBD-II cable''' 

The RaceCapture/Track MK4 connects to the vehicle’s data network using the M8 CAN Bus to OBD-II cable, which is included with the RaceCapture/Track MK4 kit. This cable allows RaceCapture/Track MK4 to interface directly with the vehicle’s OBD-II diagnostic port, enabling access to CAN bus and OBD-II data.

'''Connection Steps'''
# Plug the M8 connector end of the cable into the CAN port on the RaceCapture/Track MK4.
# Connect the OBD-II connector end to the vehicle’s OBD-II diagnostic port (typically located under the dashboard).
# Ensure the connection is secure before powering on the system.
Once connected, RaceCapture/Track MK4 will automatically communicate with the vehicle’s CAN/OBD-II system

'''M8 CAN Bus to OBD-II Cable specifications'''

The M8 CAN Bus to OBD-II cable has a length of approximately 2 meters and uses a right-angle OBD-II connector. The cable also supplies power to the RaceCapture/Track MK4 with a supported input range.

'''Vehicle compatibility''' 

Most vehicles from model year 2008 and newer support CAN communication over the OBD-II port. Some vehicles from model years 2006–2007 may provide early CAN support. Vehicles from 1996–2005 typically do not support CAN over the OBD-II port. In these cases, an OBD-II Classic adapter is required. [https://www.autosportlabs.com/product/obdii-legacy-adapter-m8/ Get the OBDII Classic adapter]

=== Connecting Data to your Racecapture ===
RaceCapture/Track MK4 simplifies integration by providing preset channel mappings for a variety of supported ECUs and CAN enabled sensor systems. These mappings ensure compatibility and reduce setup time.
==== OBDII ====
During the First-Time Setup Wizard, you can select your OBDII preset, if you’re integrating with your vehicle’s OEM data. Additional default channels (e.g., RPM, TPS, coolant temperature) may also be preloaded, depending on the system selected.
==== CAN Channel Mappings ====
You can also connect your aftermarket ECU and CAN enabled sensors to your system, tapping into up to 100 CAN sensor channels. You can verify, edit, or remove CAN channel mappings at any time by navigating to:
'''Setup > CAN Channel Mappings''' in the RaceCapture app
From this section, you can:
* View currently active channels
* Modify channel parameters (e.g., CAN ID, offset, formulae)
* Remove unused or duplicate channels
* Add custom channels manually if needed
[[File:CAN Channel Mappings.gif|800px]]
==== Full CAN Bus Integration Guide ====
For advanced configurations or unsupported systems, refer to the [https://wiki.autosportlabs.com/CAN_Bus_Integration Full CAN Bus Integration Guide.]
=== Lua Scripting and Virtual Channels ===
RaceCapture and Podium uses the standard, lightweight Lua scripting language, used as an extension / customization language for many software applications.
* For Custom Modification you can refer to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting Lua Scripting Guide] for detailed instructions and examples.
=== CAN Bus Configuration ===
To configure the CAN bus settings:
* Open the RaceCapture app and navigate to Setup > CAN Bus.
* Set the Baud Rate to match the specifications of your connected data system (e.g., 500 kbps, 1 Mbps).
* Ensure that termination is enabled if RaceCapture/Track MK4 is at one end of the CAN bus.
'''Note:''' Proper baud rate configuration and bus termination are essential for stable and accurate CAN communication.

=== Tire Pressure Monitoring System (TPMS) ===
RaceCapture/Track MK4 support direct reading of compatible Bluetooth-based [https://www.autosportlabs.com/product/tpms-sensors/ TPMS sensors]. These sensors broadcast tire pressure and temperature data wirelessly and can be read by the device without any additional TPMS receiver hardware. Unlike older 433 MHz TPMS systems, which require a separate in-vehicle receiver module, Bluetooth TPMS sensors communicate directly with RaceCapture/Track MK4.

==== System Overview ====

* TPMS sensors use Bluetooth Low Energy (BLE)
* No external TPMS receiver box is required
* Sensors wake up automatically when a pressure change is detected
* Tire pressure and temperature data are available in real time

==== Supported Features ====
* RaceCapture/Track MK4 support upto 16 TPMS sensors
* Sensors can be assigned to wheel positions:
** Left Front
** Right Front
** Left Rear
** Right Rear
* Multiple sensors may be registered per wheel position
* Sensors can be quickly reassigned when swapping wheels or tire sets

==== Registering TPMS Sensors ====
[[File:Racecapture tpms setup.gif|700px]]
# In the RaceCapture app, navigate to Setup
# Select TPMS
# Select Register Sensor.
# When the sensor is detected, add it to the sensor list.
# Assign the sensor to the appropriate wheel position.
Each sensor is identified by a unique sensor ID and signal strength indicator.

'''Sensor Identification Notes''' 

Each TPMS sensor supports an optional short text note that can be used to identify a specific wheel or tire set (for example, wheel type or tire model). 

[[File:TPMS Notes.png|400px]]

=== Driver ID and Heart Rate Sensor Setup ===
[[File:Jst-xhp-2-0mm-6-pin-connector-kit-male-female-with-pins-5-pack-7 61691.jpg|640PX]]

====Driver ID====
* Utilizes Bluetooth Low Energy (BLE) technology to automatically identify the driver in the cockpit.
* Each driver is assigned with a unique BLE-enabled device, which the system detects and associates with a registered driver profile.
* Enables real-time attribution of telemetry data (e.g., RPM, throttle position, engine temperature, g-forces) to the correct driver without manual input.
* Especially useful in endurance racing formats with multiple drivers sharing the same vehicle.

====Heart Rate Monitoring====
* Supports real-time heart rate monitoring when using a compatible heart rate sensor.
* Compatible with any device that implements the Bluetooth Heart Rate Profile (HRP).
* Verified devices include generic BLE heart rate monitors such as the [https://www.amazon.com/s?k=cyclplus+heart+rate+monitor CYCPLUS HRM]
* Provides a critical layer of biometric insight by capturing drivers’ physiological responses during sessions.

'''Note:''' Not currently compatible with most smartwatches (e.g., Garmin, Apple Watch), as they typically use proprietary protocols that do not expose standard heart rate services.

====Setup Instructions====
* Ensure your RaceCapture/Track MK4 system is upgraded to the latest firmware and the latest version of the RaceCapture app is installed.
* Open the app and navigate to Setup > Driver ID.
* Enable both Driver ID and Heart Rate options, then click Register Device.
* Register each Bluetooth device one at a time.
'''Important:''' Only power on one device during each registration to avoid incorrect pairing.
* After all devices are registered, press the Write button to save the configuration.

'''To Verify:'''
* Power on each registered Bluetooth device individually.
* The Driver ID field in the app should update automatically to reflect the active device.
* If a compatible heart rate monitor is in use, the system will also display the heart rate indicator alongside the Driver ID.
[[File:Podium Connect micro heart rate setting.gif]]

=== Bluetooth Connectivity ===
RaceCapture/Track MK4 support Bluetooth connectivity for communication with the RaceCapture app. Bluetooth can be used as an alternative to Wi-Fi for device setup, configuration, and telemetry access.

'''Overview''' 

* Bluetooth provides a direct wireless connection between the device and the RaceCapture app
* No external networking hardware is required
* Bluetooth is typically used for initial setup or when Wi-Fi is not available

'''Default Bluetooth Password''' 

By default, Bluetooth connections use the following password:
* Default Bluetooth password: 123456
'''Note :''' Older RaceCapture systems used a default Bluetooth password of 1234. Newer systems use 123456 by default.

'''Connecting via Bluetooth''' 

* Power on the RaceCapture/Track MK4
* Under your phone/tablet's Android Settings, navigate to the Bluetooth section.
* Select the option to pair a device. Your phone/tablet will search for available devices.
* Once the RaceCapture device is found, select it to pair.

'''Changing Connection Type''' 
* The connection method can be changed within the RaceCapture app:
* Open the RaceCapture app.
* Navigate to Setup → App Preferences.
* Select the desired connection type (Bluetooth or Wi-Fi).
* Return to the main screen and reconnect using the selected method.

'''Note :''' The Bluetooth password can be changed from within the device configuration settings in the RaceCapture app.

== RaceCapture App & Podium General Information ==
===RaceCapture App & Podium General Information===
'''Racecapture'''
* See the [https://wiki.autosportlabs.com/RaceCapture-Pro_MK3#RaceCapture_App_Tour RACE CAPTURE APP GENERAL INFORMATION] for a full understanding of using the app and setting up your system
[[File:RaceCapture App & Podium General Information.gif]] 

'''Podium'''
* [https://wiki.autosportlabs.com/Podium_Driver_Data_Analysis VISIT THE GUIDE ON USING PODIUM] which includes a video tour of the essential features.
[[File:Quick_Start.gif|640px]]
 
==Telemetry and Logging Setup==
===On Board Flash Memory Logging===
* Enable automatic logging under Setup > Automatic Control.
* Logging can be triggered based on a specific channel, Speed is commonly used as a trigger.
* Note: After your session, log files will be available on the SD card. These files can be imported into the RaceCapture app for analysis, or into spreadsheet tools. Refer to the log file format documentation for compatibility details
===Buffering Telemetry to Flash Memory===
* To ensure no data is lost during temporary network dropouts, PodiumConnect can buffer telemetry data to the SD card.
* When a network connection is unavailable, the system stores telemetry locally, and once reconnected, it bursts the stored data to the Podium platform.
* This buffering covers approximately one lap (~3 minutes) and is ideal for tracks with intermittent network coverage.

==Accessing Flash Memory for Log File Transfer==
PodiumConnect/Micro logs data locally in addition to live telemetry streaming. These logs can be accessed by mounting the system as a USB flash drive.

'''To enable USB drive mode:'''
* Ensure the system is connected to your desktop or mobile device via USB cable.
* Navigate to Setup > Firmware.
* Press the Switch to USB Drive Mode button to access stored log files directly.
[[File:Racecapture app switch system to usb drive mode.jpg|720px]]

'''Important Caveats:'''
* App connectivity will be temporarily disrupted if using a USB connection (Windows, macOS, Linux).
* The system must not be actively logging or broadcasting telemetry when switching to USB drive mode. 

'''To exit USB drive mode and resume normal operation:''' 
* Fully power cycle the system by disconnecting both USB and 12V power.

'''Formatting Flash Memory:'''
* Connect the system to your desktop or mobile device.
* Navigate to Setup > Firmware.
* Press the Format Flash Storage button.
=Firmware and Software Updates=
Below are the steps for updating your firmware.
==Backing Up Configurations==
Updating firmware can cause your RaceCaptureTrack MK4 to be restored to factory settings. Before updating firmware, save your settings to a file.
Steps:
* Connect to RaceCapture/Track MK4 using the RaceCapture app - using USB, or WiFi.
* Navigate to Setup and press the Read button to read the current settings from Podium Connect Micro.
* Press Save to save your settings to a file. These will be later restored after firmware is updated.

==Updating Firmware==
* Download the latest RaceCapture firmware from [http://podium.live/software Firmware]
* Unzip the archive to a location on your computer
* Connect RaceCaptureTrack MK4 via USB (Windows or OSX only)
* In the RaceCapture app, navigate to Setup and press the Firmware menu option.
* Press the Update Firmware button
* Navigate to the RaceCaptureTrack MK4 firmware you unzipped. The file will end with the extension '.ihex'. Example: PodiumConnect_2.15.2.ihex
* Press Open
The firmware update process will begin, and will complete when the gauge is 100%
After re-connecting, the firmware version should be updated in the connection message at the upper right-hand corner.

==Restoring Settings==
* Navigate to Setup and press Open.
* Select the previously saved settings file, and open the file.
* Press Write to write the settings back to PodiumConnect.

Main Page

2026-01-16T04:23:50Z

Brentp: /* RaceCapture/Pro */

__NOTOC__
{|
|}
{|id="EnWpMpBook2" style="width:100%; background-repeat: no-repeat; background-position: 0% 20%;background-color: #e0e0e0; border: 1px solid #ccc;"
|style="width:40%;"|
<div style="float: left; text-align:center;padding-left:20px;white-space: nowrap;">
<h1 style="font-size: 175%; border: none; margin: 0; padding: 1px;">
Welcome to '''Autosport Labs'''</h1>
|style="width:60%; padding-left: 10%;"|
<div style="font-size: 90%" align="right">
<div style="padding-bottom: 0px;">
'''[[Autosport_Labs:About|About Autosport Labs]]''' -
[[Autosport Labs Technology License]]
</div><div style="border-top: 1px solid #999;">
[[MegaJolt_Lite_Jr._-_A_DIY_Programmable_EDIS_Ignition_Controller_-_Users_Welcome%21| MegaJolt Lite Jr. Users Welcome]]
</div>
</div>
</div>
|}

=Autosport Labs Projects=
==Motorsports Data and Telemetry==

===RaceCapture/Pro===
[[image:racecapture_pro_mk4_connectors_1024.jpg|link=https://wiki.autosportlabs.com/RaceCapture-Pro_MK4|600px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/racecapture-pro-mk4-lap-timer-data-logger-telemetry-system/]]

===RaceCapture/Track===
[[Image:RaceCaptureTrack_MK4_3quarter_view_antenna.jpg|link=RaceCaptureTrack_MK4|500px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/racecapture-track-real-time-motorsports-telemetry-system/]]

===PodiumConnect/Micro===
[[Image:PodiumConnectMicro_3quarter_front_view.jpg|link=PodiumConnect_Micro|500px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/podiumconnect-micro-live-motorsports-telemetry-stream-data-from-your-racecar-with-aim-motec-ecumaster-vbox-lowrance/]]

[[Image:
===PodiumConnect===
[[Image:PodiumConnect_with_data_systems_white_background.jpg|link=PodiumConnect|500px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/podiumconnect-live-stream-motorsport-real-time-telemetry-from-aim-motec-race-technology-or-other-data-acquisition-systems-to-podium/]]

===Video+Data livestreaming===
Add video+data livestreaming to any RaceCapture or PodiumConnect system 
[[Image:racecapture-video-and-data-overlay.jpg|link=video_plus_data_streaming_with_racecapture|500px]]

===RaceCapture App on the Raspberry Pi===
Use a Raspberry Pi and create a dedicated dash for your RaceCapture system

[[image:racecapture_raspberry_pi.jpg|link=RaceCapture_on_Raspberry_Pi|500px]]

=Engine Management=
===Megajolt Programmable Crank Fired Ignition===
[[Image:MegajoltE_map.jpg|400px|link=Megajolt Lite Jr.]]


=Sensors and Integration=
===TireX Multi-zone tire temperature sensor===
[[file:tirex_3quarter.jpg|600px|link=TireX]]
 
[https://www.autosportlabs.com/tirex_preorders_starting_soon Pre-orders starting soon]

===ShiftX3 RGB sequential shift light, alerts and gear display===
[[Image:Shiftx3_3quarter.jpg|link=ShiftX3|700px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/shiftx3-sequential-shift-light-and-alerts/]]

===AnalogX2 4 channel Analog to CAN===
[[file:analogx2_top.jpg|400px|link=AnalogX2]]
 

===OBD2CAN OBDII Legacy Adapter===
[[Image:ASL_OBD2CAN_M8.jpg|link=OBD2CAN|400px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/obdii-legacy-adapter/]]

=Development boards / CAN bus hacking=
===ESP32-CAN-X2 dual CAN bus development board===
[[Image:ESP32-CAN-X2_3quarter_1280.jpg|link=ESP32-CAN-X2|400px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Legacy Products=
For checking legacy products, please [https://wiki.autosportlabs.com/Legacy_Products click here]

Main Page

2026-01-11T18:45:58Z

Brentp: /* Motorsports Data and Telemetry */

__NOTOC__
{|
|}
{|id="EnWpMpBook2" style="width:100%; background-repeat: no-repeat; background-position: 0% 20%;background-color: #e0e0e0; border: 1px solid #ccc;"
|style="width:40%;"|
<div style="float: left; text-align:center;padding-left:20px;white-space: nowrap;">
<h1 style="font-size: 175%; border: none; margin: 0; padding: 1px;">
Welcome to '''Autosport Labs'''</h1>
|style="width:60%; padding-left: 10%;"|
<div style="font-size: 90%" align="right">
<div style="padding-bottom: 0px;">
'''[[Autosport_Labs:About|About Autosport Labs]]''' -
[[Autosport Labs Technology License]]
</div><div style="border-top: 1px solid #999;">
[[MegaJolt_Lite_Jr._-_A_DIY_Programmable_EDIS_Ignition_Controller_-_Users_Welcome%21| MegaJolt Lite Jr. Users Welcome]]
</div>
</div>
</div>
|}

=Autosport Labs Projects=
==Motorsports Data and Telemetry==

===RaceCapture/Pro===
[[image:racecapture_pro_mk4_connectors_1024.jpg|link=https://wiki.autosportlabs.com/RaceCapture-Pro_MK4|600px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/racecapturepro-mk4/]]

===RaceCapture/Track===
[[Image:RaceCaptureTrack_MK4_3quarter_view_antenna.jpg|link=RaceCaptureTrack_MK4|500px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/racecapture-track-real-time-motorsports-telemetry-system/]]

===PodiumConnect/Micro===
[[Image:PodiumConnectMicro_3quarter_front_view.jpg|link=PodiumConnect_Micro|500px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/podiumconnect-micro-live-motorsports-telemetry-stream-data-from-your-racecar-with-aim-motec-ecumaster-vbox-lowrance/]]

[[Image:
===PodiumConnect===
[[Image:PodiumConnect_with_data_systems_white_background.jpg|link=PodiumConnect|500px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/podiumconnect-live-stream-motorsport-real-time-telemetry-from-aim-motec-race-technology-or-other-data-acquisition-systems-to-podium/]]

===Video+Data livestreaming===
Add video+data livestreaming to any RaceCapture or PodiumConnect system 
[[Image:racecapture-video-and-data-overlay.jpg|link=video_plus_data_streaming_with_racecapture|500px]]

===RaceCapture App on the Raspberry Pi===
Use a Raspberry Pi and create a dedicated dash for your RaceCapture system

[[image:racecapture_raspberry_pi.jpg|link=RaceCapture_on_Raspberry_Pi|500px]]

=Engine Management=
===Megajolt Programmable Crank Fired Ignition===
[[Image:MegajoltE_map.jpg|400px|link=Megajolt Lite Jr.]]


=Sensors and Integration=
===TireX Multi-zone tire temperature sensor===
[[file:tirex_3quarter.jpg|600px|link=TireX]]
 
[https://www.autosportlabs.com/tirex_preorders_starting_soon Pre-orders starting soon]

===ShiftX3 RGB sequential shift light, alerts and gear display===
[[Image:Shiftx3_3quarter.jpg|link=ShiftX3|700px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/shiftx3-sequential-shift-light-and-alerts/]]

===AnalogX2 4 channel Analog to CAN===
[[file:analogx2_top.jpg|400px|link=AnalogX2]]
 

===OBD2CAN OBDII Legacy Adapter===
[[Image:ASL_OBD2CAN_M8.jpg|link=OBD2CAN|400px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/obdii-legacy-adapter/]]

=Development boards / CAN bus hacking=
===ESP32-CAN-X2 dual CAN bus development board===
[[Image:ESP32-CAN-X2_3quarter_1280.jpg|link=ESP32-CAN-X2|400px]]
[[Image:add_to_cart.png|link=https://www.autosportlabs.com/product/esp32-can-x2-dual-can-bus-automotive-grade-development-board/]]

=Legacy Products=
For checking legacy products, please [https://wiki.autosportlabs.com/Legacy_Products click here]

Legacy Products

2026-01-09T15:40:02Z

Brentp:

===RaceCapture/Apex===
RaceCapture/Apex is a pro-motorsports grade real-time telemetry system with mission-critical features. For more details, please click on the image below.

[[Image:RaceCapture_Apex.jpg|link=RaceCapture-Apex|400px]]

===RaceCapture/Pro Mk3===
RaceCapture/Pro MK3 is motorsports telemetry system, packed with features for Endurance Racing, Sprint Racing, Autocross, Time Attack and more. For more details, please click on the image below.

[[Image:RaceCapturePro_MK3.jpg|link=RaceCapture-Pro_MK3|400px]]

===RaceCapture/Pro MK2===
RaceCapture/Pro MK2 is a motorsports telemetry system designed for precision performance analytics and real-time data streaming to elevate your racing strategy. For more details, please click on the image below.

[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapture-Pro_MK2]]

===RaceCapture/Pro MK1===
RaceCapture/Pro MK1 is also a a powerful, multi-channel data acquisition and control system for motorsport applications. For more details, please click on the image below.

[[Image:RaceCapturePro_RevF_with_gps.jpg|446px|link=RaceCapturePro-MK1]]

===RaceCapture/Track MK3===
[[Image:rct_mk3_3quarter.jpg|link=RaceCapture-Track_MK3|400px]]

===RaceCapture/Track MK2===
The RaceCapture-Track MK2 is a data logger, lap timer, and gauge system for race or street cars. It is ultra-compact and has OBDII and direct CAN integration to almost any sensor or ECU. For more details, please click on the image below.

[[Image:RaceCapture_external_antenna_3quarter.jpg|link=RaceCapture-Track_MK2|400px]]

===RaceCapture/Track MK1===
The RaceCapture/Track MK1 is a compact and powerful data acquisition system specifically designed for the grassroots racer and track day enthusiasts. It offers essential features to capture and analyze vehicle and driver performance, designed with affordability and ease of use in mind. For more details, please click on the image below.
[[Image:RCT in hand.jpg|link=RaceCapture-Track|400px]]

===AnalogX 4 channel analog to CAN bus I/O exapnder===
AnalogX is a compact and lightweight 4 channel Analog to CAN I/O expander, designed to be installed in-line with your wiring harness and specially designed for the harsh automotive electrical environment. For more details, please click on the image below.

[[Image:AnalogX_icons.jpg|link=AnalogX|400px]]

===ShiftX2 RGB Sequential Shift light and alerts===
The ShiftX2 is a sequential shift light and sensor alert module that is controlled by RaceCapture over CAN bus. It can monitor critical sensors, visualize predictive lap times, and customize alarms. It’s your light to use the way you want to!. For more details, please click on the image below.

[[Image:shiftX_multi.png|link=ShiftX2|400px]]

===OBD2CAN OBDII Legacy Adapter (RJ45 cable style)===
The OBD2CAN OBDII Legacy Adapter translates your car's legacy OBDII interface into a CAN OBDII interface, transparently - effectively modernizing your car's OBDII interface. For more details, please click on the image below.

[[Image:obd2can_full.jpg|link=OBD2CAN_RJ45|400px]]