RaceCapturePro Lua Scripting Examples - Revision history

Brentp: /* Send a CAN message with two different Channel values */

2025-08-20T21:20:48Z

Send a CAN message with two different Channel values

← Older revision		Revision as of 21:20, 20 August 2025
Line 986:		Line 986:
	* Standard (11 bit) CAN identifier		* Standard (11 bit) CAN identifier
	* CAN1 channel is used		* CAN1 channel is used

			'''Note''': This script will generate an error if the specified channel names do not exist

	function onTick()		function onTick()

Brentp: /* Send A CAN message with a temperature value */

2025-08-20T21:19:44Z

Send A CAN message with a temperature value

← Older revision		Revision as of 21:19, 20 August 2025
Line 966:		Line 966:

	==Send A CAN message with a temperature value==		==Send A CAN message with a temperature value==
	~~''available in future Firmware version 2.0''~~

	Given:		Given:
	* Analog 0 reads a calibrated temperature value between 0 and 255		* Analog 0 reads a calibrated temperature value between 0 and 255
	* Destination CAN device is looking for a message with ID 1234		* Destination CAN device is looking for a message with ID 1234
	* Standard (11 bit) CAN ~~identifer~~		* Standard (11 bit) CAN identifier
	* CAN1 channel is used		* CAN1 channel is used

	function onTick()		function onTick()
	local ~~tmp~~ = getAnalog(0)		local value = getAnalog(0)
	local msg = {~~tmp~~}		local msg = {value}
	txCAN(0, 1234, 0, msg)		txCAN(0, 1234, 0, msg)
	end		end

			==Send a CAN message with two different Channel values==

			Given:
			* Reading two channels with a specific name
			* Destination CAN device is looking for a message with ID 1234
			* Standard (11 bit) CAN identifier
			* CAN1 channel is used

			function onTick()
			local heartRate = getChannel("HeartRate")
			local driver = getChannel("Driver")
			local msg = {heartRate, driver}
			txCAN(0, 1234, 0, msg)
			end

	==Use RCP as a general purpose CAN data logger==		==Use RCP as a general purpose CAN data logger==

Brentp: /* Filtering a channel */

2025-01-16T15:16:07Z

Filtering a channel

← Older revision		Revision as of 15:16, 16 January 2025
Line 370:		Line 370:

	-- create the filtered channel		-- create the filtered channel
	-- 10Hz, 0 precision, min/max -300/-300		-- 10Hz, 0 precision, min/max -300/300
	filter_yaw_id = addChannel("FYaw", 10, 0, -300, 300)		filter_yaw_id = addChannel("FYaw", 10, 0, -300, 300)

Brentp: /* Virtual Channels (AKA Math Channels) */

2025-01-16T15:09:02Z

Virtual Channels (AKA Math Channels)

← Older revision		Revision as of 15:09, 16 January 2025
Line 351:		Line 351:

	=Virtual Channels (AKA Math Channels)=		=Virtual Channels (AKA Math Channels)=

			==Filtering a channel==
			This scripts uses an exponential moving average filter to smooth the rate of a channel. Here, we're using the Yaw channel as input.

			<pre>
			setTickRate(10)

			local function ema_filter(alpha)
			local ema = nil -- Initialize EMA value as nil
			return function(new_value)
			ema = (ema == nil) and new_value or (alpha * new_value + (1 - alpha) * ema)
			return ema
			end
			end

			alpha = 0.1 -- Smoothing factor (between 0 and 1)
			ema = ema_filter(alpha)

			-- create the filtered channel
			-- 10Hz, 0 precision, min/max -300/-300
			filter_yaw_id = addChannel("FYaw", 10, 0, -300, 300)

			function onTick()
			setChannel(filter_yaw_id, ema(getChannel("Yaw")))
			end
			</pre>

	==Averaging a fuel level reading or other sensor==		==Averaging a fuel level reading or other sensor==

Brentp: /* Integrate with RaceVoice via CAN */

2024-12-05T02:18:01Z

Integrate with RaceVoice via CAN

Show changes

Brentp: /* Average two sensor values and set to a virtual channel */

2024-01-25T19:50:43Z

Average two sensor values and set to a virtual channel

← Older revision		Revision as of 19:50, 25 January 2024
Line 408:		Line 408:

	function onTick()		function onTick()
	local a1 = ~~getAnalog~~(0)		local a1 = getChannel("ch1")
	local a2 = ~~getAnalog~~(1)		local a2 = getChannel("ch2")
	setChannel(avgId, (a1 + a2) / 2)		setChannel(avgId, (a1 + a2) / 2)
	end		end

Sbarton: /* Display OBDII Codes as a channel and allow driver to reset the OBDII Codes with a button */

2020-06-08T16:26:48Z

Display OBDII Codes as a channel and allow driver to reset the OBDII Codes with a button

