Autosport Labs - User contributions [en]

RaceCapture on Raspberry Pi

2022-11-11T22:25:26Z

GTIspirit: /* Additional Tips */

=Introduction=

We designed the RaceCapture app to run nearly anywhere - even a Raspberry Pi. And now, for about $100 you can create a hardwired, dedicated dash for your RaceCapture system.

[[image:racecapture_raspberry_pi.jpg|1024px]]

==Benefits==
You get all of the benefits of a dedicated dash:
* '''Automatically runs upon power up''' - you can configure the dash to automatically launch the RaceCapture App - just as you'd expect it to work.
* '''Hard-wired data connection to RaceCapture''' - no wireless connections to configure, with the reliability of a direct wire.
* '''Runs on the bare metal''' - The RaceCapture app runs without Android or iOS; there's no other apps competing for resources, or compromising system stability.
* '''Overheating resistance''' - Your typical mobile device requires extra care in very hot weather to prevent damage to it's internal battery, and will shut down if overheated. With proper heat-sinking, the Raspberry Pi should handle the heat.

==Compatibility==
The RaceCapture app running on the Raspberry Pi is compatible with any hardware version of RaceCapture or PodiumConnect.

[[image:racecapture_raspberry_pi_backside.jpg|1024px]]

==Experimental!==
While the results are pretty great, these instructions are ''currently'' for those adventurous race car hackers who know their away around a command line, comfortable working with hardware and want to dig in. '''Think it's cool, but too much to tackle?''' Rope in your nearest computer/electronics geek - you need one on your race team, anyway. :) '''Or, just use the plug and play option''' and use an Android or iOS device via Bluetooth or WiFi.

==Current status and future plans==
Even though this is brand new and officially experimental in nature, we still made it as easy as reasonably possible: we wrapped up the RaceCapture App into as close to a self-running installer, that can run on a bone stock Raspberry Pi image - only a few changes are required to the default image, detailed below.

'''However''', in the near future we will create a dedicated Raspberry Pi image that you can burn to an SD card and simply boot up, and move towards more official support as we iron out the issues.

