DOCSEARCHbyAlgolia
Submit Docs

ATLAS by Motion Applied

website·Indexed 33 days ago

https://atlas.motionapplied.com

An advanced ecosystem for motorsport and engineering, featuring System Monitor for ECU configuration, calibration, and real-time telemetry. ATLAS supports local, cloud, and hybrid setups for data acquisition, including Burst Logging, CAN configurations, and SQL Race Management Studio (SRMS) for structured telemetry dataset storage.

Tokens
297K
Snippets
1.1K
Records
1.9K
Agent score
61%

What's inside ATLAS

  2. Overview of MA.DataPlatforms.Indexing Services

    The MA.DataPlatforms.Indexing solution is a microservice-based system designed for file and configuration indexing within Motion Applied's data platform. It consists of two primary services:

    1. Files Service (Port 5000): A general-purpose service for recursive directory scanning, metadata extraction (size, modification dates, checksums), and status tracking (Exist, Processed, NotFound, Error). It supports scheduled scanning via Quartz cron expressions.
    2. Configs Service (Port 5050): A specialized service for processing .cfg and .pgv files. It extracts configuration IDs, application versions, and header information, mapping relationships between CFG and PGV files.

    Both services support dual storage backends: MongoDB for production and LiteDB for development.

  3. Overview of System Monitor capabilities

    System Monitor is a software application designed for interfacing with Electronic Control Units (ECUs) and related systems. It is primarily used for trackside support, unit optimisation, dyno testing, development, and production. While optimised for Motion Applied systems, it can be adapted for third-party controllers via hardware modifications.

    Key capabilities include:

    • ECU Program Management: Uploading and downloading ECU program files.
    • Tuning: Modifying editable ECU parameters via Live Tune (instant) or offline, including automatic tuning with a Testbed.
    • Parameter Information Display: Real-time monitoring of measurement parameters for diagnostics.
    • Data Logging Configuration: Managing data logging specifically for TAG ECUs.
    • Sensor Configuration: Calibrating sensors and actuators, and configuring the DATALab system.

  4. Overview of the System Monitor Configuration API

    The Configuration API is a multi-platform gRPC interface available from System Monitor version 8.85 onwards. It is used for ECU programming and monitoring, mediating access to units via System Monitor across a network. It supports clients written in C#, C++, Python, Java, and Go.

    Key architectural details:

    • Threading: API calls are managed on a single-threaded basis; subsequent calls are blocked until previous requests complete.
    • Caching: Measurement values are cached on the API server for fast response times; these specific calls are not blocked by other actions. The cache update rate is configurable.
    • Compatibility: All information available via the legacy COM API is available via the Configuration Service.

  5. Overview of ATLAS Alarms

    Alarms in ATLAS allow users to define conditions over live or historical telemetry data. When a specified condition is met, ATLAS executes one or more predefined actions. Alarms evaluate on every incoming sample of the specified parameters or events. They can be configured within the software or defined in an Alarms.xal file.

  6. Overview of the Packet Writer Service

    The Packet Writer Service enables high-performance data publishing to Kafka topics. It supports multiple writing modes tailored to different data requirements: single packet writing for low-frequency critical data, batch operations for high-throughput scenarios, essential packet handling for critical routing, and stream-based routing for automatic topic/partition selection. Key performance features include asynchronous non-blocking writes, internal buffering, connection pooling, and optional Prometheus metrics for monitoring (requires admin privileges).

  7. Overview of ATLAS Developer APIs

    ATLAS provides a suite of API-first extensibility interfaces for integrating, automating, and extending telemetry and data analytics workflows across motorsport, automotive, aerospace, and simulation environments. These APIs support both real-time and historical data workflows.

  8. Overview of the Interpolation Module

    The Interpolation Module (alternatively referred to as the Data Reader or Data API Module) allows applications to subscribe to parameters at custom frequencies. It automatically performs interpolation or decimation on data received from the Sample Reader output, ensuring that the consuming application receives data at its desired sampling rate regardless of the original data frequency.

  9. Overview of RTA Schema Mapping Service

    The RTA Schema Mapping Service is part of the RTA Toolkit Services suite. It provides a repository to map source schemas (e.g., named fields in files, tables, or documents) to the RTA domain model. While the Config Service describes the RTA domain model, the Schema Mapping Service describes the relationship with the specific data storage technology. It exposes a gRPC interface for defining and querying these mappings and is strictly optional.

  10. Overview of System Monitor for TAG systems

    System Monitor is a configuration and monitoring tool for TAG systems used to manage how Electronic Control Units (ECUs) and data logging devices acquire and store data. It supports both live and offline data acquisition workflows and integrates with ATLAS for analysis. The tool is primarily divided into two functional areas: Logging (configuring data acquisition, storage, and telemetry) and Sensors (setup and calibration of software-calibrated and externally configured sensors).

  11. Overview of RTA Data Service

    The RTA Data Service is part of the RTA Toolkit Services suite, providing compact, high-performance telemetry storage. It supports sample rates from 0.001 Hz to 1 MHz and handles backfill (late samples and channels) with stable memory use and back-pressure control. It is designed for high-speed sample storage and retrieval without resampling or aggregation, specifically optimized for RTA. It is intended to be used alongside the Session, Config, Stream, and Gateway services.

  12. Overview of the Virtual Parameter Service (VPS)

    The Virtual Parameter Service (VPS) calculates virtual parameters (defined as FDL functions in ECU logging configurations) in real time and writes them back to the broker. This eliminates the need for downstream clients (like ATLAS) to perform redundant local calculations.

    Key Workflow:

    1. Connects to a Kafka broker via the Stream API.
    2. Listens for live telemetry sessions from ADS via the Bridge Service.
    3. Compiles FDL expressions into executable functions at runtime.
    4. Buffers incoming samples and calculates virtual parameter values.
    5. Writes results back to the Stream API as an associated session.