Enabling telemetry logging
Because of the added disk space requirements, the logging of telemetry details is disabled by default. To enable it, open the Options of the Second Monitor main application. There are three settings affecting the logging of telemetry data.
- Enable Telemetry - Enables or disables the logging of telemetry data
- Telemetry Data interval - Defines the minimal time interval, in miliseconds, between two data points. The default value of 16ms represents logging at 60fps. In reality the typical interval between two points will be bigger, because of internal delays, and frequency the data from simulators are fetched in general (most sims are fetched every 10ms).
- Maximum Session Stored - The application will keep only the most recent X sessions, to avoid consumed space creep. If the number of stored sessions exceeds this number, then the oldes session in deleted.
All completed, valid laps, are saved immediately after completion. A session is available for analysis after a first lap within that session is completed.
Note: Space Requirements: The space requirements for telemetry logging are not insignificant. A single 3.5 minutes lap on the default 16ms settings consumes around 20mb of harddrive storage. A full race session can easily require more than 400MB of data.
Note: Performance Impact of Telemetry Logging: There shouldn't be any perceived cpu usage increase because of telemery logging, as there is no filtering, or any other algorithmical processing, done on the data, and they are stored as they come.