The ArrowPoint Telemetry system is designed to very light weight in terms of physical infrastructure.
In a race environment TeamArrow runs the entire system on a single i7 laptop with an SSD hard drive. However, since the solution does store substantial amounts of information we would recommend at a minimum a 256GB SSD with 100GB free storage for a race environment.
The system has been tested on Windows 10 and Amazon EC2 Unix, but should run on any form of Unix that supports Docker (including Apple Laptops). As the system is passive apart from a couple of key features, it is possible to run two instances of the solution on two laptops and achieve high availability. Laptops make much more sense than dedicated hardware or PCs in a race environment as the battery in a laptop is fundamentally built in and the power supply problems are much simpler in a chase car when running low power electronics.
The software infrastructure required to run the ArrowPoint Telemetry system is complex and the simplest way to install the solution is using Docker. Docker is a container management solution designed to provide containers for applications or in our case application components such as a database or Splunk. The containers then run on a docker instance which is installed on your PC. Prohelion has prepared Docker containers with the right setup for your database and Splunk configuration. While you can setup these manually, it’s complex and we wouldn’t recommended it. If you are not wanting to use Docker then please see the Docker Free Installation information below.
To install the ArrowPoint Telemetry system download a copy of the code from the GitHub repository by cloning the code or downloading a release zip.
In the root directory of your download you will find a file called
This file contains the configuration information to run the software in Docker.
Docker does not support UDP traffic on its virtual network. As such the telemetry system cannot receive traffic from the CAN Bus devices such as the Tritum WaveSculptor. To get around this issue the infrastructure required to run the Telemetry system runs in Docker apart from the core application which runs as a stand alone Spring Boot Application and hence can access the UDP network directly.
Modify the hosts file on your machine to include the name of the three hosts used in the system. Information on how to modify your host file can be found on the following article from how to geek.
If you are just running the whole configuration on one machine then the hosts file should look like this
|3||Run the Docker configuration. Note the first time you run this command the system will need to download a lot of images from docker. It’s worthwhile doing this on a high speed network as you are probably going to be downloading 100’s of MBs worth of images.
|4||Run the main application, note again the first time you run this application a bunch of files will need to be downloaded from maven repositories, this is a one off event.
|5||To simulate some CAN Bus traffic to see the system operating you can run the command
|6||Open the appropriate console by going to the following URL:
ArrowPoint Console : http://localhost:9000 - Login: admin / passw0rd!
Splunk Console: http://localhost:8000 - Login: admin / passw0rd!
PgAdmin Console: http://localhost:5080 - Login: firstname.lastname@example.org / passw0rd!