Skip to main content

Aquila - OBD II Features

This page presents the public feature context for the Aquila OBD II GPS tracker and how those features are used with Plaspy. It describes user-facing capabilities, practical workflows, and the kinds of telemetry the device can send to a Plaspy server so fleet managers and technical evaluators understand how the tracker can fit into an operational deployment.

Exact feature availability and behavior can vary by device firmware, hardware revision, the specific vehicle interface, and how the manufacturer implements each capability. Consult the tracker vendor and the device documentation for definitive, model-specific technical details before deployment.

Feature Overview​

The Aquila OBD II is a plug-and-play OBD-II tracker that combines GPS location with onboard vehicle diagnostics to deliver location and vehicle parameter telemetry to a server. It is designed to collect both standard and some manufacturer-specific diagnostic parameters and send that data via cellular data to a remote platform for processing.

  • Real-time GPS location reporting combined with OBD-II diagnostic data for richer vehicle context.
  • OBD-II interface that can read standard PIDs and certain manufacturer specific parameters for diagnostics and monitoring.
  • Motion sensing using a 3-axis accelerometer to detect vehicle movement and trigger activity events.
  • Support for CAN and K-Line vehicle bus protocols to access a broad range of vehicle models.
  • Cellular GPRS data uplink using TCP/IP with connection optimizations to reduce traffic and preserve data usage.

Core Features of Aquila - OBD II​

  • OBD-II plug-in design for quick installation and access to vehicle diagnostics.
  • GPS location reporting for continuous position tracking and route visibility.
  • 3-axis accelerometer based motion sensing for movement detection and event generation.
  • Support for CAN and K-Line protocols to read vehicle bus data where available.
  • Ability to report vehicle battery voltage and basic electrical status.
  • Over-the-air configuration support to allow remote updates to device settings when provided by the manufacturer.
  • Automatic protocol detection to simplify integration with tracking servers.

How These Features Work with Plaspy​

Plaspy receives the telemetry and diagnostic data the Aquila OBD II sends and presents that information in ways that support monitoring and operational oversight. Plaspy automatically detects common tracker protocols and accepts device connections to the platform; Aquila devices may be configured to report into Plaspy using TCP or UDP to the Plaspy server domain.

  • Location data from the tracker appears on Plaspy maps and historical routes for tracking and replay.
  • OBD-II parameters and supported diagnostic PIDs received from the device are stored as telemetry and can be displayed as vehicle status or custom data fields.
  • Motion events generated by the accelerometer are reflected as movement or stop events inside Plaspy, helping with activity monitoring.
  • Power failure and battery voltage reports provide visibility of vehicle electrical state and can be surfaced as status alerts or dashboard indicators.
  • Plaspy can receive configuration messages and device telemetry over TCP or UDP to the platform domain, and the platform automatically detects tracker protocol for onboarding.

Typical Use Cases​

  • Fleet tracking with combined location and vehicle diagnostic context for maintenance planning.
  • Remote visibility into vehicle battery voltage and power events to reduce downtime.
  • Movement and stop monitoring using accelerometer-based motion detection for operational reporting.
  • Diagnostics-based fleet triage to prioritize vehicles for service based on reported parameters.
  • Plug-and-play installations for rapid deployment across large vehicle fleets.

Feature Availability Notes​

  • Some capabilities depend on the device firmware version and may change with manufacturer updates.
  • CAN and K-Line data availability varies by vehicle make, model, and year; not all vehicle parameters are available on every vehicle.
  • Optional features such as Bluetooth and specific manufacturer PIDs may not be present on every hardware variant.
  • Over-the-air configuration and advanced parameter reads depend on manufacturer support and the configuration options exposed by the device.

Why Use Plaspy with These Features​

Using the Aquila OBD II together with Plaspy gives teams a unified view of location and vehicle health signals in a single platform. Plaspy's device onboarding and protocol detection streamline integration so fleets can start consuming GPS and OBD telemetry rapidly, and then use the platform to monitor routes, detect motion events, and surface vehicle status in dashboards and reports.

Learn more about how Plaspy can work with compatible trackers on the Plaspy website https://www.plaspy.com. For the most current device features, firmware behavior, and manufacturer implementation details, verify information with the device maker at https://www.itriangle.in/.

Tracker Capabilities

See how these features fit into Plaspy

Plaspy helps turn compatible tracker capabilities into useful visibility, monitoring, and operational workflows across vehicles and assets.

Learn more about Plaspy