Skip to main content

Autoseeker - AT-18 Protocol

This page provides a public overview of the communication context for using the Autoseeker AT-18 tracker with Plaspy. It summarizes how the device reports location and basic telemetry to Plaspy and what the platform expects from compatible trackers, drawing on the AT-18 device description and Plaspy connection settings.

Plaspy uses shared connection settings for all supported devices and automatically detects the tracker protocol when a device reports to the Plaspy endpoint. Exact message timing, available telemetry, and command behavior can vary by firmware version, hardware revision, and manufacturer implementation, so this page focuses on public, non sensitive details useful for integration and troubleshooting.

Protocol Overview​

The AT-18 communicates location and status information over cellular data with SMS as a fallback. At a high level the device protocol defines how the tracker identifies itself, reports GPS positions and status signals such as ACC or low battery, and triggers alarm conditions that Plaspy can surface to users.

  • Enables periodic position reporting and event driven updates to Plaspy for real time visibility
  • Conveys basic telemetry such as ignition status, battery level, and alarm flags alongside location
  • Provides mechanisms to notify Plaspy about geofence breaches, overspeed events, and other configured alarms
  • Supports fallback reporting by SMS for critical alerts when packet data is unavailable
  • Allows Plaspy to map incoming reports to a device identity and to store history for reporting and analysis

How Plaspy Detects the Protocol​

Plaspy accepts incoming connections on a shared endpoint and port and performs automatic protocol detection so most devices will work without manual protocol selection in the platform. If the AT-18 is configured to report to Plaspy, the platform will match incoming reports to a compatible device profile and process the data for maps, alerts, and history.

  • Plaspy uses a common server endpoint and port for device reporting to simplify configuration
  • The device should be configured to report to d.plaspy.com or the Plaspy server IP to reach the platform
  • Plaspy automatically detects the tracker protocol for supported devices when data arrives
  • Users typically do not need to pick a protocol inside Plaspy if the tracker is correctly pointed at the Plaspy endpoint
  • If a device fails to register, checking device reporting settings and firmware versions is the usual next step

Transport and Connection Context​

The AT-18 is typically used with GPRS TCP reporting and can use SMS as a fallback channel. When integrating with Plaspy, the relevant transport and endpoint details are consistent across supported trackers so installation is straightforward and repeatable.

  • Devices may be configured to report to d.plaspy.com or to the Plaspy server IP 54.85.159.138
  • Plaspy accepts both UDP and TCP reporting on port 8888 depending on device support and configuration
  • The device may be configured using UDP or TCP on port 8888 to reach Plaspy
  • All devices in Plaspy use the same port which simplifies mass deployment and provisioning
  • Use the transport supported by the device firmware and the mobile operator environment for best reliability

Protocol Compatibility Notes​

  • Firmware revisions can alter message timing, supported fields, and optional telemetry; confirm behavior against the installed firmware
  • Hardware revisions or regional variants may expose different IO or alarm wiring; verify physical wiring for ACC and alarm inputs
  • Transport selection between TCP and UDP may affect delivery semantics and reporting reliability on some networks
  • SMS fallback behavior is manufacturer dependent and can vary in available fields compared to GPRS reporting
  • Always validate device identity and heartbeat reporting after initial installation to confirm Plaspy receives expected updates
  • Consult official manufacturer documentation to confirm any model specific commands or settings

Why Protocol Understanding Matters​

Understanding how the AT-18 communicates helps ensure a smooth setup and reliable long term operation with Plaspy. Knowledge of the reporting channel, expected telemetry, and alarm behavior reduces time to value and simplifies troubleshooting when devices do not appear on the platform as expected.

  • Helps confirm correct device configuration and endpoint settings so reports reach Plaspy
  • Speeds troubleshooting when position updates, alerts, or telemetry are missing
  • Supports decisions about transport selection for reliability in specific mobile network conditions
  • Informs expectations around SMS fallback limitations compared to packet based reporting
  • Aids in coordinating firmware updates and hardware swaps while preserving continuity of reporting

Why Use Plaspy with This Protocol​

Pairing the Autoseeker AT-18 with Plaspy gives organizations a straightforward way to collect real time GPS positions and essential telemetry from compact, covert trackers. The platform consolidates location feeds, surfaces alarms such as geofence breaches or overspeed events, and retains historical records for reporting and operational review. For fleet and asset managers the combination of AT-18 hardware and Plaspy software supports theft protection, route oversight, and basic usage monitoring.

To learn more about Plaspy and how it works with compatible trackers visit https://www.plaspy.com. Please verify device specific protocol support and the latest firmware and implementation details on the manufacturer website https://autoseekergps.com/ since protocol support and firmware behavior can change over time.

Tracker Communication

Looking for a platform that works with compatible protocols

Plaspy helps receive data from supported trackers and organize monitoring, visibility, and reporting in one place.

Learn more about Plaspy