Skip to main content

Meitrack - TA255 Protocol

This page covers the public protocol context for using the Meitrack TA255 series GPS tracker with Plaspy. It explains how the TA255 reports location and telemetry to Plaspy, what to consider when configuring the device to communicate with the platform, and which connection details Plaspy uses publicly. The guidance is focused on high level protocol and connection considerations rather than device internals.

The TA255 is a rugged solar asset tracker designed for long term unattended deployments, and it supports GNSS positioning, multi network cellular, Wi Fi and Bluetooth sensors. Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol, but exact protocol behavior can vary depending on firmware version, hardware revision and manufacturer implementation. Always validate device specific behavior against Meitrack documentation when needed.

Protocol Overview​

At a high level, the device communication protocol is the set of rules the TA255 uses to announce its identity, send GNSS positions, report sensor telemetry and emit event notifications to a server. When integrated with Plaspy the protocol enables the tracker to deliver usable location and telemetry so Plaspy can visualize status, trigger alerts and store historical data.

  • The protocol transports periodic GNSS fixes and event driven messages such as motion, drop detection and input changes.
  • Telemetry payloads typically include sensor readings from BLE sensors, fuel sensors, temperature probes and internal accelerometers.
  • The protocol allows the tracker to identify itself so Plaspy can associate incoming data with the correct device record.
  • Heartbeat and status messages help Plaspy determine device health and connectivity for remote monitoring.
  • Configuration responses and over the air updates are coordinated outside of the basic reporting flow and may require specific manufacturer procedures.

How Plaspy Detects the Protocol​

Plaspy receives incoming device traffic on a shared endpoint and port and performs automatic protocol detection so users generally do not need to select a protocol manually inside Plaspy. Proper device configuration to point to Plaspy is the main prerequisite to let the platform recognize and process messages from the TA255.

  • Plaspy listens for device connections at the public server domain d.plaspy.com and the public server IP 54.85.159.138.
  • All devices in Plaspy use the same port so incoming traffic is consolidated for automated handling.
  • The active port for device reporting is 8888 and Plaspy supports trackers configured to report there.
  • Plaspy automatically detects the tracker protocol once the device starts reporting to the shared endpoint.
  • In most cases a TA255 configured to send data to d.plaspy.com or the provided IP on port 8888 will be identified by Plaspy without manual protocol selection.

Transport and Connection Context​

Connection context describes how the TA255 establishes transport to Plaspy and which addressing options are commonly used. This information helps administrators configure device endpoints and choose UDP or TCP based on the device firmware and network environment.

  • The TA255 may be configured to use either UDP or TCP for reporting depending on device support and configuration preferences.
  • Plaspy accepts device traffic on port 8888 so both UDP and TCP sessions directed to that port are supported for reporting.
  • Devices can target the Plaspy endpoint by domain name d.plaspy.com or by the public IP 54.85.159.138 when domain resolution is not available.
  • Using the shared port simplifies deployments because all supported devices report to the same Plaspy port.
  • Network level considerations such as carrier NAT, firewall rules and APN configuration can affect whether UDP or TCP works best for a given deployment.

Protocol Compatibility Notes​

  • Firmware versions can alter message timing, available telemetry fields and transport preferences, so check the device firmware level when diagnosing differences.
  • Hardware revisions or regional variants may include or omit peripherals such as BLE sensors or specific inputs that affect the reported telemetry set.
  • Manufacturer configuration options determine whether a TA255 uses UDP or TCP on port 8888; choose the transport supported by your firmware and network.
  • Plaspy relies on the device sending to the correct endpoint and port for automatic detection so ensure the device reports to d.plaspy.com or 54.85.159.138 on port 8888.
  • Features such as FOTA and remote configuration depend on manufacturer support and may require additional setup beyond basic reporting.
  • Validate any manufacturer supplied command interfaces or remote control features against official Meitrack guidance before use in production.

Why Protocol Understanding Matters​

Understanding how the TA255 communicates with Plaspy helps ensure a smooth setup, reliable operation and easier troubleshooting when issues arise. Familiarity with transport options, basic telemetry expectations and firmware dependencies reduces deployment friction and improves long term reliability.

  • Proper endpoint and port configuration is the most common cause of failed connections and is straightforward when the protocol and transport are understood.
  • Knowing whether your deployment should use UDP or TCP helps avoid intermittent connectivity caused by carrier or firewall behavior.
  • Awareness of firmware and hardware variation helps explain differences in reported telemetry and guides compatibility checks.
  • Understanding event types and telemetry cadence lets you tune reporting intervals to balance battery life and data freshness.
  • Clear knowledge of how the device identifies itself simplifies device provisioning and inventory management in Plaspy.

Why Use Plaspy with This Protocol​

Using the Meitrack TA255 with Plaspy provides a practical solution for organizations that need persistent visibility of trailers, containers and other remote assets. The TA255 hardware is designed for long life and low maintenance with solar charging and stackable batteries, while Plaspy handles incoming location and sensor telemetry for visualization, alerts and reporting.

Plaspy centralizes incoming TA255 data so fleet managers can monitor location, fuel levels, temperature, movement events and remote relay actions from a single platform. Because Plaspy uses a shared endpoint and the same port for all devices and automatically detects tracker protocols, integration is often straightforward when the TA255 is configured to report to d.plaspy.com or 54.85.159.138 on port 8888 using UDP or TCP.

To learn more about Plaspy visit https://www.plaspy.com. Protocol support, firmware behavior and device implementation details can change over time, so please verify current device specific protocol information and firmware notes with the manufacturer at https://www.meitrack.com/ before finalizing deployment plans.

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