Concox - VL103 Protocol
This page provides the public protocol context for using the Concox VL103 tracker with Plaspy. It explains how the device communicates in general terms, which connection endpoints Plaspy exposes publicly, and what to check when configuring the tracker to report location, status, and alerts to Plaspy. The guidance here is meant to help fleet administrators and integrators understand the communication role without exposing private implementation details.
Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol when a device reports to the Plaspy endpoint. Exact protocol behavior can vary by firmware version, hardware revision, and manufacturer implementation, so physical device features such as GPS, BDS, LBS positioning, buzzer controls, and remote listen-in availability may affect what data is reported and how it appears in Plaspy.
Protocol Overview
The VL103 communicates with backend platforms using the device's reporting protocol. That protocol is the set of rules the tracker uses to identify itself, send periodic location updates, and report alerts such as speeding, geofence events, low battery, vibration alerts, and other telemetry that the device supports.
- The protocol defines how the tracker identifies itself to the server so received messages can be associated with the correct asset.
- Telemetry such as GPS BDS LBS positions and basic status flags are delivered through the reporting mechanism supported by the device.
- Alerts generated by onboard features like the external buzzer audible warnings and low battery are transmitted as event reports.
- The protocol enables remote features to be triggered or acknowledged when supported, subject to manufacturer and firmware limitations.
- Standardized reporting lets Plaspy interpret incoming messages and present location and event information in the platform.
How Plaspy Detects the Protocol
Plaspy receives connections on a shared endpoint and automatically determines the device protocol from the incoming data stream. In most cases you do not need to select a protocol manually inside Plaspy when the device is configured to report to the Plaspy server.
- Plaspy exposes a single public server domain for device reporting at d.plaspy.com.
- The Plaspy server IP is publicly listed as 54.85.159.138 for environments that prefer numeric addressing.
- Plaspy listens on a single port for all supported devices which simplifies device configuration and deployment.
- When a tracker reports to the Plaspy endpoint Plaspy detects the protocol automatically and associates the device with the proper parser and handling.
- Proper device configuration (correct server address and transport) is typically all that is required for Plaspy to detect the tracker protocol.
Transport and Connection Context
Connection and transport choices govern how the VL103 sends data to Plaspy. The device can be configured to use either UDP or TCP depending on device firmware and local configuration preferences. Knowing the address and port to point the tracker at is a core step to getting the device to report.
- Devices may be configured to report to d.plaspy.com or directly to the numeric IP 54.85.159.138.
- Plaspy listens on port 8888 for device traffic and that port is used uniformly across all supported devices.
- The VL103 may support either UDP or TCP transport to the Plaspy endpoint; choose the transport supported by your firmware and network.
- Using the correct server address and transport typically causes the device to begin reporting to Plaspy where automatic protocol detection can occur.
- Confirm carrier and firewall rules allow outbound UDP or TCP to the Plaspy endpoint on port 8888.
Protocol Compatibility Notes
- Firmware revisions can change message timing, available fields, or optional features; always check device firmware notes when evaluating compatibility.
- Hardware revisions or region variants may affect which positioning systems are active such as GPS BDS or supplemental LBS data.
- Manufacturer-side configuration options determine whether certain events like remote listen-in or buzzer control are reported and how they are signaled.
- Transport selection (UDP versus TCP) may vary by device firmware and by the stability requirements of your deployment.
- Platform-side automatic detection eases integration but you should verify first connections and sample reports before large scale rollout.
- When in doubt, validate behavior on a single device and consult manufacturer documentation for firmware specific differences.
Why Protocol Understanding Matters
Understanding the tracker reporting protocol helps ensure reliable setup and long term operation with Plaspy. Even when Plaspy automatically detects the protocol, knowing the role of the protocol and common points of variation reduces setup time and speeds troubleshooting.
- It clarifies what data the tracker will send and how that data maps to fields visible in Plaspy.
- It helps you choose the correct transport and network configuration for stable reporting.
- It guides troubleshooting steps when devices fail to appear or send unexpected values.
- It informs decisions about firmware updates and how they might change reported behavior.
- It reduces integration surprises when deploying multiple hardware revisions or regional variants.
Why Use Plaspy with This Protocol
Using the Concox VL103 with Plaspy gives fleet operators a practical path to gather location, status, and alert data from small industrial and commercial trackers. Plaspy’s shared endpoint approach and automatic protocol detection reduce initial configuration complexity so you can focus on operational setup such as geofences, alerts, and reporting intervals.
To learn more about integrating devices like the VL103 and to review platform capabilities visit https://www.plaspy.com. Protocol support and device behavior can change with firmware and manufacturer updates, so please verify the latest device specific protocol and firmware details on the manufacturer site https://www.iconcox.com/.
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.