← Older revision		Revision as of 16:26, 8 June 2020
Line 95:		Line 95:

	==Display OBDII Codes as a channel and allow driver to reset the OBDII Codes with a button==		==Display OBDII Codes as a channel and allow driver to reset the OBDII Codes with a button==
	This script creates a virtual channel called OBDIICodes and sets it to the first OBDII Trouble Code found (It will not have the alpha prefix (Ie P, C , B, or U), but will just have up to 4 digits. You can then use these digits to figure out the P code. Ie, if 155 is returned, your OBDII code would be P0155. If -1 is shown for the OBDIICodes channel that means RaceCapture has not received any codes from the ECU yet. If 0 is shown for OBDIICodes channel that means the ECU sent back P0000 which means there are no OBDII trouble codes in the ECU. This channel will be logged and sent via telemetry just like a regular channel. If more than one OBDII code is found, it will cycle setting the OBDIICodes channel to the first 2-3 OBDII codes that were returned. It will cycle to the next code every couple of seconds.		This script creates a virtual channel called ''OBDIICodes'' and sets it to the first OBDII Trouble Code found (It will not have the alpha prefix (Ie P, C , B, or U), but will just have up to 4 digits. You can then use these digits to figure out the P code. Ie, if 155 is returned, your OBDII code would be P0155. If -1 is shown for the ''OBDIICodes'' channel that means RaceCapture has not received any codes from the ECU yet. If 0 is shown for ''OBDIICodes'' channel that means the ECU sent back P0000 which means there are no OBDII trouble codes in the ECU. This channel will be logged and sent via telemetry just like a regular channel. If more than one OBDII code is found, it will cycle setting the ''OBDIICodes'' channel to the first 2-3 OBDII codes that were returned. It will cycle to the next code every couple of seconds.

	I also added the ability for the driver to reset the OBDII Trouble codes using an external button. This button needs to be mapped to an Analog or GPIO channel called ClearOBD. It will reset the vehicle's OBDII codes and reset the OBDIICodes channel to -1.		I also added the ability for the driver to reset the OBDII Trouble codes using an external button. This button needs to be mapped to an Analog or GPIO channel called ''ClearOBD''. It will reset the vehicle's OBDII codes and reset the ''OBDIICodes'' channel to -1.

	[[Image:ClearOBDChannel.png\|500px]]		[[Image:ClearOBDChannel.png\|500px]]

Sbarton: /* Spoof AIM data logger in order to use AIM SmartyCam alone with Race Capture */

2020-05-22T13:44:27Z

Spoof AIM data logger in order to use AIM SmartyCam alone with Race Capture

← Older revision		Revision as of 13:44, 22 May 2020
Line 1,199:		Line 1,199:

	==Spoof AIM data logger in order to use AIM SmartyCam alone with Race Capture ==		==Spoof AIM data logger in order to use AIM SmartyCam alone with Race Capture ==
	If you want to add video with automatic data overlay, you can use an AIM SmartyCam. Normally this has to be connected to an AIM data logging system in order for it to get the data to overlay onto the video.		If you want to add video with automatic data overlay, you can use an [https://www.bimmerworld.com/AiM-SmartyCam-HD-Camera-System-84-Deg-Lens.html AIM SmartyCam]. Normally this has to be connected to an AIM data logging system in order for it to get the data to overlay onto the video.
	We will use the CAN transmit ability of the Race Capture devices to spoof an AIM data logger and send our RCP sensor data (or RCT OBDII data) over to the AIM SmartyCam.		We will use the CAN transmit ability of the Race Capture devices to spoof an AIM data logger and send our RCP sensor data (or RCT OBDII data) over to the AIM SmartyCam.

			Note: For the AIM SmartyCAM HD Rev 1 with 5 pin connector you will just need an [https://www.autosportlabs.com/product/aim-dashboard-telemetry-cable/ ASL AIM to RCP cable]. If you have an original AIM SmartyCam or SmartyCam HD Rev 2 which have 7 pin connectors, you will also need an [https://www.bimmerworld.com/AiM-4-Way-Data-Hub.html AIM Data Hub]. You will plug your 7 pin to 5 pin cable you got with your original SmartyCam or SmartyCam HDrev2 into your SmartyCam and the other end (5 pin end) into the AIM Data Hub. You would then plug your ASL AIM to RCP cable into the RCP and the AIM Data Hub.
			These will communicate on CAN Channel 1 with a baud rate of 1M. Make those settings in the CAN Bus settings.

	<pre>		<pre>

Sbarton: /* CAN bus scripts */

2020-05-22T03:42:57Z

CAN bus scripts

Show changes

Sbarton: /* Integrate with RaceVoice via CAN */

2020-05-19T21:29:16Z

Integrate with RaceVoice via CAN

← Older revision		Revision as of 21:29, 19 May 2020
Line 1,196:		Line 1,196:
	''otherwise it will just keep saying Hello World! every 30 seconds. Delete that section if you don't want to send custom alerts or messages to RaceVoice.''		''otherwise it will just keep saying Hello World! every 30 seconds. Delete that section if you don't want to send custom alerts or messages to RaceVoice.''

	''Note: the message is limited to 16 characters. Only the first 16 characters will be spoken. You can send multiple messages if needed.''		''Note: the custom message is limited to 16 characters. Only the first 16 characters will be spoken. You can send multiple messages if needed.''

	=Serial Port=		=Serial Port=