Skip to main content

Bofan - PT-300X Configuration

This page covers the public configuration context for using the Bofan PT-300X tracker with the Plaspy platform. It focuses on the practical settings and SMS commands that are commonly used to point the tracker at Plaspy and validate basic connectivity. Where manufacturer commands are public, those examples are presented for convenience.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol when a device connects. Exact manufacturer-side setup steps can vary by firmware revision, hardware version, installation type, and vendor tools, so treat the commands and workflow here as practical, generally applicable guidance based on public information.

Configuration Overview​

The goal of configuration is to prepare the PT-300X to communicate reliably with Plaspy, validate connectivity, and enable device visibility and reporting in the platform. The PT-300X supports SMS and GPRS reporting using TCP or UDP, and the example commands below show a common SMS-based configuration flow that many installers use.

  • Configure the device identifier so Plaspy can associate reports with the correct asset.
  • Set the mobile data APN so the tracker can establish GPRS connections when using data reporting.
  • Point the device to the Plaspy server endpoint so location and event data are routed into the platform.
  • Define reporting interval so position updates meet your monitoring needs.
  • Validate connectivity and confirm the tracker appears in Plaspy after configuration.

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 when the device connects
  • All devices in Plaspy use the same port to simplify configuration

Typical Requirements Before Setup​

  • A powered and functional PT-300X unit with access to its SIM card or SMS-capable phone number.
  • A valid SIM with mobile data enabled and the correct APN for the mobile operator.
  • Access to the manufacturer configuration method such as SMS commands or official vendor software.
  • Knowledge of the device IMEI so you can derive or confirm the tracker identifier.
  • A tool or phone capable of sending SMS to the tracker number if using SMS-based setup.
  • Access to Plaspy account or administrator interface to confirm the device appears after setup.

How This Tracker Connects to Plaspy​

The PT-300X is configured to report to the shared Plaspy server endpoint and port so Plaspy can ingest location and event messages. Depending on your setup, the tracker sends periodic updates and event alerts to the platform over GPRS TCP or UDP, and some functions can be controlled or verified via SMS.

  • The tracker reports position updates at the configured time interval to the Plaspy server endpoint.
  • Event alerts such as overspeed, geofence trigger, low battery, or SOS are sent to Plaspy when generated by the device.
  • The device is set to use Plaspy server settings so location data is routed to the correct platform account.
  • Plaspy receives connections on port 8888 and automatically detects the tracker protocol, removing the need to select a protocol in most cases.
  • If SMS-based setup is used, commands are sent to the device phone number to update GPRS and server settings.

Common Configuration Workflow​

  1. Access the official manufacturer configuration method or software, or prepare to send SMS commands to the device phone number.
  2. Set the server address to d.plaspy.com or the server IP 54.85.159.138 as supported by the device.
  3. Set the server port to 8888 (Plaspy uses the same port for all devices).
  4. Choose UDP or TCP for transport if the device requires a transport selection.
  5. Configure the device identifier and APN using the manufacturer commands or tools.
  6. Apply or save the configuration on the device and restart the unit if required by the firmware.
  7. Validate that the device reports to Plaspy and appears in your Plaspy account or platform view.

Example Configuration Commands​

The PT-300X supports SMS-based configuration. Below are the public commands that can be sent as SMS messages to the device phone number. The sample setup uses the factory password 000000 by default. Replace placeholders where indicated.

  • Factory reset (optional initial step)
000000DFT

Note: This resets the device to factory defaults. Use only if you need to restore defaults before a fresh configuration.

  • Set 14 digit device identifier used with Plaspy
000000GID<14-digit-identifier>

Explanation: Use the last 14 digits of the IMEI as the identifier if you follow the common Plaspy convention. Replace <14-digit-identifier> with the actual 14 digits.

  • Set the APN for the operator
000000APN[apn],[apnu],[apnp]

Explanation: Keep the placeholders [apn], [apnu], and [apnp]. Fill [apn] with the operator APN. Use [apnu] for APN username and [apnp] for APN password if required by the mobile operator. If no username or password is needed, omit those values or leave them blank according to the device SMS syntax.

  • Set the GPRS server to Plaspy using the public IP and port
000000SVR54.85.159.138,8888

Explanation: This command points the tracker to the Plaspy server IP and port. The device may accept domain names in other firmware versions, but the public command shown uses the IP address.

  • Set the update interval to 1 minute
000000GTI60

Explanation: The value 60 represents 60 seconds interval for periodic position reports.

Important: The default device password in these examples is 000000. If the device password has been changed, prefix commands with the active password. Always confirm the correct SMS syntax for your device firmware version.

Configuration Notes​

  • SMS based configuration is supported and commonly used for PT-300X units; ensure your sending phone can reach the device number.
  • Firmware or regional variants may accept domain names or require different SMS syntax; consult manufacturer documentation when in doubt.
  • Choose UDP or TCP based on network behavior and any guidance from Plaspy or your carrier; Plaspy will detect the protocol automatically once the device connects.
  • Keep the device password secure and consider changing it after initial setup if supported by the device.
  • After applying server and APN settings, allow a few minutes and then validate the tracker appears in Plaspy to confirm end to end connectivity.

Why Use Plaspy with This Configuration​

Using Plaspy with the Bofan PT-300X gives organizations a straightforward path to centralize vehicle location and event data. The shared Plaspy server endpoint and consistent port reduce per-device configuration complexity, and automatic protocol detection simplifies onboarding so devices begin reporting with minimal manual protocol selection.

Learn more about Plaspy and how to integrate trackers at https://www.plaspy.com. For the latest device specific instructions, firmware details, and manufacturer guidance verify current information on the official Bofan site https://www.bofancloud.com/ as methods 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