Autosport Labs - User contributions [en]

RaceCapture-Track

2016-11-28T20:22:21Z

Rdoherty:

=Start it up=
[[image:RaceCapture_QuickReference.png|640px]]

==Plug it in==
Unpackage the RaceCapture system and included cable.

* Plug one end of the cable into the RaceCapture unit
* Plug the other end of the cable into your car's OBDII port.
* Place the RaceCapture unit on your dashboard with clear view of the sky. Position the system so it's square to the car's axis.

[[image:RCT_in_hand.jpg|640px]]

==Download the app==
Download the RaceCapture app for your mobile device.

* [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play]
* [https://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE Amazon App Store]
* Apple iOS app store (coming soon)

===Windows / OSX===
You can also connect to RaceCapture over USB using your Windows or OSX computer
* [http://podium.live/software Download]

==Connect to your RaceCapture system==
In your mobile device WiFI settings, connect to the RaceCapture WiFi network.
* By default, RaceCapture will setup a WiFi network starting with 'RaceCapture', with no password. You can immediately connect to this network.

Once you've connected to the RaceCapture WiFi network, launch the RaceCapture app.

===Verifying Connectivity===
The RaceCapture app will guide you through a brief automated setup and tour. During this process the connection to RaceCapture will be verified.

{{#evu:https://www.youtube.com/watch?v=gZrx4w1Y_rc}}

==System Status==

Access the system status pages through the top left menu. The system status offers information on GPS status, current WiFi state and more. You can also get a copy of the RaceCapture application log for diagnostics.

[[image:RaceCapture_status_page.png|640px]]

==Dashboard Mode==
To view your dashboard, touch the dashboard option on the main screen.

[[image:RC_app_dash_screenshot.png|640px]]
===Customizing a gauge===
Most gauges can be customized for the channel and setting visual alerts. Touch the gauge you wish to customize, select the channel you wish to monitor and optionally configure alerts.

===Navigating dashboard screens===
You can navigate between dashboard screens by swiping left or right, or press the arrow buttons in the lower corners of the screen.

===Track mapping and predictive lap timing===
RaceCapture offers predictive lap timing, which relies on a robust track detection system leveraging hundreds of track maps worldwide.

[[image:RaceCapture_trackmap_browser.png|640px]]

====How it works====
* When GPS receives a lock, RaceCapture will search for a nearby track.
* If a track is detected with one configuration, it is automatically selected.
* If a track is detected with multiple configurations, the RaceCapture app will prompt you for which configuration you're using.
* If no tracks are detected nearby, the RaceCapture app will offer the ability to create a track on the spot.
** If you're not able to immediately create the track, you can do so later under '''Setup'''.
* '''Track not found?''' [[RaceTracks|Submit the track to us]] and we'll get it into our online database.

[[image:RaceCapture_create_custom_track.png|640px]]

==Setup Mode==
You can configure all of RaceCapture's options under the setup page.

* '''Note:''' Whenever you make a change on one of these pages, you will need to '''write''' your changes back to the RaceCapture device.

===Race Tracks===
On the RaceTracks page you can create a custom track, which will be included in the library of track maps for automatic detection. To create a custom track, turn off 'Automatic race track detection' and then press the add (+) button. You will be presented with an option to create a circuit or Autocross (point-point) style course. Follow the on-screen instructions to create your track.

[[image:RaceCapture_select_track_type.png|640px]]

===GPS===
The GPS page allows you to adjust the GPS sample rate and enable/disable various channels.
* '''Note:''' We highly recommend you keep the default channels enabled for proper operation of analysis and lap timing.
* 10Hz is the recommended sample rate for the best balance of performance / accuracy. [[RaceCapturePro2_GPS|Getting the best GPS performance]]

===Race Timing===
These enable the lap timer and predictive lap timer. Leave these 'on' to enable these features.

===Analog Sensors===
RaceCapture has one analog sensor that measures current battery voltage. The default 1Hz is the recommended sample rate. To disable, set the sample rate to 'Disabled'.

* '''Note:''' Normally you would not need to adjust these settings.

===Accel / Gyro===
The recommended mounting orientation for RaceCapture is square with the chassis.
* You can re-map channels by re-assigning the physical axis to the mapped channel.
* Once defined, you can calibrate the accelerometer + gyro by pressing the calibrate button, and then pressing the '''write''' button to write the calibration back to RaceCapture.

[[image:RaceCapture_imu_config.png|640px]]

===CAN bus===
For OBDII operation, ensure the CAN bus is set to '''On'''.
* Common baud rates for OBDII are 500K and 250K. The default is 500K, which applies to nearly every CAN OBDII vehicle.

[[image:RaceCapture_CAN_config.png|640px]]

===OBDII===
You can select from a standard list of OBDII channels on the OBDII configuration screen.

[[image:RaceCapture_OBDII_config.png|640px]]
====Selecting sample rates====
For channels that require a faster response rate, like RPM and TPS, we recommend 10, 25 or 50Hz. More slowly changing channels like EngineTemperature should be set to 1 or 5Hz.

* '''Note about unsupported channels:''' If your ECU does not support a channel, the value will remain at 0. RaceCapture will time-out waiting for a response from the ECU, which will affect the performance of other channels. We recommend removing all unsupported channels to ensure optimal OBDII performance.

===Wireless===
You can configure RaceCapture's WiFi for both '''Access Point''' and '''Client''' mode.

[[image:RaceCapture_WiFi_config.png|640px]]
====Client Mode====
To enable client mode, specify the SSID and password for the network you wish to connect to and turn the client mode switch to '''on'''

====Access Point Mode====
To enable the RaceCapture access point, specify the SSID and a password.
* '''Note:''' If specified, passwords must be minimum of 8 characters. Leave the field blank to create an open network.

===Real-time Telemetry===
[[image:podium.png|thumb|200px]]
You can live-stream your data to [http://podium.live Podium ] so you can compare and share laps and runs with your friends.

<img src="http://i.imgur.com/WzHsdU1.gif" width="640"/>

====Enabling Telemetry====
* Create an account on [http://podium.live Podium] and create a device ID.
* Enter the provided device ID into the telemetry configuration page of your RaceCapture app
* Enable the telemetry option in the top level application preferences.

[[image:RaceCapture_telemetry_config.png|640px]]

When telemetry is broadcasting, you will see a green cloud icon in the application toolbar.

=====Notes about Android devices=====

* '''Hotspot mode''': Older versions of Android will lose their internet connection when connected to a WiFi network that doesn't provide an internet connection. This is a common issue when connecting to WiFi enabled cameras such as GoPros and other WiFi enabled devices. Fortunately, iOS and newer versions of Android have the smarts to detect this condition and keep the cellular connection active, but older versions of Android will require an different approach.

If you have a device that loses it's internet connection when connected to RaceCapture's WiFi network, you can solve this by enabling a hot spot on your device, and then configuring RaceCapture's WiFi interface by enabling the client configuration to connect to your hotspot, effectively reversing the connection. Once RaceCapture is configured to connect to your hotspot, it will automatically connect whenever your hotspot is turned on, and then you'll be able to broadcast telemetry to Podium.

===Logs===
To view the log messages provided by the RaceCapture unit, you can enable the '''Poll log''' check box. You can copy the current log to the clipboard by pressing the '''Copy''' button.
* '''Note:''' These logs are useful for diagnosing issues with your RaceCapture unit.

==Analysis Mode==
RaceCapture will automatically record your session in the background while in dashboard mode. To view the data, enter the '''Analysis''' mode and load an existing session. The session will be automatically named with the local track or with a timestamp.

{{#evu:https://www.youtube.com/watch?v=Hi9nA2N87RY}}

===Reviewing Laps===
If the data contains lap times, the laps will be shown in the dropdown list on the right. Select the laps you wish to compare; the '''Speed''' channel is selected by default.
* '''Comparing additional channels''': You can review additional channels by pressing the gear icon on the line chart.

===Navigating data===
Swipe across the data to compare various points correlated with the position on the track map.
* '''Zooming''' you can zoom the chart using a two-finger pinch gesture, or using the mouse scroll wheel or your laptop's trackpad scroll feature.

===Selecting time vs distance===
You can switch between time and distance data comparison by accessing the chart options, or pressing the -> or clock icon in the line chart.

===Reviewing raw data===
If your data contains no laps, such as data from a static test or dyno pull, the data will be present in one entry under the loaded session. Select this entry to view the data. The RaceCapture app will auto-select the '''Time''' dimension if it detects no significant distance traveled within the data.

===Comparing laps / runs between sessions===
You can compare data between sessions if they are in a coinciding location - just load multiple sessions and select laps between those sessions.

==Exporting Data==
You can export your sessions from your list of saved sessions.

===Importing to 3rd party software===

The RaceCapture log file format is plain CSV, which can be imported into 3rd party software.

* '''RaceRender''' provides native support for the RaceCapture log file format.
* '''DashWare''' has been used by RaceCapture customers - Rowan Hick has a write-up on [https://www.rowanhick.com/2016/01/07/racecapture-pro-dashware-win Dashware integration].

==Applying Decals==
Install the included decals on your car in prominent locations - for a guaranteed +5 HP!

[[image:chris_wynne_asl.jpg|640px]]

=More=

==Alternative ways to power==

===USB===
You can power RaceCapture using the included USB cable, plugged into your car's USB charger.

===Custom Cable===
You can build a custom cable for power and CAN bus using a standard CAT-5 ethernet cable with an RJ45 connector. Wire up using

{| class="wikitable" style="text-align:center; width:700px; height:200px;"
|+ Power, ground and CAN bus connections to RaceCapture/Pro
|-
! Connection
! RaceCapture/Pro (RJ45 cable)
|-
| +12v
| Brown
|-
| Ground
| Orange/White
|-
| CAN 1 High
| Orange
|-
| CAN 1 Low
| Green/White
|}

'''Note:''' These color codes assume EIA-T568B RJ45 cable (check printing on the cable to confirm)

[[File:RCT_RJ45_CAN.png|200px]]

RaceCapture-Track

2016-08-22T17:26:38Z

Rdoherty:

===Install software===
Download the latest RaceCapture app for your platform here: https://podium.live/software

Also install the RaceCapture App on your phone or tablet. https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture

===Connect to RaceCapture===

====WiFi (Android/iOS)====
By default, RaceCapture will setup a WiFi network named 'RaceCapture XXX' (XXX will be a random number). Connect to this WiFi network, then open the RaceCapture App.

====USB (Windows/Mac/Linux)====

Plug the USB cable into RaceCapture and your computer. Windows 10, Mac and Linux computers do not need any additional software to connect to RaceCapture.

=====Windows XP, 7, 8=====
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 users''' - These drivers are unsigned. You will need to disable the driver signing requirement for Windows 8, or upgrade to Windows 10. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]
*** [http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ Win8 64bit unsigned driver instructions]
* Plug RaceCapture in to the computer.
* If prompted to install a driver, direct Windows to the folder where you unzipped the RaceCapture/Pro drivers.
* If not prompted, manually update driver:
** Open Windows Device Manager and find the '''Ports (COM and LPT)''' section. RaceCapture/Pro should be listed there, possibly with a yellow (!) over the icon.
** Right click and select 'Update Driver'.
** Follow the instructions and direct Windows to the folder where you unzipped the RaceCapture/Pro drivers.

===Configure track===
If RaceCapture does not have a track set, when you select the Dashboard view you will be prompted to set a track: <br>[[Image:Screen Shot 2016-08-20 at 2.22.05 PM.png|500px]] <br>Search for and select your track, then click/tap the checkbox to set the track.

You can also change your track in the Tracks section in the Configuration screen: <br> [[Image:Rcttrackconfig.png|500px]]

===Setup OBDII (optional)===
To setup OBDII channels, use the OBDII screen. Turn on OBDII channels and click the + button at the bottom to add a channel. Select the channel name and sample rate. <strong>Note:</strong> Due to the design of the OBD2 protocol, individual channels (PIDs) are requested sequentially, so individual channel rates decrease based on the number of channels enabled.

[[File:Setup obdii.png|500px]]

===Save Config===

Once configured, press the Save button on the bottom right to save your configuration. Now hit the track!

File:Setup obdii.png

2016-08-22T17:21:57Z

Rdoherty:

RaceCapture-Track

2016-08-22T17:14:48Z

Rdoherty:

===Install software===
Download the latest RaceCapture app for your platform here: https://podium.live/software

Also install the RaceCapture App on your phone or tablet. https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture

===Connect to RaceCapture===

====WiFi (Android/iOS)====
By default, RaceCapture will setup a WiFi network named 'RaceCapture XXX' (XXX will be a random number). Connect to this WiFi network, then open the RaceCapture App.

====USB (Windows/Mac/Linux)====

Plug the USB cable into RaceCapture and your computer. Windows 10, Mac and Linux computers do not need any additional software to connect to RaceCapture.

<strong>Windows XP, 7, 8:</strong>
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 users''' - These drivers are unsigned. You will need to disable the driver signing requirement for Windows 8, or upgrade to Windows 10. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]
*** [http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ Win8 64bit unsigned driver instructions]
* Plug RaceCapture in to the computer.
* If prompted to install a driver, direct Windows to the folder where you unzipped the RaceCapture/Pro drivers.
* If not prompted, manually update driver:
** Open Windows Device Manager and find the '''Ports (COM and LPT)''' section. RaceCapture/Pro should be listed there, possibly with a yellow (!) over the icon.
** Right click and select 'Update Driver'.
** Follow the instructions and direct Windows to the folder where you unzipped the RaceCapture/Pro drivers.

===Configure track===
If RaceCapture does not have a track set, when you select the Dashboard view you will be prompted to set a track: <br>[[Image:Screen Shot 2016-08-20 at 2.22.05 PM.png|500px]] <br>Search for and select your track, then click/tap the checkbox to set the track.

You can also change your track in the Tracks section in the Configuration screen: <br> [[Image:Rcttrackconfig.png|500px]]

===Setup OBDII (optional)===

===Save Config===

RaceCapture-Track

2016-08-22T16:58:00Z

Rdoherty:

===Install software===
Download the latest RaceCapture app for your platform here: https://podium.live/software

===Configure track===
If RaceCapture does not have a track set, when you select the Dashboard view you will be prompted to set a track: <br>[[Image:Screen Shot 2016-08-20 at 2.22.05 PM.png|500px]] <br>Search for and select your track, then click/tap the checkbox to set the track.

You can also change your track in the Tracks section in the Configuration screen: <br> [[Image:Rcttrackconfig.png|500px]]

===Setup OBDII (optional)===

===Save Config===

RaceCapture-Track

2016-08-20T21:35:55Z

Rdoherty:

# Install software
## Download the latest RaceCapture app for your platform here: https://podium.live/software
# Configure track
## If RaceCapture does not have a track set, when you select the Dashboard view you will be prompted to set a track: <br>[[Image:Screen Shot 2016-08-20 at 2.22.05 PM.png|500px]] <br>Search for and select your track, then click/tap the checkbox to set the track.
## You can also change your track in the Tracks section in the Configuration screen: <br> [[Image:Rcttrackconfig.png|500px]]
# Setup OBDII (optional)
# Save Config

File:Rcttrackconfig.png

2016-08-20T21:29:57Z

Rdoherty:

File:Screen Shot 2016-08-20 at 2.22.05 PM.png

2016-08-20T21:23:20Z

Rdoherty:

RaceCapture-Track

2016-08-20T21:22:55Z

Rdoherty:

RaceCapture-Track

2016-08-20T03:13:28Z

Rdoherty: Created page with "# Install software # Configure track # Setup OBDII (optional) # Save Config"

# Install software
# Configure track
# Setup OBDII (optional)
# Save Config

RaceCapture/Track

2016-08-20T03:12:17Z

Rdoherty: Created page with "* Quickstart Guide"

* [[RaceCaptureTrack_Quickstart| Quickstart Guide]]

Main Page

2016-08-20T03:11:30Z

Rdoherty: /* RaceCapture */

__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==
<center>
<table>
<tr>
<td align="center">
[[Image:RaceCapturePro_logo_small.png|link=RaceCapturePro]]
<br>[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapturePro]]
<br>

<h2 style="text-decoration:underline;font-weight:bold;">[[RaceCapturePro|Race Capture Pro]]</h2>
'''Data Acquisition and Control'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]
</td>
<td align="center">
[[Image:mjlj_small_logo.png|link=Megajolt Lite Jr.]]
<br><br>[[Image:MegajoltE_map.jpg|300px|link=Megajolt Lite Jr.]]
<br><h2 style="text-decoration:underline;font-weight:bold;">[[Megajolt Lite Jr.|Megajolt Lite Jr.]]</h2>
'''Programmable Ignition Controller'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/megajolte/]]

</td>
</tr>
</table>
</center>

==Other things we're working on==

===RaceCapture===
* [[RaceCapture/Track|RaceCapture - the little brother to RaceCapture/Pro]]

===DIY Racing Helmet Microphone===
*[[Helmet_mic|Build a helmet mic on the cheap!]]

===Tweeting Race Car===
[[Tweeting_Race_Car|Our race cars tweet autonomously while on the race track!]]

===Ignition Driver Modules===
[[IgnitionDrivers|Ignition driver boards for Coil On Plug and other applications]]

===Tachometer Adapter===
[[TachAdapter|Tachometer Adapter: Adapts Tachometer to multiple coil packs]]

===Megajolt2 Roadmap===
Info on our next generation [[Megajolt2|Megajolt2]] platform- testing in 2010!

===Autosport Labs R&D Platforms===
[[Research_and_Development_Platforms|Meet the test platforms we inflict our projects upon!]]
[[Image:240z_left_rear_3quarter_400px.jpg|right]]

===Lighting===
*[[Dual_LED_cluster|Dual LED Cluster]]
*[[Sequential_shift_light_array|Sequential Shift Light Array]]

===CPU Module===
The Autosport Labs CPU Module will be the heart of our future projects. This piece combines DIY friendliness with high speed high performance 32 bit processing power.
*[[CPU_Module|CPU Module]]

===Other Things===

*[[Handy_hints|Helpful Engineering Resources]]

Main Page

2016-08-20T03:10:43Z

Rdoherty:

__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==
<center>
<table>
<tr>
<td align="center">
[[Image:RaceCapturePro_logo_small.png|link=RaceCapturePro]]
<br>[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapturePro]]
<br>

<h2 style="text-decoration:underline;font-weight:bold;">[[RaceCapturePro|Race Capture Pro]]</h2>
'''Data Acquisition and Control'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]
</td>
<td align="center">
[[Image:mjlj_small_logo.png|link=Megajolt Lite Jr.]]
<br><br>[[Image:MegajoltE_map.jpg|300px|link=Megajolt Lite Jr.]]
<br><h2 style="text-decoration:underline;font-weight:bold;">[[Megajolt Lite Jr.|Megajolt Lite Jr.]]</h2>
'''Programmable Ignition Controller'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/megajolte/]]

</td>
</tr>
</table>
</center>

==Other things we're working on==

===RaceCapture===
* [[RaceCapture|RaceCapture - the little brother to RaceCapture/Pro]]

===DIY Racing Helmet Microphone===
*[[Helmet_mic|Build a helmet mic on the cheap!]]

===Tweeting Race Car===
[[Tweeting_Race_Car|Our race cars tweet autonomously while on the race track!]]

===Ignition Driver Modules===
[[IgnitionDrivers|Ignition driver boards for Coil On Plug and other applications]]

===Tachometer Adapter===
[[TachAdapter|Tachometer Adapter: Adapts Tachometer to multiple coil packs]]

===Megajolt2 Roadmap===
Info on our next generation [[Megajolt2|Megajolt2]] platform- testing in 2010!

===Autosport Labs R&D Platforms===
[[Research_and_Development_Platforms|Meet the test platforms we inflict our projects upon!]]
[[Image:240z_left_rear_3quarter_400px.jpg|right]]

===Lighting===
*[[Dual_LED_cluster|Dual LED Cluster]]
*[[Sequential_shift_light_array|Sequential Shift Light Array]]

===CPU Module===
The Autosport Labs CPU Module will be the heart of our future projects. This piece combines DIY friendliness with high speed high performance 32 bit processing power.
*[[CPU_Module|CPU Module]]

===Other Things===

*[[Handy_hints|Helpful Engineering Resources]]

RaceCapture App User's Guide

2016-06-02T20:31:16Z

Rdoherty: /* Manual Track Configuration */

The RaceCapture/Pro V2 firmware and app represents a major upgrade to the capabilities of the original RaceCapture/Pro system.

Currently supported platforms:

* Windows: currently supported
* Linux: currently supported by running from source
* OSX - beta support

Planned support:

* Android: Beta available, contact us a racecapture@autosportlabs.com for access
* iOS

==Downloads==
Get the latest firmware and app from the [[RaceCapturePro_Downloads|Downloads Page]]

==Discussion Forums==
In the spirit of sharing and collaboration, please post all of your questions / feedback in the community forums.

[http://www.autosportlabs.org/viewforum.php?f=33 RaceCapture V2 App/Firmware Discussion Forum]

=Features=

Check out some kickass features:

==Multi-Platform, touch oriented application==
Capable of running on Windows and Android, the new RaceCapture app will ultimately combine RaceAnalyzer and the current Mobile app into a unified configuration, dashboard and analysis solution.

[[Image:RA_home_screen6.png|500px]]
[[Image:RA_AnalogChannelsView_headers.png|500px]]

[[Image:tacho_gauge_10k.png|500px]]
[[Image:RA_automatic_track_detection.png|500px]]

==Automatic Track Detection and configuration==
[[Image:rc_track_browse4.png|right|thumb|300px]]
The RaceCapture/Pro firmware supports automatic track detection and configuration, supporting up to 40 of your favorite race tracks.

When RaceCapture/Pro is powered up and GPS locks on, the system searches for a track within a 2 mile radius. If one is found, the start/finish line and sector points are automatically configured, enabling lap, sector and predictive timing features without having to alter configuration.

The latest race track configurations can be automatically downloaded and synchronized from http://www.race-capture.com via the application. If your track is not in the list, email us at racecapture@autosportlabs.com and we will work to get it added.

Automatic configuration can still be disabled and manual start/finish and sector points can be defined.

==Manual Track Configuration==

You can manually specify start/finish lines for custom track configurations.

* On the Race Track sectors page set '''Automatic Track Detection''' to '''Off'''
* For circuit type racing, set '''Separate start and finish lines''' to '''Off'''
* Click on the gear icon to the right of the Start/Finish configuration line

[[Image:Manual track config.jpg|300px]]
[[Image:Manual track config points.png|300px]]

* '''Minimum Configuration'''
** Set the latitude / longitude point of the start finish line in the Start/Finish section

* '''Sector Configuration'''
** Set additional sector points ordered in the '''direction of travel''' on the track.

==Multi-Sector Timing==
We've expanded timing from a single split point to up to 20 sectors, enabling true sector based timing. The sector timing information are exposed as two additional channels:
* sectorTime - indicates the time of the last completed sector
* sector - indicates the last completed sector

==Separate Start/Finish Lines==

To enable auto-x/rally/hillclimb scenarios we've enabled the ability to define a separate start and finish line.

The beginning of a lap is triggered by the combination of a start point which defines the general area where the race car is staged, and a launch detection algorithm combining a speed and g-force delta threshold.

The completion of a lap is detected using the conventional GPS target detection mechanism.

==Predictive Lap Timing==
A new predictive lap timing algorithm augments current 'lapTime' channel with a new channel called 'predTime'.

Once a lap is completed, the data is used as a model to predict the next, ongoing lap. The predicted time sample rate is configurable up to the native GPS data rate.

==CAN bus expansion==
[[Image:CAN_configuration.png|right|thumb|300px]]
A single CAN bus channel is supported using the CANx expansion module, which plugs in to the expansion port next to the green terminal block.

The CAN feature can be configured with a variety of standard baud rates.

CAN send and receive commands are made available via Lua scripting and can be combined with the Virtual Channel feature.

==OBD2 support==
[[Image:OBDII_view.png|right|thumb|300px]]

Enabled via the CANx module, standard OB2 PIDs can be queried and mapped to RaceCapture channels along with other sensors.

Due to the design of the OBD2 protocol, individual channels (PIDs) are requested sequentially, so individual channel rates decrease based on the number of channels enabled.

==Virtual Channels==
A virtual channel (aka 'Math channel') can be used to derive new channels from existing channel values. Examples include:

* Detecting gear based on RPM and speed ratios
* Turbo intercooler efficiency by calculating the difference between inlet and outlet temperature probes
* A calculated 'engine load' indicator by integrating RPM + Manifold Pressure Sensor value.

[[RaceCapturePro_Lua_Scripting#CAN_Bus_functions|Lua Scripting CAN bus API]]

==Lua Scripting==
Lua Scripting stability, error recovery and logging has been improved.

* Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging.
* If a wayward script somehow crashes the firmware, the RCP watchdog will fire and start up RCP in safe mode, illuminating the red LED and bypassing script execution. Then, you'll have a chance to make fixes.
* Functions have been streamlined and normalized for consistency. Additional Lua functions have been added to support virtual channels, OBDII and CAN bus messaging.

Read more in our [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]

==Improved log timing accuracy==
The core sample rate tick is now derived directly from the system's crystal-backed oscillator, making log file sample rates much more accurate.

=Upcoming Features=

The following upcoming features will bring the analysis features from RaceAnalyzer and the dashboard features from the current RaceCapture Android app into a unified experience for RaceCapture/Pro.

==Dashboard==
[[Image:tacho_gauge_10k.png|thumb|right|300px]]
The dashboard view will feature most, if not all,, of the same informational views as the current RaceCapture mobile app, including:

* Multi-gauge dashboard view
* Lap Time view showing last, predicted, best time and delta from best
* Raw channel monitoring view to show all known channels in a list
* Lap Time + real-time accelerometer + gyro view

=Installation=
Note, installation of the V2 firmware will disable the configuration functions of RaceAnalyzer. You will still be able to use analyze data from the RaceCapture/Pro log files until the analysis features are ported over to the new app.

Before continuing, save your old RaceCapture/Pro configuration to preserve any sensor calibration data. You will need this later when re-entering the calibration data into the new app

* '''Note, Due to the significant changes in the firmware, the RaceCapture .rcap configuration files are not compatible with the new configuration file format'''

==Firmware==
To start, install the latest V2 beta firmware from the downloads section. Follow the flashing instructions in the file. After flashing, unplug / replug RaceCapture/Pro and verify the USB device is recognized.

* Windows: Check under Device Manager for a RaceCapture/Pro device under the Ports section.
* Linux: When plugged in, a CDC-ACM device should show up. Check it by issuing the dmesg command; typically it will be /dev/ttyACM0

(screenshot of firmware flashing progress)

==Application==
Install the RaceCapture app after downloading the setup package from the [[RaceCapturePro_Downloads|downloads section]]

=Running=
The RaceCapture app will search for a compatible RaceCapture/Pro on all of the available ports. If it is found, the configuration will be automatically read.

=Editing Configuration=
You can edit the RaceCapture/Pro configuration by entering the configuration view by touching the top level icon or accessing the sidebar menu.

==Reading / Writing / Saving / Opening configuration==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Use the icons in the lower left of the configuration view to read / write configuration data from the controller as well as save / load configuration files.

When reading the configuration, the progress bar at the top will show activity. After making a change, be sure to write back the configuration to RaceCapture/Pro.

==Auto track detection==
[[Image:RA_automatic_track_detection.png|500px]]

To enable automatic track detection and configuration, select the Race Track / Sectors option in the left menu. Touch the "+" icon at the bottom to select tracks to add.

* Note: For the first time running you will need to download the latest set of race tracks by touching the cloud icon in the lower right corner of the app.

Search for your favorite tracks by name and add them to the list.

==GPS Configuration==
[[Image:GPS_Channel_config.png|500px]]

You can select a common sample rate for GPS related channels, up to the limit of the sensor (10Hz).

* '''Note''': Leave the Position, Speed, Distance, and Time of Day channels enabled for accurate analysis.

==Analog Channels==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Configure analog sensors using this view.

Enable a channel by selecting a channel name and sample rate, then configure the mapping scheme:

* Raw value
* Simple linear scaling
* Interpolated map

Most sensors are configured in map mode to compensate for non-linear response, like many temperature sensors.

* '''Note''' Channel #8 is fixed as a battery input channel and should not be changed.

==Pulse/RPM Sensors==
[[Image:rc_app_pulse_rpm_input.png|500px]]

Configure RPM / Timer / pulse channels using this view.

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Channel Operation Mode''': RPM, frequency, or pulse period
* '''Clock divider''': This specifies the operating range for measuring the pulse. This is typically left at 128.
* '''Pulse Per Revolution / Teeth Per Wheel''': This specifies the number of pulses representing a complete revolution of the wheel.
** For RPM mode This value is typically set based on the number of cylinders and the number of coil packs used on the engine

==Digital In/Out==
[[Image:ra_gpio_config_view.png|500px]]

Configure the 3 digital input / output channels using this view:

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Mode''': Set the channel to '''input''' for reading digital on/off sensors, or '''output''' to use the channel in output mode to control a device.

==Accelerometer/Gyro==
[[Image:rc_app_accelerometer_config_view.png|500px]]

Configure the Accelerometer / Gyro with this view. Edit channel mappings, orientation and zero levels.

==Pulse/Analog Out==
[[Image:rc_app_pwm_analog_out_config.png|500px]]

Up to 4 PWM / analog output channels are available for controlling devices - LEDs, motors - or sending signals to other systems.

Enable a channel by selecting the channel name and sample rate, then configure the channel options:
* '''Output Mode''' Select either Frequency / Pulse Width Modulated (PWM) mode or analog output mode. '''MK1 only:''' to enable analog mode you also need to flip the hardware dip switch on the RaceCapture/Pro main board.
* '''Logging Mode''' Select either logging the frequency or the analog output voltage.
* '''Startup Duty Cycle''' The default duty cycle when the system starts up.
* '''Startup Period''' The default startup value for the pulse period. A larger number means individual pulses are spread further apart.

==CAN Bus==
[[Image:CAN_configuration.png|500px]]

Enable the CAN bus interface and baud rate using this screen.

==OBD II==
[[Image:OBDII_view.png|500px]]

You can create OBDII channels and query standard OBD2 PIDs over a compatible OBD2 CAN bus link.

'''Note''' OBD2 is only supported for ECUs that support the CAN bus protocol. The mandatory requirement for CAN support is 2008, but some vehicles implemented it earlier. Research your year/make/model to confirm.

To add an OBD2 channel, click the + sign at the bottom of this configuration page and select the channel you wish to log.

'''Important''' The sample rate you select is the '''logged''' sample rate, not the actual sample rate of the data. Due to the limitations of the OBDII protocol, channels are queried sequentially in a request/reply fashion. Therefore, as more channels are enabled the effective individual channel sample rate is reduced.

==Wireless==
[[Image:Wirelessconfig.png|500px]]

===Bluetooth===
You can enable Bluetooth via the Wireless settings. After enabling and saving the configuration to RaceCapture/Pro, following these steps:

# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Turn on Bluetooth on your tablet and pair with RaceCapture/Pro, password is 1234
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
# Swipe to the digital dash screen and you should see values changing, pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

===Telemetry===

For detailed setup instructions read our [[RaceCapturePro2_TelemetryQuickstart|Telemetry Quickstart]]

==Scripting==
[[Image:Luascripting.png|500px]]

LuaScripting for RaceCapture/Pro enables unlimited capabilities for your data logging and control requirements. Create a virtual/math channel or control an airbrake or intercooler sprayer. For full information about how to write Lua Scripts, read our [[RaceCapturePro_Lua_Scripting| Lua Scripting Guide]]

Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging!

RaceCapture App User's Guide

2016-06-02T20:30:22Z

Rdoherty: /* Manual Track Configuration */

The RaceCapture/Pro V2 firmware and app represents a major upgrade to the capabilities of the original RaceCapture/Pro system.

Currently supported platforms:

* Windows: currently supported
* Linux: currently supported by running from source
* OSX - beta support

Planned support:

* Android: Beta available, contact us a racecapture@autosportlabs.com for access
* iOS

==Downloads==
Get the latest firmware and app from the [[RaceCapturePro_Downloads|Downloads Page]]

==Discussion Forums==
In the spirit of sharing and collaboration, please post all of your questions / feedback in the community forums.

[http://www.autosportlabs.org/viewforum.php?f=33 RaceCapture V2 App/Firmware Discussion Forum]

=Features=

Check out some kickass features:

==Multi-Platform, touch oriented application==
Capable of running on Windows and Android, the new RaceCapture app will ultimately combine RaceAnalyzer and the current Mobile app into a unified configuration, dashboard and analysis solution.

[[Image:RA_home_screen6.png|500px]]
[[Image:RA_AnalogChannelsView_headers.png|500px]]

[[Image:tacho_gauge_10k.png|500px]]
[[Image:RA_automatic_track_detection.png|500px]]

==Automatic Track Detection and configuration==
[[Image:rc_track_browse4.png|right|thumb|300px]]
The RaceCapture/Pro firmware supports automatic track detection and configuration, supporting up to 40 of your favorite race tracks.

When RaceCapture/Pro is powered up and GPS locks on, the system searches for a track within a 2 mile radius. If one is found, the start/finish line and sector points are automatically configured, enabling lap, sector and predictive timing features without having to alter configuration.

The latest race track configurations can be automatically downloaded and synchronized from http://www.race-capture.com via the application. If your track is not in the list, email us at racecapture@autosportlabs.com and we will work to get it added.

Automatic configuration can still be disabled and manual start/finish and sector points can be defined.

==Manual Track Configuration==
[[Image:Manual track config.jpg||thumb|300px]]
[[Image:Manual track config points.png||thumb|300px]]
You can manually specify start/finish lines for custom track configurations.

* On the Race Track sectors page set '''Automatic Track Detection''' to '''Off'''
* For circuit type racing, set '''Separate start and finish lines''' to '''Off'''
* Click on the gear icon to the right of the Start/Finish configuration line

* '''Minimum Configuration'''
** Set the latitude / longitude point of the start finish line in the Start/Finish section

* '''Sector Configuration'''
** Set additional sector points ordered in the '''direction of travel''' on the track.

==Multi-Sector Timing==
We've expanded timing from a single split point to up to 20 sectors, enabling true sector based timing. The sector timing information are exposed as two additional channels:
* sectorTime - indicates the time of the last completed sector
* sector - indicates the last completed sector

==Separate Start/Finish Lines==

To enable auto-x/rally/hillclimb scenarios we've enabled the ability to define a separate start and finish line.

The beginning of a lap is triggered by the combination of a start point which defines the general area where the race car is staged, and a launch detection algorithm combining a speed and g-force delta threshold.

The completion of a lap is detected using the conventional GPS target detection mechanism.

==Predictive Lap Timing==
A new predictive lap timing algorithm augments current 'lapTime' channel with a new channel called 'predTime'.

Once a lap is completed, the data is used as a model to predict the next, ongoing lap. The predicted time sample rate is configurable up to the native GPS data rate.

==CAN bus expansion==
[[Image:CAN_configuration.png|right|thumb|300px]]
A single CAN bus channel is supported using the CANx expansion module, which plugs in to the expansion port next to the green terminal block.

The CAN feature can be configured with a variety of standard baud rates.

CAN send and receive commands are made available via Lua scripting and can be combined with the Virtual Channel feature.

==OBD2 support==
[[Image:OBDII_view.png|right|thumb|300px]]

Enabled via the CANx module, standard OB2 PIDs can be queried and mapped to RaceCapture channels along with other sensors.

Due to the design of the OBD2 protocol, individual channels (PIDs) are requested sequentially, so individual channel rates decrease based on the number of channels enabled.

==Virtual Channels==
A virtual channel (aka 'Math channel') can be used to derive new channels from existing channel values. Examples include:

* Detecting gear based on RPM and speed ratios
* Turbo intercooler efficiency by calculating the difference between inlet and outlet temperature probes
* A calculated 'engine load' indicator by integrating RPM + Manifold Pressure Sensor value.

[[RaceCapturePro_Lua_Scripting#CAN_Bus_functions|Lua Scripting CAN bus API]]

==Lua Scripting==
Lua Scripting stability, error recovery and logging has been improved.

* Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging.
* If a wayward script somehow crashes the firmware, the RCP watchdog will fire and start up RCP in safe mode, illuminating the red LED and bypassing script execution. Then, you'll have a chance to make fixes.
* Functions have been streamlined and normalized for consistency. Additional Lua functions have been added to support virtual channels, OBDII and CAN bus messaging.

Read more in our [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]

==Improved log timing accuracy==
The core sample rate tick is now derived directly from the system's crystal-backed oscillator, making log file sample rates much more accurate.

=Upcoming Features=

The following upcoming features will bring the analysis features from RaceAnalyzer and the dashboard features from the current RaceCapture Android app into a unified experience for RaceCapture/Pro.

==Dashboard==
[[Image:tacho_gauge_10k.png|thumb|right|300px]]
The dashboard view will feature most, if not all,, of the same informational views as the current RaceCapture mobile app, including:

* Multi-gauge dashboard view
* Lap Time view showing last, predicted, best time and delta from best
* Raw channel monitoring view to show all known channels in a list
* Lap Time + real-time accelerometer + gyro view

=Installation=
Note, installation of the V2 firmware will disable the configuration functions of RaceAnalyzer. You will still be able to use analyze data from the RaceCapture/Pro log files until the analysis features are ported over to the new app.

Before continuing, save your old RaceCapture/Pro configuration to preserve any sensor calibration data. You will need this later when re-entering the calibration data into the new app

* '''Note, Due to the significant changes in the firmware, the RaceCapture .rcap configuration files are not compatible with the new configuration file format'''

==Firmware==
To start, install the latest V2 beta firmware from the downloads section. Follow the flashing instructions in the file. After flashing, unplug / replug RaceCapture/Pro and verify the USB device is recognized.

* Windows: Check under Device Manager for a RaceCapture/Pro device under the Ports section.
* Linux: When plugged in, a CDC-ACM device should show up. Check it by issuing the dmesg command; typically it will be /dev/ttyACM0

(screenshot of firmware flashing progress)

==Application==
Install the RaceCapture app after downloading the setup package from the [[RaceCapturePro_Downloads|downloads section]]

=Running=
The RaceCapture app will search for a compatible RaceCapture/Pro on all of the available ports. If it is found, the configuration will be automatically read.

=Editing Configuration=
You can edit the RaceCapture/Pro configuration by entering the configuration view by touching the top level icon or accessing the sidebar menu.

==Reading / Writing / Saving / Opening configuration==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Use the icons in the lower left of the configuration view to read / write configuration data from the controller as well as save / load configuration files.

When reading the configuration, the progress bar at the top will show activity. After making a change, be sure to write back the configuration to RaceCapture/Pro.

==Auto track detection==
[[Image:RA_automatic_track_detection.png|500px]]

To enable automatic track detection and configuration, select the Race Track / Sectors option in the left menu. Touch the "+" icon at the bottom to select tracks to add.

* Note: For the first time running you will need to download the latest set of race tracks by touching the cloud icon in the lower right corner of the app.

Search for your favorite tracks by name and add them to the list.

==GPS Configuration==
[[Image:GPS_Channel_config.png|500px]]

You can select a common sample rate for GPS related channels, up to the limit of the sensor (10Hz).

* '''Note''': Leave the Position, Speed, Distance, and Time of Day channels enabled for accurate analysis.

==Analog Channels==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Configure analog sensors using this view.

Enable a channel by selecting a channel name and sample rate, then configure the mapping scheme:

* Raw value
* Simple linear scaling
* Interpolated map

Most sensors are configured in map mode to compensate for non-linear response, like many temperature sensors.

* '''Note''' Channel #8 is fixed as a battery input channel and should not be changed.

==Pulse/RPM Sensors==
[[Image:rc_app_pulse_rpm_input.png|500px]]

Configure RPM / Timer / pulse channels using this view.

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Channel Operation Mode''': RPM, frequency, or pulse period
* '''Clock divider''': This specifies the operating range for measuring the pulse. This is typically left at 128.
* '''Pulse Per Revolution / Teeth Per Wheel''': This specifies the number of pulses representing a complete revolution of the wheel.
** For RPM mode This value is typically set based on the number of cylinders and the number of coil packs used on the engine

==Digital In/Out==
[[Image:ra_gpio_config_view.png|500px]]

Configure the 3 digital input / output channels using this view:

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Mode''': Set the channel to '''input''' for reading digital on/off sensors, or '''output''' to use the channel in output mode to control a device.

==Accelerometer/Gyro==
[[Image:rc_app_accelerometer_config_view.png|500px]]

Configure the Accelerometer / Gyro with this view. Edit channel mappings, orientation and zero levels.

==Pulse/Analog Out==
[[Image:rc_app_pwm_analog_out_config.png|500px]]

Up to 4 PWM / analog output channels are available for controlling devices - LEDs, motors - or sending signals to other systems.

Enable a channel by selecting the channel name and sample rate, then configure the channel options:
* '''Output Mode''' Select either Frequency / Pulse Width Modulated (PWM) mode or analog output mode. '''MK1 only:''' to enable analog mode you also need to flip the hardware dip switch on the RaceCapture/Pro main board.
* '''Logging Mode''' Select either logging the frequency or the analog output voltage.
* '''Startup Duty Cycle''' The default duty cycle when the system starts up.
* '''Startup Period''' The default startup value for the pulse period. A larger number means individual pulses are spread further apart.

==CAN Bus==
[[Image:CAN_configuration.png|500px]]

Enable the CAN bus interface and baud rate using this screen.

==OBD II==
[[Image:OBDII_view.png|500px]]

You can create OBDII channels and query standard OBD2 PIDs over a compatible OBD2 CAN bus link.

'''Note''' OBD2 is only supported for ECUs that support the CAN bus protocol. The mandatory requirement for CAN support is 2008, but some vehicles implemented it earlier. Research your year/make/model to confirm.

To add an OBD2 channel, click the + sign at the bottom of this configuration page and select the channel you wish to log.

'''Important''' The sample rate you select is the '''logged''' sample rate, not the actual sample rate of the data. Due to the limitations of the OBDII protocol, channels are queried sequentially in a request/reply fashion. Therefore, as more channels are enabled the effective individual channel sample rate is reduced.

==Wireless==
[[Image:Wirelessconfig.png|500px]]

===Bluetooth===
You can enable Bluetooth via the Wireless settings. After enabling and saving the configuration to RaceCapture/Pro, following these steps:

# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Turn on Bluetooth on your tablet and pair with RaceCapture/Pro, password is 1234
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
# Swipe to the digital dash screen and you should see values changing, pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

===Telemetry===

For detailed setup instructions read our [[RaceCapturePro2_TelemetryQuickstart|Telemetry Quickstart]]

==Scripting==
[[Image:Luascripting.png|500px]]

LuaScripting for RaceCapture/Pro enables unlimited capabilities for your data logging and control requirements. Create a virtual/math channel or control an airbrake or intercooler sprayer. For full information about how to write Lua Scripts, read our [[RaceCapturePro_Lua_Scripting| Lua Scripting Guide]]

Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging!

RaceCapture App User's Guide

2016-06-02T20:29:24Z

Rdoherty: /* Manual Track Configuration */

The RaceCapture/Pro V2 firmware and app represents a major upgrade to the capabilities of the original RaceCapture/Pro system.

Currently supported platforms:

* Windows: currently supported
* Linux: currently supported by running from source
* OSX - beta support

Planned support:

* Android: Beta available, contact us a racecapture@autosportlabs.com for access
* iOS

==Downloads==
Get the latest firmware and app from the [[RaceCapturePro_Downloads|Downloads Page]]

==Discussion Forums==
In the spirit of sharing and collaboration, please post all of your questions / feedback in the community forums.

[http://www.autosportlabs.org/viewforum.php?f=33 RaceCapture V2 App/Firmware Discussion Forum]

=Features=

Check out some kickass features:

==Multi-Platform, touch oriented application==
Capable of running on Windows and Android, the new RaceCapture app will ultimately combine RaceAnalyzer and the current Mobile app into a unified configuration, dashboard and analysis solution.

[[Image:RA_home_screen6.png|500px]]
[[Image:RA_AnalogChannelsView_headers.png|500px]]

[[Image:tacho_gauge_10k.png|500px]]
[[Image:RA_automatic_track_detection.png|500px]]

==Automatic Track Detection and configuration==
[[Image:rc_track_browse4.png|right|thumb|300px]]
The RaceCapture/Pro firmware supports automatic track detection and configuration, supporting up to 40 of your favorite race tracks.

When RaceCapture/Pro is powered up and GPS locks on, the system searches for a track within a 2 mile radius. If one is found, the start/finish line and sector points are automatically configured, enabling lap, sector and predictive timing features without having to alter configuration.

The latest race track configurations can be automatically downloaded and synchronized from http://www.race-capture.com via the application. If your track is not in the list, email us at racecapture@autosportlabs.com and we will work to get it added.

Automatic configuration can still be disabled and manual start/finish and sector points can be defined.

==Manual Track Configuration==
[[Image:Manual track config.jpg|right|thumb|300px]]
[[Image:Manual track config points.png|right|thumb|300px]]
You can manually specify start/finish lines for custom track configurations.

* On the Race Track sectors page set '''Automatic Track Detection''' to '''Off'''
* For circuit type racing, set '''Separate start and finish lines''' to '''Off'''
* Click on the gear icon to the right of the Start/Finish configuration line

* '''Minimum Configuration'''
** Set the latitude / longitude point of the start finish line in the Start/Finish section

* '''Sector Configuration'''
** Set additional sector points ordered in the '''direction of travel''' on the track.

==Multi-Sector Timing==
We've expanded timing from a single split point to up to 20 sectors, enabling true sector based timing. The sector timing information are exposed as two additional channels:
* sectorTime - indicates the time of the last completed sector
* sector - indicates the last completed sector

==Separate Start/Finish Lines==

To enable auto-x/rally/hillclimb scenarios we've enabled the ability to define a separate start and finish line.

The beginning of a lap is triggered by the combination of a start point which defines the general area where the race car is staged, and a launch detection algorithm combining a speed and g-force delta threshold.

The completion of a lap is detected using the conventional GPS target detection mechanism.

==Predictive Lap Timing==
A new predictive lap timing algorithm augments current 'lapTime' channel with a new channel called 'predTime'.

Once a lap is completed, the data is used as a model to predict the next, ongoing lap. The predicted time sample rate is configurable up to the native GPS data rate.

==CAN bus expansion==
[[Image:CAN_configuration.png|right|thumb|300px]]
A single CAN bus channel is supported using the CANx expansion module, which plugs in to the expansion port next to the green terminal block.

The CAN feature can be configured with a variety of standard baud rates.

CAN send and receive commands are made available via Lua scripting and can be combined with the Virtual Channel feature.

==OBD2 support==
[[Image:OBDII_view.png|right|thumb|300px]]

Enabled via the CANx module, standard OB2 PIDs can be queried and mapped to RaceCapture channels along with other sensors.

Due to the design of the OBD2 protocol, individual channels (PIDs) are requested sequentially, so individual channel rates decrease based on the number of channels enabled.

==Virtual Channels==
A virtual channel (aka 'Math channel') can be used to derive new channels from existing channel values. Examples include:

* Detecting gear based on RPM and speed ratios
* Turbo intercooler efficiency by calculating the difference between inlet and outlet temperature probes
* A calculated 'engine load' indicator by integrating RPM + Manifold Pressure Sensor value.

[[RaceCapturePro_Lua_Scripting#CAN_Bus_functions|Lua Scripting CAN bus API]]

==Lua Scripting==
Lua Scripting stability, error recovery and logging has been improved.

* Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging.
* If a wayward script somehow crashes the firmware, the RCP watchdog will fire and start up RCP in safe mode, illuminating the red LED and bypassing script execution. Then, you'll have a chance to make fixes.
* Functions have been streamlined and normalized for consistency. Additional Lua functions have been added to support virtual channels, OBDII and CAN bus messaging.

Read more in our [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]

==Improved log timing accuracy==
The core sample rate tick is now derived directly from the system's crystal-backed oscillator, making log file sample rates much more accurate.

=Upcoming Features=

The following upcoming features will bring the analysis features from RaceAnalyzer and the dashboard features from the current RaceCapture Android app into a unified experience for RaceCapture/Pro.

==Dashboard==
[[Image:tacho_gauge_10k.png|thumb|right|300px]]
The dashboard view will feature most, if not all,, of the same informational views as the current RaceCapture mobile app, including:

* Multi-gauge dashboard view
* Lap Time view showing last, predicted, best time and delta from best
* Raw channel monitoring view to show all known channels in a list
* Lap Time + real-time accelerometer + gyro view

=Installation=
Note, installation of the V2 firmware will disable the configuration functions of RaceAnalyzer. You will still be able to use analyze data from the RaceCapture/Pro log files until the analysis features are ported over to the new app.

Before continuing, save your old RaceCapture/Pro configuration to preserve any sensor calibration data. You will need this later when re-entering the calibration data into the new app

* '''Note, Due to the significant changes in the firmware, the RaceCapture .rcap configuration files are not compatible with the new configuration file format'''

==Firmware==
To start, install the latest V2 beta firmware from the downloads section. Follow the flashing instructions in the file. After flashing, unplug / replug RaceCapture/Pro and verify the USB device is recognized.

* Windows: Check under Device Manager for a RaceCapture/Pro device under the Ports section.
* Linux: When plugged in, a CDC-ACM device should show up. Check it by issuing the dmesg command; typically it will be /dev/ttyACM0

(screenshot of firmware flashing progress)

==Application==
Install the RaceCapture app after downloading the setup package from the [[RaceCapturePro_Downloads|downloads section]]

=Running=
The RaceCapture app will search for a compatible RaceCapture/Pro on all of the available ports. If it is found, the configuration will be automatically read.

=Editing Configuration=
You can edit the RaceCapture/Pro configuration by entering the configuration view by touching the top level icon or accessing the sidebar menu.

==Reading / Writing / Saving / Opening configuration==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Use the icons in the lower left of the configuration view to read / write configuration data from the controller as well as save / load configuration files.

When reading the configuration, the progress bar at the top will show activity. After making a change, be sure to write back the configuration to RaceCapture/Pro.

==Auto track detection==
[[Image:RA_automatic_track_detection.png|500px]]

To enable automatic track detection and configuration, select the Race Track / Sectors option in the left menu. Touch the "+" icon at the bottom to select tracks to add.

* Note: For the first time running you will need to download the latest set of race tracks by touching the cloud icon in the lower right corner of the app.

Search for your favorite tracks by name and add them to the list.

==GPS Configuration==
[[Image:GPS_Channel_config.png|500px]]

You can select a common sample rate for GPS related channels, up to the limit of the sensor (10Hz).

* '''Note''': Leave the Position, Speed, Distance, and Time of Day channels enabled for accurate analysis.

==Analog Channels==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Configure analog sensors using this view.

Enable a channel by selecting a channel name and sample rate, then configure the mapping scheme:

* Raw value
* Simple linear scaling
* Interpolated map

Most sensors are configured in map mode to compensate for non-linear response, like many temperature sensors.

* '''Note''' Channel #8 is fixed as a battery input channel and should not be changed.

==Pulse/RPM Sensors==
[[Image:rc_app_pulse_rpm_input.png|500px]]

Configure RPM / Timer / pulse channels using this view.

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Channel Operation Mode''': RPM, frequency, or pulse period
* '''Clock divider''': This specifies the operating range for measuring the pulse. This is typically left at 128.
* '''Pulse Per Revolution / Teeth Per Wheel''': This specifies the number of pulses representing a complete revolution of the wheel.
** For RPM mode This value is typically set based on the number of cylinders and the number of coil packs used on the engine

==Digital In/Out==
[[Image:ra_gpio_config_view.png|500px]]

Configure the 3 digital input / output channels using this view:

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Mode''': Set the channel to '''input''' for reading digital on/off sensors, or '''output''' to use the channel in output mode to control a device.

==Accelerometer/Gyro==
[[Image:rc_app_accelerometer_config_view.png|500px]]

Configure the Accelerometer / Gyro with this view. Edit channel mappings, orientation and zero levels.

==Pulse/Analog Out==
[[Image:rc_app_pwm_analog_out_config.png|500px]]

Up to 4 PWM / analog output channels are available for controlling devices - LEDs, motors - or sending signals to other systems.

Enable a channel by selecting the channel name and sample rate, then configure the channel options:
* '''Output Mode''' Select either Frequency / Pulse Width Modulated (PWM) mode or analog output mode. '''MK1 only:''' to enable analog mode you also need to flip the hardware dip switch on the RaceCapture/Pro main board.
* '''Logging Mode''' Select either logging the frequency or the analog output voltage.
* '''Startup Duty Cycle''' The default duty cycle when the system starts up.
* '''Startup Period''' The default startup value for the pulse period. A larger number means individual pulses are spread further apart.

==CAN Bus==
[[Image:CAN_configuration.png|500px]]

Enable the CAN bus interface and baud rate using this screen.

==OBD II==
[[Image:OBDII_view.png|500px]]

You can create OBDII channels and query standard OBD2 PIDs over a compatible OBD2 CAN bus link.

'''Note''' OBD2 is only supported for ECUs that support the CAN bus protocol. The mandatory requirement for CAN support is 2008, but some vehicles implemented it earlier. Research your year/make/model to confirm.

To add an OBD2 channel, click the + sign at the bottom of this configuration page and select the channel you wish to log.

'''Important''' The sample rate you select is the '''logged''' sample rate, not the actual sample rate of the data. Due to the limitations of the OBDII protocol, channels are queried sequentially in a request/reply fashion. Therefore, as more channels are enabled the effective individual channel sample rate is reduced.

==Wireless==
[[Image:Wirelessconfig.png|500px]]

===Bluetooth===
You can enable Bluetooth via the Wireless settings. After enabling and saving the configuration to RaceCapture/Pro, following these steps:

# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Turn on Bluetooth on your tablet and pair with RaceCapture/Pro, password is 1234
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
# Swipe to the digital dash screen and you should see values changing, pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

===Telemetry===

For detailed setup instructions read our [[RaceCapturePro2_TelemetryQuickstart|Telemetry Quickstart]]

==Scripting==
[[Image:Luascripting.png|500px]]

LuaScripting for RaceCapture/Pro enables unlimited capabilities for your data logging and control requirements. Create a virtual/math channel or control an airbrake or intercooler sprayer. For full information about how to write Lua Scripts, read our [[RaceCapturePro_Lua_Scripting| Lua Scripting Guide]]

Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging!

File:Manual track config points.png

2016-06-02T20:28:50Z

Rdoherty: Rdoherty uploaded a new version of File:Manual track config points.png

File:Manual track config points.png

2016-06-02T20:25:46Z

Rdoherty:

File:Manual track config.jpg

2016-06-02T20:25:15Z

Rdoherty:

RaceCapture-Pro MK2

2016-05-25T20:59:38Z

Rdoherty: /* RaceCapture/Pro MK2 Specifications */

=RaceCapture/Pro Quick Links=
* [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

==Getting Started==
*'''[[RaceCapturePro_Downloads|Software Downloads]]'''
*'''[[RaceCapturePro2_QuickStart|First time setup]]'''
*'''[[RaceCapturePro2_Hardware_Install|Hardware install]]'''

==How To==
*[[RaceCapturePro2_TelemetryQuickstart|How to: set up telemetry]]
*[[RaceCapturePro2_Enable_Predictive_Timing|How to: enable Predictive Timing]]
*[[RaceCapturePro2_OBD2|How to: enable OBD2 channels]]
*[[RaceCapturePro2_GoProWiFi|How to: Automatically trigger a GoPro camera]]
*[[RaceCapturePro2_Calibrate_Sensor|How to: calibrate and configure an analog sensor]]
*[[RaceCapturePro2_ShiftLights|How to: sequential shift lights]]
*[[RaceCapturePro2_GPS|How to: get best GPS data]]
*[[RCP_CAN|How to: Integrate ECU / CAN bus data]]
*[[RaceTracks|How to: Submit a new race track]]
*[[RaceCapturePro_Analysis|How to: analyze your data]]
*[[RaceCapturePro_FAQ|More FAQs and How-To's]]

==User Guides==
*[[RaceCapturePro2_hardware_guide|Hardware installation and operation]]
*[[RaceCapturePro2_3.5G_module_upgrade|3.5G Module Upgrade]]
*[[RaceCapture_App_User%27s_Guide|RaceCapture App User's Guide]]
*[[RaceCapturePro_Sensors|Sensor Guide]]
*[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]

==By Car==
*[[RaceCapturePro2_vehicle_guide|Vehicle Guide]]

==By Sensor Type==
*[[RaceCapturePro2_RPM|RPM]]'''

==Reference==
*[[RaceCapturePro2_logfile_reference|Log file reference]]

==More Information==
*[https://github.com/autosportlabs Source code]

===Previous Hardware Versions===
[[RaceCapturePro-MK1|RaceCapture/Pro MK1]]

=Quick Reference=
Download a [http://www.autosportlabs.com/racecapturepro-mk2-quick-reference/racecapture-pro-mk2-quick-reference-sheet printable PDF]

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

=RaceCapture/Pro MK2 Specifications=

{| class="wikitable" style="text-align: left"
!colspan="2"|Input / Output Channels
|-
!colspan="2"|'''Analog Inputs'''
|-
|Channels
|8 (battery voltage dedicated on channel 8)
|-
|Voltage range
|0-5v
|-
|Input impedance
|1M ohm
|-
|Voltage protection
|400v (intermittent)
|-
|ADC precision
|12 bit
|-
|Maximum sample rate
|1000Hz
|-
|Mapping
|Raw / Linear formula / Interpolated map
|-
!colspan="2"|'''Digital I/O'''
|-
|Channels
|3
|-
|Output mode type
|Open drain
|-
|Output current capacity
|1A, inductive clamped
|-
|Input mode voltage range
|0-12v
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''Timer Inputs (RPM / Frequency)'''
|-
|Channels
|3
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''PWM/Analog outputs'''
|-
|Channels
|4
|-
|PWM output type
|push/pull
|-
|PWM output voltage range
|5v
|-
|Output current capacity
|50mA
|-
|Analog Output
|0-5v
|-
!colspan="2"|Voltage Reference
|-
|Output Voltage/Capacity
|5v / 1A
|-
!colspan="2"|Connectivity
|-
!colspan="2"|'''CAN Bus'''
|-
|CAN Channels
|2
|-
|CAN baud rate
|125K, 250K, 500K, 1M baud
|-
|CAN filters
|14 per channel
|-
|Protocol support
|OBDII PID, custom CAN messaging
|-
!colspan="2"|'''Telemetry/Wireless'''
|-
|Cellular (North America)
|3.5G GSM 850/1900MHz (internal module, optional)
|-
|Cellular (Worldwide)
|2.5G Quad-band GSM (internal module, optional)
|-
|Bluetooth
|Bluetooth 2.0 (external module, optional)
|-
|Aux Serial
|Type External RJ11 / RS232 signaling
|-
|Max Baud Rate
|230400
|-
!colspan="2"|Inertial Motion Unit
|-
|Accelerometer Channels
|3 (X/Y/Z) (2G, 4G capable)
|-
|Gyro
|3 (Yaw/Pitch/Roll) (1000 degrees/sec)
|-
|Magnetic compass
|1 (Bearing) (device capable of 3) (*Coming in 2.9.x firmware)
|-
!colspan="2"|GPS
|-
|GPS Type
|External active antenna
|-
|GPS Maximum sample rate
|50Hz
|-
|GPS accuracy
|2.5M CEP
|-
!colspan="2"|Storage
|-
|Micro SD
|Up to 32GB (SDHC) FAT32
|-
!colspan="2"|Configuration Capacity
|-
|Auto-detect track database
|240
|-
|Sectors per track
|20
|-
|Channel support
|200
|-
!colspan="2"|Physical
|-
|Dimensions
|5.3" (width) x 4.2" (height) x 1.2" (tall) / 135x110x31 mm(est)
|-
|Mounting area
|5.5"(140mm) x 4"(102mm)
|-
|Mounting holes
|Dual mounting points on 5" (127mm) centers - 0.125"-0.25" (3-6mm) fastener
|-
|Weight
|9oz / 255gm (est)
|-
|Power Consumption (max)
|Main System: 0.6W<br/>With Bluetooth: 1.6W<br/>With Cellular Telemetry: 8.6W<br/>With Cellular Telemetry and Bluetooth: 9.6W
|-
|Temperature
| Max Internal Temperature while operating: -40°C ~ 85°C / -40°C ~ 80°C (Telemetry module)
|}

[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

How To Update Firmware

2016-05-05T14:55:20Z

Rdoherty:

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

'''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.

Connect RaceCapture/Pro MK2 to your computer and connect to it with the app.

* Press the 'Configuration' button to navigate to the configuration section.
* On the left menu, select Firmware
* On the firmware screen, press the button "Update Firmware"
* Navigate to the firmware file ending in ".ihex"
* Select this file. The firmware will update and show a percentage progress indicator.

* If there is a problem detecting RaceCapture/Pro, unplug/replug and restart the app.

'''Alternative method'''
* While holding down the button on RaceCapture/Pro, power it up by plugging in to USB.
* You should observe a rapidly flashing red LED on the unit: it is in bootloader mode.
* Start the app. Note, it will not be able to connect - this is expected.
* Navigate to the configuration/firmware update screen, select the firmware file and update the firmware.

Problems? visit http://autosportlabs.org and post your question - we will help you promptly.

=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.

RaceCapturePro installation guide

2016-04-05T04:20:23Z

Rdoherty:

=MK1 Installation Guide=
This guide is for MK1, MK2 guide is here: https://www.autosportlabs.net/RaceCapturePro2_Hardware_Install
==Connections==

[[File:RCP_terminal_block_connectors.png]]

[[File:RaceCapture-Pro LED connections.png]]

===Power Connection===
Connect RaceCapture/Pro to a power source between 9 and 24V. To fully support all devices and outputs, provide at least a 5A fused connection.

==Sensors==
'''Also see the [[RaceCapturePro_Sensors|Comprehensive Sensor installation guide]]'''

===Analog Inputs 1-7===

====Specifications====
* RaceCapture/Pro has 8 analog inputs; the 8th input is wired internally to measuring battery voltage.
* Analog input range is 0 - 5v
* Input Impedance: 15K ohm

====Active Sensors/Signals====
The Analog Input Channels accept a 0-5v input signal (protected up to 40V). Connect the input from a sensor to the appropriate connection of the terminal block.
<center>[[Image:active_sensor_connection.png]]</center>

====Resistive sensor====
When connecting resistive style sensors, like many temperature and pressure sensors, one terminal of the sensor is connected to ground, and the other is connected to the Analog input, with a pullup resistor connected to the +5V Voltage Reference on the terminal block. A 2.2K resistor is recommended for most applications.
<center>[[Image:temp_sensor_connection.png]]</center>

===5V Voltage Reference===
This output provides a 5V reference to be used with the Analog Inputs. Up to 50mA is provided to supply power to active sensors, pull-up resistors and other purposes. This reference output is protected against short-circuits with an auto-resetting fuse. If the fuse is active, a low or zero voltage reading may be observed on this port. To verify an over-current situation, test the voltage on the port without any load connected.

===Analog/Frequency Outputs 1 - 4===
Depending on configuration, these outputs provide a settable 0-5v analog output voltage, or frequency output where the pulse-width and frequency can be set. These outputs can supply 50mA each.

====DIP switch setting====
In order to configure a channel for digital or analog output, you must set the [[#4_position_DIP_switch_.28SW1.29|DIP switch]] as well updating the [[RaceCapturePro_SoftwareOperation#Digital_I.2FO|Software Setting]]

===General Input/Output Channels 1 - 3===
Depending on configuration, these channels can accept either a digital input, or provide an output to control external devices.
* When configured for '''input''', the channel accepts a 0-5v input (protected up to 45V). Each input channel has a built-in 10K pullup resistor connected to 5V.
* When configured for '''output''', the channel provides an open-drain output that can drive 1A and is thermal / over-current protected with inductive load clamping. When the output is deactivated, a 1K ohm pull-up to +5v is present.

====Jumper Configuration====
In order to configure a channel for input and output, you must set the [[#GPIO_configuration_jumpers|appropriate jumper]] as well updating the [[RaceCapturePro_SoftwareOperation#Analog.2FPulse_Outputs|Software Setting]]

===Frequency/Pulse Input 1 - 3===
These input channels can be used to time the duration between digital pulses for purposes of measuring RPM, shaft speed, and so on. The input accepts 0-5V (protected up to 40V). Each input has a built-in 10K pullup resistor connected to 5V.

====TACH SIGNAL NOTES====

'''Do not connect the old-style tachometer signal directly to RaceCapture/Pro.''' This signal is typically sourced from a wire that connects directly to the (-) post of the ignition coil. These signals are 400-500v peak and can damage your RaceCapture/Pro hardware.

'''[[CoilX CoilX Sensor Module]]'''

[[Image:coilx_wiring_sm.jpg|300px]]

You can use the CoilX sensor module to safely interface this high voltage RPM signal. See the [[CoilX|CoilX page]] for more information.

Newer style tach signals sourced from the ECU will likely provide a clean square wave signal and can be connected directly to this input.

If unsure, observe the signal with an oscilloscope and/or consult technical documentation of your vehicle.

===Expansion Port===

[[File:Expansionport.jpg]]

The RJ45 connector to the right of the terminal block is used for the CAN/OBDII bus expansion module or other custom hardware expansion devices.

===SD Card Slot===

[[File:Sdcard.jpg]]

The SD card slot is used to store datalogging sessions. 512MB to 32GB cards are supported.

===USB Port===

[[File:Usbport.jpg]]

Used for configuring RaceCapture Pro via [[RaceCapturePro_SoftwareOperation Race Analyzer Software]]

===LED Indicators===

[[File:Leds.jpg]]

* Power LED
Indicates the unit is powered up (via 12v supply or USB)
* LED1
Indicates GPS Activity. Slow flash (1Hz) indicates GPS is actively acquiring. Fast flash (10 times per second) indicates GPS is locked on to satellites.
* LED2
Indicates SD card Logging Activity. The flash rate matches the channel with the highest configured logging rate.
* LED3
Indicates error status when writing to SD Card (future error conditions will be indicated by this LED)

===Pushbutton===

[[File:Pushbutton.jpg]]

Press to manually start / stop a logging session. Note this may be overridden by any on-board scripts that may automatically start or stop logging.

===Communication Ports===

[[File:Expansionports.jpg]]

The communication ports a standard RS232 serial connection with power (up to 5v at 1.5A)
* Port 1
Used for telemetry expansion module
* Port 2
Used for GPS module

==Installation==
==Mounting orientation and position==

The ideal mounting position for RaceCapture/Pro is mounted flat (right side up or upside down), in the exact center of the vehicle. This gives the best effect from the built in Gyroscope, which measures Yaw (understeer / oversteer).

<<Todo: add picture or diagram here>>

===Shock isolation mounting===
In very harsh environments you may want to mount RaceCapture/Pro using rubber isolators. [http://www.karman.com/selectvibro.cfm Info on isolation mounts]

===Default Accelerometer Configuration===
The default accelerometer configuration assumes RaceCapture/Pro is mounted flat, right side up with the terminal block pointed towards the front of the vehicle. Other orientations are supported by changing the settings in the Software. See the [[RaceCapturePro_SoftwareOperation#Accelerometer_Inputs|Operation Guide]] for more information.

==Internal Switches / Jumpers==
===4 position DIP switch (SW1)===

[[File:Dipswitches.jpg]]

This switch bank configures the 4 outputs for Analog or Frequency/PWM mode. To enable analog mode for a particular output channel, slide the switch for the selected channel to the 'on' position. For Frequency/PWM mode slide the switch to 'off'.

===GPIO configuration jumpers===

[[File:Dpio.jpg]]

The array of jumper blocks configures the 3 GPIO channels for either digital input or output. To configure a particular channel, move the jumper to either the IN position (for input) or OUT (for output)

===Reset Pushbutton===

[[File:Resetpushbutton.jpg]]

The reset push-button, if installed, is used as a hard reset for the running firmware.

===Test Pushbutton===

[[File:Testpushbutton.jpg]]

The test push-button, if installed, is used to load the factory bootloader for re-writing flash. Also see: [[RaceCapture/Pro_firmware_upgrade|How to flash RaceCapture/Pro firmware]]

RaceCapture App User's Guide

2016-04-05T04:18:30Z

Rdoherty: /* Pulse/Analog Out */

The RaceCapture/Pro V2 firmware and app represents a major upgrade to the capabilities of the original RaceCapture/Pro system.

Currently supported platforms:

* Windows: currently supported
* Linux: currently supported by running from source
* OSX - beta support

Planned support:

* Android: Beta available, contact us a racecapture@autosportlabs.com for access
* iOS

==Downloads==
Get the latest firmware and app from the [[RaceCapturePro_Downloads|Downloads Page]]

==Discussion Forums==
In the spirit of sharing and collaboration, please post all of your questions / feedback in the community forums.

[http://www.autosportlabs.org/viewforum.php?f=33 RaceCapture V2 App/Firmware Discussion Forum]

=Features=

Check out some kickass features:

==Multi-Platform, touch oriented application==
Capable of running on Windows and Android, the new RaceCapture app will ultimately combine RaceAnalyzer and the current Mobile app into a unified configuration, dashboard and analysis solution.

[[Image:RA_home_screen6.png|500px]]
[[Image:RA_AnalogChannelsView_headers.png|500px]]

[[Image:tacho_gauge_10k.png|500px]]
[[Image:RA_automatic_track_detection.png|500px]]

==Automatic Track Detection and configuration==
[[Image:rc_track_browse4.png|right|thumb|300px]]
The RaceCapture/Pro firmware supports automatic track detection and configuration, supporting up to 40 of your favorite race tracks.

When RaceCapture/Pro is powered up and GPS locks on, the system searches for a track within a 2 mile radius. If one is found, the start/finish line and sector points are automatically configured, enabling lap, sector and predictive timing features without having to alter configuration.

The latest race track configurations can be automatically downloaded and synchronized from http://www.race-capture.com via the application. If your track is not in the list, email us at racecapture@autosportlabs.com and we will work to get it added.

Automatic configuration can still be disabled and manual start/finish and sector points can be defined.

==Manual Track Configuration==
[[Image:rc_manual_track_config.png|right|thumb|300px]]
You can manually specify start/finish lines for custom track configurations.

* On the Race Track sectors page set '''Automatic Track Detection''' to '''Off'''
* For circuit type racing, set '''Separate start and finish lines''' to '''Off'''

* '''Minimum Configuration'''
** Set the latitude / longitude point of the start finish line in the Start/Finish section

* '''Sector Configuration'''
** Set additional sector points ordered in the '''direction of travel''' on the track.

==Multi-Sector Timing==
We've expanded timing from a single split point to up to 20 sectors, enabling true sector based timing. The sector timing information are exposed as two additional channels:
* sectorTime - indicates the time of the last completed sector
* sector - indicates the last completed sector

==Separate Start/Finish Lines==

To enable auto-x/rally/hillclimb scenarios we've enabled the ability to define a separate start and finish line.

The beginning of a lap is triggered by the combination of a start point which defines the general area where the race car is staged, and a launch detection algorithm combining a speed and g-force delta threshold.

The completion of a lap is detected using the conventional GPS target detection mechanism.

==Predictive Lap Timing==
A new predictive lap timing algorithm augments current 'lapTime' channel with a new channel called 'predTime'.

Once a lap is completed, the data is used as a model to predict the next, ongoing lap. The predicted time sample rate is configurable up to the native GPS data rate.

==CAN bus expansion==
[[Image:CAN_configuration.png|right|thumb|300px]]
A single CAN bus channel is supported using the CANx expansion module, which plugs in to the expansion port next to the green terminal block.

The CAN feature can be configured with a variety of standard baud rates.

CAN send and receive commands are made available via Lua scripting and can be combined with the Virtual Channel feature.

==OBD2 support==
[[Image:OBDII_view.png|right|thumb|300px]]

Enabled via the CANx module, standard OB2 PIDs can be queried and mapped to RaceCapture channels along with other sensors.

Due to the design of the OBD2 protocol, individual channels (PIDs) are requested sequentially, so individual channel rates decrease based on the number of channels enabled.

==Virtual Channels==
A virtual channel (aka 'Math channel') can be used to derive new channels from existing channel values. Examples include:

* Detecting gear based on RPM and speed ratios
* Turbo intercooler efficiency by calculating the difference between inlet and outlet temperature probes
* A calculated 'engine load' indicator by integrating RPM + Manifold Pressure Sensor value.

[[RaceCapturePro_Lua_Scripting#CAN_Bus_functions|Lua Scripting CAN bus API]]

==Lua Scripting==
Lua Scripting stability, error recovery and logging has been improved.

* Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging.
* If a wayward script somehow crashes the firmware, the RCP watchdog will fire and start up RCP in safe mode, illuminating the red LED and bypassing script execution. Then, you'll have a chance to make fixes.
* Functions have been streamlined and normalized for consistency. Additional Lua functions have been added to support virtual channels, OBDII and CAN bus messaging.

Read more in our [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]

==Improved log timing accuracy==
The core sample rate tick is now derived directly from the system's crystal-backed oscillator, making log file sample rates much more accurate.

=Upcoming Features=

The following upcoming features will bring the analysis features from RaceAnalyzer and the dashboard features from the current RaceCapture Android app into a unified experience for RaceCapture/Pro.

==Dashboard==
[[Image:tacho_gauge_10k.png|thumb|right|300px]]
The dashboard view will feature most, if not all,, of the same informational views as the current RaceCapture mobile app, including:

* Multi-gauge dashboard view
* Lap Time view showing last, predicted, best time and delta from best
* Raw channel monitoring view to show all known channels in a list
* Lap Time + real-time accelerometer + gyro view

=Installation=
Note, installation of the V2 firmware will disable the configuration functions of RaceAnalyzer. You will still be able to use analyze data from the RaceCapture/Pro log files until the analysis features are ported over to the new app.

Before continuing, save your old RaceCapture/Pro configuration to preserve any sensor calibration data. You will need this later when re-entering the calibration data into the new app

* '''Note, Due to the significant changes in the firmware, the RaceCapture .rcap configuration files are not compatible with the new configuration file format'''

==Firmware==
To start, install the latest V2 beta firmware from the downloads section. Follow the flashing instructions in the file. After flashing, unplug / replug RaceCapture/Pro and verify the USB device is recognized.

* Windows: Check under Device Manager for a RaceCapture/Pro device under the Ports section.
* Linux: When plugged in, a CDC-ACM device should show up. Check it by issuing the dmesg command; typically it will be /dev/ttyACM0

(screenshot of firmware flashing progress)

==Application==
Install the RaceCapture app after downloading the setup package from the [[RaceCapturePro_Downloads|downloads section]]

=Running=
The RaceCapture app will search for a compatible RaceCapture/Pro on all of the available ports. If it is found, the configuration will be automatically read.

=Editing Configuration=
You can edit the RaceCapture/Pro configuration by entering the configuration view by touching the top level icon or accessing the sidebar menu.

==Reading / Writing / Saving / Opening configuration==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Use the icons in the lower left of the configuration view to read / write configuration data from the controller as well as save / load configuration files.

When reading the configuration, the progress bar at the top will show activity. After making a change, be sure to write back the configuration to RaceCapture/Pro.

==Auto track detection==
[[Image:RA_automatic_track_detection.png|500px]]

To enable automatic track detection and configuration, select the Race Track / Sectors option in the left menu. Touch the "+" icon at the bottom to select tracks to add.

* Note: For the first time running you will need to download the latest set of race tracks by touching the cloud icon in the lower right corner of the app.

Search for your favorite tracks by name and add them to the list.

==GPS Configuration==
[[Image:GPS_Channel_config.png|500px]]

You can select a common sample rate for GPS related channels, up to the limit of the sensor (10Hz).

* '''Note''': Leave the Position, Speed, Distance, and Time of Day channels enabled for accurate analysis.

==Analog Channels==
[[Image:RA_AnalogChannelsView_headers.png|500px]]

Configure analog sensors using this view.

Enable a channel by selecting a channel name and sample rate, then configure the mapping scheme:

* Raw value
* Simple linear scaling
* Interpolated map

Most sensors are configured in map mode to compensate for non-linear response, like many temperature sensors.

* '''Note''' Channel #8 is fixed as a battery input channel and should not be changed.

==Pulse/RPM Sensors==
[[Image:rc_app_pulse_rpm_input.png|500px]]

Configure RPM / Timer / pulse channels using this view.

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Channel Operation Mode''': RPM, frequency, or pulse period
* '''Clock divider''': This specifies the operating range for measuring the pulse. This is typically left at 128.
* '''Pulse Per Revolution / Teeth Per Wheel''': This specifies the number of pulses representing a complete revolution of the wheel.
** For RPM mode This value is typically set based on the number of cylinders and the number of coil packs used on the engine

==Digital In/Out==
[[Image:ra_gpio_config_view.png|500px]]

Configure the 3 digital input / output channels using this view:

Enable a channel by selecting a channel name and sample rate, then configure the channel options:

* '''Mode''': Set the channel to '''input''' for reading digital on/off sensors, or '''output''' to use the channel in output mode to control a device.

==Accelerometer/Gyro==
[[Image:rc_app_accelerometer_config_view.png|500px]]

Configure the Accelerometer / Gyro with this view. Edit channel mappings, orientation and zero levels.

==Pulse/Analog Out==
[[Image:rc_app_pwm_analog_out_config.png|500px]]

Up to 4 PWM / analog output channels are available for controlling devices - LEDs, motors - or sending signals to other systems.

Enable a channel by selecting the channel name and sample rate, then configure the channel options:
* '''Output Mode''' Select either Frequency / Pulse Width Modulated (PWM) mode or analog output mode. '''MK1 only:''' to enable analog mode you also need to flip the hardware dip switch on the RaceCapture/Pro main board.
* '''Logging Mode''' Select either logging the frequency or the analog output voltage.
* '''Startup Duty Cycle''' The default duty cycle when the system starts up.
* '''Startup Period''' The default startup value for the pulse period. A larger number means individual pulses are spread further apart.

==CAN Bus==
[[Image:CAN_configuration.png|500px]]

Enable the CAN bus interface and baud rate using this screen.

==OBD II==
[[Image:OBDII_view.png|500px]]

You can create OBDII channels and query standard OBD2 PIDs over a compatible OBD2 CAN bus link.

'''Note''' OBD2 is only supported for ECUs that support the CAN bus protocol. The mandatory requirement for CAN support is 2008, but some vehicles implemented it earlier. Research your year/make/model to confirm.

To add an OBD2 channel, click the + sign at the bottom of this configuration page and select the channel you wish to log.

'''Important''' The sample rate you select is the '''logged''' sample rate, not the actual sample rate of the data. Due to the limitations of the OBDII protocol, channels are queried sequentially in a request/reply fashion. Therefore, as more channels are enabled the effective individual channel sample rate is reduced.

==Wireless==
[[Image:Wirelessconfig.png|500px]]

===Bluetooth===
You can enable Bluetooth via the Wireless settings. After enabling and saving the configuration to RaceCapture/Pro, following these steps:

# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Turn on Bluetooth on your tablet and pair with RaceCapture/Pro, password is 1234
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
# Swipe to the digital dash screen and you should see values changing, pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

===Telemetry===

For detailed setup instructions read our [[RaceCapturePro2_TelemetryQuickstart|Telemetry Quickstart]]

==Scripting==
[[Image:Luascripting.png|500px]]

LuaScripting for RaceCapture/Pro enables unlimited capabilities for your data logging and control requirements. Create a virtual/math channel or control an airbrake or intercooler sprayer. For full information about how to write Lua Scripts, read our [[RaceCapturePro_Lua_Scripting| Lua Scripting Guide]]

Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging!

RaceCapturePro Lua Scripting

2016-04-04T20:23:07Z

Rdoherty:

==Example Scripts and How-Tos==

'''[[RaceCapturePro Lua Scripting Examples|Lua Scripting Examples]]'''

==Lua Script Basics==

* All inputs and outputs are numbered starting at 0 (getGpio(0), setChannel(0), etc)
* All channel values must be numbers
* All virtual channel names must have no spaces (to be fixed in future revisions)

==General Input / Output (GPIO) Functions==

===getGpio( channel )===
Retrieves the state of the specified GPIO channel

*params
** channel: integer 0 - 2
*returns:
** state: 1 = channel is high, 0 = channel is low

When the channel is configured for input mode, a voltage high input (> 2 volts) will read as 1; a voltage low will read as 0. A disconnected channel will read as high due to the internal pullup resistor.

When the channel is configured as output, the channel reads 1 when the channel is activated (output transistor is connected to ground) and 0 when the channel is deactivated (pullup resistor is active)

===setGpio ( channel, state )===
Sets the state of the GPIO channel when the channel is configured for output mode.

*params
** channel: integer 0 - 2, state - 1 = output active; 0 = output inactive
*returns:
** none

When the state specified is 1, the output is active (transistor is connected to ground). When state is 0, transistor is disconnected, and pullup resistor is active.

When configured for input mode this function has no effect.

===getButton()===
Gets the state of the front panel pushbutton.

*params
** none
*returns
** state: 1 = pushbutton is depressed; 0 = pushbutton is not depressed

==PWM / Analog Output functions==

===setPwmDutyCycle( channel, dutyCyclePct )===
Sets the duty cycle of the specified PWM / Analog output channel to the specified duty cycle percentage

*params
** channel: PWM / Analog output channel 0 - 3
** dutyCyclePct: Percentage value of the duty cycle as a counting number 0 - 100
*returns
** none

===setPwmClockFreq( frequency )===
Sets the clock frequency of the PWM outputs

*params
** frequency: the frequency of the PWM clock, in Hz. Supported range is 320-40000 Hz
* returns
** none

===setAnalogOut( channel, voltage )===
Sets the output voltage of the specified PWM / Analog output channel to the specified period. A convenience function equivalent to setPwmDutyCycle that translates voltage to PWM percentage.

*params
** channel: PWM / Analog output channel 0 - 3
** voltage: the specified output voltage ( 0 - 5v)
** returns
* none

==Timer / RPM Sensor Functions==

===getTimerRpm(channel)===
Returns the current RPM of the specified timer input channel. Note, the timer channel configuration must be set to RPM mode.

*params
** channel: Timer channel 0 - 2
** returns: RPM value

===getTimerPeriodMs(channel)===
Returns the current duration of the full cycle pulse of the specified timer input channel, in milliseconds. Note the timer channel configuration must be set to Duration mode.

*params
** channel: Timer channel 0 - 3
** returns: millisecond value

===getTimerFreq(channel)===
Returns the current frequency present on the specified timer input channel, in Hz. Note the timer channel configuration must be set to Frequency Mode.

*params
** channel: Timer channel 0 - 3
** returns: Frequency in Hz

===getTimerRaw(channel)===
Returns the current raw timer value as measured on the specified timer input channel.

*params
** channel: Timer channel 0 - 3
** returns: Raw timer value between 0 - 65535



==Analog Sensor Functions==

===getAnalog(channel)===
Reads the scaled analog value for the specified analog input channel.
*params
** channel: Analog input channel 0 - 7
*** Note: channel 7 is internally dedicated to battery voltage.
** returns: Scaled / calculated value for the specified analog channel as defined in the channel scaling configuration

==Accelerometer / Yaw Sensor Functions==

===getImu(channel)===
Reads the specified IMU channel
* params
** channel (0 - 2 for accelerometer, 3 for yaw gyro sensor)
* returns
** The value scaled to G force, or degrees/sec depending on the channel selected

===getImuRaw(channel)===
Reads the raw value of the specified accelerometer or yaw channel
* params
** channel (0 - 2 for accelerometer, 3 for yaw gyro sensor)
* returns
** The raw accelerometer value

==GPS Sensor Functions==

===getGpsPos()===
Reads the current position as measured by the attached GPS module ''coming in firmware 2.0''
* params
** none
* returns
** Latitude: latitude in decimal degrees
** Longitude: longitude in decimal degress

===getGpsSpeed()===
Provides the current speed as measured by the attached GPS module
* params
** (none)
* returns
** The current speed in MPH

===getGpsQuality()===
Provides the current GPS quality indicator as indicated by the attached GPS module
* params
** (none)
* returns
** The current GPS quality indicator
** 0: No fix; 1: Fixed; 2: SPS Fix; 3: Differential Fix

===getGpsTime()===
Provides the current GPS time as indicated by the attached GPS module (in NMEA format) ''todo: document this''
* params
** (none)
* returns
** The current GPS time value

===getGpsDist()===
Provides the current GPS calculated distance from the beginning of the logging session, or from the start finish line, if configured.
* params
** (none)
* returns
** The distance, in Miles

===getGpsAltitude()===
Provides the current GPS calculated altitude from sea level in feet. The method will return 0 if there is no GPS lock.
* Added: v2.9.0
* Parameters: ''None''
* Returns: <altitude>

===getLapCount()===
Provides the current Lap Count as determined by the start/finish line configuration and measured by the attached GPS module.
* params
** (none)
* returns
** The number of laps detected since the logging session started

===getLapTime()===
Provides the last lap time as determined by the start/finish line configuration and measured by the attached GPS module.
* params
** (none)
* returns
** The last measured lap time in decimal minutes / seconds

===getGpsSec()===
Provides the number of seconds since midnight, as measured by the GPS module. ''todo: how does this relate to timezone? GMT or local?''
* params
** (none)
* returns
** number of seconds since midnight, as measured by the attached GPS module

===getAtStartFinish()===
Indicates if within the start finish line target as determined by the start/finish line configuration and measured by the attached GPS module.
* params
** (none)
* returns
** 1 if currently within the start/finish line target, 0 if outside

===getTimeDiff(time1, time2)===
Utility function to calculate the absolute difference between two time values, in seconds. ''todo: investigate the need for this function. may be eliminated in 1.2 firmware''
* params
** time1
** time2
* returns
** The absolute difference between the specified values

===getTimeSince(time)===
Utility function to calculate the time since midnight, in seconds. ''todo: investigate the need for this function. may be eliminated in 1.2 firmware''
* params
** time
* returns
** The number of seconds since midnight

==CAN Bus functions==

===initCAN(channel, baud )===
''available in firmware 2.0''
Initializes the CAN bus module. Normally this is done when RaceCapture/Pro powers on; use this function if you need to change the CAN baud rate on the fly.
* params
** channel: The CAN channel. 0 for the first channel, 1 for the 2nd, if supported on the hardware
** baud rate: Supported baud rates: 100000, 125000, 250000, 500000, 1000000
* returns
** 1 if successful, 0 if initialization fails, nil if parameters are incorrect

===txCAN(channel, id, isExtended, data, [timeout] )===
''available in firmware 2.0''
Transmit a CAN message.
* params
** channel: The CAN channel. 0 for the first channel, 1 for the 2nd, if supported on the hardware
** identifier: The Identifier value of the message, either in standard (11 bit) or extended (29 bit) format.
** isExtended: 0 for Standard (11 bit) Identifier or 1 for Extended (29 bit) Identifier.
** data: CAN message payload; array up to 8 elements long.
** timeout: (optional) specify a timeout for sending this message. if the transmit queue is full, will block for the specified milliseconds. Defaults to 100ms
* returns
** 1 if successful, 0 if failed, nil if parameters are incorrect

Example:
channel = 0
id = 1234
ext = 0
data = {11,22,33}
res = txCAN(channel, id, ext, data)

===rxCAN(channel, [timeout] )===
''available in firmware 2.0''
Receive a CAN message, if available.
* params
** channel: The CAN channel. 0 for the first channel, 1 for the 2nd, if supported on the hardware
** timeout (optional). read timeout in milliseconds. defaults to 100ms
* returns
** identifier: The Identifier value of the message, either in standard (11 bit) or extended (29 bit) format.
** isExtended: 0 for Standard (11 bit) Identifier or 1 for Extended (29 bit) Identifier.
** Data: CAN message payload; array up to 8 elements long.

If no CAN message was received, the function returns nil

Example:
id, ext, data = rxCAN(0, 100) --100ms timeout
if id ~= nil then
println("CAN rx: " ..id .." " ..data[1]) --print ID and first element of received message
end

===setCANfilter(channel, filterId, extended, filter, mask )===
''available in firmware 2.0''
Sets the specified CAN filter ID, to ignore messages with a particular address. Must use in combination with setCANMask() to set a complete filter and mask.
* params
** channel: The CAN channel. 0 for the first channel, 1 for the 2nd, if supported on the hardware
** filterId: The id of the filter. Up to 6 filters are supported on MK1, 15 per channel on MK2. Filter ids start at 0.
** extended: 0 for Standard (11 bit) Identifier or 1 for Extended (29 bit) Identifier.
** filter: Pattern value for CAN filter
** mask: the mask for the CAN filter
* returns
** 1 for success, 0 for fail, nil if parameters are incorrect

===readOBD2( PID )===
''available in firmware 2.0''
Reads an OBD2 PID and returns the calculated value. This is a convenience method wrapped around the built-in CAN functions.
* params
** The OBD2 PID to read. Supported PIDs (TBD documented)
* returns
** The calculated PID value, or nil if the OBD2 PID was invalid or could not be read (e.g. CAN receive message timeout)

==Logger Control Functions==

===onTick()===
* params:
** (none)
* returns:
** (none)

The onTick() function is the main loop where scripting activity takes place. By default it is called by RaceCapture/Pro every 1 second (1Hz). The rate can be adjusted using the setTickRate() function.

* '''Note''' - you should only define one onTick() function in your code. If multiple onTick() functions are defined, only the last defined onTick() function will be used.

Example:

function onTick()
println("Hello") --write something to the log
end

===setTickRate(rate)===
Sets the rate at which the onTick() function is called
* params
** rate: The rate the onTick() function is called, in Hz. Max tick rate is 30Hz.
* returns
** (none)

===startLogging()===
Begins a logging session
* params
** (none)
* returns
** (none)

===stopLogging()===
Stops the current logging session. If not logging, this function has no effect.
* params
** (none)
* returns
** (none)

===setLed( led, state )===
Sets the state of a front panel LED
* params
** led (1-3)
** state : 1 = on, 0 = off
* returns
** (none)

==Serial Port Communications==

These function calls allow reading / writing line oriented data from the built in serial ports.

===Port mappings===
0 = USB port<br/>
1 = GPS port<br/>
2 = Internal telemetry port (MK2 only)<br/>
3 = Wireless / Bluetooth port<br/>
4 = Auxiliary port<br/>

* '''Note''': We only recommend using ports 3 and 4 for connecting script to external devices. Ports 0 - 2 have been included for reference; using them may interfere with normal operations of the unit.

===initSer( port, baud, bits, parity, stopBits)===
Initializes the specified serial port

* params
** port: The port to initialize. (defaults to Auxiliary port)
** baud: The baud rate to set (defaults to 115200)
** bits: Number of bit in the message (8 or 7) (defaults to 8)
** parity: (1 = Even Parity, 2 = Odd Parity, 0 = No Parity) (defaults to No Parity)
** stopBits: number of stop bits (1 or 2) (defaults to 1)

* returns
** 1 if initialization succeeds, -1 if parameters are incorrect

===readCSer( port, [timeout])===
''Available since firmware 2.8.4''<br>
Read a character from the specified serial port

* params
** port: The port to read. (required)
** timeout - the read timeout, in ms.

* returns
** the character read, or nil if the timeout was reached

===readSer( port, [timeout])===
Read a line of data from the specified serial port. This command blocks until a newline ('\n') character is received on the port, or a timeout occurs.
* params
** port: Serial port 0 - 4
** timeout - the read timeout, in ms.
** returns: a line of serial data, or nil if the timeout was reached

===writeCSer( port, data )===
''Available since firmware 2.8.4''<br>
Writes the specified character to the serial port. The call will block until the character is written.
* params:
** port - the serial port to write
** char - the character to write.

* returns:
(no return values)

===writeSer( port, data )===
Writes a line of data to the specified serial port, appending a newline at the end. The call will block until all characters are written.
* params
** port: Serial port 0 - 4
** data: the data in string format

* returns:
(no return values)

==Logger Configuration Functions==

===flashLoggerCfg()===
Writes the current configuration in RAM to flash memory.
* params
** (none)
* returns
** (none)

===setPwmClockFreq( freq )===
Sets the clock frequency for all PWM channels
* params
** freq: The clock frequency ''todo: what units?''
* returns
** (none)

===getPwmClockFreq()===
Gets the PWM clock frequency controlling all PWM channels
* params
** (none)
* returns
** the PWM clock frequency ''todo: what units?''

===calibrateImuZero()===
Automatically Calibrates the accelerometer zero position.
* params
** (none)
* returns
** (none)

==Virtual Channels==

===addChannel( name, sampleRate, [precision], [min], [max], [units] )===
''available in firmware 2.0''
Adds a virtual channel. This virtual channel remains in memory during runtime; it is not persisted in the configuration. Up to 30 virtual channels can be created.
* params
** name: The name of the channel, up to 10 characters long. We recommend using an existing System channel name as defined by the app when possible.
** sampleRate: A supported sample rate (1,10,25,50,100,200Hz)
** precision: (optional) the numerical precision (number of decimal places) used when logging to SD and telemetry. Defaults to 2
** min: (optional) The min expected value for this channel. Defaults to 0
** max: (optional) The max expected value for this channel. Defaults to 1000
** units: (optional) The units label for this channel. Defaults to empty string / none

* returns
** the id of the new virtual channel, or NIL if the virtual channel could not be created. Use this id for setting the channel value (see setChannel() )

===getChannel( <Channel ID | Channel Name> )===
* Available: v2.9.0
* Parameters
** Channel ID (number) - The channel id value as provided by the ''addChannel'' method.
** Channel Name (string) - The name of the channel as provided to the ''addChannel'' method. Using the Channel ID method is preferred and is faster.
* Returns
** (number) The value of the channel.
* Examples:
** <code> val = getChannel(1) </code>
** <code> val = getChannel("foo") </code>

===setChannel( channelId, value )===
''available in firmware 2.0''
Updates the value of a previously created virtual channel.
* params
** channelId: the ID of the channel provided by addChannel()
** value: the new value to set for the virtual channel

Example:

id = addChannel("EGT", 1)

function onTick()
temp = getAnalog(0) --read analog channel 0
temp = temp * 1000
setChannel(id, temp) --sets the virtual channel value
end

==Time Info==
These methods get you information about dates and time. This is useful in controlling script behavior or just knowing what time it is.

===getUptime()===
''Available since firmware 2.8.4''<br>
Returns the number of miliseconds since the device last started. This is always available and is the most consistent way to time things in LUA script on RaceCapture.

* Returns
** Number of milliseconds since CPU boot.

===getDateTime()===
''Available since firmware 2.8.4''<br>
Returns date and time info to the best of the systems ability. Only available after GPS lock has been established. Will return epoch time (Jan 1, 1970 00:00:000) if time is not available.

* Returns: A list of date and time information in the following order:
** Year
** Month
** Day
** Hour
** Second
** Millisecond

RaceCapturePro2 logfile reference

2016-03-15T22:18:01Z

Rdoherty: /* Troubleshoothing */

=Log file format=

RaceCapture/Pro logs data onto SD cards using a sparsely populated comma separated value (CSV) format.

==File naming==
RaceCapture/Pro names files in an ascending order in a pattern of RC_XX.LOG where XX represents a number. When a new log file is created, RaceCapture/Pro will create the next log file where XX is the next available number, preventing duplicate or overwritten log files.

==Header==
The log file header defines the information present in the data segment of the log file.

===Format===
Each sampled channel is represented by a comma separated column. The column in the file is defined as a data structure with the following format:

* Channel Name
* Units Label
* Min value
* Max value
* Sample Rate (Hz)

The data structure is defined as follows:
"<Name>"|"<Units>"|<Min value>|<Max Value>|<Sample Rate>

Example:

"Battery"|"Volts"|0.0|50.0

Each data structure describing a segment is separated with a comma.

===Special Columns===

The following columns are system defined and will appear on every log file sample, regardless of the indicated sample rate.

====Interval====
Interval represents the milliseconds uptime of the system, and will reflect the number of milliseconds elapsed between samples.

====Utc====
Utc is sourced from GPS data and will be a valid, non zero value representing Utc time in milliseconds. When there is no GPS lock, UTC will be zero.

==Data segment==

Within the data segment, sample values appear at the frequency defined in the header file. Channels logged at lower sample rates will appear sparsely within the file, with empty values appearing in the space between samples.

==Example==
<pre>
"Interval"|"ms"|0|0|1,"Utc"|"ms"|0|0|1,"Battery"|"Volts"|0.0|50.0|1,"AccelX"|"G"|0.0|0.0|25,"AccelY"|"G"|0.0|0.0|25,"AccelZ"|"G"|0.0|0.0|25,"Yaw"|"Deg/Sec"|0.0|0.0|25,"Pitch"|"$
402,0,,-0.02,-0.03,0.93,0.5,-6.2,-0.2,,,,,,,,,,,,,,,,,,,,
442,0,,-0.02,-0.03,0.95,0.2,-6.0,-0.3,0,,,979,26,0.0,0.0,0.0,0.0,0.0,0,0,0.0,0,0.0,-1,0.0,0.0,0.0,0
482,0,,-0.01,-0.03,0.97,0.1,-5.5,-0.2,,,,,,,,,,,,,,,,,,,,
522,0,,-0.01,-0.03,0.99,0.0,-5.0,-0.2,,,,,,,,,,,,,,,,,,,,
542,0,,,,,,,,0,,,986,26,0.0,0.0,0.0,0.0,0.0,0,0,0.0,0,0.0,-1,0.0,,0.0,0

</pre>

==Troubleshooting==

It's best to use a freshly formatted FAT16 or FAT32 file. If you log a file and the data looks scrambled, encrypted, do a fresh re-format and try again.

RaceCapturePro2 QuickStart

2016-02-29T18:49:59Z

Rdoherty: /* Prerequisites */

__FORCETOC__

== Prerequisites ==
* [https://www.race-capture.com/software/ Download and install] the latest RaceCapture App
Windows 10:
* No drivers are needed for Windows 10. Windows will automatically detect RaceCapture/Pro, and it will appear as a '''USB Serial''' device under Device Manager.

Windows XP, 7, 8:
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 users''' - These drivers are unsigned. You will need to disable the driver signing requirement for Windows 8, or upgrade to Windows 10. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]
*** [http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ Win8 64bit unsigned driver instructions]
* Plug RaceCapture/Pro in to the computer.
* If prompted to install a driver, direct Windows to the folder where you unzipped the RaceCapture/Pro drivers.
* If not prompted, manually update driver:
** Open Windows Device Manager and find the '''Ports (COM and LPT)''' section. RaceCapture/Pro should be listed there, possibly with a yellow (!) over the icon.
** Right click and select 'Update Driver'.
** Follow the instructions and direct Windows to the folder where you unzipped the RaceCapture/Pro drivers.

== Quick Start ==

Watch our software installation video here: https://www.youtube.com/watch?v=oqveE2C1vo0

# Attach GPS and Bluetooth module (if purchased) to RaceCapture/Pro
# Plug in the supplied USB cable to RaceCapture/Pro and your computer.
# When prompted for drivers, select them from the zip file you unzipped previously.
## If not prompted or Windows does not ask you to locate drivers, open Device Manager, find RaceCapture/Pro (usually under 'Other devices'), right click and select 'Update Driver' software. Then select the folder containing the unzipped drivers you downloaded previously.
# Confirm you really want to install the drivers

==Running the Application==
# Open the RaceCapture application.
## You should see 'Reading Configuration' at the top of the window once the app detects RaceCapture/Pro.
# Click on 'Dashboard'
# Click on the bottom right arrow three times, which will display the digital dash. You should see the Utc and Interval channels changing, which means data is being transmitted over USB.

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

## '''Protip:''' Pick up the RaceCapture/Pro unit, move it around and observe changes from the internal accelerometer and gyro sensors!

# You have now setup the RaceCapture app!

== Selecting your favorite race tracks==
RaceCapture/Pro can auto-detect and configure your favorite race tracks as soon as GPS lock is obtained.

# After connecting the RaceCapture app and verifying connectivity, navigate to the configuration view.
# Select the Race Tracks from the menu on the left.
# Search and select the race tracks you will be typically attending.
# Once the tracks have been selected, write the updated configuration using the [[Image:rc_appwrite_config.png]] button in the lower left.

When you arrive at the track and RaceCapture is powered up, it will automatically detect and configure the track's start/finish line and any available sectors.

ProTip: Periodically click the update button [[Image:update_from_cloud.png]] to pull down the latest set of race track configurations.

[[Image:RA_automatic_track_detection.png|800px]]

== Setting up Bluetooth ==
===Enabling Bluetooth in firmware settings===
* Complete the Quick Start steps above, leaving RaceCapture/Pro connected to your computer
* Connect the Bluetooth module to the inner of the two RaceCapture/Pro ports on the same side the USB cable connects to
* Open the Race Capture app
* Click on the top left 'Menu' button
* Click on 'Configuration'
* Click on 'Wireless' in the list of options on the left
* Click the toggle to the right of 'Bluetooth'
<br> [[File:RC_app_wireless_config.jpg|800px]]
* Click the 'Write Config' button on the bottom left (down array pointing to a RaceCapture/Pro)

===Set up Android tablet/phone===

App Download:
* Google Play Store [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Download]
* Amazon App Store [http://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1446478866&sr=1-1 Download]

==Requirements==
For best performance, we recommend the following minimum specification:
* Android 4.4 and higher
* Quad core 1.6 GHz processor
* 2 GB RAM, 8 GB flash
* 1024x600 resolution, IPS display
* 7" or 10" screen

Recommended Brands for tablets:
* Samsung
** Samsung Galaxy Tab S with AMOLED screen (best performance)
** Samsung Galaxy Tab Pro 8.4 (good alternative)
** Samsung Galaxy Tab 4 8.0 inch T337 - good choice with 4G LTE
* Google Nexus
* LG
* Lenovo
* [http://www.amazon.com/dp/B00TSUGXKE Amazon Fire Tablet] $49.95 edition

==Touch screen operation with gloves==
We recommend [http://http://www.amazon.com/AnyGlove-TM-Synthetic-Touchscreen-Compatible/dp/B00AB3EVOW AnyGlove] to make your racing gloves touch screen compatible.

==Bluetooth pairing==
# Go into the Android settings and pair your device with the RaceCapture/Pro Bluetooth module
## Ensure Bluetooth is turned on in the Android device settings.
## Ensure the RaceCapture/Pro Bluetooth module is powered on (green light is flashing)
## Default password is 1234
# Install the Race Capture app on your Android device:
* Google Play Store [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Download]
* Amazon App Store [http://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1446478866&sr=1-1 Download]

# Open the RaceCapture app. The RaceCapture app will search for the RaceCapturePro device

===Verify connectivity===
# Select the dashboard screen and switch to the raw channels view - you should see values updating in real-time.

<br> [[File:Dash.png|800px]]

===Troubleshooting Bluetooth connection issues===
* Ensure RaceCapture/Pro is powered up and the Bluetooth module is plugged in to the inner RJ11 port, located to the right of the front panel push-button
* Ensure Bluetooth is enabled in the wireless settings of the RaceCapture/Pro configuration
** Note, you will need to connect via USB to verify this setting
* Ensure Bluetooth is enabled under the Android Settings
** On some tablets with a marginal or unstable Bluetooth support, a disable/re-enable of Bluetooth may help
* Try un-pairing and re-pairing the RaceCapture/Pro Bluetooth device
* Try re-starting the Android device

==Basic Logging of Data==
* Insert a micro SD card into SD card slot on the front face of the unit.
** Use a 32GB card or smaller
* Press the button on the front of the panel. You will see the Logging LED flash
* When you are finished logging, press the button again. THe Logging LED will stop flashing.
* Remove the card. You will find your log file on the SD card.
** The filename will end in .log
** The logfile is in plain CSV data format.

===Automatic logging control===
You can use the on-board Lua scripting to [[RaceCapturePro_Lua_Scripting_Examples#Automatic_logging_control|Automate Logging]] behavior using speed, RPM or other logic.

Main Page

2016-01-03T00:03:54Z

Rdoherty:

__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==
<center>
<table>
<tr>
<td align="center">
[[Image:RaceCapturePro_logo_small.png|link=RaceCapturePro]]
<br>[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapturePro]]
<br>

<h2 style="text-decoration:underline;font-weight:bold;">[[RaceCapturePro|Race Capture Pro]]</h2>
'''Data Acquisition and Control'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]
</td>
<td align="center">
[[Image:mjlj_small_logo.png|link=Megajolt Lite Jr.]]
<br><br>[[Image:MegajoltE_map.jpg|300px|link=Megajolt Lite Jr.]]
<br><h2 style="text-decoration:underline;font-weight:bold;">[[Megajolt Lite Jr.|Megajolt Lite Jr.]]</h2>
'''Programmable Ignition Controller'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/megajolte/]]

</td>
</tr>
</table>
</center>

==Other things we're working on==

===DIY Racing Helmet Microphone===
*[[Helmet_mic|Build a helmet mic on the cheap!]]

===Tweeting Race Car===
[[Tweeting_Race_Car|Our race cars tweet autonomously while on the race track!]]

===Ignition Driver Modules===
[[IgnitionDrivers|Ignition driver boards for Coil On Plug and other applications]]

===Tachometer Adapter===
[[TachAdapter|Tachometer Adapter: Adapts Tachometer to multiple coil packs]]

===Megajolt2 Roadmap===
Info on our next generation [[Megajolt2|Megajolt2]] platform- testing in 2010!

===Autosport Labs R&D Platforms===
[[Research_and_Development_Platforms|Meet the test platforms we inflict our projects upon!]]
[[Image:240z_left_rear_3quarter_400px.jpg|right]]

===Lighting===
*[[Dual_LED_cluster|Dual LED Cluster]]
*[[Sequential_shift_light_array|Sequential Shift Light Array]]

===CPU Module===
The Autosport Labs CPU Module will be the heart of our future projects. This piece combines DIY friendliness with high speed high performance 32 bit processing power.
*[[CPU_Module|CPU Module]]

===Other Things===

*[[Handy_hints|Helpful Engineering Resources]]

Main Page

2015-12-02T23:53:52Z

Rdoherty:

<h2 style="text-decoration:underline;font-weight:bold;">[https://www.kickstarter.com/projects/autosportlabs/racecapture-and-podium-race-it-share-it-prove-it RaceCapture is now available on Kickstarter!]</h2>
<br/>
[[Image:Rct-hero.jpg|link=https://www.kickstarter.com/projects/autosportlabs/racecapture-and-podium-race-it-share-it-prove-it]]

__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==
<center>
<table>
<tr>
<td align="center">
[[Image:RaceCapturePro_logo_small.png|link=RaceCapturePro]]
<br>[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapturePro]]
<br>

<h2 style="text-decoration:underline;font-weight:bold;">[[RaceCapturePro|Race Capture Pro]]</h2>
'''Data Acquisition and Control'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]
</td>
<td align="center">
[[Image:mjlj_small_logo.png|link=Megajolt Lite Jr.]]
<br><br>[[Image:MegajoltE_map.jpg|300px|link=Megajolt Lite Jr.]]
<br><h2 style="text-decoration:underline;font-weight:bold;">[[Megajolt Lite Jr.|Megajolt Lite Jr.]]</h2>
'''Programmable Ignition Controller'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/megajolte/]]

</td>
</tr>
</table>
</center>

==Other things we're working on==

===DIY Racing Helmet Microphone===
*[[Helmet_mic|Build a helmet mic on the cheap!]]

===Tweeting Race Car===
[[Tweeting_Race_Car|Our race cars tweet autonomously while on the race track!]]

===Ignition Driver Modules===
[[IgnitionDrivers|Ignition driver boards for Coil On Plug and other applications]]

===Tachometer Adapter===
[[TachAdapter|Tachometer Adapter: Adapts Tachometer to multiple coil packs]]

===Megajolt2 Roadmap===
Info on our next generation [[Megajolt2|Megajolt2]] platform- testing in 2010!

===Autosport Labs R&D Platforms===
[[Research_and_Development_Platforms|Meet the test platforms we inflict our projects upon!]]
[[Image:240z_left_rear_3quarter_400px.jpg|right]]

===Lighting===
*[[Dual_LED_cluster|Dual LED Cluster]]
*[[Sequential_shift_light_array|Sequential Shift Light Array]]

===CPU Module===
The Autosport Labs CPU Module will be the heart of our future projects. This piece combines DIY friendliness with high speed high performance 32 bit processing power.
*[[CPU_Module|CPU Module]]

===Other Things===

*[[Handy_hints|Helpful Engineering Resources]]

Main Page

2015-12-02T23:48:37Z

Rdoherty:

<h2 style="text-decoration:underline;font-weight:bold;">[https://www.kickstarter.com/projects/autosportlabs/racecapture-and-podium-race-it-share-it-prove-it RaceCapture is now available on Kickstarter!]</h2>
<br/>
[[Image:Rct-hero.jpg]]

__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==
<center>
<table>
<tr>
<td align="center">
[[Image:RaceCapturePro_logo_small.png|link=RaceCapturePro]]
<br>[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapturePro]]
<br>

<h2 style="text-decoration:underline;font-weight:bold;">[[RaceCapturePro|Race Capture Pro]]</h2>
'''Data Acquisition and Control'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]
</td>
<td align="center">
[[Image:mjlj_small_logo.png|link=Megajolt Lite Jr.]]
<br><br>[[Image:MegajoltE_map.jpg|300px|link=Megajolt Lite Jr.]]
<br><h2 style="text-decoration:underline;font-weight:bold;">[[Megajolt Lite Jr.|Megajolt Lite Jr.]]</h2>
'''Programmable Ignition Controller'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/megajolte/]]

</td>
</tr>
</table>
</center>

==Other things we're working on==

===DIY Racing Helmet Microphone===
*[[Helmet_mic|Build a helmet mic on the cheap!]]

===Tweeting Race Car===
[[Tweeting_Race_Car|Our race cars tweet autonomously while on the race track!]]

===Ignition Driver Modules===
[[IgnitionDrivers|Ignition driver boards for Coil On Plug and other applications]]

===Tachometer Adapter===
[[TachAdapter|Tachometer Adapter: Adapts Tachometer to multiple coil packs]]

===Megajolt2 Roadmap===
Info on our next generation [[Megajolt2|Megajolt2]] platform- testing in 2010!

===Autosport Labs R&D Platforms===
[[Research_and_Development_Platforms|Meet the test platforms we inflict our projects upon!]]
[[Image:240z_left_rear_3quarter_400px.jpg|right]]

===Lighting===
*[[Dual_LED_cluster|Dual LED Cluster]]
*[[Sequential_shift_light_array|Sequential Shift Light Array]]

===CPU Module===
The Autosport Labs CPU Module will be the heart of our future projects. This piece combines DIY friendliness with high speed high performance 32 bit processing power.
*[[CPU_Module|CPU Module]]

===Other Things===

*[[Handy_hints|Helpful Engineering Resources]]

File:Rct-hero.jpg

2015-12-02T23:44:18Z

Rdoherty:

RaceCapturePro2 QuickStart

2015-12-01T17:31:32Z

Rdoherty:

__FORCETOC__

== Prerequisites ==
* [https://race-capture.com/software/54aacf81183b3a6722000001 Download and install] the latest RaceCapture App
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 or 10 users''' - These drivers are unsigned. We are working on creating a signed driver set, but in the meantime you will need to disable the driver signing requirement for Windows 8/10. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]
*** [http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ Win8 64bit unsigned driver instructions]

== Quick Start ==

Watch our software installation video here: https://www.youtube.com/watch?v=oqveE2C1vo0

# Attach GPS and Bluetooth module (if purchased) to RaceCapture/Pro
# Plug in the supplied USB cable to RaceCapture/Pro and your computer.
# When prompted for drivers, select them from the zip file you unzipped previously.
## If not prompted or Windows does not ask you to locate drivers, open Device Manager, find RaceCapture/Pro (usually under 'Other devices'), right click and select 'Update Driver' software. Then select the folder containing the unzipped drivers you downloaded previously.
# Confirm you really want to install the drivers

==Running the Application==
# Open the RaceCapture application.
## You should see 'Reading Configuration' at the top of the window once the app detects RaceCapture/Pro.
# Click on 'Dashboard'
# Click on the bottom right arrow three times, which will display the digital dash. You should see the Utc and Interval channels changing, which means data is being transmitted over USB.

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

## '''Protip:''' Pick up the RaceCapture/Pro unit, move it around and observe changes from the internal accelerometer and gyro sensors!

# You have now setup the RaceCapture app!

== Selecting your favorite race tracks==
RaceCapture/Pro can auto-detect and configure your favorite race tracks as soon as GPS lock is obtained.

# After connecting the RaceCapture app and verifying connectivity, navigate to the configuration view.
# Select the Race Tracks from the menu on the left.
# Search and select the race tracks you will be typically attending.
# Once the tracks have been selected, write the updated configuration using the [[Image:rc_appwrite_config.png]] button in the lower left.

When you arrive at the track and RaceCapture is powered up, it will automatically detect and configure the track's start/finish line and any available sectors.

ProTip: Periodically click the update button [[Image:update_from_cloud.png]] to pull down the latest set of race track configurations.

[[Image:RA_automatic_track_detection.png|800px]]

== Setting up Bluetooth ==
===Enabling Bluetooth in firmware settings===
* Complete the Quick Start steps above, leaving RaceCapture/Pro connected to your computer
* Connect the Bluetooth module to the inner of the two RaceCapture/Pro ports on the same side the USB cable connects to
* Open the Race Capture app
* Click on the top left 'Menu' button
* Click on 'Configuration'
* Click on 'Wireless' in the list of options on the left
* Click the toggle to the right of 'Bluetooth'
<br> [[File:RC_app_wireless_config.jpg|800px]]
* Click the 'Write Config' button on the bottom left (down array pointing to a RaceCapture/Pro)

===Set up Android tablet/phone===

App Download:
* Google Play Store [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Download]
* Amazon App Store [http://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1446478866&sr=1-1 Download]

==Requirements==
For best performance, we recommend the following minimum specification:
* Android 4.4 and higher
* Quad core 1.6 GHz processor
* 2 GB RAM, 8 GB flash
* 1024x600 resolution, IPS display
* 7" or 10" screen

Recommended Brands for tablets:
* Samsung
** Samsung Galaxy Tab S with AMOLED screen (best performance)
** Samsung Galaxy Tab Pro 8.4 (good alternative)
** Samsung Galaxy Tab 4 8.0 inch T337 - good choice with 4G LTE
* Google Nexus
* LG
* Lenovo
* [http://www.amazon.com/dp/B00TSUGXKE Amazon Fire Tablet] $49.95 edition

==Touch screen operation with gloves==
We recommend [http://http://www.amazon.com/AnyGlove-TM-Synthetic-Touchscreen-Compatible/dp/B00AB3EVOW AnyGlove] to make your racing gloves touch screen compatible.

==Bluetooth pairing==
# Go into the Android settings and pair your device with the RaceCapture/Pro Bluetooth module
## Ensure Bluetooth is turned on in the Android device settings.
## Ensure the RaceCapture/Pro Bluetooth module is powered on (green light is flashing)
## Default password is 1234
# Install the Race Capture app on your Android device:
* Google Play Store [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Download]
* Amazon App Store [http://www.amazon.com/Autosport-Labs-Race-Capture/dp/B016ZJM7GE/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1446478866&sr=1-1 Download]

# Open the RaceCapture app. The RaceCapture app will search for the RaceCapturePro device

===Verify connectivity===
# Select the dashboard screen and switch to the raw channels view - you should see values updating in real-time.

<br> [[File:Dash.png|800px]]

===Troubleshooting Bluetooth connection issues===
* Ensure RaceCapture/Pro is powered up and the Bluetooth module is plugged in to the inner RJ11 port, located to the right of the front panel push-button
* Ensure Bluetooth is enabled in the wireless settings of the RaceCapture/Pro configuration
** Note, you will need to connect via USB to verify this setting
* Ensure Bluetooth is enabled under the Android Settings
** On some tablets with a marginal or unstable Bluetooth support, a disable/re-enable of Bluetooth may help
* Try un-pairing and re-pairing the RaceCapture/Pro Bluetooth device
* Try re-starting the Android device

==Basic Logging of Data==
* Insert a micro SD card into SD card slot on the front face of the unit.
** Use a 32GB card or smaller
* Press the button on the front of the panel. You will see the Logging LED flash
* When you are finished logging, press the button again. THe Logging LED will stop flashing.
* Remove the card. You will find your log file on the SD card.
** The filename will end in .log
** The logfile is in plain CSV data format.

===Automatic logging control===
You can use the on-board Lua scripting to [[RaceCapturePro_Lua_Scripting_Examples#Automatic_logging_control|Automate Logging]] behavior using speed, RPM or other logic.

RaceCapturePro Analysis

2015-11-25T04:53:42Z

Rdoherty: /* Upload your datalog for viewing online */

==Upload your datalog for viewing online==

If you have data logged to an SD card you can upload the data for viewing online.

[[Image:log-file-upload.jpg]]

These are the same tools you get when streaming data live; perfect for analyzing data when you're out of cellular coverage.

===Steps to upload===
* [https://www.race-capture.com/home Create an event] on race-capture.com
* Add a device to the event.
* On this page, select the log file you wish to upload.

Once uploaded, your data will be processed and within a few minutes your data will appear. You can add more than one file by repeating the process.

From there you can share and analyze from anywhere in the world using just a web browser.
==== Uploading more than one log file ====

* Click on the Edit icon next to your car at an event:
[[Image:Upload again.jpg|300px]]
* Select the log file
[[Image:log-file-upload.jpg]]
* Click 'Update event device information'

===Log file requirements===

* The analysis software requires laps to be present in the data, so you need to be at a race track where you have a track configuration selected, or, you've manually set a start/finish line.

RaceCapturePro Analysis

2015-11-25T04:52:05Z

Rdoherty: /* Upload your datalog for viewing online */

==Upload your datalog for viewing online==

If you have data logged to an SD card you can upload the data for viewing online.

[[Image:log-file-upload.jpg]]

These are the same tools you get when streaming data live; perfect for analyzing data when you're out of cellular coverage.

===Steps to upload===
* [https://www.race-capture.com/home Create an event] on race-capture.com
* Add a device to the event.
* On this page, select the log file you wish to upload.

Once uploaded, your data will be processed and within a few minutes your data will appear. You can add more than one file by repeating the process.

From there you can share and analyze from anywhere in the world using just a web browser.
==== Uploading more than one log file ====

* Click on the Edit icon next to your car at an event:
[[Image:Upload again.jpg]]
* Select the log file
[[Image:log-file-upload.jpg]]
* Click 'Update event device information'

===Log file requirements===

* The analysis software requires laps to be present in the data, so you need to be at a race track where you have a track configuration selected, or, you've manually set a start/finish line.

RaceCapturePro Analysis

2015-11-25T04:50:54Z

Rdoherty: /* Steps to upload */

==Upload your datalog for viewing online==

If you have data logged to an SD card you can upload the data for viewing online.

[[Image:log-file-upload.jpg]]

These are the same tools you get when streaming data live; perfect for analyzing data when you're out of cellular coverage.

===Steps to upload===
* [https://www.race-capture.com/home Create an event] on race-capture.com
* Add a device to the event.
* On this page, select the log file you wish to upload.

Once uploaded, your data will be processed and within a few minutes your data will appear. You can add more than one file by repeating the process.

From there you can share and analyze from anywhere in the world using just a web browser.
==== Uploading more than one log file ====

* Click on the Edit icon next to your car at an event:
[File:Upload again.jpg]

===Log file requirements===

* The analysis software requires laps to be present in the data, so you need to be at a race track where you have a track configuration selected, or, you've manually set a start/finish line.

File:Upload again.jpg

2015-11-25T04:50:07Z

Rdoherty:

RaceCapturePro2 Hardware Install

2015-11-24T18:24:31Z

Rdoherty: /* Sensors */

==Connections==

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

===Power Connection===
Connect RaceCapture/Pro to a power source between 9 and 24V. To fully support all devices and outputs, provide at least a 5A fused connection.

==Sensors==
'''Also see the [[RaceCapturePro_Sensors|Comprehensive Sensor installation guide]]'''

===Analog Inputs 1-7===

====Specifications====
* RaceCapture/Pro has 8 analog inputs; the 8th input is wired internally to measuring battery voltage.
* Analog input range is 0 - 5v
* Input Impedance: 15K ohm

====Active Sensors/Signals====
The Analog Input Channels accept a 0-5v input signal (protected up to 40V). Connect the input from a sensor to the appropriate connection of the terminal block.
<center>[[Image:active_sensor_connection.png]]</center>

====Resistive sensor====
When connecting resistive style sensors, like many temperature and pressure sensors, one terminal of the sensor is connected to ground, and the other is connected to the Analog input, with a pullup resistor connected to the +5V Voltage Reference on the terminal block. A 2.2K resistor is recommended for most applications.
<center>[[Image:temp_sensor_connection.png]]</center>

===5V Voltage Reference===
This output provides a 5V reference to be used with the Analog Inputs. Up to 50mA is provided to supply power to active sensors, pull-up resistors and other purposes. This reference output is protected against short-circuits with an auto-resetting fuse. If the fuse is active, a low or zero voltage reading may be observed on this port. To verify an over-current situation, test the voltage on the port without any load connected.

===Analog/Frequency Outputs 1 - 4===
Depending on configuration, these outputs provide a settable 0-5v analog output voltage, or frequency output where the pulse-width and frequency can be set. These outputs can supply 50mA each.

===General Input/Output Channels 1 - 3===
Depending on configuration, these channels can accept either a digital input, or provide an output to control external devices.
* When configured for '''input''', the channel accepts a 0-5v input (protected up to 45V). Each input channel has a built-in 10K pullup resistor connected to 5V.
* When configured for '''output''', the channel provides an open-drain output that can drive 1A and is thermal / over-current protected with inductive load clamping. When the output is deactivated, a 1K ohm pull-up to +5v is present.

===Frequency/Pulse Input 1 - 3===
These input channels can be used to time the duration between digital pulses for purposes of measuring RPM, shaft speed, and so on. The input accepts 0-5V (protected up to 40V). Each input has a built-in 10K pullup resistor connected to 5V.

====TACH SIGNAL NOTES====

'''Do not connect the old-style tachometer signal directly to RaceCapture/Pro.''' This signal is typically sourced from a wire that connects directly to the (-) post of the ignition coil. These signals are 400-500v peak and can damage your RaceCapture/Pro hardware.

'''[[CoilX CoilX Sensor Module]]'''

[[Image:coilx_wiring_sm.jpg|300px]]

You can use the CoilX sensor module to safely interface this high voltage RPM signal. See the [[CoilX|CoilX page]] for more information.

Newer style tach signals sourced from the ECU will likely provide a clean square wave signal and can be connected directly to this input.

If unsure, observe the signal with an oscilloscope and/or consult technical documentation of your vehicle.

===LED Indicators===

[[File:Leds.jpg]]

* Power LED
Indicates the unit is powered up (via 12v supply or USB)
* LED1
Indicates GPS Activity. Slow flash (1Hz) indicates GPS is actively acquiring. Fast flash (10 times per second) indicates GPS is locked on to satellites.
* LED2
Indicates SD card Logging Activity. The flash rate matches the channel with the highest configured logging rate.
* LED3
Indicates error status when writing to SD Card (future error conditions will be indicated by this LED)

===Pushbutton===

[[File:Pushbutton.jpg]]

Press to manually start / stop a logging session. Note this may be overridden by any on-board scripts that may automatically start or stop logging.

===Communication Ports===

[[File:Expansionports.jpg]]

The communication ports a standard RS232 serial connection with power (up to 5v at 1.5A)
* Port 1
Used for BT module
* Port 2
Serial I/O

==Installation==
==Mounting orientation and position==

The ideal mounting position for RaceCapture/Pro is mounted flat (right side up or upside down), in the exact center of the vehicle. This gives the best effect from the built in Gyroscope, which measures Yaw (understeer / oversteer).

===Shock isolation mounting===
In very harsh environments you may want to mount RaceCapture/Pro using rubber isolators. [http://www.karman.com/selectvibro.cfm Info on isolation mounts]

===Default Accelerometer Configuration===
The default accelerometer configuration assumes RaceCapture/Pro is mounted flat, right side up with the green terminal block pointed towards the front of the vehicle. Other orientations are supported by changing the settings in the Software. See the [[RaceCapturePro_SoftwareOperation#Accelerometer_Inputs|Operation Guide]] for more information.

RaceCapturePro2 Hardware Install

2015-11-24T18:23:17Z

Rdoherty: Created page with "==Connections== Image:RaceCapture-Pro MK2 quick reference sheet.jpg ===Power Connection=== Connect RaceCapture/Pro to a power source between 9 and 24V. To fully support..."

==Connections==

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

===Power Connection===
Connect RaceCapture/Pro to a power source between 9 and 24V. To fully support all devices and outputs, provide at least a 5A fused connection.

==Sensors==
'''Also see the [[RaceCapturePro_Sensors|Comprehensive Sensor installation guide]]'''

===Analog Inputs 1-7===

====Specifications====
* RaceCapture/Pro has 8 analog inputs; the 8th input is wired internally to measuring battery voltage.
* Analog input range is 0 - 5v
* Input Impedance: 15K ohm

====Active Sensors/Signals====
The Analog Input Channels accept a 0-5v input signal (protected up to 40V). Connect the input from a sensor to the appropriate connection of the terminal block.
<center>[[Image:active_sensor_connection.png]]</center>

====Resistive sensor====
When connecting resistive style sensors, like many temperature and pressure sensors, one terminal of the sensor is connected to ground, and the other is connected to the Analog input, with a pullup resistor connected to the +5V Voltage Reference on the terminal block. A 2.2K resistor is recommended for most applications.
<center>[[Image:temp_sensor_connection.png]]</center>

===5V Voltage Reference===
This output provides a 5V reference to be used with the Analog Inputs. Up to 50mA is provided to supply power to active sensors, pull-up resistors and other purposes. This reference output is protected against short-circuits with an auto-resetting fuse. If the fuse is active, a low or zero voltage reading may be observed on this port. To verify an over-current situation, test the voltage on the port without any load connected.

===Analog/Frequency Outputs 1 - 4===
Depending on configuration, these outputs provide a settable 0-5v analog output voltage, or frequency output where the pulse-width and frequency can be set. These outputs can supply 50mA each.

===General Input/Output Channels 1 - 3===
Depending on configuration, these channels can accept either a digital input, or provide an output to control external devices.
* When configured for '''input''', the channel accepts a 0-5v input (protected up to 45V). Each input channel has a built-in 10K pullup resistor connected to 5V.
* When configured for '''output''', the channel provides an open-drain output that can drive 1A and is thermal / over-current protected with inductive load clamping. When the output is deactivated, a 1K ohm pull-up to +5v is present.

===Frequency/Pulse Input 1 - 3===
These input channels can be used to time the duration between digital pulses for purposes of measuring RPM, shaft speed, and so on. The input accepts 0-5V (protected up to 40V). Each input has a built-in 10K pullup resistor connected to 5V.

====TACH SIGNAL NOTES====

'''Do not connect the old-style tachometer signal directly to RaceCapture/Pro.''' This signal is typically sourced from a wire that connects directly to the (-) post of the ignition coil. These signals are 400-500v peak and can damage your RaceCapture/Pro hardware.

'''[[CoilX CoilX Sensor Module]]'''

[[Image:coilx_wiring_sm.jpg|300px]]

You can use the CoilX sensor module to safely interface this high voltage RPM signal. See the [[CoilX|CoilX page]] for more information.

Newer style tach signals sourced from the ECU will likely provide a clean square wave signal and can be connected directly to this input.

If unsure, observe the signal with an oscilloscope and/or consult technical documentation of your vehicle.

===SD Card Slot===

[[File:Sdcard.jpg]]

The SD card slot is used to store datalogging sessions. 512MB to 32GB cards are supported.

===USB Port===

[[File:Usbport.jpg]]

Used for configuring RaceCapture Pro via [[RaceCapturePro_SoftwareOperation Race Analyzer Software]]

===LED Indicators===

[[File:Leds.jpg]]

* Power LED
Indicates the unit is powered up (via 12v supply or USB)
* LED1
Indicates GPS Activity. Slow flash (1Hz) indicates GPS is actively acquiring. Fast flash (10 times per second) indicates GPS is locked on to satellites.
* LED2
Indicates SD card Logging Activity. The flash rate matches the channel with the highest configured logging rate.
* LED3
Indicates error status when writing to SD Card (future error conditions will be indicated by this LED)

===Pushbutton===

[[File:Pushbutton.jpg]]

Press to manually start / stop a logging session. Note this may be overridden by any on-board scripts that may automatically start or stop logging.

===Communication Ports===

[[File:Expansionports.jpg]]

The communication ports a standard RS232 serial connection with power (up to 5v at 1.5A)
* Port 1
Used for BT module
* Port 2
Serial I/O

==Installation==
==Mounting orientation and position==

The ideal mounting position for RaceCapture/Pro is mounted flat (right side up or upside down), in the exact center of the vehicle. This gives the best effect from the built in Gyroscope, which measures Yaw (understeer / oversteer).

===Shock isolation mounting===
In very harsh environments you may want to mount RaceCapture/Pro using rubber isolators. [http://www.karman.com/selectvibro.cfm Info on isolation mounts]

===Default Accelerometer Configuration===
The default accelerometer configuration assumes RaceCapture/Pro is mounted flat, right side up with the green terminal block pointed towards the front of the vehicle. Other orientations are supported by changing the settings in the Software. See the [[RaceCapturePro_SoftwareOperation#Accelerometer_Inputs|Operation Guide]] for more information.

RaceCapture-Pro MK2

2015-11-24T18:17:11Z

Rdoherty: /* Getting Started */

=RaceCapture/Pro Quick Links=
* [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

==Getting Started==
*'''[[RaceCapturePro_Downloads|Software Downloads]]'''
*'''[[RaceCapturePro2_QuickStart|First time setup]]'''
*'''[[RaceCapturePro2_Hardware_Install|Hardware install]]'''

==How To==
*[[RaceCapturePro2_TelemetryQuickstart|How to: set up telemetry]]
*[[RaceCapturePro2_Enable_Predictive_Timing|How to: enable Predictive Timing]]
*[[RaceCapturePro2_OBD2|How to: enable OBD2 channels]]
*[[RaceCapturePro2_Calibrate_Sensor|How to: calibrate and configure an analog sensor]]
*[[RaceCapturePro2_RPM|How to: Connect RPM]]'''
*[[RaceCapturePro2_ShiftLights|How to: sequential shift lights]]
*[[RaceCapturePro2_GPS|How to: get best GPS data]]
*[[RCP_CAN|How to: Integrate CAN bus data]]
*[[RaceTracks|How to: Submit a new race track]]
*[[RaceCapturePro_FAQ|More FAQs and How-To's]]

==User Guides==
*[[RaceCapture_App_User%27s_Guide|RaceCapture App User's Guide]]
*[[RaceCapturePro_Sensors|Sensor Guide]]
*[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]

==More Information==
*[https://github.com/autosportlabs Source code]

===Previous Hardware Versions===
[[RaceCapturePro-MK1|RaceCapture/Pro MK1]]

=Quick Reference=
Download a [http://www.autosportlabs.com/racecapturepro-mk2-quick-reference/racecapture-pro-mk2-quick-reference-sheet printable PDF]

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

=RaceCapture/Pro MK2 Specifications=

{| class="wikitable" style="text-align: left"
!colspan="2"|Input / Output Channels
|-
!colspan="2"|'''Analog Inputs'''
|-
|Channels
|8 (battery voltage dedicated on channel 8)
|-
|Voltage range
|0-5v
|-
|Input impedance
|1M ohm
|-
|Voltage protection
|400v (intermittent)
|-
|ADC precision
|12 bit
|-
|Maximum sample rate
|1000Hz
|-
|Mapping
|Raw / Linear formula / Interpolated map
|-
!colspan="2"|'''Digital I/O'''
|-
|Channels
|3
|-
|Output mode type
|Open drain
|-
|Output current capacity
|1A, inductive clamped
|-
|Input mode voltage range
|0-12v
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''Timer Inputs (RPM / Frequency)'''
|-
|Channels
|3
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''PWM/Analog outputs'''
|-
|Channels
|4
|-
|PWM output type
|push/pull
|-
|PWM output voltage range
|5v
|-
|Output current capacity
|50mA
|-
|Analog Output
|0-5v
|-
!colspan="2"|Voltage Reference
|-
|Output Voltage/Capacity
|5v / 1A
|-
!colspan="2"|Connectivity
|-
!colspan="2"|'''CAN Bus'''
|-
|CAN Channels
|2
|-
|CAN baud rate
|125K, 250K, 500K, 1M baud
|-
|CAN filters
|14 per channel
|-
|Protocol support
|OBDII PID, custom CAN messaging
|-
!colspan="2"|'''Telemetry/Wireless'''
|-
|Cellular
|Quad-band GSM (internal module, optional)
|-
|Bluetooth
|Bluetooth 2.0 (external module, optional)
|-
|Serial
|Type External RJ11
|-
|Max Baud Rate
|230400
|-
!colspan="2"|Inertial Motion Unit
|-
|Accelerometer Channels
|3 (X/Y/Z) (2G, 4G capable)
|-
|Gyro
|3 (Yaw/Pitch/Roll) (1000 degrees/sec)
|-
|Magnetic compass
|1 (Bearing) (device capable of 3) (*Coming in 2.9.x firmware)
|-
!colspan="2"|GPS
|-
|GPS Type
|External active antenna
|-
|GPS Maximum sample rate
|50Hz
|-
|GPS accuracy
|2.5M CEP
|-
!colspan="2"|Storage
|-
|Micro SD
|Up to 32GB (SDHC)
|-
!colspan="2"|Configuration Capacity
|-
|Auto-detect track database
|240
|-
|Sectors per track
|20
|-
|Channel support
|200
|-
!colspan="2"|Physical
|-
|Dimensions
|5.3″ (w) x 4.2″ (h) x 1.2″ (tall) / 135x110x31 mm(est)
|-
|Weight
|9oz / 255gm (est)
|-
|Power Consumption (max)
|Main System: 0.6W<br/>With Bluetooth: 1.6W<br/>With Cellular Telemetry: 8.6W<br/>With Cellular Telemetry and Bluetooth: 9.6W
|-
|Temperature
| Max Internal Temperature while operating: -40°C ~ 85°C / -40°C ~ 80°C (Telemetry module)
|}

[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

BMW E46 CAN

2015-05-26T00:51:42Z

Rdoherty: /* CAN Bus connection */

=Installation=

==Things you'll need==
* Crimp tool
* Wire cutter
* Wire stripper
* Philipps screwdriver
* Multimeter
* 22 gauge solid wire
* RJ 45 (Ethernet) cable, ~6ft
* Shrink tubing (optional, electrical tape will work too, but not look as nice)
* [http://www.amazon.com/Posi-tap-Connectors-20-22-Gauge-Wire/dp/B004D0C2RC/ref=sr_1_1?ie=UTF8&qid=1423755810&sr=8-1&keywords=positaps| Posi-tap connectors] (2) - Do *not* cut the CAN wires during this installation, use wire taps (Posi-taps work very well)
* Butt connectors (2) for 22 gauge wire
* Flashlight
* RaceCapture/Pro with Bluetooth
* Android tablet
* An E46 ;)

==Estimated Time==
2-3 hours, depending on level of wiring experience. The most time consuming part is splicing the CAN, power and ground wires into the RJ45 cable.

===RaceCapture/Pro installation (Race / Spec E46)===
We recommend installing RaceCapture/Pro on the transmission tunnel to the right of the driver's seat. This is near the center of rotation to get the best effect from the on-board IMU (Accelerometer + Gyro)

[[Image:RCP_install_E46.jpg]]

==CAN wires==
The CAN+/CAN- wires are located in 2 places: under the driver's side dash above the footrest or in the DME panel. For these instructions it is assumed you are using the wires under the dash.

CAN wire colors are as follows:
* Yellow/Brown = CAN- (low)
* Yellow/Red = CAN+ (high)

They are a twisted pair in or attached to the main wiring harness under the driver's side dash above the dead pedal.

===Remove bottom of dash===
You will have to remove the panel below the steering wheel via 3 philipps screws, a plastic thumb screw (turn 90 degrees and pull) behind the pedals and a press fit plastic screw on the transmission tunnel (pull the tiny center pin out first, then the larger screw).

Once you have removed the panel you should see a large wiring harness above the dead pedal.

===Locate CAN wires===
Look for a twisted pair of wires that are Yellow/Brown and Yellow/Red like so:

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

Those are the 2 wires you need to *tap* into, not cut.

===Tapping CAN wires===
To tap into the wires, you'll first need to tease them apart because they are very tightly wound. Peel back some of the black cloth tape wrapping the harness and gently pull the wires apart. This may take some time. You'll want to have enough room for 2 fingers in between the wires.

Tapping the wires via Posi-taps (recommended) is easy. Pull the top off the Positap, place the wire in it and tighten. Verify you've tapped the wire by loosening and checking for a hole in the wire.

[[File:Positaps.png]]

Once you've tapped both it will most likely look like this:

[[File:Can-tapped.jpg|700px]]

===Create CAN wiring for RaceCapture/Pro===
Now that you've tapped the CAN wires, cut two 6 foot lengths of solid wire, strip both ends and attach one to CAN+ and CAN-. Make sure to label them or you'll have to keep looking under the dash. Yellow/Brown is CAN- and Yellow/Red is CAN+.

Where you run these two wires is dependent on where RaceCapture/Pro is. You can either run them down the driver's side of the car, next to the dead pedal or find a way to route them into the center dash and out below the CD player/HVAC controls. For these instructions we routed them next to the dead pedal, under the floor mat and taped them onto the transmission tunnel next to the driver hidden away. (Our RaceCapture/Pro was installed on the center rear seat)

==Power and ground wiring==

Note: You can skip this section if you already have power wired to RaceCapture/Pro and don't want to change it.

Mk1 owners: do not wire in power or ground.

===Locate power and ground wires===

The easiest to tap and most convenient power wires are under the coin holder in the center armrest. Pull the cup holder and coin holder out. Beneath them will be a cloth/foam wrapper containing a cellular phone connector. It contains 12v switched power and ground. Pull it gently towards the back of the car, then up to get more slack. Pull apart the foam to get to the wires.

The 12v wire is purple/white, ground is brown. *Note*: there is also a tan wire that looks very similar to brown. Compare the two and pick the darker one.

===Splice power and ground wires===

You can tap these wires if needed, for these instructions we cut them.

Cut 2 pieces of solid wire about 3ft long or appropriate length needed. Cut the 12v and ground wires and connect them to the wires you just made. Tape or add shrink tubing as necessary. Label the wires 12v and ground.

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

==CAN Bus connection==

In order for RaceCapture/Pro to read CAN data you need to connect the CAN+/CAN- wires to a RJ45 (ethernet cable).

Cut one end off the RJ45 cable and pull apart all the wires.

Identify and label the CAN1 High, CAN1 Low, 12v and ground wires via a multimeter.

For a standard RJ45 cable (EIA T568B) the colors are:

* Orange: CAN1 High
* Green/white: CAN1 Low
* Brown: Power
* Orange/white: Ground

Use the following diagram:

[[File:Canrj45.png]]

You will end up with something that looks like this:

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

Once you have identified and labeled the wires, strip them and attach to the CAN wires and power/ground wires from the car. RJ45 wires are very thin, you will want to loop them around the thicker wires and add tape or shrink tubing.

==Configure RaceCapture/Pro==

===Quick Start E46 configuration===
This configuration can be imported into your RaceCapture/Pro system to get you started.

Download: [http://autosportlabs.net/images/2/23/E46_CAN.rcp E46 CAN starter configuration] (right-click, save-as)

To complete your configuration:
* [[RaceCapture_App_User%27s_Guide#Automatic_Track_Detection_and_configuration|Add your favorite race tracks]] for automatic detection
* [[RaceCapturePro2_TelemetryQuickstart#Enable_Telemetry_and_Device_Id|Set your telemetry device id]] as provided by [http://www.race-capture.com race-capture.com]

===Manual Setup===
If you already have an existing, customized configuration, follow these steps to add E46 CAN bus integration.

'''[[RaceCapturePro2_OBD2#Enable_CAN_bus|Enable the CAN bus]]''' in your RaceCapture/Pro configuration

* Rate is 500kb/s
* Do '''not''' enable OBD-II channels.

Add this script to the Scripting section, this will enable Coolant, Oil Temp, Throttle position and brake switch. (More sensors coming soon!)

<pre>
--This example configured for E46 CAN
-- Automatically starts logging with engine 'on' (RPM triggered)

--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)
steerId = addChannel("Steering", 10, 0, -360, 360)

function steerFilter(value)
if value > 32768 - 1 then value = value - 32768 end
return value
end

--Convert C to F
function toF(value)
return value * 1.8 + 32
end

--E46 TPS, correct your throttle here for true 100%
function e46_tps(value)
return value * 1.0
end

--only start logging / telemetry if engine is running
function rpmFilter(value)
if value > 500 then startLogging() else stopLogging() end
return value
end

----------------------------------------
--customize here for CAN channel mapping
--format is:
--[CAN Id] = function(data) map_chan(<chan_id>, data, <CAN offset>, <CAN length>, <multiplier>,
-- <adder>, [filter])
----------------------------------------
CAN_map = {
[809] = function(data) map_chan(tpsId, data, 5, 1 , 0.392156863, 0, e46_tps) map_chan_le(tempId, data, 1, 1, 0.69202, -48, toF) end,
[1349] = function(data) map_chan(oilTempId, data, 4, 1, 0.8117, -48, toF) end,
[790] = function(data) map_chan(rpmId, data, 2, 2, 0.15625, 0, rpmFilter) end,
[501] = function (data)
local steer = 0
if data[2] > 127 then
steer = -1*(((data[2]-128)*256)+data[1])
else
steer = (data[2]*256)+data[1]
end
setChannel(steerId, (steer*0.045))
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, filter)
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
local cv = (value + add) * mult
if filter ~= nil then cv = filter(cv) end
setChannel(cid, cv)
end

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

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

==Test!==
Once everything is connected, plug in the other end of the RJ45 cable to RaceCapture/Pro, turn it on and turn on your car. Make sure RCP is connected to your tablet and the RaceCapture/App is running.

Swipe to the digital dash page and you should see data for Coolant, Oil Temp, Throttle and brake!

==Real-Time Telemetry==
Just 4 wires - Power, Ground, CAN+ and CAN- is needed to stream tons of data to [http://www.race-capture.com race-capture.com] for monitoring engine, driver and suspension performance!

[[Image:E46_realtime_data.jpg|700px]]

==Troubleshooting==
If you don't see any data, verify all connections and splices.

If everything is connected connect your laptop to RaceCapture/Pro, open the RaceCapture/App, go to the Scripting section, set Logging Level to debug and select 'Poll logfile'. Check the output for any obvious errors.

If you are still having issues post your problem on the forums here http://www.autosportlabs.org/viewforum.php?f=20

==CAN Channel Mapping==
The full CAN bus mapping can be found in our [[CAN_database#BMW_E46|CAN Database]]

==Additional resources==
* http://aimsportsystems.com.au/download/ecu/stock/bmw/BMW_Mini_100_eng.pdf - AIM docs for e46 M3 CAN codes
* http://www.diyelectriccar.com/forums/showthread.php/my-can-bus-gauge-solution-bmw-84882.html
* http://www.beisansystems.com/misc/SEIMENS_MS_420_ENGINE_CONTROL_SYSTEM.pdf
* http://www.bmwtech.ru/pdf/e46/ST034/2%20Driver%20Information%20Internet-1.pdf
* http://www.gadgetgangster.com/news/54-new-projects/556-the-car-kracker.html
* http://www.reslers.de/IBUS/index.html
* http://www.bimmerforums.com/forum/showthread.php?1887229-E46-Can-bus-project
* http://forum.e46fanatics.com/showpost.php?p=15754605&postcount=5

BMW E46 CAN

2015-05-26T00:51:08Z

Rdoherty: /* CAN Bus connection */

=Installation=

==Things you'll need==
* Crimp tool
* Wire cutter
* Wire stripper
* Philipps screwdriver
* Multimeter
* 22 gauge solid wire
* RJ 45 (Ethernet) cable, ~6ft
* Shrink tubing (optional, electrical tape will work too, but not look as nice)
* [http://www.amazon.com/Posi-tap-Connectors-20-22-Gauge-Wire/dp/B004D0C2RC/ref=sr_1_1?ie=UTF8&qid=1423755810&sr=8-1&keywords=positaps| Posi-tap connectors] (2) - Do *not* cut the CAN wires during this installation, use wire taps (Posi-taps work very well)
* Butt connectors (2) for 22 gauge wire
* Flashlight
* RaceCapture/Pro with Bluetooth
* Android tablet
* An E46 ;)

==Estimated Time==
2-3 hours, depending on level of wiring experience. The most time consuming part is splicing the CAN, power and ground wires into the RJ45 cable.

===RaceCapture/Pro installation (Race / Spec E46)===
We recommend installing RaceCapture/Pro on the transmission tunnel to the right of the driver's seat. This is near the center of rotation to get the best effect from the on-board IMU (Accelerometer + Gyro)

[[Image:RCP_install_E46.jpg]]

==CAN wires==
The CAN+/CAN- wires are located in 2 places: under the driver's side dash above the footrest or in the DME panel. For these instructions it is assumed you are using the wires under the dash.

CAN wire colors are as follows:
* Yellow/Brown = CAN- (low)
* Yellow/Red = CAN+ (high)

They are a twisted pair in or attached to the main wiring harness under the driver's side dash above the dead pedal.

===Remove bottom of dash===
You will have to remove the panel below the steering wheel via 3 philipps screws, a plastic thumb screw (turn 90 degrees and pull) behind the pedals and a press fit plastic screw on the transmission tunnel (pull the tiny center pin out first, then the larger screw).

Once you have removed the panel you should see a large wiring harness above the dead pedal.

===Locate CAN wires===
Look for a twisted pair of wires that are Yellow/Brown and Yellow/Red like so:

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

Those are the 2 wires you need to *tap* into, not cut.

===Tapping CAN wires===
To tap into the wires, you'll first need to tease them apart because they are very tightly wound. Peel back some of the black cloth tape wrapping the harness and gently pull the wires apart. This may take some time. You'll want to have enough room for 2 fingers in between the wires.

Tapping the wires via Posi-taps (recommended) is easy. Pull the top off the Positap, place the wire in it and tighten. Verify you've tapped the wire by loosening and checking for a hole in the wire.

[[File:Positaps.png]]

Once you've tapped both it will most likely look like this:

[[File:Can-tapped.jpg|700px]]

===Create CAN wiring for RaceCapture/Pro===
Now that you've tapped the CAN wires, cut two 6 foot lengths of solid wire, strip both ends and attach one to CAN+ and CAN-. Make sure to label them or you'll have to keep looking under the dash. Yellow/Brown is CAN- and Yellow/Red is CAN+.

Where you run these two wires is dependent on where RaceCapture/Pro is. You can either run them down the driver's side of the car, next to the dead pedal or find a way to route them into the center dash and out below the CD player/HVAC controls. For these instructions we routed them next to the dead pedal, under the floor mat and taped them onto the transmission tunnel next to the driver hidden away. (Our RaceCapture/Pro was installed on the center rear seat)

==Power and ground wiring==

Note: You can skip this section if you already have power wired to RaceCapture/Pro and don't want to change it.

Mk1 owners: do not wire in power or ground.

===Locate power and ground wires===

The easiest to tap and most convenient power wires are under the coin holder in the center armrest. Pull the cup holder and coin holder out. Beneath them will be a cloth/foam wrapper containing a cellular phone connector. It contains 12v switched power and ground. Pull it gently towards the back of the car, then up to get more slack. Pull apart the foam to get to the wires.

The 12v wire is purple/white, ground is brown. *Note*: there is also a tan wire that looks very similar to brown. Compare the two and pick the darker one.

===Splice power and ground wires===

You can tap these wires if needed, for these instructions we cut them.

Cut 2 pieces of solid wire about 3ft long or appropriate length needed. Cut the 12v and ground wires and connect them to the wires you just made. Tape or add shrink tubing as necessary. Label the wires 12v and ground.

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

==CAN Bus connection==

In order for RaceCapture/Pro to read CAN data you need to connect the CAN+/CAN- wires to a RJ45 (ethernet cable).

Cut one end off the RJ45 cable and pull apart all the wires.

Identify and label the CAN1 High, CAN1 Low, 12v and ground wires via a multimeter.

For a standard RJ45 cable (EIA T568B) the colors are:

* Brown: Power
* Orange/white: Ground
* Green/white: CAN1 Low
* Orange: CAN1 High

Use the following diagram:

[[File:Canrj45.png]]

You will end up with something that looks like this:

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

Once you have identified and labeled the wires, strip them and attach to the CAN wires and power/ground wires from the car. RJ45 wires are very thin, you will want to loop them around the thicker wires and add tape or shrink tubing.

==Configure RaceCapture/Pro==

===Quick Start E46 configuration===
This configuration can be imported into your RaceCapture/Pro system to get you started.

Download: [http://autosportlabs.net/images/2/23/E46_CAN.rcp E46 CAN starter configuration] (right-click, save-as)

To complete your configuration:
* [[RaceCapture_App_User%27s_Guide#Automatic_Track_Detection_and_configuration|Add your favorite race tracks]] for automatic detection
* [[RaceCapturePro2_TelemetryQuickstart#Enable_Telemetry_and_Device_Id|Set your telemetry device id]] as provided by [http://www.race-capture.com race-capture.com]

===Manual Setup===
If you already have an existing, customized configuration, follow these steps to add E46 CAN bus integration.

'''[[RaceCapturePro2_OBD2#Enable_CAN_bus|Enable the CAN bus]]''' in your RaceCapture/Pro configuration

* Rate is 500kb/s
* Do '''not''' enable OBD-II channels.

Add this script to the Scripting section, this will enable Coolant, Oil Temp, Throttle position and brake switch. (More sensors coming soon!)

<pre>
--This example configured for E46 CAN
-- Automatically starts logging with engine 'on' (RPM triggered)

--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)
steerId = addChannel("Steering", 10, 0, -360, 360)

function steerFilter(value)
if value > 32768 - 1 then value = value - 32768 end
return value
end

--Convert C to F
function toF(value)
return value * 1.8 + 32
end

--E46 TPS, correct your throttle here for true 100%
function e46_tps(value)
return value * 1.0
end

--only start logging / telemetry if engine is running
function rpmFilter(value)
if value > 500 then startLogging() else stopLogging() end
return value
end

----------------------------------------
--customize here for CAN channel mapping
--format is:
--[CAN Id] = function(data) map_chan(<chan_id>, data, <CAN offset>, <CAN length>, <multiplier>,
-- <adder>, [filter])
----------------------------------------
CAN_map = {
[809] = function(data) map_chan(tpsId, data, 5, 1 , 0.392156863, 0, e46_tps) map_chan_le(tempId, data, 1, 1, 0.69202, -48, toF) end,
[1349] = function(data) map_chan(oilTempId, data, 4, 1, 0.8117, -48, toF) end,
[790] = function(data) map_chan(rpmId, data, 2, 2, 0.15625, 0, rpmFilter) end,
[501] = function (data)
local steer = 0
if data[2] > 127 then
steer = -1*(((data[2]-128)*256)+data[1])
else
steer = (data[2]*256)+data[1]
end
setChannel(steerId, (steer*0.045))
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, filter)
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
local cv = (value + add) * mult
if filter ~= nil then cv = filter(cv) end
setChannel(cid, cv)
end

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

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

==Test!==
Once everything is connected, plug in the other end of the RJ45 cable to RaceCapture/Pro, turn it on and turn on your car. Make sure RCP is connected to your tablet and the RaceCapture/App is running.

Swipe to the digital dash page and you should see data for Coolant, Oil Temp, Throttle and brake!

==Real-Time Telemetry==
Just 4 wires - Power, Ground, CAN+ and CAN- is needed to stream tons of data to [http://www.race-capture.com race-capture.com] for monitoring engine, driver and suspension performance!

[[Image:E46_realtime_data.jpg|700px]]

==Troubleshooting==
If you don't see any data, verify all connections and splices.

If everything is connected connect your laptop to RaceCapture/Pro, open the RaceCapture/App, go to the Scripting section, set Logging Level to debug and select 'Poll logfile'. Check the output for any obvious errors.

If you are still having issues post your problem on the forums here http://www.autosportlabs.org/viewforum.php?f=20

==CAN Channel Mapping==
The full CAN bus mapping can be found in our [[CAN_database#BMW_E46|CAN Database]]

==Additional resources==
* http://aimsportsystems.com.au/download/ecu/stock/bmw/BMW_Mini_100_eng.pdf - AIM docs for e46 M3 CAN codes
* http://www.diyelectriccar.com/forums/showthread.php/my-can-bus-gauge-solution-bmw-84882.html
* http://www.beisansystems.com/misc/SEIMENS_MS_420_ENGINE_CONTROL_SYSTEM.pdf
* http://www.bmwtech.ru/pdf/e46/ST034/2%20Driver%20Information%20Internet-1.pdf
* http://www.gadgetgangster.com/news/54-new-projects/556-the-car-kracker.html
* http://www.reslers.de/IBUS/index.html
* http://www.bimmerforums.com/forum/showthread.php?1887229-E46-Can-bus-project
* http://forum.e46fanatics.com/showpost.php?p=15754605&postcount=5

BMW E46 CAN

2015-05-26T00:49:27Z

Rdoherty: /* CAN Bus connection */

=Installation=

==Things you'll need==
* Crimp tool
* Wire cutter
* Wire stripper
* Philipps screwdriver
* Multimeter
* 22 gauge solid wire
* RJ 45 (Ethernet) cable, ~6ft
* Shrink tubing (optional, electrical tape will work too, but not look as nice)
* [http://www.amazon.com/Posi-tap-Connectors-20-22-Gauge-Wire/dp/B004D0C2RC/ref=sr_1_1?ie=UTF8&qid=1423755810&sr=8-1&keywords=positaps| Posi-tap connectors] (2) - Do *not* cut the CAN wires during this installation, use wire taps (Posi-taps work very well)
* Butt connectors (2) for 22 gauge wire
* Flashlight
* RaceCapture/Pro with Bluetooth
* Android tablet
* An E46 ;)

==Estimated Time==
2-3 hours, depending on level of wiring experience. The most time consuming part is splicing the CAN, power and ground wires into the RJ45 cable.

===RaceCapture/Pro installation (Race / Spec E46)===
We recommend installing RaceCapture/Pro on the transmission tunnel to the right of the driver's seat. This is near the center of rotation to get the best effect from the on-board IMU (Accelerometer + Gyro)

[[Image:RCP_install_E46.jpg]]

==CAN wires==
The CAN+/CAN- wires are located in 2 places: under the driver's side dash above the footrest or in the DME panel. For these instructions it is assumed you are using the wires under the dash.

CAN wire colors are as follows:
* Yellow/Brown = CAN- (low)
* Yellow/Red = CAN+ (high)

They are a twisted pair in or attached to the main wiring harness under the driver's side dash above the dead pedal.

===Remove bottom of dash===
You will have to remove the panel below the steering wheel via 3 philipps screws, a plastic thumb screw (turn 90 degrees and pull) behind the pedals and a press fit plastic screw on the transmission tunnel (pull the tiny center pin out first, then the larger screw).

Once you have removed the panel you should see a large wiring harness above the dead pedal.

===Locate CAN wires===
Look for a twisted pair of wires that are Yellow/Brown and Yellow/Red like so:

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

Those are the 2 wires you need to *tap* into, not cut.

===Tapping CAN wires===
To tap into the wires, you'll first need to tease them apart because they are very tightly wound. Peel back some of the black cloth tape wrapping the harness and gently pull the wires apart. This may take some time. You'll want to have enough room for 2 fingers in between the wires.

Tapping the wires via Posi-taps (recommended) is easy. Pull the top off the Positap, place the wire in it and tighten. Verify you've tapped the wire by loosening and checking for a hole in the wire.

[[File:Positaps.png]]

Once you've tapped both it will most likely look like this:

[[File:Can-tapped.jpg|700px]]

===Create CAN wiring for RaceCapture/Pro===
Now that you've tapped the CAN wires, cut two 6 foot lengths of solid wire, strip both ends and attach one to CAN+ and CAN-. Make sure to label them or you'll have to keep looking under the dash. Yellow/Brown is CAN- and Yellow/Red is CAN+.

Where you run these two wires is dependent on where RaceCapture/Pro is. You can either run them down the driver's side of the car, next to the dead pedal or find a way to route them into the center dash and out below the CD player/HVAC controls. For these instructions we routed them next to the dead pedal, under the floor mat and taped them onto the transmission tunnel next to the driver hidden away. (Our RaceCapture/Pro was installed on the center rear seat)

==Power and ground wiring==

Note: You can skip this section if you already have power wired to RaceCapture/Pro and don't want to change it.

Mk1 owners: do not wire in power or ground.

===Locate power and ground wires===

The easiest to tap and most convenient power wires are under the coin holder in the center armrest. Pull the cup holder and coin holder out. Beneath them will be a cloth/foam wrapper containing a cellular phone connector. It contains 12v switched power and ground. Pull it gently towards the back of the car, then up to get more slack. Pull apart the foam to get to the wires.

The 12v wire is purple/white, ground is brown. *Note*: there is also a tan wire that looks very similar to brown. Compare the two and pick the darker one.

===Splice power and ground wires===

You can tap these wires if needed, for these instructions we cut them.

Cut 2 pieces of solid wire about 3ft long or appropriate length needed. Cut the 12v and ground wires and connect them to the wires you just made. Tape or add shrink tubing as necessary. Label the wires 12v and ground.

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

==CAN Bus connection==

In order for RaceCapture/Pro to read CAN data you need to connect the CAN+/CAN- wires to a RJ45 (ethernet cable).

Cut one end off the RJ45 cable and pull apart all the wires.

Identify and label the CAN1 High, CAN1 Low, 12v and ground wires via a multimeter.

For a standard RJ45 cable the colors are:

* Brown: power/8
* Orange/white: ground
* Green/white: CAN1 low
* Orange: CAN1 high

Use the following diagram:

[[File:Canrj45.png]]

You will end up with something that looks like this:

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

Once you have identified and labeled the wires, strip them and attach to the CAN wires and power/ground wires from the car. RJ45 wires are very thin, you will want to loop them around the thicker wires and add tape or shrink tubing.

==Configure RaceCapture/Pro==

===Quick Start E46 configuration===
This configuration can be imported into your RaceCapture/Pro system to get you started.

Download: [http://autosportlabs.net/images/2/23/E46_CAN.rcp E46 CAN starter configuration] (right-click, save-as)

To complete your configuration:
* [[RaceCapture_App_User%27s_Guide#Automatic_Track_Detection_and_configuration|Add your favorite race tracks]] for automatic detection
* [[RaceCapturePro2_TelemetryQuickstart#Enable_Telemetry_and_Device_Id|Set your telemetry device id]] as provided by [http://www.race-capture.com race-capture.com]

===Manual Setup===
If you already have an existing, customized configuration, follow these steps to add E46 CAN bus integration.

'''[[RaceCapturePro2_OBD2#Enable_CAN_bus|Enable the CAN bus]]''' in your RaceCapture/Pro configuration

* Rate is 500kb/s
* Do '''not''' enable OBD-II channels.

Add this script to the Scripting section, this will enable Coolant, Oil Temp, Throttle position and brake switch. (More sensors coming soon!)

<pre>
--This example configured for E46 CAN
-- Automatically starts logging with engine 'on' (RPM triggered)

--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)
steerId = addChannel("Steering", 10, 0, -360, 360)

function steerFilter(value)
if value > 32768 - 1 then value = value - 32768 end
return value
end

--Convert C to F
function toF(value)
return value * 1.8 + 32
end

--E46 TPS, correct your throttle here for true 100%
function e46_tps(value)
return value * 1.0
end

--only start logging / telemetry if engine is running
function rpmFilter(value)
if value > 500 then startLogging() else stopLogging() end
return value
end

----------------------------------------
--customize here for CAN channel mapping
--format is:
--[CAN Id] = function(data) map_chan(<chan_id>, data, <CAN offset>, <CAN length>, <multiplier>,
-- <adder>, [filter])
----------------------------------------
CAN_map = {
[809] = function(data) map_chan(tpsId, data, 5, 1 , 0.392156863, 0, e46_tps) map_chan_le(tempId, data, 1, 1, 0.69202, -48, toF) end,
[1349] = function(data) map_chan(oilTempId, data, 4, 1, 0.8117, -48, toF) end,
[790] = function(data) map_chan(rpmId, data, 2, 2, 0.15625, 0, rpmFilter) end,
[501] = function (data)
local steer = 0
if data[2] > 127 then
steer = -1*(((data[2]-128)*256)+data[1])
else
steer = (data[2]*256)+data[1]
end
setChannel(steerId, (steer*0.045))
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, filter)
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
local cv = (value + add) * mult
if filter ~= nil then cv = filter(cv) end
setChannel(cid, cv)
end

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

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

==Test!==
Once everything is connected, plug in the other end of the RJ45 cable to RaceCapture/Pro, turn it on and turn on your car. Make sure RCP is connected to your tablet and the RaceCapture/App is running.

Swipe to the digital dash page and you should see data for Coolant, Oil Temp, Throttle and brake!

==Real-Time Telemetry==
Just 4 wires - Power, Ground, CAN+ and CAN- is needed to stream tons of data to [http://www.race-capture.com race-capture.com] for monitoring engine, driver and suspension performance!

[[Image:E46_realtime_data.jpg|700px]]

==Troubleshooting==
If you don't see any data, verify all connections and splices.

If everything is connected connect your laptop to RaceCapture/Pro, open the RaceCapture/App, go to the Scripting section, set Logging Level to debug and select 'Poll logfile'. Check the output for any obvious errors.

If you are still having issues post your problem on the forums here http://www.autosportlabs.org/viewforum.php?f=20

==CAN Channel Mapping==
The full CAN bus mapping can be found in our [[CAN_database#BMW_E46|CAN Database]]

==Additional resources==
* http://aimsportsystems.com.au/download/ecu/stock/bmw/BMW_Mini_100_eng.pdf - AIM docs for e46 M3 CAN codes
* http://www.diyelectriccar.com/forums/showthread.php/my-can-bus-gauge-solution-bmw-84882.html
* http://www.beisansystems.com/misc/SEIMENS_MS_420_ENGINE_CONTROL_SYSTEM.pdf
* http://www.bmwtech.ru/pdf/e46/ST034/2%20Driver%20Information%20Internet-1.pdf
* http://www.gadgetgangster.com/news/54-new-projects/556-the-car-kracker.html
* http://www.reslers.de/IBUS/index.html
* http://www.bimmerforums.com/forum/showthread.php?1887229-E46-Can-bus-project
* http://forum.e46fanatics.com/showpost.php?p=15754605&postcount=5

RaceCapturePro2 QuickStart

2015-05-20T19:04:23Z

Rdoherty: /* Prerequisites */

__FORCETOC__

== Prerequisites ==
* [https://race-capture.com/software/54aacf81183b3a6722000001 Download and install] the latest RaceCapture App
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 users''' - These drivers are unsigned. We are working on creating a signed driver set, but in the meantime you will need to disable the driver signing requirement for Windows 8. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]
*** [http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/ Win8 64bit unsigned driver instructions]

== Quick Start ==

Watch our software installation video here: https://www.youtube.com/watch?v=oqveE2C1vo0

# Attach GPS and Bluetooth module (if purchased) to RaceCapture/Pro
# Plug in the supplied USB cable to RaceCapture/Pro and your computer.
# When prompted for drivers, select them from the zip file you unzipped previously.
## If not prompted or Windows does not ask you to locate drivers, open Device Manager, find RaceCapture/Pro (usually under 'Other devices'), right click and select 'Update Driver' software. Then select the folder containing the unzipped drivers you downloaded previously.
# Confirm you really want to install the drivers
# Open the RaceCapture application.
## You should see 'Reading Configuration' at the top of the window once the app detects RaceCapture/Pro.
# Click on 'Dashboard'
# Click on the bottom right arrow three times, which will display the digital dash. You should see the Utc and Interval channels changing, which means data is being transmitted over USB.
## '''Protip:''' Pick up the RaceCapture/Pro unit, move it around and observe changes from the internal accelerometer and gyro sensors!

[[File:Dash.png|500px]]

# You have now setup the RaceCapture app!

== Selecting your favorite race tracks==
RaceCapture/Pro can auto-detect and configure your favorite race tracks as soon as GPS lock is obtained.

# After connecting the RaceCapture app and verifying connectivity, navigate to the configuration view.
# Select the Race Tracks from the menu on the left.
# Search and select the race tracks you will be typically attending.
# Once the tracks have been selected, write the updated configuration using the [[Image:rc_appwrite_config.png]] button in the lower left.

When you arrive at the track and RaceCapture is powered up, it will automatically detect and configure the track's start/finish line and any available sectors.

ProTip: Periodically click the update button [[Image:update_from_cloud.png]] to pull down the latest set of race track configurations.

[[Image:RA_automatic_track_detection.png|500px]]

== Setting up Bluetooth ==
===Enabling Bluetooth in firmware settings===
# Complete the Quick Start steps above, leaving RaceCapture/Pro connected to your computer
# Connect the Bluetooth module to the inner of the two RaceCapture/Pro ports on the same side the USB cable connects to
# Open the Race Capture app
# Click on the top left 'Menu' button
# Click on 'Configuration'
# Click on 'Wireless' in the list of options on the left
# Click the toggle to the right of 'Bluetooth' <br> [[File:Bt.png|500px]]
# Click the 'Write Config' button on the bottom left (down array pointing to a RaceCapture/Pro)

===Set up Android tablet/phone===
==Requirements==
For best performance, we recommend the following minimum specification:
* Android 4.4 and higher
* Quad core 1.6 GHz processor
* 2 GB RAM, 8 GB flash
* 1024x600 resolution, IPS display
* 7" or 10" screen

Recommended Brands for tablets:
* Samsung
* Google Nexus
* LG
* Lenovo

==Touch screen operation with gloves==
We recommend [http://http://www.amazon.com/AnyGlove-TM-Synthetic-Touchscreen-Compatible/dp/B00AB3EVOW AnyGlove] to make your racing gloves touch screen compatible.

==Bluetooth pairing==
# Go into the Android settings and pair your device with the RaceCapture/Pro Bluetooth module
## Ensure Bluetooth is turned on in the Android device settings.
## Ensure the RaceCapture/Pro Bluetooth module is powered on (green light is flashing)
## Default password is 1234
# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
## The green light on the Bluetooth module should be solid and not flashing

===Verify connectivity===
# Swipe to the digital dash screen and you should see values changing. Pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

RaceCapturePro Downloads

2015-05-19T15:41:51Z

Rdoherty: /* RaceCapture/Pro MK1 */

=RaceCapture App=
* Use the RaceCapture App to configure and visualize data from your RaceCapture/Pro device.
* For '''MK1 and MK2''' versions of RaceCapture/Pro
** ''MK1 users:'' ensure you have updated to the latest V2 firmware.

'''Note''' - Dashboard, configuration and telemetry analysis features via [http://race-capture.com race-capture.com] are available now; in-app analysis features will be available in the upcoming release (soon)

===Windows===
Requires: Windows 7+; 2GB RAM; OpenGL 2.0 graphics support

[http://autosportlabs.net/asl_dist/rc_app/raceCapture_1.2.5.exe RaceCapture App v1.2.5]

Note: The app will fail to launch if OpenGL 2.0 graphics are not supported. If this happens try updating your graphics driver.

[[RaceCapturePro_Previous_Versions|Previous Versions]]

Extract this zip package to your computer and direct Windows to the location of the drivers when you are prompted for drivers after RaceCapture/Pro is plugged in.

===Mac OS X===
[http://autosportlabs.net/asl_dist/rc_app/raceCapture_osx_1.2.5.zip RaceCapture App v1.2.5 Beta]

Requires OSX 10.6+

Unzip the file and copy the RaceCapture app to your Applications directory.

'''This is a beta''' it may crash or have unexpected behavior. Please file bugs on our forums here http://www.autosportlabs.org/viewforum.php?f=33

===Linux===
Packages coming soon!

===Mobile App===
Android: Use the RaceCapture/App in the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Play Store]

* '''Note''' : The main RaceCapture app will be supported on Android in an near-term upcoming release. This will provide a unified experience across all platforms.

==USB Driver==
* Windows: [http://autosportlabs.net/asl_dist/rcp2/drivers/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
'''Note for Windows 8 users''' - These drivers are unsigned. We are working on creating a signed driver set, but in the meantime you will need to disable the driver signing requirement for Windows 8. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]

* OS X: No driver needed

* Linux: No driver needed

=RaceCapture/Pro MK2=

==Firmware==
See the CHANGELOG file in the .zip file package to see the list of changes for that release.
* [http://autosportlabs.net/asl_dist/rcp2/firmware/RaceCapturePro_MK2_2.7.9.zip RaceCapture/Pro MK2 firmware 2.7.9]
[[RaceCapturePro_Previous_Versions|Previous Versions]]

[[RaceCapturePro_How_To_Update_Firmware|How To Update Firmware]]

=RaceCapture/Pro MK1=

Note: For Mac users 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.

==Firmware==
The V2.x.x firmware for MK1 is considered 'stable beta' - We feel it's much better quality than the previous 1.2.x firmware and RaceAnalyzer combination, but since it is the first V2 firmware and app release for MK1, we are officially calling it Beta. Please visit the [http://www.autosportlabs.org/viewforum.php?f=33 Discussion / support forum] for help.

* [http://autosportlabs.net/asl_dist/rcp/firmware/RaceCapturePro_MK1_2.7.9.zip RaceCapture/Pro MK1 firmware 2.7.9]

[[RaceCapturePro_Previous_Versions|Previous Versions]]

[[RaceCapturePro_How_To_Update_Firmware|How To Update Firmware]]

===MK1 Bootloader Releases===
The bootloader is permanently, factory installed and shouldn't normally need to be re-flashed - contact us for support if you have any questions.

* [http://autosportlabs.net/asl_dist/rcp/bootloader/bootloader_0.0.2.bin bootloader_0.0.2.bin]
* [http://autosportlabs.net/asl_dist/rcp/bootloader/bootloader_0.0.1.bin bootloader_0.0.1.bin]

===Firmware update utility===
This is a small command-line utility that writes new firmware to RaceCapture/Pro. Note, it is already included in the .zip distributions of RaceCapture/Pro firmware.
* [http://autosportlabs.net/asl_dist/rcp/bootloader/flasher_WinXPVista7_8.zip flasher (WindowsXP/Vista/7/8)]
* [http://autosportlabs.net/asl_dist/rcp/bootloader/flasher_x86_64.tgz flasher (Linux x86_64)]

RaceCapturePro Downloads

2015-05-19T15:41:39Z

Rdoherty: /* RaceCapture/Pro MK1 */

=RaceCapture App=
* Use the RaceCapture App to configure and visualize data from your RaceCapture/Pro device.
* For '''MK1 and MK2''' versions of RaceCapture/Pro
** ''MK1 users:'' ensure you have updated to the latest V2 firmware.

'''Note''' - Dashboard, configuration and telemetry analysis features via [http://race-capture.com race-capture.com] are available now; in-app analysis features will be available in the upcoming release (soon)

===Windows===
Requires: Windows 7+; 2GB RAM; OpenGL 2.0 graphics support

[http://autosportlabs.net/asl_dist/rc_app/raceCapture_1.2.5.exe RaceCapture App v1.2.5]

Note: The app will fail to launch if OpenGL 2.0 graphics are not supported. If this happens try updating your graphics driver.

[[RaceCapturePro_Previous_Versions|Previous Versions]]

Extract this zip package to your computer and direct Windows to the location of the drivers when you are prompted for drivers after RaceCapture/Pro is plugged in.

===Mac OS X===
[http://autosportlabs.net/asl_dist/rc_app/raceCapture_osx_1.2.5.zip RaceCapture App v1.2.5 Beta]

Requires OSX 10.6+

Unzip the file and copy the RaceCapture app to your Applications directory.

'''This is a beta''' it may crash or have unexpected behavior. Please file bugs on our forums here http://www.autosportlabs.org/viewforum.php?f=33

===Linux===
Packages coming soon!

===Mobile App===
Android: Use the RaceCapture/App in the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Play Store]

* '''Note''' : The main RaceCapture app will be supported on Android in an near-term upcoming release. This will provide a unified experience across all platforms.

==USB Driver==
* Windows: [http://autosportlabs.net/asl_dist/rcp2/drivers/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
'''Note for Windows 8 users''' - These drivers are unsigned. We are working on creating a signed driver set, but in the meantime you will need to disable the driver signing requirement for Windows 8. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]

* OS X: No driver needed

* Linux: No driver needed

=RaceCapture/Pro MK2=

==Firmware==
See the CHANGELOG file in the .zip file package to see the list of changes for that release.
* [http://autosportlabs.net/asl_dist/rcp2/firmware/RaceCapturePro_MK2_2.7.9.zip RaceCapture/Pro MK2 firmware 2.7.9]
[[RaceCapturePro_Previous_Versions|Previous Versions]]

[[RaceCapturePro_How_To_Update_Firmware|How To Update Firmware]]

=RaceCapture/Pro MK1=

*Note* For Mac users 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.

==Firmware==
The V2.x.x firmware for MK1 is considered 'stable beta' - We feel it's much better quality than the previous 1.2.x firmware and RaceAnalyzer combination, but since it is the first V2 firmware and app release for MK1, we are officially calling it Beta. Please visit the [http://www.autosportlabs.org/viewforum.php?f=33 Discussion / support forum] for help.

* [http://autosportlabs.net/asl_dist/rcp/firmware/RaceCapturePro_MK1_2.7.9.zip RaceCapture/Pro MK1 firmware 2.7.9]

[[RaceCapturePro_Previous_Versions|Previous Versions]]

[[RaceCapturePro_How_To_Update_Firmware|How To Update Firmware]]

===MK1 Bootloader Releases===
The bootloader is permanently, factory installed and shouldn't normally need to be re-flashed - contact us for support if you have any questions.

* [http://autosportlabs.net/asl_dist/rcp/bootloader/bootloader_0.0.2.bin bootloader_0.0.2.bin]
* [http://autosportlabs.net/asl_dist/rcp/bootloader/bootloader_0.0.1.bin bootloader_0.0.1.bin]

===Firmware update utility===
This is a small command-line utility that writes new firmware to RaceCapture/Pro. Note, it is already included in the .zip distributions of RaceCapture/Pro firmware.
* [http://autosportlabs.net/asl_dist/rcp/bootloader/flasher_WinXPVista7_8.zip flasher (WindowsXP/Vista/7/8)]
* [http://autosportlabs.net/asl_dist/rcp/bootloader/flasher_x86_64.tgz flasher (Linux x86_64)]

RaceCapture-Pro MK2

2015-05-15T23:00:25Z

Rdoherty: /* RaceCapture/Pro Quick Links */

=RaceCapture/Pro Quick Links=
* [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

==Getting Started==
*'''[[RaceCapturePro2_QuickStart|First time setup]]'''

*'''[[RaceCapturePro2_OBD2|How to: enable OBD2 channels]]'''
*'''[[RaceCapturePro2_Calibrate_Sensor|How to: calibrate and configure an analog sensor]]'''
*'''[[RaceCapturePro2_RPM|How to: Connect RPM]]'''
*'''[[RaceCapturePro2_Enable_Predictive_Timing|How to: enable Predictive Timing]]'''
*'''[[RaceCapturePro2_TelemetryQuickstart|How to: set up telemetry]]'''
*'''[[RaceCapturePro2_ShiftLights|How to: sequential shift lights]]'''
*'''[[RaceCapturePro2_GPS|How to: get best GPS data]]'''

*[[RaceCapturePro_FAQ|More FAQs and How-To's"]]

*'''[[RaceCapture_App_User%27s_Guide|RaceCapture App User's Guide]]
*'''[https://race-capture.com/software Software and Firmware downloads]'''
*'''[[RaceCapturePro_Sensors|Sensor Guide]]'''
*'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''
*[https://github.com/autosportlabs Source code]
*[[RaceTracks|List of supported Race Tracks and Track Maps]]
*[[RCP_CAN|CAN Integration support]]

===Previous Hardware Versions===
[[RaceCapturePro-MK1|RaceCapture/Pro MK1]]

=Quick Reference=
Download a [http://www.autosportlabs.com/racecapturepro-mk2-quick-reference/racecapture-pro-mk2-quick-reference-sheet printable PDF]

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

=RaceCapture/Pro MK2 Specifications=

{| class="wikitable" style="text-align: left"
!colspan="2"|Input / Output Channels
|-
!colspan="2"|'''Analog Inputs'''
|-
|Channels
|8 (battery voltage dedicated on channel 8)
|-
|Voltage range
|0-5v
|-
|Input impedance
|1M ohm
|-
|Voltage protection
|400v (intermittent)
|-
|ADC precision
|12 bit
|-
|Maximum sample rate
|1000Hz
|-
|Mapping
|Raw / Linear formula / Interpolated map
|-
!colspan="2"|'''Digital I/O'''
|-
|Channels
|3
|-
|Output mode type
|Open drain
|-
|Output current capacity
|1A, inductive clamped
|-
|Input mode voltage range
|0-12v
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''Timer Inputs (RPM / Frequency)'''
|-
|Channels
|3
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''PWM/Analog outputs'''
|-
|Channels
|4
|-
|PWM output type
|push/pull
|-
|PWM output voltage range
|5v
|-
|Output current capacity
|50mA
|-
|Analog Output
|0-5v
|-
!colspan="2"|Voltage Reference
|-
|Output Voltage/Capacity
|5v / 1A
|-
!colspan="2"|Connectivity
|-
!colspan="2"|'''CAN Bus'''
|-
|CAN Channels
|2
|-
|CAN baud rate
|125K, 250K, 500K, 1M baud
|-
|CAN filters
|14 per channel
|-
|Protocol support
|OBDII PID, custom CAN messaging
|-
!colspan="2"|'''Telemetry/Wireless'''
|-
|Cellular
|Quad-band GSM (internal module, optional)
|-
|Bluetooth
|Bluetooth 2.0 (external module, optional)
|-
|Serial
|Type External RJ11
|-
|Max Baud Rate
|230400
|-
!colspan="2"|Inertial Motion Unit
|-
|Accelerometer Channels
|3 (X/Y/Z) (2G, 4G capable)
|-
|Gyro
|3 (Yaw/Pitch/Roll) (1000 degrees/sec)
|-
|Magnetic compass
|1 (Bearing) (device capable of 3)
|-
!colspan="2"|GPS
|-
|GPS Type
|External active antenna
|-
|GPS Maximum sample rate
|50Hz
|-
|GPS accuracy
|2.5M CEP
|-
!colspan="2"|Storage
|-
|Micro SD
|Up to 32GB (SDHC)
|-
!colspan="2"|Configuration Capacity
|-
|Auto-detect track database
|240
|-
|Sectors per track
|20
|-
|Channel support
|200
|-
!colspan="2"|Physical
|-
|Dimensions
|5.3″ (w) x 4.2″ (h) x 1.2″ (tall) / 135x110x31 mm(est)
|-
|Weight
|9oz / 255gm (est)
|-
|Temperature
| Max Internal Temperature while operating: -40°C ~ 85°C / -40°C ~ 80°C (Telemetry module)
|}

[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

Main Page

2015-05-15T22:59:58Z

Rdoherty: /* Autosport Labs Projects */

__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==
<center>
<table>
<tr>
<td align="center">
[[Image:RaceCapturePro_logo_small.png|link=RaceCapturePro]]
<br>[[Image:racecapture_mk2_3quarter.jpg|446px|link=RaceCapturePro]]
<br>

<h2 style="text-decoration:underline;font-weight:bold;">[[RaceCapturePro|Race Capture Pro]]</h2>
'''Data Acquisition and Control'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]
</td>
<td align="center">
[[Image:mjlj_small_logo.png|link=Megajolt Lite Jr.]]
<br><br>[[Image:MegajoltE_map.jpg|300px|link=Megajolt Lite Jr.]]
<br><h2 style="text-decoration:underline;font-weight:bold;">[[Megajolt Lite Jr.|Megajolt Lite Jr.]]</h2>
'''Programmable Ignition Controller'''<br>
[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/megajolte/]]

</td>
</tr>
</table>
</center>

==Other things we're working on==

===DIY Racing Helmet Microphone===
*[[Helmet_mic|Build a helmet mic on the cheap!]]

===Tweeting Race Car===
[[Tweeting_Race_Car|Our race cars tweet autonomously while on the race track!]]

===Ignition Driver Modules===
[[IgnitionDrivers|Ignition driver boards for Coil On Plug and other applications]]

===Tachometer Adapter===
[[TachAdapter|Tachometer Adapter: Adapts Tachometer to multiple coil packs]]

===Megajolt2 Roadmap===
Info on our next generation [[Megajolt2|Megajolt2]] platform- testing in 2010!

===Autosport Labs R&D Platforms===
[[Research_and_Development_Platforms|Meet the test platforms we inflict our projects upon!]]
[[Image:240z_left_rear_3quarter_400px.jpg|right]]

===Lighting===
*[[Dual_LED_cluster|Dual LED Cluster]]
*[[Sequential_shift_light_array|Sequential Shift Light Array]]

===CPU Module===
The Autosport Labs CPU Module will be the heart of our future projects. This piece combines DIY friendliness with high speed high performance 32 bit processing power.
*[[CPU_Module|CPU Module]]

===Other Things===

*[[Handy_hints|Helpful Engineering Resources]]

RaceCapturePro2 QuickStart

2015-05-15T22:15:39Z

Rdoherty: /* Quick Start */

__FORCETOC__

== Prerequisites ==
* [https://race-capture.com/software/54aacf81183b3a6722000001 Download and install] the latest RaceCapture App
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 users''' - These drivers are unsigned. We are working on creating a signed driver set, but in the meantime you will need to disable the driver signing requirement for Windows 8. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]

== Quick Start ==

Watch our software installation video here: https://www.youtube.com/watch?v=oqveE2C1vo0

# Attach GPS and Bluetooth module (if purchased) to RaceCapture/Pro
# Plug in the supplied USB cable to RaceCapture/Pro and your computer.
# When prompted for drivers, select them from the zip file you unzipped previously.
## If not prompted or Windows does not ask you to locate drivers, open Device Manager, find RaceCapture/Pro (usually under 'Other devices'), right click and select 'Update Driver' software. Then select the folder containing the unzipped drivers you downloaded previously.
# Confirm you really want to install the drivers
# Open the RaceCapture application.
## You should see 'Reading Configuration' at the top of the window once the app detects RaceCapture/Pro.
# Click on 'Dashboard'
# Click on the bottom right arrow three times, which will display the digital dash. You should see the Utc and Interval channels changing, which means data is being transmitted over USB.
## '''Protip:''' Pick up the RaceCapture/Pro unit, move it around and observe changes from the internal accelerometer and gyro sensors!

[[File:Dash.png|500px]]

# You have now setup the RaceCapture app!

== Selecting your favorite race tracks==
RaceCapture/Pro can auto-detect and configure your favorite race tracks as soon as GPS lock is obtained.

# After connecting the RaceCapture app and verifying connectivity, navigate to the configuration view.
# Select the Race Tracks from the menu on the left.
# Search and select the race tracks you will be typically attending.
# Once the tracks have been selected, write the updated configuration using the [[Image:rc_appwrite_config.png]] button in the lower left.

When you arrive at the track and RaceCapture is powered up, it will automatically detect and configure the track's start/finish line and any available sectors.

ProTip: Periodically click the update button [[Image:update_from_cloud.png]] to pull down the latest set of race track configurations.

[[Image:RA_automatic_track_detection.png|500px]]

== Setting up Bluetooth ==
===Enabling Bluetooth in firmware settings===
# Complete the Quick Start steps above, leaving RaceCapture/Pro connected to your computer
# Connect the Bluetooth module to the inner of the two RaceCapture/Pro ports on the same side the USB cable connects to
# Open the Race Capture app
# Click on the top left 'Menu' button
# Click on 'Configuration'
# Click on 'Wireless' in the list of options on the left
# Click the toggle to the right of 'Bluetooth' <br> [[File:Bt.png|500px]]
# Click the 'Write Config' button on the bottom left (down array pointing to a RaceCapture/Pro)

===Set up Android tablet/phone===
==Requirements==
For best performance, we recommend the following minimum specification:
* Android 4.4 and higher
* Quad core 1.6 GHz processor
* 2 GB RAM, 8 GB flash
* 1024x600 resolution, IPS display
* 7" or 10" screen

Recommended Brands for tablets:
* Samsung
* Google Nexus
* LG
* Lenovo

==Touch screen operation with gloves==
We recommend [http://http://www.amazon.com/AnyGlove-TM-Synthetic-Touchscreen-Compatible/dp/B00AB3EVOW AnyGlove] to make your racing gloves touch screen compatible.

==Bluetooth pairing==
# Go into the Android settings and pair your device with the RaceCapture/Pro Bluetooth module
## Ensure Bluetooth is turned on in the Android device settings.
## Ensure the RaceCapture/Pro Bluetooth module is powered on (green light is flashing)
## Default password is 1234
# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
## The green light on the Bluetooth module should be solid and not flashing

===Verify connectivity===
# Swipe to the digital dash screen and you should see values changing. Pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

RaceCapturePro2 QuickStart

2015-05-12T20:01:38Z

Rdoherty: /* Prerequisites */

__FORCETOC__

== Prerequisites ==
* [https://race-capture.com/software/54aacf81183b3a6722000001 Download and install] the latest RaceCapture App
* Download and unzip drivers: [https://autosportlabs-software.s3-us-west-2.amazonaws.com/RaceCapturePro_drivers_winXPVista7_V2.zip Windows XP/Vista/7/8 Drivers V2]
** '''Note for Windows 8 users''' - These drivers are unsigned. We are working on creating a signed driver set, but in the meantime you will need to disable the driver signing requirement for Windows 8. [https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/disabling-signed-driver-enforcement-on-windows-8 Instructions]

== Quick Start ==

# Attach GPS and Bluetooth module (if purchased) to RaceCapture/Pro
# Plug in the supplied USB cable to RaceCapture/Pro and your computer.
# When prompted for drivers, select them from the zip file you unzipped previously.
## If not prompted or Windows does not ask you to locate drivers, open Device Manager, find RaceCapture/Pro (usually under 'Other devices'), right click and select 'Update Driver' software. Then select the folder containing the unzipped drivers you downloaded previously.
# Confirm you really want to install the drivers
# Open the RaceCapture application.
## You should see 'Reading Configuration' at the top of the window once the app detects RaceCapture/Pro.
# Click on 'Dashboard'
# Click on the bottom right arrow three times, which will display the digital dash. You should see the Utc and Interval channels changing, which means data is being transmitted over USB.
## '''Protip:''' Pick up the RaceCapture/Pro unit, move it around and observe changes from the internal accelerometer and gyro sensors!

[[File:Dash.png|500px]]

# You have now setup the RaceCapture app!

== Selecting your favorite race tracks==
RaceCapture/Pro can auto-detect and configure your favorite race tracks as soon as GPS lock is obtained.

# After connecting the RaceCapture app and verifying connectivity, navigate to the configuration view.
# Select the Race Tracks from the menu on the left.
# Search and select the race tracks you will be typically attending.
# Once the tracks have been selected, write the updated configuration using the [[Image:rc_appwrite_config.png]] button in the lower left.

When you arrive at the track and RaceCapture is powered up, it will automatically detect and configure the track's start/finish line and any available sectors.

ProTip: Periodically click the update button [[Image:update_from_cloud.png]] to pull down the latest set of race track configurations.

[[Image:RA_automatic_track_detection.png|500px]]

== Setting up Bluetooth ==
===Enabling Bluetooth in firmware settings===
# Complete the Quick Start steps above, leaving RaceCapture/Pro connected to your computer
# Connect the Bluetooth module to the inner of the two RaceCapture/Pro ports on the same side the USB cable connects to
# Open the Race Capture app
# Click on the top left 'Menu' button
# Click on 'Configuration'
# Click on 'Wireless' in the list of options on the left
# Click the toggle to the right of 'Bluetooth' <br> [[File:Bt.png|500px]]
# Click the 'Write Config' button on the bottom left (down array pointing to a RaceCapture/Pro)

===Set up Android tablet/phone===
==Requirements==
For best performance, we recommend the following minimum specification:
* Android 4.4 and higher
* Quad core 1.6 GHz processor
* 2 GB RAM, 8 GB flash
* 1024x600 resolution, IPS display
* 7" or 10" screen

Recommended Brands for tablets:
* Samsung
* Google Nexus
* LG
* Lenovo

==Touch screen operation with gloves==
We recommend [http://http://www.amazon.com/AnyGlove-TM-Synthetic-Touchscreen-Compatible/dp/B00AB3EVOW AnyGlove] to make your racing gloves touch screen compatible.

==Bluetooth pairing==
# Go into the Android settings and pair your device with the RaceCapture/Pro Bluetooth module
## Ensure Bluetooth is turned on in the Android device settings.
## Ensure the RaceCapture/Pro Bluetooth module is powered on (green light is flashing)
## Default password is 1234
# Install the Race Capture app on your Android device from the [https://play.google.com/store/apps/details?id=com.autosportlabs.racecapture&hl=en Google Play Store]
# Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
# Tap the Bluetooth icon at the top right <br> [[File:Selectbt.png|500px]]
# Select RaceCapture/Pro <br> [[File:Selectrcp.png|500px]]
# After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
## The green light on the Bluetooth module should be solid and not flashing

===Verify connectivity===
# Swipe to the digital dash screen and you should see values changing. Pick up your RaceCapture/Pro and move it around, you should see even more sensors changing! <br> [[File:Digtalbt.png|500px]]

RaceCapture-Pro MK2

2015-05-12T18:19:43Z

Rdoherty: /* Getting Started */

=RaceCapture/Pro Quick Links=
* [[Image:add_to_cart.png|link=http://www.autosportlabs.com/racecapturepro-2/]]

==Getting Started==
*'''[[RaceCapturePro2_QuickStart|First time setup]]'''

*'''[[RaceCapturePro2_OBD2|How to: enable OBD2 channels]]'''
*'''[[RaceCapturePro2_Calibrate_Sensor|How to: calibrate and configure an analog sensor]]'''
*'''[[RaceCapturePro2_RPM|How to: Connect RPM]]'''
*'''[[RaceCapturePro2_Enable_Predictive_Timing|How to: enable Predictive Timing]]'''
*'''[[RaceCapturePro2_TelemetryQuickstart|How to: set up telemetry]]'''
*'''[[RaceCapturePro2_ShiftLights|How to: sequential shift lights]]'''
*'''[[RaceCapturePro2_GPS|How to: get best GPS data]]'''

*[[RaceCapturePro_FAQ|More FAQs and How-To's"]]

*'''[[RaceCapture_App_User%27s_Guide|RaceCapture App User's Guide]]
*'''[https://race-capture.com/software Software and Firmware downloads]'''
*'''[[RaceCapturePro_Sensors|Sensor Guide]]'''
*'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''
*[https://github.com/autosportlabs Source code]
*[[RaceTracks|List of supported Race Tracks and Track Maps]]
*[[RCP_CAN|CAN Integration support]]

===Previous Hardware Versions===
[[RaceCapturePro-MK1|RaceCapture/Pro MK1]]

=Quick Reference=
Download a [http://www.autosportlabs.com/racecapturepro-mk2-quick-reference/racecapture-pro-mk2-quick-reference-sheet printable PDF]

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

=RaceCapture/Pro MK2 Specifications=

{| class="wikitable" style="text-align: left"
!colspan="2"|Input / Output Channels
|-
!colspan="2"|'''Analog Inputs'''
|-
|Channels
|8 (battery voltage dedicated on channel 8)
|-
|Voltage range
|0-5v
|-
|Input impedance
|1M ohm
|-
|Voltage protection
|400v (intermittent)
|-
|ADC precision
|12 bit
|-
|Maximum sample rate
|1000Hz
|-
|Mapping
|Raw / Linear formula / Interpolated map
|-
!colspan="2"|'''Digital I/O'''
|-
|Channels
|3
|-
|Output mode type
|Open drain
|-
|Output current capacity
|1A, inductive clamped
|-
|Input mode voltage range
|0-12v
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''Timer Inputs (RPM / Frequency)'''
|-
|Channels
|3
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''PWM/Analog outputs'''
|-
|Channels
|4
|-
|PWM output type
|push/pull
|-
|PWM output voltage range
|5v
|-
|Output current capacity
|50mA
|-
|Analog Output
|0-5v
|-
!colspan="2"|Voltage Reference
|-
|Output Voltage/Capacity
|5v / 1A
|-
!colspan="2"|Connectivity
|-
!colspan="2"|'''CAN Bus'''
|-
|CAN Channels
|2
|-
|CAN baud rate
|125K, 250K, 500K, 1M baud
|-
|CAN filters
|14 per channel
|-
|Protocol support
|OBDII PID, custom CAN messaging
|-
!colspan="2"|'''Telemetry/Wireless'''
|-
|Cellular
|Quad-band GSM (internal module, optional)
|-
|Bluetooth
|Bluetooth 2.0 (external module, optional)
|-
|Serial
|Type External RJ11
|-
|Max Baud Rate
|230400
|-
!colspan="2"|Inertial Motion Unit
|-
|Accelerometer Channels
|3 (X/Y/Z) (2G, 4G capable)
|-
|Gyro
|3 (Yaw/Pitch/Roll) (1000 degrees/sec)
|-
|Magnetic compass
|1 (Bearing) (device capable of 3)
|-
!colspan="2"|GPS
|-
|GPS Type
|External active antenna
|-
|GPS Maximum sample rate
|50Hz
|-
|GPS accuracy
|2.5M CEP
|-
!colspan="2"|Storage
|-
|Micro SD
|Up to 32GB (SDHC)
|-
!colspan="2"|Configuration Capacity
|-
|Auto-detect track database
|240
|-
|Sectors per track
|20
|-
|Channel support
|200
|-
!colspan="2"|Physical
|-
|Dimensions
|5.3″ (w) x 4.2″ (h) x 1.2″ (tall) / 135x110x31 mm(est)
|-
|Weight
|9oz / 255gm (est)
|-
|Temperature
| Max Internal Temperature while operating: -40°C ~ 85°C / -40°C ~ 80°C (Telemetry module)
|}

[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]

RaceCapture-Pro MK2

2015-05-12T18:19:22Z

Rdoherty: /* RaceCapture/Pro Quick Links */

=RaceCapture/Pro Quick Links=
* [[Image:add_to_cart.png|link=http://www.autosportlabs.com/racecapturepro-2/]]

==Getting Started==
*'''[[RaceCapturePro2_QuickStart|First time setup]]'''

*'''[[RaceCapturePro2_OBD2|How to: enable OBD2 channels]]'''
*'''[[RaceCapturePro2_Calibrate_Sensor|How to: calibrate and configure an analog sensor]]'''
*'''[[RaceCapturePro2_RPM|How to: Connect RPM]]'''
*'''[[RaceCapturePro2_Enable_Predictive_Timing|How to: enable Predictive Timing]]'''
*'''[[RaceCapturePro2_TelemetryQuickstart|How to: set up telemetry]]'''
*'''[[RaceCapturePro2_ShiftLights|How to: sequential shift lights]]'''
*'''[[RaceCapturePro2_GPS|How to: get best GPS data]]'''

*[[RaceCapturePro_FAQ|More FAQs and How-To's"]]

*'''[[RaceCapture_App_User%27s_Guide|RaceCapture App User's Guide]]
*'''[http://race-capture.com/software Software and Firmware downloads]'''
*'''[[RaceCapturePro_Sensors|Sensor Guide]]'''
*'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''
*[https://github.com/autosportlabs Source code]
*[[RaceTracks|List of supported Race Tracks and Track Maps]]
*[[RCP_CAN|CAN Integration support]]

===Previous Hardware Versions===
[[RaceCapturePro-MK1|RaceCapture/Pro MK1]]

=Quick Reference=
Download a [http://www.autosportlabs.com/racecapturepro-mk2-quick-reference/racecapture-pro-mk2-quick-reference-sheet printable PDF]

[[Image:RaceCapture-Pro MK2 quick reference sheet.jpg]]

=RaceCapture/Pro MK2 Specifications=

{| class="wikitable" style="text-align: left"
!colspan="2"|Input / Output Channels
|-
!colspan="2"|'''Analog Inputs'''
|-
|Channels
|8 (battery voltage dedicated on channel 8)
|-
|Voltage range
|0-5v
|-
|Input impedance
|1M ohm
|-
|Voltage protection
|400v (intermittent)
|-
|ADC precision
|12 bit
|-
|Maximum sample rate
|1000Hz
|-
|Mapping
|Raw / Linear formula / Interpolated map
|-
!colspan="2"|'''Digital I/O'''
|-
|Channels
|3
|-
|Output mode type
|Open drain
|-
|Output current capacity
|1A, inductive clamped
|-
|Input mode voltage range
|0-12v
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''Timer Inputs (RPM / Frequency)'''
|-
|Channels
|3
|-
|Input voltage protection
|400v (intermittent)
|-
|Maximum sample rate
|1000Hz
|-
!colspan="2"|'''PWM/Analog outputs'''
|-
|Channels
|4
|-
|PWM output type
|push/pull
|-
|PWM output voltage range
|5v
|-
|Output current capacity
|50mA
|-
|Analog Output
|0-5v
|-
!colspan="2"|Voltage Reference
|-
|Output Voltage/Capacity
|5v / 1A
|-
!colspan="2"|Connectivity
|-
!colspan="2"|'''CAN Bus'''
|-
|CAN Channels
|2
|-
|CAN baud rate
|125K, 250K, 500K, 1M baud
|-
|CAN filters
|14 per channel
|-
|Protocol support
|OBDII PID, custom CAN messaging
|-
!colspan="2"|'''Telemetry/Wireless'''
|-
|Cellular
|Quad-band GSM (internal module, optional)
|-
|Bluetooth
|Bluetooth 2.0 (external module, optional)
|-
|Serial
|Type External RJ11
|-
|Max Baud Rate
|230400
|-
!colspan="2"|Inertial Motion Unit
|-
|Accelerometer Channels
|3 (X/Y/Z) (2G, 4G capable)
|-
|Gyro
|3 (Yaw/Pitch/Roll) (1000 degrees/sec)
|-
|Magnetic compass
|1 (Bearing) (device capable of 3)
|-
!colspan="2"|GPS
|-
|GPS Type
|External active antenna
|-
|GPS Maximum sample rate
|50Hz
|-
|GPS accuracy
|2.5M CEP
|-
!colspan="2"|Storage
|-
|Micro SD
|Up to 32GB (SDHC)
|-
!colspan="2"|Configuration Capacity
|-
|Auto-detect track database
|240
|-
|Sectors per track
|20
|-
|Channel support
|200
|-
!colspan="2"|Physical
|-
|Dimensions
|5.3″ (w) x 4.2″ (h) x 1.2″ (tall) / 135x110x31 mm(est)
|-
|Weight
|9oz / 255gm (est)
|-
|Temperature
| Max Internal Temperature while operating: -40°C ~ 85°C / -40°C ~ 80°C (Telemetry module)
|}

[[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]