Skip to main content

GOTOP - A5G Protocol

This page provides public protocol context for using the GOTOP A5G vehicle tracker with the Plaspy platform. It focuses on how the device communicates in general terms, what connection settings Plaspy requires, and how that communication supports real time tracking, alarms, and telemetry without exposing sensitive implementation details. The A5G is a camera capable 4G+3G+2G tracker with RS232 and 1-wire interfaces and configurable alarms that make it well suited for fleet, taxi, rental, and anti theft applications when connected to Plaspy.

Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol when a device reports to the Plaspy endpoint, but exact protocol behavior can vary by firmware version, hardware revision and manufacturer implementation. This document explains the publicly useful aspects of that integration, including the Plaspy endpoint and transport options, while encouraging teams to confirm firmware specific details with the manufacturer.

Protocol Overview​

The tracker reporting protocol defines how the A5G identifies itself to a server, reports location and sensor data, and transmits alarm and status events for use by a fleet platform like Plaspy. On a high level the protocol covers device identification, periodic or event driven telemetry, and status updates that Plaspy consumes to populate maps, alerts and historical logs.

  • Enables the A5G to send GPS coordinates, GSM fallback location, speed, heading and sensor values to Plaspy for real time visibility.
  • Carries alarm and event information such as SOS, jamming, antenna cut, power cut, door and ignition events so Plaspy can trigger alerts and workflows.
  • Provides identification and status information that allows Plaspy to associate reports with the correct vehicle and device record.
  • Supports configurable reporting intervals and event triggers so operators can balance update frequency and data usage.
  • Works over standard network transports so the device can report to the centralized Plaspy endpoint for processing and display.

How Plaspy Detects the Protocol​

Plaspy’s platform accepts connections on a shared endpoint and port and is designed to automatically detect the tracker protocol when a properly configured device reports in. In most deployments the device simply needs to be configured to report to the Plaspy endpoint and choose an appropriate transport; Plaspy handles the rest without a manual protocol selection in the platform UI.

  • Plaspy’s public server domain for device reporting is d.plaspy.com and the server IP is 54.85.159.138.
  • Plaspy listens on port 8888 for device reports and all devices in Plaspy use the same port.
  • When the A5G is configured to report to d.plaspy.com or 54.85.159.138 on port 8888, Plaspy will accept the connection and perform automatic protocol detection.
  • Users typically do not need to select a protocol inside Plaspy if the device is sending to the Plaspy endpoint and is configured correctly.
  • If a device fails to communicate as expected, verifying network settings, firmware version and transport selection is the usual first step.

Transport and Connection Context​

The A5G can be set to use common network transports to reach Plaspy’s collection endpoint. Transport choice may depend on device firmware and configuration options offered by GOTOP, and operators should confirm available modes for their hardware revision before deployment.

  • The device may be configured to use UDP or TCP on port 8888 depending on device support and configuration.
  • Devices can point to the Plaspy domain d.plaspy.com or to the numeric server address 54.85.159.138 when configuring the reporting endpoint.
  • Plaspy uses the same port 8888 for all supported devices to simplify device configuration and network firewall rules.
  • Network considerations such as APN setup, SIM plan data routing and operator roaming behavior can affect connectivity to the Plaspy endpoint.
  • Ensure outbound traffic to d.plaspy.com on port 8888 is permitted from the vehicle network or cellular gateway used by the device.

Protocol Compatibility Notes​

  • Firmware variations can change available reporting modes, transport support and optional features such as camera event forwarding or sensor mapping.
  • Hardware revisions of the A5G may expose different interfaces or wiring for RS232, 1-wire and analog inputs; verify pinout and wiring for your unit.
  • Manufacturer configuration menus and default APN settings may differ by region or production batch; update settings to point to d.plaspy.com or 54.85.159.138 on port 8888.
  • Some advanced features such as remote immobilization or camera evidence transfer may require specific firmware or server-side handling that should be validated.
  • Transport selection (UDP versus TCP) can affect message reliability and delivery timing; choose the transport supported by your firmware and recommended by GOTOP for your use case.
  • Always validate device behavior after firmware updates as protocol tweaks or new features can change how the tracker reports.

Why Protocol Understanding Matters​

A practical understanding of the A5G communication protocol helps installers and operators set up devices correctly, troubleshoot connectivity issues, and ensure consistent data quality in Plaspy for daily operations and incident response.

  • Helps confirm the device is reporting to the correct Plaspy endpoint and transport so data appears in the right account.
  • Assists troubleshooting of missing telemetry by guiding checks for APN, outbound port 8888 access and server reachability to d.plaspy.com or 54.85.159.138.
  • Enables informed decisions about reporting intervals and event triggers to balance timeliness and cellular data costs.
  • Clarifies which sensor and alarm inputs map to Plaspy events so alerts and automation can be configured accurately.
  • Prepares teams to validate behavior after firmware upgrades or when swapping hardware revisions to avoid unexpected changes in reporting.

Why Use Plaspy with This Protocol​

Using the GOTOP A5G with Plaspy gives organizations consolidated visibility into vehicle location, alarms, driver events and optional camera or sensor data. Plaspy’s centralized dashboard and alerting convert the A5G’s telemetry into operational insights for routing, security, maintenance and compliance, benefitting fleets, rental operations and transport providers.

If you want to learn more about how Plaspy handles device integrations, visit https://www.plaspy.com to explore platform features and deployment guidance. Protocol support, firmware behavior and device implementation details can change over time, so please verify the latest A5G specific information and firmware notes with the manufacturer at https://www.gotop.cc/.

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