RaceCapture App User's Guide: Difference between revisions

(filled in more config views)
(48 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The RaceCapture/Pro V2 firmware and app represents a major upgrade to the capabilities of the original RaceCapture/Pro system.
The RaceCapture/Pro V2 firmware and app represents a major upgrade to the capabilities of the original RaceCapture/Pro system.


==What's New==
Currently supported platforms:
 
* Windows: currently supported
* Linux: currently supported by running from source
* OSX - beta support
 
Planned support:
 
* Android: Beta available, contact us a [email protected] 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===
==Multi-Platform, touch oriented application==
Capable of running on Windows, OS X, Linux, iOS and Android, the new RaceCapture app will ultimately combine RaceAnalyzer and the current Mobile app into a unified configuration, dashboard and analysis solution.
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_home_screen6.png|500px]]
Line 12: Line 33:
[[Image:RA_automatic_track_detection.png|500px]]
[[Image:RA_automatic_track_detection.png|500px]]


With this beta/preview release the RaceCapture app will initially support configuration for RaceCapture/Pro system running the V2 firmware. Dashboard and then Analysis features will follow to make the official application launch.
==Automatic Track Detection and configuration==
 
===Automatic Track Detection and configuration===
[[Image:rc_track_browse4.png|right|thumb|300px]]
[[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.
The RaceCapture/Pro firmware supports automatic track detection and configuration, supporting up to 40 of your favorite race tracks.
Line 24: Line 43:
Automatic configuration can still be disabled and manual start/finish and sector points can be defined.
Automatic configuration can still be disabled and manual start/finish and sector points can be defined.


===Multi-Sector Timing===
==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:
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
* sectorTime - indicates the time of the last completed sector
* sector - indicates the last completed sector  
* sector - indicates the last completed sector  


===Separate Start/Finish Lines===
==Separate Start/Finish Lines==
''Not yet implemented''
 
To enable auto-x/rally/hillclimb scenarios we've enabled the ability to define a separate start and finish line.  
To enable auto-x/rally/hillclimb scenarios we've enabled the ability to define a separate start and finish line.  


Line 37: Line 73:
The completion of a lap is detected using the conventional GPS target detection mechanism.
The completion of a lap is detected using the conventional GPS target detection mechanism.


===Predictive Lap Timing===
==Predictive Lap Timing==
 
A new predictive lap timing algorithm augments current 'lapTime' channel with a new channel called 'predTime'.  
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.
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.


===Streamlined Sensor and Channel Configuration===
==CAN bus expansion==
[[Image:GPS_Channel_config.png|right|thumb|300px]]
Channel configuration has been simplified where possible with additional default settings that make sense.  Automatic channel configuration wizards will help auto-calibrate things like throttle position, fuel level and and steering angle sensors.
 
===CAN bus expansion===
[[Image:CAN_configuration.png|right|thumb|300px]]
[[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.  
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.  
Line 55: Line 86:
CAN send and receive commands are made available via Lua scripting and can be combined with the Virtual Channel feature.
CAN send and receive commands are made available via Lua scripting and can be combined with the Virtual Channel feature.


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


Line 62: Line 93:
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.
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.


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


Line 71: Line 100:
* A calculated 'engine load' indicator by integrating RPM + Manifold Pressure Sensor value.
* A calculated 'engine load' indicator by integrating RPM + Manifold Pressure Sensor value.


(link to Lua scripting reference, add code example)
[[RaceCapturePro_Lua_Scripting#CAN_Bus_functions|Lua Scripting CAN bus API]]
 
==Lua Scripting==
Lua Scripting stability, error recovery and logging has been improved.


===Channel Filtering===
* Use the print() and println() to print out log messages which will show up in the scripting view. Great for debugging.
Analog, Timer and Accelerometer channels feature an adjustable dampening filter that allows you to smooth out sensor readings as needed. Examples of this use:
* 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.


* Filtering accelerometer readings for rough environments
Read more in our [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]
* Averaging fuel level readings to compensate for fuel tank slosh


===Channel Customization===
==Improved log timing accuracy==
[[Image:channels_view_editing.png|thumb|right|300px]]
The core sample rate tick is now derived directly from the system's crystal-backed oscillator, making log file sample rates much more accurate.
The concept of a channel has been formalized into a set of universal system level channels where min/max and unit labels can be customized. Additionally, user-defined channels can be defined for special purpose channels.
 
==Upcoming==
=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.  
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===
==Dashboard==
[[Image:tacho_gauge_10k.png|thumb|right|300px]]
[[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:
The dashboard view will feature most, if not all,, of the same informational views as the current RaceCapture mobile app, including:
Line 95: Line 127:
* Lap Time + real-time accelerometer + gyro view
* Lap Time + real-time accelerometer + gyro view


===Analysis===
=Installation=
The analysis mode will feature the ability to analyze data on a lap by lap basis, with the ability to compare different laps.
 
* Line charts showing channels over distance, with the ability to combine multiple channels into a single chart
* GPS plots showing the line taken in reference to the center line of the track map
* Sector times for each part of the track
 
 
==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.
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.


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


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


Line 118: Line 142:
(screenshot of firmware flashing progress)
(screenshot of firmware flashing progress)


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


Currently supported platforms:
=Running=
* Windows: currently supported
* Linux: currently supported by running from source
* OS X: experimental support - USB interface for RaceCapture/Pro does not yet work.
* Android: under development
* iOS: under development
 
==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.
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==
=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.
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===
==Reading / Writing / Saving / Opening configuration==
[[Image:RA_AnalogChannelsView_headers.png|500px]]
[[Image:RA_AnalogChannelsView_headers.png|500px]]


Line 141: Line 158:
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.
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===
==Auto track detection==
[[Image:RA_automatic_track_detection.png|500px]]
[[Image:RA_automatic_track_detection.png|500px]]


Line 150: Line 167:
Search for your favorite tracks by name and add them to the list.
Search for your favorite tracks by name and add them to the list.


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


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


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


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


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


Line 184: Line 201:
** For RPM mode This value is typically set based on the number of cylinders and the number of coil packs used on the engine
** 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===
==Digital In/Out==
[[Image:ra_gpio_config_view.png|500px]]
[[Image:ra_gpio_config_view.png|500px]]


Line 193: Line 210:
* '''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.
* '''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===
==Accelerometer/Gyro==
[[Image:rc_app_accelerometer_config_view.png]]
[[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.


Configure the Accelerometer / Gyro with this view. Edit channel mappings, orientation and zero levels.  
==OBD II==
[[Image:OBDII_view.png|500px]]


===Pulse/Analog Out===
You can create OBDII channels and query standard OBD2 PIDs over a compatible OBD2 CAN bus link.


===CAN Bus===
'''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.


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


===Wireless===
'''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===
===Telemetry===


===Scripting===
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]]


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

Revision as of 20:31, 2 June 2016

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:

Downloads

Get the latest firmware and app from the Downloads Page

Discussion Forums

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

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.

RA home screen6.png RA AnalogChannelsView headers.png

Tacho gauge 10k.png RA automatic track detection.png

Automatic Track Detection and configuration

Rc track browse4.png

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 [email protected] 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

Manual track config.jpg Manual track config points.png

  • 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

CAN configuration.png

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

OBDII view.png

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.

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

Tacho gauge 10k.png

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

RA AnalogChannelsView headers.png

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

RA automatic track detection.png

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

GPS Channel config.png

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

RA AnalogChannelsView headers.png

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

Rc app pulse rpm input.png

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

Ra gpio config view.png

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

Rc app accelerometer config view.png

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

Pulse/Analog Out

Rc app pwm analog out config.png

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

CAN configuration.png

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

OBD II

OBDII view.png

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

Wirelessconfig.png

Bluetooth

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

  1. Install the Race Capture app on your Android device from the Google Play Store
  2. Turn on Bluetooth on your tablet and pair with RaceCapture/Pro, password is 1234
  3. Open the RaceCapture app, tap the screen until the RaceCapture logo show up at the top.
  4. Tap the Bluetooth icon at the top right
    Selectbt.png
  5. Select RaceCapture/Pro
    Selectrcp.png
  6. After a few seconds you should see a 'Connected to RaceCapture/Pro' message and data will be transmitting to your tablet.
  7. 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!
    Digtalbt.png

Telemetry

For detailed setup instructions read our Telemetry Quickstart

Scripting

Luascripting.png

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 Lua Scripting Guide

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