Skip to main content

Meitrack - GT-30 Configuration

This page covers the public configuration context for using the Meitrack GT-30 with the Plaspy platform. It consolidates the Plaspy server settings you must apply and practical setup steps commonly used with the GT-30, including the SMS-based configuration commands that many installers use to point the device to a backend server.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol. Exact manufacturer-side setup steps can vary by firmware, hardware revision, installation type, and vendor tools. The GT-30 supports SMS and GPRS TCP or UDP communications and can be configured to report to a specified server or mobile number, so this guide focuses on the public, practical steps to register the device with Plaspy while advising you to check manufacturer documentation for firmware-specific behavior.

Configuration Overview​

The goal of the configuration process is to prepare the GT-30 so it reliably communicates with Plaspy and appears in the platform for tracking and event monitoring. This typically means setting the device communication server, transport, reporting intervals, and any event reporting settings required for your operational needs.

  • Configure the GT-30 to use the Plaspy server endpoint and port so location and event data reach the platform.
  • Set reporting intervals and event reporting so the device sends updates at the needed cadence.
  • Use SMS or the manufacturer tool to apply and verify settings, including APN placeholders where required.
  • Validate the device reaches Plaspy and that the platform receives position reports and events.
  • Optionally apply a factory reset or initial setup command when installing a device for the first time.

Plaspy Server Settings​

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support for UDP or TCP
  • Plaspy automatically detects the tracker protocol

These values are the public server settings you must use when pointing a GT-30 to Plaspy. Plaspy uses the same port for all supported devices, and the platform will detect the tracker protocol automatically.

Typical Requirements Before Setup​

  • A charged and powered GT-30 with working SIM and data capability for GPRS and SMS functions.
  • Knowledge of the device default password (the GT-30 default password in these commands is 0000).
  • Access to the official Meitrack configuration method you prefer (SMS commands, vendor software, or a configuration tool).
  • Valid APN settings for the SIM carrier where placeholders such as [apn], [apnu], and [apnp] will be required.
  • A test workflow to confirm the device reaches the Plaspy server and reports location or events to the platform.

How This Tracker Connects to Plaspy​

The GT-30 sends location and event data to the Plaspy server endpoint configured on the device. When configured to use GPRS, the tracker establishes a TCP or UDP session to the Plaspy server and then transmits periodic reports and event messages. If no live connection is available the device stores coordinates in internal memory for later upload once connectivity is restored.

  • The GT-30 is configured to report to the shared Plaspy server endpoint and port.
  • Reports are sent over GPRS using either UDP or TCP depending on configuration.
  • The tracker can send periodic position updates and event-triggered messages to Plaspy.
  • Plaspy receives those messages and automatically detects the protocol to parse tracker data.
  • If GPRS is unavailable, stored locations can be uploaded when the device regains connectivity.

Common Configuration Workflow​

  1. Access the official Meitrack configuration method or software you will use for setup, such as SMS or the vendor configuration tool.
  2. Enter the Plaspy server address as either d.plaspy.com or the server IP 54.85.159.138 in the device server configuration.
  3. Set the device port to 8888 which Plaspy uses for all supported devices.
  4. If the device requires explicit transport selection, choose UDP or TCP according to your preference or network reliability.
  5. Provide APN details if needed using placeholders like [apn] and optional [apnu] and [apnp] for APN credentials.
  6. Apply or save the configuration on the device, and restart the tracker if the device or instructions require it.
  7. Validate that the device reports to Plaspy by checking that the tracker appears in the platform and that location updates or events are received.

Example Configuration Commands​

The GT-30 can be configured using SMS commands. The following public SMS commands are commonly used for initial setup. The default device password used in these examples is 0000. If you change the password, substitute the new password in the same location.

  • Optional initial or factory settings reset (use when preparing a device for first installation):
0000,F11
  • Set the GPRS server to point to Plaspy using the Plaspy server IP, port, and APN placeholder. Replace [apn] with your carrier APN and add [apnu] and [apnp] if your APN requires username or password.
0000,A21,2,54.85.159.138,8888,[apn],[apnu],[apnp]

Note: You may use d.plaspy.com in place of the IP address when the device accepts a domain name for the server field.

  • Set the time zone to UTC 0 (modify as needed for your location):
0000,B36,0
  • Set the update interval to 1 minute (example command for periodic reporting):
0000,A12,6,0
  • Configure event reporting (example to set basic events):
0000,C03,0

Explanation of placeholders:

  • [apn] — APN provided by the SIM carrier
  • [apnu] — APN username if required
  • [apnp] — APN password if required

Send each command as an SMS to the GT-30 from an authorized phone number. After applying server and APN settings, confirm the device establishes a GPRS session and sends data to Plaspy.

Configuration Notes​

  • Firmware and hardware revisions can change command syntax or behavior; always confirm commands against the GT-30 manual for your firmware version.
  • The GT-30 supports SMS-based configuration as well as GPRS TCP or UDP; choose the transport best suited to your network and reliability needs.
  • Plaspy uses a single port (8888) for all devices and automatically detects the tracker protocol, so you do not need to assign a device-specific port.
  • If you use the factory reset command, treat it as an optional initial setup step; it may clear custom settings including passwords and reporting intervals.
  • Keep APN placeholders visible in commands and replace them with your carrier values when sending configuration SMS messages.

Why Use Plaspy with This Configuration​

Using the Meitrack GT-30 with Plaspy provides a straightforward way to collect position reports and event messages in a centralized platform. The GT-30’s support for GPRS TCP/UDP and SMS configuration makes it flexible to deploy, while Plaspy’s automatic protocol detection and shared server settings simplify backend setup so devices from many models can be managed consistently.

To learn more about Plaspy and supported workflows visit https://www.plaspy.com. For the most current device specific commands, firmware notes, and manufacturer guidance verify details on the Meitrack website https://www.meitrack.com/ as hardware and firmware behavior can change over time.

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