Skip to main content

Coban - GPS103 Protocol

This page provides public protocol context for using the Coban GPS103 tracker with the Plaspy platform. It explains how the device communicates in a general, non sensitive way and what to consider when configuring the tracker to report location and telemetry to Plaspy for vehicle monitoring and fleet management.

The Coban GPS103 is a vehicle focused tracker that supports SMS, GPRS, and internet data transmission and includes features such as accurate positioning, GPS drift suppression, multiple alarm types, remote cut off, and a TCP UDP switch for transport selection. Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol, while exact protocol behavior can vary by firmware version, hardware revision, and manufacturer implementation.

Protocol Overview​

The protocol for a device like the GPS103 is the set of rules that govern how the tracker identifies itself, how it packages and sends location and alarm data, and how a backend platform like Plaspy receives and interprets those reports. This section frames the role of that communication without relying on firmware specific internals.

  • Enables the tracker to send GPS coordinates, timestamps, and alarm events to a remote server for real time tracking.
  • Provides device identification and session context so Plaspy can associate incoming data with the correct unit.
  • Transmits periodic updates and on demand events such as SOS, overspeed, geo fence, and power state changes.
  • Supports multiple transports and addressing methods so devices can report over mobile data networks to a central endpoint.
  • Allows configuration commands and remote control options to be initiated from the server or through configuration tools when supported.

How Plaspy Detects the Protocol​

Plaspy receives incoming connections on a shared endpoint and automatically detects the tracker protocol so users typically do not need to select a protocol manually. Proper device configuration to point at the Plaspy endpoint is the key step for integration.

  • Plaspy listens at the public server domain d.plaspy.com and the server IP 54.85.159.138 on a single port used for all devices.
  • The platform inspects the incoming session and payload metadata to determine which device type and reporting style is being used.
  • If the GPS103 is configured to report to the Plaspy endpoint, detection is automatic and minimal user configuration inside Plaspy is required.
  • Automatic detection reduces setup steps when integrating many units across different models and manufacturers.
  • For edge cases or customized firmware, reviewing device reporting settings can help ensure correct detection.

Transport and Connection Context​

Transport selection and addressing determine how the device reaches Plaspy but not the higher level meaning of messages. The GPS103 supports common mobile data transports and can be configured to use either UDP or TCP depending on device support.

  • Devices may be configured to use either UDP or TCP on port 8888 depending on the GPS103 hardware and firmware configuration.
  • Trackers can point to the Plaspy server by domain d.plaspy.com or directly to the server IP 54.85.159.138 when DNS or carrier restrictions require it.
  • Plaspy uses port 8888 as the single shared port for all devices in the platform, simplifying device configuration.
  • Choosing TCP or UDP can affect delivery guarantees and network behavior but does not change the high level data the tracker sends.
  • When configuring many devices, use consistent transport and addressing to reduce variability in network behavior.

Protocol Compatibility Notes​

  • The GPS103 is compatible with Plaspy when the device is configured to report to the Plaspy endpoint and transport settings match platform expectations.
  • Firmware versions and hardware revisions can alter message timing, available fields, or supported commands; verify behavior on the unit in hand.
  • Some deployments use a TCP UDP switch or USB configuration tools to select transport and server address on the GPS103.
  • Manufacturer side variations or regional firmware builds may change available alarms or feature flags that affect integration.
  • Network operators and SIM profile constraints can influence GPRS or packet data connectivity and should be tested.
  • Always validate a small set of devices end to end before rolling out large scale monitoring to ensure consistent behavior.

Why Protocol Understanding Matters​

A practical understanding of the GPS103 communication protocol helps ensure reliable reporting to Plaspy, smooth onboarding of devices, and faster troubleshooting when issues occur. Knowing where transport, firmware, and configuration intersect makes deployments predictable.

  • Enables focused troubleshooting for connectivity problems, such as transport mismatches or incorrect server address.
  • Helps confirm that device identification and reporting cadence meet operational requirements for tracking and alerts.
  • Aids in selecting the correct transport mode and network settings for stable mobile data performance.
  • Improves planning for firmware updates or hardware changes that could affect reporting behavior.
  • Supports operational decisions such as alarm handling, data retention cadence, and event driven reporting.

Why Use Plaspy with This Protocol​

Using the Coban GPS103 with Plaspy gives organizations straightforward vehicle visibility and the operational tools to monitor location, alarms, and basic telemetry in a unified platform. The GPS103 feature set of real time tracking, multiple alarm types, and transport flexibility aligns with common fleet monitoring needs.

Plaspy is designed to accept reports from many tracker models using a single shared port and automatic protocol detection, which simplifies large scale deployments and device onboarding. To learn more about Plaspy and how it works with devices like the GPS103 visit https://www.plaspy.com. For the latest device specific protocol details, firmware notes, and manufacturer guidance please verify current information on the official Coban website https://www.coban.net/.

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