Skip to main content

TrackerKing - J14 Protocol

This page describes the public protocol context for using the TrackerKing J14 with Plaspy. It focuses on how the device communicates location and event telemetry in a way that Plaspy ingests for live maps, alerts and historical playback. The J14 is a compact wired vehicle tracker with GPS and BDS positioning, a rugged IP65 enclosure, and multiple alarm mechanisms that generate the events Plaspy consumes.

Plaspy uses shared connection settings across supported devices and automatically detects the tracker reporting protocol when a device is correctly pointed to the Plaspy endpoint. Exact protocol behaviour and feature availability can vary by firmware version, hardware revision and manufacturer implementation, so this page presents the public communication context rather than firmware level details.

Protocol Overview​

The tracker communication protocol is the mechanism by which the J14 sends GNSS fixes and alarm events to a remote backend. At a high level the protocol enables identification, telemetry delivery and event reporting so Plaspy can convert raw device messages into usable tracking data and alerts.

  • Carries device identity and time stamped location fixes so Plaspy can map positions to vehicles
  • Transmits alarm and event signals such as geofence, overspeed, movement and power loss for rule based alerts
  • Delivers periodic or event driven telemetry to support live tracking and historical playback in Plaspy
  • Allows configuration parameters and device acknowledgement flows when supported by the manufacturer
  • Provides the necessary context for Plaspy to correlate position data with vehicle signals when available

How Plaspy Detects the Protocol​

Plaspy receives incoming connections on a single shared endpoint and port and automatically detects the tracker protocol for supported devices. In most deployments the device simply needs to be configured to report to the Plaspy endpoint and Plaspy will classify incoming messages and handle them without manual selection of a protocol in the platform.

  • Plaspy listens on a common server endpoint for device reports and detects the protocol automatically
  • Users generally do not need to pick a protocol inside Plaspy if the device is pointed to the Plaspy endpoint
  • Proper device reporting configuration is the key requirement for automatic detection and correct ingestion
  • Protocol detection supports both continuous position streams and event driven messages
  • If you experience detection issues, verify device reporting settings and firmware behavior with the manufacturer

Transport and Connection Context​

The J14 can be configured to use standard network transports to forward its telemetry to Plaspy. Devices may be set to use UDP or TCP depending on device support and installer preference. For Plaspy deployments the public endpoint information is consistent across devices so installers can point units to the same destination.

  • Plaspy server domain for device reports is d.plaspy.com
  • Plaspy server IP address for direct routing is 54.85.159.138
  • The port used by Plaspy for device connections is 8888
  • Devices may be configured using UDP or TCP on port 8888 depending on device capabilities
  • All devices supported by Plaspy use the same port to simplify deployment and routing

Protocol Compatibility Notes​

  • Firmware revisions may change which messages or alarms are available and how they are reported
  • Hardware revisions can affect available inputs and the way events are signalled to the protocol
  • Manufacturer configuration options determine whether the device reports over UDP or TCP
  • Network or SIM related settings on the device can impact delivery timing and reliability
  • Always validate that the device is configured to report to the Plaspy endpoint to enable automatic detection
  • Consult the manufacturer for firmware specific behavior that may affect Plaspy integration

Why Protocol Understanding Matters​

Understanding the communication protocol helps installers and fleet operators set up J14 units reliably, troubleshoot reporting issues and interpret the events Plaspy surfaces. Knowledge of the reporting context reduces configuration errors and supports predictable behaviour in operational use.

  • Ensures device reporting is pointed to d.plaspy.com or the Plaspy IP so data reaches the platform
  • Helps diagnose missing telemetry by checking transport settings and firmware versions
  • Clarifies which events and alarms the device will forward to Plaspy for automated alerts
  • Improves installation quality by aligning power and mounting choices with expected operational behaviour
  • Enables informed conversations with manufacturers when firmware or feature gaps appear

Why Use Plaspy with This Protocol​

Using the TrackerKing J14 with Plaspy gives organizations continuous position visibility and actionable event telemetry for fleet management, asset protection and recovery workflows. The J14’s dual GNSS positioning and multi alarm capabilities supply the location and event signals Plaspy needs to support live monitoring, incident alerts and historical route analysis.

To learn more about deploying the J14 with Plaspy and the broader platform capabilities, visit https://www.plaspy.com. Please verify the latest device specific protocol details, firmware notes and installation guidance with the manufacturer at https://trackerking.cn/ since protocol support and firmware behavior can change over time.

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