Skip to main content

CanTrack - TK06A Protocol

This page provides the public protocol context for using the CanTrack TK06A tracker with the Plaspy platform. It explains how the device commonly communicates over cellular networks and what role the reporting protocol plays when sending location and status data to Plaspy. The information here is intended for system integrators, fleet managers, and technical users who want a clear, non sensitive overview of protocol behavior and server connection expectations.

Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol when a properly configured device reports to the platform. For Plaspy the server endpoint is d.plaspy.com and the server IP is 54.85.159.138. All devices use the same port and Plaspy accepts device connections on port 8888. Devices may be configured to use UDP or TCP on port 8888 depending on device firmware and user settings. Exact protocol behavior can vary by firmware version, hardware revision, and manufacturer implementation so users should validate device specifics with the manufacturer documentation.

Protocol Overview​

The protocol of the TK06A governs how the tracker formats and transmits GPS location, status, and alarm information over the cellular network so a backend like Plaspy can receive and process the data. For real time tracking this typically means sending periodic position reports and event messages via GPRS to an internet endpoint, while SMS can be used for individual queries or alerts.

  • Enables the tracker to report GPS coordinates and basic telemetry to a remote server for mapping and history.
  • Provides identification information so Plaspy can associate incoming messages with the correct device account.
  • Carries status and event flags such as ignition, power, overspeed, and alarm conditions that Plaspy can surface to users.
  • Supports different transport modes so devices can send data via GPRS in real time or via SMS for single reports.
  • Allows the device to receive simple control instructions or configuration replies where supported by the tracker and platform.

How Plaspy Detects the Protocol​

Plaspy is designed to accept incoming connections from many tracker models on a single endpoint and determine the device protocol automatically so users do not typically need to choose a protocol manually. When a CanTrack TK06A is pointed to the Plaspy endpoint and reporting over the configured transport, the platform will match the incoming data to a compatible protocol handler.

  • Plaspy listens on a single port for device reports and applies automatic protocol detection for incoming connections.
  • The Plaspy server domain is d.plaspy.com and the server IP is 54.85.159.138 which devices can use to report data.
  • All devices supported by Plaspy use the same port and the platform accepts both UDP and TCP on port 8888.
  • If a device is configured correctly to report to the Plaspy endpoint, users generally do not need to select a protocol inside Plaspy.
  • Automatic detection reduces setup steps but correct device address and transport settings remain essential for successful reporting.

Transport and Connection Context​

Transport selection and server addressing are fundamental for establishing a reliable link between the TK06A and Plaspy. The TK06A uses GSM GPRS for data transmission and can send position reports to an internet server over the cellular network. How the device is configured to reach Plaspy determines whether reporting is immediate and how events are forwarded.

  • Devices may be configured to point to the Plaspy server domain d.plaspy.com or directly to the IP address 54.85.159.138.
  • The Plaspy platform accepts connections on port 8888 and all supported devices use this same port.
  • The TK06A may be set to use either UDP or TCP on port 8888 depending on firmware options and the installer preference.
  • GPRS reporting is commonly used for continuous tracking while SMS remains an option for occasional location queries or alerts.
  • Verify network APN and GPRS settings on the device so it can establish a data session and reach the Plaspy endpoint.

Protocol Compatibility Notes​

  • Firmware versions can alter message behavior and available features so always check the device firmware release notes for protocol changes.
  • Hardware revisions or regional variants of the TK06A may implement slightly different reporting behaviors or default settings.
  • Transport choice between UDP and TCP may affect reliability and should match what is configured on the device and allowed by the network.
  • Manufacturer configuration commands and default APN settings are outside Plaspy and should be validated against official CanTrack documentation.
  • Using the Plaspy endpoint and port 8888 is required for automatic detection and centralized handling of incoming reports.
  • If you rely on SMS features, remember SMS delivery is separate from GPRS reporting and may be subject to carrier constraints.

Why Protocol Understanding Matters​

A practical understanding of the tracker protocol helps with initial setup, diagnosing reporting issues, and ensuring long term reliability of device data within Plaspy. Knowing what the device sends and how it connects makes it easier to align device configuration with Plaspy expectations and to interpret device behavior when events occur.

  • Speeds up initial configuration by confirming the correct server address and transport mode are set on the device.
  • Helps isolate problems such as missing reports, incorrect identification, or intermittent connectivity.
  • Assists in choosing device settings that balance update frequency, data usage, and battery life.
  • Improves alarm and event handling by ensuring the device reports the signals Plaspy expects.
  • Supports maintenance planning by clarifying which firmware versions and hardware revisions are in use.

Why Use Plaspy with This Protocol​

Using the CanTrack TK06A with Plaspy gives organizations a practical way to collect location and event data from vehicles and mobile assets while centralizing monitoring and reporting. Plaspy’s shared connection approach simplifies onboarding by requiring devices to point to a single endpoint and port, reducing configuration variability across a mixed fleet.

Plaspy is a useful option for fleet managers and operators who want consolidated visibility, historical tracking, alarm management, and operational reporting from devices like the TK06A. To learn more about Plaspy and platform features visit https://www.plaspy.com. Protocol support, firmware behavior, and device implementation details can change over time so verify the latest device specific protocol and firmware information with the manufacturer at https://www.cantrackgps.com/.

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