Skip to main content

Gelix - Gelix G Lite Protocol

This document covers the public protocol context for using the Gelix G Lite tracker with the Plaspy platform. It explains how the tracker communicates in general terms, what connection points Plaspy exposes, and the practical considerations that affect successful reporting and integration. The content focuses on public facing facts and avoids firmware or vendor private implementation details.

The Gelix G Lite is a receptionist telematics GPS tracker with GLONASS and GPS navigation, GSM GPRS connectivity, fast startup behavior, and optional integrations such as relay control, fuel level sensors, and CAN bus adapters. Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol, while exact protocol behavior can vary with firmware version, hardware revision, and manufacturer implementation.

Protocol Overview​

The protocol used by a Gelix G Lite device is the mechanism by which the tracker reports position, status, and auxiliary sensor data to a remote server and receives remote control commands where supported. For Plaspy this means the tracker must be configured to report to the Plaspy endpoint so the platform can receive and interpret the device messages.

  • Enables transmission of GNSS based location and time stamped telemetry to a backend service
  • Carries auxiliary data such as relay state, fuel sensor readings, and CAN bus derived metrics when available
  • Allows the device to identify itself so Plaspy can associate messages with the correct asset
  • Supports heartbeat and periodic reporting that keep the device visible in the platform
  • Provides a channel for remote command or configuration updates when the manufacturer firmware supports such features

How Plaspy Detects the Protocol​

Plaspy receives device traffic on a shared public endpoint and determines how to interpret incoming messages without requiring per device manual protocol selection in most deployments. If the Gelix G Lite is configured to report to Plaspy, the platform will attempt to match the incoming stream to a supported device pattern and handle decoding according to the detected format.

  • Plaspy listens on a common endpoint to consolidate device traffic and simplify configuration
  • The Plaspy server domain for device reporting is d.plaspy.com
  • The Plaspy server IP address for device reporting is 54.85.159.138
  • Plaspy uses the same port for all supported devices and automatically detects the tracker protocol
  • Typically there is no need to manually select a protocol inside Plaspy if the device is correctly configured to report to the Plaspy endpoint

Transport and Connection Context​

Connection transport and addressing are key to getting a Gelix G Lite to report to Plaspy. The tracker can use standard cellular GPRS to send data and may be configured to use either UDP or TCP depending on device firmware and the desired behavior. Ensuring the correct host and transport are set in the tracker configuration is the most common requirement for establishing a working link with Plaspy.

  • Devices may be configured to report to d.plaspy.com or directly to 54.85.159.138
  • The device may be configured using UDP or TCP on port 8888
  • All devices in Plaspy use the same port for reporting to simplify deployments
  • Choose UDP for lower overhead reporting or TCP when transport reliability and session state are preferred, according to device support
  • Verify the device APN and cellular connectivity to ensure that GPRS traffic can reach the Plaspy endpoint

Protocol Compatibility Notes​

  • Firmware revisions can change message timing, available fields, or optional features so always confirm the firmware level when troubleshooting
  • Hardware revisions and module variants may enable or disable features such as relay control, fuel sensor inputs, or CAN bus adapters
  • Manufacturer configuration defaults may differ from Plaspy expected values so update the device reporting host to d.plaspy.com or 54.85.159.138 and the transport and port to 8888 as needed
  • Some features depend on optional accessories or wiring, for example fuel sensors and CAN adapters, which affect the telemetry the device can send
  • Transport selection between UDP and TCP should match the device capability and the chosen configuration in the field
  • Validate compatibility against the manufacturer documentation for the specific firmware build shipped with your devices

Why Protocol Understanding Matters​

A practical understanding of the device communication protocol helps streamline setup, accelerates troubleshooting, and reduces time to operational readiness when integrating Gelix G Lite trackers with Plaspy. While Plaspy handles automatic detection and decoding wherever possible, having awareness of the device reporting settings and variant behavior improves outcomes.

  • Ensures the device is pointed to the correct Plaspy endpoint for immediate connectivity
  • Helps diagnose common issues such as missing telemetry, incorrect timestamps, or absent sensor readings
  • Guides decisions about choosing UDP or TCP based on network conditions and device support
  • Assists in confirming whether optional hardware features are expected to appear in platform data
  • Reduces support time by clarifying whether an issue is device side or platform side

Why Use Plaspy with This Protocol​

Using Gelix G Lite devices with Plaspy gives organizations a reliable pathway to collect GNSS based location, telematics, and accessory sensor data in a unified fleet management environment. Plaspy’s shared endpoint approach and automatic protocol detection simplify large scale rollouts and reduce the per device configuration burden when deploying mixed fleets of devices.

To learn more about Plaspy and how it works with devices like the Gelix G Lite, visit https://www.plaspy.com. For the latest device specific protocol details, firmware behavior, and implementation notes consult the Gelix manufacturer site at http://www.gelix.com/ since device support and firmware behavior can change over time and should be verified against official manufacturer documentation.

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