===Reporting issues and getting support===
Chances are you'll encounter an issue you'll want to report. Before you do that, [https://github.com/autosportlabs/RaceCapture_App/issues?q=is%3Aopen+is%3Aissue+label%3A%22raspberry+pi%22 check the issue log] to see if it's already known.

Otherwise - the best place for support, feedback and sharing success stories is [http://forum.autosportlabs.com on the forums] . Drop us a note there so we can see the progress of your project!

=Hardware Selection=
===Raspberry Pi===
We recommend the Raspberry Pi 4 2GB and higher for best performance and support.

===Display===
The RaceCapture app package is designed to recognize the following screens:

* [https://www.raspberrypi.org/products/raspberry-pi-touch-display/ Official Raspberry Pi display] with capacitive touch screen;
* Displays supporting the AR1100 resistive touch screen controller.

Other displays can work as well, and additional work may be needed to support the screen's touch controller. If unsure, just pick the [https://www.raspberrypi.org/products/raspberry-pi-touch-display/ Official Raspberry Pi display]
===Enclosure===
A recommended enclosure is the [http://https://www.amazon.com/dp/B01HV97F64 Smart Pi Touch Case]

You can 3D print a sun shade for this enclosure [[file:P001 Raspberry Pi Display Sun Shade.stl.zip|download the .stl file]] (''Courtesy of Michael Lee'')

[[image:SmartPi_touch_case.jpg|400px]] [[image:RaceCapture_Sun_shade_3dprinted_preview.jpg|400px]]

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

Installed on Dashboard

===Power Supply===
The Raspberry Pi dashboard requires its own power supply. You'll need a high quality 5v power supply with 2 amps minimum capacity; 3 amps is highly recommended, and ideally one with a low drop out voltage, so power is not cut to the Raspberry Pi when you're loading the main battery, such as when cranking the engine.

'''Suggested Power Supplies'''
* [https://www.amazon.com/Jabinco-LM2596-Converter-3-0-40V-1-5-35V/dp/B0817P8BGB/ Buck Converter based on the LM2596]

====Powering RaceCapture====
After you have power to the Raspberry Pi dashboard, you may notice your RaceCapture device will be powered by the USB cable connected to the Pi, just as if you're powering RaceCapture from your laptop. '''You will still want to power your RaceCapture via 12v'''; see the respective installation guides for information on how to power your device.

===Heat sinking===
If you're running in hot weather, we recommend the standard Raspberry Pi heatsink kit to keep your system cool.

For Pi4 users, we recommend active fan cooling in addition to the heat sink.

=Installation=
==Installing Rasbian OS==
At the moment we recommend Buster Lite - problems have been reported with later versions.

Download from [https://www.raspberrypi.org/downloads/raspbian/ download from the official site] and follow the instructions for burning to an SD card.

Once you've created your image, boot up your Raspberry Pi and log in with the default username of 'pi' and password 'raspberry'.

===Updating to latest packages===
It is always good form to update the latest packages after a fresh install. Enter this at the command line:
<pre>
sudo apt-get update
sudo apt-get dist-upgrade
</pre>

==Raspberry Pi support==
The RaceCapture app is compatible with Raspberry Pi 4 and 3.

===Enable GPU driver===
Enable Fake KMS under advanced boot options:

<pre>
sudo raspi-config
</pre>

Go to Advanced Options -> GL Driver -> Select OpenGL desktop driver with fake KMS

* Be sure to reboot after exiting raspi-config

==Installing dependencies==
===Activate ssh===
Ssh is used to store passwords used by the app. Steps to ensure it is running:

<pre>
sudo raspi-config
</pre>
Go under Interfacing Options or Advanced Options and start the ssh service.

Next, at the command prompt enter
<pre>
ssh-add
</pre>
to create at least one key.

===Install package dependencies===
<pre>
sudo apt-get install mesa-utils libgles2 libegl1-mesa libegl-mesa0
</pre>
===Change the default password===
For maximum security, change the password for the default user 'pi'

<pre>
> passwd
</pre>

and specify a new, secure password.

===Configure Raspberry Pi base settings===
====Enable Hardware rendering====
Enter the following line to enable hardware accelerated rendering.
<pre>
> sudo adduser pi render
</pre>
* '''Notes''':
** Without this setting, UI rendering will be extremely slow.
** Assumes RaceCapture is launched as pi. If not, replace pi with the user you are logging in as.
** If you're coming in to fix this after the fact, you'll need to reboot/re-login to take effect.

====Enable WiFi====
If you want network capability in addition to the ethernet connection, [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md enable and configure WiFi per the official documentation]

====(Optional) Enable SSH====
You can optionally enable SSH for remote management from the comfort of your main computer's keyboard and screen.

[https://www.raspberrypi.org/documentation/remote-access/ssh/ Enable and configure ssh per the official documentation]

====Install multi-touch tools====
Install the packages that enable multi-touch interfaces. Enter the following at the command line:

<pre>
> sudo apt-get install mtdev-tools
</pre>

====Configure memory split====
You'll need to bump up the memory made available to the GPU. Increase the default value of 64 to '''256'''.

* '''Via raspi-config tool'''
You can adjust the memory split by running the raspi-config tool. See the [https://www.raspberrypi.org/documentation/configuration/raspi-config.md official documentation]

* '''Editing /boot/config.txt'''

You can adjust the value directly by editing the /boot/config.txt file.

<pre>
> sudo nano /boot/config.txt
</pre>

Find the line containing gpu_mem=64 and change the number to 256

<pre>
gpu_mem=256
</pre>

''Save the file by pressing '''ctrl-x''' then press '''Y''' to confirm.''

==Installing the RaceCapture app package==

Download the latest [http://podium.live/software RaceCapture app package for Raspberry Pi] and place it in the /opt/ directory of the Raspberry Pi.

* '''Directly downloading to the Raspberry Pi'''
You can download it directly by getting the URL of the package by right-clicking the download link and copying the URL to your clipboard. Then, use it in the command below:

<pre>
cd /opt
sudo wget <package URL>
</pre>

===Extract the package===
Now extract the downloaded package :

<pre>
sudo tar -xjvf <downloaded file>
</pre>

===Launch the app===
Launch the RaceCapture app by running the following command:

<pre>
/opt/racecapture/run_racecapture.sh
</pre>

===Launching with Watchdog===
You can enable an automatic watchdog that re-launches the app in case a crash occurs.

<pre>
/opt/racecapture/run_racecapture.sh -w 1
</pre>

* '''Note:''' You can break out of the application by issuing '''Alt + PrntScn + k''' to the application.

You can further stop all racecapture processes by issuing the following command (e.g. via ssh)
<pre>
killall -9 run_racecapture
</pre>

===Enabling on screen keyboard===
If you don't have a wireless keyboard attached via usb, you can enable an on-screen keyboard.

Edit the kivy config.ini file with:
<pre>
sudo nano ~/.kivy/config.ini
</pre>

and update the keyboard_mode line with:

keyboard_mode = multi

==Automatic start upon power up==
To get the full dedicated dashboard experience, you can enable automatic launch of the RaceCapture app upon power up.

To do this, edit the system's startup file:

<pre>
sudo nano /etc/rc.local
</pre>

and add the following line '''before the exit 0''' line.

<pre>
/opt/racecapture/boot_racecapture.sh pi

exit 0
</pre>

''Save the file by pressing '''ctrl-x''' then press '''Y''' to confirm.''

=Connecting to your RaceCapture system=
[[image:racecapture_raspberry_pi_connections.jpg|900px]]
===Powering up===
* Connect the power to your display and power up.
* Connect your RaceCapture/Pro or RaceCapture/Track to the Raspberry Pi using the USB cable.

* Launch the RaceCapture app by running:

<pre>
/opt/racecapture/run_racecapture.sh
</pre>

If you have it set to launch automatically, simply let it start upon power-up.

===Connection and usage===

Once the RaceCapture App is running, it will connect automatically over USB. You can use the app just as you would on Android or iOS.

=Extra Features=

===Hardwire buttons===

The RaceCapture app responds to keyboard commands for certain behaviors. You can use a USB keyboard - or a device that emulates keyboard commands - to control the RaceCapture App.

Currently there are keyboard commands for the following:
* '''Navigating dashboard screens''' - Use the left and right arrow keys to switch between screens
* '''Escaping from screens / menus''' - The Escape key can be used to exit out of screens and options, just like the 'back' button on Android.
* '''Acknowledging alerts''' - Use the following keys to acknowledge alerts, including responding to pit-to-car alerts:
** K : to indicate 'Yes' or 'OK'
** N : to indicate 'No"

=Additional Tips=
See this link for additional tips on how to setup the Pi and speed up the boot times. This should be especially helpful for beginners.

https://wiki.autosportlabs.com/Raspberry_Pi_Tips

Logfiles for troubleshooting can be found at

/home/pi

RaceCapture on Raspberry Pi

2021-12-21T22:54:16Z

GTIspirit: /* Enabling on screen keyboard */

=Introduction=

We designed the RaceCapture app to run nearly anywhere - even a Raspberry Pi. And now, for about $100 you can create a hardwired, dedicated dash for your RaceCapture system.

[[image:racecapture_raspberry_pi.jpg|1024px]]

==Benefits==
You get all of the benefits of a dedicated dash:
* '''Automatically runs upon power up''' - you can configure the dash to automatically launch the RaceCapture App - just as you'd expect it to work.
* '''Hard-wired data connection to RaceCapture''' - no wireless connections to configure, with the reliability of a direct wire.
* '''Runs on the bare metal''' - The RaceCapture app runs without Android or iOS; there's no other apps competing for resources, or compromising system stability.
* '''Overheating resistance''' - Your typical mobile device requires extra care in very hot weather to prevent damage to it's internal battery, and will shut down if overheated. With proper heat-sinking, the Raspberry Pi should handle the heat.

==Compatibility==
The RaceCapture app running on the Raspberry Pi is compatible with any hardware version of RaceCapture or PodiumConnect.

[[image:racecapture_raspberry_pi_backside.jpg|1024px]]

==Experimental!==
While the results are pretty great, these instructions are ''currently'' for those adventurous race car hackers who know their away around a command line, comfortable working with hardware and want to dig in. '''Think it's cool, but too much to tackle?''' Rope in your nearest computer/electronics geek - you need one on your race team, anyway. :) '''Or, just use the plug and play option''' and use an Android or iOS device via Bluetooth or WiFi.

==Current status and future plans==
Even though this is brand new and officially experimental in nature, we still made it as easy as reasonably possible: we wrapped up the RaceCapture App into as close to a self-running installer, that can run on a bone stock Raspberry Pi image - only a few changes are required to the default image, detailed below.

'''However''', in the near future we will create a dedicated Raspberry Pi image that you can burn to an SD card and simply boot up, and move towards more official support as we iron out the issues.

===Reporting issues and getting support===
Chances are you'll encounter an issue you'll want to report. Before you do that, [https://github.com/autosportlabs/RaceCapture_App/issues?q=is%3Aopen+is%3Aissue+label%3A%22raspberry+pi%22 check the issue log] to see if it's already known.

Otherwise - the best place for support, feedback and sharing success stories is [http://forum.autosportlabs.com on the forums] . Drop us a note there so we can see the progress of your project!

=Hardware Selection=
===Raspberry Pi===
RaceCapture currently requires the Raspberry Pi 3: [https://www.raspberrypi.org/products/raspberry-pi-3-model-b/ Raspberry Pi 3].

It is not yet compatible with the Pi 4, due to extensive changes in the graphics subsystem. Expect to see Pi 4 support in the 2.0 version of the app.

===Display===
The RaceCapture app package is designed to recognize the following screens:

* [https://www.raspberrypi.org/products/raspberry-pi-touch-display/ Official Raspberry Pi display] with capacitive touch screen;
* Displays supporting the AR1100 resistive touch screen controller.

Other displays can work as well, and additional work may be needed to support the screen's touch controller. If unsure, just pick the [https://www.raspberrypi.org/products/raspberry-pi-touch-display/ Official Raspberry Pi display]
===Enclosure===
A recommended enclosure is the [http://https://www.amazon.com/dp/B01HV97F64 Smart Pi Touch Case]

You can 3D print a sun shade for this enclosure [[file:P001 Raspberry Pi Display Sun Shade.stl.zip|download the .stl file]] (''Courtesy of Michael Lee'')

[[image:SmartPi_touch_case.jpg|400px]] [[image:RaceCapture_Sun_shade_3dprinted_preview.jpg|400px]]

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

Installed on Dashboard

===Power Supply===
The Raspberry Pi dashboard requires its own power supply. You'll need a high quality 5v power supply with 2 amps minimum capacity; 3 amps is highly recommended, and ideally one with a low drop out voltage, so power is not cut to the Raspberry Pi when you're loading the main battery, such as when cranking the engine.

'''Suggested Power Supplies'''
* [https://www.amazon.com/Jabinco-LM2596-Converter-3-0-40V-1-5-35V/dp/B0817P8BGB/ Buck Converter based on the LM2596]

====Powering RaceCapture====
After you have power to the Raspberry Pi dashboard, you may notice your RaceCapture device will be powered by the USB cable connected to the Pi, just as if you're powering RaceCapture from your laptop. '''You will still want to power your RaceCapture via 12v'''; see the respective installation guides for information on how to power your device.

===Heat sinking===
If you're running in hot weather, we recommend the standard Raspberry Pi heatsink kit to keep your system cool.

For Pi4 users, we recommend active fan cooling in addition to the heat sink.

=Installation=
==Installing Rasbian OS==
We recommend installing the latest Lite distribution - [https://www.raspberrypi.org/downloads/raspbian/ download from the official site] and follow the instructions for burning to an SD card.

Once you've created your image, boot up your Raspberry Pi and log in with the default username of 'pi' and password 'raspberry'.

===Updating to latest packages===
It is always good form to update the latest packages after a fresh install. Enter this at the command line:
<pre>
sudo apt-get update
sudo apt-get dist-upgrade
</pre>

==Raspberry Pi support==
The RaceCapture app is compatible with Raspberry Pi 4 and 3.

===Enable GPU driver===
Enable Fake KMS under advanced boot options:

<pre>
sudo raspi-config
</pre>

Go to Advanced Options -> GL Driver -> Select OpenGL desktop driver with fake KMS

* Be sure to reboot after exiting raspi-config

==Installing dependencies==
===Activate ssh===
Ssh is used to store passwords used by the app. Steps to ensure it is running:

<pre>
sudo raspi-config
</pre>
Go under Interfacing Options or Advanced Options and start the ssh service.

Next, at the command prompt enter
<pre>
ssh-add
</pre>
to create at least one key.

===Install package dependencies===
<pre>
sudo apt-get install mesa-utils libgles2 libegl1-mesa libegl-mesa0
</pre>
===Change the default password===
For maximum security, change the password for the default user 'pi'

<pre>
> passwd
</pre>

and specify a new, secure password.

===Configure Raspberry Pi base settings===
====Enable Hardware rendering====
Enter the following line to enable hardware accelerated rendering.
<pre>
> sudo adduser pi render
</pre>
* '''Notes''':
** Without this setting, UI rendering will be extremely slow.
** Assumes RaceCapture is launched as pi. If not, replace pi with the user you are logging in as.
** If you're coming in to fix this after the fact, you'll need to reboot/re-login to take effect.

====Enable WiFi====
If you want network capability in addition to the ethernet connection, [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md enable and configure WiFi per the official documentation]

====(Optional) Enable SSH====
You can optionally enable SSH for remote management from the comfort of your main computer's keyboard and screen.

[https://www.raspberrypi.org/documentation/remote-access/ssh/ Enable and configure ssh per the official documentation]

====Install multi-touch tools====
Install the packages that enable multi-touch interfaces. Enter the following at the command line:

<pre>
> sudo apt-get install mtdev-tools
</pre>

====Configure memory split====
You'll need to bump up the memory made available to the GPU. Increase the default value of 64 to '''256'''.

* '''Via raspi-config tool'''
You can adjust the memory split by running the raspi-config tool. See the [https://www.raspberrypi.org/documentation/configuration/raspi-config.md official documentation]

* '''Editing /boot/config.txt'''

You can adjust the value directly by editing the /boot/config.txt file.

<pre>
> sudo nano /boot/config.txt
</pre>

Find the line containing gpu_mem=64 and change the number to 256

<pre>
gpu_mem=256
</pre>

''Save the file by pressing '''ctrl-x''' then press '''Y''' to confirm.''

==Installing the RaceCapture app package==

Download the latest [http://podium.live/software RaceCapture app package for Raspberry Pi] and place it in the /opt/ directory of the Raspberry Pi.

* '''Directly downloading to the Raspberry Pi'''
You can download it directly by getting the URL of the package by right-clicking the download link and copying the URL to your clipboard. Then, use it in the command below:

<pre>
cd /opt
sudo wget <package URL>
</pre>

===Extract the package===
Now extract the downloaded package :

<pre>
sudo tar -xjvf <downloaded file>
</pre>

===Launch the app===
Launch the RaceCapture app by running the following command:

<pre>
/opt/racecapture/run_racecapture.sh
</pre>

===Launching with Watchdog===
You can enable an automatic watchdog that re-launches the app in case a crash occurs.

<pre>
/opt/racecapture/run_racecapture.sh -w 1
</pre>

* '''Note:''' You can break out of the application by issuing '''Alt + PrntScn + k''' to the application.

You can further stop all racecapture processes by issuing the following command (e.g. via ssh)
<pre>
killall -9 run_racecapture
</pre>

===Enabling on screen keyboard===
If you don't have a wireless keyboard attached via usb, you can enable an on-screen keyboard.

Edit the kivy config.ini file with:
<pre>
sudo nano ~/.kivy/config.ini
</pre>

and update the keyboard_mode line with:

keyboard_mode = multi

==Automatic start upon power up==
To get the full dedicated dashboard experience, you can enable automatic launch of the RaceCapture app upon power up.

To do this, edit the system's startup file:

<pre>
sudo nano /etc/rc.local
</pre>

and add the following line '''before the exit 0''' line.

<pre>
/opt/racecapture/boot_racecapture.sh pi

exit 0
</pre>

''Save the file by pressing '''ctrl-x''' then press '''Y''' to confirm.''

=Connecting to your RaceCapture system=
[[image:racecapture_raspberry_pi_connections.jpg|900px]]
===Powering up===
* Connect the power to your display and power up.
* Connect your RaceCapture/Pro or RaceCapture/Track to the Raspberry Pi using the USB cable.

* Launch the RaceCapture app by running:

<pre>
/opt/racecapture/run_racecapture.sh
</pre>

If you have it set to launch automatically, simply let it start upon power-up.

===Connection and usage===

Once the RaceCapture App is running, it will connect automatically over USB. You can use the app just as you would on Android or iOS.

=Extra Features=

===Hardwire buttons===

The RaceCapture app responds to keyboard commands for certain behaviors. You can use a USB keyboard - or a device that emulates keyboard commands - to control the RaceCapture App.

Currently there are keyboard commands for the following:
* '''Navigating dashboard screens''' - Use the left and right arrow keys to switch between screens
* '''Escaping from screens / menus''' - The Escape key can be used to exit out of screens and options, just like the 'back' button on Android.
* '''Acknowledging alerts''' - Use the following keys to acknowledge alerts, including responding to pit-to-car alerts:
** K : to indicate 'Yes' or 'OK'
** N : to indicate 'No"

=Additional Tips=
See this link for additional tips on how to setup the Pi and speed up the boot times. This should be especially helpful for beginners.

https://wiki.autosportlabs.com/Raspberry_Pi_Tips

RaceCapture on Raspberry Pi

2021-12-12T19:51:42Z

GTIspirit: SSH activation is under 5 Interfacing Options and not Advanced Options on Pi 4 running Buster

=Introduction=

We designed the RaceCapture app to run nearly anywhere - even a Raspberry Pi. And now, for about $100 you can create a hardwired, dedicated dash for your RaceCapture system.

[[image:racecapture_raspberry_pi.jpg|1024px]]

==Benefits==
You get all of the benefits of a dedicated dash:
* '''Automatically runs upon power up''' - you can configure the dash to automatically launch the RaceCapture App - just as you'd expect it to work.
* '''Hard-wired data connection to RaceCapture''' - no wireless connections to configure, with the reliability of a direct wire.
* '''Runs on the bare metal''' - The RaceCapture app runs without Android or iOS; there's no other apps competing for resources, or compromising system stability.
* '''Overheating resistance''' - Your typical mobile device requires extra care in very hot weather to prevent damage to it's internal battery, and will shut down if overheated. With proper heat-sinking, the Raspberry Pi should handle the heat.

==Compatibility==
The RaceCapture app running on the Raspberry Pi is compatible with any hardware version of RaceCapture or PodiumConnect.

[[image:racecapture_raspberry_pi_backside.jpg|1024px]]

==Experimental!==
While the results are pretty great, these instructions are ''currently'' for those adventurous race car hackers who know their away around a command line, comfortable working with hardware and want to dig in. '''Think it's cool, but too much to tackle?''' Rope in your nearest computer/electronics geek - you need one on your race team, anyway. :) '''Or, just use the plug and play option''' and use an Android or iOS device via Bluetooth or WiFi.

==Current status and future plans==
Even though this is brand new and officially experimental in nature, we still made it as easy as reasonably possible: we wrapped up the RaceCapture App into as close to a self-running installer, that can run on a bone stock Raspberry Pi image - only a few changes are required to the default image, detailed below.

'''However''', in the near future we will create a dedicated Raspberry Pi image that you can burn to an SD card and simply boot up, and move towards more official support as we iron out the issues.

===Reporting issues and getting support===
Chances are you'll encounter an issue you'll want to report. Before you do that, [https://github.com/autosportlabs/RaceCapture_App/issues?q=is%3Aopen+is%3Aissue+label%3A%22raspberry+pi%22 check the issue log] to see if it's already known.

Otherwise - the best place for support, feedback and sharing success stories is [http://forum.autosportlabs.com on the forums] . Drop us a note there so we can see the progress of your project!

=Hardware Selection=
===Raspberry Pi===
RaceCapture currently requires the Raspberry Pi 3: [https://www.raspberrypi.org/products/raspberry-pi-3-model-b/ Raspberry Pi 3].

It is not yet compatible with the Pi 4, due to extensive changes in the graphics subsystem. Expect to see Pi 4 support in the 2.0 version of the app.

===Display===
The RaceCapture app package is designed to recognize the following screens:

* [https://www.raspberrypi.org/products/raspberry-pi-touch-display/ Official Raspberry Pi display] with capacitive touch screen;
* Displays supporting the AR1100 resistive touch screen controller.

Other displays can work as well, and additional work may be needed to support the screen's touch controller. If unsure, just pick the [https://www.raspberrypi.org/products/raspberry-pi-touch-display/ Official Raspberry Pi display]
===Enclosure===
A recommended enclosure is the [http://https://www.amazon.com/dp/B01HV97F64 Smart Pi Touch Case]

You can 3D print a sun shade for this enclosure [[file:P001 Raspberry Pi Display Sun Shade.stl.zip|download the .stl file]] (''Courtesy of Michael Lee'')

[[image:SmartPi_touch_case.jpg|400px]] [[image:RaceCapture_Sun_shade_3dprinted_preview.jpg|400px]]

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

Installed on Dashboard

===Power Supply===
The Raspberry Pi dashboard requires its own power supply. You'll need a high quality 5v power supply with 2 amps minimum capacity; 3 amps is highly recommended, and ideally one with a low drop out voltage, so power is not cut to the Raspberry Pi when you're loading the main battery, such as when cranking the engine.

'''Suggested Power Supplies'''
* [https://www.amazon.com/Jabinco-LM2596-Converter-3-0-40V-1-5-35V/dp/B0817P8BGB/ Buck Converter based on the LM2596]

====Powering RaceCapture====
After you have power to the Raspberry Pi dashboard, you may notice your RaceCapture device will be powered by the USB cable connected to the Pi, just as if you're powering RaceCapture from your laptop. '''You will still want to power your RaceCapture via 12v'''; see the respective installation guides for information on how to power your device.

===Heat sinking===
If you're running in hot weather, we recommend the standard Raspberry Pi heatsink kit to keep your system cool.

For Pi4 users, we recommend active fan cooling in addition to the heat sink.

=Installation=
==Installing Rasbian OS==
We recommend installing the latest Lite distribution - [https://www.raspberrypi.org/downloads/raspbian/ download from the official site] and follow the instructions for burning to an SD card.

Once you've created your image, boot up your Raspberry Pi and log in with the default username of 'pi' and password 'raspberry'.

===Updating to latest packages===
It is always good form to update the latest packages after a fresh install. Enter this at the command line:
<pre>
sudo apt-get update
sudo apt-get dist-upgrade
</pre>

==Raspberry Pi support==
The RaceCapture app is compatible with Raspberry Pi 4 and 3.

===Enable GPU driver===
Enable Fake KMS under advanced boot options:

<pre>
sudo raspi-config
</pre>

Go to Advanced Options -> GL Driver -> Select OpenGL desktop driver with fake KMS

* Be sure to reboot after exiting raspi-config

==Installing dependencies==
===Activate ssh===
Ssh is used to store passwords used by the app. Steps to ensure it is running:

<pre>
sudo raspi-config
</pre>
Go under Interfacing Options or Advanced Options and start the ssh service.

Next, at the command prompt enter
<pre>
ssh-add
</pre>
to create at least one key.

===Install package dependencies===
<pre>
sudo apt-get install mesa-utils libgles2 libegl1-mesa libegl-mesa0
</pre>
===Change the default password===
For maximum security, change the password for the default user 'pi'

<pre>
> passwd
</pre>

and specify a new, secure password.

===Configure Raspberry Pi base settings===
====Enable Hardware rendering====
Enter the following line to enable hardware accelerated rendering.
<pre>
> sudo adduser pi render
</pre>
* '''Notes''':
** Without this setting, UI rendering will be extremely slow.
** Assumes RaceCapture is launched as pi. If not, replace pi with the user you are logging in as.
** If you're coming in to fix this after the fact, you'll need to reboot/re-login to take effect.

====Enable WiFi====
If you want network capability in addition to the ethernet connection, [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md enable and configure WiFi per the official documentation]

====(Optional) Enable SSH====
You can optionally enable SSH for remote management from the comfort of your main computer's keyboard and screen.

[https://www.raspberrypi.org/documentation/remote-access/ssh/ Enable and configure ssh per the official documentation]

====Install multi-touch tools====
Install the packages that enable multi-touch interfaces. Enter the following at the command line:

<pre>
> sudo apt-get install mtdev-tools
</pre>

====Configure memory split====
You'll need to bump up the memory made available to the GPU. Increase the default value of 64 to '''256'''.

* '''Via raspi-config tool'''
You can adjust the memory split by running the raspi-config tool. See the [https://www.raspberrypi.org/documentation/configuration/raspi-config.md official documentation]

* '''Editing /boot/config.txt'''

You can adjust the value directly by editing the /boot/config.txt file.

<pre>
> sudo nano /boot/config.txt
</pre>

Find the line containing gpu_mem=64 and change the number to 256

<pre>
gpu_mem=256
</pre>

''Save the file by pressing '''ctrl-x''' then press '''Y''' to confirm.''

==Installing the RaceCapture app package==

Download the latest [http://podium.live/software RaceCapture app package for Raspberry Pi] and place it in the /opt/ directory of the Raspberry Pi.

* '''Directly downloading to the Raspberry Pi'''
You can download it directly by getting the URL of the package by right-clicking the download link and copying the URL to your clipboard. Then, use it in the command below:

<pre>
cd /opt
sudo wget <package URL>
</pre>

===Extract the package===
Now extract the downloaded package :

<pre>
sudo tar -xjvf <downloaded file>
</pre>

===Launch the app===
Launch the RaceCapture app by running the following command:

<pre>
/opt/racecapture/run_racecapture.sh
</pre>

===Launching with Watchdog===
You can enable an automatic watchdog that re-launches the app in case a crash occurs.

<pre>
/opt/racecapture/run_racecapture.sh -w 1
</pre>

* '''Note:''' You can break out of the application by issuing '''Alt + PrntScn + k''' to the application.

You can further stop all racecapture processes by issuing the following command (e.g. via ssh)
<pre>
killall -9 run_racecapture
</pre>

===Enabling on screen keyboard===
If you don't have a wireless keyboard attached via usb, you can enable an on-screen keyboard.

Edit the ~/.kivy/config.ini and update the keyboard_mode line with:

``` keyboard_mode = multi```

==Automatic start upon power up==
To get the full dedicated dashboard experience, you can enable automatic launch of the RaceCapture app upon power up.

To do this, edit the system's startup file:

<pre>
sudo nano /etc/rc.local
</pre>

and add the following line '''before the exit 0''' line.

<pre>
/opt/racecapture/boot_racecapture.sh pi

exit 0
</pre>

''Save the file by pressing '''ctrl-x''' then press '''Y''' to confirm.''

=Connecting to your RaceCapture system=
[[image:racecapture_raspberry_pi_connections.jpg|900px]]
===Powering up===
* Connect the power to your display and power up.
* Connect your RaceCapture/Pro or RaceCapture/Track to the Raspberry Pi using the USB cable.

* Launch the RaceCapture app by running:

<pre>
/opt/racecapture/run_racecapture.sh
</pre>

If you have it set to launch automatically, simply let it start upon power-up.

===Connection and usage===

Once the RaceCapture App is running, it will connect automatically over USB. You can use the app just as you would on Android or iOS.

=Extra Features=

===Hardwire buttons===

The RaceCapture app responds to keyboard commands for certain behaviors. You can use a USB keyboard - or a device that emulates keyboard commands - to control the RaceCapture App.

Currently there are keyboard commands for the following:
* '''Navigating dashboard screens''' - Use the left and right arrow keys to switch between screens
* '''Escaping from screens / menus''' - The Escape key can be used to exit out of screens and options, just like the 'back' button on Android.
* '''Acknowledging alerts''' - Use the following keys to acknowledge alerts, including responding to pit-to-car alerts:
** K : to indicate 'Yes' or 'OK'
** N : to indicate 'No"

=Additional Tips=
See this link for additional tips on how to setup the Pi and speed up the boot times. This should be especially helpful for beginners.

https://wiki.autosportlabs.com/Raspberry_Pi_Tips

AutomaticCameraControl

2020-05-17T19:02:33Z

GTIspirit: /* Lua Script for Garmin Virb */

=Automatic Camera Control=

==Introduction==
This guide shows you how to enable automatic start / stop control of WiFi enabled cameras, such as GoPro using RaceCapture or PodiumConnect.

==How it works==
Most action cameras offer a WiFi interface for remote control. GoPro is one such camera, and allows shutter control via the WiFi interface, which RaceCapture or PodiumConnect can leverage for automatic triggering.

===Currently supported versions of RaceCapture hardware===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2
* RaceCapture/Pro MK2 with external WiFi add-on (see below)

===Currently supported cameras===
* GoPro Hero 2/3
* GoPro Hero 4/5 (experimental)
* Garmin Virb Ultra 30 (experimental)

Note, We recommend GoPro 2/3 due to stability / reliability issues seen with the later GoPro devices.

Additional Camera support will be added with future firmware releases.

==Overview==
RaceCapture or PodiumConnect is configured so it's WiFi client connects to the camera's access point using its SSID and WiFi password.

When RaceCapture/PodiumConnect triggers the camera based on a sensor threshold such as speed, RPM or other value, it sends a command to the camera to start recording. When the sensor falls below the threshold, the corresponding command is sent to stop the recording.

===Simultaneous WiFi connection with the RaceCapture App===
Since the WiFi client feature is used on RaceCapture/PodiumConnect to connect to the camera, the Access Point remains available for the RaceCapture app to connect via WiFi, as usual. Or, via Bluetooth, if supported by the RaceCapture system.

[[Image:automatic_camera_control.jpg|400px]]

==Setting up Automatic Camera Control==

===Applies to===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2

==Requirements==
* Firmware 2.13.0 or higher

===Set up WiFi client===
Navigate to Setup / Wireless and ensure:
* WiFi is turned '''ON'''
* WiFi client is turned '''ON'''
* Camera SSID and password are specified in the WiFi client settings.

[[image:WiFi_camera_control_config.png]]

===Set up Automatic Control===
Navigate to Setup / Automatic Control and ensure:
* The desired sensor channel trigger is selected (Speed is the default)
* Your start / stop and time thresholds are configured
* Camera Control is turned '''ON''' and you have your camera model selected.

[[Image:automatic_control_camera_settings.png]]

===Write Settings===
Write the settings back to RaceCapture by pressing the '''Write''' button under Setup.

==Testing==
Turn on the camera and ensure the camera has it's WiFi interface enabled.

Power up RaceCapture, connect the RaceCapture app and verify the WiFi client is connected under the System Status page.
[[image:verifying_wifi_client_connected.png]]

It may take several seconds for the client to connect. If not, re-check the camera's SSID/password, and ensure WiFi is enabled on the camera.
* '''Note''': On GoPros, the Camera must be in 'App mode' with WiFi enabled.

Once it is connected to the camera, you can test the camera by triggering the configured camera's threshold.
* '''Tip''': For static testing, you can configure the camera control to one of the Accelerometer channels, such as '''AccelZ''' and trigger by inverting RaceCapture. Or, use RPM, battery voltage or similar.

==RaceCapture/Pro MK2==
While the automatic camera control firmware feature is not available for RaceCapture/Pro MK2, it can still be controlled via a Lua script.

[[image:RaceCapture_WiFi_GoPro_control_diagram.png]]

When WiFi is enabled on your GoPro camera it creates a network that other devices can connect to. A WiFi enabled version of RaceCapture/Pro can connect to this network and issue the appropriate commands to control various camera functions - in this case, starting and stopping video recording.

Starting and stopping the GoPro can be controlled by a variety of means: speed, RPM or based on other sensor data, enabled by a Lua Script running on RaceCapture/Pro.

This guide focuses on using GPS speed to trigger the camera; for triggering on other sensors see the [[RaceCapturePro_Lua_Scripting|Lua scripting guide]] as a reference for what other sensor data is available.

==Notes==
* Currently, the WiFi module can only be used to enable GoPro triggering.
* '''If running firmware version 2.10.x or higher''' To use this script, you must disable the built-in WiFi control, or else it will take over the connection and block the script from running.
* Future versions of RaceCapture firmware and app will allow built-in firmware control of GoPro cameras, which will eliminate the need for this script.

==Requirements==
* RaceCapture/Pro MK2 running firmware 2.9.1 or higher
* [https://www.autosportlabs.com/product/racecapturepro-wifi-module/ RaceCapture/Pro WiFi module]
* WiFi enabled GoPro Hero camera, with WiFi activated
* GPS Connectivity (for speed measurement)

==Steps==

===Configure your GoPro===
Using the GoPro app, configure the WiFi network, making a note of the network name (SSID) and password.

===Connect the WiFi module===
Connect the RaceCapture/Pro WiFi module to the outermost (Auxiliary) port of RaceCapture/Pro.
* When powered up, you should see the power LED illuminate.
* This port is to the right of the Bluetooth Port.
** The WiFi module does not interfere with the operation of the Bluetooth module.

===Enable Lua script for GoPro connectivity===
Customize the Lua script shown at the bottom with the GoPro's WiFi network name (SSID) and password, then copy and paste the Lua script shown at the bottom into the scripting window of your RaceCapture/Pro.

Steps:
* Connect RaceCapture/Pro to the RaceCapture app and read the current configuration.
* Copy the Lua script into the Scripting window:
** Ensure the script window is first blank by removing the default script by deleting the text in the window.
*** '''Note''': If you have an existing script you want to keep, you will need to blend the camera functionality with your existing script. How to do this is beyond the scope of this guide; see the [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]] for more information.
** Copy the script into the window by using the '''ctrl-v''' keyboard shortcut.
* Write the configuration back to RaceCapture/Pro.

[[image:gopro_script.png]]

===Bench testing===
Once the Lua script is written to RaceCapture/Pro, it will attempt to connect to the network created by the GoPro camera. Once connected, it will be ready to issue start / stop commands to the camera.

[[image:GoProCameraControl_RaceCapture.jpg]]

Before road testing, ensure RaceCapture/Pro can connect to the GoPro's WiFi network by observing the messages in the window below the script.
* '''Tip 1''': Touch or click the '''Poll Log''' to see the current message in the RaceCapture/Pro log
* '''Tip 2''': To restart the Lua script, touch or click the 'Restart' button.

===Road testing===
Mount the GoPro in the car as usual and power up RaceCapture/Pro, waiting for GPS achieve a lock.

* Drive carefully above the speed threshold and observe the GoPro - you should hear and see the familiar beep and red light activate, just as if you manually started recording using the shutter button on the camera.
* When you drop below the threshold, the GoPro should stop recording.

As RaceCapture/Pro starts and stops the camera, you will see the following information in the log:
<pre>
[GoProWiFi] start GoPro
[GoProWiFi] stop GoPro
</pre>

=Troubleshooting=
If RaceCapture/Pro cannot control the camera, check the following:
* '''GoPro WiFi network name (SSID) and password''': Ensure the name and password currently in the script matches how your GoPro was configured.
* '''Enable WiFi on the GoPro''': The blue LED on the GoPro should be blinking periodically
* '''RaceCapture/Pro WiFi module connection''': Ensure the module is plugged into the outermost RJ11 port and the green LED is illuminated.
* '''Verify WiFi connection''': Ensure RaceCapture/Pro can connect to the GoPro WiFi network. You should see the following messages in the log upon power-up:
<pre>
[lua] Successfully loaded script.
[GoProWiFi] initializing
[GoProWiFi] ready for GoPro
</pre>

If RaceCapture/Pro cannot connect to the GoPro's network you will see this in the log:
<pre>
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
</pre>

=Lua Script for GoPro=

The following Lua Script enables WiFi control of your GoPro camera.

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''GoPro WiFi password''': Specify the WiFi password used for the GoPro WiFi adapter
* '''GoPro SSID''': Specify the GoPro WiFi network name (SSID)

===Optional===
* '''goproStart''': Change this if you want to start recording at a different threshold.
* '''goproStop''': Change this if you want to stop recording at a different threshold. '''Ensure this is less than the start trigger'''
* '''tickRate''': Adjust this to update how often you want RaceCapture/Pro to perform a start/stop check. Value is in Hz. If uncertain, leave this alone
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
--Specify your GoPro wifi password here
goproPwd = '12345678'

--Specify your GoPro SSID here
goproSsid = 'aslhero1'

--Speed threshold to start recording
goproStart = 10

--Speed threshold to stop recording
goproStop = 5

--How fast we check, in Hz
tickRate = 10

--Set this to 1 to log communications between RCP & WiFi
debug = 0
-----------------------------
--DO NOT EDIT BELOW
-----------------------------
--the serial port where the WiFi is connected
port = 4
--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000

function logMsg(msg)
println('[GoProWiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpGet(url)
sendAt('AT+CIPSTART="TCP","10.5.5.9",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local get = 'GET ' ..url ..' HTTP/1.0' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#get))
sleep(100)
sendRaw(get)
sleep(100)
sendAt("AT+CIPCLOSE")
end

function sendGoProShutter(cmd)
httpGet('/bacpac/SH?t=' ..goproPwd ..'&p=%' ..cmd)
end

function startGoPro()
logMsg('start GoPro')
sendGoProShutter('01')
end

function stopGoPro()
logMsg('stop GoPro')
sendGoProShutter('00')
end

recording = 0

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..goproSsid ..'","' ..goproPwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for GoPro')
end
end

function checkGoPro()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to GoPro')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
trigger = getGpsSpeed()

if recording == 0 and trigger > goproStart then
startGoPro()
recording = 1
end
if recording == 1 and trigger < goproStop then
stopGoPro()
recording = 0
end
end

function onTick()
checkGoPro()
end

setTickRate(tickRate)
</pre>

=Lua Script for Garmin Virb=

The following Lua Script enables WiFi control of your Garmin Virb camera using the Garmin [https://developer.garmin.com/downloads/virb/Camera_Network_Services_API_v0.5.pdf Camera Network Services API]. Not all commands in the API may work. Use commandList (via [https://www.postman.com/ Postman]) to determine which API commands are supported by your Garmin Virb camera. 
''The Garmin Virb always uses 192.168.0.1 HTTP port ( 80 ).'' 
'''NOTE''': this Lua script is different than the GoPro script above in that Garmin uses POST commands instead of GET commands. 
''For a more detailed explanation, see'' [https://forum.autosportlabs.com/viewtopic.php?t=6267 How to send HTTP POST request via Lua Script?] 
It may be possible to control other WiFi devices by altering the POST command accordingly. e.g. instead of sending httpPost arguments {"command":"startRecording"} substitute this with the commands specified by the device API. Be sure to adjust the server host IP address if different than the Garmin standard. 

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''Ssid''': Specify the WiFi network name (SSID)
* '''Pwd''': Specify the WiFi password

===Optional===
* '''Port''': 5 is the WiFi port for the RaceCapture/Track MK2. Change according to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting#Port_mappings Port mapping]
* '''autoStart''': Change this if you want to start recording at a different threshold.
* '''autoStop''': Change this if you want to stop recording at a different threshold.
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
setTickRate(10) --TickRate is in Hz
--configure WiFi serial port
port = 5
initSer(port,115200,8,0,1)
--Specify client SSID here
Ssid = 'VIRB-4615'
--Specify client wifi password here
Pwd = '12345678'
--Set this to 1 to log communications between RCP & WiFi
debug = 0

--initialize variables
trigger = 0
recording = 0

--define constants
autoStart = 0 --Threshold to start recording
autoStop = 1 --Threshold to stop recording

------WiFi Code--------------
--DO NOT EDIT BELOW
-----------------------------

--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000
reps = 3 --number of times to repeat command

function logMsg(msg)
println('[WiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpPost(cmd)
sendAt('AT+CIPSTART="TCP","192.168.0.1",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local post = 'POST /virb HTTP/1.1\r\nHost: 192.168.0.1\r\nAccept: */*\r\nContent-Length: ' ..toInt(#cmd)..'\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n' ..cmd ..'\r\n' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#post))
sleep(100)
sendRaw(post)
if debug == 1 then println(post) end
sleep(100)
sendAt('AT+CIPCLOSE')
end

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..Ssid ..'","' ..Pwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') or string.match(line, 'WIFI CONNECTED') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for WiFi')
end
end

function checkWiFi()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to WiFi')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
--trigger = getGpsSpeed()
trigger = bit.rshift(bit.band(getChannel("77AB2"),0x40),6)
--trigger = 1
if recording == 0 and trigger > autoStart then
for i=1,reps,1
do
httpPost('{"command":"startRecording"}')
end
recording = 1
end
if recording == 1 and trigger < autoStop then
for i=1,reps,1
do
httpPost('{"command":"stopRecording"}')
end
recording = 0
end
end

function onTick()
checkWiFi()
--println('trigger value: ' ..trigger)
--println('recording status: ' ..recording)
if debug ==1 then println("WiFi Status: " ..wifiStatus) end
end

</pre>

A few comments:
* The POST command is repeated the number of times specified by reps. This is because during testing the startRecording was not entirely reliable. The camera somehow missed the command.
* The trigger condition is set to use bit 6 of the CAN channel 77AB2. This signal comes from a switch on the dashboard wired to an ECU, which then sends switch status on the CAN to which the RaceCapture/Track MK2 is connected. Modify accordingly if you have a similar switch, otherwise comment this out and uncomment the getGpsSpeed() line, altering the autoStart and autoStop thresholds accordingly.

AutomaticCameraControl

2020-05-17T18:58:14Z

GTIspirit: /* Lua Script for Garmin Virb */

=Automatic Camera Control=

==Introduction==
This guide shows you how to enable automatic start / stop control of WiFi enabled cameras, such as GoPro using RaceCapture or PodiumConnect.

==How it works==
Most action cameras offer a WiFi interface for remote control. GoPro is one such camera, and allows shutter control via the WiFi interface, which RaceCapture or PodiumConnect can leverage for automatic triggering.

===Currently supported versions of RaceCapture hardware===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2
* RaceCapture/Pro MK2 with external WiFi add-on (see below)

===Currently supported cameras===
* GoPro Hero 2/3
* GoPro Hero 4/5 (experimental)
* Garmin Virb Ultra 30 (experimental)

Note, We recommend GoPro 2/3 due to stability / reliability issues seen with the later GoPro devices.

Additional Camera support will be added with future firmware releases.

==Overview==
RaceCapture or PodiumConnect is configured so it's WiFi client connects to the camera's access point using its SSID and WiFi password.

When RaceCapture/PodiumConnect triggers the camera based on a sensor threshold such as speed, RPM or other value, it sends a command to the camera to start recording. When the sensor falls below the threshold, the corresponding command is sent to stop the recording.

===Simultaneous WiFi connection with the RaceCapture App===
Since the WiFi client feature is used on RaceCapture/PodiumConnect to connect to the camera, the Access Point remains available for the RaceCapture app to connect via WiFi, as usual. Or, via Bluetooth, if supported by the RaceCapture system.

[[Image:automatic_camera_control.jpg|400px]]

==Setting up Automatic Camera Control==

===Applies to===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2

==Requirements==
* Firmware 2.13.0 or higher

===Set up WiFi client===
Navigate to Setup / Wireless and ensure:
* WiFi is turned '''ON'''
* WiFi client is turned '''ON'''
* Camera SSID and password are specified in the WiFi client settings.

[[image:WiFi_camera_control_config.png]]

===Set up Automatic Control===
Navigate to Setup / Automatic Control and ensure:
* The desired sensor channel trigger is selected (Speed is the default)
* Your start / stop and time thresholds are configured
* Camera Control is turned '''ON''' and you have your camera model selected.

[[Image:automatic_control_camera_settings.png]]

===Write Settings===
Write the settings back to RaceCapture by pressing the '''Write''' button under Setup.

==Testing==
Turn on the camera and ensure the camera has it's WiFi interface enabled.

Power up RaceCapture, connect the RaceCapture app and verify the WiFi client is connected under the System Status page.
[[image:verifying_wifi_client_connected.png]]

It may take several seconds for the client to connect. If not, re-check the camera's SSID/password, and ensure WiFi is enabled on the camera.
* '''Note''': On GoPros, the Camera must be in 'App mode' with WiFi enabled.

Once it is connected to the camera, you can test the camera by triggering the configured camera's threshold.
* '''Tip''': For static testing, you can configure the camera control to one of the Accelerometer channels, such as '''AccelZ''' and trigger by inverting RaceCapture. Or, use RPM, battery voltage or similar.

==RaceCapture/Pro MK2==
While the automatic camera control firmware feature is not available for RaceCapture/Pro MK2, it can still be controlled via a Lua script.

[[image:RaceCapture_WiFi_GoPro_control_diagram.png]]

When WiFi is enabled on your GoPro camera it creates a network that other devices can connect to. A WiFi enabled version of RaceCapture/Pro can connect to this network and issue the appropriate commands to control various camera functions - in this case, starting and stopping video recording.

Starting and stopping the GoPro can be controlled by a variety of means: speed, RPM or based on other sensor data, enabled by a Lua Script running on RaceCapture/Pro.

This guide focuses on using GPS speed to trigger the camera; for triggering on other sensors see the [[RaceCapturePro_Lua_Scripting|Lua scripting guide]] as a reference for what other sensor data is available.

==Notes==
* Currently, the WiFi module can only be used to enable GoPro triggering.
* '''If running firmware version 2.10.x or higher''' To use this script, you must disable the built-in WiFi control, or else it will take over the connection and block the script from running.
* Future versions of RaceCapture firmware and app will allow built-in firmware control of GoPro cameras, which will eliminate the need for this script.

==Requirements==
* RaceCapture/Pro MK2 running firmware 2.9.1 or higher
* [https://www.autosportlabs.com/product/racecapturepro-wifi-module/ RaceCapture/Pro WiFi module]
* WiFi enabled GoPro Hero camera, with WiFi activated
* GPS Connectivity (for speed measurement)

==Steps==

===Configure your GoPro===
Using the GoPro app, configure the WiFi network, making a note of the network name (SSID) and password.

===Connect the WiFi module===
Connect the RaceCapture/Pro WiFi module to the outermost (Auxiliary) port of RaceCapture/Pro.
* When powered up, you should see the power LED illuminate.
* This port is to the right of the Bluetooth Port.
** The WiFi module does not interfere with the operation of the Bluetooth module.

===Enable Lua script for GoPro connectivity===
Customize the Lua script shown at the bottom with the GoPro's WiFi network name (SSID) and password, then copy and paste the Lua script shown at the bottom into the scripting window of your RaceCapture/Pro.

Steps:
* Connect RaceCapture/Pro to the RaceCapture app and read the current configuration.
* Copy the Lua script into the Scripting window:
** Ensure the script window is first blank by removing the default script by deleting the text in the window.
*** '''Note''': If you have an existing script you want to keep, you will need to blend the camera functionality with your existing script. How to do this is beyond the scope of this guide; see the [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]] for more information.
** Copy the script into the window by using the '''ctrl-v''' keyboard shortcut.
* Write the configuration back to RaceCapture/Pro.

[[image:gopro_script.png]]

===Bench testing===
Once the Lua script is written to RaceCapture/Pro, it will attempt to connect to the network created by the GoPro camera. Once connected, it will be ready to issue start / stop commands to the camera.

[[image:GoProCameraControl_RaceCapture.jpg]]

Before road testing, ensure RaceCapture/Pro can connect to the GoPro's WiFi network by observing the messages in the window below the script.
* '''Tip 1''': Touch or click the '''Poll Log''' to see the current message in the RaceCapture/Pro log
* '''Tip 2''': To restart the Lua script, touch or click the 'Restart' button.

===Road testing===
Mount the GoPro in the car as usual and power up RaceCapture/Pro, waiting for GPS achieve a lock.

* Drive carefully above the speed threshold and observe the GoPro - you should hear and see the familiar beep and red light activate, just as if you manually started recording using the shutter button on the camera.
* When you drop below the threshold, the GoPro should stop recording.

As RaceCapture/Pro starts and stops the camera, you will see the following information in the log:
<pre>
[GoProWiFi] start GoPro
[GoProWiFi] stop GoPro
</pre>

=Troubleshooting=
If RaceCapture/Pro cannot control the camera, check the following:
* '''GoPro WiFi network name (SSID) and password''': Ensure the name and password currently in the script matches how your GoPro was configured.
* '''Enable WiFi on the GoPro''': The blue LED on the GoPro should be blinking periodically
* '''RaceCapture/Pro WiFi module connection''': Ensure the module is plugged into the outermost RJ11 port and the green LED is illuminated.
* '''Verify WiFi connection''': Ensure RaceCapture/Pro can connect to the GoPro WiFi network. You should see the following messages in the log upon power-up:
<pre>
[lua] Successfully loaded script.
[GoProWiFi] initializing
[GoProWiFi] ready for GoPro
</pre>

If RaceCapture/Pro cannot connect to the GoPro's network you will see this in the log:
<pre>
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
</pre>

=Lua Script for GoPro=

The following Lua Script enables WiFi control of your GoPro camera.

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''GoPro WiFi password''': Specify the WiFi password used for the GoPro WiFi adapter
* '''GoPro SSID''': Specify the GoPro WiFi network name (SSID)

===Optional===
* '''goproStart''': Change this if you want to start recording at a different threshold.
* '''goproStop''': Change this if you want to stop recording at a different threshold. '''Ensure this is less than the start trigger'''
* '''tickRate''': Adjust this to update how often you want RaceCapture/Pro to perform a start/stop check. Value is in Hz. If uncertain, leave this alone
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
--Specify your GoPro wifi password here
goproPwd = '12345678'

--Specify your GoPro SSID here
goproSsid = 'aslhero1'

--Speed threshold to start recording
goproStart = 10

--Speed threshold to stop recording
goproStop = 5

--How fast we check, in Hz
tickRate = 10

--Set this to 1 to log communications between RCP & WiFi
debug = 0
-----------------------------
--DO NOT EDIT BELOW
-----------------------------
--the serial port where the WiFi is connected
port = 4
--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000

function logMsg(msg)
println('[GoProWiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpGet(url)
sendAt('AT+CIPSTART="TCP","10.5.5.9",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local get = 'GET ' ..url ..' HTTP/1.0' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#get))
sleep(100)
sendRaw(get)
sleep(100)
sendAt("AT+CIPCLOSE")
end

function sendGoProShutter(cmd)
httpGet('/bacpac/SH?t=' ..goproPwd ..'&p=%' ..cmd)
end

function startGoPro()
logMsg('start GoPro')
sendGoProShutter('01')
end

function stopGoPro()
logMsg('stop GoPro')
sendGoProShutter('00')
end

recording = 0

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..goproSsid ..'","' ..goproPwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for GoPro')
end
end

function checkGoPro()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to GoPro')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
trigger = getGpsSpeed()

if recording == 0 and trigger > goproStart then
startGoPro()
recording = 1
end
if recording == 1 and trigger < goproStop then
stopGoPro()
recording = 0
end
end

function onTick()
checkGoPro()
end

setTickRate(tickRate)
</pre>

=Lua Script for Garmin Virb=

The following Lua Script enables WiFi control of your Garmin Virb camera using the Garmin [https://developer.garmin.com/downloads/virb/Camera_Network_Services_API_v0.5.pdf Camera Network Services API]. 
''The Garmin Virb always uses 192.168.0.1 HTTP port ( 80 ).'' 
'''NOTE''': this Lua script is different than the GoPro script above in that Garmin uses POST commands instead of GET commands. 
''For a more detailed explanation, see'' [https://forum.autosportlabs.com/viewtopic.php?t=6267 How to send HTTP POST request via Lua Script?] 
It may be possible to control other WiFi devices by altering the POST command accordingly. e.g. instead of sending httpPost arguments {"command":"startRecording"} substitute this with the commands specified by the device API. Be sure to adjust the server host IP address if different than the Garmin standard. 

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''Ssid''': Specify the WiFi network name (SSID)
* '''Pwd''': Specify the WiFi password

===Optional===
* '''Port''': 5 is the WiFi port for the RaceCapture/Track MK2. Change according to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting#Port_mappings Port mapping]
* '''autoStart''': Change this if you want to start recording at a different threshold.
* '''autoStop''': Change this if you want to stop recording at a different threshold.
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
setTickRate(10) --TickRate is in Hz
--configure WiFi serial port
port = 5
initSer(port,115200,8,0,1)
--Specify client SSID here
Ssid = 'VIRB-4615'
--Specify client wifi password here
Pwd = '12345678'
--Set this to 1 to log communications between RCP & WiFi
debug = 0

--initialize variables
trigger = 0
recording = 0

--define constants
autoStart = 0 --Threshold to start recording
autoStop = 1 --Threshold to stop recording

------WiFi Code--------------
--DO NOT EDIT BELOW
-----------------------------

--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000
reps = 3 --number of times to repeat command

function logMsg(msg)
println('[WiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpPost(cmd)
sendAt('AT+CIPSTART="TCP","192.168.0.1",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local post = 'POST /virb HTTP/1.1\r\nHost: 192.168.0.1\r\nAccept: */*\r\nContent-Length: ' ..toInt(#cmd)..'\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n' ..cmd ..'\r\n' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#post))
sleep(100)
sendRaw(post)
if debug == 1 then println(post) end
sleep(100)
sendAt('AT+CIPCLOSE')
end

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..Ssid ..'","' ..Pwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') or string.match(line, 'WIFI CONNECTED') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for WiFi')
end
end

function checkWiFi()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to WiFi')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
--trigger = getGpsSpeed()
trigger = bit.rshift(bit.band(getChannel("77AB2"),0x40),6)
--trigger = 1
if recording == 0 and trigger > autoStart then
for i=1,reps,1
do
httpPost('{"command":"startRecording"}')
end
recording = 1
end
if recording == 1 and trigger < autoStop then
for i=1,reps,1
do
httpPost('{"command":"stopRecording"}')
end
recording = 0
end
end

function onTick()
checkWiFi()
--println('trigger value: ' ..trigger)
--println('recording status: ' ..recording)
if debug ==1 then println("WiFi Status: " ..wifiStatus) end
end

</pre>

A few comments:
* The POST command is repeated the number of times specified by reps. This is because during testing the startRecording was not entirely reliable. The camera somehow missed the command.
* The trigger condition is set to use bit 6 of the CAN channel 77AB2. This signal comes from a switch on the dashboard wired to an ECU, which then sends switch status on the CAN to which the RaceCapture/Track MK2 is connected. Modify accordingly if you have a similar switch, otherwise comment this out and uncomment the getGpsSpeed() line, altering the autoStart and autoStop thresholds accordingly.

AutomaticCameraControl

2020-05-17T18:53:56Z

GTIspirit: /* Optional */

=Automatic Camera Control=

==Introduction==
This guide shows you how to enable automatic start / stop control of WiFi enabled cameras, such as GoPro using RaceCapture or PodiumConnect.

==How it works==
Most action cameras offer a WiFi interface for remote control. GoPro is one such camera, and allows shutter control via the WiFi interface, which RaceCapture or PodiumConnect can leverage for automatic triggering.

===Currently supported versions of RaceCapture hardware===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2
* RaceCapture/Pro MK2 with external WiFi add-on (see below)

===Currently supported cameras===
* GoPro Hero 2/3
* GoPro Hero 4/5 (experimental)
* Garmin Virb Ultra 30 (experimental)

Note, We recommend GoPro 2/3 due to stability / reliability issues seen with the later GoPro devices.

Additional Camera support will be added with future firmware releases.

==Overview==
RaceCapture or PodiumConnect is configured so it's WiFi client connects to the camera's access point using its SSID and WiFi password.

When RaceCapture/PodiumConnect triggers the camera based on a sensor threshold such as speed, RPM or other value, it sends a command to the camera to start recording. When the sensor falls below the threshold, the corresponding command is sent to stop the recording.

===Simultaneous WiFi connection with the RaceCapture App===
Since the WiFi client feature is used on RaceCapture/PodiumConnect to connect to the camera, the Access Point remains available for the RaceCapture app to connect via WiFi, as usual. Or, via Bluetooth, if supported by the RaceCapture system.

[[Image:automatic_camera_control.jpg|400px]]

==Setting up Automatic Camera Control==

===Applies to===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2

==Requirements==
* Firmware 2.13.0 or higher

===Set up WiFi client===
Navigate to Setup / Wireless and ensure:
* WiFi is turned '''ON'''
* WiFi client is turned '''ON'''
* Camera SSID and password are specified in the WiFi client settings.

[[image:WiFi_camera_control_config.png]]

===Set up Automatic Control===
Navigate to Setup / Automatic Control and ensure:
* The desired sensor channel trigger is selected (Speed is the default)
* Your start / stop and time thresholds are configured
* Camera Control is turned '''ON''' and you have your camera model selected.

[[Image:automatic_control_camera_settings.png]]

===Write Settings===
Write the settings back to RaceCapture by pressing the '''Write''' button under Setup.

==Testing==
Turn on the camera and ensure the camera has it's WiFi interface enabled.

Power up RaceCapture, connect the RaceCapture app and verify the WiFi client is connected under the System Status page.
[[image:verifying_wifi_client_connected.png]]

It may take several seconds for the client to connect. If not, re-check the camera's SSID/password, and ensure WiFi is enabled on the camera.
* '''Note''': On GoPros, the Camera must be in 'App mode' with WiFi enabled.

Once it is connected to the camera, you can test the camera by triggering the configured camera's threshold.
* '''Tip''': For static testing, you can configure the camera control to one of the Accelerometer channels, such as '''AccelZ''' and trigger by inverting RaceCapture. Or, use RPM, battery voltage or similar.

==RaceCapture/Pro MK2==
While the automatic camera control firmware feature is not available for RaceCapture/Pro MK2, it can still be controlled via a Lua script.

[[image:RaceCapture_WiFi_GoPro_control_diagram.png]]

When WiFi is enabled on your GoPro camera it creates a network that other devices can connect to. A WiFi enabled version of RaceCapture/Pro can connect to this network and issue the appropriate commands to control various camera functions - in this case, starting and stopping video recording.

Starting and stopping the GoPro can be controlled by a variety of means: speed, RPM or based on other sensor data, enabled by a Lua Script running on RaceCapture/Pro.

This guide focuses on using GPS speed to trigger the camera; for triggering on other sensors see the [[RaceCapturePro_Lua_Scripting|Lua scripting guide]] as a reference for what other sensor data is available.

==Notes==
* Currently, the WiFi module can only be used to enable GoPro triggering.
* '''If running firmware version 2.10.x or higher''' To use this script, you must disable the built-in WiFi control, or else it will take over the connection and block the script from running.
* Future versions of RaceCapture firmware and app will allow built-in firmware control of GoPro cameras, which will eliminate the need for this script.

==Requirements==
* RaceCapture/Pro MK2 running firmware 2.9.1 or higher
* [https://www.autosportlabs.com/product/racecapturepro-wifi-module/ RaceCapture/Pro WiFi module]
* WiFi enabled GoPro Hero camera, with WiFi activated
* GPS Connectivity (for speed measurement)

==Steps==

===Configure your GoPro===
Using the GoPro app, configure the WiFi network, making a note of the network name (SSID) and password.

===Connect the WiFi module===
Connect the RaceCapture/Pro WiFi module to the outermost (Auxiliary) port of RaceCapture/Pro.
* When powered up, you should see the power LED illuminate.
* This port is to the right of the Bluetooth Port.
** The WiFi module does not interfere with the operation of the Bluetooth module.

===Enable Lua script for GoPro connectivity===
Customize the Lua script shown at the bottom with the GoPro's WiFi network name (SSID) and password, then copy and paste the Lua script shown at the bottom into the scripting window of your RaceCapture/Pro.

Steps:
* Connect RaceCapture/Pro to the RaceCapture app and read the current configuration.
* Copy the Lua script into the Scripting window:
** Ensure the script window is first blank by removing the default script by deleting the text in the window.
*** '''Note''': If you have an existing script you want to keep, you will need to blend the camera functionality with your existing script. How to do this is beyond the scope of this guide; see the [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]] for more information.
** Copy the script into the window by using the '''ctrl-v''' keyboard shortcut.
* Write the configuration back to RaceCapture/Pro.

[[image:gopro_script.png]]

===Bench testing===
Once the Lua script is written to RaceCapture/Pro, it will attempt to connect to the network created by the GoPro camera. Once connected, it will be ready to issue start / stop commands to the camera.

[[image:GoProCameraControl_RaceCapture.jpg]]

Before road testing, ensure RaceCapture/Pro can connect to the GoPro's WiFi network by observing the messages in the window below the script.
* '''Tip 1''': Touch or click the '''Poll Log''' to see the current message in the RaceCapture/Pro log
* '''Tip 2''': To restart the Lua script, touch or click the 'Restart' button.

===Road testing===
Mount the GoPro in the car as usual and power up RaceCapture/Pro, waiting for GPS achieve a lock.

* Drive carefully above the speed threshold and observe the GoPro - you should hear and see the familiar beep and red light activate, just as if you manually started recording using the shutter button on the camera.
* When you drop below the threshold, the GoPro should stop recording.

As RaceCapture/Pro starts and stops the camera, you will see the following information in the log:
<pre>
[GoProWiFi] start GoPro
[GoProWiFi] stop GoPro
</pre>

=Troubleshooting=
If RaceCapture/Pro cannot control the camera, check the following:
* '''GoPro WiFi network name (SSID) and password''': Ensure the name and password currently in the script matches how your GoPro was configured.
* '''Enable WiFi on the GoPro''': The blue LED on the GoPro should be blinking periodically
* '''RaceCapture/Pro WiFi module connection''': Ensure the module is plugged into the outermost RJ11 port and the green LED is illuminated.
* '''Verify WiFi connection''': Ensure RaceCapture/Pro can connect to the GoPro WiFi network. You should see the following messages in the log upon power-up:
<pre>
[lua] Successfully loaded script.
[GoProWiFi] initializing
[GoProWiFi] ready for GoPro
</pre>

If RaceCapture/Pro cannot connect to the GoPro's network you will see this in the log:
<pre>
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
</pre>

=Lua Script for GoPro=

The following Lua Script enables WiFi control of your GoPro camera.

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''GoPro WiFi password''': Specify the WiFi password used for the GoPro WiFi adapter
* '''GoPro SSID''': Specify the GoPro WiFi network name (SSID)

===Optional===
* '''goproStart''': Change this if you want to start recording at a different threshold.
* '''goproStop''': Change this if you want to stop recording at a different threshold. '''Ensure this is less than the start trigger'''
* '''tickRate''': Adjust this to update how often you want RaceCapture/Pro to perform a start/stop check. Value is in Hz. If uncertain, leave this alone
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
--Specify your GoPro wifi password here
goproPwd = '12345678'

--Specify your GoPro SSID here
goproSsid = 'aslhero1'

--Speed threshold to start recording
goproStart = 10

--Speed threshold to stop recording
goproStop = 5

--How fast we check, in Hz
tickRate = 10

--Set this to 1 to log communications between RCP & WiFi
debug = 0
-----------------------------
--DO NOT EDIT BELOW
-----------------------------
--the serial port where the WiFi is connected
port = 4
--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000

function logMsg(msg)
println('[GoProWiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpGet(url)
sendAt('AT+CIPSTART="TCP","10.5.5.9",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local get = 'GET ' ..url ..' HTTP/1.0' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#get))
sleep(100)
sendRaw(get)
sleep(100)
sendAt("AT+CIPCLOSE")
end

function sendGoProShutter(cmd)
httpGet('/bacpac/SH?t=' ..goproPwd ..'&p=%' ..cmd)
end

function startGoPro()
logMsg('start GoPro')
sendGoProShutter('01')
end

function stopGoPro()
logMsg('stop GoPro')
sendGoProShutter('00')
end

recording = 0

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..goproSsid ..'","' ..goproPwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for GoPro')
end
end

function checkGoPro()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to GoPro')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
trigger = getGpsSpeed()

if recording == 0 and trigger > goproStart then
startGoPro()
recording = 1
end
if recording == 1 and trigger < goproStop then
stopGoPro()
recording = 0
end
end

function onTick()
checkGoPro()
end

setTickRate(tickRate)
</pre>

=Lua Script for Garmin Virb=

The following Lua Script enables WiFi control of your Garmin Virb camera using the Garmin [https://developer.garmin.com/downloads/virb/Camera_Network_Services_API_v0.5.pdf Camera Network Services API]. 
'''NOTE''': this Lua script is different than the GoPro script above in that Garmin uses POST commands instead of GET commands. 
''For a more detailed explanation, see'' [https://forum.autosportlabs.com/viewtopic.php?t=6267 How to send HTTP POST request via Lua Script?] 
It may be possible to control other WiFi devices by altering the POST command accordingly. e.g. instead of sending httpPost arguments {"command":"startRecording"} substitute this with the commands specified by the device API. 

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''Ssid''': Specify the WiFi network name (SSID)
* '''Pwd''': Specify the WiFi password

===Optional===
* '''Port''': 5 is the WiFi port for the RaceCapture/Track MK2. Change according to [https://wiki.autosportlabs.com/RaceCapturePro_Lua_Scripting#Port_mappings Port mapping]
* '''autoStart''': Change this if you want to start recording at a different threshold.
* '''autoStop''': Change this if you want to stop recording at a different threshold.
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
setTickRate(10) --TickRate is in Hz
--configure WiFi serial port
port = 5
initSer(port,115200,8,0,1)
--Specify client SSID here
Ssid = 'VIRB-4615'
--Specify client wifi password here
Pwd = '12345678'
--Set this to 1 to log communications between RCP & WiFi
debug = 0

--initialize variables
trigger = 0
recording = 0

--define constants
autoStart = 0 --Threshold to start recording
autoStop = 1 --Threshold to stop recording

------WiFi Code--------------
--DO NOT EDIT BELOW
-----------------------------

--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000
reps = 3 --number of times to repeat command

function logMsg(msg)
println('[WiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpPost(cmd)
sendAt('AT+CIPSTART="TCP","192.168.0.1",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local post = 'POST /virb HTTP/1.1\r\nHost: 192.168.0.1\r\nAccept: */*\r\nContent-Length: ' ..toInt(#cmd)..'\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n' ..cmd ..'\r\n' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#post))
sleep(100)
sendRaw(post)
if debug == 1 then println(post) end
sleep(100)
sendAt('AT+CIPCLOSE')
end

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..Ssid ..'","' ..Pwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') or string.match(line, 'WIFI CONNECTED') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for WiFi')
end
end

function checkWiFi()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to WiFi')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
--trigger = getGpsSpeed()
trigger = bit.rshift(bit.band(getChannel("77AB2"),0x40),6)
--trigger = 1
if recording == 0 and trigger > autoStart then
for i=1,reps,1
do
httpPost('{"command":"startRecording"}')
end
recording = 1
end
if recording == 1 and trigger < autoStop then
for i=1,reps,1
do
httpPost('{"command":"stopRecording"}')
end
recording = 0
end
end

function onTick()
checkWiFi()
--println('trigger value: ' ..trigger)
--println('recording status: ' ..recording)
if debug ==1 then println("WiFi Status: " ..wifiStatus) end
end

</pre>

A few comments:
* The POST command is repeated the number of times specified by reps. This is because during testing the startRecording was not entirely reliable. The camera somehow missed the command.
* The trigger condition is set to use bit 6 of the CAN channel 77AB2. This signal comes from a switch on the dashboard wired to an ECU, which then sends switch status on the CAN to which the RaceCapture/Track MK2 is connected. Modify accordingly if you have a similar switch, otherwise comment this out and uncomment the getGpsSpeed() line, altering the autoStart and autoStop thresholds accordingly.

AutomaticCameraControl

2020-05-17T18:48:21Z

GTIspirit: /* Lua Script for Garmin Virb */

=Automatic Camera Control=

==Introduction==
This guide shows you how to enable automatic start / stop control of WiFi enabled cameras, such as GoPro using RaceCapture or PodiumConnect.

==How it works==
Most action cameras offer a WiFi interface for remote control. GoPro is one such camera, and allows shutter control via the WiFi interface, which RaceCapture or PodiumConnect can leverage for automatic triggering.

===Currently supported versions of RaceCapture hardware===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2
* RaceCapture/Pro MK2 with external WiFi add-on (see below)

===Currently supported cameras===
* GoPro Hero 2/3
* GoPro Hero 4/5 (experimental)
* Garmin Virb Ultra 30 (experimental)

Note, We recommend GoPro 2/3 due to stability / reliability issues seen with the later GoPro devices.

Additional Camera support will be added with future firmware releases.

==Overview==
RaceCapture or PodiumConnect is configured so it's WiFi client connects to the camera's access point using its SSID and WiFi password.

When RaceCapture/PodiumConnect triggers the camera based on a sensor threshold such as speed, RPM or other value, it sends a command to the camera to start recording. When the sensor falls below the threshold, the corresponding command is sent to stop the recording.

===Simultaneous WiFi connection with the RaceCapture App===
Since the WiFi client feature is used on RaceCapture/PodiumConnect to connect to the camera, the Access Point remains available for the RaceCapture app to connect via WiFi, as usual. Or, via Bluetooth, if supported by the RaceCapture system.

[[Image:automatic_camera_control.jpg|400px]]

==Setting up Automatic Camera Control==

===Applies to===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2

==Requirements==
* Firmware 2.13.0 or higher

===Set up WiFi client===
Navigate to Setup / Wireless and ensure:
* WiFi is turned '''ON'''
* WiFi client is turned '''ON'''
* Camera SSID and password are specified in the WiFi client settings.

[[image:WiFi_camera_control_config.png]]

===Set up Automatic Control===
Navigate to Setup / Automatic Control and ensure:
* The desired sensor channel trigger is selected (Speed is the default)
* Your start / stop and time thresholds are configured
* Camera Control is turned '''ON''' and you have your camera model selected.

[[Image:automatic_control_camera_settings.png]]

===Write Settings===
Write the settings back to RaceCapture by pressing the '''Write''' button under Setup.

==Testing==
Turn on the camera and ensure the camera has it's WiFi interface enabled.

Power up RaceCapture, connect the RaceCapture app and verify the WiFi client is connected under the System Status page.
[[image:verifying_wifi_client_connected.png]]

It may take several seconds for the client to connect. If not, re-check the camera's SSID/password, and ensure WiFi is enabled on the camera.
* '''Note''': On GoPros, the Camera must be in 'App mode' with WiFi enabled.

Once it is connected to the camera, you can test the camera by triggering the configured camera's threshold.
* '''Tip''': For static testing, you can configure the camera control to one of the Accelerometer channels, such as '''AccelZ''' and trigger by inverting RaceCapture. Or, use RPM, battery voltage or similar.

==RaceCapture/Pro MK2==
While the automatic camera control firmware feature is not available for RaceCapture/Pro MK2, it can still be controlled via a Lua script.

[[image:RaceCapture_WiFi_GoPro_control_diagram.png]]

When WiFi is enabled on your GoPro camera it creates a network that other devices can connect to. A WiFi enabled version of RaceCapture/Pro can connect to this network and issue the appropriate commands to control various camera functions - in this case, starting and stopping video recording.

Starting and stopping the GoPro can be controlled by a variety of means: speed, RPM or based on other sensor data, enabled by a Lua Script running on RaceCapture/Pro.

This guide focuses on using GPS speed to trigger the camera; for triggering on other sensors see the [[RaceCapturePro_Lua_Scripting|Lua scripting guide]] as a reference for what other sensor data is available.

==Notes==
* Currently, the WiFi module can only be used to enable GoPro triggering.
* '''If running firmware version 2.10.x or higher''' To use this script, you must disable the built-in WiFi control, or else it will take over the connection and block the script from running.
* Future versions of RaceCapture firmware and app will allow built-in firmware control of GoPro cameras, which will eliminate the need for this script.

==Requirements==
* RaceCapture/Pro MK2 running firmware 2.9.1 or higher
* [https://www.autosportlabs.com/product/racecapturepro-wifi-module/ RaceCapture/Pro WiFi module]
* WiFi enabled GoPro Hero camera, with WiFi activated
* GPS Connectivity (for speed measurement)

==Steps==

===Configure your GoPro===
Using the GoPro app, configure the WiFi network, making a note of the network name (SSID) and password.

===Connect the WiFi module===
Connect the RaceCapture/Pro WiFi module to the outermost (Auxiliary) port of RaceCapture/Pro.
* When powered up, you should see the power LED illuminate.
* This port is to the right of the Bluetooth Port.
** The WiFi module does not interfere with the operation of the Bluetooth module.

===Enable Lua script for GoPro connectivity===
Customize the Lua script shown at the bottom with the GoPro's WiFi network name (SSID) and password, then copy and paste the Lua script shown at the bottom into the scripting window of your RaceCapture/Pro.

Steps:
* Connect RaceCapture/Pro to the RaceCapture app and read the current configuration.
* Copy the Lua script into the Scripting window:
** Ensure the script window is first blank by removing the default script by deleting the text in the window.
*** '''Note''': If you have an existing script you want to keep, you will need to blend the camera functionality with your existing script. How to do this is beyond the scope of this guide; see the [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]] for more information.
** Copy the script into the window by using the '''ctrl-v''' keyboard shortcut.
* Write the configuration back to RaceCapture/Pro.

[[image:gopro_script.png]]

===Bench testing===
Once the Lua script is written to RaceCapture/Pro, it will attempt to connect to the network created by the GoPro camera. Once connected, it will be ready to issue start / stop commands to the camera.

[[image:GoProCameraControl_RaceCapture.jpg]]

Before road testing, ensure RaceCapture/Pro can connect to the GoPro's WiFi network by observing the messages in the window below the script.
* '''Tip 1''': Touch or click the '''Poll Log''' to see the current message in the RaceCapture/Pro log
* '''Tip 2''': To restart the Lua script, touch or click the 'Restart' button.

===Road testing===
Mount the GoPro in the car as usual and power up RaceCapture/Pro, waiting for GPS achieve a lock.

* Drive carefully above the speed threshold and observe the GoPro - you should hear and see the familiar beep and red light activate, just as if you manually started recording using the shutter button on the camera.
* When you drop below the threshold, the GoPro should stop recording.

As RaceCapture/Pro starts and stops the camera, you will see the following information in the log:
<pre>
[GoProWiFi] start GoPro
[GoProWiFi] stop GoPro
</pre>

=Troubleshooting=
If RaceCapture/Pro cannot control the camera, check the following:
* '''GoPro WiFi network name (SSID) and password''': Ensure the name and password currently in the script matches how your GoPro was configured.
* '''Enable WiFi on the GoPro''': The blue LED on the GoPro should be blinking periodically
* '''RaceCapture/Pro WiFi module connection''': Ensure the module is plugged into the outermost RJ11 port and the green LED is illuminated.
* '''Verify WiFi connection''': Ensure RaceCapture/Pro can connect to the GoPro WiFi network. You should see the following messages in the log upon power-up:
<pre>
[lua] Successfully loaded script.
[GoProWiFi] initializing
[GoProWiFi] ready for GoPro
</pre>

If RaceCapture/Pro cannot connect to the GoPro's network you will see this in the log:
<pre>
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
</pre>

=Lua Script for GoPro=

The following Lua Script enables WiFi control of your GoPro camera.

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''GoPro WiFi password''': Specify the WiFi password used for the GoPro WiFi adapter
* '''GoPro SSID''': Specify the GoPro WiFi network name (SSID)

===Optional===
* '''goproStart''': Change this if you want to start recording at a different threshold.
* '''goproStop''': Change this if you want to stop recording at a different threshold. '''Ensure this is less than the start trigger'''
* '''tickRate''': Adjust this to update how often you want RaceCapture/Pro to perform a start/stop check. Value is in Hz. If uncertain, leave this alone
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
--Specify your GoPro wifi password here
goproPwd = '12345678'

--Specify your GoPro SSID here
goproSsid = 'aslhero1'

--Speed threshold to start recording
goproStart = 10

--Speed threshold to stop recording
goproStop = 5

--How fast we check, in Hz
tickRate = 10

--Set this to 1 to log communications between RCP & WiFi
debug = 0
-----------------------------
--DO NOT EDIT BELOW
-----------------------------
--the serial port where the WiFi is connected
port = 4
--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000

function logMsg(msg)
println('[GoProWiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpGet(url)
sendAt('AT+CIPSTART="TCP","10.5.5.9",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local get = 'GET ' ..url ..' HTTP/1.0' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#get))
sleep(100)
sendRaw(get)
sleep(100)
sendAt("AT+CIPCLOSE")
end

function sendGoProShutter(cmd)
httpGet('/bacpac/SH?t=' ..goproPwd ..'&p=%' ..cmd)
end

function startGoPro()
logMsg('start GoPro')
sendGoProShutter('01')
end

function stopGoPro()
logMsg('stop GoPro')
sendGoProShutter('00')
end

recording = 0

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..goproSsid ..'","' ..goproPwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for GoPro')
end
end

function checkGoPro()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to GoPro')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
trigger = getGpsSpeed()

if recording == 0 and trigger > goproStart then
startGoPro()
recording = 1
end
if recording == 1 and trigger < goproStop then
stopGoPro()
recording = 0
end
end

function onTick()
checkGoPro()
end

setTickRate(tickRate)
</pre>

=Lua Script for Garmin Virb=

The following Lua Script enables WiFi control of your Garmin Virb camera using the Garmin [https://developer.garmin.com/downloads/virb/Camera_Network_Services_API_v0.5.pdf Camera Network Services API]. 
'''NOTE''': this Lua script is different than the GoPro script above in that Garmin uses POST commands instead of GET commands. 
''For a more detailed explanation, see'' [https://forum.autosportlabs.com/viewtopic.php?t=6267 How to send HTTP POST request via Lua Script?] 
It may be possible to control other WiFi devices by altering the POST command accordingly. e.g. instead of sending httpPost arguments {"command":"startRecording"} substitute this with the commands specified by the device API. 

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''Ssid''': Specify the WiFi network name (SSID)
* '''Pwd''': Specify the WiFi password

===Optional===
* '''autoStart''': Change this if you want to start recording at a different threshold.
* '''autoStop''': Change this if you want to stop recording at a different threshold.
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
setTickRate(10) --TickRate is in Hz
--configure WiFi serial port
port = 5
initSer(port,115200,8,0,1)
--Specify client SSID here
Ssid = 'VIRB-4615'
--Specify client wifi password here
Pwd = '12345678'
--Set this to 1 to log communications between RCP & WiFi
debug = 0

--initialize variables
trigger = 0
recording = 0

--define constants
autoStart = 0 --Threshold to start recording
autoStop = 1 --Threshold to stop recording

------WiFi Code--------------
--DO NOT EDIT BELOW
-----------------------------

--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000
reps = 3 --number of times to repeat command

function logMsg(msg)
println('[WiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpPost(cmd)
sendAt('AT+CIPSTART="TCP","192.168.0.1",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local post = 'POST /virb HTTP/1.1\r\nHost: 192.168.0.1\r\nAccept: */*\r\nContent-Length: ' ..toInt(#cmd)..'\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n' ..cmd ..'\r\n' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#post))
sleep(100)
sendRaw(post)
if debug == 1 then println(post) end
sleep(100)
sendAt('AT+CIPCLOSE')
end

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..Ssid ..'","' ..Pwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') or string.match(line, 'WIFI CONNECTED') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for WiFi')
end
end

function checkWiFi()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to WiFi')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
--trigger = getGpsSpeed()
trigger = bit.rshift(bit.band(getChannel("77AB2"),0x40),6)
--trigger = 1
if recording == 0 and trigger > autoStart then
for i=1,reps,1
do
httpPost('{"command":"startRecording"}')
end
recording = 1
end
if recording == 1 and trigger < autoStop then
for i=1,reps,1
do
httpPost('{"command":"stopRecording"}')
end
recording = 0
end
end

function onTick()
checkWiFi()
--println('trigger value: ' ..trigger)
--println('recording status: ' ..recording)
if debug ==1 then println("WiFi Status: " ..wifiStatus) end
end

</pre>

A few comments:
* The POST command is repeated the number of times specified by reps. This is because during testing the startRecording was not entirely reliable. The camera somehow missed the command.
* The trigger condition is set to use bit 6 of the CAN channel 77AB2. This signal comes from a switch on the dashboard wired to an ECU, which then sends switch status on the CAN to which the RaceCapture/Track MK2 is connected. Modify accordingly if you have a similar switch, otherwise comment this out and uncomment the getGpsSpeed() line, altering the autoStart and autoStop thresholds accordingly.

AutomaticCameraControl

2020-05-17T18:23:38Z

GTIspirit: Initial page for Garmin Virb camera control

=Automatic Camera Control=

==Introduction==
This guide shows you how to enable automatic start / stop control of WiFi enabled cameras, such as GoPro using RaceCapture or PodiumConnect.

==How it works==
Most action cameras offer a WiFi interface for remote control. GoPro is one such camera, and allows shutter control via the WiFi interface, which RaceCapture or PodiumConnect can leverage for automatic triggering.

===Currently supported versions of RaceCapture hardware===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2
* RaceCapture/Pro MK2 with external WiFi add-on (see below)

===Currently supported cameras===
* GoPro Hero 2/3
* GoPro Hero 4/5 (experimental)
* Garmin Virb Ultra 30 (experimental)

Note, We recommend GoPro 2/3 due to stability / reliability issues seen with the later GoPro devices.

Additional Camera support will be added with future firmware releases.

==Overview==
RaceCapture or PodiumConnect is configured so it's WiFi client connects to the camera's access point using its SSID and WiFi password.

When RaceCapture/PodiumConnect triggers the camera based on a sensor threshold such as speed, RPM or other value, it sends a command to the camera to start recording. When the sensor falls below the threshold, the corresponding command is sent to stop the recording.

===Simultaneous WiFi connection with the RaceCapture App===
Since the WiFi client feature is used on RaceCapture/PodiumConnect to connect to the camera, the Access Point remains available for the RaceCapture app to connect via WiFi, as usual. Or, via Bluetooth, if supported by the RaceCapture system.

[[Image:automatic_camera_control.jpg|400px]]

==Setting up Automatic Camera Control==

===Applies to===
* PodiumConnect
* RaceCapture/Apex
* RaceCapture/Pro MK3
* RaceCapture/Track MK1 and MK2

==Requirements==
* Firmware 2.13.0 or higher

===Set up WiFi client===
Navigate to Setup / Wireless and ensure:
* WiFi is turned '''ON'''
* WiFi client is turned '''ON'''
* Camera SSID and password are specified in the WiFi client settings.

[[image:WiFi_camera_control_config.png]]

===Set up Automatic Control===
Navigate to Setup / Automatic Control and ensure:
* The desired sensor channel trigger is selected (Speed is the default)
* Your start / stop and time thresholds are configured
* Camera Control is turned '''ON''' and you have your camera model selected.

[[Image:automatic_control_camera_settings.png]]

===Write Settings===
Write the settings back to RaceCapture by pressing the '''Write''' button under Setup.

==Testing==
Turn on the camera and ensure the camera has it's WiFi interface enabled.

Power up RaceCapture, connect the RaceCapture app and verify the WiFi client is connected under the System Status page.
[[image:verifying_wifi_client_connected.png]]

It may take several seconds for the client to connect. If not, re-check the camera's SSID/password, and ensure WiFi is enabled on the camera.
* '''Note''': On GoPros, the Camera must be in 'App mode' with WiFi enabled.

Once it is connected to the camera, you can test the camera by triggering the configured camera's threshold.
* '''Tip''': For static testing, you can configure the camera control to one of the Accelerometer channels, such as '''AccelZ''' and trigger by inverting RaceCapture. Or, use RPM, battery voltage or similar.

==RaceCapture/Pro MK2==
While the automatic camera control firmware feature is not available for RaceCapture/Pro MK2, it can still be controlled via a Lua script.

[[image:RaceCapture_WiFi_GoPro_control_diagram.png]]

When WiFi is enabled on your GoPro camera it creates a network that other devices can connect to. A WiFi enabled version of RaceCapture/Pro can connect to this network and issue the appropriate commands to control various camera functions - in this case, starting and stopping video recording.

Starting and stopping the GoPro can be controlled by a variety of means: speed, RPM or based on other sensor data, enabled by a Lua Script running on RaceCapture/Pro.

This guide focuses on using GPS speed to trigger the camera; for triggering on other sensors see the [[RaceCapturePro_Lua_Scripting|Lua scripting guide]] as a reference for what other sensor data is available.

==Notes==
* Currently, the WiFi module can only be used to enable GoPro triggering.
* '''If running firmware version 2.10.x or higher''' To use this script, you must disable the built-in WiFi control, or else it will take over the connection and block the script from running.
* Future versions of RaceCapture firmware and app will allow built-in firmware control of GoPro cameras, which will eliminate the need for this script.

==Requirements==
* RaceCapture/Pro MK2 running firmware 2.9.1 or higher
* [https://www.autosportlabs.com/product/racecapturepro-wifi-module/ RaceCapture/Pro WiFi module]
* WiFi enabled GoPro Hero camera, with WiFi activated
* GPS Connectivity (for speed measurement)

==Steps==

===Configure your GoPro===
Using the GoPro app, configure the WiFi network, making a note of the network name (SSID) and password.

===Connect the WiFi module===
Connect the RaceCapture/Pro WiFi module to the outermost (Auxiliary) port of RaceCapture/Pro.
* When powered up, you should see the power LED illuminate.
* This port is to the right of the Bluetooth Port.
** The WiFi module does not interfere with the operation of the Bluetooth module.

===Enable Lua script for GoPro connectivity===
Customize the Lua script shown at the bottom with the GoPro's WiFi network name (SSID) and password, then copy and paste the Lua script shown at the bottom into the scripting window of your RaceCapture/Pro.

Steps:
* Connect RaceCapture/Pro to the RaceCapture app and read the current configuration.
* Copy the Lua script into the Scripting window:
** Ensure the script window is first blank by removing the default script by deleting the text in the window.
*** '''Note''': If you have an existing script you want to keep, you will need to blend the camera functionality with your existing script. How to do this is beyond the scope of this guide; see the [[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]] for more information.
** Copy the script into the window by using the '''ctrl-v''' keyboard shortcut.
* Write the configuration back to RaceCapture/Pro.

[[image:gopro_script.png]]

===Bench testing===
Once the Lua script is written to RaceCapture/Pro, it will attempt to connect to the network created by the GoPro camera. Once connected, it will be ready to issue start / stop commands to the camera.

[[image:GoProCameraControl_RaceCapture.jpg]]

Before road testing, ensure RaceCapture/Pro can connect to the GoPro's WiFi network by observing the messages in the window below the script.
* '''Tip 1''': Touch or click the '''Poll Log''' to see the current message in the RaceCapture/Pro log
* '''Tip 2''': To restart the Lua script, touch or click the 'Restart' button.

===Road testing===
Mount the GoPro in the car as usual and power up RaceCapture/Pro, waiting for GPS achieve a lock.

* Drive carefully above the speed threshold and observe the GoPro - you should hear and see the familiar beep and red light activate, just as if you manually started recording using the shutter button on the camera.
* When you drop below the threshold, the GoPro should stop recording.

As RaceCapture/Pro starts and stops the camera, you will see the following information in the log:
<pre>
[GoProWiFi] start GoPro
[GoProWiFi] stop GoPro
</pre>

=Troubleshooting=
If RaceCapture/Pro cannot control the camera, check the following:
* '''GoPro WiFi network name (SSID) and password''': Ensure the name and password currently in the script matches how your GoPro was configured.
* '''Enable WiFi on the GoPro''': The blue LED on the GoPro should be blinking periodically
* '''RaceCapture/Pro WiFi module connection''': Ensure the module is plugged into the outermost RJ11 port and the green LED is illuminated.
* '''Verify WiFi connection''': Ensure RaceCapture/Pro can connect to the GoPro WiFi network. You should see the following messages in the log upon power-up:
<pre>
[lua] Successfully loaded script.
[GoProWiFi] initializing
[GoProWiFi] ready for GoPro
</pre>

If RaceCapture/Pro cannot connect to the GoPro's network you will see this in the log:
<pre>
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
[GoProWiFi] could not connect to GoPro
[GoProWiFi] initializing
</pre>

=Lua Script for GoPro=

The following Lua Script enables WiFi control of your GoPro camera.

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''GoPro WiFi password''': Specify the WiFi password used for the GoPro WiFi adapter
* '''GoPro SSID''': Specify the GoPro WiFi network name (SSID)

===Optional===
* '''goproStart''': Change this if you want to start recording at a different threshold.
* '''goproStop''': Change this if you want to stop recording at a different threshold. '''Ensure this is less than the start trigger'''
* '''tickRate''': Adjust this to update how often you want RaceCapture/Pro to perform a start/stop check. Value is in Hz. If uncertain, leave this alone
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
--Specify your GoPro wifi password here
goproPwd = '12345678'

--Specify your GoPro SSID here
goproSsid = 'aslhero1'

--Speed threshold to start recording
goproStart = 10

--Speed threshold to stop recording
goproStop = 5

--How fast we check, in Hz
tickRate = 10

--Set this to 1 to log communications between RCP & WiFi
debug = 0
-----------------------------
--DO NOT EDIT BELOW
-----------------------------
--the serial port where the WiFi is connected
port = 4
--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000

function logMsg(msg)
println('[GoProWiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpGet(url)
sendAt('AT+CIPSTART="TCP","10.5.5.9",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local get = 'GET ' ..url ..' HTTP/1.0' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#get))
sleep(100)
sendRaw(get)
sleep(100)
sendAt("AT+CIPCLOSE")
end

function sendGoProShutter(cmd)
httpGet('/bacpac/SH?t=' ..goproPwd ..'&p=%' ..cmd)
end

function startGoPro()
logMsg('start GoPro')
sendGoProShutter('01')
end

function stopGoPro()
logMsg('stop GoPro')
sendGoProShutter('00')
end

recording = 0

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..goproSsid ..'","' ..goproPwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for GoPro')
end
end

function checkGoPro()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to GoPro')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
trigger = getGpsSpeed()

if recording == 0 and trigger > goproStart then
startGoPro()
recording = 1
end
if recording == 1 and trigger < goproStop then
stopGoPro()
recording = 0
end
end

function onTick()
checkGoPro()
end

setTickRate(tickRate)
</pre>

=Lua Script for Garmin Virb=

The following Lua Script enables WiFi control of your Garmin Virb camera.

==Customization==
You will need to edit the following fields at the minimum, located at the top of the script:

===Required===
* '''Ssid''': Specify the WiFi network name (SSID)
* '''Pwd''': Specify the WiFi password

===Optional===
* '''autoStart''': Change this if you want to start recording at a different threshold.
* '''autoStop''': Change this if you want to stop recording at a different threshold. '''Ensure this is less than the start trigger'''
* '''debug''': If things aren't working as expected you can set this to 1 to see the conversation between the WiFi module and the GoPro.
** This information shows up in the log window below the script window - check the box '''Poll log''' to see this information.

<pre>
setTickRate(10) --TickRate is in Hz
--configure WiFi serial port
port = 5
initSer(port,115200,8,0,1)
--Specify client SSID here
Ssid = 'VIRB-4615'
--Specify client wifi password here
Pwd = '12345678'
--Set this to 1 to log communications between RCP & WiFi
debug = 0

--initialize variables
trigger = 0
recording = 0

--define constants
autoStart = 0 --Threshold to start recording
autoStop = 1 --Threshold to stop recording

------WiFi Code--------------
--DO NOT EDIT BELOW
-----------------------------

--indicates wifiStatus
--0 = not init, 1 = init sent, 2 = got IP, 3 = ready
wifiStatus = 0
lastInitTime = 0
initTimeout = 20000
reps = 3 --number of times to repeat command

function logMsg(msg)
println('[WiFi] ' ..msg)
end

function sendCrlf()
writeCSer(port, 13)
writeCSer(port, 10)
end

function sendRaw(val)
for i=1, #val do
local c = string.sub(val, i, i)
writeCSer(port, string.byte(c))
end
end

function sendAt(val)
if debug == 1 then logMsg('send: ' ..val) end
sendRaw(val)
sendCrlf()
end

function toInt(val)
return string.sub(val, 1, -3)
end

function httpPost(cmd)
sendAt('AT+CIPSTART="TCP","192.168.0.1",80')
sleep(500)
local crlf = string.char(13) ..string.char(10)
local post = 'POST /virb HTTP/1.1\r\nHost: 192.168.0.1\r\nAccept: */*\r\nContent-Length: ' ..toInt(#cmd)..'\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n' ..cmd ..'\r\n' ..crlf ..crlf
sendAt('AT+CIPSEND=' ..toInt(#post))
sleep(100)
sendRaw(post)
if debug == 1 then println(post) end
sleep(100)
sendAt('AT+CIPCLOSE')
end

function initWiFi()
logMsg('initializing')
sendAt('AT+RST')
sleep(2000)
sendAt('AT+CWMODE_CUR=1')
sleep(1000)
sendAt('AT+CWJAP_CUR="' ..Ssid ..'","' ..Pwd ..'"')
wifiStatus = 1
end

function processIncoming()
local line = readSer(port, 100)
if line ~= '' and debug == 1 then print(line) end
if string.match(line, 'WIFI GOT IP') or string.match(line, 'WIFI CONNECTED') then
wifiStatus = 2
end
if wifiStatus == 2 and string.match(line, 'OK') then
wifiStatus = 3
logMsg('ready for WiFi')
end
end

function checkWiFi()
if wifiStatus == 0 then
initWiFi()
lastInitTime = getUptime()
return
end
if wifiStatus == 1 and getUptime() > lastInitTime + initTimeout then
logMsg('could not connect to WiFi')
wifiStatus = 0
end
processIncoming()
if wifiStatus ~= 3 then
return
end
--trigger = getGpsSpeed()
trigger = bit.rshift(bit.band(getChannel("77AB2"),0x40),6)
--trigger = 1
if recording == 0 and trigger > autoStart then
for i=1,reps,1
do
httpPost('{"command":"startRecording"}')
end
recording = 1
end
if recording == 1 and trigger < autoStop then
for i=1,reps,1
do
httpPost('{"command":"stopRecording"}')
end
recording = 0
end
end

function onTick()
checkWiFi()
println('trigger value: ' ..trigger)
println('recording status: ' ..recording)
if debug ==1 then println("WiFi Status: " ..wifiStatus) end
end

</pre>

AutomaticCameraControl

2020-05-17T18:13:23Z

GTIspirit: /* Lua Script */

AutomaticCameraControl

2020-05-17T18:09:09Z

GTIspirit: /* Currently supported cameras */