Devices¶
In this part of RaceStudio 3 you will see and manage all the AiM devices the PC is connected to.
The devices window is vertically divided in two parts: left and right.
The left part is the ‘filtering’ part, in which you can choose which connected AiM device you want to work with.
The right part is where you find some windows, each dedicated to a specific functionality.
Live View¶
This window is available only for the devices that feature a camera and support the capability of streaming videos, such as all the SmartyCam(s). You can, from here, fine tune the field of view of the camera directly from RaceStudio 3. You can also save a snapshot of what the camera is aiming, so to place all the overlays where eventually there’s space that can be covered.
Live Measures¶
This window shows you a table that shows the current values for all the channels the device is managing. You can calibrate channels, you can force channels values in order to test alarms. You can trigger the start recording logic.
Data Download¶
This window allows you to download all data and videos from AiM devices. The download process is the starting point for all the analyses you can do with data and videos.
Note
AiM Tech Tips short video, held by Bryc Talley, named “Downloading Data”.
Click here to open the August 9th, 2024 video.
WiFi and Properties¶
You can use this window to tune the configuration of the use of WiFi networks the devices do. Of course if the device doesn’t support the WiFi this part will not be visible. You can also pre-set some fields, such as Racer Name, Vehicle Name (or others) so to have those fields to be automatically populated in the download phase.
Settings¶
This window allows you to set device specific parameters. All what is here depends on firmware. It is normally useful for devices that doesn’t feature any human operatable display, as in these cases the RaceStudio 3 is the only interface to them.
Tracks¶
You can find in this window all the tracks (*.tkk files) that the device has in. The tracks files are very important for the device as they carry to the device all the major information to manage time zones and daylight saving time, they carry, even more important, all the information to the device for it to trigger lap times.
Predictive Reference Lap in Device¶
Please read more about predictive reference laps in Predictive Reference Lap.
In this window you can choose the strategy against which the device computes the predictive time. The prediction is always computed against a reference lap. Such a reference lap can be: the best lap of session, the best of the day, the previous lap or a reference lap saved by the RaceStudio 3 Analysis. In this latter case, you can choose in this window which are the analysis predictive reference laps files (*.prl files) you move into your device, and which of them will be used as default.
Please remember that the reference lap is strictly bound to a track configuration, and that there will be only one default reference lap file per track configuration. This behavior is similar but not identical to user pit lanes, described few lines below here.
User Pit Lane in Device¶
Please read more about pit lanes management in User Pit Lane.
In this window you can choose the strategy against which the device triggers the pit lanes computations.
Please remember that the user pit lane is strictly bound to a track start/finish line position. This implies that when two or more track configurations share the same start/finish line you can use in all those configurations the user pit lane defined for one of them. This behavior is similar but not identical to user predictive references, described few lines above here.
Counters¶
This window allows you to check the odometers stored into the device. You can set or reset them (some can be set, some can only be reset). In some devices, according to configurations, you can also see the fuel usage.
Firmware¶
This window allows you into a quick overview of the firmware versions of the device itself and of all the CAN expansions connected to it. One of the things that can be useful here is the “Export for AiM” functionality.