Skip to main content

Meitrack - TA255 Configuration

This page documents the public configuration context for using the Meitrack TA255 tracker with Plaspy. It summarizes the shared Plaspy server settings you will apply on the device and provides practical SMS commands published for the TA255 series. Use this guide to prepare the tracker for reporting to Plaspy and to validate basic connectivity before completing a full deployment.

Plaspy uses a single shared server endpoint and port across supported devices and automatically detects the tracker protocol when data arrives. Manufacturer side setup steps can vary by firmware, hardware revision, installation type, and vendor configuration tools, so treat the commands here as a practical starting point and verify details against Meitrack documentation or your vendor tools as needed.

Configuration Overview​

The goal of configuration is to point the TA255 to Plaspy, confirm the device can reach the GPRS network, and verify that location and event data appear in the Plaspy platform. The TA255 supports SMS based configuration commands that many installers use to set a GPRS server, update intervals, and event reporting behavior.

  • Configure the device GPRS server to point at Plaspy so telemetry is delivered reliably.
  • Set an appropriate reporting interval to balance battery life and visibility.
  • Configure time zone and event reporting to ensure events are timestamped and handled correctly.
  • Validate connectivity to the Plaspy endpoint and confirm the device is visible in the Plaspy platform.
  • Keep a record of any changes to the default device password and configuration for ongoing support.

Plaspy Server Settings​

  • Server domain d.plaspy.com is the canonical Plaspy host for device configuration and DNS based setups.
  • Server IP 54.85.159.138 can be used where an IP based server entry is required by the device.
  • Port 8888 is the destination port Plaspy uses for all supported devices.
  • The TA255 may be configured to use UDP or TCP transported to port 8888 depending on device settings and installer preference.
  • Plaspy automatically detects the tracker protocol when the device connects so devices using the same port can be handled without per device protocol selection on the server side.
  • Note that all devices in Plaspy use the same port 8888 for uniform handling across device models.

Typical Requirements Before Setup​

  • A charged TA255 with working power and, if applicable, installed battery modules or solar charge connected.
  • A valid cellular SIM with data enabled and GPRS available for the target network region.
  • Access to a phone capable of sending SMS to the device for SMS based configuration, or the official Meitrack configuration tool if available.
  • The device default password if unchanged; the sample commands below use the TA255 default password 0000.
  • The correct APN settings for the SIM operator to allow GPRS connectivity.
  • Reference to official Meitrack documentation or firmware notes for variant specific commands and options.

How This Tracker Connects to Plaspy​

When configured, the TA255 sends location and event data to the shared Plaspy server endpoint and port so Plaspy can ingest, decode, and present device telemetry. Plaspy’s automatic protocol detection means the platform will identify the tracker protocol without additional per device protocol registration.

  • The device is configured to report to either d.plaspy.com or the IP 54.85.159.138 on port 8888.
  • Telemetry and events are delivered over the selected transport UDP or TCP to the single Plaspy port.
  • Plaspy decodes the incoming protocol automatically and makes the device visible in your Plaspy account once the device is associated.
  • Regular position updates, movement events, and configured sensor readings are forwarded to Plaspy for visualization and alerting.
  • Validation of reporting is done by confirming the device appears in Plaspy and that recent position timestamps match expectations.

Common Configuration Workflow​

  1. Access the official Meitrack configuration method or software, or prepare a phone to send SMS commands to the tracker as described by Meitrack.
  2. Enter the Plaspy server endpoint using either d.plaspy.com or the IP address 54.85.159.138 in the device server settings.
  3. Set the destination port to 8888, which is the single port used by Plaspy for all devices.
  4. Choose UDP or TCP if the TA255 requires a transport selection for GPRS reporting.
  5. Apply or save the configuration on the device and ensure the device accepts the setting (SMS response or software confirmation).
  6. Restart the device if the device or firmware requires a reboot for new network settings to take effect.
  7. Validate that the device reports to Plaspy by checking the device list and most recent telemetry in your Plaspy account.

Example Configuration Commands​

The TA255 supports SMS based configuration commands. The sample commands below use the device default password 0000. Replace the password prefix with your configured device password if you have changed it.

  • Factory reset or restore to factory settings

    0000,F11

    Note: Use this command as an optional initial step when you need to clear previous settings.

  • Set the GPRS server to the Plaspy IP address and port 8888 with APN placeholders

    0000,A21,2,54.85.159.138,8888,[apn],[apnu],[apnp]

    Explanation of placeholders

    • [apn] is the mobile network APN name required for GPRS data
    • [apnu] is the APN username if the operator requires one
    • [apnp] is the APN password if required by the operator Note: apnu and apnp are often optional and may be omitted if your SIM provider does not require them.

  • Set the time zone to UTC 0

    0000,B36,0

  • Set the location update interval to once per minute

    0000,A12,6,0

  • Configure basic event reporting

    0000,C03,0

Preserve the command order when applying them during initial setup if you rely on a factory reset or a sequential setup flow.

Configuration Notes​

  • Firmware and regional hardware variants may change available SMS commands or parameter formats; always check the Meitrack release notes for your TA255 variant.
  • The TA255 supports SMS based configuration as shown, but many installers prefer the Meitrack software tools for bulk provisioning and FOTA workflows.
  • When a device requires a transport choice, test both UDP and TCP if connectivity issues occur; Plaspy supports both transports on port 8888.
  • APN placeholders [apn], [apnu], and [apnp] must be filled with values provided by your mobile operator. Username and password are commonly optional.
  • If you change the device password from the default 0000, update your provisioning records and use the new password in subsequent SMS commands.

Why Use Plaspy with This Configuration​

Using the Meitrack TA255 with Plaspy gives organizations a straightforward path to continuous visibility and telemetry for trailers, containers, and other long term assets. The shared Plaspy server settings simplify large deployments because every device points to the same endpoint and port, and Plaspy automatically detects device protocols minimizing per device protocol management.

To learn more about Plaspy and how it supports device connectivity and fleet monitoring, visit https://www.plaspy.com. For device specific details, firmware updates, and the most current TA255 command references verify information on the manufacturer website https://www.meitrack.com/

Tracker Configuration

Need a platform for this tracker setup

Plaspy helps you connect compatible trackers, receive device data, and centralize monitoring from one GPS tracking platform.

Learn more about Plaspy